Skip to content

RP2 Tech Notes

Microcode mismatch after upgrade

TN0971

Product: RP2, RP2.1, RA16BA, RV8, RM1, RM2
Version: > v80
Date Added: 2016-08-02

Issue

After updating to v84 TDT drivers (or above) and updating the microcode on the devices in your system, zBUSmon will show a mismatch (red lettering) and indicate the version number is 80 for the following devices: RP2, RP2.1, RA16BA, RV8, RM1, and RM2.

Workaround

The latest microcode version for these devices is v80. You can still use the "Update All Devices" command to update your system's microcode. The microcode installer can detect the device types and install the correct microcode according to the device type. In this case, you can safely use both microcode versions in your system as needed. You will see a microcode mismatch indicator (red lettering) for devices using v80, but you can disregard the warning indicator in this situation.

Solution

Upgrade to the latest version of TDT Drivers. The mismatch indicator no longer erroneously appears for these devices.

Modulation distortion in RP2

TN0094

Product: RP2
Version: ZB1 Serial numbers < 3000
Date Added: 2001-07-03

Issue

With an RP2 is mounted in the right hand slot of a zBUS device caddies with a serial number < 3000 (serial number is located on a sticker located in the left slot -- you will have to remove the left side module to check it) its output signals might be modulated by 50, 60, 100, or 120 Hz. This results in side bands in the signal that are -80 dB relative to the main signal.

Solution

To avoid this problem move the RP2 to the left-hand slot. You may also contact TDT for an upgrade to the zBUS.

Connecting the RP2 or Stingray (RL2) to a video camera or VCR

TN0093

Product: RP2, RP2.1, RL2
Version: All
Date Added: 2001-03-01

Issue

This Tech Note describes how to construct a cable for connecting the RP2 or Stingray (RL2) to a video camera or VCR. This will allow you to use these devices to control recording and playback.

Solution

In the diagram below, the numbers listed under RL2 and RP2 indicate the pin numbers on the digital inputs and outputs that should be connected to the LANC connector.

The codes for controlling these devices are not published anywhere. Hobbyists have figured them out, and it may take some work to get them to work with the RP2 and RL2.

For more information on how SONY LANC™ protocol works see: http://www.boehmel.de/lanc.htm

'G21K' is displayed in place of the RP2 in the zBusMon system diagram

TN0082

Product: RP2
Version: All
Date Added: 2003-05-02

Issue

Pin 12 on the RP2 digital I/O port is used for forcing a reset of the microcode. When a long (50' or more) cable is connected to the digital I/O port it may trigger pin 12. This causes the RP2's microcode to reset. "G21K" will be displayed in place of the RP2 in the zBusMon system diagram. The RP2 will not function correctly until the cable is removed.

Workaround

The pin on the cable that corresponds to pin 12 on the RP2 can safely be removed. This will keep the microcode from being reset unintentionally. Contact TDT Technical Support for assistance to make sure that only the correct pin is removed.

Random and intermittent failure of programmable devices

TN0065

Product: RP2, RX, RZ
Version: All
Date Added: 2002-11-27

Issue

The real-time processors can intermittently fail to boot if there is an external device connected to the Digital I/O port on the device.

Workaround

Remove any cable connected to the digital I/O on your processor before booting it up. Replace the cable once the device is fully booted.

Increased signal noise on DAC outputs when viewed with an oscilloscope

TN0064

Product: RP2, RX, RZ
Version: All
Date Added: 2002-12-17

Issue

An oscilloscope samples at a much higher rate than the processors run at. Users may see increased signal noise beyond the Nyquist frequency. If the sampling rate is set properly, the noise is above the hearing range of your subject and has insufficient power to have any physiological effect.

Workaround

Sample at a higher rate or filter the signal after it is sent from the device.

Important

If signal is acquired on another device, make sure that other device is running at a sampling rate at least as fast as your TDT processor to avoid aliasing artifacts.