Piscanc

Yesterday i got another new unit, parallel card looks ok at first glance... no obvious shorts. Loaded FWs are 56.13 and 80.43 (made in 11/24) still havent heard from support regarding new display FW (80.43), or servicve manual. Regarding BP problem, last time it was mentiond that main board costs 80% of new unit I have both versions installed 1.20sp8 and 1.16sp4, seems like factory password was implemented in 1.20 1.16 only asks for user login, after logging as admin it seaminglly saves setting change but after exiting and re-loading sw, setting remains unchanged (without unit reset).

also is this now a thing, factory password? solarpower V1.20 first asks to login and then for factory pass... V1.16SP4 only asks for login any ideas? it is not wifi pass

i get the trace intended ones...

Currently i run 2 units in parallel, yes with parallel cards. "VGA" style data sharing cables and current sharing cables with original lenght. only one unit is connected to BMS, that unit is master and non co Today i was recording BP problem on oldest unit for easun support, since i got my laptop near i decided to connect it to parallel setup. SolarPower sw recognised parallel setup and showed 2 units, but battary SOC was incoreect most of the time, jumping between 90% and 32% (witch was correct). After switching slave unit to LiB, reading was correct but it was shortly folowed by alarm on slave. This problem is "hard" to solve since it will trigger "pink/ponk" blame finger pointing. I was given info that Taico battery uses paceBMS witch in parallel setup reports info of each unit in sequence one by one. Since only 20% of the time data is given the rest of the time inverter uses data from voltage and USE parameter table, to fill in the gap resulting in different readings. Described bechavior is when master is set to LiB and slave to USE. I belive i have found original problem with paralleling first two units, short between two pins on the card.Picture is 4.99MB... I need to find appropriate time soon to check the rest of prallel cards. as side request, if support fails (witch probbably will ) can anyone direct me to topic/picture where to connect directly on the board to try update with ST-Link, or at least learn bit more first before

yes and 2 days later i got complety empty battery, SOC 0% and inverters went in fault witch caused power outage on that circuit.

admin can delite this post

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.

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.

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.

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?

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

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

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

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?