Contact Neuralynx Support

If you have a product that you need to return for repair or replacement, first please contact a Neuralynx Support representative using contact info above.

To expedite the return of your product, a Neuralynx Support representative will provide you with an RMA number and return packaging and shipping instructions. Sales & Support will notify you when your repaired/replacement product is being shipped back to you.

Note: All RMAs are returned to and repaired at Neuralynx Headquarters in Bozeman, Montana, USA.

Ship authorized return to:

Neuralynx, Inc.
Attn: RMA# xxxxx-xxx
105 Commercial Drive
Bozeman MT 59715
406-585-4542

Cheetah 32 Driver

Version: 6.7.4
Drivers for Cheetah 32 acquisition card.


Cheetah 160 and Digital Lynx Drivers

Version: 4.2.4.3
Drivers for use with both Cheetah 160 and Digital Lynx 4/10S acquisition systems.


Instacal

Version: 6
Software and drivers for use with the L8-ACP, L8-ACP-USB, and Measurement Computing digital I/O add-on cards. Please choose the appropriate download to work with your installed Cheetah version.


Digital Lynx Firmware Update

Version: 2.1.0
Firmware update for Digital Lynx SX. Before updating to this firmware, you must update your acquisition software to Cheetah 6.1 or newer. Firmware V1.3.0 is required for Cheetah 5.6 and 5.7. Please contact support@neuralynx.com with any questions.


General Questions

How can I see the sampling rate of my recordings?

You can view the Header (which has a lot of information regarding the recording session) with Notepad (or something similar), Neuraview (Data Properties-select desired acq ent) or with Matlab.

CSC sampling rate equation: fs=512/(TS2-TS1)

What is Netcom?

NetCom is an application programming interface (API) library that you can use to create your own custom programs to monitor and control Cheetah. Netcom adds the ability to leverage multiple programs on multiple PCs to both monitor and control your experiment. Please see this page for more information.

