Skip to content

OpenBrowser Tech Notes

OpenBrowser export issues


Product: OpenBrowser
Version: All
Date Added: 2014-12-05


Many users find OpenBrowser functionality limited or experience errors during exporting, such as "ERROR: Internal function ParseEv() failed."


TDT recommends OpenBridge for data exports. It is available to OpenEx users on the Downloads page of the TDT website:

OpenBrowser ASCII export columns out of order


Product: OpenBrowser
Version: <= 2.16
Date Added: 2013-05-22


ASCII data is not in the correct column, particularly when using epoch filters.


Upgrade to the latest version of OpenEx

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.
Out of Memory error for large data sets in OpenBrowser


Product: OpenBrowser
Version: < 2.12
Date Added: 2010-11-10


When the OpenBrowser plot is refreshed, the entire data set is loaded into memory. For large data sets (larger than ~500MB) this can frequently cause Out of Memory errors that force OpenBrowser to close.


In the menu, select View > Data View Table. This will turn the plot off and show a data table of timestamps, which uses less memory.


This was fixed in v2.12. Upgrade to v2.12 or above.

'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.

Channel numbers out of order when exporting to an ASCII file from OpenBrowser


Product: OpenBrowser
Version: All
Date Added: 2005-05-13


When exporting streaming data to ASCII format from a tank in OpenBrowser, the channel numbers may be out of order.


This problem can be remedied by either exporting channels one at a time and then concatenating the files or, by slightly altering your analysis program to account for the channel number order.

Problems exporting to NEV


Product: OpenBrowser
Version: 1.54 - 2.18
Date Added: 2004-03-02


Although OpenBrowser included an export function for the .NEV file format, this export function did not work correctly and was eventually removed.Note: Users who wish to export data for use with Plexon's Offline Sorter should use the latest version of OpenBridge.

Some blocks of data do not appear in OpenScope and OpenBrowser


Product: OpenBrowser, OpenScope
Version: All
Date Added: 2003-06-04


When using oxBuffers or oxSnippets with large block sizes (greater than 5000), some blocks of data do not appear in OpenScope and OpenBrowser.


All blocks of data are still correctly stored in the tank, so the data can be exported and used with other software. If possible, keep block sizes smaller than 5000.


Use the provided storage macros.