From ec79c194d274e12b4d14a05e582f5e40f3076aec Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andreas=20Bo=CC=88hm?= Date: Mon, 16 Sep 2024 21:25:26 +0200 Subject: [PATCH] Adjust logging of can message identifiers to support extended frames So far we only worked with non-extended can message identifiers. In the deye can protocol there are also extended frames with extenden identifiers specified. To allow further testing we should log all identifiers in full length. --- src/BatteryCanReceiver.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/BatteryCanReceiver.cpp b/src/BatteryCanReceiver.cpp index ff16fd043..094e1c331 100644 --- a/src/BatteryCanReceiver.cpp +++ b/src/BatteryCanReceiver.cpp @@ -140,7 +140,7 @@ void BatteryCanReceiver::loop() } if (_verboseLogging) { - MessageOutput.printf("[%s] Received CAN message: 0x%04X -", + MessageOutput.printf("[%s] Received CAN message: 0x%X -", _providerName, rx_message.identifier); for (int i = 0; i < rx_message.data_length_code; i++) {