EG4 Community Forum

6000XP Charging eve...
 
Notifications
Clear all

6000XP Charging even though it's forbidden

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

I'm writing my own BMS that communicates the the Pylon protocol.

It's been a bit tricky, but now I'm worried that the inverter won't listen to the BMS about its charge preferences. The amps are communicated correctly, but the "Charge disabled" and "Charge enabled" are not being followed. i.e. we see "forbidden", yet it's still charging. 

Is this expected?

image

 

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

I've been following a protocol spec from Pylontech (RS485 pylon version 3.2). Is this the spec that the 6000XP implements for Lithium Type: 2 ? OR is there a different spec?
https://github.com/Frankkkkk/python-pylontech/blob/master/RS485-protocol-pylon-low-voltage-V3.3-20180821.pdf

The inverter claims to implement this spec (in its packets)

But I've seen several problems:

1. 6000XP doesn't seem to accept the "extended capacity" fields in the battery info packet (CID2 = 0x42)

image
image

2. 6000XP Does seem to accept the charging enabled / disable states (when sending false, charging stops and battery icon turns red), but it always says "BMS Charge: Forbidden" no matter what is sent (as in the screenshot in the above post).

   2.a When clicking the "Forbidden" on the website, we see "The internal fault code of the device is 0"

image

3. 6000XP Doesn't seem to receive cell temps, cell volts, nor cycle counts. However, it's receiving the battery volts which is later in the same response packet

image

 

Reply
Share: