Other products from the Inertial Systems product line are also supported but not all of them have been field tested.
The following data can be decoded and stored from the packet protocol stream:
- Motion (Roll, Pitch and Heave)
- Velocities, Accelerations and Rotations
- Metadata (Status flags, Temperature, Pressure, etc.)
Please note that ANPP messages from the acoustic product line (e.g. Subsonus) are not 100% compatible with ANPP messages from the INS products so this means that you should only use this driver for the Spatial FOG INS.
Advanced Navigation Spatial ANPP
|Driver Class Type||Counted|
|UTC Driver||Yes||Input / Output||Input||Executable||
When using the serial driver make sure to use the RS-232 interface because Qinsy doesn't support (in general) RS-422.
Note that Qinsy v9.5.1 (and newer versions) will also support a network interfacing (TCP) with the Spatial FOG sensor.
The UDP network interface is not supported by this driver.
The driver will use the time from the System State Packet (PID 20) message for time-stamping.
But only when the Filter Status 'UTC Time' has been initialized.
In order to check this you may use:
- the Status dialog of the Spatial FOG Manager: the bullet point Time must be green.
- Use a Generic Display to monitor the Filter Status value: Bit 3 must be set.
See paragraph Qinsy Online, Displays, Generic Display for more information about the Filter Status values.
When the Filter Status UTC Time is not (yet) initialized then the driver will time-stamp the data upon arrival.
You may test the incoming data using the manufacturer's own software called Spatial FOG Manager which can be downloaded from their website.
Note that this software requires for Java to be installed on your computer.
Because of the serial connection you can't connect simultaneously, so before going online with Qinsy you should disconnect the Spatial FOG Manager from the sensor.
(Of course use in the Qinsy template setup the same COMport and baudrate.)
From the View pull-down menu you can select all kinds of dialogs showing specific sensor information.
A useful display to select from the Spatial FOG Manager View menu is the Status dialog:
Note that most of this sensor specific information can also be monitored using the Qinsy displays while working online and this will also be recorded for processing and analyzing.
It is important to use the same interfacing settings for all 'Advanced Navigation Spatial ANPP' systems in your template setup.
Add a Gyro Compass System to your template setup and select driver "Advanced Navigation Spatial ANPP (Heading)" when using the serial I/O interface or "Network (TCP) - Advanced Navigation Spatial ANPP (Heading)" when using the network interface.
The heading observation will be decoded from the System State Packet (PID 20) and its quality indicator will be standard deviation as decoded from the Euler Orientation Standard Deviation Packet (PID 28).
Add a Pitch Roll Heave Sensor to your template setup and select driver "Advanced Navigation Spatial ANPP (Roll Pitch Heave)" when using the serial I/O interface or "Network (TCP) - Advanced Navigation Spatial ANPP (Roll Pitch Heave)" when using the network interface.
The roll and pitch observation will be decoded from the System State Packet (PID 20).
The heave will be decoded from the Heave Packet (PID 58) heave point 1 field.
Therefore it is important to set the Primary Reference Point offsets (Heave Point 1) to zero in the setup of the Spatial FOG Manager.
- Select the correct Node location.
This will be the node location of where the Spatial FOG INS is mounted on the vessel.
Make sure to use to following sign conventions:
Roll: Positive heeling to starboard
Pitch: Positive bow up
- Heave: Positive upwards
- Rotation Measurement Type: HPR (roll first)
Illustrations from the Advanced Navigation Spatial FOG Reference Manual
- You may leave all parameters at their defaults
Add an Acceleration Velocity Sensor to your template setup and select driver "Advanced Navigation Spatial ANPP (Velo, Acc, RoT)" when using the serial I/O interface or "Network (TCP) - Advanced Navigation Spatial ANPP (Velo, Acc, RoT)" when using the network interface.
Velocity, acceleration and rotation observations will be decoded from the System State Packet (PID 20).
- Add the required observation types that you want and select for each one the same location of the Spatial FOG INS.
You may change the default name for each observation as long as it doesn't exceed 16 characters.
- Here you can also change the default name of each observation and you may leave all parameters at their defaults.
- Speed unit must be 'Meters / Second', Acceleration unit must be 'Meters / Second^2' and Rate-of-Turn unit must be 'Degrees / Second'.
Add a Miscellaneous System to your template setup and select driver "Advanced Navigation Spatial ANPP (Metadata)" when using the serial I/O interface or "Network (TCP) - Advanced Navigation Spatial ANPP (Metadata)" when using the network interface.
Generic observations will be decoded from the System State Packet (PID 20) and the Raw Sensors Packet (PID 28).
- Here you can add up to six generic observations that you may want to monitor.
Each generic observation needs a unique Slot Id so the driver knows which field to decode.
It is highly recommended to use the drop-down selection for the correct Slot Id:
Of course you may change the default name for each observation as long as it doesn't exceed 16 characters.
Observation Packet ID Slot 1 System status System State Packet (PID 20)
Filter status System State Packet (PID 20)
G force (g) System State Packet (PID 20)
IMU Temperature (Degrees C) Raw Sensors Packet (PID 28)
Pressure (Pascals) Raw Sensors Packet (PID 28)
Pressure Temperature (Degrees C) Raw Sensors Packet (PID 28) PRESS_TEMP Debug Information All packets DEBUG_INFO
Note that the Slot ID is case-sensitive.
- You may add manually an extra generic observation with Slot Id "DEBUG_INFO".
This special observation (useful for debugging or analyzing purposes) will decode the packet ID of each incoming packet even if the contents of that packet are not decoded by the driver.
Further, if that packet has a device address or device id, then it will be the quality indicator of that observation.
Packets without a device address will have a quality indicator of zero.
- Here you can also change the default name of each observation as long as it doesn't exceed 16 characters.
You may leave all parameters at their defaults.
In this example observation PRESSURE has been selected. Note that the value will be decoded from the Raw Sensor Packet (PID 28) and has unit Pascal.
If you set the Scale factor in this dialog to 0.00001 you will get for the corrected value in Qinsy the pressure value in unit Bars.
The driver has no user-interface so you need to set up several displays to see if data is received, decoded and what the computed results are.
Always useful as a starter to see if data is coming in at the I/O port.
Observation Physics Display
Useful display to see if data is coming in, at what update rate and how the values are decoded.
A generic display is particular useful to show the meaning of the individual bits of the SYSTEM STATUS and FILTER STATUS flag value.
So with this display you can easily monitor the same important information as you would see using the Spatial FOG Manager's Status View (as described in the System Interfacing paragraph of this document).
Copy the layout (Use right-mouse 'Save Link As...') to your current Project's Settings\Display folder and open it using a new Generic Display.
Please note that Save as will not work when you are viewing this document offline through the Qinsy Console; it is only accessible via the QPS website.
After downloading you only need to select the correct miscellaneous system and generic observation as defined in your template setup and the correct positioning system:
The pictures in this example are also not embedded but feel free to browse for your own ones