-
Notifications
You must be signed in to change notification settings - Fork 7
Home
Privatecoder edited this page Dec 3, 2025
·
1 revision
2025-11-28 11:24:27 DEBUG:SeplosBMS:Frame has hex only: OK
2025-11-28 11:24:27 DEBUG:SeplosBMS:Frame length mismatch - expected: 98, got: 64
2025-11-28 11:24:27 DEBUG:SeplosBMS:Frame has hex only: OK
2025-11-28 11:24:27 ERROR:SeplosBMS:Pack1:Failed to read telesignalization after 5 retries
and
2025-11-28 11:24:30 DEBUG:SeplosBMS:Pack3:telemetry_command: b'~20034642E00201FD33\r'
2025-11-28 11:24:30 DEBUG:SeplosBMS:Frame includes non-hexadecimal characters: b'03460010960003100C510C3B0C380C340C340C350C3E0C2F0C2F0C340C350C350C2E0C330C380C41060B2'
When running multi-pack-setups, i.e. more than one pack is connected to your reading-RS485-device, you will somewhat be able to read the slaves data but not the master and only with lots of errors like the ones above.
This is, because with your reading-RS485-device and the Master connected to your slaves there are multiple masters on the same bus, which will cause multi-master-collisions.
With multiple packs do not connect your reading-RS485-device to any of the RS485-ports of either the Master or the Slaves. Instead use the described CAN-splitting-method.