AUTHCODES

List of authorization codes

Platform:

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

The AUTHCODES log lists all auth-codes installed on the receiver and their status.

See Receiver Features: Authorization and Subscriptions for descriptions of auth-codes, software models and interaction with dispatch messages.

See Receiver Features: Authorization and Subscriptions for descriptions of auth-codes and software models.

A signature auth-code is one that has been installed with the AUTH command. An embedded auth-code is included as part of the firmware image. Only those auth-codes with Valid = TRUE can be used as the selected permanent model. The auth-code string is the same up to 7 part string used in the AUTH command with the same format. The model name appears after the 5th comma in the string. If a model has an expiry date, the expiry date follows the model.

See the VERSION log for which model is currently active and which is the selected permanent model.

See the DISPATCHSCHEDULE log or VERSION log for which model is currently active and which is the selected permanent model.

See the VERSION log for which model is currently active and which is the selected permanent model.

The following situations will cause an authorization code to be marked invalid: Authorization Code is for a different receiver Authorization Code has expired Authorization Code was entered incorrectly If you require new authorization codes, contact NovAtel Customer Service.

The AUTHCODES log also reports on the validity of the main firmware digital signature. This signature ensures only uncorrupted NovAtel firmware is installed and run on the receiver.

Message ID: 1348

Log type: Polled

Recommended input:

log authcodesa once

Abbreviated ASCII example:

AUTHCODES COM1 0 66.5 FINESTEERING 2345 157213.000 02000000 2ad2 17375

     VALID 1

           SIGNATURE TRUE "W4PJRF,48GDMN,FPB3H3,5ZB5M2,BZ8B9G,FFNLYNTMNP1"

Field	Field type	Description	Format	Binary bytes	Binary offset
1	Log header	AUTHCODES header For information about log headers, see ASCII, Abbreviated ASCII or Binary.		H	0
2	AUTHCODES firmware signature status	Status of the digital signature check on the main firmware. 1 = NONE 2 = INVALID 3 = VALID 5 = HIGH_SPEED	Enum	4	H
3	Number of Auth-Codes	# of Auth-Codes to follow (max is 24)	Ulong	4	H+4
4	Auth-code type	2=SIGNATURE: Installed with AUTH command. 3=EMBEDDED: Included in the main firmware image.	Enum	4	H+8
5	Valid	TRUE if the Auth-Code has been verified. This model can be used only if TRUE. May be FALSE if expired, incorrect receiver or incorrectly entered.	Bool	4	H+12
6	Auth-Code String	ASCII String of the Auth Code	String [max 80]	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+16
7...	Next Auth-Code = H+8+ (#AuthCodes*variable)
8	xxxx	32-bit CRC (ASCII and Binary only)	Hex	4	H+8+ (#AuthCodes* variable)
9	[CR][LF]	Sentence terminator (ASCII only)	-	-	-