What is the correct response over CANBUS when using the Native 2 protocol? I manage to decode the data from batrium fine but It says timeout so I’m assuming it’s expecting a response of some kind but the protocol PDF doesn’t mention it. i.e. for Pylontech it wants an arrray of 0 on 773 I think.
Hi tweekzilla,
While we are not expecting a response in order to function, I can share the format we expect it to be in.
All payload IDs are referenced to the Base Address set in the integration page.
Summary
| offset | function |
|---|---|
| 8 | Charge Status Actual |
| 9 | Charge Status Flags |
| 10 | Discharge Status Actual |
| 11 | Discharge Status Flags |
Payloads
Charge Status Flags
| offset (bytes) | data type | name |
|---|---|---|
| 0 | u32 | Flags 1 |
| 4 | u32 | Flags 2 |
Not sure what these do, I will have to ask our software engineer
Charge Status Actual
| offset (bytes) | data type | name |
|---|---|---|
| 0 | u16 | Actual Volts |
| 2 | u16 | Actual Amps |
| 4 | u16 | Actual Power |
| 6 | u8 | Actual Celcius |
Discharge Status Actual
| offset (bytes) | data type | name |
|---|---|---|
| 0 | u16 | Actual Volts |
| 2 | u16 | Actual Amps |
| 4 | u16 | Actual Power |
| 6 | u8 | Actual Celcius |
Discharge Status Flags
| offset (bytes) | data type | name |
|---|---|---|
| 0 | u32 | Flags 1 |
| 4 | u32 | Flags 2 |
Not sure what these do, I will have to ask our software engineer