The article shows nicely that CAN is the better choice for our application. Using IP you need additional protocol layers for a lot of tasks. This means more complexity, more testing, more computing power and memory. Add this to the higher hardware cost (remember we are talking about embedded software here and not gaming PCs) makes it a clear choice. What the article is not addressing is EMI immunity. My understanding is that CAN is superior in that area as well. Speed is only relevant if your system requires this speed otherwise it is wasted money. Robustness and data integrity is something that at least myself would call a must. Concerning connecting other devices : having a compatible physical and protocol layer doesn‘t mean that you can use it in any practical way within the network out of the box. Don‘t get me wrong - I wouldn‘t use CAN for my home network, but for low cost networked avionics it is a ideal choice. Simply the right tool for the right application...