13 minutes ago, mihaigsm2003 said:

this i have, maibe not last...

Don't use inverter witout battery! Can destroy hardware

good luck!

Yea it is working. Let’s see tomorrow with solar energy. Thanks for the help man! U were awesome. I would never figure it out without your help. Now if someone needs help I will also be able to help a bit! 

Hi

 

did i see it right?

112.19 works in combination with 90.06 firmware ?

31 minutes ago, Georg594 said:

Hi

 

did i see it right?

112.19 works in combination with 90.06 firmware ?

Yes it’s working. But final tests will be tomorrow with sun. But all functions are working. Just Wi-Fi not working 

Confirmed today that everything is working great including Wi-Fi. Thanks everyone for the help and assistance! 

On 2022/11/19 at 6:14 AM, Georg594 said:

did i see it right?

112.19 works in combination with 90.06 firmware ?

My latest theory: Any 12.xx or 112.xx will work with recent DSP firmware, as long as xx is at least a certain value. In other words, at say xx=11 (wild guess!!), they fixed it so the display would work with either DSP chip (2809 or 28066, with flash command BDR96 or C28066 respectively). Still to be confirmed!

BUT! You probably have to use the right firmware for your display or DSP chip. If the major version number is ≥100, then you must have the 28065 DSP chip or the GD display chip. It seems like pretty sudden death if you get that wrong (or at the very least, you need a JTAG programmer, and in the case of the DSP, you also need a password).

I just checked, and 12.06 already has checks for BDR96, C28066, :28062, and :dsp001. So unless the problem is only with firmwares with xx < 06, I think my theory is busted. Or the changes for compatibility with any DSP are elsewhere, not just parsing the reflash command. Actually, that seems more likely, now that I think about it.

So: That's that cleared up. Not. 🤔😡

Edited November 20, 20223 yr by Coulomb

On 2022/11/18 at 11:51 PM, Gilberto said:

I think it's this?

original.hex 616.08 kB · 1 download

I was going to respond that I have good news and very bad news... The good news is that you appear to be able to read the chip; the bad news is that it has no firmware or even bootloader! It just has a series of endless loops, and 32-bit words that increment by 1 for each longword (32-bits). I don't have a GD32 bootloader, but fortunately, @mihaigsm2003 did, and was able to sort you out. Well done, both of you!

It's certainly good to know that a thorough bricking like this can at least sometimes be overcome.

11 hours ago, Gilberto said:

Confirmed today that everything is working great including Wi-Fi. Thanks everyone for the help and assistance! 

You can do backup of firmware and store, also can place here. 👍

Edited November 20, 20223 yr by mihaigsm2003

3 hours ago, Coulomb said:

I was going to respond that I have good news and very bad news... The good news is that you appear to be able to read the chip; the bad news is that it has no firmware or even bootloader! It just has a series of endless loops, and 32-bit words that increment by 1 for each longword (32-bits). I don't have a GD32 bootloader, but fortunately, @mihaigsm2003 did, and was able to sort you out. Well done, both of you!

It's certainly good to know that a thorough bricking like this can at least sometimes be overcome.

Thanks mate for the help over this week! This is not for the faint hearted 😂 but seems possible when u have the right firmware for the chip. 

1 hour ago, mihaigsm2003 said:

You can do backup of firmware and store, also can place here. 👍

Yea I’ve done that for future problems! Thanks again for your help. Without it this would not be possible! 

I thought the issues was sorted out. I have to limit my battery to max 45ah. Everytime my house demands more than 45ah the inverter shuts its self off and gives me error f52. Why does this happen? 

43 minutes ago, Gilberto said:

Everytime my house demands more than 45ah the inverter shuts its self off and gives me error f52.

? Battery "demand" is in amps or watts. Or do you mean if your battery is discharged to the point of an estimated 45 Ah of capacity, you see this fault code?

Fault code 52 is "bus voltage too low". 59.8 V seems very high for a battery, nearly any battery. What battery is this?

Are you using battery type PYL or USE or ?

35 minutes ago, Coulomb said:

? Battery "demand" is in amps or watts. Or do you mean if your battery is discharged to the point of an estimated 45 Ah of capacity, you see this fault code?

Fault code 52 is "bus voltage too low". 59.8 V seems very high for a battery, nearly any battery. What battery is this?

Are you using battery type PYL or USE or ?

My battery is a 15s so max would be 63v. This is my home made battery. My inverter is set to 40amp max battery discharge. My bms is set to 46amp max. So I have a safety between them 2 if one fails 

1 hour ago, Coulomb said:

? Battery "demand" is in amps or watts. Or do you mean if your battery is discharged to the point of an estimated 45 Ah of capacity, you see this fault code?

Fault code 52 is "bus voltage too low". 59.8 V seems very high for a battery, nearly any battery. What battery is this?

