2una

Ah, fair enough, the Tuya or CBI apps kinda suck with the breakdown of usage over time, agreed. I got them since they work with Home Assistant, which does do a nice graph.
I also have used a Nanoview in the past which I think can do 16 CTs, but that was also feeding into Grafana for graphing which needed some modifications.
 
Good luck!

Yes but i guess cloud charting is the part I'm mostly looking for, at least to start with anyway but that one is maybe on ewelinks supported webview list, the one I brought is not. 

I think that's almost a certain 🤣, solution might be jamming some prozac in that port

🤣
Check the master battery gender. I bet it's a woman and since you've upset her, she does not want to talk to you.

This is a weird problem
Today i monkeyed around some more & decided to try match the PC Date/time format to what the connection time out error messages were saying.
That worked out to be set the PC Time zone +8H China & 24h time format - Regions were already on US.
Then using the Update tool ( the failed firmware tool) left everything blank & unchecked & hit connect.
Viola it linked.
Closed update tool, checked with BV, working there also , unplugged & went back to the 2nd battery & updated its firmware.
Then back to the problem connection batt, connected again with BV & firmware update worked.
Thinking i'd cracked the problem & while the batts were offline returned my linkport leads back to the original way where the problem one was Master.
But after doing that no more talkies again with the problem 1, other 2 still fine.
Maybe I just got lucky but seems pretty odd. 
Anyway now have all 3 batts on v3.4
 

Looks like a good place for me to stay out of 🤪

Jobs done on the master - copying the history & event data after the upgrade is painful slow now tho vrs when I did it earlier. Not sure I even need it but that SOP says to so following orders.

Thanks a bunch for your help Youda 

 

options
login
administrator
pylontech
console window
 
other CLI commands to play with
help
pwr 2
pwrsys
stat
info 2
soh 2
config
....
 
Good luck
 

Seems clean enough

The one not working top & a working one below 
 

Batt 1-2-3 What was module 1-2-3 from top to bottom , when switching the linkports so the no3 or bottom battery is Master that becomes the new module 1, 2 stays the same & 3 is then the top one.

Looks like that. RIP.
 
Great question. Cannot answer this.
Whenever I am doing FW upgrade, I do it one by one, without using parallel.
Message unclear, please clarify.

Hi @2una
I have a couple of very old US3000 too, just like yours - with the RJ11 console port.
A couple of tips:
If the cable works for #2 and #3 it is okay and should work for the master battery too. (Of course, if the console port on the master is not physically or electrically damaged). AFAIK, a direct USB to RJ11 cable was sold for ICC monitor in the past. Maybe that's how you got it. CAN communication does not interfere with the serial console. They both run in parallel without any issue. So, you can leave master battery connected to Venux GX while playing with the console and BV. As far as I can remember mine US3000 worked the best with the BV2.0. Only after I upgraded FW they started to work OK with the BV 3.0.x. For the purposes of connection testing there's no need to check "parallel" and to enter the number of stacked batteries. Just select COM port and press OK. Even if the batteries are physically daisy chained, the BV will connect directly and show the values for the brick it is connected to. Works for master and for other batteries too. 115 200 baud worked for me every time, but the truth is the manual says that the console runs at 1 200 baud. DIP switches are for setting RS485 address of the master battery and for setting RS485 baudrate. They have no influence to the console. Sometimes the console of the BMS got stuck, especially if I tried talking to it via Putty too much, etc. If that's the case, just turn all the batteries OFF/ON in order to restart BMS. Beware of the power surge, caused by the empty capacitors in the inverter. The best would be to switch off the inverter first, but leave DC cables connected to the batteries so the capacitors will not get drained within a minute or two that you will need for that restart. Console does not reply when connected via Putty. It waits silently for a "magic sequence" that BV sends upon connection. Once that sequence is received by the BMS, it starts to accept CLI commands, sending replies etc. In this state you can use CLI that is built in the BV, or kill the BV and switch to Putty (or any other terminal emulator). TL:DR - I would suggest to restart the batteries
 

 

***DISCLAIMER: Use at you own risk. You may brick and/or damage your batteries
How to upgrade firmware of the Pylontech batteries
If it works okay, do not touch it! If it does not work okay, contact your dealer. If your dealer is not helpful, contact Pylontech support. If Pylontech support is not answering, then you can try to upgrade the firmware. Connect laptop PC to the Pylontech battery:
1) First, you'll need to make (or purchase) a serial cable in order to connect a laptop to CONSOLE port of the battery.
Older models of Pylontech batteries are using RJ-11, while newer models are equipped with RJ-45.

Wiring on the right is suitable for all the new models, including US3000C, US5000C, Force H1 and Force H2:

