Hello everyone. I have 2 pieces easun sv4 with 2 different firmwares and i cant paralelize them. I found on a profile forum firmware for it, but after flash i have error 32. Can someone help me with a new firmware or somehow to solve the problem???

 

6 hours ago, add1c7ed55 said:

I found on a profile forum firmware for it, but after flash i have error 32.

* What was the original firmware version, if you know it?

* What version did you flash it with?

These Igrid models are grid interactive, and seem to be less popular than the off-grid models, especially in South Africa. So the chances of finding a compatible firmware update file are slimmer.

I assume that you have restarted the inverter? It's possible that you have firmware for the wrong DSP chip, but in that case (at least with the on-grid Voltronic models), it won't erase the original flash image, so it should restart once you cycle power. You need to cycle power to get out of the bootloader.

I have the same problem. Bought last year 2 EASUN IGRID SV IV and I used them in parallel. This year I've broken(don't ask) one and I bought a third one (newer firmware). Once I connect the new one in parallel with the old one that works it shows me error F86. They work in SINGLE mode with no problem. 

Where can we get a new firmware (or even an old one, but I want to bring them on the same version). If you have one please send it to [email protected]

Thanks!

Hello, I have a similar issue, want to connect in parallel two iGrid SV IV but they see different voltage for the same battery and firmware is different too... I was wondering maybe by upgrading the old one to the newer version might fix this issue, or at least I should try it

6 hours ago, ata2k6 said:

they see different voltage for the same battery

That won't be a firmware issue, it's a calibration value, or some of your sense resistors have drifted in value.

My post on fixing this needs some work, but until then, here it is: https://forums.aeva.asn.au/viewtopic.php?p=71631#p71631

The different firmware for the Axpert MKS IVs (which I think yours probably are) is probably only because of a difference in chipset. I believe that this should not affect paralleling.

Hello, thanks for the suggestion, I'll try that first, once I receive the serial usb adapter cable, which hopefully works. 

Meanwhile I discussed with the seller and they are sending a new mainboard for test.

My two inverters main CPU version in 07601 on the older inverter and 05606 on the new one in the app, on their display shows U176.01 respectively U156.06.

The strange issue is that the old one reads about 0.1V more but not all the time, so I guess actually is less than 0.1V the difference but as it rounds the number up it jumps between the same value or 0.1 higher. Is such a voltage difference enought to throw F83 in parallel mode? The battery cables are the same cross section and lenght and they are connected both pairs in the same point. 

2 hours ago, ata2k6 said:

Is such a voltage difference enough to throw F83 in parallel mode?

No, only 0.1 V difference and even that only some of the time is as good as it gets. One firmware that I looked at seems to have a threshold of 4.0 V (in a 48 V system), and 6.0 V if the other machine is in a different mode (battery versus line mode for example). So it seems to me that only the most gross battery voltage differences should trigger fault code 83, and in fact I suspect that in practice it means that the firmwares disagree about the interpretation of can message formats. So the two machines are comparing completely different things, resulting in what appears to be more than 4.0 V discrepancy in battery voltage readings.

Of course, iGrid models are on-grid models, and I'm only familiar with off-grid firmware, so I might be way off base. I find that I do have Infini V IV firmware version 76.03, which might be close enough; use at your own risk, I don't recall where I found it:

4564-00H7 FW upgrade_28335_DSP INFINI V IV 5.6K 76.03.7z

I also have 56.00, which might match 76.01 better than 56.05 matches 76.03:

INFINIVIV5.6KReflash5600.rar

Oh, thanks a lot, that's a good starting point, I guess in FW the last two numbers are the actual FW version, the first two are versioning / batch number?

I managed to discuss with the seller and they are sending me a spare main board, so I will have a backup. Unfortunately we don't know what version will have, only after installing it.

8 hours ago, ata2k6 said:

I guess in FW the last two numbers are the actual FW version

It seems so. 

8 hours ago, ata2k6 said:

the first two are versioning / batch number?

I have no idea about the 4567-00H7, 28335 very likely refers to the DSP psrr number TMS320F28335, which is a chip with floating point hardware. Even though the floating point hardware isn't uded, the compiler pushes and pops all the floating point registers, making this firmware needlessly incompatible with '2809 firmware. More incompatibility to deal with! In the second file, 5.6K obviously refers to a 5.6kW rating. This firmware runs only that power level, I think that the other one handles 4 power levels, depending on the voltage at a pin at power-on. 

