Revolutionize Automotive Ethernet with 10BASE-T1S Simplify, Scale, Save.
Say goodbye to legacy networks like CAN and LIN. Say hello to a unified, cost-effective Ethernet architecture built for the future of mobility.
Connect With Us
Our Field Of Expertise
Why Legacy Networks Are Holding You Back
Modern vehicles are packed with ECUs, sensors, and actuators. Yet, 80–90% of communication still happens over low-bandwidth legacy protocols like CAN, CAN-FD and LIN. These networks require gateways, add complexity, and limit scalability.
Meet 10BASE-T1S – Ethernet for Every Node
Key Benefits
- 10 Mbps shared bandwidth
- Single twisted pair cabling
- PLCA for collision-free access
- Power over Data Lines (PoDL)
- Scalable up to 255 nodes”
Built for Engineers, Trusted by OEMs
Technica Engineering offers two powerful tools to help you deploy, simulate, and analyze 10BASE-T1S networks
Capture Module 10BASE- T1S
Your All-in-One Solution for 10BASE-T1S Automotive Ethernet Testing and Monitoring.
Capture the traffic of the in-vehicle communication without losses
Easy and straight forward device configuration
Hardware timestamping and time synchronization support
Sleep and wake up capability to meet low power requirements
Network Interfacer 10BASE- T1S
High-Performance Solution for 10BASE-T1S Networking
Advanced routing and egress mirroring ensure efficient traffic management and diagnostics
10BASE-T1S PLCA configuration via DIP switches or an intuitive web interface
Real time device statistics to monitor your setup
Port segmentation and other switch functionalities, ensuring optimal data flow and reducing unnecessary traffic
Our Products at a Glance
| Feature | Network Interfacer 10BASE-T1S | Capture Module 10BASE-T1S |
|---|---|---|
| Role | Media converter & simulation tool | Passive logger & diagnostic tool |
| Ports | 3x 10BASE-T1S MQS | 6x 10BASE-T1S MQS |
| PLCA Configuration | DIP switch + Web GUI | Web GUI |
| Beacon & Empty Cycle Detection | × | ✔ |
| Traffic Injection | ✔ (Advanced License) | × |
| Logging | × | ✔ (Lossless, timestamped) |
| Use Case | Simulation, integration, testing | Diagnostics, compliance, analysis |
| Certification | Early Access (pre-CE) | Early Access (pre-CE) |
Technical Details
| Features | Capture Module 10BASE-T1S | Network Interfacer 10BASE-T1S |
|---|---|---|
Operating Temperature
|
-40 °C to +85 °C | -40 °C to +85 °C |
Supply Voltage
|
6 V to 30 V DC (Typ. 12 V) | 6.5 V to 32 V DC (Typ. 12 V) |
System Connector
|
MQS 16 Pin Connector For Power And 10BASE-T1S Bus | – |
Power Consumption
|
5 – 10 W | 5 to 7 Watt |
IP Protection Class
|
IP20 | IP 20 |
Housing Dimensions
|
99.5 mm (W) × 93 mm (L) × 32 mm (H) | 166.5 mm (W) × 130 mm (L) × 36 mm (H) |
Weight
|
0.3 kg (Approx.) | 0.7 kg (Approx.) |
Interface
|
USB-C Ethernet Port (1x 10/100BASE-T) RJ-45 Connector (1x 10BASE-T1) H-MTD Connector (1x 10BASE-T1S) SFP Port (1x 100/1000BASE-T) Micro-HDMI (Only for Internal Usage) |
6x 10BASE-T1S (MQS) 3x 10BASE-T1 (RJ45) for Config, Logging, Sync 1x 10BASE-T1 (MQS) for Config 1x 10BASE-T1S (MQS) for Config 2x Wake In/Out (MQS) |
Designed for Automotive. Ready for Deployment.
Already present in platforms of an European OEM, 10BASE-T1S is transforming how OEMs think about in-vehicle networking. Whether you’re building EVs, autonomous systems, or next-gen infotainment, this is the Ethernet layer that scales.
Datasheet
Capture Module 10BASE-T1S
Complete technical specifications, Connectivity options, and deployment guidelines
Download PDF 
Network Interfacer 10BASE-T1S
Detailed product information, performance benchmarks and integration examples
Download PDF
FAQ
How to check the link quality on a 10BASE-T1S connection?
In the TECMP Status Messages “Status bus” of the device you can find the link quality of each port, next to other information
What part of the daisy chain connection is referred to as a “stub”? What is a “stub”?
In a multidrop bus, the “stub” is any short connection branching off the main bus. Stub lines are local wires to each device.
How to set up a 10BASE-T1S Multidrop Network
- Cable Type: Use twisted pair cables specified for 10BASE-T1S, ensuring they meet the necessary electrical and mechanical specifications.
- Cable Length: The maximum total length for a 10BASE-T1S multidrop segment is 25 meters. Ensure the sum of all segment lengths does not exceed this limit. Stubs are allowed but they should not exceed 10 cm each.
- Bus Topology: In a multidrop configuration, all nodes are connected along a single continuous cable, forming a bus topology (daisy chain). Each node taps into this bus at its respective connection point.
- Node Spacing: Distribute nodes evenly along the bus to avoid signal reflections and ensure balanced loading. Maintain a minimum distance of 1 meter between nodes to minimize interference and signal degradation.
- Bus Termination: Proper termination at both ends of the bus is crucial. Use the appropriate termination resistors as specified in the 10BASE-T1S standard (differential 100 ohms) to prevent signal reflections and ensure reliable communication.
How to do proper cabling for 10BASE-T1S Technica devices?
- Ensure that all 10BASE-T1S connections in MQS connector are connected as described in User Manuals for specific Technica product (Network Interfacer 10BASE-T1S or Capture Module 10BASE-T1S)
- The device includes two pins for adding the 100-ohm differential termination. This termination can also be enabled or disabled internally through the webserver interface.
- To facilitate cabling, all 10BASE-T1S pins are duplicated. This allows you to create a bus with a daisy chain topology without needing to make any T-connections between wire pairs.
- Follow guideline from How to set up a 10BASE-T1S Multidrop Network (link to previous question) or User Manual
What is the maximum frame size which can be logged?
It is the same as the standard for Ethernet II.
The supported maximum frame size is 1514 bytes (mtu). Jumbo frames are not supported by our product.
When logging data, TECMP message flag information is always disbabled (PLCA Enabled)?
When a port is used as an injector, the “PLCA Enabled” flag is set to 1, else it is 0.
The PHYs are working in a passive mode and doesn’t take part in the PLCA cycle.
Which symbols are counted in the TECMP symbol count?
The current Symbol count is only counting BEACONs. Also, in future releases only the BEACONs will be counted.
The 10cm limit must be considered stub lines, when connecting the ECU as a branch?
It is guaranteed that it works always with stub lines lower than 10cm, longer stub lines can still be fine, setup dependent, but not guaranteed.
Proper operation is guaranteed for stub lines below 10 cm. Longer stub lines may work, depending on the setup, but are not guaranteed.?
Why is capturing not working on a port with activated traffic-injection?
This is expected behavior. Once a port is configured for traffic injection, it is dedicated to transmit and cannot support logging or packet capture functions simultaneously. The port is an active part of the 10BASE-T1S BUS.
How can be detected the Fallback Mode (CSMA/CD)?
- The fallback to CSMA/CD mode requires indirect observation and deeper analysis of logged data.
- 1-second TECMP Bus Status message provides some info about the BUS.
- But Event Logging license provides the possibility of a more precise detection mechanism. The Capture Module can generate Control Messages with precise timestamps whenever significant change in PLCA behavior is detected.
- The following PLCA-related events are particularly relevant:
- PLCA Symbols Detected: PLCA symbols (e.g., beacons) were absent for a period, and their reception has resumed.
- PLCA Symbols Missing: PLCA symbols were being received regularly but are now missing at the expected timing.
- PLCA Empty Cycle: Beacons are still present, but no Ethernet traffic is detected between them—this may indicate silent or idle operation.
How to detect a Malformed Topology?
- Packet collisions
- Frame CRC errors
- Symbol-level decoding issues
- PLCA-related events like PLCA Symbols Missing or PLCA Empty Cycle may indicate invalid or broken timing due to misconfigured nodes.
- Also End of Stream Delimiter (ESD) Errors, or 5B Decode Errors events might be helpful.
- CRC validation failures, are directly shown in TECMP traces and point to physical or MAC-layer corruption.
- A beacon with doubled periodicity could be a symptom of two Coordinators active on the bus—something observable via timestamp analysis in Control Messages.
- Event Logging Control Messages
- CRC and ESD error fields in TECMP
- Timing pattern analysis (beacon periodicity, jitter, etc.)
- This avoids the need for an oscilloscope or physical-layer tools in most cases.
Does the Network Interfacer support TC10?
- Needed HW: v3.1 or higher
- Needed SW: R.006.002 or higher
- License: no advanced license needed
SFP slot is not working?
- Is the port mode correctly configured (SGMII or 1000BASE-X)? Some SFPs are not supporting both
- Did you check with recommended SFP modules? (specific list link)
- Did you check which SFP modules are supported? (1G or less)
- Did you test with replacement of Network Interfacer with same SFP module?
which Switch is implemented in the Network Interfacer?
which PHY is used in the Network Interfacer?
which PHY is used in the Network Interfacer?
- 88Q5151 – FIR Switch B0 from Infineon for HW v2.1 and higher
- 88Q5151 – FIR Switch D0 from Infineon for HW 3.1 and higher
- The PHYs are integrated
There is no coordinator on the 10BASE-T1S BUS. How is Data Transmition working through the NI?
When the PLCA coordinator (Node ID = 0) is not present in the network, the devices cannot execute PLCA arbitration.
Fall Back: Instead, they fall back to a basic CSMA/CD-like (Carrier Sense Multiple Access with Collision Detection) mechanism, often referred to internally as CSDM:
- Devices attempt transmission after sending if the line is idle.
- There’s no guaranteed collision avoidance or deterministic time-slot scheduling.
- It is useful for simple or minimal test setups (e.g. 1–2 nodes) but not recommended for production environments or multi-node scenarios.
When does the “Collisions Tx” value increase on dashboard
A rising “Collisions Tx” value often indicates an issue with the physical setup, rather than actual protocol-level collisions.
In a properly configured PLCA (Physical Layer Collision Avoidance) network, physical collisions should never occur, as only one node is allowed to transmit at a time. This is managed by PLCA’s in-band signaling and timing coordination.
If the bus is not correctly terminated or if the impedance of the network is not within specification, the device may interpret the resulting signal reflections or disturbances on the line as a collision. This is because the physical characteristics of the signal in such cases can resemble the condition of two nodes transmitting simultaneously. Since the device cannot reliably differentiate between an actual simultaneous transmission and a poor bus condition, it increases the “Collisions Tx” counter accordingly.
Maximum Performance and PLCA Behavior
- transmit-opportunity is set to 3.2us:
- only 64bytes long frames are sent
- only node 0 is sending 1 frame per cycle
Why is the performance for 1 or 2 nodes worse in comparision to higher amount of nodes
This is because the MAC requires a minimum inter-packet gap (IPG) of 9.6 μs, which cannot be achieved when using 64-byte packets with Node Count = 1 or 2.
What is minimum Packet Interval in CSMA/CD?
In the specific case with only two active nodes (Node Count = 1 effectively means two devices in the network), the performance with or without PLCA should be quite similar—assuming there are no collisions. In such a scenario, the communication can operate close to the line rate even in CSMA/CD mode.
what is the difference of basic Interfacer mode and Multinode Injector
Main difference is that each node gets a unique MAC address. Further information can be found in the User Manual.
Is API control supported?
Yes. For more details, please check the UM.
Ready to Upgrade Your Automotive Testing?
Our network solutions provide the accuracy and reliability demanded by modern automotive development.