# Pylontech: Requests Charging **URL:** \ **Category:** Deutschsprachiger Bereich\ **Tags:** cerbo\_gx\ **Created:** [11 January 2026 21:11 UTC](https://community.victronenergy.com/t/pylontech-requests-charging/51485 "2026-01-11T21:11:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![DirkW](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/dirkw/32/33865_2.png) [@DirkW](https://community.victronenergy.com/u/DirkW)\ **Post date:** [11 January 2026 21:11 UTC](https://community.victronenergy.com/t/pylontech-requests-charging/51485/1 "2026-01-11T21:11:39Z")
Hallo in die Runde, Wird der Parameter “Requests charging” der Pylontech Akkus irgendwie vom Cerbo ausgewertet? Im Cerbo Handbuch oder über Google hab ich nichts brauchbares darüber gefunden ![grafik](https://europe1.discourse-cdn.com/victron/original/3X/3/b/3be16bc7630ae62ebf765a1ef6e6e48d3ce8e848.png) Danke für die Hilfe ---
**Author:** ![MikeD](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/miked/32/1522_2.png) [@MikeD](https://community.victronenergy.com/u/MikeD)\ **Post date:** [12 January 2026 02:29 UTC](https://community.victronenergy.com/t/pylontech-requests-charging/51485/2 "2026-01-12T02:29:13Z")
Unfortunately this is one of the UID’s ignored (so far) by the Cerbo. however, your system should not get into this state, as the Cerbo should start charging on low voltage or low SOC first. ---
**Author:** ![DirkW](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/dirkw/32/33865_2.png) [@DirkW](https://community.victronenergy.com/u/DirkW)\ **Post date:** [12 January 2026 11:42 UTC](https://community.victronenergy.com/t/pylontech-requests-charging/51485/3 "2026-01-12T11:42:40Z")
Thanks for the reply. I was just curious to know what was behind it. Under Details, there are also parameters related to the topic. After a little web search, I finally found the protocol, but with little explanation. > **[Pylontech Battery CAN comms – V1.2 vs V1.3 | Setfire Labs](https://www.setfirelabs.com/energy-monitoring/pylontech-battery-can-comms-v1-2-vs-v1-3)** ---
**Author:** ![MikeD](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/miked/32/1522_2.png) [@MikeD](https://community.victronenergy.com/u/MikeD)\ **Post date:** [12 January 2026 18:28 UTC](https://community.victronenergy.com/t/pylontech-requests-charging/51485/4 "2026-01-12T18:28:01Z")
I have copies of both the Pylontech and Victron protocols, but these are subject to confidentiality agreements. Pylontech have 0x35c = BMS request: Bits 4&5 are labeled as “force charge”, with “Immediately charge the battery system until these 2 flags = 0, Triggered when capacity too low”. So in a normally operating system these flags should NEVER get set, as the Venus o/s will trigger the generator / grid charge well before they are set. As such, there is little point in Venus recognising these, as the action they request has already been taken if possible. ---
**Author:** ![DirkW](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/dirkw/32/33865_2.png) [@DirkW](https://community.victronenergy.com/u/DirkW)\ **Post date:** [12 January 2026 18:37 UTC](https://community.victronenergy.com/t/pylontech-requests-charging/51485/5 "2026-01-12T18:37:39Z")
> [@MikeD](#): > > 0x35c Thank you very much. I was just curious when the Pylontech batteries set the flag and what happens on the Victron side. The link above explains it quite well. It seems to be part of the old Pylontech protocol. We still have six CAN messages, but the ID 0x359 (Protection & Alarms) and 0x35C (charge/discharge requests) have gone, replaced by IDs 0x35A and 0x35F. Additionally, 0x355 has changed from 4 bytes to six. A bit of an explanation is on this table I found, produced by Open Solar Energy: [![CAN communication IDs and descriptions for Pylontech, SMA and Victron.](https://europe1.discourse-cdn.com/victron/original/3X/2/e/2e22a91c9f50431ec0c5404d4f9f04a123dbfff8.png)](https://www.setfirelabs.com/wp-content/uploads/2025/05/CAN_ids.png) As you can see, 0x359 and 0x35C were unique to Pylon – not used by SMA and Victron. This would be a good reason to drop them – to bring things in line with other manufacturer’s protocols. 0x35A and 0x35F are both used by SMA and Victron.