It's not weight they are optimising for
It's cost, that's of course heavily correlated to weight as the heavy stuff of a cable is also the expensive stuff.
The march of Ethernet into motor vehicles continues, with the IEEE launching the first automotive standard for 100 Mbps Ethernet over single twisted pair cables. IEEE 802.3bw, aka 100BASE-T1, is designed to give the auto sector a single homogeneous network architecture, the IEEE says. The main game for auto applications is to …
Actually it is probably both, if well implemented, this will allow cars to save weight and cost by having a single power line to each part of the car, think how many wires are required to power the rear lights, with each having its own wire running from front to back. That is a lot of copper. With the ethernet, each light cluster could have a single data line running to it and tap power of the main conduit then decide which lights should be on.
This post has been deleted by its author
I would think that a standard for a car would actually include some kind of shared-bus, similar to token ring or similar. Would that not be more practical in terms of weight? Rather than 50 cables all trying to come back to one point, you could just tap into the nearest cable for it and piggyback from it.
I can't believe that a car is going to want to have a full, uncontended 100Mbps to every single sensor or whatever it's wired to, so surely a shared bus or ring architecture is a much better idea in terms of wiring than a star kind of topology? Even if you made it a 1Gigabit shared bus, with proper QoS for those devices that need to take up more urgent data?
Do we need another standard, is there an issue with using the current 'almost CAT6' 28 & 30 AWG cables that are available?
e.g.
Telegärtner:
http://www.telegaertner.co.uk/telegaertner-uk-news/press-releases/30AWG-Reduced-Diameter-Cat-6-patch-leads_165.htm
Panduit:
http://www.panduit.com/en/landing-pages/small-diameter-patch-cords
(I use both of these in various fixed and mobile applications, they're both LSZH, so what's not to like?)
This post has been deleted by its author
There are functions that will need this kind of bandwidth, but not that many.
It will become more prevalent with autonomous vehicles, with potentially high bandwidth sensors.
Question is does it offer more than say CAN-FD or Flexray if there is this need?
One of the main advantages of CAN is that a large portion of the bus management is done in HW. When operating on lowest cost Microcontrollers this can make a big difference!
Especially when they can be running between 80-90% CPU load when operating, adding extra communications processing is going to be greater cost add.
Ethernet hasn't had collisions since we started using switches, so that is not much of an issue any more. Temporary block in the switch though because some other packet is currently being sent out a given port is still an issue though. And there are Ethernet extension standards to deal with bandwidth reservation and such for those cases where that matters.