Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

Configuring IRIG-B Port Parameters for CTP Bundles (CTPView)

This topic describes how to configure port parameters for IRIG-B daughter cards.

Adaptive clocking is configured by default on IRIG-B bundles, and the packet size is set to 64 bytes. The packet size combined with the default data rate of 16 Kbps produces a packet rate of 32 pps, which is a good packet rate for adaptive clocking.

Before you begin:

  • Log in to the CTPView software at least at the Net_Admin level.
  • Connect the CTPView server to the CTP device for which you want to configure bundles.

To configure IRIG-B port parameters using CTPView:

  1. In the side pane, select Bundle > Configuration.
  2. Run your mouse over the Display and Select an Existing Bundle bar.
  3. In the table of bundles, select the bundle that you want to modify.
  4. Under Bundle Options, configure the parameters as described in Table 39 and click Click to Submit Bundle AND Port Changes.

Table 39: CTP Bundle IRIG-B Port Parameter Settings in CTPView

FieldFunctionYour Action

Port Description

Specifies a description for the port.

Enter a description of up to 64 alphanumeric characters. Do not use the following characters:

( ; ' " ) ]

I/F Type

Specifies the daughter card as the interface type.

Select DCARD.

Port Speed

Specifies the data rate on the IP connection.

Unless network bandwidth is at a premium, we do not recommend that you change this value from the default of 16,000 bps.

Enter a number from 1.000 through 25.500 KHz. The port speed must be a multiple of 100 bps.

Direction

Specifies the direction of the circuit. Although the IP circuit connection through the network is full duplex, an IRIG-B circuit is actually a simplex application, and the daughter card can operate only in Rx or Tx mode and not both at the same time.

If the autonegotiation setting of the CTP Ethernet media and the far-end switch or router do not match, it is possible for the CTP Ethernet ports to be in a half-duplex state, although the duplex setting is not configurable and always assumed to be full-duplex on the CTP device. Starting with CTPOS Release 7.2, the half-duplex state at CTP network interface card (NIC) ports are acquired, regardless of the duplex setting configured on the far-end node. After the autonegotiation process is completed, if the CTP NIC cannot acquire full-duplex mode, then the interfaces are considered to be down and a log message is recorded in both the /var/log/messages directory and the syslog file stating that the interface is down due to a non-full duplex condition. You are prompted to verify the cable connection, speed, and duplex settings because the NIC link might be down.

Select one:

  • RX—The end of the circuit that recovers IRIG-B from the attached cable and generates IP packets toward the network.
  • TX—The end of the circuit that accepts IP packets, extracts the IRIG-B data codes, and transmits IRIG-B signaling output onto the cable.

Output High Volts Level

This option appears only if you set the direction of the port to Tx.

Specifies the high output level, which is measured in peak-to-peak voltage. This setting is based on a 50-ohm termination

Enter a number from 0.00 through 7.85 volts peak-to-peak.

Output Low Volts Level

This option appears only if you set the direction of the port to Tx.

Specifies the low output level, which is measured in peak-to-peak voltage. This setting is based on a 50-ohm termination.

Enter a number from 0.00 through 7.85 volts peak-to-peak.

Clock Cfg

Specifies the type of clocking for the bundle.

Select one:

  • Custom—The custom clocking configuration is used.
  • Voice/IRIG-B Master End—This end of the circuit generates a clock signal and sends it to the remote end.
  • Voice/IRIG-B Slave End—This end of the circuit receives the clock signal from the remote end. The clock slave uses its period to determine when to sample data and how to transmit data across the link.

Modified: 2018-01-29