On 2023/04/28 at 3:48 PM, birdibird said:

So, there is an unbalance between the batteries. And the 3rd battery must have given the #71 signal as protection.

I see that at this moment the batteries are not charging further than 91% again. (If I set the Axpert to user, it does continue to charge.)

I would try charging each battery individually to 100% with user settings and then connect them all up again and see if that helps balance them out.

I would rather separate the third module temporarily, see if each set gets to 100% on its own.

I worry that USE setting will allow far too fast a charge for the third module, which could damage the module or at least curtail its life. 

On 2023/04/28 at 3:48 PM, birdibird said:

What I do notice, looking in the history of Solar Assistant, that the batteries are not being charged full all the time.
The last time that they hit 100% was on 14/4. Then you see in the 2 weeks after they are being charged up to almost every 2 days 1V less, resulting in the max SoC yesterday on 91%. The previous date they hit 100% was March 27, which was the day I installed the patched 45.11 and display 12.21.

Before that they were running on unpatched 45.07 and display 12.13 and the last date before March 27 that they had 100% charge was January 17.

Is this something Dyness is doing in their BMS?

IIRC @mzezmanhas the same issue on a sunsynk with dyness batteries and he has to change to use mode once a week in order to charge them to 100%. It might just be the bms. @mzezmancan you help out at all?

2 hours ago, jumper said:

IIRC @mzezmanhas the same issue on a sunsynk with dyness batteries and he has to change to use mode once a week in order to charge them to 100%. It might just be the bms. @mzezmancan you help out at all?

No it wasn't me (at least I don't think so 🤣) I do have Dyness but they haven't displayed this behaviour but I also ensure to get them to 100% everyday

15 minutes ago, mzezman said:

No it wasn't me (at least I don't think so 🤣) I do have Dyness but they haven't displayed this behaviour but I also ensure to get them to 100% everyday

Oops, I obviously didn't recall correctly 😬

Hello,

I have an Axpert Max 7.2k from SolarPower24, with 90V bug at low light.

Firmware U1 88.02, Display U2 12.21. I don't know which chip it uses.

Which is the best firmware I can install to solve 90V bug?

Thanks

Edited May 16, 20233 yr by pongo

4 hours ago, pongo said:

Firmware U1 88.02, Display U2 12.21. I don't know which chip it uses.

Unfortunately, we have not seen a firmware update file for 88.xx. I've seen 45.xx for the '2809 processor, and 69.xx for the '28066 processor, and various 90.xx firmwares that could be for any model. So I don't know why yours has a different major version number to all these. Maybe there is some minor customisation for your reseller.

The best thing would be to complain to your supplier, maybe they will provide a firmware update file. It almost certainly won't solve the problem, but at least we can patch it to reduce the severity of the problem.

Thanks @Coulomb, I will try to contact supplier and see if I could have a firmware file.

Thanks

I'm trying to chase down a bug that appears to be in some of the 7.2 max inverters that prevents monitoring from reporting the second pv string data. The bug manifests itself in a couple of different ways. 1. Different versions of the inverter report the second string fine and other don't. 2. the ones that do work standalone when put into parallel then don't work.

It's incredibly annoying that we can't see where the power is actually coming from. I've tried all sorts of workarounds, but its impossible to get the correct amount all of the time so I really need to be able to read the second strings consistently. 

Has anyone else seen this?

9 minutes ago, Davo said:

I'm trying to chase down a bug that appears to be in some of the 7.2 max inverters that prevents monitoring from reporting the second pv string data.

Do you have firmware versions, particularly main (U1) firmware versions, for those that work and those that don't?

This seems likely to be a firmware issue.

Hello everyone need some serious help i currently have may be a clone of this inverter and i am getting issues like error 61 and that 90v stuck on a cloudy day can anyone direct me what  firmware i need to flash there and how can i do that thank you.My inverter model is currently PowMr MAx 7.2 which i guess identical to the axpert max thanks for reaching out anyone.

 

My inverter model is currently PowMr MAx 7.2 which i guess identical to the axpert max

Not necessarily so, although the stuck at 90 V issue makes it sound like they stole Voltronic firmware complete with its bugs. PowMr/Must models often seem to have non-standard firmware (settings numbers different, for example).

What firmware (main, U1) are you running now?

 

 

Not necessarily so, although the stuck at 90 V issue makes it sound like they stole Voltronic firmware complete with its bugs. PowMr/Must models often seem to have non-standard firmware (settings numbers different, for example).

What firmware (main, U1) are you running now?

I mess around flash firmware no more 90v but my bigest problem is trying ot have my lithium battery conneted to inverter through cable so inverter and battery can sync together,so what happen as of now since they cant sync togeter i am getting error 61 .The reason i currently not on error 61 because i go to user settings and inverter and battery still wont suync when ever battery get to like 58% it literally shuts down the house power in SBU mode so this i am really trying to get going so battery and invert can sync together.I am currently running one Orient Powerwall Battery with Pylontec BMS.See image of firmware version and battery i am using thanks.

 

Edited September 23, 20232 yr by kifo
Added battery pics

 

I am currently running one Orient Powerwall Battery with Pylontec BMS.

It sounds like your main problem is BMS cable pinout. Or perhaps the battery is not talking Pylontech protocol despite what it claims. Or maybe it only implements CAN bus Pylontech protocol; true Pylontechs can communicate either CAN bus or RS-485, but the inverter's display/BMS firmware only talks RS-485 to Pylontechs. Even though it talks CAN bus to some other BMS protocols.

You might be able to work around that with something like Solar Assistant, which can talk to the battery BMS and also to the inverter.

