Mantas wrote: ↑
Tue, 19 May 2020, 21:11
Is it possible to parallel an Axpert 5K (145V SCC) with an Axpert MK2 5K (450V SCC)?
It's a tricky question.
I found this on the forum:
"** Firmware version 71.71...
I've updated that today to include some more recent firmware version numbers. Sorry for not keeping that page up to date.
Is the MKS II and the MK2 the same thing?
Where did you see "MK2"? I've not seen it. I would say it's the same thing.
If it is at all possible, what version FW do I need to install to make it work? Currently, the MK2 is on 71.80 and the Axpert 5K is on 72.70C, which was what was needed to make it work with an older 5KVA/4KW
72.70 and its patched versions have the same paralleling constant as PIP-5048MG/Axpert MKS IIs and their patched versions. I used to think that having the same paralleling constant was all that was needed for compatibility, though we had to revise that with our patched firmware (hence pseudo constants 118fz and the like in the parallel compatibility
post). But then we found other issues; it seems that the manufacturer has been lax with changing the paralleling constant when the CAN packet command set changes.
Considering specifically the combination 72.70 and 71.80 (for PIP-5048MG / Axpert MKS II, not
PIP-5048MK / Axpert King), I would highly not recommend it. 71.80 has five more CAN packets that it decodes and presumably sends; 72.70 will merely ignore them. There is no patched firmware for 71.80 that has the altered parameter ranges of 72.70c, that's why it would have to be factory firmware. Though if you're not using an LFP battery and don't intend to use dynamic charge control, that would not matter, and you could attempt to pair 72.70c with 71.80a.
There is one experiment that should be pretty safe to perform, and would perhaps put an end to speculation. You could temporarily attempt to parallel 72.70c and 71.80 (no firmware updating required), without connecting the outputs
. During a few minutes of running like that, see if you get the problem with NE coming up intermittently (see this post
). If it does, then it's definitely not going to parallel, and you can put that idea out of your mind. Perhaps power them up such that master and slave swap over if you don't get the problem, to see if it appears when master and slave swap over. Remember that allocation of master and slave is meant to be random, even though usually 99% of the time, they end up in a particular order.
If the above experiment fails to rule this out, and you don't use an LFP battery or dynamic charge control, you might consider flashing the MK2 to 71.80a and paralleling them for real, hoping that the lack of complete CAN command decoding won't be an issue. Again, I don't recommend this. The main missing command in 72.70c is related to clearing a flag that says we are the "reserve" master. That sounds to me like a subtle bug has been fixed.
Nissan Leaf 2012 with new battery May 2019.
5650 W solar, 2xPIP-4048MS inverters, 16 kWh battery.
1.4 kW solar with 1.2 kW Latronics inverter and FIT.
160 W solar, 2.5 kWh 24 V battery for lights.
Patching PIP-4048/5048 inverter-chargers.