10Base-T1S: A Quick Start Guide

1. Introduction: Why Does the Automotive World Need a "Different" Type of Ethernet?

1.1 Current Challenges in Automotive Networking

In today’s vehicles, the network architecture is like a technical “United Nations”. Multiple communication technologies coexist, each serving a specific role. For example, we have CAN FD for body control, FlexRay for high-reliability control systems, and point-to-point automotive Ethernet (such as 100BASE-T1 or 1000BASE-T1) for high-bandwidth infotainment and Advanced Driver Assistance Systems (ADAS).

This heterogeneous architecture poses a significant challenge: different technologies cannot communicate directly. To make them work together, engineers must design complex and expensive Gateways. Gateways act as translators, converting data between different network protocols. However, the hardware and software for these gateways are not only costly but often become a root cause of potential quality issues during vehicle production.

1.2 The Vision of the "All-Ethernet" Car

To address these challenges, the industry has proposed a compelling vision: building a homogeneous network architecture entirely composed of automotive Ethernet—the “All-Ethernet” car.

The core advantage of this vision is simplicity. If the entire vehicle uses Ethernet, we can fully leverage mature addressing methods such as MAC and IP addresses. Data can be automatically routed and forwarded throughout the vehicle network based on these addresses, much like in home or office networks. Consequently, complex and expensive dedicated gateways can be greatly simplified or even completely replaced, thereby improving reliability and reducing costs.

1.3 Limitations of Traditional Ethernet and the Birth of 10Base-T1S

Why can’t we simply replace bus networks like CAN or FlexRay with existing automotive Ethernet? The answer goes far beyond just cost. Traditional office Ethernet (such as 100BASE-TX) is unsuitable for automotive environments for several fundamental reasons:

Wiring and Cost: Traditional Ethernet typically uses a four-wire or eight-wire system, whereas automotive buses (like CAN) generally use a single twisted pair. Fewer cables mean lower costs and lighter weight. Additionally, point-to-point or switched Ethernet topologies require more transceivers (PHYs), further increasing hardware costs.
Electromagnetic Compatibility (EMC): The electromagnetic environment in a vehicle is extremely harsh, and its EMC requirements are far higher than those for consumer electronics. Standard Ethernet cannot meet these demands.
Power Modes: Vehicles have extreme power consumption requirements when the engine is off to prevent battery drain. Standard Ethernet lacks such ultra-low-power sleep modes.
Wake-up Time: Automotive ECUs must be able to fully wake up from sleep and be operational within 100 milliseconds—a target unreachable for standard Ethernet.

It was specifically to solve these challenges that 10BASE-T1S was born. It is an Ethernet technology designed for automotive applications that supports bus (or multi-drop) topologies, aiming to achieve the simplicity and efficiency of traditional bus networks using the language of Ethernet.

With the background of 10BASE-T1S clearly defined, let’s delve into the specific technical features of this technology.

2.What is 10Base-T1S? 什么是 10Base-T1S？

Core Features at a Glance The following table summarizes the key technical parameters of 10Base-T1S:

Feature	Description
Technology Name	10BASE-T1S
Data Rate	10 Mb/s
Network Topology	Multi-drop or Bus
Physical Medium	Single Twisted Pair (UTP), similar to cables used by CAN FD or FlexRay.
Nodes & Length	Supports at least 8 nodes; maximum bus length of 25 meters.
Data Encoding	DME (Differential Manchester Encoding): Encodes data based on signal “transitions” rather than absolute voltage levels. (This method provides an inherent clock signal for reliable data recovery at the receiver).

Now that we have covered these basic parameters, the most critical question arises: In a bus network where all nodes share a single cable, how does 10BASE-T1S avoid data collisions? The answer lies in its core mechanism—PLCA.

3. Core Mechanism: How PLCA Works

3.1 The Fundamental Problem of Bus Networks

All bus technologies must prevent signal collisions and data corruption caused by multiple nodes transmitting simultaneously. Automotive networks use different solutions:

CAN: Non-destructive arbitration (nodes with lower IDs/higher priority win bus access).
FlexRay: Time Division (each node has a fixed time slot to transmit, preventing collisions at the source).

3.2 The PLCA Mechanism

