HubertD
CAN FD Database setup at Cangaroo with unexpected outputs
Bug Description
When a CAN-FD database is associated at setup process, the outcome at the incoming message decomposition is not the expected.
SW & HW used
- OS and version: Windows 11 Pro 22H2
- Cangaroo version 0.2.3
- Vector CANdb++ Version 3.1.25 (SP3) for CAN FD database creation
- CANable compatible device with slcan firmware
To reproduce
-
Create a simple CAN FD database. The message represented in the following image should be decomposed into 14 different elements, with 8 bits each, representing the first 14 bytes of the respective message. STATS message is defined with a DLC of 32 bytes.
-
Setup Cangaroo with the CAN FD database.
-
Wait for a message respecting the format shown at 1. and check the decomposed message values.
Expected behaviour
As noticeable at 3., the decomposed elements do not match the values received at the original message.
| b1 | b2 | b3 | b4 | b5 | b6 | b7 | b8 | b9 | b10 | b11 | b12 | b13 | b14 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Real Outcome | 01 | 03 | 03 | 03 | 03 | 01 | 01 | 01 | 01 | 03 | 03 | 03 | 03 | 01 |
| Expected Outcome | 01 | 03 | 03 | 03 | 03 | 01 | 01 | 01 | 01 | 00 | 00 | 8A | 00 | 00 |
Taking just a quick overview about the issue, it looks like the Cangaroo software is somehow just looking for the first 8 bytes of the received frame and showing them cyclically.
Taking just a quick overview about the issue, it looks like the Cangaroo software is somehow just looking for the first 8 bytes of the received frame and showing them cyclically.
Did you try with different values like a 1 to 14 row to check periodicity?
