nibbler79

thank you so much for all the support

Good news to this topic… Effekta did, as instructed by pylontech support. Did a warranty repair. Root Cause: Current Sensor broken on the board…. So fuses were intact. A classical DOA Device, slipped QA somehow….

Just wanted to update about the case - pylontech has quite quickly instructed effekta to arrange a pickup for the battery. Battery is arriving today or tomorrow. I did not receive any instructions or firmware I can share.

will keep you posted. Lets see if they supply me with 3.0

did change the firmware to 2.9 including a eeprom reset - but same situation as before. I am reaching out to pylontech support now.

i think i did not clear eeprom. should i give that a try?

thank you for the long feedback. so my socic measuring 0 is not of concern? i also tried to turn on cfet as well as dfet via the debug console. obe works the other does not. I am not measuring any voltage as well with the downgraded version. Next I would try the v2.9 then, and also try the reset. you mentioned different batteryview versions earlier, which should I use and can it be downloaded here? what has to be done to do the reset in batteryview properly?

Ok, sorry. Lets start over, I'll try to be as precise as possible. - I know I confused you with the wrong version information on the second thread. I am running the Victron Setup since 07/2023 with the 2 "old" US3000C. So one Victron Multiplus II with Cerbo GX and Lynx Distribution. The two Batteries connected with one uplink kit cable set to the lynx. Batteries paralelled with the shorty cables and connecting positve uplink from the lynx on one US3000C and negative uplink on the other US3000C. The setup was running since that day and night without any issues or errors. The Usecase is single phase ESS and critical load UPS for the IT Equipment and Fridge. There is no DC Charging from PV on the setup - I have 5 microinverters from Hoymiles that are AC coupled to the grid. (4xhm1500 on the roof, and 1xhm800 on the balcony) End of October I ordered 2 US3000C at a german reseller for Extending Capacity. I ordered one additional Uplink Kit as well, since I wanted to hook it up like the other one paralelled to lynx. I received goods about two weeks later. When unwrapping the two US3000Cs I switched them on and started BMS to see if they come up properly. One did (green led blinking, SOC about 50%), the other one did not show any Leds first, and after cycling again went into "ALM LED on" state. None of my others ever did that, so reading the manual I came to the conclusion that LED on, no beep means undervoltage. Manual states to charge until LED goes off. So I measured with a Voltmeter, and did not see any voltage at all. Hooking them up to the other block without Can Connection to Balance it, or trying to charge with Bench Power Supply at 53 Volts / Limit 200mA did not Change the condition. The US3000C was not accepting any charge. At that point I was contacting the reseller, asking for replacement. I was asked to send the device to effekta directly, shipping on me. I was also warned that in addition to shipping the cost for checking at effekta will also be in my charge if they conclude this is no warranty issue. No other instructions where given at all. Asking for effekta contact, I did not receive anything. Checking shipping cost for dangerous goods I figured that the total cost to get this fixed might be quite high - leading to further investigation on my own. So next I was getting a proper USB/RS232 Adapter and hooked up the terminal. I used the console to check for errors. - but appart from the syserror I did not see any problem with cell voltage or temperature. I also took some console logs. (the ones I used to copy/paste the wrong version number from later - SORRY!) Next I was looking for instructions from Effekta. I found the firmware pack (labeled as latest) on the effekta homepage, and figured a fw upgrade might resolve the issues I am seeing. Unfortunately I missinterpreted the version number as newer and downgraded the US3000C to v2.8 without any change to the behaviour - LED ON, no Voltage on the Pack. Situation was worse now - having a older version on the device, not having fixed the issue. To make use of the new working US3000C I hooked this one up to the stack to balance, and took it into production after that. Now working without problem since a day (~ 1 cycle, balance of the 3 packs is quite good already) - Still the CAN Master being one of the old ones because of CAN Cable length being too short to reach the new one at the bottom in the rack. Later that day I found your forum, and read about batteryview. Thinking about additional insights and not beeing in possession of a working copy of batteryview I registered here, and after getting my account enabled used batteryview to produce the screenshots used in the post. I created the post already showing downgraded v2.8 but did not mention the downgrade unfortunately. In parallel I found the other post talking about Firmware from June. Thats why I asked if anyone has a recent firmware, at best the one I already have on the new properly running US3000C or even a newer one if existing, planing to upgrade all to that, if anyone can share it. I forgot to mention that I meanwhile downgraded the module to v2.8 here as well. This led to all the confusion I produced Meanwhile I am quite out of ideas what I still can try to recover the not working US3000C - so if there is anything I would be glad to get a hint. So status quo is: 4 US3000C, 3 in proper production, 1 in the ALM state being separated from the stack and sitting on my electronics workbench. (Still closed since I dont want to void warranty) Versions are: Older ones: Production: 20221027 Board: NF4.E2 Board Version: V10R04 Main Soft Version B69.13.1.0 Soft Version 1.7 Boot version 1.0 Comm version 2.0 Release Date:220825 newer working one: Production: 20240812 Board: not showing Board Version: V10R04 Main Soft Version B68.8.0.0 Soft Version 3.0 Boot version 2.1 Comm version 2.0 Release Date:240725 newer errorneous one: Production: 20240812 Board: not showing Board Version: V10R04 Main Soft Version B68.5.0.0 Soft Version 2.8 Boot version 2.1 Comm version 2.0 Release Date: 220902 Using MultiSIBControl I figured that it gives pylon_debug access, so I had a look at some command outputs. I am curious if this is the problem - it seems that the Pack Voltage according to bmic is 49218 while socic is showing 0 volts. See outputs collected below. pylon_debug>data @ ----------------------------------------------- Item Index : 3 Time : 24-11-17 23:05:43 Voltage : 49218 mV Current : 0 mA Temperature : 23100 mC Percent : 39 % Total Coulomb : 74000 mAH Max Voltage : 54000 mV Base State : SysError Volt. State : Normal Curr. State : Normal Tempr. State : Normal Coul. Status : Normal Power Events : 0x10000000 SYSERR Bat Events : 0x0 Bat Protect ENA : BOV BHV BLV BUV BSLP CBOT CBHT CBLT CBUT DBOT DBHT DBLT DBUT Pwr Protect ENA : POV PHV PLV PUV PSLP POT PHT COC2 COC COCA DOCA DOC DOC2 SC LCOUL System Fault : 0x1000 ----------------------------------------------- Battery Volt Curr Tempr Base State Volt. State Curr. State Temp. State Coulomb 0 3281 0 21000 Idle Normal Normal Normal 39% 1 3281 0 21000 Idle Normal Normal Normal 39% 2 3281 0 21000 Idle Normal Normal Normal 39% 3 3281 0 21000 Idle Normal Normal Normal 39% 4 3281 0 21000 Idle Normal Normal Normal 39% 5 3281 0 21000 Idle Normal Normal Normal 39% 6 3281 0 21000 Idle Normal Normal Normal 39% 7 3281 0 21000 Idle Normal Normal Normal 39% 8 3281 0 21000 Idle Normal Normal Normal 39% 9 3281 0 21000 Idle Normal Normal Normal 39% 10 3282 0 21000 Idle Normal Normal Normal 39% 11 3282 0 21000 Idle Normal Normal Normal 39% 12 3282 0 21000 Idle Normal Normal Normal 39% 13 3281 0 21000 Idle Normal Normal Normal 39% 14 3281 0 21000 Idle Normal Normal Normal 39% Command completed successfully $$ Remote command: Command completed successfully $$ pylon_debug>socd @ BQ34z100 Data ------------------------------ Pack Volt : 100 mv Pack Current : 400 mA state of charge : 100 % Remain Capacity : 400 mAH ------------------------------ Command completed successfully $$ pylon_debug>tsoc @ Bq34z100 work abnormal, reset Test result:fail Command completed successfully $$ pylon_debug>soct @ Chemistry id: 0 Bq34z100 Ra Table +-----+--------+--------+ |Pos |R_a0 |R_a0x | +-----+--------+--------+ |flag |0 |0 | +-----+--------+--------+ |0 |0 |0 | +-----+--------+--------+ |1 |0 |0 | +-----+--------+--------+ |2 |0 |0 | +-----+--------+--------+ |3 |0 |0 | +-----+--------+--------+ |4 |0 |0 | +-----+--------+--------+ |5 |0 |0 | +-----+--------+--------+ |6 |0 |0 | +-----+--------+--------+ |7 |0 |0 | +-----+--------+--------+ |8 |0 |0 | +-----+--------+--------+ |9 |0 |0 | +-----+--------+--------+ |10 |0 |0 | +-----+--------+--------+ |11 |0 |0 | +-----+--------+--------+ |12 |0 |0 | +-----+--------+--------+ |13 |0 |0 | +-----+--------+--------+ |14 |0 |0 | +-----+--------+--------+ Command completed successfully $$ pylon_debug>tpv @ socic volt: 0 bmic volt: 49197 Bq34z100 Total volt error > 30 mV, calibrate it Test result:fail Command completed successfully $$

