Hacker News Reader

That's a very useful analysis, thanks!

To add to this, I2C is more common between a controller and 'slaves' which are architecturally simpler, for instance single output sensors often have I2C as their comms interface.

CAN is really meant for distributed embedded systems where you are having to implement full blown communication between equally complex nodes.

CAN is indeed much more robust both at a physical layer with a differential line and at a transfer layer with all sorts of error detection and mitigation mechanisms.

I see, thanks. I'm asking mostly from a model airplane perspective, where you have a receiver, GPS, mag, transmitter, etc. Right now they use UART, with only the mag using I2C, but CAN sounds like a better solution, especially given the amount of electrical noise you get from the motors/servos.

You could go for a realism factor and adopt MIL-STD-1553 or ARINC 429.

No LOL, but that made me giggle.

It doesn't have wide adoption yet, but it's coming! https://uavcan.org/

Oooh, that's very exciting! Worth it just for the standardized connectors, pinouts are such a mess right now, no two of them are the same.

Reply on news.ycombinator.com