8 hours ago, ata2k6 said:

they are sending me a spare main board, so I will have a backup. Unfortunately we don't know what version will have,

I'm pretty sure that with Infinis, like most higher power Axperts, the DSP which contains the main firmware in its flash memory, is on a control board, which is a daughter board separate to the main board. But perhaps you meant that they are sending you a spare control board? 

3 hours ago, Coulomb said:

It seems so. 

I have no idea about the 4567-00H7, 28335 very likely refers to the DSP psrr number TMS320F28335, which is a chip with floating point hardware. Even though the floating point hardware isn't uded, the compiler pushes and pops all the floating point registers, making this firmware needlessly incompatible with '2809 firmware. More incompatibility to deal with! In the second file, 5.6K obviously refers to a 5.6kW rating. This firmware runs only that power level, I think that the other one handles 4 power levels, depending on the voltage at a pin at power-on. 

I'm pretty sure that with Infinis, like most higher power Axperts, the DSP which contains the main firmware in its flash memory, is on a control board, which is a daughter board separate to the main board. But perhaps you meant that they are sending you a spare control board? 

Well, I need to clarify this, sales person doesn't seems to be a technical person, hopefully they refer to to control board, not to the power electronics board, otherwise we did nothing...

 

I'll need to disassembly one of the inverters probably to send a picture of the control board, otherwise they might send me something else and I will stay without inverters for some more time

 

Edited November 15, 20231 yr by ata2k6

Aaaand the winner is @Coulomb

The upgrade to 76.03 did the trick, the inverters are connected and works in parallel, no more voltage difference on the display.

Thanks man, you saved the whole week, not just the day!

Hi, I have the same problem. I need to upload the software but the links have expired. Can someone send it to me again?

On 2024/02/18 at 10:16 PM, michalch said:

I need to upload the software but the links have expired.

Which firmware? 73.06 is an Axpert Max firmware, and this is an iGrid SV_IV thread. The firmware I see on this page is stored on this forum, so it can't have expired.

Hi