Sorry for confusing you. Newer 2 are on different firmware since I downgraded one of them thinking the pack from effekta is newer: Production: 20240812 Board: not showing Board Version: V10R04 Main Soft Version B68.8.0.0 / B68.5.0.0 Soft Version 3.0 / 2.8 Boot version 2.1 Comm version 2.0 Release Date:240725/220902

I did the firmware change. I misinterpreted that it is newer, while it actually is older than what was on there initialy. The retailer I bought from was telling me to return it to effekta on my cost. I was also warned that I would have to pay for troubleshooting if I return it without a need. I wanted to be sure it is not revivable without sending it through the land once more, and didnt want to risk 400 bucks which is half of the devices price. If they would have offered to take it back right away I would not have bothered to tinker with it. Might habe brought me into a situation now that is leaving me with an expensive paperweight.

at the moment i am running the stack with 3 (2 old / 1 new) one of the old is master and its working properly without errors. the 4th though cannot be added. its not getting into a state of running even as standalone and there is no voltage output at all. meanwhile i was playing a bit with the pylon debug console and found: pylon_debug>tpv socic volt: 0 bmic volt: 49214 Bq34z100 Total volt error > 30 mV, calibrate it Test result:fail I fear there is some hw issue.

the effekta download included a flasher that autoselects the right file according to the documentation of the flasher. (using the zipped file) the serial starts with Y240812C1001

