The hardware and tools used in this video are: CANPico board: www.skpang.co.uk/products/canpico-board?variant=39816530886851 Busmaster tool: rbei-etas.github.io/busmaster/ Kvaser Leaf CAN adapter: duckduckgo.com/?q=kvaser+leaf&t=osx The CANHack toolkit: github.com/kentindell/canhack The can2 protocol decoder for PulseView is also available at the above repository. PulseView: www.sigrok.org/wiki/Downloads
@@kentindell Ah got it, 2 payload and CRC One is actual while the other is spiking only at 50% sampling point. Each receiver based on their sample point sees different data and CRC, so both acknowledges it. Wondering how the receiver controller managed phase errors and ReSync Jump Width due to more transitions from recessive to dominant introduced due to spiking.
The hardware and tools used in this video are:
CANPico board: www.skpang.co.uk/products/canpico-board?variant=39816530886851
Busmaster tool: rbei-etas.github.io/busmaster/
Kvaser Leaf CAN adapter: duckduckgo.com/?q=kvaser+leaf&t=osx
The CANHack toolkit: github.com/kentindell/canhack
The can2 protocol decoder for PulseView is also available at the above repository.
PulseView: www.sigrok.org/wiki/Downloads
How did the receiver manage not to give CRC errors?
Because the Janus frame includes two CRCs as well as payloads. If you go to 7m06s you'll see the two bit patterns of each sequence printed out.
@@kentindell Ah got it, 2 payload and CRC
One is actual while the other is spiking only at 50% sampling point.
Each receiver based on their sample point sees different data and CRC, so both acknowledges it.
Wondering how the receiver controller managed phase errors and ReSync Jump Width due to more transitions from recessive to dominant introduced due to spiking.
It exploits CAN sync rules: CAN only syncs on falling edges, only once per bit, and only if the previous bit sampled as a recessive.
@@kentindell Thank you very much for your time and explanation.