My Tickets

Drivers Manual

OISTAR Digilog (Modified Anschutz) - 03


Driver for Digilog gyro compass output sentences, containing (gyro)compass heading, pitch and roll data.

Driver can be used as gyro system, to obtain the heading, and as MRU system, to obtain the pitch and roll.
Two formats can be decoded: the Digilog ASCII comms format and the Modified Anschutz format, matching the Anschutz telegram format with the addition of pitch and roll encoded in the magnetic heading locations.
The ASCII SG Brown format output by a Digilog compass can be decoded using a Sperry Repeater (ASCII).

When option "OISTAR" has been selected, the driver will use timetags from preceding OiSTAR headers.

Driver Information

Driver Digilog Interface Type Serial  Driver Class Type Terminated 
UTC Driver (question) No Input / Output Input  Executable DrvGyroDigilog.exe 
Related Systems
Related Pages

Decoding Notes

The quality indicator (see Observation Physics Display) is obtained from the status flags as follows.




Value ASCII (T)

Value Anschutz (fg)



exact heading





sensor timeout





heating phase





settling phase





no valid heading





no data found



The quality indicator of the pitch and roll observations is copied from the heading observation when the pitch and roll data fields are valid, otherwise it is set to -1 to indicate that no valid data field was found.

The quality indicator of the heave observation is always -1, since there is no heave data field available.

Note that observations with a negative quality indicator are not used in Qinsy. This can be checked with the Observation Physics display.

Database Setup

To decode the  pitch and roll , add a "System" of type "Pitch, roll and heave", select the Digilog driver, and define the MRU observation parameters.
To decode all three observations (pitch, roll and heading), add both these system types to the Qinsy database and make sure to select the same driver name and the same serial I/O parameters for both systems. 

Drivers IO Notes

Command line parameter "OI" indicates that timetags are obtained from preceding "OiSTAR" headers, if available.

Otherwise the time of the first incoming byte is used.
"2" indicates Modified Anschutz format.