Skip to content

OpenEx Tech Notes

OpenController parameters spontaneously reset

TN0982

Product: OpenEx, OpenController
Version: < 2.24
Date Added: 2016-08-03

Issue

Switching from standby Mode to Record may cause some Controller parameters to spontaneously reinitialize.

Solution

Upgrade to the latest version of OpenEx.

Timing issues with media players

TN0981

Product: RV2, OpenEx, Synapse
Version: All
Date Added: 2016-08-22

Issue

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.

Solution

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

Resized OpenController window is too small

TN0980

Product: OpenEx, OpenController
Version: < 2.24
Date Added: 2016-08-03

Issue

When OpenController is run, any floating Controller windows are resized automatically. The new size may be too small and scroll bars may overlap some controls.

Solution

Upgrade to the latest version of OpenEx.

Note Options menu not available in OpenScope

TN0978

Product: OpenScope, OpenEx, Synapse
Version: < OpenEx 2.24 / Synapse 84
Date Added: 2016-08-13

Issue

After opening an existing XSP file, the Note Options shortcut menu can't be displayed. When creating a new XSP file, the Note options are available, but changes can't be saved.

Solution

Upgrade to the latest version of OpenEx or Synapse.

Block List Empty when Tank is selected

TN0977

Product: TTankX, OpenEx, OpenDeveloper
Version: < 2.24
Date Added: 2016-08-02

Issue

When a Legacy tank is selected in a Tank Window, the BlockSelect window remains empty, making navigation and data extraction impossible. This may be caused by misidentified tank paths or tank type.

Solution

Upgrade to the latest version of OpenEx.

Can't read epoc timestamps from long recordings

TN0976

Product: TTankX, OpenEx, OpenDeveloper
Version: < 2.24
Date Added: 2016-08-02

Issue

In recordings with a duration of more than a day, epoc timestamps beyond about 24 hours can't be read in OpenScope or using GetEpocsV.

Solution

Upgrade to the latest version of OpenEx or Synapse.

OpenEx threshold settings lost on mode change

TN0967

Product: OpenEx, SpikePac
Version: All
Date Added: 2016-01-29

Issue

OpenEx/SpikePac threshold settings are lost when changing from preview to record mode.

Workaround

Instead of going directly from Preview to Record, change from Preview to Standby to Record. This gives Controller enough time to register the mode change and save/load the settings properly. This should keep your SpikePac threshold/sorting settings intact.

Experiment interrupted by Windows Update on Windows 10 PC

TN0964

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

Issue

Long or overnight experiments might be interrupted by Windows Update on PCs running Windows 10.

Workaround

In Windows 10, non-enterprise editions, Windows Update is set to automatic updates by default and the only way to inhibit updates is to disable the service.

Important

If you use this workaround, you will need to return to the Services regularly and turn it on to update your copy of Windows. To be able to install the newest updates, you must install each available update in turn, from oldest to newest. When your computer has no more updates to install, remember to turn off the Windows Update service again.

We don't recommend disabling automatic Windows Update in Windows 10 unless you are making long/overnight recordings or are experiencing problems with automatic updates.

To turn off Windows Updates:

  1. Right-click the Windows Start icon on the desktop.

  2. Click Control Panel.

  3. Click Administrative Tools.

  4. Click Services.

  5. In the Services window, scroll down then right-click the Windows Update process and click Properties.

  6. Next to Startup type, select Disabled.

  7. Click OK.

Group Policy

If your Windows 10 computer uses a Group Policy, you can also change some settings using the Group Policy Editor. Run gpedit and navigate to the following policy setting:

  1. Computer Configuration | Administrative Templates | Windows Components > Windows Update.

  2. On the right side, double-click Configure Automatic Updates and change its setting to suit your requirements.

Tank cache errors and timing

TN0963

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

Issue

OpenEx or Synapse stops recording and displays a "Trouble saving data to Tank" or "Tank unable to cache events" error message.

Solution

Errors related to data storage and timing can occur when saving high rates of data, your PC's hard drive is busy or full, or communication between your PC and your TDT system fails. To narrow the possibilities, look at the timestamp comparison located at the end of the error line in the messages window.

