When a CAN frame is ejected from the queue the timestamp is set to 10ms in the future. unfortunately there is no way to store the timestamp correctly.
This may be the root cause of #186, but regardless it should be fixed.
The most sane implementation method is blocked on this upstream issue stm32-rs/fdcan#61.
When a CAN frame is ejected from the queue the timestamp is set to 10ms in the future. unfortunately there is no way to store the timestamp correctly.
This may be the root cause of #186, but regardless it should be fixed.
The most sane implementation method is blocked on this upstream issue stm32-rs/fdcan#61.