Skip to content

RS4 Tech Notes

RV2 or RS4 can't be reached on network

TN0990

Product: RS4, RV2, Synapse
Version: All
Date Added: 2019-01-10

Issue

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.

Solution

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.

RS4 High Channel Count Streaming

TN0989

Product: RS4, Synapse, RPvdsEx
Version: 90
Date Added: 2018-10-15

Issue

Improvements to the RS4 firmware have improved stability when streaming high channel count data to multiple ports on the RS4. This requires updates to the software (Synapse and RPvdsEx macros) and RS4 firmware.

Solution

Users streaming high channel count data to multiple RS4 ports require an additional setting. The "Use Larger Buffer Size" option allows more DSP memory to hold the data destined for the RS4, which improves reliability during the data transfer. The RS4 must be updated to v1.19 firmware to most effectively use this setting (more on that below).

In Synapse, this option is in the RS4 options:

If using OpenEx, this option is in the v90 Stream_Server_MC macro In RPvdsEx:

RS4 v1.19 Firmware Update:

It is recommended that all RS4 users update to the latest RS4 firmware. With the RS4 connected to the internet, go to the Config tab and select "Update Firmware". The updates are incremental, so you may need to repeat this step several times until the version number at the top of the Ports tab says "v1.19".

In v1.19, the RS4 saves a log text file within each recording folder that tracks the starting and ending sample of each stream. It also makes audible beeps when a recording starts and stops, or if there is a transfer error during the recording.If there is a gap in the saved data stream (typically this would be caused by a physical problem with the fiber optic connection between the RZ2 and RS4), this will also be indicated in the log file, so the data can be aligned in post processing. If the gap is long enough, the RS4 will assume the recording has stopped and start new files when data comes in. This allowable gap is controlled by the "Rec Stop Timeout" setting on the Config tab Settings.

Issue streaming 32-bit data to RS4 in v90

TN0988

Product: RS4, Synapse
Version: 90
Date Added: 2018-10-15

Issue

32-bit data recorded by the RS4 in v90 Synapse is all zero.

Solution

Users streaming 32-bit data to the RS4 who have already updated to v90 Synapse must install a new patch to fix a potential data transfer issue. With the Synapse computer connected to the internet, go to Menu → About → Check for Updates to install the latest version. This issue was resolved in Synapse v90.0.39174.

RS4 does not properly close files when switching between Preview and Record modes

TN0969

Product: RS4
Version: All
Date Added: 2015-05-26

Issue

The RS4 does not recognize OpenEx Record and Preview mode changes if they occur too quickly. The RS4 detects a data stream, opens the necessary files and start writing until the stream stops. If you switch between Preview and Record mode quickly, there isn't a large enough break in the stream for the RS4 to detect that the data stopped, and a new stream has started. When this happens the RS4 doesn't close the data file, continuing to record in the same file.

Workaround

To prevent this, make the Workbench window active, go to the Setup|Triggers and Mode Switching menu, and set 'zTrgA On' to 1000 ms. This ensures that whenever the system enters Preview or Record mode, there is a break in the streaming data of at least 1 second.

Copying/deleting files while RS4 is recording causes crash

TN0959

Product: RS4
Version: < 1.8
Date Added: 2016-01-29

Issue

Copying or deleting files while the RS4 data streamer is recording can cause a system crash.

Workaround

Connect your RS4 to the internet and use the RS4 interface to upgrade it to the latest firmware version.

Data Stores Have Different Durations

TN0957

Product: TTankX, OpenEx, RS4, Synapse
Version: All
Date Added: 2015-09-02

Issue

When comparing different data elements saved with the TDT system you may see different total recorded lengths. The TDT data storage methodology emphasizes and guarantees data synchronization across all data sampled on a TDT system, independent of sample rate or data format - even across different devices within the system.

In software, continuous data is stored as a timestamp and a chunk of points that starts and remains synchronized, sample for sample, for the entire recording session. You see different total recorded lengths on different data elements saved with the TDT system because the data Stores are saved to the tank in evenly sized chunks and only full chunks are written. This chunk size is user settable or set automatically in software depending on the sampling rate. By default, chunk sizes run anywhere from 100ms to 500ms. For example, the default chunk size is 2048 samples when sampling at 24414.0625 Hz. You can see the exact chunk size in the Storage Specification table when Workbench is in 'Idle' mode, under 'Store Description'.

When recording ends, sampling stops, and any incomplete chunks are not saved to disk. The start time for each store will always line up precisely, but the recorded duration of each data store will likely be different.

The RS4 works differently. Data is saved sample-by-sample while the software is recording, so its chunk size is effectively one and thus it will always have more data than stores with 'chunked' data.

All data across the tanks and RS4 will be synchronized from the onset of the recording, but each store might have a different recorded duration.

Here is a graphical depiction of what is happening:

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.

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.

Tank server reads SEV file header as data

TN0900

Product: RS4
Version: < v1.9
Date Added: 2012-06-07

Issue

In RS4 versions < v1.9, the first 80 bytes of each SEV file are used for the header, however, the tank server only ignores the first 40 bytes. The second 40 bytes are returned as if they were the first data points in the recording.

If the file consists of 32-bit floating point values, this will appear as 10 zeros at the start of the recording. If the file consists of 16-bit integer values, this will appear as 20 zeros at the start of the recording.

Workaround

Ignore the first 10 or 20 values read by the tank server, depending on the data format of the SEV file.

Solution

Upgrade the RS4 firmware to v1.9 or greater. The SEV header is now 40 bytes, which the tank server correctly ignores.

Blocks missing or skipped when user changes the active interface tab on the RS4

TN0879

Product: RS4
Version: All
Date Added: 2010-10-12

Issue

Start/stop messages sent to the RS4 by the RZ may be missed if the RS4 interface is not on the Port tab or if the user changes the active interface tab during recording. If this happens, data files will not be closed and opened correctly, and blocks will be skipped or missing. Any new recording blocks started will be added to the most recent block.

Solution

The RS4 interface should be set to the Port tab during recording. Avoid changing the active interface tab while the RS4 is recording data.