Can StarFire Correction Data be output from StarFire receivers?
Extensive engineering changes are necessary in order to successfully utilize the clock and orbit corrections that are broadcast by NavCom’s StarFire network with a multi-frequency receiver. NavCom has implemented clock and orbit compatibility in its own line of multi-frequency receivers. However, NavCom also makes StarFire corrections available for use with third party manufacturer’s receivers. If implementation with a third party manufacturer’s receiver is intended, a thorough evaluation of the receiver performance has to be made. In particular, specific data regarding the biases that are generated by the receiver’s code correlation techniques has to be obtained and then adjusted as part of any position solution to be generated using clocks and orbits in conjunction with such a receiver. Please contact our business development group for further details (firstname.lastname@example.org).
How does the Event Marker work?
This feature allows an external system such an aerial camera or echo sounder to send a pulse to the GPS receiver. The receiver logs and/or transmits a time-stamped message when the pulse (or event) occurred. Please refer to “System/Control Commands” under Protocol in the “Technical Reference Manual”: 0x20 – Data Request and 0xb4 – Event Latch Data for more details.
In the case of the 'all-in-one' NavCom product positioning mode, SureNav™, how do I know which mode the unit is currently operating in?
The NMEA standard GGA message provides a Quality Indicator which informs the user what mode they are operating in (No Correction, DGPS, or RTK Mode). Since the NMEA format does not allow the user to ascertain the differences between different types of DGPS modes (i.e. WAAS, RTCM or StarFire), NavCom has incorporated a use of the GGA REF ID field within the GGA message to deliver this information to the user. It should also be noted that all of this information is readily available through NavCom’s proprietary binary format.