Knowledge Base

Controlling Hardware Devices

Set the Port Connections

1. The Device Configuration window appears, listing the available ports of the interface device: TTL Port 1, 2,... and SDI Port 1, 2,... (the latter only for the USB-IO box and the Mini USB-IO box). You can assign one physical device to each row.
2. If you have connected multiple USB-IO boxes, select one from the list at the top.
3. In the Ports column, locate the first available port of the correct type.
   • Locate a TTL Port and click under Device type to view the list of the devices. Select the device that applies.
   • Locate an SDI Port and click under Device type to view the list of the devices. Select the device that applies. Use SDI ports to connect the Lickometers and the PhenoTyper's Top Unit Interface. If you select the latter, four additional rows appear below the option. Select the PhenoTypers' Top Units. For details, see Set the Port Connections for PhenoTyper below.
4. From the Device type list, select the type of device that is (or will be) connected to that port.
5. In the Device ID field, enter the name of the physical device that should be connected to that port.
6. Repeat steps 1 through 5 for other devices, until they are all assigned to a port of the IO-box.
7. Repeat the steps above for the next USB-IO box.
8. When ready, click OK. You return to the Experiment Settings screen. Proceed with assigning devices to the arenas.

Notes:

• The number next to IO-box is the identification number of the IO-box set by the manufacturer. You cannot change this number.
• You must set the port connections only the first time you connect them.
• The port connection settings are at experiment level, and are applied to all your Trial Control Settings. Once you acquire at least one trial, the settings become locked and you can no longer change them. If you need to add devices, create a new experiment or remove the acquired trials.
• If you plan to create several experiments with the same set of devices, you can use an experiment as a template experiment with the hardware settings selected but containing no trials. To create a new experiment from a template experiment: from the File menu, select New template experiment and then Use a custom template. Next, open the experiment you want to use as a template and use the new experiment to acquire data.
• The Device ID is by default the name of the Device type plus a progressive number 1, 2,... We advise you to enter a name that you can recognize easily in your setup.
• For the difference between TTL and SDI ports, see the relevant section of the reference manual.
• Under Device type, select TTL Port Tester if you want to test the functionality of a TTL port.
• Under Device type, select USB-IO monitor if you want to test the connection in the USB-IO box.
• When you select a device type, that device type is added to the file Hardware Setup.xml, which is stored in one of the folders located in the experiment folder ...\Configuration Files\Add-ins\Hardware. Which file is used depends on whether you use the USB-IO box, the Mini USB-IO box, or another system (for example, the Ugo Basile FC Controller, which does not require the USB-IO box or Mini USB-IO box):
  • {A8DA8F3E-7EA3-4629-8327-9D21C90FB3ED} for the USB-IO box.
  • {0308106B-1EBE-4620-B00D-396ABEBBC219} for the Mini USB-IO box.
  • {3AA139A2-4737-4D6D-BF7B-0153CFD4D302} for the Ugo Basile FC Controller.

Use Multiple USB-IO Boxes

You can connect multiple Noldus USB-IO Boxes to one EthoVision XT computer to control more devices. For more information, see the section on using multiple USB-IO boxes in the reference manual.

Set the Port Connections for PhenoTyper

1. Locate SDI Port 13. Under Device type, select Top Unit Interface. This expands the SDI Port to four extra rows.
2. For each of the four rows, under Device type, select:
   • Top Unit (Standard) for standard PhenoTypers.
   • Top Unit (NeuroBsik) for PhenoTypers of the Neuro-Bsik type.
   • Top Unit Tester (PTTB-002x) only when you want to use the Top Unit Tester instead of the actual PhenoTyper Top Unit, for testing purposes.
3. Under Device ID for the rows appended, enter the name of the physical Top Units.
4. When ready, click OK. Next, assign the Top Units to the arenas.

To set the port connections for other groups of PhenoTypers, you must adjust the jumpers for the ports you are going to use. See the PhenoTyper - EthoVision XT 18 - Service Manual.

Set the Port Connections for COM Ports

Prerequisite: Install the Serial interface for EthoVision XT using the steps below.

Install the Serial Interface

