Contents

10BASE-T1S — Ethernet to the edge

10 Mbit/s single-pair Ethernet with a multidrop bus topology, giving CAN-like wiring with Ethernet addressing for sensors, actuators and smart lights in zones.

Why it exists

Gateways that translate between CAN and Ethernet add latency, software and cost. If the edge of the network spoke Ethernet too, data could flow from sensor to central compute without translation. 10BASE-T1S makes that affordable.

What it is

  • 10 Mbit/s over a single twisted pair.
  • Multidrop: several nodes share one cable, like CAN.
  • PLCA (Physical Layer Collision Avoidance): nodes take turns in a round-robin cycle, so access is deterministic and collision-free.
PLCA cycle
BEACONSent by node 0
Node 0Transmit opportunity
Node 1Transmit opportunity
Remaining IDsOne opportunity each, in ascending order
Next BEACONNode 0 starts the next cycle

The configured node count determines the cycle's opportunities; nodes without data let their opportunity pass.

How it is used

A zone controller connects a 10BASE-T1S segment to smart lamps, sensors or actuators. Some concepts let edge nodes be controlled remotely without their own application software.

When to use it

For edge devices that need more than LIN offers, IP-based diagnostics or a uniform Ethernet architecture. Compare with CAN FD and CAN XL on cost and ecosystem.

Best practices

  • Configure PLCA node IDs and cycle times consistently and document them.
  • Validate worst-case latency with all nodes active.

Common pitfalls

  • Expecting 10 Mbit/s of throughput per node — the bandwidth is shared across the segment.

What it means for your discipline

  • Networks & communication Core

    Designs multidrop segments and PLCA configuration; bridges edge nodes into the Ethernet backbone without protocol translation.

  • Hardware & silicon Core

    Uses low-cost PHYs and transceivers; some edge nodes need no MCU at all (remote control protocol).

  • E/E architecture Partial

    Allows an 'Ethernet everywhere' architecture that simplifies gateways and software.

  • Cybersecurity Partial

    Ethernet security mechanisms like MACsec become possible at the edge — if the node can afford them.

  • Base software Partial

    Requires Ethernet stack support in zone controllers and edge ECUs.

No direct stake: Functional safety · HPC & application software · Diagnostics & lifecycle · Software update & OTA

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)

Not directly involved on this node type.

MCU-based ECU · AUTOSAR Classic
  • ECU abstraction — Connects the Ethernet stack to edge-network hardware through EthIf and transceiver abstractions.
  • Microcontroller abstraction (MCAL) — Drives the Ethernet controller and supports hardware-specific configuration needed for the shared 10BASE-T1S segment.
  • Microcontroller · HSM — Provides controller resources and peripheral interfaces for an MCU-based Ethernet edge node.