Wrong DVOC Hardware Version Selected in Experiment Settings Causes IO-Box Error
Last updated: Nov 01, 2026
Problem
EthoVision XT reports 'At least one Noldus Mini USB IO box was not found' when attempting to test tapping or lighting via Arena Hardware Mapping, even though the DanioVision hardware is connected and powered.
Details
Symptoms: The error appears specifically when testing hardware (tapping device, white light) through the Arena–Hardware Mapping button. All physical connections appear correct. The system has a DanioVision Observation Chamber 5 (DVOC 5 / DV-0050) but the project or experiment was configured for an earlier model (e.g., DVOC 4). Selecting the wrong hardware version causes EthoVision XT to look for an IO-box that is not part of the newer system. Distinct from the case where an IO-box is genuinely missing from a shipment (covered in the existing article 'DanioVision IO-Box / IO-Warrior Not Detected by EthoVision XT').
Solution
1. In EthoVision XT, open the relevant Experiment and navigate to Experiment Settings → Hardware.
2. Check which DanioVision Observation Chamber model is selected (e.g., DVOC 4 vs. DVOC 5).
3. Change the selection to match the actual hardware installed in your lab (e.g., select DVOC 5 / DV-0050 if that is the unit you have — check the label on the chamber or the original packing list).
4. Save the experiment settings.
5. Re-run the hardware test via Arena–Hardware Mapping. The IO-box error should no longer appear and tapping/lighting functions should respond correctly.
6. If the correct model is already selected and the error persists, refer to the existing article 'DanioVision IO-Box / IO-Warrior Not Detected by EthoVision XT' for further steps.