nussfit

🤣
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.

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

Connect via BV to master, open CLI console and write down command: pwr
Then check the text output.
All the info about cells, temps and voltages is available to the master. Only thing that new FW does is that it puts small sample of this info into CAN protocol extension that Victron uses.
So, just update the master and it should work okay with the Victron, despite all the others (or #3) will stay on the old FW.
If you mess something, FW downgrade is possible in Pylontech.
 
 
 
 
 
 

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
 

 

IMHO, that's from intermediate version of the protocol. Also, for example, Seplos batteries are using this too.
Anyway, you're a real CAN expert!
SEPLOS BMS CAN Protocoll V1.0.pdf

I found the problem with the Teensy setup, I had 4 receive mailboxes set as standard and 4 as extended. The 4 as standard were not enough so I added another 4 standard and can now get all the messages.
I can confirm that if you send 0x305 and 0x307 it opens up the 0x372 > onwards. (Tried it on my Teensy instead of the Venus Pi).
I don't know where the 0x70 and 0x371 come from on that chart but I'm sure it's wrong.

Hmm, this is interesting:
0x12 0x34 0x56 0x78 0x56 0x49 0x43 0x00
12345678VIC
 

AFAIK, for US5000 the latest is 1.3.

Puzzling it is, but there's still a pattern going on. If you open all the historical BIN files, you can see this:
firmware line X = US3000 only firmware line Y = US3000C + US2000C + UP5000 firmware line Z = US5000 BTW: Support for UP5000 was included in the US3000C firmware line for years. Contrary, US5000 has it's own firmware line, incompatible with everything else.
So, even if US5000 at FW1.9 needs a heartbeat to stay alive (as we are being told now) this has no effect on US2000C and US3000C. At least, until Pylontech will decide to implement it specifically for these.
 
Makes sense?

Hi guys, I've just uploaded BatteryView 3.0.37 in the Files section:
Use at your own risk. And do not forget to read the instructions first.