E2X Transport Configuration Help
Operating mode The Exgine platform can operate in one of two modes: Exgine Mode and Transport Mode. Exgine mode is to be configured if the board is embedded in an M50 exciter, while transport mode is used when the board is to translate from one E2X transport protocol to another and the board is not embedded in an M50 exciter.

E2X Transport Protocol This setting defines the protocol that is to be sent back out to the configured destination. The protocol to be received is configured as part of the network configuration screen. The E2X UDP protocol is the standard iBiquity defined E2X protocol running in uni-directional mode. E2X TCP mode is used for bidirectional links and is also a standard E2X transport mode, which is unsupported by iBiquity.

Note: Unlike the iBiquity implementation of this protocol on the exporter, this implementation can detect connection loss and automatically reestablish a connection with the exciter.

The Nautel E2X encapsulation mode is a Nautel proprietary transport mode for the E2X protocol. It can be used across uni-directional, as well as, bi-directional STLs.

Enable Timing Recovery Enabling this option filters incoming clock packet jitter by dsicplining a hardware phase locked loop to the incoming clock packet stream and filtering high frequency clock jitter. When this mode is enabled the unit first tries to determine an appropriate startup time and then relies on the phase locked for future clock packet transmission.

This mode is usefull when experiencing significant jitter across an STL that the exciter is unable to synchronize to. The resultant output jitter is due to on board processing delays and output Ethernet transmission, but the incoming clock jitter is removed.

In this mode the unit will only produce an output aftter successfully determining a starting point (128 clock packets by default).

Suggested default setting: yes

Transmit Buffer Depth The E2X Transporter requires a transmit buffer in order to remove any time variances in E2X packet delivery. The buffer depth is configured as E2X packets with a period of 92.8ms. This configuration should reflect throughput latency variations across the STL.

Note: Since the Nautel E2X encapsulation protocol distributes E2X data over time, this buffer must be configured to be at least 16 packets deep.

Suggested default setting: 16

Destination IP address Configures the receiver IP address. Broadcast IP addresses are supported. If the destination IP address is not on the same subnet as this board, ensure that a proper gateway is configured in the network configuration screen.

Destination MAC address If this board is connected to the destination address through a bi-directional network (i.e. it can be successfully pinged). Then the destination MAC address does not need to be configured and the Address Resolution Protocol (ARP) can dynamically determine the destination MAC address. In this case, configure the MAC address to 00:00:00:00:00:00. When using broadcast mode, no MAC address needs to be configured either.

Control Packet Rate When using the Nautel E2X encapsulation mode, the E2X control packet that starts an exciter's modulation process can be repeated after N data packets allowing an exciter to start automatically with a pre-established E2X stream. Set to 0 to disable control packet insertion.

Suggested default setting: 17

Main Bandwidth
The Nautel E2X encapsulation protocol uses this setting to guarantee this amount of bandwidth for the main E2X data stream not including retransmitted packets. This setting must be greater than the maximum bandwidth requirements for the E2X protocol as specified by iBiquity. Setting is in bits per second.

Suggested default setting: 150000

Total Bandwidth The Nautel E2X encapsulation protocol uses this setting to guarantee overall bandwidth consumption including retransmitted data does not exceed this amount of bandwidth. This setting should reflect the maximum bandwidth allocated to the E2X data stream across the STL. This includes the main bandwidth setting and, therefore, must exceed the main bandwidth setting. By setting this value to reflect available STL bandwidth, the Nautel E2X protocol minimizes congestion across the STL.

Suggested default setting: 300000

Data Plane Port
Control Plane Master Port
Control Plane Slave Port

The port assignments for the Nautel E2X encapsulation protocol can be changed with these settings.

Do not change unless directed by Nautel Customer Service.

IP TOS field (decimal) This setting controls the Type of service (TOS) field in the IP header of the emitted data stream for the E2X encapsulation protocol. If intermediate STL equipment implements Quality of Service queuing then this setting can provide a higher priority of the HD traffic compared to other traffic. This setting must be entered in decimal.

The TOS field is an 8-bit field with the following bit definition:


bit: 0 1 2 3 4 5 6 7

Bits 0-2: Precedence
111 	Network control.
110 	Internetwork control.
101 	CRITIC/ECP.
100 	Flash override.
011 	Flash.
010 	Immediate.
001 	Priority.
000 	Routine.

Bit 3: Delay
0 	Normal delay.
1 	Low delay.

Bit 4: Throughput
0 	Normal throughput.
1 	High throughput.

Bit 5: Reliability
0 	Normal reliability.
1 	High reliability.

Bits 6-7: Reserved for future use.

To determine this setting, concatenate the desired settings in a binary number string. For example, for high priority traffic we want Flash precedence, low delay, high throughput, and high reliability, so we arrive at a binary number of 01111100. This number can be entered into a scientific calculator (as provided by most operating systems) and converted into decimal. In our case, this translates into decimal 124.

Suggested default setting: 0 (normal priority) 124 (high priority)

More information on the IP protocol can be found at http://www.protocols.com/pbook/tcpip2.htm

Different TOS for clock packets This setting allows a different TOS value to be configured for E2X clock packets in order to provide for improved studio transmitter synchronization.

Suggested default setting: no

Clock TOS field (decimal) This field operates in the same way as the previously described IP TOS field and configures the TOS value for clock packets only.

Suggested default setting: 0