SOFTLOADSETUP

Sends configuration information to the receiver for the SoftLoad process

Platform:

OEM719, OEM729, OEM7500, OEM7600, OEM7700, OEM7720, PwrPak7, CPT7, CPT7700, SMART7, SMART2

The SOFTLOADSETUP command can be used in place of the SOFTLOADSREC command when sending S0 Records. This command is meant to be used if the user requires that the entire SoftLoad process be performed in binary, but can also be used in ASCII or abbreviated ASCII. The examples below are given in abbreviated ASCII for simplicity.

Refer to Updating Using SoftLoad Commands for more information about the SoftLoad process.

This command can only be sent to the receiver when the SOFTLOADSTATUS log reports READY_FOR_SETUP.

After each SOFTLOADSETUP command, the user must wait for the OK or ERROR command response before proceeding. This response is guaranteed to be output from the receiver within 15 seconds from the time the command was received by the receiver. If an error response is returned, consult the SOFTLOADSTATUS log for more detail.

NovAtel S0 records use the following format: S0~X~<<DATA>>, where X is the Setup Type and <<DATA>> is a NULL terminated string. To convert from S0 record to the SOFTLOADSETUP command, convert the Setup Type to the appropriate Setup type enumeration, as described in Table: Available Set Up Commands, and copy the <<DATA>> string in to the Setup data string.

Message ID: 1219

Abbreviated ASCII Syntax:

SOFTLOADSETUP setuptype setupdata

Input Example:

SOFTLOADSETUP datatype "APP"

Field	Field Type	ASCII Value	Binary Value	Description	Format	Binary Bytes	Binary Offset
1	Command header	-	-	SOFTLOADSETUP header This field contains the command name for abbreviated ASCII or the message header for ASCII (see page 1) or Binary (see page 1).	-	H	0
2	Setuptype	See Table: Available Set Up Commands		The type of setup command	Enum	4	H
3	Setupdata	-	-	ASCII setup data string. See Table: Available Set Up Commands for details on this data. This data can be pulled from the S0 records of the hex file being loaded onto the receiver. If the ASCII form of this command is used, this string must be enclosed in double quotes (“ “)	String [512]	variable1 In the binary case, each string field needs to be NULL terminated and additional bytes of padding added to maintain 4-byte alignment, up to the maximum defined by the string size. The next defined field starts immediately at the next 4-byte alignment following the NULL.	H+4

Available Set Up Commands

Binary	ASCII	Description
1	Platform	Comma separated list of platforms supported by the data to be uploaded. This corresponds to S0~P~. For example, the S-Record S0~P~OEM729,OEM7700,OEM719, translates to SOFTLOADSETUP PLATFORM "OEM729,OEM7700,OEM719"
2	Version	Version of the data to be uploaded. This corresponds to S0~V~. For example, the S-Record S0~V~OMP070400RN0000, translates to SOFTLOADSETUP VERSION "OMP070400RN0000"
3	Datatype	Intended data block for the data to be uploaded. This corresponds to S0~T~. For example, the S-Record S0~T~APP, translates to SOFTLOADSETUP DATATYPE "APP"
4	Authcode	PSN and AUTH code for the data to be uploaded. The format is: PSN:AuthCode.Note that since there are commas within the AuthCode, double quotes must surround the PSN:AuthCode string. For example: SOFTLOADSETUP AUTHCODE "BFN10260115: T48JF2,W25DBM,JH46BJ,2WGHMJ,8JW5TW,G2SR0RCCR,101114"