Knowledge Base

Issues

• EthoVision XT does not record the pellet drops
• The USB-IO box was accidentally disconnected, or is not found
• EthoVision XT does not trigger the LED in an optogenetics setup
• I cannot select devices from the second USB-IO box
• Some inputs of the Fear Conditioning System do not work
• How can I send data through a COM port?

EthoVision XT Does Not Record the Pellet Drops

The problem occurs also when the Pellet dispenser works just fine.

1. Check that all USB-IO boxes are powered up. If the USB-IO box is not powered up, it may work half way and that is rarely noticed.
2. If many devices are connected or there is much USB activity, EthoVision XT cannot read the pellet drops in the necessary time. The Pellet dispenser sends out an approximately 100 ms pulse to the USB-IO box and then EthoVision XT; if it takes longer to read the pulse, EthoVision XT misses the read out. Try to reduce USB devices that work simultaneously.

See also the EthoVision XT 19 - Trial and Hardware Control - Reference Manual for limitations in the number of devices that can be controlled.

The USB-IO Box Was Accidentally Disconnected, or Is Not Found

The message At least one USB-IO box was not found appears.

1. Reconnect the USB-IO box to the EthoVision XT PC. Check that the USB-IO box is powered.
2. Click the Retry button (when this button is available).
3. Establishing connection requires some time. Wait until a message is given that the USB-IO box is detected again.

If the message of re-established connection does not appear, close and then restart EthoVision XT.

EthoVision XT Does Not Trigger the LED in an Optogenetics Setup

In an optogenetics experimental setup, EthoVision XT controls one or more Pulsers through the USB-IO box. The Pulser and the LED can be triggered manually or with the Pulser software, but not through EthoVision XT. When the trigger command is sent out from EthoVision XT, the LED in the USB-IO box does not switch on.

Solution: Review all the cable connections as described in the chapter Optogenetics experiments in the EthoVision XT 19 - Application Manual. Check that on the LED controller box, the switch at the back is set to Ext. Also in the Device Configuration window of EthoVision XT, make sure that for the ports TTL1, TTL2, etc., Custom hardware is selected. For details on this step, see the EthoVision XT 19 - Trial and Hardware Control - Reference Manual.

I Cannot Select Devices from the Second USB-IO Box

A number of devices are connected to the EthoVision XT system through two USB-IO boxes. When one tries to select devices in the Device Configuration window, the drop-down menu under Devices is grayed-out.

Solution:

1. Close EthoVision XT, and uninstall the Noldus HardwareInterface software. You can find this in the Windows Control Panel > Programs and Features.
2. Download the full installation file (see Install EthoVision XT), and browse to Drivers and tools > PreRequisites > HardwareInterfaceIobox. Run the installation file HardwareInterface_Iobox_x64 [version number].msi.

Some Inputs of the Fear Conditioning System Do Not Work

Check that the USB-IO box is powered. Review the cable connections as described in the section of the EthoVision XT 19 - Application Manual which describes the Ugo Basile Fear Conditioning System.

How Can I Send Data Through a COM Port?

Use case: Send a string or an integer to an Arduino board via COM.

To do so, you must first install a DLL interface component. Please contact Noldus for further details. Once this component is installed:

1. In the Experiment Settings, declare the COM port as you would when using the Noldus USB-IO box and other devices.
2. In the Arena-Hardware Mapping window, map the COM port onto the arena.
3. In the Trial Control Settings, add an action based on a COM port.

Note that:

• Data (string or long integers) is sent out as a string. For example, if you specify 1234, the string "1234" is sent out.
• A string can also be hexadecimal, for example, 0x6261. Two bytes are sent out, first 0x61, then 0x62.

Issues

• The quality of detection deteriorates with time
• I cannot specify the white light fade duration in minutes and hours
• There are spikes in the tracks
• The DanioVision White light does not work when I skip some arenas

The Quality of Detection Deteriorates with Time

After a few trials, the subjects are no longer correctly detected. The issue likely occurs because of condensation on the Fresnel lens.

1. Set the anti-condensation mechanism to permanent On (see the DanioVision DVOC-0041 - Reference Manual for details). This bypasses the automatic control.
2. If condensation disappears after a while, the temperature sensor and/or the sensor circuit may be defective. If condensation remains, the glass heater may be defective. Contact Noldus Support for more information.

I Cannot Specify the White Light Fade Duration in Minutes and Hours

Probably you have an experiment created with a previous version of EthoVision XT. In that version you can only select a fade duration of the white light in seconds.

There Are Spikes in the Tracks

See the topic Troubleshooting: Data Acquisition > I see spikes in the track.

The DanioVision White Light Does Not Work When I Skip Some Arenas

Normally the White light device is associated with Arena 1 (A1 in most well plates). If you set that arena to To Skip, once you start the trial EthoVision XT does not send any command to the White light device because the corresponding arena is not active.

To solve this issue, do one of the following:

• In the Trial List, set Arena 1 back to Planned. EthoVision XT collects data for all the planned arenas, including Arena 1. If you are not interested in the data of Arena 1, you can filter it out in the Data Profile (Filter option).
• In the Trial List, keep Arena 1 set to To Skip. Open the Arena Settings and in the Arena-Hardware Mapping window select No device allocated under Arena 1 and select White Light Stimulus under one of the arenas that you do not skip.

The second option is only available when your experiment does not contain tracks yet.

Issues

• My results differ from what I obtain using the original Python scripts
• Number and names of subjects do not match those in the LMT database file
• The LMT database file is of incompatible format

My Results Differ from What I Obtain Using the Original Python Scripts

This may occur when you use Python scripts that were modified after the release of EthoVision XT. In that case we cannot guarantee that EthoVision XT gives exactly the same results. EthoVision XT is based on the Live Mouse Tracker scripts of version 1.0.3 (October 4, 2022).

Number and Names of Subjects Do Not Match Those in the LMT Database File

After you have selected a LMT database (*.sqlite) for import, an error message opens.

1. Click Close and open the Experiment Settings.
2. Next to Number of Subjects per Arena, enter the number of individuals that interacted in the LMT experiment.
3. If necessary, rename the subjects to A, B, C, etc. Do not enter other names. See Subjects per Arena.
4. Repeat the import data procedure. See Import Live Mouse Tracker Data.

The LMT Database File Is of Incompatible Format

After you have selected a LMT database (*.sqlite) for import, an error message opens. This could be caused by the experiment file being empty or without a definition of the subjects. It is probably corrupt. Try to export the LMT data again.

Source: EthoVision XT 19 Help, Noldus Information Technology