2) A lot of people are struggling with making a working cable, because in some versions of Pylontech user-manual there's a missing information on the GND pin for the RJ-45 console port. Other people are unable to connect since they swapped TX and RX. So, here's the actual pinout of console port for RJ-11 and RJ-45:

3) Grab a Windows laptop PC equipped with a physical DB9 serial port and connect it to the battery stack via the cable above. As an alternative, you can use cheap USB-to-SERIAL converter, for example FTDI-based.
WARNING: Console port is RS232, with positive and negative voltage levels. Therefore, you have to use true RS232 serial-port interface, NOT UART 3.3 or 5V!
4) Download and unpack Pylontech_Tools.zip from the link bellow.
The password for the ZIP file is: Youda
5) Start the BatteryView software:
For batteries with a very old firmware, BatteryView 2 works the best. For new batteries, use BatteryView 3.0.28 or newer. Select the respective COM port and use 115200 baud-rate 6) Now you can perform diagnostic tasks, or update battery's firmware.

Updating Pylontech firmware:
1) When updating firmware, the best is to power-down whole stack, remove all the LINK cables between the batteries and then turning-on just one battery at a time and perform the FW upgrade on it. Then repeat the process for the next battery. Updating batteries while online in a stack works too, but you will get alarms and red lights.
2) There are several models of Pylontech batteries and the firmware is INCOMPATIBLE between most of them:
If you flash a wrong FW in the battery you will brick it. FW numbering is INCONSISTENT between the models. Fox example: For an old battery with certain PCB the FW2.4 might be the most-recent, while for a new battery with a different PCB and chipset the most-recent version would be FW1.9. In other words - higher number does not automatically mean that the firmware is newer, nor better! 3) If possible, it's preferred to update FW via BatteryView 3.0.28 while using following rules:
For updating US2000C, US3000C and US5000 select the whole ZIP file that includes two BIN packages inside and perform update. The BW3.0.28 will be able to pick right BIN file inside the ZIP package automatically. DO NOT select BIN package manually. When updating US2000 and US3000 then you must select the correct BIN file manually, for a shame. 4) Due to the silicon chip shortage Pylontech changed the BMS chip for some of the produced batteries. Therefore, for some models there are two different firmware branches. One for the original chip and the other for the new chip. Luckily, when upgrading FW via the ZIP method desribed above, the BW3.0.28 will choose the correct branch (BIN file) automatically.
 

5) This list indicates firmware version suitable for the each model and what file to flash:

Model: US2000plus
FW: V2.9
FLASH: us2000b_v2.9_Crc.bin
Model: US2000plus95
FW: V3.4
FLASH: us2000B_Plus_V3.4_Crc.bin
Model: US3000
FW: V3.4
FLASH: us3000a_V3.4_Crc.bin
Model: US2000C (original chip)
FW: V2.8
FLASH: NT1.7+2.8.zip
Model: US3000C (original chip)
FW: V2.8
FLASH: NT1.7+2.8.zip
Model: US2000C (new chip)
FW: V1.7
FLASH: NT1.7+2.8.zip
Model: US3000C (new chip)
FW: V1.7
FLASH: NT1.7+2.8.zip
Model: US5000 (original chip)
FW: V1.3
FLASH: US5000 ST+NT 1.3.zip
Model: US5000 (new chip)
FW: V1.3
FLASH: US5000 ST+NT 1.3.zip
 
6) If you have a bricked battery, you can use Pylontech Upgrade Tool V1.0.9 from the Pylontech_Tools.zip to recover it via flashing a correct firmware. The process is as follows:
Connect the debug cable to this software and the battery (attention: at this time please do not switch the battery on), then 1. open the software, click Immediate Update. 2. Click Connect. 3. Click Browse to select the correct firmware. 4. Then click Program and switch on the battery by hard switch and the red soft start button immediately. This will bring the battery back to normal. 7) When updating firmware, it's the best to turn-off all the batteries in the stack and remove all the LINK cables.
Then power-on a single battery and perform FW update on it.
Repeat for the remaining batteries in the stack.
Reconnect all the LINK cables and start the stack as normal.
Although it is possible to perform FW update while the battery is running in the stack, you will get alarms and red lights when you'll do it that way.

8 ) Firmware packages mentioned above are packed in this archive:
Download and unpack the ZIP budle from the link bellow.
The password for the ZIP file is: Youda
 
Youda

Not a lot of help but i've measured my MP II 5000 & that was throwing out 58db whilst loaded up with 6000W using a phone sound meter app(sound meter) 

