forked from tbnobody/OpenDTU
-
Notifications
You must be signed in to change notification settings - Fork 66
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Feature: parse additional Pylontech CAN protocol fields (#1213)
I noticed that these are missing while looking at dissassembly of the Pytes implementation of the protocol. I also found Pylontech sample CAN messages] which match the Pytes implementation [1]: ``` CAN ID – followed by 2 to 8 bytes of data: 0x351 – 14 02 74 0E 74 0E CC 01 – Battery voltage + current limits ^^^^^ discharge cutoff voltage 46.0V 0x355 – 1A 00 64 00 – State of Health (SOH) / State of Charge (SOC) 0x356 – 4e 13 02 03 04 05 – Voltage / Current / Temp 0x359 – 00 00 00 00 0A 50 4E – Protection & Alarm flags ^^^^^ always 0x50 0x59 in Pytes implementation ^^ module count (matches the blog article image) 0x35C – C0 00 – Battery charge request flags ^^ two possible additional flags (bit 3 and bit 4) 0x35E – 50 59 4C 4F 4E 20 20 20 – Manufacturer name (“PYLON “) ^^^^^^^^^^^^^^ Note: Pytes sends a 5-byte message "PYTES" instead padding with spaces ``` The extra charge request flag is "bit4: SOC low" (Seems to be SoC < 10% threshold for Pytes), I haven't bothered adding that as it provides little value. [1] https://www.setfirelabs.com/green-energy/pylontech-can-reading-can-replication
- Loading branch information
Showing
4 changed files
with
23 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters