Design Article

Proven 1394 technology trumps Ethernet AVB potential for the vehicle network

1394 Trade Association

7/2/2010 1:39 AM EDT

With the automobile becoming yet another home for a network of interconnected intelligent subsystems, vehicle designers must choose a multimedia network technology. Modern automobiles need a way to move everything from video to safety data around the auto. Ethernet works well in the office and the home, and at first glance it might appear a good fit for vehicles. A detailed investigation, however, reveals that the Ethernet physical layer (PHY) is not a proper match for the automotive environment, and that no high-level protocols exist for multimedia delivered over Ethernet in the automobile. Conversely, 1394 has a more flexible PHY that supports numerous topologies (including preferred daisy-chained connections) and also includes proven protocols for passing real-time multimedia streams.

Let's take a closer look at the requirements of an automotive network. The network must connect a variety of passenger-entertainment and driver-information systems. For example, the network might need to carry video from a central DVD or Blu-ray player to video screens located at each passenger seating location. The same network might need to carry real-time video from a rear-facing camera to a driver display so that the driver can see approaching traffic or move in reverse more safely. The network might also link to storage devices such as Flash memory or hard drives that might store navigation data. With wireless WAN data networks such as WiMax emerging, the network might carry Internet traffic. And of course the network will carry streaming music.

When considering a network for the above scenario, the evaluation should include the types of media a network can use as well as the supported PHY layer performance and topologies. The evaluation should also consider the higher-layer protocols that ensure that devices interoperate seamlessly. For example, a network-connected display must be compatible with a source such as a DVD player. Unlike in the home, the DVD player won't connect directly to the display. Instead, both devices must connect and interoperate via a network. Finally, the evaluation should consider the standards body behind the network, and the roadmap for the future. See figure 1 below for examples of automotive networks.

Figure 1: Automotive network examples

The 1394 standard is promulgated by the 1394 Trade Association (TA). The 1394 Automotive standard includes 1394 technology developed for PC and consumer electronics applications, as well as additional auto-centric technology. For example, 1394 Automotive includes all of the auto-centric standards development originally handled in the IDB Forum, and includes a direct link to AMI-C, ISO, IEC, IEEE, SAE and USCAR standards. Consider a comparison of the 1394 Automotive standard and Ethernet Audio/Video Bridging, AVB (see Table 1).

Table 1: Comparison of the standards

Ethernet AVB is being promulgated by the AVnu Alliance. The alliance will promote A/V transmission using the established Ethernet PHY and Link layers combined with the AVB addition developed in the IEEE 802.1 standards body. Specifically, Ethernet AVB will use the new 802.1Qat Stream Reservation Protocol and 802.1AS Precision Time Protocol to add multimedia capabilities to the Ethernet LAN.

Let's start the detailed comparison with the maximum data rates supported by 1394 and Ethernet. Today, 100-Mbps and 1-Gbps Ethernet ICs designed for IT applications are readily available. In the case of 1394, 400-Mbps (S400) and 800-Mbps (S800) automotive grade ICs are readily available and the technology is broadly deployed in computer products. 800-Mbps 1394 is essentially equal to1-Gbps Ethernet in usable bandwidth due to the fact that Ethernet uses 8b/10b data encoding and incurs what's essentially a 20-percent performance hit in terms of actual data rate. While both Ethernet and 1394 offer plenty of raw bandwidth for automobile multimedia network needs, the evaluation must go beyond data rate to topology considerations and cost.

Topology and weight in the automotive network
It's fair to question why we need an automotive network. Why wouldn't point-to-point connections like the ones most broadly used in consumer A/V systems work perfectly well? Automakers in recent years have used point-to-point connections such as LVDS to carry video. The answer to why a network is better lies in the weight of the cable. Automakers are constantly seeking to reduce vehicle weight to increase both fuel efficiency and performance.

Wiring harnesses contribute significantly to vehicle weight. Lower-speed networks (like CAN), which connect driveline systems such as braking and engine control, came about largely based on the desire to minimize the wiring harness. Now, automakers seek a similar solution for multimedia data. The 1394 Automotive technology has demonstrated that a network can carry the multimedia data that in many cases today still traverses point-to-point connections.

In fact, 1394 offers far more flexibility in topology than does Ethernet, and that advantage translates into simpler, more flexible and lighter-weight wiring harnesses. The 1394 Automotive standard inherently supports star, tree, ring, or daisy-chained topologies. In most automotive cases, the daisy chain choice delivers the desired simplicity in the wiring harness. Table 2 below illustrates some of the basic topology differences.

Table 2 shows the comparison of topologies

Next:




LarryM99

7/8/2010 1:35 PM EDT

The points made about the wire harness are valid. Wire thickness is a concern in automotive designs, and a centralized Ethernet hub architecture would require more wiring than a daisy-chained 1394 one. Unfortunately, they both suffer from susceptibility to EMI. If Intel can get Light Peak going that might be superior to either of these on those counts, though.

Larry M.

Sign in to Reply



j.cordaro

7/10/2010 6:48 PM EDT

The article has several factual inaccuracies about Ethernet. For example, 100BASE-TX and 1000BASE-T use 4B5B encoding, not 8B/10B. Even with the encoding, the wire speed (data rate) for 1000BASE-T is 1000Megabits per second, not 800 Megabits per second. In other words, 8 data bits are transmitted every 8ns with 1000BASE-T. With 1518 byte packets (including 4-byte CRC) and minimum IPG (12-bytes), the maximum raw (non-IP) throughput of 100BASE-TX and 1000BASE-T Ethernet is 98.9% of wire speed.

Jay Cordaro
Gigabit PHY Applications Engineer

Sign in to Reply



EldridgeMount

7/21/2010 12:29 AM EDT

Another fairly significant misconception this article bases much of its argument on is the idea that Ethernet is constrained to a single, inflexible topology. The use of rapid spanning tree protocol (RSTP) permits just about any topology one can dream up.

Coupled with low-port-count and inexpensive switch chips, Ethernet permits the same daisy-chain scheme from device to device, with much lower price points driven by Ethernet volumes, as well as a wide variety of physical media.

Eldridge Mount
VP of Engineering
Lab X Technologies, LLC

Sign in to Reply



Please sign in to post comment

Navigate to related information

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)

Feedback Form