Trimble Outdoors 58052-00 Benutzerhandbuch
Copernicus GPS Receiver 1 0 9
FIRMWARE UPGRADE 1 1
Pseudo-Code Explanation
The following provides details about the steps shown in the above pseudo-code for
the firmware loading procedure.
the firmware loading procedure.
1.
Read firmware BIN file and load into a memory buffer.
(See Appendix A for an example function that shows how this is achieved.)
(See Appendix A for an example function that shows how this is achieved.)
2.
Establish a serial port connection to the target in the TSIP or NMEA mode.
Communication with the target over its serial port must be established first.
Change the local host’s port settings to match those of the target. Refer to the
GPS receiver’s user manual for details.
Change the local host’s port settings to match those of the target. Refer to the
GPS receiver’s user manual for details.
If using TSIP, issue a TSIP version request (packet 0x1F) and wait for the
response (packet 0x45). The receipt of the packet 0x45 shows that the host port
settings and the target port settings match and the host is communicating with
the target. If the packet 0x45 is not received, the host and target port settings
are not in agreement.
response (packet 0x45). The receipt of the packet 0x45 shows that the host port
settings and the target port settings match and the host is communicating with
the target. If the packet 0x45 is not received, the host and target port settings
are not in agreement.
If using NMEA, issue NMEA version request (packet VR) and wait for the
response. The user manual includes the TSIP and NMEA protocol
specification. The receipt of the response of the packet VR shows that the host
port settings and the target port settings match and the host is communicating
with the target. If the response of the packet VR is not received, the host and
target port settings are not in agreement.
response. The user manual includes the TSIP and NMEA protocol
specification. The receipt of the response of the packet VR shows that the host
port settings and the target port settings match and the host is communicating
with the target. If the response of the packet VR is not received, the host and
target port settings are not in agreement.
In some cases, the target may enter the monitor mode automatically when
power is applied. For example, if the previous firmware loading process has
not been finished, the firmware checksum won’t match, and the target will
automatically start up in the monitor mode. In such cases, Step 2 will fail, and
the loading procedure should continue at Step 4 as described below.
power is applied. For example, if the previous firmware loading process has
not been finished, the firmware checksum won’t match, and the target will
automatically start up in the monitor mode. In such cases, Step 2 will fail, and
the loading procedure should continue at Step 4 as described below.
3.
Force the target into the monitor mode.
Assuming the communication has been established, issue the “Force to
Monitor” command. If using TSIP, the following byte string (hex values) must
be sent to the target to force it into the monitor mode:
Monitor” command. If using TSIP, the following byte string (hex values) must
be sent to the target to force it into the monitor mode:
10 1E 4D 10 03
If using NMEA, the following character string must be sent to the target to
force it into the monitor mode:
force it into the monitor mode:
$PTNLSEM*
Once the system is in the monitor mode, a special Monitor protocol is used to
communicate with the Copernicus GPS Receiver.
communicate with the Copernicus GPS Receiver.
See the Appendices in this manual for detailed information on both TSIP and
NMEA Force to Monitor commands.
NMEA Force to Monitor commands.
After issuing the command, wait 0.5 seconds before proceeding with the next
step to allow the target to switch to the monitor mode and be ready to accept
Monitor mode commands.
step to allow the target to switch to the monitor mode and be ready to accept
Monitor mode commands.