SPRY351 September   2025 DRV8434A-Q1 , DRV8889-Q1 , MCF8315C-Q1 , MCF8316C-Q1 , MCF8329A-Q1 , TPS92544-Q1

 

  1.   1
  2.   Overview
  3.   At a glance
  4.   Introduction
  5.   Traditional vs. remote-controlled edge nodes
  6.   Remote-controlled edge-node benefits
  7.   Remote-controlled edge-node considerations
  8.   Remote-controlled edge applications
  9.   Remote-controlled edge protocols
  10.   Remote-controlled edge system solutions
  11.   Conclusion

Remote-controlled edge protocols

The solutions for remote-controlled protocols include 10BASE-T1S, CAN FD light and UART over CAN. These protocols operate in half duplex, allowing non-simultaneous, bidirectional data transmission between two devices. Half duplex enables multidrop capability, where more than two devices communicate on the same bus, requiring only a single networking device in the commander ECU to interact with multiple edge nodes. Figure 7 illustrates an example of a multidrop topology.

 A multidrop topology from a
                    commander ECU to edge nodes. Figure 7 A multidrop topology from a commander ECU to edge nodes.

10BASE-T1S, CAN FD light and UART over CAN differ in speed, payload capacity and number of nodes in the multidrop and bus topologies. Table 2 compares these protocols.

Table 2 Remote-controlled edge networking protocol comparison between 10BASE-T1S, CAN FD light and UART over CAN.
10BASE-T1S CAN FD light UART over CAN
Network protocol Ethernet CAN UART
Speed 10Mbps 1-5Mbps 0.1-1Mbps
Payload 46-1,500 bytes 1-64 bytes 1-64 bytes
Maximum number of nodes 16 64 64
Topology Round robin Commander responder Commander responder

Figure 8 shows the difference between the round-robin and commander-responder topologies. The round-robin topology operates cyclically, where each node has a dedicated transmission opportunity per cycle based on its node ID. This automates arbitration, but requires mediation to ensure that priority or time-critical data is not delayed by low-priority data on the bus. The commander-responder topology requires the commander ECU to prompt downstream nodes before sending data on the bus. The order of transmission is up to the commander ECU rather than being dictated by node ID.

 Transmission comparison of
                    round-robin vs. commander-responder topologies. Figure 8 Transmission comparison of round-robin vs. commander-responder topologies.

10BASE-T1S, standardized by Institute of Electrical and Electronics Engineers (IEEE) 802.3cg, uses the Remote Control Protocol, which is standardized by Technical Committee 18. It operates at 10Mbps and in a round-robin multidrop topology. As an Ethernet protocol, 10BASE-T1S can incorporate Ethernet features such as Media Access Control Security (MACSec), Time-Sensitive Networking (TSN), Audio Video Bridging (AVB) and Power over Data Line (PoDL). Table 3 describes these four features. Additionally, systems already using a high-speed Ethernet backbone may benefit from simplified software with an all-Ethernet network.

Table 3 List and description of 10BASE-T1S Ethernet features and standards.
Feature Description Standard
MACSec Layer 2, point-to-point cybersecurity protocol for Ethernet IEEE 802.1AE
TSN Standards enabling deterministic, real-time communication for data synchronization throughout an Ethernet network IEEE 802.1Q
IEEE 802.1AS
AVB Standards defining TSN for audio and video applications IEEE 802.1BA
IEEE 1722
PoDL Power transmission over shielded twisted-pair cables used for point-to-point Ethernet IEEE 802.1cg

CAN FD light, a variant of CAN FD based on the International Organization for Standardization (ISO) 11898-1:2024 standard, operates at 1Mbps to 5Mbps. Unlike traditional CAN, which follows CAN arbitration (where nodes transmit simultaneously and the node with the lowest node ID wins), CAN FD light operates using a commander-responder topology. Edge nodes employ CAN FD light responders, while commander ECUs use CAN FD light commanders or CAN FD transceivers. Since many preexisting architectures already use CAN FD transceivers to communicate with edge nodes, integrating CAN FD light into current architectures is easy. Achieving speeds >1Mbps requires CAN FD light commanders, however, given controller arbitration phase constraints.

Both the 10BASE-T1S and CAN FD light protocols bridge Ethernet and CAN to other protocols such as SPI, I2C, UART, GPIO and PWM (see Figure 9). This bridging enables remote control of multiple sensors and drivers through 10BASE-T1S and CAN FD light, making both solutions versatile across various end applications.

 Block diagram of a 10BASE-T1S
                    or CAN FD light edge node. Figure 9 Block diagram of a 10BASE-T1S or CAN FD light edge node.

UART over CAN transmits UART packets over the CAN physical layer (PHY) using CAN transceivers (see Figure 10). Operating at ≤1Mbps in a commander-responder topology, UART over CAN offers a cost-effective solution but relies on UART-based drivers such as an LED, or motor drivers with integrated real-time control and diagnostic features.

 Block diagram of a UART over
                    CAN edge node. Figure 10 Block diagram of a UART over CAN edge node.

Smart drivers with integrated real-time control complement remote-controlled edge solutions by reducing the amount of upstream control requirements. Texas Instruments (TI) offers smart motor drivers with integrated control for sensorless motor systems, including sensorless field-oriented control for brushless-DC (BLDC) motor drivers and integrated current sensing and stall detection for stepper motor drivers. Stepper motors are especially good for remote-controlled edge applications because they require less upstream diagnostic data given the increased rotation accuracy. Table 4 lists some TI devices.

Table 4 TI’s motor-driver offerings.
Device Type Field-effect transistor
MCF8329A-Q1 BLDC motor driver External
MCF8316C-Q1 BLDC motor driver Internal
MCF8315C-Q1 BLDC motor driver Internal
DRV8889-Q1 Stepper motor driver Internal