in the Voltronic FTP server section dedicated to EASUN (http://ftps.voltronic.com.tw/E/Easunpower-93CB312922AC474787C6/) there is a "sv iv 5.6k sn96132209100103" directory in which the Infinity firmware v73.06 is listed (but I agree, this is not in line with the version numbering - my own iGrid SV IV, which is 05606)

@ata2k6: do you confirm you successfully updated your EASunpower iGrid SV IV with the infinity v73.06 v73.03 firmware above ?

Matt

Update: version update after right Coulomb's comment.

Edited February 28, 20241 yr by msevestre

1 hour ago, msevestre said:

in the Voltronic FTP server section dedicated to EASUN (http://ftps.voltronic.com.tw/E/Easunpower-93CB312922AC474787C6/) there is a "sv iv 5.6k sn96132209100103" directory in which the Infinity firmware v73.06 is listed

I see version 76.03. Details like this are really important!

The 76.03 firmware is for a vastly different DSP, the  '28335. This one has floating point, and a completely different address range compared to the '2809 and '28066 DSPs, as well as at least twice the flash memory.

The 56.xx firmwares (at least 56.05 that I have) is for (I believe) the '28066 DSP, the same as for many Axperts, although some have the '2809 DSP, some the smaller again '28062 DSP, and some have a different microcontroller altogether.

So these two firmwares are not compatible in any way. AND, as far as I can tell, the reflash tool probably won't save you from bricking  your machine if you try this! The address mismatch should stop the flashing at the wrong address, but I suspect not before the flash memory is erased. Fortunately, IF you have a suitable 56.xx firmware update file, that should rescue the machine, but I can't be sure.

Edited February 28, 20241 yr by Coulomb

Hi

you're right. 76.03 (I updated my initial message to correct my mistake).

Does that mean that iGrid SV IV running 56.xx  firmware should better be (if possible ?) updated with Axperts firmwares and that what's on the voltronics FTP in the "SV IV" directory implies there are different flavors of this machine running DSP 28335 (thus such 76.xx firmwares must not be used for 56.xx firmware-based units (as running on DSP 28066)).

I'd be curious to get @ata2k6 feedback, as his message dated 15th Nov talks about updating with the 76.03 you shared... 🤔

Thanks @Coulomb for your feedback & warning.

Matthieu

9 minutes ago, msevestre said:

Does that mean that iGrid SV IV running 56.xx  firmware should better be (if possible ?) updated with Axperts firmwares

The iGrid models are not Axperts, they are Infinis. Infinis are on-grid models with certification and the ability to export to the grid if settings and grid conditions allow. Axperts have no grid interactive certification, and are so-called "off-grid" models, though most of them do connect the AC-in port to the grid; they are not supposed to export power to the grid.

12 minutes ago, msevestre said:

thus such 76.xx firmwares must not be used for 56.xx firmware-based units

Yes, you can't mix them: only use 76.xx on machines that come with 76.xx, and only use 56.xx with machines that come with 56.xx. Some of these models may have slave DSPs as well, though perhaps these days the display firmware takes over the role of the slave processor. I'm not very familiar with the Infini firmwares.

15 minutes ago, msevestre said:

Thanks @Coulomb for your feedback & warning.

I'm glad it prevented you from bricking or semi-bricking your machine, and it may help others too.

Great. So only possible firmware would be Infinisolar 56.xx firmwares...

 

The only one I've seen is 56.05, which is presumably a step backwards for you.

Edit: Oops, also see 56.00, which is presumably even older.

Edited February 29, 20241 yr by Coulomb

EASUN sent me some firmware for my EASUN INFINI V IV 5.6K as I had the same problem with paralleling 3 of the buggers ie straight to battery voltage fault within a few seconds on power up. The fw update resolved the parallel issue but I am honestly sick of the things. To clarify I have them in an off grid config wth grid backup and pytes lithium batteries but I have issues such as grid spikes every hour of around 500W for 12-15 mins where the mode switches from solar/battery to hybrid for no reason that I can fathom which adds 100GBP to my bill each month(UK) and phantom power surges back to the grid. EASUN have ignored requests for help so my advice is steer clear if you will, as I do, need support. I also have two external fans cooling them constantly as they overheat easily but  I fully expect them to fail by the end of the year.

4165-07G FW Upgrade_28066_DSP INFINI V IV 5.6K 56.12.7z

 

Remote Panel - 3573-11S3 INFINISOLAR V IV 80.41.7z

Edited March 5, 20241 yr by ddmbr

Hi

thanks for this. This looks like a more recent firmware than the one I have. Did you flash both DSP & Remote panel ?

 

On my end, I am still struggling to get feedback from my reseller.

My issue is : the inverter always throws back to grid power which could have been used to charge battery or power loads (and then, less discharging battery). On a normal sunny day, while solar generate 2.5kW, I’m observing a 150 to 200w drain to grid... of pure loss  

Matt

Edited March 5, 20241 yr by msevestre

3 hours ago, msevestre said:

Hi

thanks for this. This looks like a more recent firmware than the one I have. Did you flash both DSP & Remote panel ?

 

On my end, I am still struggling to get feedback from my reseller.

My issue is : the inverter always throws back to grid power which could have been used to charge battery or power loads (and then, less discharging battery). On a normal sunny day, while solar generate 2.5kW, I’m observing a 150 to 200w drain to grid... of pure loss  

Matt

I did both and I don't think the order matters.

What do you use to monitor the system? I use solar assistant and the latest beta version has some decent automation added which forces the state of lots of different parameters during specific times such as output source priority. It runs on a raspberry pi and super easy to setup. I think I would have the same issue as you without it ie it would be more than 15 mins or so of loss per hour as you say. You're probably looking at 100 bucks to get a pi and the software and maybe another 10 or 20 for a console cable to connect to your inverter and batteries.

 

I use solar assistant, with home assistant on the back. This drain is not under control and solely coming from inverter, which behaves abnormaly.

I lost the RS232 cable provided with my inverter - so need to find the working pinout (I found one, but no success for now - at least the WatchPower Windows APP does not talk to the inverter)

Edited March 5, 20241 yr by msevestre

I just dont understand how they can put out critical firmware with so many bugs. According to solar assistant my inverters just sent an 88KW spike back to the grid except grid-tie is disabled. Be aware that if you install the same firmware you might see similar issues.