The PLCA (Physical Layer Collision Avoidance) mechanism used by 10BASE-T1S applies this proven time-division concept from FlexRay to Ethernet. It prevents collisions from occurring at the source by precisely assigning a dedicated transmission time window to each node.

PLCA includes several core concepts:

Node ID: Each node in the network is assigned a unique ID from 0 to N, which determines its transmission order in the communication cycle.
Master Node: Usually the node with ID 0. It acts as the network coordinator and is responsible for periodically sending a “Beacon” to start a new communication cycle.
Beacon: A special signal sent by the Master Node that marks the start of a new transmission cycle and synchronizes the timing of all nodes on the network.
Commit Symbol: If a node has data to send during its transmission opportunity, it first sends a “Commit Symbol”. This symbol is crucial—it’s like “raising a hand to speak” in a meeting, clearly indicating that it will occupy the bus. This behavior distinguishes it from nodes that simply let their opportunity expire silently. After sending the Commit Symbol, the node immediately begins sending standard Ethernet data frames.
Transmit Opportunity (TO): After the Master Node sends the Beacon, all nodes receive a dedicated time window to send data, strictly in ascending order of their ID numbers.

With these basic concepts understood, let’s explore several specific scenarios to see how PLCA operates in actual communication.

4. PLCA in Action: Analysis of Common Scenarios

4.1 Scenario 1: All Nodes Have Data to Send

In this full-load condition, every node in the network needs to transmit data:

Node 0 sends the Beacon to start the cycle.
Node 0’s transmission opportunity arrives. Since it has data, it immediately sends a “Commit Symbol” followed by a full Ethernet data frame.
Next is Node 1’s opportunity; it also sends its “Commit Symbol” and data frame.
This process continues until all nodes have been polled.

4.2 Scenario 2: Partial Nodes Have Data to Send (e.g., Nodes 1 and 3)

In this more typical case, only some nodes need to transmit:

Node 0 sends the Beacon to start the cycle.
Node 0’s opportunity arrives and expires because it has no data.
Next is Node 1’s opportunity. Since it has data, it sends a “Commit Symbol” and its data frame.
After Node 1 finishes, it’s Node 2’s turn, but it has no data, so the opportunity expires.
Then Node 3 takes its turn, sending a “Commit Symbol” and its data frame.
The process continues until all nodes are polled.

4.3 Scenario 3: Idle Network (No Nodes Have Data)

In this simplest case, the entire network is quiet:

Node 0 (Master) sends the Beacon to start a new cycle.
It is Node 0’s transmission opportunity, but since it has no data to send, the opportunity automatically expires after a brief window.
It is then Node 1’s transmission opportunity; it also has no data to send, so the opportunity expires as well.
This process continues sequentially until the transmission opportunities for all nodes have been polled and expired. Then, the Master Node will send the Beacon again to start the next cycle.

5. PLCA in Action: Analysis of Optimized Scenarios

5.1 Scenario 4: Burst Mode

10BASE-T1S provides an optional “Burst Mode” to handle asymmetric data flows. In many automotive applications, data flow is not uniform—for example, a sensor might be a primary data producer while other nodes are consumers. Burst Mode allows a configured node to continuously send more than one frame within a single transmission opportunity. This greatly improves efficiency for nodes requiring high throughput.

5.2 Scenario 5: Multiple IDs for a Single Node

Engineers can software-configure a node to have multiple IDs if it requires low latency or high bandwidth. Furthermore, multiple IDs can be combined with Burst Mode. These strategies allow for fine-tuning of network performance to ensure priority for critical data, though they may increase the transmission latency of neighboring nodes.

6. PLCA in Action: Analysis of Special Scenarios

6.1 Scenario 6: A Slave Node (Non-ID 0) Unexpectedly Goes Offline

When an ordinary slave node is lost, the bus continues to operate as usual. When the scheduler reaches that node’s Transmit Opportunity (TO), the bus does not wait; the time window is simply skipped, and the polling moves immediately to the next node.

Network Stability: The communication cycle and other nodes are unaffected.
Diagnostics: While the physical layer remains normal, upper-layer protocols will detect the lost heartbeat or data to determine the node is offline.

6.2 Scenario 7: The Master Node (ID 0) Unexpectedly Goes Offline

This is a more serious event as the Master initiates the cycle. Slave nodes will experience an unusually long “silence”：

