When used for data acquisition, ODIN needs to connect with an RTNet Server that resides either on the same computer as ODIN (if a MiniHub system is in use) or more commonly on a Codamotion active hub (CodaHub or similar). The RTNet server is responsible for the real-time control of hardware functions and receives the acquired data before it is passed to ODIN.
Hardware used in conjunction with ODIN (e.g. CODA units, EMG systems and force plates) must first be defined using the Configuration Manager (a separate utility) that manages hardware configurations for the RTNet Server.
For most regular users of the ODIN system, it is only necessary to check that the ODIN computer has a network link to the CodaHub, and then to select the server from ODIN, and then a predefined hardware configuration to use to use for the data acquisition session.
With a MiniHub system, the RTNet Server should have been installed on the ODIN computer itself, and then it is necessary to manually start it – there will be a desktop shortcut to do this. When the RTNet Server is running on the local computer, ODIN still makes an internal network connection to it.
First select Hardware > Select Hardware Server from the top menu in the ODIN window.
ODIN automatically searches the current network for active RTNet Servers, and then displays a selection list – in most cases there will be only one:
If no server is found on the network, a message will be displayed. When using a Codamotion CodaHub, this means that either the CodaHub has not been started, or that is not visible on the network. If the ODIN computer has a direction Ethernet connection to the CodaHub, it may be necessary to check the network configuration.
When using a minihub, this means that the RTNet server is not running.
After selecting “OK” on the Server selection dialogue, a list of available hardware configurations will be displayed:
This screen shows all the hardware configurations available on the chosen RTNet server. As mentioned above, new hardware configurations must be defined using the Configuration Manager utility. When selecting a hardware configuration, the user should always select the one with the minimum number of devices required for the current data acquisition session. For example, do not select a configuration with force platforms if force data is not required. When OK is clicked on the Hardware Configuration selection dialogue, the RTNet Server will attempt to initialise the selected configuration of hardware units, and there is a short delay while this proceeds. If successful, the configuration name is displayed in the lower right corner of the ODIN screen.
A configuration defines the number of CODA units in use, the ports to which they are connected and the third party equipment (force plates, EMG systems etc.) attached, as well as such parameters as the correlation coefficient to be used for CODA measurements. For simple systems, there will be only a few configurations defined. For systems with several different acquisition devices, many combinations may be configured. The Codamotion Configuration Manager is used to manage the list.