A timestamp comparison of:

  1. "-6.x vs 6" tells you that OpenWorkbench/Synapse can't store the data fast enough.

    1. If you don't need access to the tank data right away, increase the Cache Delay to the maximum (30 seconds). In OpenWorkbench, this option is found in File → Preferences menu. In Synapse, this option is found in Menu → Preferences → Advanced.

    2. Try increasing the Target Bus Loading setting to ~80%. This puts more resources towards storing the data and less on distributing it to applications that are viewing the data, like OpenController or the Synapse run-time interface. In OpenWorkbench, this setting is in the Setup → Polling and Performance menu. In Synapse, this setting is Menu → Preferences → Run-time Ops → Data Read Limit.

  2. "-18.x vs 6" (or similar, where the first number is ~3x larger than the second number) tells you there is a problem saving data to disk. This may be because:

    1. The hard drive is close to capacity or something else, like a virus scanner, is demanding heavy access.

    2. Check your hard drive storage capacity. If that is not the problem, try turning off auto virus scans, update, or other auto-process including Superfetch (aka prefetch) and Indexing. See Tech Note #0237 for more information on optimizing to avoid errors.

    3. The hard drive is failing.

      1. Tool to test hard drive can be downloaded here:

        http://crystalmark.info/download/index-e.html

        http://crystalmark.info/redirect.php?product=CrystalDiskInfo

      2. Note the following 5 best Self-Monitoring, Analysis and Reporting Technology (SMART) hard drive stats that indicate impending disk drive failure as reported by Backblaze:

        SMART 5 - Reallocated_Sector_Count
        SMART 187 - Reported_Uncorrectable_Errors SMART 188 - Command_Timeout
        SMART 197 - Current_Pending_Sector_Count
        SMART 198 - Offline_Uncorrectable

        SMART is a monitoring system included in computer hard disk drives (HDDs) and solid-state drives (SSDs) that detects and reports on indicators of drive reliability, with the intent of enabling the anticipation of predictable (40%) hardware failures.

        Any other values are usually indicative of a communication failure.

    4. Try reseating the fiber optic cables on both the RZ and PC sides. If errors continue to occur, contact Support.

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:

Using OpenEx clients across a network with Windows 7

TN0954

Product: OpenEx, OpenDeveloper, OpenController, OpenScope
Version: All
Date Added: 2015-04-28

Issue

Security settings must be modified on both the server and client computers to allow simultaneous access to a Workbench server running an OpenEx project from more than one computer.

Solution

Before software components distributed across networked computers can communicate with each other, several DCOM security settings must be modified on the server computer. The steps below ensure a client computer can access data from a registered new or legacy format tank located on a server computer.

In this example, the computer connected to the TDT hardware is named TDTServer. The computer that will run OpenController or TDevAccX remotely has a user account client1 with password password1.

Server Computer

Create a user account on the server computer:

  1. From the Control Panel, double-click Administrative Tools and then double-click Computer Management. If necessary, expand System Tools in the left panel and then expand Local Users and Groups.
  2. Right-click Users and select New User from the shortcut menu.

    The account user name and password MUST match the client computer's user name and password.

  3. In the New User dialog box, type the user name (client1) and password (password1) in the corresponding fields.

    Clear the User must change password at next logon check box and then select the User cannot change password and Password never expires check boxes.

  4. Click Create and then click Close.

This account must be an Administrator. To grant administrator privileges you must add that user to the Administrators group.

Add the user to the Administrators group:

  1. In the Computer Management window, under System Tools and then Local Users and Groups, click **Groups **in the left panel.

  2. In the window on the right, right-click the Administrators group and select Add to Group on the shortcut menu.

    The Administrators Properties window will open.

  3. Click the Add button. The Select Users, Computers, Service Accounts, or Groups window will open.

  4. Enter the user name in the Enter the object names to select field and click the Check Names button.

    Note

    If the user is not found, you may need to browse for a different location, using the Locations button.

    If the computer is on a domain, this step will have to be performed for both the local account and the network account.

    To change between the local machine and the network, click Locations and select either the machine or the network and click OK to return to the previous window.

  5. In the Select Users, Computers, Service Accounts, or Groups window Verify the spelling, and click OK.

  6. Close the **Computer Management **window.

  7. The Control Panel and Administrative Tools windows should still be open (if not, reopen now). Double-click **Component Services**in the panel on the left.

  8. Expand Component Services, expand Computers, right-click My Computer, and click Properties.

  9. In the My Computer Properties window, click the COM Security tab.

  10. Under Access Permissions, click the Edit Default button.

  11. Under Access Permissions in the My Computer Properties window, click the Add button. The Select Users, Computers, or Groups window is displayed.

  12. In the Enter the object names to select field, type client1.

  13. Click the Check Names button.

    Note

    If the user is not found, you may need to browse for a different location, using the Locations button.

  14. Verify spelling, then click OK.

  15. In the Access Permissions window, ensure the names SYSTEM, INTERACTIVE, and client1 are all present and all have Local Access and Remote Access permission.

    If any group names are missing, click Add to enter the group name.

  16. Click OK.

  17. Under Access Permissions in the My Computer Properties window, click the Edit Limits button and then click the Add button.

  18. In the Enter the object names to select field, type client1. Click the Check Names button, verify spelling, then click OK.

  19. In the Access Permission window, ensure the group names ANONYMOUS (or ANONYMOUS LOGON), Everyone, and client1 are all present and all have Local Access and Remote Access permission. If any group names are missing, click Add to enter the group name as before.

  20. Click OK. and return to the My Computer Properties window, COM Security tab.

  21. Repeat steps 10-20 under the Launch and Activation Permissions options.