Are you using battery type PYL or USE or ?

I am using USE type

Inverter start on battery only?

2 hours ago, Gilberto said:

My battery is a 15s so max would be 63v.

Ah. Usually a ternary lithium battery is 14S for nominally 48 V.

My guess is that at 45 A current draw (around 2.5 kW battery load, a bit over 2 kW house load), your BMS does something to disconnect the battery, and the inverter doesn't like it. Hence the fault code 52 somehow.

Are you sure that that whole wall of cells can't safely exceed 45 A total?

Edit: Or maybe it's the inverter itself, when the current exceeds the discharge current limit. I don't know what the inverter does to ensure that battery current limit. Maybe it's not very smart about how it implements the limit.

Edited November 20, 20223 yr by Coulomb

2 hours ago, mihaigsm2003 said:

Inverter start on battery only?

Yes it does start with battery only 

2 hours ago, Coulomb said:

Ah. Usually a ternary lithium battery is 14S for nominally 48 V.

My guess is that at 45 A current draw (around 2.5 kW battery load, a bit over 2 kW house load), your BMS does something to disconnect the battery, and the inverter doesn't like it. Hence the fault code 52 somehow.

Are you sure that that whole wall of cells can't safely exceed 45 A total?

Edit: Or maybe it's the inverter itself, when the current exceeds the discharge current limit. I don't know what the inverter does to ensure that battery current limit. Maybe it's not very smart about how it implements the limit.

I have found the problem. The bms was at 40ah and inverter at 40ah. But the bms has quick response on cutting the energy and the inverter did not like it. Solution was to put the bms at 45ah so the inverter cuts 1st. But still when I pass the 40ah the inverter goes to utility and does not go to solar and utility. It only goes again to utility, solar and battery when I turn off the appliance that passed the 40ah mark. Any solution to this? When this happened there was about 2kw of solar

write DSP firmware U1 90.10, solve more problems

10 hours ago, mihaigsm2003 said:

write DSP firmware U1 90.10, solve more problems

Ok. Do u have? 

16 hours ago, mihaigsm2003 said:

write DSP firmware U1 90.10, solve more problems

6 hours ago, Gilberto said:

Ok. Do u have? 

I note that main firmware version 90.10 (August 2021) is actually older than main firmware version 90.06 (February 2022). I'm pretty sure that I have verified that 90.10 is missing some changes that are present in 90.06. There is an even more recent 8 kW MAX firmware, but it seems not be be in favour.

So for now, 90.06 and its patched versions are the latest trusted firmwares for Axpert MAX 8 kW, IF you have the '2809 chip. 

4 hours ago, Coulomb said:

I note that main firmware version 90.10 (August 2021) is actually older than main firmware version 90.06 (February 2022). I'm pretty sure that I have verified that 90.10 is missing some changes that are present in 90.06. There is an even more recent 8 kW MAX firmware, but it seems not be be in favour.

So for now, 90.06 and its patched versions are the latest trusted firmwares for Axpert MAX 8 kW, IF you have the '2809 chip. 

Ok thanks. But why does it fail to manage the sources? When it exceeds the mark of instant 40ah at battery, why does it cuts off all battery power and go only to utility power? In my mind I think it must work like this: when it reaches the 40ah battery max it should go get the rest of the power needed from solar and then if solar is not sufficient it should turn to utility, but all this still consuming from the battery and solar at the same time 

36 minutes ago, Gilberto said:

But why does it fail to manage the sources?

I'm guessing it's more bugs in the firmware.

That part of the firmware code (deciding what mode to be in, and how much power to allocate to the various sources) is very hard to follow, at least for me.

1 hour ago, Coulomb said:

I'm guessing it's more bugs in the firmware.

That part of the firmware code (deciding what mode to be in, and how much power to allocate to the various sources) is very hard to follow, at least for me.

Maybe there will be someone that could fix this firmware issue 

Today i received for repair other display for inverter 8kw dead on update, i disassembly and microcontroller is GD32F305

I think, all new inverters display removable and wifi use new MCU GD32, and firmware for ST32F107 not compatible.

BUT, i use SWD with ST-Link V2, i select ST32F105 abd i write firmware , and work good.

Original firmware was 12.21, not work with 12.13, i write 113.16 and work good

Edited November 22, 20223 yr by mihaigsm2003

1 minute ago, mihaigsm2003 said:

Today i received for repair other display for inverter 8kw dead on update, i disassembly and microcontroller is GD32F305

I think, all new inverters display removable and wifi use new MCU GD32, and firmware for ST32F107 not compatible.

BUT, i use SWD with ST-Link V2, i select ST32F105 abd i write firmware , and work good.

Original firmware was 12.21, not work with 12.13, i write 113.16 and work good

Great!