RV2 Tech Notes
RV2 or RS4 can't be reached on network
Product: RS4, RV2, Synapse
Date Added: 2019-01-10
If you can see the RS4/RV2 in zBusMon but are having problems mapping it as a network drive, reaching it from Windows Explorer, or problems retrieving an image from the RV2 camera in RVMap, it is likely a compatibility issue with the server protocol the RS4/RV2 uses.
You can enable support for SMB1 on your machine in the Turn Windows features on or off dialog (part of Add or Remove programs).
More information on the topic can be found at this link.
Timing issues with media players
Product: RV2, OpenEx, Synapse
Date Added: 2016-08-22
Media players do not provide synchronized playback for viewing or scoring recorded data. Because media players use time rather than frame number, playback will inherently lag behind data playback and this lag becomes longer over time. This happens because the frames per second (FPS) value is always rounded to an integer while the TDT clock runs at 24414.0625 Hz. If you select an RZ sample rate of 30 Hz, the actual sample rate is the corresponding fixed or realizable sample rate. For example: A rate of 24414.0625 / 30fps = 813.8 samples per frame. This gets rounded to 814. When stimulation is triggered at 24414.0625 / 814 = 29.9927 fps, which is the real FPS that the RV2 is triggered at and the video is stored at. When viewing in a media player that thinks the video is recorded at exactly 30fps, the time difference after 1 minute is [(30 / 29.9927) * 60000 ms/min] - 60000 = 14.6 ms.
Use the Video Viewer in OpenScope for synchronized data scoring. For more information of this feature, OpenEx users see: OpenEx User Guide, p. 258 Synapse users see: OpenEx Supplement for Synapse, p.43
External RV2 monitor is unreliable
Version: < 1.9
Date Added: 2015-09-04
When a second monitor is added to an RV2, the external monitor is sometimes unreliable. This behavior has been addressed and resolved with a firmware update.
Connect your RV2 to the internet and use the RV2 interface to upgrade it to the latest firmware version.
RS4 files named incorrectly, RV2 not identified by OpenEx/Synapse, zBusMon or Synapse can't identify RS4/RV2, or UDP communication failure
Product: RV2, RS4, RZ-UDP, Synapse, OpenEx, zBUSmon
Date Added: 2011-12-06
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.
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:
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.
Finding the MAC Address
Product: RS4, RV2, PZ5, BH32, RZ-UDP
Version: RS4 and RV2 Firmware < v1.13, PZ5 and BH32 = All
Date Added: 2014-08-15
In some labs, the network administrator may require users to provide a networked TDT device's MAC address.
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.
On your PC, run the zBUSmon network search to make sure you can see the device and note it's IP address.
Click Start. In the Search/Run box, type cmd and press the Enter key.
In the Command Line window, type ping xxx.xxx.xxx.xxx, replacing xxx.xxx.xxx.xxx with the IP address of the device.
After the ping response has finished, type arp -a.
Under Internet Address, locate the IP address you just pinged. In the same line, under Physical Address, the corresponding MAC address is listed.
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.