canplayer -g gap option seems not working.

[kaizh102]

canplayer -g gap option seems not working.

[kaizh102]

removing the "-g 100" opiton from the command, canplayer follows the timestamp from the log.

[hartkopp]

This might be correct.
Can you post the section of the log file that led to this output?

[kaizh102]

This might be correct. Can you post the section of the log file that led to this output?

here you go:

$ cat candump-2023-11-29_102133.log
(0000052894.459000) can0 0F1##5BD004000170000A000000000A00000000000000A000800000000000000000000
(0000052894.469000) can0 0F1##5F10140005B0100FD01000000A000000000000046010800000000000000000000
(0000052894.479000) can0 0F1##5250240008F02001A02000000A000000000000092020800000000000000000000
(0000052894.489000) can0 0F1##569034000C303004703000000A0000000000000DE030800000000000000000000
(0000052894.499000) can0 0F1##5900440003A0400C904000000A000000000000027040800000000000000000000
(0000052894.509000) can0 0F1##5DC0540007605009405000000A00000000000006B050800000000000000000000
(0000052894.519000) can0 0F1##508064000A206007306000000A0000000000000BF060800000000000000000000
(0000052894.529000) can0 0F1##544074000EE07002E07000000A0000000000000F3070800000000000000000000
(0000052894.539000) can0 0F1##5E70840004D08007208000000A000000000000050080800000000000000000000
(0000052894.549000) can0 0F1##5AB0940000109002F09000000A00000000000001C090800000000000000000000
(0000052894.559000) can0 0F1##57F0A4000D50A00C80A000000A0000000000000C80A0800000000000000000000
(0000052894.569000) can0 0F1##5330B4000990B00950B000000A0000000000000840B0800000000000000000000
(0000052894.579000) can0 0F1##5CA0C4000600C001B0C000000A00000000000007D0C0800000000000000000000
(0000052894.589000) can0 0F1##5860D40002C0D00460D000000A0000000000000310D0800000000000000000000
(0000052894.599000) can0 0F1##5520E4000F80E00A10E000000A0000000000000E50E0800000000000000000000

[kaizh102]

It was recorded via candump, and I slightly aligned the timestamp (the millisecond portion) mannually.

[hartkopp]

Thanks! I can confirm the behavior and will take a closer look at it.
Actually I have to remember myself why I made the gap value configurable o_O
IIRC I was calculating with the expectation that we can roughly send a CAN frame on a CAN bus every millisecond - and then sending all the frames that fit into that slot. But I have to recheck.

[kaizh102]

Thanks! I can confirm the behavior and will take a closer look at it. Actually I have to remember myself why I made the gap value configurable o_O IIRC I was calculating with the expectation that we can roughly send a CAN frame on a CAN bus every millisecond - and then sending all the frames that fit into that slot. But I have to recheck.

thanks! take your time.
Actully the configurable gap could be very helpful - on the vehicle application, the messages are mostly cyclic, with typical period of 10ms, 20ms, 50ms, 100ms, 200ms, 1000ms; 1ms period is pretty rare.