Growatt Canbus
#88
-
|
Hey there, I've been trying to connect to a couple seplos v3 batteries using either the pylon canbus or groWatt canbus protocols, I was wondering if you had some better docs/guidance on how to set up the transports? |
Beta Was this translation helpful? Give feedback.
Answered by
HotNoob
May 30, 2025
Replies: 4 comments 23 replies
-
|
The key should be the bridge.
If you look at the example configuration, that should have what you need.
Just instead of a modbus protocol, use the canbus one.
I can go in more details on a later date if needed.
GL.
…On Wed, May 28, 2025, 8:08 p.m. Craig Bailey ***@***.***> wrote:
Hey there, I've been trying to connect to a couple seplos v3 batteries
using either the pylon canbus or groWatt canbus protocols, I was wondering
if you had some better docs/guidance on how to set up the transports?
I am using a pi can hat and am able to read some output using candump can0.
Working backwards with the pylon can doc I've been able to figure out the
pack voltage, but not how to get PPG to read the data and push it to mqtt.
-yNos
—
Reply to this email directly, view it on GitHub
<#88>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQUIMKRVS3RFTE6UE7A3B33AZT25AVCNFSM6AAAAAB6EKIGRCVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGM4DOMBZG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
PPG is now scrolling the can data, which is a move in the right direction, but it's not publishing data to MQTT - It is connecting and setting itself to offline in the correct topic though. Trimmed output: Mqtt: |
Beta Was this translation helpful? Give feedback.
-
|
analyze_protocol should be false. This is for debug only ( nothing will
send in this mode )
And the protocol needs to be set to one of the canbus protocols.
They should be in the documentation. Otherwise I can find it later.
…On Thu, May 29, 2025, 8:05 a.m. Craig Bailey ***@***.***> wrote:
PPG is now scrolling the can data, which is a move in the right direction,
but it's not publishing data to MQTT - It is connecting and setting itself
to offline in the correct topic though.
Config:
`
Transport 2 and 3 are for the Seplos BMS batts over can0 --> mqtt
[transport.2]
transport = canbus
port = can0
protocol_version = v0.14
analyze_protocol = true
write = false
bridge = transport.3
manufacturer = Growatt
model = v3
#optional; leave blank to autofetch serial from device
serial_number =
read_interval = 10
error_interval = 60
Trimmed output:
INFO:.transport_base[transport.2]:Received message: 318, data:
bytearray(b'\r\x15\r\x16\r\x14\r\x14')
INFO:.transport_base[transport.2]:Received message: 311, data:
bytearray(b'\x02@\x07\x08\x07\x08\x00j')
INFO:.transport_base[transport.2]:Received message: 312, data:
bytearray(b'\x00\x00\x00\x00\x01\x00\x00\x10')
INFO:.transport_base[transport.2]:Received message: 313, data:
bytearray(b'\x14\xee\x00\x12\x00\xdd]d')
INFO:.transport_base[transport.2]:Received message: 314, data:
bytearray(b't@}\x00\x00\x03\x00\x0e')
INFO:.transport_base[transport.2]:Received message: 319, data:
bytearray(b'\xc0\r\x16\r\x13\x01\x01\x00')
INFO:.transport_base[transport.2]:Received message: 320, data:
bytearray(b'GT\n\n\x00\x00\x00\x00')
INFO:.transport_base[transport.2]:Received message: 322, data:
bytearray(b'\x00\xdd\x00\xd6\x01\x01]]')
INFO:.transport_base[transport.2]:Received message: 315, data:
bytearray(b'\r\x13\r\x14\r\x14\r\x14')
INFO:.transport_base[transport.2]:Received message: 316, data:
bytearray(b'\r\x14\r\x15\r\x14\r\x15')
INFO:.transport_base[transport.2]:Received message: 317, data:
bytearray(b'\r\x15\r\x14\r\x15\r\x14')
INFO:.transport_base[transport.2]:Received message: 318, data:
bytearray(b'\r\x15\r\x16\r\x14\r\x14')
Traceback (most recent call last):
File "/home/solar/src/PythonProtocolGateway/protocol_gateway.py", line
195, in run
info = transport.read_data()
^^^^^^^^^^^^^^^^^^^^^
File "/home/solar/src/PythonProtocolGateway/classes/transports/canbus.py",
line 239, in read_data
new_info = self.protocolSettings.process_registery(registry,
self.protocolSettings.get_registry_map(Registry_Type.ZERO))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/solar/src/PythonProtocolGateway/classes/protocol_settings.py",
line 311, in get_registry_map
return self.registry_map[registry_type]
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
KeyError: <Registry_Type.ZERO: 0>
[2025-05-29 09:57:45,637] {protocol_gateway.py:209} ERROR -
<Registry_Type.ZERO: 0>
ERROR:invertermodbustomqqt_log:<Registry_Type.ZERO: 0>
INFO:.transport_base[transport.2]:Received message: 311, data:
bytearray(b'\x02@\x07\x08\x07\x08\x00j')
INFO:.transport_base[transport.2]:Received message: 312, data:
bytearray(b'\x00\x00\x00\x00\x01\x00\x00\x10')
INFO:.transport_base[transport.2]:Received message: 313, data:
bytearray(b'\x14\xed\x00\x12\x00\xdd]d')
INFO:.transport_base[transport.2]:Received message: 314, data:
bytearray(b't@}\x00\x00\x03\x00\x0e')
INFO:.transport_base[transport.2]:Received message: 319, data:
bytearray(b'\xc0\r\x16\r\x13\x01\x01\x00')
INFO:.transport_base[transport.2]:Received message: 320, data:
bytearray(b'GT\n\n\x00\x00\x00\x00')
INFO:.transport_base[transport.2]:Received message: 322, data:
bytearray(b'\x00\xdd\x00\xd6\x01\x01]]')
INFO:.transport_base[transport.2]:Received message: 315, data:
bytearray(b'\r\x13\r\x14\r\x14\r\x14')
`
—
Reply to this email directly, view it on GitHub
<#88 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQUIMORUM6YUIIPNJNGYMD3A4HZNAVCNFSM6AAAAAB6EKIGRCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMZRGAZDQNQ>
.
You are receiving this because you commented.Message ID:
<HotNoob/PythonProtocolGateway/repo-discussions/88/comments/13310286@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Oh. Maybe have to look at the protocol folder.
I should make a protocol index in the documentation for sure.
https://github.com/HotNoob/PythonProtocolGateway/blob/86b7e6451da5e5522e4b2fd08ff018efbe807533/documentation/devices/AOLithium.md
https://github.com/HotNoob/PythonProtocolGateway/blob/86b7e6451da5e5522e4b2fd08ff018efbe807533/documentation/usage/configuration_examples/canbus_to_mqtt.md
https://github.com/HotNoob/PythonProtocolGateway/tree/86b7e6451da5e5522e4b2fd08ff018efbe807533/protocols/growatt
Grow watt can protocol is:
growatt_bms_canbus_v1.04
…On Thu, May 29, 2025, 8:59 a.m. Cody ***@***.***> wrote:
analyze_protocol should be false. This is for debug only ( nothing will
send in this mode )
And the protocol needs to be set to one of the canbus protocols.
They should be in the documentation. Otherwise I can find it later.
On Thu, May 29, 2025, 8:05 a.m. Craig Bailey ***@***.***>
wrote:
> PPG is now scrolling the can data, which is a move in the right
> direction, but it's not publishing data to MQTT - It is connecting and
> setting itself to offline in the correct topic though.
> Config:
> `
> Transport 2 and 3 are for the Seplos BMS batts over can0 --> mqtt
>
> [transport.2]
> transport = canbus
> port = can0
> protocol_version = v0.14
> analyze_protocol = true
> write = false
> bridge = transport.3
> manufacturer = Growatt
> model = v3
> #optional; leave blank to autofetch serial from device
> serial_number =
> read_interval = 10
> error_interval = 60
> Trimmed output:
> INFO:.transport_base[transport.2]:Received message: 318, data:
> bytearray(b'\r\x15\r\x16\r\x14\r\x14')
> INFO:.transport_base[transport.2]:Received message: 311, data:
> bytearray(b'\x02@\x07\x08\x07\x08\x00j')
> INFO:.transport_base[transport.2]:Received message: 312, data:
> bytearray(b'\x00\x00\x00\x00\x01\x00\x00\x10')
> INFO:.transport_base[transport.2]:Received message: 313, data:
> bytearray(b'\x14\xee\x00\x12\x00\xdd]d')
> INFO:.transport_base[transport.2]:Received message: 314, data:
> bytearray(b't@}\x00\x00\x03\x00\x0e')
> INFO:.transport_base[transport.2]:Received message: 319, data:
> bytearray(b'\xc0\r\x16\r\x13\x01\x01\x00')
> INFO:.transport_base[transport.2]:Received message: 320, data:
> bytearray(b'GT\n\n\x00\x00\x00\x00')
> INFO:.transport_base[transport.2]:Received message: 322, data:
> bytearray(b'\x00\xdd\x00\xd6\x01\x01]]')
> INFO:.transport_base[transport.2]:Received message: 315, data:
> bytearray(b'\r\x13\r\x14\r\x14\r\x14')
> INFO:.transport_base[transport.2]:Received message: 316, data:
> bytearray(b'\r\x14\r\x15\r\x14\r\x15')
> INFO:.transport_base[transport.2]:Received message: 317, data:
> bytearray(b'\r\x15\r\x14\r\x15\r\x14')
> INFO:.transport_base[transport.2]:Received message: 318, data:
> bytearray(b'\r\x15\r\x16\r\x14\r\x14')
> Traceback (most recent call last):
> File "/home/solar/src/PythonProtocolGateway/protocol_gateway.py", line
> 195, in run
> info = transport.read_data()
> ^^^^^^^^^^^^^^^^^^^^^
> File
> "/home/solar/src/PythonProtocolGateway/classes/transports/canbus.py", line
> 239, in read_data
> new_info = self.protocolSettings.process_registery(registry,
> self.protocolSettings.get_registry_map(Registry_Type.ZERO))
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File
> "/home/solar/src/PythonProtocolGateway/classes/protocol_settings.py", line
> 311, in get_registry_map
> return self.registry_map[registry_type]
> ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
> KeyError: <Registry_Type.ZERO: 0>
> [2025-05-29 09:57:45,637] {protocol_gateway.py:209} ERROR -
> <Registry_Type.ZERO: 0>
> ERROR:invertermodbustomqqt_log:<Registry_Type.ZERO: 0>
> INFO:.transport_base[transport.2]:Received message: 311, data:
> bytearray(b'\x02@\x07\x08\x07\x08\x00j')
> INFO:.transport_base[transport.2]:Received message: 312, data:
> bytearray(b'\x00\x00\x00\x00\x01\x00\x00\x10')
> INFO:.transport_base[transport.2]:Received message: 313, data:
> bytearray(b'\x14\xed\x00\x12\x00\xdd]d')
> INFO:.transport_base[transport.2]:Received message: 314, data:
> bytearray(b't@}\x00\x00\x03\x00\x0e')
> INFO:.transport_base[transport.2]:Received message: 319, data:
> bytearray(b'\xc0\r\x16\r\x13\x01\x01\x00')
> INFO:.transport_base[transport.2]:Received message: 320, data:
> bytearray(b'GT\n\n\x00\x00\x00\x00')
> INFO:.transport_base[transport.2]:Received message: 322, data:
> bytearray(b'\x00\xdd\x00\xd6\x01\x01]]')
> INFO:.transport_base[transport.2]:Received message: 315, data:
> bytearray(b'\r\x13\r\x14\r\x14\r\x14')
> `
>
> —
> Reply to this email directly, view it on GitHub
> <#88 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAQUIMORUM6YUIIPNJNGYMD3A4HZNAVCNFSM6AAAAAB6EKIGRCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMZRGAZDQNQ>
> .
> You are receiving this because you commented.Message ID:
> <HotNoob/PythonProtocolGateway/repo-discussions/88/comments/13310286@
> github.com>
>
|
Beta Was this translation helpful? Give feedback.
22 replies
-
|
ahh were close. just another not so tested area. 7e9175b |
Beta Was this translation helpful? Give feedback.
-
|
It worked again the first push, but fails on subsequent pushes. |
Beta Was this translation helpful? Give feedback.
-
|
ok. i took the time to add a "simulator" so i can test with your can dump. just give me a few more to debug now :) |
Beta Was this translation helpful? Give feedback.
-
|
and that should do it! |
Beta Was this translation helpful? Give feedback.
Answer selected by
yNosGR
-
|
Looks good, thanks bruv! One nit pick. |
Beta Was this translation helpful? Give feedback.
-
|
ffd84ab variable names are based on whatever documentation i can get my hands on. |
Beta Was this translation helpful? Give feedback.
-
|
oh. im not sure how reliable the "bit flags" will be. Protection Flags i might have to continue to test and fix things for that later. |
Beta Was this translation helpful? Give feedback.
-
|
I've pulled the latest, fix looks good :) - let me know if there's any testing you want me to do as things come along. I can also switch it over to pylon_can if you need some testing there. |
Beta Was this translation helpful? Give feedback.
-
|
"do I need to setup a separate transport bridge" |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
44e031a
and that should do it!