Turn off the windows firewall:

  1. From the Control Panel, open Windows Firewall, and select the Off radio button.

  2. Click OK.

  3. From the Control Panel, double-click Administrative Tools, and then Component Services. Expand Component Services, expand Computers, expand My Computer, and double-click DCOM Config (you can click No if you are asked to record a registry value at this point).

  4. Right-click XpMaker and select Properties.

  5. On the Identity tab, ensure that The Interactive User is the account selected to run this application.

  6. Repeat steps 3 and 4 for TTankEng in the DCOM Config.

  7. After you finished making the security setting changes, reboot the server computer.

Client Computer

Test the communication link by pinging the server computer from the client computer and verifying the connection in OpenController.

To ping the server computer from the client computer:

  1. From the Start menu type cmd in the search box.

    Press the Enter key.

  2. A DOS command prompt opens, type ping TDTServer

  3. Verify that the server computer was reached and responded to the ping.

Add a registry entry with the user name and password of the client computer:

  1. From the Start menu type regedit in the search box, and press the Enter key. If a prompt for confirmation is display, click Yes.

  2. In the Registry Editor window, expand HKEY_LOCAL_MACHINE, SOFTWARE, Wow6432Node, TDT, and then TTank.

    Note

    For Windows 7 32-bit systems, expand HKEY_LOCAL_MACHINE, SOFTWARE, TDT, and then TTank.

  3. Right-click the EnumServers folder and select New String Value.

  4. Type the server name (TDTServer) as the Value Name and press Enter.

  5. Right-click the Value name and click Modify. Add the server name, user name and password for Value Data in the following form:

    TDTServer client1 * password1

    Important

    This is case sensitive and must include the asterisk and spaces

    After the entry is added, the registry should look like the example below:

    While Workbench is running on the server computer, test communication from the client in OpenController.

  6. Launch OpenController.

  7. In the Edit menu, click Window Property. The Setup Default Properties dialog will open.

  8. In the Default Server Name box, click the "..." browse button to view available servers.

    The server name that was entered in the registry is now available.

  9. Click TDTServer to highlight it, then right-click TDTServer, and click Test Connection on the shortcut menu.

  10. If the connection was successful, the following message dialog will be displayed:

  11. Click OK.

  12. Double-click TDTServer to select it as the default server for Controller.

  13. Click OK.

    You should now have access to the Workbench server running the TDT equipment just like you would if you were running Controller locally on that machine.

  14. On the client computer, launch OpenController.

  15. Add a ValueWatch control.

  16. Double-click the ValueWatch control and click the "..." browse button for the Source Target. The Select Target dialog will launch and display available targets as shown below. If this dialog is empty, or if you get an Access Denied error, try turning off User Account Control (UAC) on both machines, reboot and test again.

  17. If you are simultaneously accessing tank data while Workbench is recording, test tank communication from the client in OpenScope.

    1. Launch OpenScope.

    2. In the File menu, click Data Source to open the Select Tank dialog.

    3. Click the Server button to open the Select Server dialog.

    4. Repeat steps 8-11 to test communication and select the remote server.

TTank Engine sometimes stops recording

TN0950

Product: OpenEx
Version: 2.20
Date Added: 2014-12-23

Issue

On rare occasions, TTank engine stops storing data in OpenEx v2.20 on 64-bit operating systems. This typically occurs with very high channel count or high event count recordings.

In the Workbench Status window below, notice the Event Rate and Data Rate indicate a problem. Workbench continues to run and display data, but the data is no longer saved to disk.

Block data stored before the interruption can be recovered with the TankRestore utility. For a link to TankRestore and instructions on using this tool see Tech Note #0935.

Solution

Upgrade to the latest version of OpenEx. This was resolved in v2.20.1.

Selecting a block located in a read-only directory causes an error

TN0948

Product: OpenEx
Version: 2.20
Date Added: 2014-11-07

Issue

In v2.20 OpenEx, TNT files (.tnt) are created along with each new block. If you select a pre-existing block with no TNT file, OpenEx will create one. This fails if the block is read-only, which can often occur when reading from a network location.

Workaround

Obtain read-write access to the tank directory or select the block from a user account that has read-write access.

Solution

Update to the latest version of OpenEx. This issue was resolved in v2.24.

Tanks with spaces in the tank name or path cannot be registered

TN0947

Product: OpenEx
Version: 2.20
Date Added: 2014-11-07

Issue

File names or paths containing spaces are not recognized when OpenEx reads the list. The tank will not appear in the Tank List but can be found by browsing directly to the Tank file. Unregistering the tank does not clean up the registry file.

Workaround

Avoid using names or paths that include spaces.

If you've already mistakenly tried to register a tank with a name or path with spaces, you can manually clean up the registry file using a text editor.

The file is named EnumTanks.txt and its location in Windows 7 is

C:\Users\{username}\AppData\Local\TDT\EnumTanks.txt

IZ2Stim Plot Display Requirements

TN0944

Product: OpenEx, SpikePac, OpenController
Version: All
Date Added: 2014-07-30

Issue

The IZ2Stim control included with SpikePac uses OpenGL 2.0 plotting. The version of OpenGL on the end user's computer must be version 2.0 or greater.

