NavCom Sapphire Rev.J - Manual (Page 73)

Sapphire Technical Reference Manual Rev. J
73
1.20.1.5 Data
In NB_LoadDataCmd message, this field contains the data. It has other meanings in
other subID messages. The maximum size of this field is 2048 bytes. If loading through
the Ethernet port using UDP, the maximum size should be less than 1400 bytes.
1.20.2 BOOTLOADPIOB SubID Message Format
1.20.2.1 SubID NB_PingCmd Message Format
SubID NB_PingCmd is sent from PC to receiver. It is used by the PC to ping the receiver
bootloader software and to start the bootloading process. Its format is defined in
Table 40.
Table 40: SubID NB_PingCmd Format
Field
Data
Type
Value and Description
Function Type SubID U08 Enum NB_PingCmd
Pass or Fail U08 0. This field is not used for this command
Valid count U16 0. There is no data following the address field
Address U32
0. The PIO does not require a “Target Type” in this message as
does the GNSS firmware.
1.20.2.2 SubID NB_PingRep Message Format
SubID NB_PingRep is sent from receiver to PC. It is the reply message for
NB_PingCmd. Its primary function in the PIO firmware load process is to verify the PIO
is ready to begin the download process. Its format is defined in Table 41.
Table 41: SubID NB_PingRep Format
Field
Data
Type
Value and Description
Function Type SubID U08 Enum NB_PingRep.
Pass or Fail U08 1. Always set to “PASS” by PIO firmware.
Valid count U16 0. There is no data following the address field
Address U32 Same as the address field in the NB_PingCmd msg.
1.20.2.3 SubID NB_BaudCmd Message Format
SubID NB_BaudCmd is sent from PC to receiver. It is used by the PC to specify an
alternative baud rate for bootloading. This message is not required if the baud rate
doesn’t need to be changed (see Table 42 for the message format).
If the PIO software bootloading port is USB or Ethernet, this command has no effect and
is not sent. Also, due to hardware architecture design, if the PIO software bootloading
port is COM1, this command is not sent.