Those firmware versions sound like Axpert firmware. Without looking it up, (1)12.19 sounds relatively recent, so I don't think that you need to risk attempting to update the display/BMS firmware.

 

Thanks @Coulomb, I will try to contact supplier and see if I could have a firmware file.

Thanks

Hello,

finally my supplier has updated my inverter firmware from 88.02 to 69.06 (DSP 28066) to solve 90V bug.

I will check next days if it truly solves this bug and let you know.
I requested also to have original 88.02, so should be patched, but not yet received.

Edited September 30, 20232 yr by pongo

 

It sounds like your main problem is BMS cable pinout. Or perhaps the battery is not talking Pylontech protocol despite what it claims. Or maybe it only implements CAN bus Pylontech protocol; true Pylontechs can communicate either CAN bus or RS-485, but the inverter's display/BMS firmware only talks RS-485 to Pylontechs. Even though it talks CAN bus to some other BMS protocols.

You might be able to work around that with something like Solar Assistant, which can talk to the battery BMS and also to the inverter.

Those firmware versions sound like Axpert firmware. Without looking it up, (1)12.19 sounds relatively recent, so I don't think that you need to risk attempting to update the display/BMS firmware.

Hello i havent being able to solve this issue have tried many different wires with pin configuaration also i ahve been experencing F52 error where inverter shuts down can you help identify the issue please thank you.

 

Hello i havent being able to solve this issue have tried many different wires with pin configuaration also i ahve been experencing F52 error where inverter shuts down can you help identify the issue please thank you.

Check out this video, you might need to change the protocol on the BMS with PBMSTools if it is not set to Pylon485. The inverter should work on the PYL battery setting with dip setting 1000, if not then it is probably a wiring issue with your BMS cable.

 

 

finally my supplier has updated my inverter firmware from 88.02 to 69.06 (DSP 28066) to solve 90V bug.

I will check next days if it truly solves this bug and let you know.

I had a look at 69.05, the closest I have in my collection, and it's nothing special with respect to MPPT control. But it would be wonderful if they've finally fixed it.

This is fw they installed

MAX_7.2K_69.06.7z

Could you check, please?

They told me that this has 80A charge limit (against 120A of 88.02), has SoC % for parameters 12, 13, 29 when battery type <> USER.

Could you check, please?

 

Could you check, please?

Gladly!

One thing I noticed (and should have noticed when I perused 69.05) is that this firmware is for the '28066. If you have a '2809, this will not work at all (unless you force it, and then it would brick your machine).

Just thought I'd get that out quickly before I check your existing firmware.

Edit: Ah, yes, it was 88.02, and I don't have any 88.* to check. Hopefully they know what they are doing; just don't mix up and load the wrong firmware from another folder (as is sadly very possible with their new Arena reflash tool). At least, you will see the meaningful file name (as opposed to always being dsp.hex, no matter what's inside). Worst case then, the firmware upload doesn't do anything, but you restart the inverter and nothing is lost.

Edited October 3, 20232 yr by Coulomb
Added last paragraph.

 

They told me that this has 80A charge limit (against 120A of 88.02)

That's not how I read it. It seems to me that as long as it detects that it's a 230 V model (the same firmware can run a 120 V model), it should show up to 120 A. We'll see who can read code 🤓

 

has SoC % for parameters 12, 13, 29 when battery type <> USER.

That's harder for me to answer, because I don't know the BMS code all that well. But it sure looks like it's present to me, but was not present in 69.05. So it looks like they got that part right.

 

But it sure looks like it's present to me, but was not present in 69.05.

Oops! I had not finished analysis of 60.05; it turns out that 69.05 already had them. That doesn't make your supplier wrong, just that these BMS features didn't just turn up in this most recent version. BTW, the hex (actually .inv) file is dated 16-May-2023.

It took me a while to find out, having just recovered from what I think was a pretty spectacular crash💥. This must have been a Windows crash, or at least a driver level crash, because in userland you just can't (or certainly shouldn't be able to!) cause so much havoc.

 

I had a look at 69.05, the closest I have in my collection, and it's nothing special with respect to MPPT control. But it would be wonderful if they've finally fixed it.

Hello is there a way to hard reset this inverter to factory setting thank you.

 

is there a way to hard reset this inverter to factory setting thank you.

Yes, sending a PF command will reset all the user settings to defaults, leaving important things like calibrations and serial numbers (more important than you may think) alone.

Many monitoring programs can do this for you, even WatchPower. You can also use the Windows Communications Tool provided by Voltronic, e.g. from here. My old, waffling post on command sending is here.

With any of these methods, you will need a USB to serial adapter, or a very old computer with a serial port, and the serial to RJ-45 cable that should have come with your inverter.

Edited October 3, 20232 yr by Coulomb
Spelling

 

It sounds like your main problem is BMS cable pinout. Or perhaps the battery is not talking Pylontech protocol despite what it claims. Or maybe it only implements CAN bus Pylontech protocol; true Pylontechs can communicate either CAN bus or RS-485, but the inverter's display/BMS firmware only talks RS-485 to Pylontechs. Even though it talks CAN bus to some other BMS protocols.

You might be able to work around that with something like Solar Assistant, which can talk to the battery BMS and also to the inverter.

Those firmware versions sound like Axpert firmware. Without looking it up, (1)12.19 sounds relatively recent, so I don't think that you need to risk attempting to update the display/BMS firmware.

Solve the issue it was bascially the battery bms firmware suppose to pylon from factory don't know it was changed i got downloaded the battery support firmware and i change  to pylontech  and voila working the way it suppose it was the wire thanks for the help.