EG4 Community Forum

Does the 6000XP val...
 
Notifications
Clear all

Question Does the 6000XP validate the checksum on Pylon RS485 packets?

4 Posts
1 Users
0 Reactions
15 Views
Posts: 37
Topic starter
(@dannybeardsley)
Trusted Member
Joined: 2 months ago

I've had a really weird situation where it seems the 6000XP started receiving corrupted packets and seemingly wasn't validating their checksum. I've logged every single packet sent from the BMS (using pylon over RS485) and none were sent incorrectly (valid checksums, format stayed the same, ...). However, bytes can go missing over the wire, it happens, that's why the pylontech protocol has a checksum.

It seems the inverter was receiving corrupted packets for charge limits and battery values. This got me wondering, does the 6000XP validate the checksums of Pylontech RS485 packets?

image
3 Replies
Posts: 37
Topic starter
(@dannybeardsley)
Trusted Member
Joined: 2 months ago

Also, a related side-question: Does the 6000XP care about and interpret the cell voltage and cell temp values from the pylontech RS485 protocol? IT parses the packet and receives the whole-battery voltage that's later in the packet, but it seems to not record or interpret the earlier cell-voltage and cell-temp parts of the packet.

Here's the spec from pylon, the later "module voltage" and capacity are being received correctly... but not the cell volts nor temps.

image
Reply
Posts: 37
Topic starter
(@dannybeardsley)
Trusted Member
Joined: 2 months ago

I'm seeing this again... notice that the max charge / discharge amps are always being sent as 90A. It appears like the inverter gets one bad packet (fails to validate checksum) and then the bad data sticks around in the cell volts / temps values. I've been under the impression that the 6000XP doesn't even use the cell volt measures from the RS485 pylon protocol. I'm sending them according to the spec, but it seems to ignore that part of the packet. If it's ignoring them, how did they get filled in?

image
Reply
Posts: 37
Topic starter
(@dannybeardsley)
Trusted Member
Joined: 2 months ago

Strangely enough, the "BMS Event" Column shows 0x6659 which is 26201 in decimal, the same as all those other corrupt fields.

I don't even know what "BMS Event" means, but it seems like some internal inverter state, not some field that's read from the protocol.

Reply
Share: