Skip to content

RZ-UDP Tech Notes

UDP network connectivity issues

TN0942

Product: RZ-UDP
Version: Serial numbers RZ2-2 < 3052, RZ2-4 < 3067, RZ2-8 < 3078, RZ5-1 < 2066, RZ5-2 < 2066, RZ5D < 1084
Date Added: 2014-10-27

Issue

Some UDP interfaces have non-unique MAC addresses. If UDP interfaces with duplicate MAC addresses are used on the same network, the behavior of the interface will be unpredictable. Depending on how the network is setup, the second device added to the network might not come online at all or might seem partially functional as some traffic intended for the first device is received.

This can affect a lab that uses multiple UDP interfaces on the same network or two or more labs that share a network with each lab using their own UDP interface. If you have multiple UDP interface devices, check the MAC address of both devices to determine whether this is the source of your UDP issues.

Solution

Contact Support for assistance reprogramming the interface. In most cases, this can be resolved without returning the device.

RS4 files named incorrectly, RV2 not identified by OpenEx/Synapse, zBusMon or Synapse can't identify RS4/RV2, or UDP communication failure

TN0939

Product: RV2, RS4, RZ-UDP, Synapse, OpenEx, zBUSmon
Version: All
Date Added: 2011-12-06

Issue

OpenEx, Synapse, and zBusMon use UDP packets to broadcast to or receive information from an RS4, RV2 or RZ with UDP on a local network. If these packets are blocked for any reason, the software can't communicate with them and no packets can be received.

When using the RV2, this will cause any attempt at communication with the device to fail.

When using an RS4, the data is still streamed but tank and block file naming information are lost and the RS4 names the data incorrectly.

When using an RZ with a UDP, UDP communication will fail.

When using zBusMon (version 80 or later), the devices are not displayed in the device diagram. Because this problem occurs with zBusMon, but not Windows Explorer, zBusMon serves as a good tool for confirming the source of problems first identified in OpenEx/Synapse Rig Editor.

Solution

The UDP packets may be blocked for any of several reasons.

If you are using OpenEx version 2.12 or earlier, upgrade to the latest version of OpenEx to avoid any related issues resolved in OpenEx version 2.14.

If you are using version 2.14 or later, packets might be blocked either by a Windows Firewall or by firewalls in place on your institutions network.

If your system is connected to your institution's network, TDT strongly recommends getting a small network switch, such as the one found at:

http://www.newegg.com/Product/Product.aspx?Item=N82E16833166061

and connecting all devices to the switch instead. This should resolve the problem. If this isn't feasible, contact your IT department for assistance.

If your system is not connected to your institution's network and you are still having a problem, it is likely that a Windows Firewall is in use on your PC (and a user may have clicked "block" the first time the system tried to communicate across the firewall). To resolve this issue, add a firewall exception for zBusMon and Synapse (or OpenWorkbench for OpenEx users) on port 41257.

Streaming Limitations Using the RZ-UDP Interface

TN0938

Product: RZ-UDP
Version: RZ2-2 Serial number < 3052, RZ2-4 SN < 2067, RZ2-8 SN < 3078, RZ5-1 SN < 2066, RZ5-2 SN < 2066, RZ5D SN < 1084
Date Added: 2014-08-13

Issue

RZ-UDP interfaces installed in RZ's with the specified serial numbers are unable to stream more than 180 channels without special data handling in the RPvdsEx circuit.

Workaround

The ZIP file linked below contains a circuit example which splits the UDP packet in two and alternates which channels are sent over:

UDP workaround zip

Contact Support if you need assistance implementing the workaround.

Solution

This limitation has been corrected for devices with the serial numbers listed above or greater. The correction can be implemented on older devices, but it must be implemented at the factory. Request an RMA from Support.

Finding the MAC Address

TN0936

Product: RS4, RV2, PZ5, BH32, RZ-UDP
Version: RS4 and RV2 Firmware < v1.13, PZ5 and BH32 = All
Date Added: 2014-08-15

Issue

In some labs, the network administrator may require users to provide a networked TDT device's MAC address.

Workaround

For the RS4 and RV2:

Upgrade the RS4 or RV2 firmware to v1.13 or later (available on the Config tab). The MAC address can now be found on the RS4 and RV2 touchscreen interface. Show the Status tab and touch the Current IP value. A Network Configuration dialog pops up and the MAC address is displayed in the dialog.

For other devices:

To determine the address, the PC must be directly connected to the TDT device so that they are on the same network. Connect one of the devices for which you need the MAC address and complete the steps below, then repeat with each device, one at a time.

  1. On your PC, run the zBUSmon network search to make sure you can see the device and note it's IP address.

  2. Click Start. In the Search/Run box, type cmd and press the Enter key.

  3. In the Command Line window, type ping xxx.xxx.xxx.xxx, replacing xxx.xxx.xxx.xxx with the IP address of the device.

  4. After the ping response has finished, type arp -a.

  5. Under Internet Address, locate the IP address you just pinged. In the same line, under Physical Address, the corresponding MAC address is listed.

Note

If the TDT device does not automatically identify on a network, you can force it to reset its IP address by unplugging the Ethernet cable and plugging it in again.

UDP interface is unable to send packets

TN0864

Product: RZ-UDP, RPvdsEx
Version: 1.2
Date Added: 2009-09-28

Issue

When using the RZ_UDP_Send macro, the UDP interface is unable to send packets.

Solution

Update to the latest version of the RZ UDP Utility.