1. Close EthoVision XT.
2. In the EthoVision XT 18 full installation package, open the folder Drivers and Tools. Open the folder HardwareInterface SerialPort and double-click HardwareInterface_SerialPort_[version number].msi. You can download the EthoVision XT 18 full installation package from my.noldus.com.
3. Restart EthoVision XT.

Define the COM Port in EthoVision XT

1. Connect the device to the EthoVision XT computer.
2. Open the EthoVision XT experiment and choose Setup > Experiment Settings.
3. Under Trial Control Hardware, select Use of Trial Control Hardware, and click the Settings button. Select COM Ports in the Hardware Interface window and click OK.
4. In the Devices window, click Add and add one or more COM ports that you want to use.
   • Note: After acquiring one or more trials, you cannot add COM ports. First delete the trials, then repeat the steps above.
   • Note: To know which COM port should be added, disconnect the USB cable and check in the Windows Device Manager under Ports (COM & LPT) which item has disappeared.
5. To check the port settings, select a COM port currently connected to a device and click Settings. The following settings should work fine: Baud rate 9600, Data bits 8, Parity None, Stop bits 1, Flow control None. When ready, click OK.
6. Click OK in the Devices window. Next, assign the COM ports to the arenas.

Assign Devices to Arenas

For experiments with one arena only, hardware devices are automatically assigned to the arena. You can skip this section and continue with testing the hardware devices or programming trial control with devices. For multi-arena experiments, follow the procedure below.

Assuming that you have defined your arenas in the Arena Settings, do the following:

1. In the Experiment Explorer, click the Arena Settings in which the arenas you want to use are defined.
2. In the Arena Settings window, click the Arena - Hardware mapping button. The Arena - Hardware mapping window appears.
3. Click Add device. A new row is appended to the table.
4. From the Device type list, select the type of device you want to assign. Select Custom hardware if the device type you are using is not listed.
5. Under Device name, a default name is displayed. This is the suggested Device name for the devices that you specify in that row. We advise you to enter a new name that can be easily recognized, especially if you have more devices of the same type in each arena.

   Example: Each arena is provided with two pellet dispensers of the same type. Enter Pellet Dispenser Left under Device name. In the next step, select the pellet dispensers to be placed on the left side of each arena. Next, click Add device again and enter Pellet Dispenser Right under Device name, then select the pellet dispensers to be placed on the right side of each arena.

6. Under the Arena name, select the physical device that you want to assign to that arena. Assign the other devices to the remaining arenas.
7. Repeat steps 3 to 6 to add a new set of devices.
8. When finished, click OK.

Notes:

• To remove a set of devices, select the corresponding row in the table and click the Remove device button.
• If your setup includes two or more devices of the same type in one arena, make sure that you select the physical devices that belong to the Device name specified under Device name.
• If you cannot select any physical device under the arena names, check that the Device type selected for that row is specified in the Port Device Mapping.
• The Arena - Hardware Mapping settings are valid for all Arena Settings in your experiment. They are added automatically to every new Arena Settings.

Assign Arenas to the PhenoTypers

1. Click Add device in the Arena - Hardware Mapping window.
2. Under Device type, select:
   • Top Unit (Standard) for PhenoTyper 1.
   • Top Unit Light (NOCA-TU1x) for PhenoTyper 2.
3. Under Device name, enter a generic name (for example, Top Unit) or accept the default name (for example, Device A). You will see the Device name again in the Trial Control Settings.
4. Under Arena n, beginning with 1, select the physical device (Top Unit) associated with that arena.
5. Repeat step 4 to assign the Top Units to the remaining arenas.

The physical devices placed in the different arenas are now linked to a generic Device name. You will use that name in the Trial Control Settings to create actions and conditions based on those devices.

Test the Hardware Devices

1. Make sure that the hardware devices are connected to the EthoVision computer via the USB-IO box or the Mini USB-IO box.
2. In the Experiment Explorer, click any Arena Settings.
3. In the Arena Settings window, click the Arena - Hardware mapping button. The Arena - Hardware mapping window appears.
4. Under the Arena name, select the physical device you want to test, and click Test. A new window appears.
5. Depending on the hardware device:
   • For any device that can receive a signal from and send it back to the computer (examples are the Pellet dispenser, Activity wheel break, or Backlight unit white light): Select the appropriate action, click Test and check that the action has been taken. You can also view the result in the Test window, for example that the Number of drops has increased by 1.
   • For any device that can only send a signal to the computer, not receive any (examples are the Lickometer, PhenoWheel, or the Activity wheel counter): Trigger the device manually and check the result in the Test window.
   • For the Top Unit: From the Command list, select the action you want to test, click Test and check the result in the PhenoTyper.
   • For the Custom Hardware Device (for example, the Illuminated shelter): From the Command list, select the action you require, click Test and check that the device has been activated correctly.
   • For the TTL Port Tester: Use this device to check the two-way communication for a specific port. Press a button on the device and check the result in the Test window. From the Command list, select a command and click Test. Check the result on the tester box.
