|
|
|
|
|
Some types of receivers, such as the Trimble NetRS receivers, are capable of sending observations and other data in BINEX format. A passive connection to the receiver is necessary.
To setup Trimble 4D Control Server for decoding BINEX data from a Trimble receiver, add a GNSS Receiver module. In this case, the connection to the receiver is always a passive connection. Go to the Decoder category of properties, Decoder group setting and select BINEX.
The following message types are supported:
Tip - BINEX does not support sending the receiver boot version. Therefore, the boot version of a receiver sending BINEX data is not displayed in the Device Manager Device Info view.
Tip - The BINEX standard does not allow to specify to which power supply source the receiver is currently connected to. Therefore, the Device Manager Voltage / Temperature Info view cannot display the current values for Voltage, Status, and Source for a GNSS Receiver module receiving BINEX input.
Note - Since a receiver sending BINEX data is connected passively, you cannot request current ephemeris data at startup. Wait for the automatic arrival of ephemeris data or use the download feature to receive precise orbits. Note that GLONASS observations need the matching ephemerides. therefore, GLONASS satellites will not be tracked or stored until ephemeris data is available.
Note - The BINEX convention does not offer a tilt message. For propagating tilt data, Trimble receivers use the comment field of the 00 Site Metadata message type. Trimble 4D Control Server correctly detects and decodes tilt data in the BINEX comment field.
For general information on the BINEX format, refer to the binex.unavco.org website.