If a compatible version of the graphics driver isn't found when the IZ2StimGen control is run, the waveform diagram will appear empty and an error message is displayed in the plot area: Hardware acceleration not available. Please check the graphics card.

Solution

OpenGL is typically installed with windows as part of the graphics adapter driver and/or the graphics card driver. If the computer is using an outdated graphics driver, updating it should resolve the problem.

To update your video driver:

  1. Open your Device Manager from the Windows Control Panel.

  2. Right-click the graphics card or display adapter and click Update Driver Software on the short-cut menu.

  3. Follow the onscreen instructions.

If updating the graphics driver does not resolve the problem, contact Support for assistance.

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.

Known Third Party Software Conflicts

TN0937

Product: OpenEx, RPvdsEx, Synapse
Version: All
Date Added: 2014-08-15

Issue

Some programs that make background memory calls on a PC create fatal errors and force TDT software, such as OpenEx or RPvdsEx, to shutdown.

Error Message: The TDT application may or may not give an error message, such as: The RPC server is unavailable.

Problem Behavior: Software crashes.

Known program conflicts:

  1. HP Security Manager (Tech Note #0908)

  2. CrashPlan Backup Software on Windows 7

  3. Dell Data Protection

Solution

Remove or disable the software causing the conflict.

The Microsoft Process Explorer (found here: http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) can be a useful tool for determining the source of the conflict.

Restoring a corrupted block of data in an OpenEx data tank

TN0935

Product: OpenEx, Synapse
Version: All
Date Added: 2014-08-04

Issue

If a block is damaged or corrupted, the stored data may not be selectable. The block name may be visible in the Tank window, but no events/stores will be listed, and data cannot be exported or plotted.

Solution

For 64-bit machines or files larger than 2-3GB, download and run: TankRestore64.exe

For 32-bit machines, download and run: TankRestore32.exe

The Data Tank Utilities window launches:

  1. Click Next.

  2. Choose your Tank and Block then click Next.

    Note

    If you can't select the corrupted block, move the corrupted block into an empty tank and try again. Sometimes the corrupted blocks will not display correctly in a list.

  3. Under Modify Tank, select Re-create Index File and click Next.

The operation should complete in under a minute. This makes a backup copy of the TBK file (if it exists) and then creates a new one based on the block data. You should be able to access your data after this operation.

Unable to Assign RCO to a device in OpenWorkbench

TN0923

Product: OpenEx
Version: <= 2.16
Date Added: 2013-05-20

Issue

Attempting to assign an RCO to a device using the shortcut menu (right-click) in the device diagram in OpenWorkbench, generates the warnings below and fails to assign the file to the device.

Warning: 'Cannot locate file XXX.rcx to import, file is not copied to current project.'

Alert: 'XXX.rcx does not exist, do you want to clear the setup of the selected device?'

Workaround

Use an alternate method of Assigning the RCO: Select the device in the diagram and then click the Browse '...' button to choose a circuit.

Solution

Upgrade to the latest version of OpenEx.

Registered Tanks are missing or locked

TN0919

Product: OpenEx
Version: v 2.18 and below
Date Added: 2013-05-20

Issue

In the OpenEx environment, Data Tanks may be registered or unregistered. Only registered tanks appear in the Tank browser window used by most OpenEx applications (TTankInterfaces). In Windows 7, the current user account determines the location where the tank registration information is stored. As a result, tanks registered by other users may not appear in the TTankInterfaces window when browsing for "registered" tanks.

Demonstration Tanks provided by TDT appear regardless of user account because they are registered in a location that requires administrator privileges to modify. Therefore, they can only be "unregistered" by users who run the application as an administrator. Also, because the user tank list and TDT Demo Tank lists are kept separate but visible, it is possible to register a tank with the same name as a Demo Tank. When accessing that data, it will not be obvious which underlying tank is actually being accessed.

Workaround

If your group needs all users to have access to the same list of registered Tanks, you will need to use a shared user account. To avoid confusion with Demo Tanks, do not register a tank called Demotank or Demotank2.

Solution

Upgrade to v2.20 or above. In v2.20 or above, each user sees the demo tanks and each user can unregister them independently if they wish.

Selecting a block in OpenEx does not show events

TN0916

Product: OpenEx
Version: All
Date Added: 2013-04-16

Issue

If selecting a block does not display the event in the block, the block index may have been corrupted. Showing block details and then selecting the block again might show events from the previous block.

Solution

Although the index may have been corrupted the data is typically still intact. See Tech Note #0935 for more information.

TTankInterfaces improperly opens legacy tanks

TN0914

Product: OpenEx, OpenDeveloper
Version: 2.16
Date Added: 2013-01-17

Issue

When a new legacy tank is selected in TTankInterfaces, the tank name has a '.tbk' appended to it. When you try to access that tank, it fails saying it couldn't find it.

Solution

Upgrade to the latest version of OpenEx.

RPvdsEx crashes when used with OpenEx

TN0908

Product: OpenEx, RPvdsEx
Version: All
Date Added: 2012-10-16

Issue

Some security programs confuse third-party software background memory calls with fatal errors and force shutdown the program either without giving an error message or giving the message "The RPC server is unavailable."

On some, but not all HP computers, the HP Security Manager will allow RPvdsEx to work without error in standalone mode but will not allow circuits to open when RPvdsEx is attached to OpenEx. Microsoft support has identified this issue and offered the following solution.

Solution

To resolve this issue, you must disable a DLL for the HP Security Manager. To do this:

  1. Browse to C:\Program Files (x86)\Hewlett-Packard\HP ProtectTools Security Manager\Bin.

  2. Locate the DpFbView.dll file and rename the file, changing the extension from .dll to .old.

Relocated tanks not recognized by TTankInterfaces

TN0907

Product: OpenEx, Synapse
Version: All
Date Added: 2012-09-19

Issue

TTank is the database server used by OpenEx and Synapse to store data. Data is stored as groups of blocks inside of specified tanks. Each block consists of a set of files that share the block name (.Tbk, .Tdx, .Tev, .Tsq, etc) while an additional file is always 'desktop.ini'. Each tank is a root folder for a group of blocks and has a 'desktop.ini' file. The 'desktop.ini' file is a necessary hidden system configuration file that TTankInterfaces uses to determine if a folder is a valid block or tank.

Because it is hidden, it is often overlooked by Windows during the relocation of bulk file sets.

Note

TTankX, TDT2mat, and TDTbin2mat do not use .ini files to access tanks and blocks.

Solution

To properly move blocks and tanks, you must include the desktop.ini file:

To ensure the desktop.ini file is included when you move block and tanks, you'll need to configure the Folder Option prior to moving the folders. To do this, make sure Show hidden files and folders is set true (checked) and Hide protected operating system files is set false (unchecked).

To enter Folder Options in Windows 7, select the Organize tab in Windows Explorer and then Folder and search options.

The Show hidden files, folders, and drives option and Hide protected operating system files options are listed under the View tab of the Folder Options dialog.

Note

If you have already moved your files and cannot easily recopy them, the linked Tank and Block desktop.ini files can be used by unzipping and copying them into the proper folders.

Sometimes when moving files from a network location, Windows sets the file attributes such that TTankInterfaces can't read the ini file to see if it is a valid tank; it shows a regular folder icon instead of the tank icon. TTankInterfaces v2.14 corrects this attribute issue for you automatically. For prior versions of OpenEx, you can fix this on the command line by setting the read attribute for the block folder like this:

C:\> attrib +r C:\TDT\OpenEx\Tanks\DEMOTANK2\Block-1\

Store Pooling does not work correctly with Slow_Store_MC macro

TN0882

Product: OpenEx, RPvdsEx
Version: < 72
Date Added: 2010-10-15

Issue

When using Store Pooling with the Slow_Store_MC macro, channels of the higher pool members will be identical to the lower pool members.

Solution

Upgrade to the latest version of TDT Drivers and OpenEx. This issue was resolved in version 72.

Erroneous 2-sample delay in Epoc_Store_With_Offset timestamp

TN0877

Product: OpenEx, RPvdsEx
Version: < 72
Date Added: 2010-10-07

Issue

When using the Epoc_Store_With_Offset macro, the onset timestamp is delayed by two samples. This can cause the onset to appear to have occurred two samples before it actually did and will not by synchronized with other Epoc_Stores in the circuit.

Solution

Upgrade to the latest version of TDT Drivers and OpenEx. This issue was resolved in v72.

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

TN0837

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

Issue

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

Workaround

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.

Solution

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

TN0836

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

Issue

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.

Solution

Upgrade to OpenEx version 2.10 or later.

Legacy Tank Blocks aren't displayed -- if Registered, non-Legacy tank icon is displayed

TN0280

Product: OpenEx
Version: > 1.9
Date Added: 2008-03-20

Issue

Legacy tanks cannot be stored inside a folder with the same name.

The legacy tank will appear in the list when browsing using the TankSelect dialog, however, no Blocks will be listed in the corresponding BlockSelect dialog (e.g. in OpenScope). If that tank is Registered, the icon changes from the typical Legacy tank icon (blue cylinder) to the non-Legacy tank icon (yellow cube) and the Blocks remain unavailable.

Workaround

Do not place a Legacy tank into a folder with the same name as that tank.

Plots in Controller or Scope do not display data

TN0277

Product: OpenEx
Version: All
Date Added: 2008-02-15

Issue

Plots in OpenController or OpenScope might not display any data even though the plot appears to be configured correctly. This issue commonly arises when an RCO file assigned to inactive device in OpenWorkbench uses the same StoreID as the active RCO file.

When devices, or device configurations, are created in OpenWorkbench, the StoreIDs contained in the assigned RCO are added to a master list that is used by other OpenEx applications (such as OpenController) to retrieve data. This list of StoreIDs does not include information about which device configuration contained the StoreID, so they will remain in the list even when a device configuration is inactive (or not assigned to any hardware device).

In OpenWorkbench, multiple device configurations can be created using the same or different RCOs, any of which might include duplicate StoreIDs. Workbench will warn the user if two active devices include the same StoreIDs (see Tech Note #0271 for more information), but no error is reported when the duplicate StoreID is contained in an RCO assigned to an inactive device configuration.

In the image below, device Acq3 is currently enabled and loaded with an RCO file that contains a store with the tag name 'eNeu'. Device configurations ~Acq1 and ~Acq2 are currently disabled and are loaded with RCO files that also contain the StoreID name 'eNeu'.

Once OpenWorbench is running, duplicate instances of the eNeu StoreID will occur and client applications like OpenController may point to an inactive StoreIDs rather than the active one.

Solution

To avoid this problem, delete inactive device configurations or ensure all Stores use a unique StoreID.

OpenWorkbench locks up when an .rcx files is loaded to a device

TN0270

Product: OpenEx
Version: 2.6
Date Added: 2007-10-26

Issue

Some *.rcx files cause OpenWorkbench to lock up when loaded to a device.

Solution

Update to the latest version of OpenEx.

OpenWorkbench plot is unresponsive

TN0264

Product: OpenEx
Version: 2.6
Date Added: 2007-09-13

Issue

If the number of unique store names exceeds 24, the OpenWorkbench plot window will fail to generate plots. It will be blank with a static time axis.

Workaround

Reduce the number of stores or contact TDT to request an interim release.

Solution

Update to the latest version of OpenEx.

OpenEx fails when used with a system with a PA5

TN0242

Product: OpenEx
Version: 2.0 and 2.2
Date Added: 2007-02-27

Issue

OpenEx Workbench versions 2.0 and 2.2 fail sporadically when used with a system having a PA5. Symptoms include displaying ??:??:?? for the record Time display when the project is running, some data stores not saving events, and zBusA trigger not being set.

Solution

Update to the latest version of OpenEx.

Invalid Store names cause filtering errors

TN0239

Product: OpenEx
Version: All
Date Added: 2007-02-14

Issue

Store names must not start with any of the following characters:

character description
- hyphen
= equal sign
( open parenthesis
) close parenthesis
< less than symbol
> greater than symbol
! exclamation point
a space
0-9 Any numeric characters

In OpenExplorer, this will generate an error message:

  • Unable to set cell filter.

  • TTank server Error.

  • Server Call: SetQueryCondition

  • Error:Invalid filter format

With OpenDeveloper TTankX, the following command is none to fail under these conditions:

  • SetFilterArray will return 0.

Note

There are likely other filtering type commands that will fail or not work properly.

Solution

Always use letters a-z and A-Z for the first character of Store names.

Running OpenEx at high data transfer rates. Optimize to avoid errors

TN0237

Product: OpenEx
Version: All
Date Added: 2007-02-02

Issue

When operating OpenEx at higher data rates (generally 16 channels or more) measures should be taken to improve overall system performance and efficiency. The system is optimized via modifications to the OpenEx project and its Stores and by terminating unnecessary applications running on the host PC.

The following list of guidelines can be used to optimize system performance.

OpenEx

  1. In OpenWorkbench, set the Cache Delay preference to 6.0 seconds and ensure the Flush read when overload preference is NOT enabled. To check or modify these values, click File → Preferences in the OpenWorkbench window.

  2. Turn off all unnecessary scrolling plots within Workbench. To turn off individual plots, right-click the plot and click Hide.

  3. Run each device/RCO in your OpenEx project at the lowest acceptable overall sample clock rate. For example, if you're collecting EEG type signals you should set the device sample rate to no more than 6 kHz.

  4. Ensure a reasonable sample rate is being used for each Store in your project and use 16-bit or even 8-bit data for Stores whenever possible.

  5. Remove any redundant data Stores. For example, if you are storing the full 25 kHz bandwidth signals in your single unit collection project, there is no need to also store a band-limited LFP version of these sample signals.

  6. In Workbench Setup → Polling and Performance, set the Target Bus Loading to 80%. This places more priority on storing the data versus distributing it to other applications, such as OpenController.

Operating System

  1. Turn off unnecessary applications including

    1. Background applications like anti-virus, firewall and spyware detection tools

    2. Services that run in the background even if you do not have the program open, including Superfetch, Prefetch, and search Indexing.

  2. Turn off any automatic update features.

  3. Avoid launching applications once data collection has started in OpenEx.

  4. Avoid doing other tasks on the collection computer while it's running OpenEx (like accessing the Internet)

  5. If you have USB or the Wired Gigabit interface, consider upgrading to the Optical Gigabit Interface.

If you need assistance with any of the above design guidelines, please contact TDT technical support.

Server Busy error with large blocks in OpenEx 2.0

TN0232

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

Issue

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

Solution

Upgrade to latest version of OpenEx.

Using an OpenEx client across a network with Windows XP

TN0231

Product: OpenEx, OpenDeveloper, OpenScope, OpenController
Version: All
Date Added: 2006-12-20 (updated 2011-09-13)

Issue

Security settings must be modified on both the server and client computers to allow simultaneous access to a Workbench server running an OpenEx project from more than one computer.

Solution

Before software components distributed across networked computers can communicate with each other, several DCOM security settings must be modified on the server computer. The steps below ensure a client computer can access data from a registered new or legacy format tank located on a server computer.

In this example, the computer connected to the TDT hardware is named TDTServer. The computer that will run OpenControlleror TDevAccX remotely has a user account client1 with password password1.

Server Computer

Ensure that simple file sharing is disabled:

  1. Open a My Computer window.

  2. On the Tools menu, click Folder Options. Click the View tab.

  3. Under Advanced Settings, scroll down, and clear the Use simple file sharing (Recommended) check box.

  4. Click OK.

Create a user account on the server computer:

  1. From the Control Panel, double-click Administrative Tools, and then Computer Management.

  2. Expand System Tools, and then Local Users and Groups.

    Right-click Users and select New User from the shortcut menu.

  3. The account user name and password must match the client computer’s user name and password.

    Type the user name (client1) and password (password1) in the corresponding fields.

  4. Clear the User must change password at next logon check box, and select the User cannot change password and Password never expires check boxes.

  5. Click Create and then click Close.

This account can be a limited user account.

Give the user Local and Remote access:

  1. From the Control Panel, double-click Administrative Tools and then Component Services.

    Expand Component Services, expand Computers, right-click My Computer and click Properties.

  2. In the My Computer Properties window, click the COM Security tab.

  3. Under Access Permissions, click the Edit Default button and then click the Add button.

    The Select Users, Computers, or Groups window is displayed. In the Enter the object names to select field, type client1. Click the Check Names button, verify spelling, then click OK.

  4. In the Access Permissions window, ensure the names SYSTEM, INTERACTIVE, and client1 are all present and all have Local Access and Remote Access permission.

    If any group names are missing, click Add to enter the group name as before.

    Click OK.

  5. Under Access Permissions in the My Computer Properties window, click the Edit Limits button and then click the Add button.

    1. In the Enter the object names to select field, type client1.

    2. Click the Check Names button, verify spelling, then click OK.

    3. In the Access Permission window, ensure the group names ANONYMOUS (or ANONYMOUS LOGON), Everyone, and client1 are all present and all have Local Access and Remote Access permission. If any group names are missing, click Add to enter the group name as before.

    Click OK.

  6. Under Launch and Activation Permissions in the My Computer Properties window, click the Edit Default button and then click the Add button.

    1. In the Enter the object names to select field, type client1.

    2. Click the Check Names button, verify spelling, then click OK.

    3. In the Launch Permission window, ensure the group names SYSTEM, INTERACTIVE, and client1 are all present and all have Local Launch, Remote Launch, Local Activation, and Remote Activation permission. If any group names are missing, click Add to enter the group name as before.

      Click OK.

  7. Under Launch and Activation Permissions in the My Computer Properties window, click the Edit Limits button and then click the Add button.

    1. In the Enter the object names to select field, type client1.

    2. Click the Check Names button, verify spelling, then click OK

    3. In the Launch Permission window, ensure the group names Administrators, Everyone, and client1 are all present and all have Local Launch, Remote Launch, Local Activation, and Remote Activation permission. If any group names are missing, click Add to enter the group name as before.

      Click OK.

Turn off the windows firewall:

  1. From the Control Panel, open Windows Firewall, and select the Off radio button.

  2. Click OK.

Select The Interactive User account to run the client application:

  1. From the Control Panel, double-click Administrative Tools, and then Component Services.

  2. Expand Component Services, expand Computers, expand My Computer, and double-click DCOM Config (you can click No if you are asked to record a registry value at this point).

  3. Right-click XpMaker and select Properties.

  4. On the Identity tab, ensure that The Interactive User is the account selected to run this application.

  5. If you would like to simultaneously access the tank data file that is recording in OpenEx through TTankX or OpenScope,repeat steps 11 and 12 for TTankEng in the DCOM Config.

  6. After you finished making the security setting changes, reboot the server computer.

Client Computer

Test the communication link by pinging the server computer from the client computer and verifying the connection in OpenController.

To ping the server computer from the client computer:

  1. From the Start menu click Run, type cmd, and click OK.

  2. In the DOS command prompt that opens, type:

    ping TDTServer

  3. Verify that the server computer was reached and responded to the ping.

Add a registry entry with the user name and password of the client computer:

  1. From the Start menu click Run, type regedit, and click OK.

  2. In the Registry Editor window, expand HKEY_LOCAL_MACHINE, SOFTWARE, TDT, and then TTank.

  3. Right-click the EnumServers folder and select New String Value.

  4. Type the server name (TDTServer) as the Value Name and type the user name and password for Value Data in the following form:

    * client1 * password1

    Important

    This is case sensitive and must include the asterisk and spaces

  5. After the entry is added, the registry should look like this example below:

  6. While Workbench is running on the server computer, test communication from the client in OpenController.

  7. Launch OpenController.

  8. In the Edit menu, click Window Property. The Setup Default Properties dialog will open.

  9. In the Default Server Name box, click the "..." browse button to view available servers.

  10. The server name that was entered in the registry is now available.

    Click TDTServer to highlight it, then right-click TDTServer, and click Test Connection on the shortcut menu.

  11. If the connection was successful, the following message dialog will be displayed:

  12. Click OK.

  13. Double-click TDTServer to select it as the default server for Controller.

  14. Click OK.

    You should now have access to the Workbench server running the TDT equipment just like you would if you were runningController locally on that machine.

  15. If you are simultaneously accessing tank data while Workbench is recording, test tank communication from the client in OpenScope.

    1. Launch OpenScope.

    2. In the File menu, click Data Source to open the Select Tank dialog.

    3. Click the Server button to open the Select Server dialog.

    4. Repeat steps 10 - 12 to test communication and select the remote server.

RZ fails to run circuit in OpenWorkbench

TN0216

Product: RZ, OpenEx
Version: All
Date Added: 2006-09-18

Issue

Because the RZ does not support sample clock synchronization, a project will fail to run if the Synchronize Sampling Clocks Preference is selected in OpenWorkbench.

Solution

In the OpenWorkbench Preferences dialog box, ensure the Synchronize sampling clocks check box is not checked when using the RZ2, RZ5 or RZ6.

When selecting a control circuit outside a project's local directory, the local copy of the control circuit is not used

TN0214

Product: OpenEx
Version: 2.0
Date Added: 2006-09-15

Issue

When a control circuit is not located in the project's local RCOCircuits directory and the user must browse outside the local directory, a local copy is created within the project's RCOCircuits folder (this local copy behavior is controlled by a preference within OpenProject). In version 2.0, the control circuit file path seems correct and a local copy is generated, however, the project is still pointing to and using the original browsed version of the circuit. Therefore, changes made to the local copy of the circuit have no effect.

Workaround

Browse to the desired file as normal then reselect the automatically generated local copy of the file from the local RCOCircuits directory.

Long recordings interrupted by antivirus utilities

TN0211

Product: OpenEx, Synapse
Version: All
Date Added: 2006-08-21

Issue

Many antivirus programs, such as Symantec Norton Antivirus, automatically scan the hard drives on the PC at fixed times. As a result, antivirus software may interrupt long recordings.

Solution

Communication to the PC controlling the TDT hardware should be limited to pertinent applications during data acquisition. We strongly recommend closing unrelated programs and disabling virus protection during data acquisition. Once an acquisition is stopped users can then access other applications.

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

TN0194

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

Issue

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

Workaround

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.

Important

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

Unable to register or unregister tanks in Tank Monitor/Debugger or OpenEx data storage interfaces

TN0176

Product: OpenEx
Version: All
Date Added: 2005-05-06

Issue

In version 2 and above, users that do not have administrator privileges will not be able to register or unregister tanks in TankMon, the Data Storage dialog (OpenWorkbench), the Tank Navigator pane (OpenScope) or the Select Tank dialog (OpenBrowser). These OpenEx operations modify the registry on your Local Machine (that is, the PC on which you run the application). Windows requires that users have administrator level privileges to modify the Local Machine registry.

In v 1.57 and below, a "Cannot delete tank. No error to report" or "Cannot add tank. No error to report" error message will be displayed whenever a user attempts to add or remove a tank.

Workaround

Ensure that all users have administrator level access.

'Access to path and application was denied' error message

TN0122

Product: OpenEx, BrainWare
Version: All
Date Added: 2004-06-15

Issue

If you are using the Windows XP or Windows 2000 operating system and you do not have administrator privileges, an "access to path and application was denied" error message will be displayed when attempting to run an OpenEx project or when exiting BrainWare. Both BrainWare and OpenEx modify the registry on your Local Machine (that is, the PC on which you run the application). Windows requires that users have administrator level privileges to modify the Local Machine registry.

Workaround

Ensure that all users have administrator level access.

'Cannot locate path: ..... Copy project failed.' error

TN0114

Product: OpenEx
Version: All
Date Added: 2004-02-13

Issue

The OpenProject Save As command will not copy a project to an unmapped network drive. A message such as "Cannot locate path: ... Copy project failed" will be displayed.

Workaround

Use Windows' Map Network Drive feature to assign a drive letter to a shared network folder or manually copy the whole project to the destination folder. When copying projects manually, keep in mind that tank files should not be copied or moved.

Only one SigGen Engine control can be created in OpenController

TN0077

Product: OpenEx
Version: All
Date Added: 2003-03-25

Issue

Only one SigGen Engine control can be created. A second one cannot be added even if the existing control is deleted.

Workaround

Currently only one SigGen Engine control can be used. If a SigGen Engine control is deleted, restart OpenController before attempting to add a new SigGen Engine control. Restarting should allow you to add a single SigGen Engine control.