The I/O Driver Editor is started from the bottom pane of the Console:
It can be used for:
- Creation of a user-defined input driver
- Creation and/or editing of generic drivers for an OPC Server
- Decoding of multiple systems from a server
- Decoding of multiple strings for a single server
- For each string that needs decoding, a separate driver needs to be created
|Driver||Generic OPCUA Input||Interface Type||OPC UA||Driver Class Type||Terminated|
|UTC Driver||No||Input / Output||Input||Executable||DrvInputOpcUAClient.exe|
- After creating a driver, it can be used in the template database to decode data strings.
If multiple strings need to be decoded for a single server:
- Select for each system you want to decode the created driver
- Select the same endpoint URL
- Acceleration Velocity Sensor
- Not to be used yet.
- Not to be used yet.
- Dredging Sensor
Driver reports active if value not equal to 0.
Please note that the driver does not use the C-O and multiplication factor from the GUI in Database Setup.
QPS defined driver definition files (installed with Qinsy) are stored under the Qinsy installation folder in the following location: <Qinsy install folder>\Drivers\Definitions\Input
User defined / edited driver definition files are stored in the Windows Common Documents folder: <common documents>\QPS\QINSy\Drivers\Definitions\Input (Normally, Common Documents is located at C:\Users\Public\Documents)
The configuration file for a generic serial input driver is conform the following layout:
For more information see the F1 inline help of the I/O Driver Editor utility.
This driver also supports connection to a classic opc server (DCOM ).
To get the correct connection URL you can start the driver stand alone.
- A command line will appear.
- Enter the discover option and the available DCOM servers will be printed.
- Use the printed endpoints as endpoint in Database Setup.
An alternative would be to start the driver from a command line:
- Windows key + R
- Enter cmd.exe
- Navigate to the Qinsy install directory
- cd C:\Program Files (x86)\QPS\QINSy\<version>
- Execute command:
- DrvInputOpcUAClient.exe -d
Additional info for Magnetometers
Add manual echosounder
Please be aware that you need to add a Manual echosounder to your towed object to be able to process the track of the towed object.
Online / Replay
Since Qinsy version 8.10.2014.10.20:
Storing magnetometer data to a sounding grid has the option to create a corridor perpendicular to the sailing direction. I.e. that the full path of the corridor is filled automatically with each single reading of the magnetometer.
To set this corridor width value, go to the Layer properties in the Controller's Session Setup, Storage, Sounding grid or use the Sounding Grid Utility, making sure that the layer type is 'Magnetometer data'.
The maximum width of the corridor is 100 times the minimum cell size of the sounding grid.
- Since 8.10.2013.01.24.1
Generic Driver Multiple String Support
The Generic Driver was modified so that multiple definitions (ini-files) may be attached to a single serial port.
This makes it possible to decode multiple systems of the same type from a single telegram.
In order to do this a definition should be made for each system.
Since 8.10.2013.05.06.1Generic Driver Network UDP Supports
Use the Console to start the I/O Driver Editor, select driver type 'Generic Input' and state on the General Information Wizard page whether the IO should be serial or from UDP.
Note that IO COMport settings or the UDP port number must be selected in Dabase Setup when adding a system using this generic driver.