Network Stability: Since only the Master sends the “Beacon,” its loss means no new cycles can start once the current one ends.
Diagnostics: Some PHY chips have a beacon-loss timer; if no beacon is received for a long time, the PHY may fallback to the CSMA/CD model. This keeps communication alive but loses the collision-free and deterministic advantages of PLCA. Alternatively, the application layer can trigger a backup Master

6.3 Scenario 8: Two Slave Nodes Wrongly Configured with the Same ID

When the TO for the duplicate ID arrives, both nodes will attempt to claim the bus simultaneously.

Network Stability: A Collision occurs at the physical layer. Waveform distortion prevents the receiver from parsing valid data (CRC failure). While scheduling doesn’t stop, efficiency for that ID and subsequent nodes drops significantly.
Diagnostics: PHY chips trigger status registers: RXINTO (Receive in TO) or TXCOL (Transmit Collision). These are key tools for debugging ECU flashing or configuration errors.

6.4 Scenario 9: Two Nodes Wrongly Configured as ID 0 (Master)

This is the most severe logical conflict as both attempt to control the bus timing.

Network Stability: Synchronization collapse. Overlapping or out-of-order beacons prevent slaves from locking onto a sync frequency, paralyzing the PLCA cycle.
Diagnostics: PHYs feature “Multi-Master Detection”. A node configured as ID 0 that receives another beacon will set the UNEXPB (Unexpected BEACON Received) flag in the STS1 register.

6.5 Scenario 10: Master's MAX_ID Configuration is Lower than the Highest Node ID

For example, IDs 0-6 exist, but the Master’s MAX_ID (Node Count) is set to 3.

Network Stability: High-ID nodes are “silenced”. The Master sends a new beacon immediately after ID 2’s turn, so IDs 3-6 never get their opportunity.
Diagnostics: Affected slaves will trigger the BCNBFTO (BEACON Received Before Transmit Opportunity) flag in the STS1 register, proving the Node Count mismatch.

Through these scenarios, we can see how PLCA gracefully coordinates communication. So, compared to traditional point-to-point Ethernet, what practical benefits does 10BASE-T1S actually provide?

7. Advantages: Why Choose 10Base-T1S?

7.1 Core Advantages

Compared to traditional point-to-point switched Ethernet, 10BASE-T1S offers:

Reduced Hardware Cost and Wiring Weight: Connecting 5 ECUs via 10BASE-T1S requires only 5 transceivers (PHYs). A switched point-to-point solution would require 10 PHYs (5 in the ECUs and 5 on the switch). Fewer PHYs and simpler wiring lead to lower costs and lighter vehicles.

Enabling All-Ethernet Architecture: 10BASE-T1S fills a critical gap, allowing a unified technology (Ethernet) to cover everything from high-bandwidth systems to low-cost sensors/actuators. This greatly simplifies the overall vehicle network architecture.

7.2 Engineering Practice: Beyond Standard Limits

While the IEEE standard guarantees support for “at least 8 nodes,” research from Ford Motor Company shows that careful design can support significantly more. Key physical layer factors include:

Node Capacitance: Every component (PHY, connector, ESD protection) adds capacitance. The standard assumes 25pF per node; keeping this at 20pF or lower is essential for increasing node counts.
Node Spacing: Physical distance affects signal integrity. Ford’s research provides specific spacing recommendations:
- 8 Nodes: Min. 0.5m spacing.
- 8-10 Nodes: Min. 0.75m spacing.
- 10-15 Nodes: Min. 1.0m spacing.
- 15-20 Nodes: Min. 1.5m spacing.

This insight transforms theoretical standards into actionable engineering guidelines: by optimizing topology design and component selection, it is entirely possible to achieve a stable network with more than 8 nodes. Of course, the final design must undergo rigorous signal integrity testing to ensure all parameters comply with specifications.

Now that we have gained a comprehensive understanding of what 10BASE-T1S is, how it works, and its advantages, let’s wrap up today’s content with a summary.

8. Conclusion

10BASE-T1S is a highly innovative automotive Ethernet technology. It cleverly combines the simple wiring and cost benefits of traditional buses (like CAN) with the power and flexibility of the standard Ethernet ecosystem. Through its unique PLCA mechanism, it provides deterministic, collision-free communication on a single twisted pair, serving as a key foundation for the future efficient and cost-optimized “All-Ethernet” vehicle.