6. When ready, click OK.

Notes:

• Data from the Lickometer and the PhenoWheel are read out in regular time intervals. For the Lickometers currently sold by Noldus IT, the time interval is two seconds, and for the current PhenoWheel it is 60 seconds.
• For all devices: The fact that a signal is given correctly in the Test window but you do not see the response from the device could mean that the device is not functioning (for example, a lamp is broken).
• For the Pellet dispenser: If the Test window shows in error state = true, the pellet dispenser is not connected to the IO-box, or the food pellets are no longer available.
• For the Lickometer: Number of licks and Duration of licks is the cumulative number and duration of licks since the Test button has been clicked, respectively. The device is read out at regular time intervals. At the end of the interval the number and duration of licks is displayed very briefly.
• Important: If you realize that the values of Number and Duration of licks given by EthoVision XT are much higher than expected, close EthoVision XT, disconnect and re-connect the IO-box to the computer, and then restart EthoVision XT.
• For the Top Unit, TTL Port Tester, and Custom Hardware Device: You can also view the result of the action to be tested in the Test window. Locate the Signal you want to test and verify that Value changes from false to true or vice versa. For the TTL Port Tester, you can also press a button and check the counts of presses for that button.

Program Trial Control with Hardware Devices

In the Trial Control Settings, you can define:

• Conditions based on a hardware device. For example, as soon as the cumulative duration of licks equals 1 minute, stop recording.
• Actions on a hardware device. For example, have the Pellet dispenser drop a pellet, or switch on the PhenoTyper's white light.

Define an Action on a Hardware Device

1. In the Components pane, under Actions, double-click the button next to the name of the device type you want to control, or click the button next to it. The Hardware Action window appears.
2. Under Name, enter an Action name. Under Comment (at the bottom) enter a description (optional).
3. Under Action to perform, select the Device name you want to use. The names listed there are defined in the Arena-Hardware mapping window.
4. From the Action to perform list, select the action that the device must take.
5. Click the Test button to check the hardware action. Click the Reset button to reset all hardware.
6. Click OK. Insert the Action box in the appropriate position in the rule.

What You Need

• One of the following hardware interfaces: the Noldus USB-IO box, the Noldus Mini USB-IO box, the Noldus Nortio Core combined with the Nortio TTL Terminal Hub, or the DanioVision Observation Chamber.
• You can control the Ugo Basile Fear Conditioning system without a hardware interface. See the EthoVision XT 18 - Application Manual.
• The hardware interface software Noldus HardwareInterface USB-IO box version 5 (for the USB-IO box, Mini USB-IO box, and DanioVision) and the Noldus HardwareInterface Nortio version 1 (for the Nortio system). This software is automatically installed when you install EthoVision XT.

Tip: To check what is currently installed on your EthoVision XT computer, see the Windows Control Panel under Programs and Features / Add or remove programs.

General Notes

• The items listed under Actions are the Device names selected in the Arena-Hardware mapping window. If the device name is not listed under Actions, check that the port connections are set correctly and that the devices are mapped in the arenas.
• If you have a setup with multiple arenas, it is assumed that each arena has a physical device under that Device name. An action is taken in each arena separately, when the accompanying condition is met in that arena.
• Actions like Light on and Sound on result in the light or sound device being activated for an indefinite time. Remember to add an extra action that switches that light or sound off. The two actions should be separated by a condition. For example: Action Light on then Condition Wait 1 s then Action Light off.
• If you define a sequence of multiple actions on the same device, these are probably evaluated at the same sample time and may conflict. Separate sequential actions on the same device with a wait condition.

Source: EthoVision XT 19 - Trial and Hardware Control Reference Manual