which part shows the chip version?

sorry again, i just realize the console logs i pulled and where i took the version information from are older than the screenshots i made. in total i got 4 us3000c. the one on the screenshot is the problematic one. i pulled the latest firmware from effekta (the distributor) and flashed that one, to see if a firmware update resets the situation. it did not, problem persists. so one of the new blocks is on v2.8 at the moment and not 3.0 anymore. anyhow - which version would ve recommended for the board i have? I would flash all 4 to the same, if you can supply the firmware link.

yes a cerbo gx.

Oh, sorry. I understand the point. The new ones are both from 20240812 and the older ones both from 20221027 I put this in the other post as well. If there are any more things I can pull from the console or any other details I can share let me know. I did not know what is needed. Thank you so far for your patience with me, and for your answers

The question is less about the setup than the strange pylontech behaviour of a brand new us3000c - never connected or charged. Box might be DOA - but the retailer wants me to send it back to the german distribution to get it checked. and I wanted to know upfront if it is clearly a warranty case. My setup is 2x2 US3000C connected to a victron multiplus II via single phase for UPS Backup Power and ESS Usage. The US3000C are connected via victron lynx as paralleled pairs. Thing is the described US3000C was not even hooked up, and was in state ALM Led on, so I tried to charge it, but no current bigger than 30mA flows. Thats why I hooked up batterview, and it seems that the pack does have 40% SOC and the failure is not due to undervoltage. Do you know what errorcode 4096 stands for?

I have B68.8.0.0 on my newer US3000Cs, anyone having the files, and could share them? I would like to update the older ones as well. edit: to be more precise on the production date and software + board of the 4 pylontechs: Older 2: Production: 20221027 Board: NF4.E2 Board Version: V10R04 Main Soft Version B69.13.1.0 Soft Version 1.7 Boot version 1.0 Comm version 2.0 Release Date:220825 Newer 2: Production: 20240812 Board: not showing Board Version: V10R04 Main Soft Version B68.8.0.0 Soft Version 3.0 Boot version 2.1 Comm version 2.0 Release Date:240725 Since version numbering is not as consistant as one would expect. What is the latest recommended version to run on all 4? sorry for the lack of information on my earlier question

Hi, I am new to the Forum, and subscribbed to ask for your valued help on the following issue I am facing. I bought 2 US3000C to extend my single phase victron ess (multiplus II) setup, one of the modules works properly, the other is detected as blocking charge/discharge because of System Internal Error. Using BatteryView I could fetch the details from the module and there is no evidence of any over/under voltage or temperature issue that would block charging. The Basic State is SysError, and the System Error Reads 4096. Is there anything else to check / or I can do apart from returning it?