This article will discuss the various methods for configuring DxLink Tx and Rx endpoints for use with a DVX or DGX switcher where Auto Setup is not desired, or as a point to point setup with a Master connection.

Auto Setup

Auto Setup is available on the DGXx00 Series and DVX-x26x-4K switchers. This allows any DxLink Tx or Rx unit to be automatically bound to the master and given a Device ID and an IP address on the internal ICSLAN network.

Device IDs and IP addresses are fixed and based on the port of the switcher, so if devices are swapped around, the ID and IP stay with the port of the switcher.

ModelDevice ID rangeIP address range
DX-TX (v1.8.x or higher)45001 - 45064198.18.130.1 -
DX-TX-4K6045001 - 45064198.18.130.1 -
DX-RX (v1.13.x or higher)46001 - 46064198.18.134.1 -
DX-RX-4K46001 - 46064 -
DX-RX-4K6046001 - 46064198.18.134.1 -

Example of a DX-RX-4K with Auto Setup enabled:

If there is a requirement to manually bind the DxLink devices to the Master so they reside on the main LAN, Auto Setup can be disabled via the Web UI under the Status menu. 

Doing so will factory reset any connected DxLink devices ready for manual configuration.

Manual configuration is also required when using a legacy DGX or DVX system that do not have the Auto Setup feature.

Manual configuration methods

When manually configuring devices to reside on the LAN network, they will show in the Online Tree as an Unbound or Searching NDP device and can be seen by any Master on the same network. 

When seen like the above, it is ready to be bound to the Master, of which there are 4 available methods.


This is the recommended method of binding devices due to the two way communication between the Master and the DxLink device making it more stable communication method.

Setup can be achieved via a telnet connection to the DxLink device, using the commands 'Set Connection', 'Set Device', and 'Set IP', with Set IP being optional depending on the IP setup of the network.

After issuing the Set Connection command, follow the steps to input the correct data, pressing Enter to move to the next stage. If data already exists, i.e. Master IP, type the new value and it will be placed to the right of the current value.

Enter Mode - Type T for TCP/URL

Enter Master IP/URL - Type in the IP or URL of the Master (hostnames can be used)

Enter Master Port - 1319 is the registered ICSP communication port and should not be changed

Enter Master User - Only required if ICSP encryption is enabled on the Master

Enter Master Password - Only required if ICSP encryption is enabled on the Master

Once confirmed that the details are correct by typing Y, you can now issue the Set Device command in the format:

Set Device <dev ID>, i.e Set Device 7001.

Once configured and rebooted, the device will now show in the main section in the Online Tree of the master you have bound it to. It will no longer show as an Unbound NDP device, and will no longer be shown in the Online Tree of any other Masters (unless Master to Master communication is in use).


UDP is configured in the same manner as TCP above. As UDP is only one way communication, it is not recommended as it can prove more unreliable and cause the device to disappear from the Online Tree, causing any control of the device, or control from it's ports (such as RS232 to a display), to be lost.


Auto mode uses the System Number of a Master to make a connection.

Using the Set Connection command, you will be prompted to enter the System Number of the Master you wish to connect to.

This is only a suitable connection method where all System Numbers on a network are unique. By default, all Masters are set to System 1, which is not an issue unless using Master to Master.

Where there a multiple Masters all on System 1, your device may connect to the correct Master, but should there be any drop outs and re-connections, or a device is rebooted, it may then come back online and connect to a different Master with System 1, therefore you will have no control of it.


NDP uses a dynamic connection method to the MAC address of a Master, as opposed to the IP address. 

While this is a more user friendly option by binding in Netlinx Studio, it is also not 2 way communication like TCP.

There is also the possibility that the MAC address of the Master could change, either due to the need to swap it out for servicing, or if upgrading a DGX CPU from a legacy model, to a 100 Series CPU. The change of MAC address would require you to reconfigure all of the DxLink endpoints to the new MAC address.

In the case of TCP binding, once the new CPU is set to the IP address of the old one, all the endpoints will automatically reconnect.