... | ... | @@ -2,7 +2,8 @@ |
|
|
|
|
|
We propose to utilise the common RoE frame structure.
|
|
|
|
|
|
![RoEv2.004](uploads/43c202beabc88d0d8d9960ea61df2001/RoEv2.004.png)
|
|
|
|
|
|
<img src="uploads/43c202beabc88d0d8d9960ea61df2001/RoEv2.004.png" width="700" >
|
|
|
|
|
|
It is comprised of:
|
|
|
* Destination address [0xffffff - indicating broadcast]
|
... | ... | @@ -44,7 +45,10 @@ If an RoE frame is received with a presentation time that has already |
|
|
expired, subsequent DDS words linked to that presentation time must be
|
|
|
discarded. If an RoE frame contains multiple presentation time fields, they must be in temporal order.
|
|
|
|
|
|
![RoEv2.006](uploads/ad4685cd7d267ca9d6e13b6a6ff0297f/RoEv2.006.png)
|
|
|
|
|
|
<img src="uploads/ad4685cd7d267ca9d6e13b6a6ff0297f/RoEv2.006.png" width="700" >
|
|
|
|
|
|
|
|
|
|
|
|
DDS Configuration words may be sent periodically, such that **deMappers** can
|
|
|
join the Ethernet work and subscribe to a **flowID** to recreate RF signals dynamically.
|
... | ... | |