Hello everyone,
I observe a behavior that all CAN TX messages appears twice in the generated trace and I have no explanation for that why this happens. I don't see that this behavior with candump.
I wrote a little bash script that sends every second the same CAN message. The message appears every second in the candump log and in the tshark log I see the CAN message twice in the same seconds with couple of microseconds delay.
candump log:
(2023-12-29 02:17:54.250846) can0 TX - - 123 [4] DE AD BE EF
(2023-12-29 02:17:55.253027) can0 TX - - 123 [4] DE AD BE EF
(2023-12-29 02:17:56.255209) can0 TX - - 123 [4] DE AD BE EF
(2023-12-29 02:17:57.258906) can0 TX - - 123 [4] DE AD BE EF
tsharklog:
1 2023-12-29 02:17:54.250507696 ? CAN 32 ID: 291 (0x123), Length: 4
2 2023-12-29 02:17:54.250846188 ? CAN 32 ID: 291 (0x123), Length: 4
3 2023-12-29 02:17:55.252689942 ? CAN 32 ID: 291 (0x123), Length: 4
4 2023-12-29 02:17:55.253027513 ? CAN 32 ID: 291 (0x123), Length: 4
5 2023-12-29 02:17:56.254869874 ? CAN 32 ID: 291 (0x123), Length: 4
6 2023-12-29 02:17:56.255209782 ? CAN 32 ID: 291 (0x123), Length: 4
I looked through the different man pages of dumpcap and tshark but I don't found any option to get the same behavior as with candump. Maybe I oversaw something.
Does anybody have an idea or run into the same problem and knows how to fix that? Every help is very appreciate.
Best Regards
Florian