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. |
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.
Essentially, PLCA establishes a transmission cycle used to choreograph Transmit Opportunities (TOs) on the bus. As with a group of individuals participating in a team-building exercise, if all nodes were chaotically speaking their minds at once, nothing would be heard properly and nothing would get accomplished in the time allotted. A PLCA transmit cycle establishes the opportunities to speak and the order in which nodes can be heard, while leaving enough flexibility that time is not wasted waiting for those who have nothing to say.
In PLCA, each node (aka PHY) is assigned with a unique PHY
ID, and only the PHY device that owns the transmit opportunity is allowed to
send data. The transmit opportunities are allocated in a round-robin algorithm
starting from PHY ID = 0, which is allocated to the Master. Nodes can initiate
a transmission only during the transmit opportunity that matches their own node
ID. A new cycle is started when the Master node sends a synchronization pattern
called the BEACON to signal the start of the PLCA cycle.
The PLCA cycle itself consists of the BEACON followed by N+1 time slots, allowing N+1 variable size DATA packets to be sent. During their transmit opportunity, a PHY may immediately transmit a packet or must transmit a COMMIT pattern of SYNC symbols to compensate for any MAC latency and to buy additional time before transmitting a packet. Nodes can enlarge the time slot to accommodate larger transmissions and can burst high priority messages. The other nodes will wait for a node to complete transmission before the cycle moves to the node with the next transmit opportunity. A new time slot starts if nothing is transmitted within a defined time (TO_TIMER) or at the end of any packet transmission.
At the beginning of each transmission cycle, Node 1 on the bus is first assigned the transmit opportunity. If there is no DATA for this node to transmit and it cannot COMMIT, it cedes its transmit opportunity to the next node on the bus.
In attempting to understand the PLCA cycle, it may help to
visualize the use of a variable delay line to relate transmit opportunities to
each node on the bus. The driving scheme of PLCA is to sync TO_TIMERs so that
the max latency consistently remains less than one PLCA cycle. TO_TIMER is very
short (typically 20 bits), so there is a negligible loss of throughput when
waiting for PHYs that have nothing to transmit.
Fig. 3, Maximum latency PLCA cycle. Every node has the
maximum size packet and sends a COMMIT while waiting for the MAC. |
The benefit of this system is that the individual nodes track TO_TIMER independently following the BEACON. Because nodes with no data to transmit will yield their transmit opportunity, the short window afforded by the TO_TIMER ensures a minimal loss of throughput or increase of latency. This variable delay is similar to TDMA, but PLCA is not a fixed or absolute reference for timed packets; instead, it adjusts according to the transmit needs of each node on the bus.
Also see:
The Difference Between 10Base-T1S and 10Base-T1L
Automotive Ethernet in the Vehicle
No comments:
Post a Comment