Skip to content

OpenExplorer Tech Notes

OpenExplorer export data is empty


Product: OpenExplorer
Version: 2.16
Date Added: 2012-12-26


Data exported from plot windows is missing. The CSV file contains headers, but the data is all zeros.


Upgrade to the latest version of TDT Drivers, OpenEx, and OpenExplorer.

Events read from the tank are missing if there is a gap in the data


Product: OpenSorter, OpenExplorer, OpenDeveloper, OpenBrowser, OpenBridge
Version: All
Date Added: 2012-10-17


In order to save time, the TTank server will stop searching for data that matches the requested criteria if there are no matches in the last 1 million events. If the data is sparse and there is a large gap, the data after the gap might not be extracted.


Note: This solution is only valid in v2.16 and above.

To override the search limiting feature and force the tank to search the entire block for data on each channel, you must manually enter a registry key:

  1. Run the Registry Editor (regedit.exe).



    For 64-bit machines, the registry path is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TDT\TTank

  3. Right-click the right pane, point to New and click DWORD (32-bit) Value on the shortcut menu.

  4. Name the new entry SEARCHLIMIT.

  5. Right-click SEARCHLIMIT and click Modify on the shortcut menu.

  6. Enter a Value data of 1.

  7. Click OK.

  8. The TTank server will now search until the end of the block for events instead of performing a quick search.

To restore default behavior:

  1. Use the Registry Editor to browse to the SEARCHLIMIT DWORD (32-bit) Value you created and delete the entry or set to 0.
'Subscript out of range' error message appears when setting a TimeRef epoch


Product: OpenExplorer, OpenScope, OpenBrowser
Version: All
Date Added: 2009-11-24


When setting a TimeRef epoch a "Subscript out of range" error message appears:

This error message is likely to occur when you have more than 10 epocs in a block under the following conditions:


  1. when setting a TimeRef epoch for a Histogram plot.


  1. when setting a TimeRef epoch for a Histogram plot.

  2. when setting a TimeRef epoch for a Raster plot.

  3. when setting "Source Name X-Axis" for Feature plot.

  4. when setting "Refresh Epoc Name" in Activity plot.


  1. when setting a TimeRef epoch.


Manually type the epoc name into the field.

OpenExplorer may display erroneous Spike counts


Product: OpenExplorer
Version: All
Date Added: 2009-01-29


When plot data is refreshed or if the plot is right-clicked while spike data are being loaded, events may be counted multiple times on several channels.

This is a difficult issue to observe since the actual number of events on a channel is not often known. Spikes that occur later in the tank are most likely to be counted multiple times. This is primarily a problem with slow PC's or large data sets. Plots affected by this issue include: Piled, Activity, Feature, and Histogram.


Reload the data by clicking refresh once. This will reload the spike data.


Do not click refresh or right-click the plot until all spike data has been loaded. Loading is finished when the progress bar fills up, shows the text 100%, and then disappears.

Using the Gigabit interface with 32-Bit versions of Windows Vista or Windows 7


Product: TDT Drivers, OpenEx, OpenDeveloper, OpenExplorer, OpenSorter
Version: 70
Date Added: 2008-08-15


After performing a typical installation of the TDT Drivers, running RPvdsEx results in an error message which states "Error loading component specification file: CmpSpec.txt". Or, if you launch zBUSmon, you will see "NO TDT card Detected."


32-bit versions of Windows Vista or Windows 7 can be used with some adjustments to security settings and program compatibility settings. This procedure has proved successful for running OpenEx with a Gigabit interface.

Configuring 32-bit versions of Windows Vista or Windows 7 for TDT software installation

  1. First, you must be using an Administrator account.

    Turn off the User Account Control (UAC) for the account that will be used to install the applications.

    The option to turn this on or off is seen when viewing the details of your user account.

  2. Download the software installation packages from the web from here: V70 software installation packages Contact TDT to request passwords for applications you have purchased.

  3. Edit the properties of the *.EXE installation files. Under the Compatibility tab, click the Run this program in compatibility mode for: checkbox and choose Windows XP (Service Pack 2) in the dropdown.

  4. Run the install packages as normal. Start with the TDT Drivers and reboot when asked. Install OpenEx before installing OpenDeveloper, OpenExplorer or OpenSorter.

Hardware Installation

Windows will recognize your hardware when it is first installed. When prompted, let windows search for drivers automatically. If you have any further difficulty, contact TDT Support.


Upgrade to Optibit Interface (FO5 with PO5/PO5e/PO5c/UZ3) and the latest version of TDT software. Current drivers are also compatible with the 64-bit USB Interface.

The number of events returned is less than expected when applying both epoch value filtering and epoch time filtering


Product: OpenEx, OpenExplorer, OpenDeveloper
Version: 2.6, 2.8
Date Added: 2008-08-06


This issue is known to occur in OpenExplorer and OpenDeveloper when using epoch value filters as well as an epoch time filter but might occur in other OpenEx clients that access and filter data. The overall time range of events could be limited erroneously, resulting in events returned for only a fraction of the total desired time range.

For example, you have a block of data that includes spike snippets and epochs storing stimulus parameters. You apply value filters to the epoch stimulus events while also applying an epoch time filter to the snippet data before reading back the spike events. Your data is known to have good epoch conditions spanning timestamps from 0 to N seconds and spike events timestamped in the range from 0 to N seconds. After applying both epoch value and time filters, the number of events returned reduces drastically and the query appears to miss events that should be returned, with maximum timestamps of the spike events being much less than N seconds.


Upgrade to OpenEx version 2.10 or later.

Accessing User SortIDs in OpenExplorer


Product: OpenExplorer
Version: All
Date Added: 2008-01-24


In OpenExplorer, to plot or filter data using SortIDs generated in OpenSorter, drag the SORT event to the Control Panel then in the Control Configuration, select the desired sort in the SortID drop down list.

You must select the desired SortID in the SortID drop down list even if you used the OpenSorter Sort event to create the plot.

See Adding a SortID Filter in the OpenExplorer User's Guide for more information.

Server Busy error with large blocks in OpenEx 2.0


Product: OpenEx, OpenExplorer, OpenDeveloper
Version: 2.0
Date Added: 2007-01-07


"Server Busy" error occurs when accessing large blocks in OpenScope or other TDT applications. The *.tdx tank file will grow each time the block is accessed by OpenScope or other TDT applications. This is especially problematic with blocks that have a lot of epoc events.


Upgrade to latest version of OpenEx.

Problems connecting to TTankEngine to access tank data from a network computer


Product: OpenEx, OpenExplorer, OpenDeveloper
Version: All
Date Added: 2005-08-25


Security settings need to be modified on both the server and client computers if the user desires simultaneous access to a data tank from more than one computer. See


If it is necessary to access a data tank across a network, you can map the networked PC's hard drive or folder to a 'drive' letter on the local PC. After the drive is mapped and the tank is registered on the local PC, you will be able to access the data as if it were stored on the local PC.

To map network drives on your computer, go to My Computer and select Map Network Drive from the Tools menu. A dialog will help you connect to a shared network folder and assign a drive letter to the connection.


When using OpenDeveloper to initiate a connection to a tank server using the TTankX handle, the ServerName argument for the ConnectServer call should be 'Local'.