Physical-Layer Collision Avoidance in 10Base-T1S Automotive Ethernet

Fig.1, 10Base-T1S PLCA cycle. If there is no data
traffic (top), only BEACONs are seen on the bus. 
Data from a node (bottom) will expand the time
between two BEACONs.

10Base-T1S (IEEE 802.cg) is a variant of Automotive Ethernet  that supports half-duplex and full-duplex communication, allowing either a point-to-point direct connection between two nodes, or use of a multidrop topology with up-to-eight nodes connected on a single 25 m bus segment.

Multidrop cabling of one bus line provides options to extend and scale with fewer physical wires and less weight than point-to-point topologies. With minimum connector space at the ECU, the bus line can be expanded simply by adding sensor units. A bus line with additional sensor units for ultrasonic and short-range radar is an example of how multidrop cabling can be scaled.  

Among the main objectives of the 10Base-T1S PHY layer are reconciliation of transmissions from a variety of mediums, ensuring cooperative behavior by the nodes on a multidrop bus. One way it does this is through the use of Physical-Layer Collision Avoidance (PLCA) technology to minimize dead time and avoid collisions. In this post, we'll describe the workings of PLCA and in a future post, how you can debug PLCA timing issues using an oscilloscope with the 10Base-T1S TDME software.

10Base-T1S Automotive Ethernet vs. 10Base-T1L Industrial Ethernet

Figure 1: 10Base-T1S and 10Base-T1L differ primarily in
reach, encoding methods, topology and applications.

10Base-T1S, a variant of Automotive Ethernet, and 10Base-T1L, also known as Industrial Ethernet, are Single Pair Ethernet (SPE) protocols described in IEEE 802.cg standards. Both offer the same 10 Mb/s communication speed using a single, unshielded twisted pair (T1), but differ in specifics of reach, encoding schemes and topologies, as well as their principal applications.

Automotive Ethernet in the Vehicle

Figure 1 Block diagram of a typical ADAS system
showing the in-vehicle networks used.

As all Automotive Ethernet technologies utilize a single twisted-pair cable (T1) and a point-to-point network topology, they differ primarily in their data rates and encoding methods. For the most part, the data rate determines the applications for which a particular Automotive Ethernet standard can be used. If we take the case of an automatic driver assistance system (ADAS), we can see where each Automotive Ethernet variant might best be used to replace existing automotive protocols. 

(Click on any figure to enlarge the image.)

Fundamentals of Automotive Ethernet

Figure 1: Automotive Ethernet is designed to support
increasingly complex vehicle electronic systems.

When we speak of “Automotive Ethernet”, we’re referring to a group of Ethernet interfaces intended for in-vehicle use, customized to meet the needs of the automotive industry. The first Automotive Ethernet standard was defined by Broadcom in 2011 with BroadR-Reach. Since then, IEEE has released standards for 100Base-T1, 1000Base-T1, 10Base-T1S and most recently MultiGBase-T1. Together, these standards define the general technology known as Automotive Ethernet.

Probably the first question you ask is, “Why not just use standard Ethernet?” A summary of the fundamental features of Automotive Ethernet will show how much better Automotive Ethernet is than standard Ethernet at meeting the industry’s demand for a higher speed, robust, lightweight and lower cost data interface, one that can ultimately replace the many other protocols currently used throughout the vehicle.

Fundamentals of 100Base-T1 Ethernet

100Base-T1 Topology

The term Automotive Ethernet can be used to refer to any Ethernet-based network for in-vehicle electrical systems. It encompasses 100Base-T1, as well as several other variants/speeds of Ethernet (e.g., 10Base-T1, 1000Base-T1). Here, we’ll describe 100 Mb/s Automotive Ethernet as defined by the IEEE in its 802.3bp specification, which is nearly identical to Broadcom’s variant, BroadR-Reach.

Debugging Ethernet, SATA, and PCIe for IoT Devices

Figure 1: A generic IoT block diagram
shows serial-data links in blue

In our ongoing review of debugging serial-data standards for Internet of Things (IoT) devices, let's now turn to three more popular protocols: Ethernet, SATA, and PCIe. Ethernet is found in computer networking applications, while the Serial Advanced Technology Attachment (SATA) connects host bus adapters to mass-storage devices. The Peripheral Component Interconnect Express (PCI Express or PCIe) handles communication between root complexes (motherboards) and expansion-card interfaces.

The Periodic Table of Oscilloscope Tools: Analyze (Part III)

We're nearing the end of our tour of the Periodic Table of Oscilloscope Tools, our way of presenting our broad palette of oscilloscope tools in a concise, clear fashion. In this installment, we'll finish up the Analyze grouping, by far the largest on the Periodic Table.

Why Automotive Ethernet?

Figure 1: The MOST infotainment protocol offers a higher
aggregate bandwidth than Automotive Ethernet, but its 150-Mb/s
bandwidth is shared across the network

In recent posts, we've been reviewing the subject of Automotive Ethernet in general and the BroadR-Reach protocol in particular. In today's installment, let's look at some of the benefits of using the protocol while comparing it to some other protocols that see usage in the automotive environment.

Let's Get Serial: About Manchester Data Encoding

Figure 1: An example of Manchester coding

Founded by the Roman Empire in the first century AD, the city of Manchester, England is probably best associated today with the Manchester United Football Club of neighboring Old Trafford. But in serial-data circles, the city's name evokes Manchester line coding, or phase encoding.