davidcole1340 / mcp2515-rs Goto Github PK

I'm trying to react on new data via interrupt. For that I enabled gpio::Interrupt::EdgeLow on the GPIO pin. That is even triggered on new data.

If I send a few packets here and there this works like a charm. I clear the interrupt after I read all messages available (read_message until Err(Error::NoMessage)). In the interrupt handler I simply sent the same message but with a different CAN id. But if data come in all the time (I connected it to my car) this works just for the first 5 or 6 messages and then it stops processing. Am I using the wrong approach?

All taht ona Raspberry Pi Pico, btw, in case that makes a difference.

There is currently no support for 1000kps 20MHz. It is supported in the Original Arduino Repo.

Presently attempting to make it work on my Raspberry pico.

Please comment if there is a reason for excluding 20MHz from this library.

In some application you want to use the delay timer for in main loop or sleep tasks, but the current API takes ownership of it. It is only ever used in reset() that is called from init(), and I think it would be better if init() mutably borrowed the delay timer when required, instead of making it unavailable for other uses. Alternatively it should be available as a public member, or through a delay_ms() call on the driver. But the microsecond delay might then also have to be exposed.

embedded-hal has released v1.0.0 which splits the CAN stuff into its own crate embedded-can. Same traits looks like.

embedded-hal v0.27.0 Frame: https://docs.rs/embedded-hal/0.2.7/embedded_hal/can/trait.Frame.html
embedded-can Frame: https://docs.rs/embedded-can/latest/embedded_can/trait.Frame.html

Are you open to bumping this if it is indeed a clean swap? I'd happily contribute the change and test on my esp-rs setup w/ 2 MCP2515s.