2 ms·
> I think the author is pointing at that concept, with the idea that CAN hasn't evolved over time in the same way as HTTP. If he works in this space, I would t
by throw0101a 6y ago
> I think the author is pointing at that concept, with the idea that CAN hasn't evolved over time in the same way as HTTP.
If he works in this space, I would think he'd know that there are new things being worked on:
* https://en.wikipedia.org/wiki/CAN_FD https://en.wikipedia.org/wiki/CAN_FD
* https://en.wikipedia.org/wiki/FlexRay https://en.wikipedia.org/wiki/FlexRay
Not that these seem to work differently at the OSI Layer 1/2 layer, so while older messages can be sent over the newer transport, it is not wire compatible.
- derefr 6y agoRight, you'd likely have to connect your old CAN-bus reader to the new system through an active PHY-to-PHY adapter dongle, sort of like a VGA-to-HDMI adapter, or (presumably, once it happens) a MIDI1.0 to MIDI2.0 adapter. As long as the new version of the protocol is still formatted on the higher OSI layers in terms of reusing the core messages from the old version, and then adding new messages that are optional to the understanding of what's going on from a CAN1.0 perspective, then a change in the PHY layer still isn't really throwing the baby out with the bath-water.