Correct. The charge voltage is 52V (in 2.60 it will be 52.4V), and when used with MPPTs the MPPTs will be instructed to charge 0.4V higher than this. The Multi feeds in everything above 52V, as you noted.
By enabling it without DC chargers, you're using this same mechanism to deflate it, should it ever go above 52V "by accident".
Also, if you haven't done it, disable SVS (shared voltage sense) in the DVCC menu.
I agree, which is why I wonder is SVS might be on. Turn it off.
The idea with SVS is that the voltage as reported by the battery is synced to the other devices (Multi, solarcharger), and this will then eliminate calibration differences and voltage drop over the cable. The only trouble is that a highly charged Lithium battery can spike up really quickly, and because the BMS often sends voltage info only once every 2 seconds or so, and that is synced with the other devices only every 3 seconds, it doesn't really work all that well with some batteries. The shared value can be stale by up to 5 seconds be the time things are recalibrated...
The only other thing that will cause some wiggling, is if your AC input limit is set to a lower value. Then the Multi will "assist" when your input current goes above the set limit. For example, I have mine set to 20A, so when we go above 4.5kW draw, the Multi assists from the battery, and recharges afterwards.

Yes. In Venus 2.60 it moved to a submenu... and the spelling mistake is fixed (two words in English, solar charger 🙂 ).

Ok i'll load that ESS back on with that setting & see what happens. 
Thanks !!

Hi,using 3 x Pylontech's.
Can program the inverter directly without GX but i think the battery bms needs to have the GX present to route thru. I use a venus with mine.
That also gives you all your monitoring pages to see via Victron VRM so its worth its cost

I have my setup in apartment & don't think that bit of fan noise is a problem, Multiplus II 3kva & later switched to a 5kva.
Neither bugs me
 

I have my setup in apartment & don't think that bit of fan noise is a problem, Multiplus II 3kva & later switched to a 5kva.
Neither bugs me
 

Done - thanks a ton for your help! - If you eat fish pm me your cell no & after this virus nonsense is done i'll try get some to you.(i have in my head your CTown?)

Correct.
Correct. On the ESS menu.

Hi @2una - I have actually checked and for me it works. The BMS activates immediately after power failure and all 3 of my Pylontechs operate through the master. Red alarm led comes on after 3 days again.

The idea of "holding" the SOC is in my opinion a flawed one, because SOC tracking is always an estimation of a chemical process. At the edges we can be fairly accurate, because we know the voltage rises as the cells fill up, but lower down LFP cells has a flat curve and you can easily end up slowly discharging a battery while you think you're holding the SOC constant.
The only solution would be to keep them at a lower voltage, say 51V (3.4V per cell). Usually in a Victron system there is enough back and forth going on that it should not be  problem, but if it is, there's three things I can think of.
1. If you're running "Keep Batteries Charged", you can (in VE.Configure) enable Dynamic current limiting for that AC input. This is actually meant for generators. What it does is when a larger load starts on the output, it uses the Multi to "cushion" the blow, so that the generator gets more of a gradual load increase. By using this you make the batteries do something every now and then.
2. Instead of using "Keep Batteries Charged", put the system into optimised mode, and then enable Scheduled charging. Set a charge schedule that runs evey day from midnight for 23 hours and 55 minutes. The effect would be that every day just before midnight it will discharge the batteries for 5 minutes, also avoiding the "error".
3. Ignore the error...

Interesting response to Pylontech alarm from company rep. in the Victron community forum
https://community.victronenergy.com/answers/50455/view.html
The cause of this alarm message：Our battery has a kind of BMS logic：When the battery is not charged or discharged for 3 days，always in idle state. The battery will automatically shut down and go to sleep mode.Only when the battery is charged or discharged again, by then the battery will automatically activate.
So when there is a battery to sleep mode and shut down, our Master battery will light up red light and send message to the inverter show there is an internal alarm. （You can check the first three days of the alarm record, the battery will be used once.）
 
What I want to highlight fist is that. This is a normal BMS logic of our battery, to reduce unnecessary self discharge consumption loss of the system.it will not affect the normal use of the whole system or cause damage to the system. So don’t worry.
 
This situation usually occurs when the inverter sets the battery to the backup power supply, or UPS mode. The battery is not used as often, and it is usually left unused after being charged to 100%.
The solution：
1.Determine the working mode of on-site situation. If the customer does not want to use the back-up mode, please set the battery has priority over the public-grid to power the load.
 
2. If the customer only wants to use the battery as a backup power source, The customer can limit the inverter to charge the battery only up to 90% not 100%, so that the battery will not enter the standby state.
 
Hope these information will help. Please let me know if you have more questions.

Internal error usually means cell imbalance. Which is weird if it has been kept charged all the time. Only thing I've tried in the past that seemed to have worked was to discharge the batteries a bit and recharge them and see if the error clears.