May 6, 20242 yr Hi guys. I have an Easun SV IV igrid 5.6kw, I'm testing it but I can't communicate with it either with its app or with watchpower via serial. I wasn't able to use USB because I don't see the virtual port with watchpower. in detail it seems that the connection occurs but then no data is displayed. I can't figure out if it's a fault or I'm doing something wrong. do you have any advice? Thank you
May 8, 20242 yr Greetings. after a couple of days of tinkering I found a partial solution, at least as far as the app is concerned. the problem was the wrong "PN" number... using the wifi ?ssid it worked... I don't know why the number on the label was wrong. the problem of the serial remains (which is the one I need to interface the inverter with home automation (openhab). the problem that arises is that the watchpower software does not detect the inverter... by querying with a terminal (at 2400 8n1 ) the inverter replies "NAKss" and this is normal given that the crc has not been inserted, but the test I needed to see if the 232 was operational... I have no idea of the type of protocol used by this inverter if it is the same as that of a VM III that I already have running (commands with the "Q" qpiri, qmod, etc. Does anyone have any idea what I can do to try something? Thank you Joseph
May 9, 20242 yr My understanding is that EASun IGrid models are Voltronic Infini inverters; these usually have a smattering of ascii commands like QPIRI (I think), but mostly use "secure" commands from the P18 (protocol 18) protocol: I can't recall if the Voltronic communications tool handles these commands. If so, that would be ideal, generating the CRCs for you, and probably a few other things like command length. It can be downloaded from the MPPSolar downloads page.
August 26, 20241 yr 17 hours ago, mihaigsm2003 said: HI, i need firmware for easun sv iv 6kw with 28335_DSP That may or may not be a Voltronic Infini model. I don't know them well, but I do collect some of the firmwares. What are the present firmware versions?
August 26, 20241 yr 4 hours ago, Coulomb said: That may or may not be a Voltronic Infini model. I don't know them well, but I do collect some of the firmwares. What are the present firmware versions? Yes, is voltronic too, but MotherBoard is diferent from 5,6Kw, use SG3525 driver for mosfet's and igbt's. V IV and V II models 5,6kw and 5Kw use individual driver for each chanel Edited August 26, 20241 yr by mihaigsm2003
October 10, 20241 yr Does anyone know what the new version brings in terms of bug fixes? My two inverters (Easun iGrid SV4s) are running 76.01. I am tempted to update to 76.03 provided that there are benefits, given the risk of bricking the inverters. Maybe something like the premature float issue?
October 20, 20241 yr I have read this long thread. My understanding is that here differend DSP on-boad. I have two EASUN_IGrid-SV-IV-5.6KW: Model from year 2022 had 54.02 and 80.25 => DSP 2809 Model from year 2023 had 56.06 and 80.31 => DSP 28066 Question -> can both inverter run the lastest remote firm 80.xx ??? Answer: maybe no..." More information for AXPERT: What Axpert firmware is that? - AEVA Forums Edited October 20, 20241 yr by rolsch
October 20, 20241 yr 1 hour ago, rolsch said: Question -> can both inverters run the latest remote firmware 80.xx ??? Sure, why not? The '2809 and '28066 DSPs execute the exact same instructions; the only difference is that the '2806x DSPs have a calibrate function in mask Read Only Memory at a particular address. The '2809 firmwares don't need this, and must not attempt to call this function, since it won't exist, and the DSP will crash very early in the life of the firmware, before any serial port is set up for updating the firmware. It's true that every now and then, the display firmware can make use of new commands that some older main firmwares don't support. So the display and main firmwares should not be too far apart in date of compilation. The best way to gauge this seems to be the file system date stamp on the hex files.
October 31, 20241 yr Hi, new here first post I have 3 easun sv4 inverters with 3 different FW versions, probablly first and last... 1. production 8/21 with 54.01 / 40.22 2. production 12/22 with 56.06 / 80.31 3. production 9/24 with 56.13 / 80.43 1and2 will not work in parallel, will trow alarms 83, 86, 71 2and3 works, but with 61 alarm now and then... also i would like to get them to same fw, support was ... alarm 86 ... user error... i asked again now that i have 2 working in parallel, hopefully it will click it wasnt basic parameters and they will send me latest FW for earliest unit. i havent opened any of them yet, but i intend to open oldest one for maintinance soon... do you fancy any pictures?
November 1, 20241 yr 18 hours ago, Piscanc said: 3. production 9/24 with 56.13 / 80.43 I don't have 56.13, but I have 56.11, which might be closer than 56.06: This was pieced together from just a hex file, so you might want to wait a while to see if your supplier comes through first.
November 1, 20241 yr 55 minutes ago, Coulomb said: I don't have 56.13, but I have 56.11, which might be closer than 56.06: First thank you for your support in this community, not only on this forum... saved me some issues with communication with taico BMS, they did not know what protocol was used for sv4... from what i could find out... my oldest unit could go from 54.01 to 54.04 without DSP change my second unit would go from 56.06 to 56.11/56.12(posted above) third is on the latest one but to run them all in parallel correctly i need DSP change... next question is if the are stable in 3-phase on different revisions/fw ? currently i am not equiped to run them in 3ph, only with jerry-rigging and no load... ps: supplier (easun power store aliexpress) is relplying... but again reluctant to provide FW without complicating Edited November 1, 20241 yr by Piscanc
November 2, 20241 yr hm... i was sent: 56.12 hex date 18.9.2023 56.14 hex date 13.5.2024 and remote 80.41 with hex date 6.11.2023 witch is newer than 80.42 found online (12.5.2023), but still older by designation than in my latest sv4 Remote Panel - 3573-11G INFINISOLAR V IV 80.41.7z 4165-09S1 FW Upgrade_28066_DSP INFINI V IV 5.6K 56.14.7z
November 2, 20241 yr 4165-07G FW Upgrade_28066_DSP INFINI V IV 5.6K 56.12(2).7z supposedly these are also for older units. I was instructed to upgrade all units to same version regardless x.12 or x.14 Edited November 2, 20241 yr by Piscanc
November 3, 20241 yr well it did not end as i would hoped... i have maneged to update last 2 units, but not the oldest one. oldest unit accepted screen update and than froze during dsp update, with last command connecting. no bloks erased or uploaded. after restart i have BP alarm, it displays battery voltage for a second after boot and than goes to zero. i can still connect to it over watch/solar power and see versoins 54.01 and 80.41 i tried updating over USB cable, but non of my update tools recognize usb, i even tried 128MB microSD card direcly on the inverter and it got stuck at 0% and timed out. i have tried several times even with above posted 54.04 it always starts upgrade menu on iverter, reads the update file and times out. should i be loking into custom cable with a switch to update, or to tap direcly on the board? what is even more bugging me, that i still have intermitent alarm 61 on slave inverter (on 56.14). it doesnt cause outage, but getting used to false alarms leads to ignoring real alarm. could this be related with BMS seqence reporting? this is the only thing coming to my mind... 2x taico 51.2V 200Ah rack mounts solutions as far as i am aware battery BMS sends status by packs in seqence one by one, so i figure some timing must be off and slave gets stuck with wrong information... looking into solar assistent, if i could solve this problem by having it in middle of BMS and inverter... would this be viable solution? Edited November 3, 20241 yr by Piscanc
November 6, 20241 yr On 2024/11/02 at 12:34 AM, Piscanc said: my oldest unit could go from 54.01 to 54.04 without DSP change My apologies if I'm misunderstanding you, but you do realise that you can't change the DSP by firmware upload? The '2809 versus '28066 refers to a Texas Instruments part number, that relates to how the millions of transistors are hard-wired. As for your other issues, I'm sorry I can't help as I have so little experience with the Infini / on-grid models' hardware and firmware. On 2024/11/04 at 6:23 AM, Piscanc said: > what is even more bugging me, that i still have intermittent alarm 61 on slave inverter (on 56.14). Assuming that these models work similarly to the Axpert on-grid models, warning 61 relates to a lack of connection to the battery's BMS via either RS-485 or via CAN bus. This connection is entirely handled by the display ("remote panel") firmware. Edited November 6, 20241 yr by Coulomb
November 10, 20241 yr Quote My apologies if I'm misunderstanding you, but you do realise that you can't change the DSP by firmware upload? The '2809 versus '28066 refers to a Texas Instruments part number, that relates to how the millions of transistors are hard-wired. i am sorry, i was refering to the whole PCB board change, my bad if it was presumed differently. I presume that swaping the board with newer part number whould enable me to flash newer FW, presumed that this is the only HW chage... little xp is more than i have i have uploaded FW on multiple things, even "compiled" my own for 3dprinter, but i still cant firgure out why update times out on U1 but not on U2... regarding alarm 61, it is always on slave unit, regardles of FW version of display on the unit. i didnt downgrade latest unit.
November 10, 20241 yr i forgot to mention this... when i try to update over USB, with micro adapter and stick, it gets stuck at 0% (right after you press yes to update it shows number as proggres) and after a while trows quick U01 error and goes back to main menu.
November 12, 20241 yr On 2024/11/11 at 6:43 AM, Piscanc said: regarding alarm 61, it is always on slave unit, regardless of FW version of display on the unit. i didn't downgrade latest unit. With Axperts (it may be different with Infinis), when you have paralleled inverters, the inverters that are not connected to the battery are supposed to have battery type USE. That would prevent warning code 61 (no communications to battery BMS). You might have to change this setting on the front panel.
December 13, 20241 yr My logic would say that all inverters should be set to same setting (LiB in my case) and inverter firmware should decide where it should get the info from (BMS port of parallel card). these settings lead to intermittent BP alarm on slave unit in my case. As stated in manual, that only master uses LiB and slave unit uses USE. This will cause slave unit receiving wrong state of change information and lead to draining the battery completely triggering BMS alarm witch triggers another alarm on the inverters. inverter then go to alarm 71, maybe BMS alarms are handled incorrectly in the fw. low SOC state alarm from bms should not trigger full alarm in the inverter, just switch to utility and wait for charging conditions (solar or utility time table). to get around this problem i had to set all inverters to USE instead of LiB. when the battery was full enough for alarm to clear i was able to go back to LiB.
December 14, 20241 yr 11 hours ago, Piscanc said: As stated in manual, that only master uses LiB and slave unit uses USE. This will cause slave unit receiving wrong state of change information and... With Axperts, when in parallel or 3-phase output types, the master takes over charging control and tells the slave what to do over the CAN bus that is inside the grey paralleling cables. The master doesn't have to be the one connected to the BMS. In theory, the one that ends up as master should be random. In practice, 99% of the time the same inverter ends up as master. Have you actually tried setting the inverters that are not connected to the BMS to USE battery type? I agree that it's a silly requirement; the ones not connected to the BMS should just ignore the battery type setting. As before, the above is how Axperts work, and I would expect Infinis to work similarly, but I'm not certain.
December 14, 20241 yr admin can delite this post Edited December 14, 20241 yr by Piscanc i forgot to include quote... :)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.