While the NetCom server is embedded within Cheetah, you create the client using the NetCom API. This requires that you have some programming knowledge in a language that is supported by NetCom: C++/MFC, .NET (e.g. C#, VB.NET, etc), any .NET aware application such as LabView, and Matlab.

Where do I find information on how to use Cheetah?

When Cheetah 5 was released, we created the Cheetah Reference Guide. The guide provides a full-text search to show you just what you are looking for. It has been updated with every Cheetah release since 5.0.0 and will continue to be the source for all information about Cheetah. The Cheetah Reference Guide should be the first place you look for any questions you have about using Cheetah. If you can’t find what you are looking for, let us know and we will update the reference guide for the next Cheetah release.

For those of you who just want a brief introduction to Cheetah, we created the Cheetah Quickstart. This file is located in the Cheetah5 Start Menu folder. This guide gives you the minimum knowledge that you need to know to start recording with Cheetah.

When should I upgrade Cheetah?

​We try and make upgrading Cheetah as easy as possible, and improve on this process with every new version. However, sometimes things just don’t work correctly. Whether it be dealing with computer specifications, driver issues, or differences in how Cheetah works, it can cause some delays before things are running normally. So, to avoid any extra stress that upgrading may cause, here is a quick guide to answer the question of “Should I upgrade?”

When Not to Upgrade Although we always encourage you to use the latest version of Cheetah, there are some instances where you should not upgrade (unless advised to by Neuralynx). These suggestions are mainly to avoid delays that could derail your experiment. When To Upgrade Some of these scenarios may be contradictory to some of the “Not to Upgrade” ones, but when in doubt, err on the side of caution and stick with what you have. If You Choose Not to Upgrade, there are some things you should know. First of all, we will only perform bug fixes or updates on the most current version of Cheetah. This means that if you find a major bug in version 5.0.0, and the current version is 5.2.0, the fix for your bug will be in 5.2.1. Next, there is no guarantee that older versions of Cheetah will be supported on newer operating systems or with newer hardware. As an example, Cheetah 5.1.0 and older will not run on Windows Vista. If you want to use Vista, you must use 5.2.0.

  • Do not upgrade during the middle of an experiment . Different versions of Cheetah can have different configuration commands, different methods of navigating through the program, or new features that could cause the data recorded for your experiment to not be consistent after the upgrade.
  • Do not upgrade if you do not have a computer that is capable of running the latest version of Cheetah. The Cheetah Requirements are updated with every Cheetah release. If your computer doesn’t meet those requirements, don’t upgrade.
  • Do not upgrade if you are under time constraints. If you don’t give yourself time to become familiar with the newest version of Cheetah before starting your experiment, it may cause delays in getting your experiment running. Also, as you become more familiar with new features, it may change how you run and record your experiment.
  • Do not upgrade if your experiment control program will not work with the upgrade. You may want to contact us via support@neuralynx.com to see if we have a solution that will allow you to upgrade. An example: Cheetah 4.x had the ability to control Cheetah via a COM interface. Because of performance and reliability issues, the COM interface was removed from Cheetah 5.0 and was replaced with NetCom. So, if you have a COM application and do not have the time or means to port it to NetCom, do not upgrade.
  • Upgrade if a new feature will help you perform your experiment. Every version of Cheetah will have a release notes document that describes what has changed since the last version. This document is included with Cheetah (Start Menu -> Neuralynx -> Cheetah5 -> Cheetah Release Notes) and is posted to the release announcement in the forums.
  • Upgrade if a new release fixes a bug or other problem you have been having with Cheetah. We try and test Cheetah as thoroughly as we can before making a release, but it is impossible to catch everything. If there are problems that are particularly bad, we will have a bugfix release. You can tell bugfix releases because the last number in the version is non-zero (i.e. 5.0.2 is a bugfix release, 5.2.0 is not). Bugfix releases have no new functionality and only address the bugs listed in the release notes.
  • When setting up a brand new system, start with the latest version of Cheetah (if possible). All new systems that are shipped from Neuralynx will have the latest release version installed before they leave.
  • Upgrade if you just want to have the latest version. As we said before, we always encourage you to use the latest version of Cheetah. Just make sure you read the “When Not to Upgrade” section before doing so.

What are the system requirements for Cheetah 5?

Minimum Hardware Requirements:

  • Dual-Core processor (Intel Pentium D / AMD 64 x2 or newer processor)
  • 3GB RAM
  • 250GB Serial ATA 3.0Gb/s 7200RPM Hard Drive
  • 512MB PCIe DirectX 9 compatible graphics card (AMD FirePro V3900 1GB Graphic Card is currently supported with HP Z420/Z820 computer systems)
  • DirectX capable sound card for audio output
  • 1000 Mbps (gigabit) Ethernet adapter

Software Requirements:

*Digital Lynx SX acquisition systems require Windows 7
**Digital Lynx S acquisition systems require a DIP switch change when upgrading from Cheetah 5.4 and earlier versions to Cheetah 5.6.3

  • Windows XP SP3 32 bit*, Windows Vista SP2 32bit*, Windows 7 32 bit**.

***Cheetah 160 acquisition systems are not supported on Windows 7

What are the system requirements for Cheetah 6?

Minimum Hardware Requirements:

  • Intel Xeon E5 or Intel i5 processor (2GHz or higher)
  • 4GB RAM
  • 500GB Serial ATA 3.0Gb/s 7200RPM Hard Drive for Windows OS
  • 2TB Serial ATA 3.0Gb/s 7200RPM Hard Drive for data storage
  • 1GB PCIe DirectX 9 compatible graphics card (AMD FirePro W2100 2GB is currently supported with HP Z440/Z840 computer systems)
  • DirectX capable sound card for audio output
  • 1000Mbps (gigabit) Ethernet adapter


Software Requirements: *Digital Lynx SX acquisition systems require Windows 10 64-bit or higher

***Cheetah 160, Cheetah 32, and Digital Lynx “S” acquisition systems are not supported with Cheetah 6.

​Why won’t Cheetah start?

Here are things to check if Cheetah will not start properly:

  • Check your logfile and read error messages. This is the most important part of figuring out what is wrong with Cheetah’s startup. It will tell you exactly which command caused Cheetah to not start properly. The error messages that are shown are also useful in trying to determine what is wrong. If neither of those provide you enough information to continue, make sure that the logfile is included in your email, or available for reference if you call. Logfiles can be viewed by either clicking View Logfile under Cheetah’s File menu, or by opening CheetahLogFile.txt file in Cheetah’s data directory.
  • Licensing Issues. Cheetah requires a valid license to create hardware sub systems. If you are running Cheetah using a Raw Data File Playback system, you do not need a license file. The logfile will have an error message stating that a licensing error has occurred. If you receive a licensing error, please read Answers to Common Neuralynx Licensing Questions.
  • Incorrect System Setup. When installing Cheetah, you will be prompted to select your system type (and amplifier control type if using the Cheetah 32 system). If you select the wrong system, the Cheetah software will try to setup your system using the wrong configuration and not load correctly. Running the installer again and selecting the correct system is the best solution (you do not need to backup or uninstall the incorrect installation). You can also edit configuration files to setup the correct system if you do not wish to reinstall. See the Cheetah Reference Guide for more information on configuration file commands.
  • Invalid Configuration File Loaded. If Cheetah tries to load a command that it does not understand, it will issue an error message and stop processing the configuration files. The line that cause the error will be the last line shown in the logfile. Since Cheetah 5 has a different command syntax than previous versions of Cheetah, you cannot use old configuration files with Cheetah 5. See the Cheetah Reference Guide for more information on configuration file commands.
  • Duplicate Object Created. If you attempt to create any object (hardware sub system, window, acquisition entity, etc.) using a name that already exists, Cheetah will show an error message and stop processing the configuration files. This is generally caused if you try and load a second electrode configuration file, or load configuration files after Cheetah has started. See the Configuration Files section of the Cheetah Reference Guide for more information.
  • Object Referenced that was Never Created. Cheetah needs to have objects created before they are used in a command. Cheetah’s logfile will show the invalid name in the error message. This is generally caused if you load configuration files after Cheetah has started. See the Configuration Files section of the Cheetah Reference Guide for more information.

Setup Questions

What kind of electrical shielding do you recommend for the recording environment with the Digital Lynx?

​The Digital Lynx does not need any additional electrical shielding in the recording environment. The recording system was engineered and designed with differential amplifiers which subtracts artifact interference. In any recording environment, it is always a good idea to keep clear any electrical devices that have the ability to output electrical noise. If there is other electrical equipment in the experiment radius, it is good practice to isolate one single ground for all equipment. We also recommend that the subject is always placed on an ungrounded, non static generating surface while recording is occurring. As always, if you have any particular questions about a certain situation, feel free to contact us and we can recommend a solution.

How can I utilize all A/D channels of a HS-36 on a Cheetah32 ERP-27?

With the ERP-27 Revision 3.0, the first 24 A/D channels come through the A1-12 and B1-12 banks and the last 8 A/D channels come through the CSC bank. With ERP-27 Revisions earlier than 3.0, an ADPT-HS-36-ERP-27 adapter must be used to physically input the signals into the CSC bank.

Cheetah 32 setup issues after installing DT3010 and DIO-24 card or upgrading your Cheetah Software.

Scanning for hardware changes in the device manager as well as opening up Instacal and running a digital test fixes this error.

Hardware Questions

​Does it matter which direction I insert the electrode wire and the pins on an EIB?

​There is no problem with inserting the wire and pins from either direction. However, if a problem occurs with the wire connection, the pin has a better chance of holding the wire more securely, thus maintaining signal connection using the method instructed, which is inserting the wire from the top and pins from the bottom. This is obviously a user preference option and will not affect your recording data.

How do you track in the infrared spectrum?

In order to track Infrared LED equipped headstages, an Infrared BW Camera Kit is used.

What is the purpose of multiple Ground connections on EIB’s?

Excluding the EIB-16, all ground connectors on the EIB’s are tied together.

At what frequency is the TTL port sampled at?

The same frequency that the AD channels are being sampled at.

Software Questions

Can Video Tracker Files (NVT) and Raw Data Files (NRD) be played back at the same time in Cheetah?

Currently, Cheetah can only playback .nrd files and not .nvt file types. The .nvt files can be viewed utilizing the Video Tracker File Playback program or, X and Y coordinate locations can be viewed in NeuraView.

How does the Event Responder specify Port and Bit?

Using the Event Responder, you can have Cheetah recognize the “Event String” and respond with a command that you set in the response command section. The string is what specifies the digital IO device, port, and bit and is set in Event Display Window-Event Options

What are the response limitations of Trial Control?

Due to computer and network latency of the system, Trial Control has a default delay time of approximately 10-15ms between commands. If a delay command is used, 100ms is the shortest allowable dealy. Future releases of Cheetah will incorporate true “real-time” response.

​What’s new in Cheetah version 5.7.x?

Cheetah 5.7.2

Fixed Bugs:

-Data files no longer lock up after ring buffer overrun errors occur.

-High frequency TTL events are now properly saved to NEV files.

-Fixed errors logged for each AE when shutting down software.

Cheetah 5.7.1

Fixed Bugs:

-Fixed communication problem with CUBE utility programs

-Pre-made configuration files now display properly in Notepad

-Y-axis labels in maximized time plot now adjust to appropriate values when using Zoom.

General Changes:

-Added back support for the 3 argument -SetClusterBoundary command in order to work with SpikeSort 3D

-NetCom data buffering is now on by default for SE, ST, and TT acquisition entities.

-Can now add multiple of the same AE to a Time or Spike window.

-Now works with Measurement Computing InstaCal v6.51

-Error message now shown when Digital Lynx SX is acquiring, but not receiving data

-DRS Properties window now adjustable
Cheetah 5.7.0

Added Features:

-Addition of feedback display window type containing FFT plot.

-Data lost during recording and file writing is now logged to a data processing errors file (NDE v1.0.0)

-Automatic recording shut off when hard drive is full.

-New data files per recording option.

-Max file length recording option.

-Raw data file playback resumes from current location when acquisition is toggled.

-Start timestamps specifier for raw data file playback.

-Raw data file playback speed adjustment.

-Plot trace color is now adjustable for for Time Plots.

-Background color is now adjustable for for Time Windows.

-Support for multiple NetCom client applications simultaneously.

-64 bit version - currently supports Windows 7 and Video Tracking, DigitalLynx SX, Raw Data Playback and Cheetah64 systems

-Adjustable channel count for Lynx SX hardware.

General Changes:

-DRS Properties display is now read only.

-Spike Plot can now only individually enable and disable display of cells 0 - 6 and then 7+ as a group.

-Last configuration file is now written out every 5 minutes.

-System configuration file now written and used to notify user of unexpected shutdown.

-All configuration files processed are now stored in sub directory of data directory.

-Addition of hot keys for displaying System Status dialog (Ctrl+Shift+A), Event Display dialog (Ctrl+Shift+E),

AE and Display Properties dialog (Ctrl+Shift+P) and Audio Output Control dialog (Ctrl+Shift+Y)

-Addition of the following commands: -GetDASBuildDate, -GetDASVersionNumber, -GetDASObjects, -GetDASState, -GetSampleFrequency (for HWSS)

-GetVoltageConversion.

-Updated version for all data file formats except log file.

-Unique recording session identifier.

-Data acquisition state retrieval.

-Recording Options dialog now contains raw data file output GUI

-Modification of error reporting and viewing in System Status dialog.

-Firmware version verification for Lynx SX systems.

-Increased log file output for property changes.

-Event history populated in Event dialog even when Event dialog is not displayed.

-Spike trace colors in time window will match trace color in spike window when using classification.

-Messages displayed in time window when window is frozen, recording is off or when raw data file playback is being performed.

-Can now copy selected messages from the System Status Dialog to the clipboard using Ctrl+C or right clicking on an item.

-Removed “Save Window Configuration to File” from menus of display windows.

-All acquisition entities now default to Headstage 01 Animal Ground as their reference.

Fixed Bugs:

-TTL values with bit 15 set to 1 now display correct decimal value in the Event history.

-Digital Lynx SX and ATLAS systems without a DRS no longer cause an exception when viewing reference properties.

-Events being created at 130 Hz no longer cause data loss when the Events Dialog is shown.

-Events created from raw data file playback for bits 16-31 no longer have a hex string of 0x0000 in the event string.

-Reordering of AD Records for Lynx SX hardware sub system.
General Changes:

Cheetah 5.6.3

  • Data Translation Driver updated from 6.7.4.26 to 6.7.4.34 for Cheetah64 analog systems.
  • Bug Fixes: Added Features: General Changes: Fixed Bugs:
  • Timestamps for events created from Digital IO input for Cheetah 32/64 HWSS are now correct.

Cheetah 5.6.0

  • All DRS references are now set using a single Cheetah command, no need to manage globals and locals on each DRS.
  • Added Named TTL Events. Allows you to associate custom event string with specific TTL bits transitioning from 0 (low) to 1 (high).
  • Cheetah will now support a sample frequency of 32768 Hz for the Lynx SX hardware sub system.
  • FIR Filters can now be used for Lynx SX DA output.
  • Cheetah now supports the Digital Lynx SX 16 board system.
  • Cheetah now requires that DRS boards only be at odd slot indices and that all input boards not paired with a DRS be placed after all paired input boards.
  • Cheetah now logs an error when the VT is no longer receiving frames from the capture device during acquisition.
  • Added New Commands:
    • SetAcqEntReference
    • GetAcqEntReference
    • GetMinMaxInputRange
    • GetDiskWriteEnabled
    • SetNamedTTLEvent
    • RemoveNamedTTLEvent
    • GetRawDataFile
    • GetDataDirectory
  • Deprecated Commands that will be removed in a future release
    • SetDRSLocalReferences (replaced by -SetAcqEntReference)
    • SetDRSGlobalReferences (replaced by -SetAcqEntReference)
    • SetDRSChannelReferences (replaced by -SetAcqEntReference)
  • All Cheetah output files now contain a file version in the file header.
  • The -AcqEntName field has been added to the event file header.
  • The -FileType, -NumADChannels and -RecordSize fields have been added to the raw data file header.
  • The -NLXBase_Class_Name field has been changed to -AcqEntName in the video file header.
  • The -FileType, -CheetahRev, -HardwareSubSystemName, -HardwareSubSystemType, -SamplingFrequency, -ADMaxValue, -ADBitVolts and -NumADChannels fields have been added to the lost AD records file header.
  • All AD and raw data timestamps are now synced to start and stop recording event timestamps for all hardware sub systems.
  • The -PostEvent command now has an optional timestamp argument.
  • Cluster and Feature library version information now written to log file.
  • AD data files are now automatically created when the Acq Ent(CSC, Spike) is created.
  • Fixed problems when using globals or making many DRS reference changes that caused Cheetah to report references incorrectly.
  • Fixed erroneous error message saying VT is not in ADAcqEntContainer.
  • Cheetah no longer generates error messages when clicking in the white space below the device selection list in the Audio Output Dialog.
  • Cheetah now returns error code for NetCom OpenStream and CloseStream commands.
  • Creation of a VT can now only happen when Cheetah is idle.
  • VT capture device selection dialog no longer shows capture devices that have invalid hardware IDs.
  • Attempting to create a plot window via NetCom now fails instead of locking Cheetah’s UI which requires a restart of Cheetah to unlock.
  • Tooltips are now shown when hovering over the icons in the time windows.
  • Cheetah now searches the path of a configuration file that calls -ProcessConfigurationFile if no complete path is specified for the file to process.

​Why does Cheetah capture multiple spikes in a single spike record?

​Cheetah captures spikes as 32 samples, and at 32KHz sampling, you usually will not capture part of a second spike during that sample window. However, if you lower your sampling rate, those 32 samples start encompassing more time. In order to detect spikes that occur during the 32 samples of a previous spike, you need to use the retrigger time on each spike acquisition entity that is affected by this issue. The retrigger time is the amount of time to wait after a spike has been detected before searching for the next spike. This setting can be useful if there are rapidly firing spikes, or echoes present on a particular acquisition entity. This avoids having portions of spikes appear in two separate records. When adjusting this value, it is best to start at a higher time and work backwards towards 1. Starting out at 1 might solve the problem, but it causes your system to do unnecessary work.

Why doesn’t Cheetah work on 64 bit Windows?

​This is mainly due to driver compatibility. Since not all of our hardware vendors provide a 64 bit version of our drivers, we cannot create a version of Cheetah that will run on 64 bit systems.

Where can I get a sample NLX file?

​There is a small sample data set available at http://neuralynx.com/software/SampleTetrodeData.zip. This data is recorded from tetrodes in the rat hippocampus. The 5 files in the set represent varying degrees of data separation, Sample1.ntt containing mostly well-defined clusters of data points (easy to sort) through Sample5.ntt with more packed data (more difficult to sort.)This sample data can also be used to evaluate the features and usability of SpikeSort 3D.

How do I get spike audio from Cheetah?

​Since version 4.40, Cheetah has had the ability to output the audio of two spike channels to the right and left stereo channels of your PC’s sound card. In order to do this, you need to include the audio.cfg setup file in your Cheetah setup either by uncommenting or adding the line reading “-PrcSetupFile Audio.cfg”

You should only need to change the -AudioSource lines in the Audio.cfg using the following syntax:

-AudioSource

is either 0 for left, or 1 for right. must be a defined AcqEnt, and must be a spike channel (SE, ST or TT) The volume on the PC might need to be turned up much louder than normal, as these are not very strong signals.

How can I convert A/D values to Volts?

​Neuralynx stores all data in our record files as A/D values. This means that any program you use that reads these files, will read the data in as A/D values by default, NOT volts. In order to convert these A/D values to volts, you need to view the header of the file in question and find the “-ADBitVolts” entry. This value will give you the number of volts for each bit increment in the A/D value. To convert to volts, simply multiply the A/D value by the ADBitVolts value.

Voltage(V)=ADValue*ADBitVolts.

Some Neuralynx programs (such as Neuraview) have an option to display data values as either A/D values or volts. See the Neuraview manual for more information. The input range of the Digital Lynx is +/- 132mV

​How do I analyze my Neuralynx data in MATLAB?

Neuralynx provides two interfaces between Neuralynx data and MATLAB:The first is the Matlab Import/Export MEX files. They will allow you to perform offline analysis of data in Matlab on files recorded from Cheetah. At this time, there is no support for raw data files.

The second option, NetCom for Matlab, allows for online analysis of data and control of Cheetah. You can download the NetCom Development Package. An example of NetCom for MATLAB usage is included in this package.

What systems will Import/Export MEX files work with?

The Import/Export MEX files are designed for use with both the 32 and 64 bit versions of Matlab 2007a and newer for Windows. While Linux versions of the readers are available on our website, they are provided as is and with no support for them via Neuralynx.

How do I install the MEX files?

I​nstalling the MEX files is a three step process after downloading them from our website:

1. Unzip the MEX files into a directory on your PC. We usually use C:\MatlabReaders, but you can use whatever you want. 2. Start up Matlab and under the File menu, select Set Path. 3. Add the full path of the directory where you extracted the MEX files and click save.

How do I use the MEX files?

​Once you have your Matlab path setup correctly, you can then type help and the MEX file name at the Matlab command prompt (i.e. >help Nlx2MatCSC ) to see how the MEX file is used. You can then call the MEX file the same way you would call any other Matlab function.