Responses
The receiver is capable of outputting several responses for various conditions. Most responses are error messages to indicate when something is not correct.
The output format of the messages is dependent on the format of the input command. If the command is input as abbreviated ASCII, the output will be abbreviated ASCII. The same rule applies for both ASCII and binary formats.
ASCII Message |
Binary Message ID |
Meaning |
---|---|---|
OK |
1 |
Command was received correctly |
Requested log does not exist |
2 |
The log requested does not exist |
Not enough resources in system |
3 |
The request has exceeded a limit (for example, the maximum number of logs are being generated) |
Data packet doesn’t verify |
4 |
Data packet is not verified |
Command failed on receiver |
5 |
Command did not succeed in accomplishing requested task |
Invalid Message ID |
6 |
The input message ID is not valid |
Invalid Message. Field = x |
7 |
Field x of the input message is not correct |
Invalid Checksum |
8 |
The checksum of the input message is not correct. Only applies to ASCII and binary format messages. |
Message missing field |
9 |
A field is missing from the input message |
Array size for field x exceeds max |
10 |
Field x contains more array elements than allowed |
parameter x is out of range |
11 |
Field x of the input message is outside the acceptable limits |
Message Id already exists in system |
12 |
Message Id already exists in system |
Debug token unknown |
13 |
Debug token unknown |
Trigger x not valid for this log |
14 |
Trigger type x is not valid for this type of log |
Authcode table full - Reload Software |
15 |
Too many authcodes are stored in the receiver. The receiver firmware must be reloaded |
Invalid date format |
16 |
This error is related to the inputting of authcodes. Indicates the date attached to the code is not valid |
Invalid Authcode entered |
17 |
The authcode entered is not valid |
No matching model to remove |
18 |
The model requested for removal does not exist |
Not valid Auth code for that Model |
19 |
The model attached to the authcode is not valid |
Channel is invalid |
20 |
The selected channel is invalid |
Requested rate is invalid |
21 |
The requested rate is invalid |
Word has no mask for this type |
22 |
The word has no mask for this type of log |
Channels locked due to error |
23 |
Channels are locked due to error (the receiver must be reset or power cycled to track satellites again) |
Injected time invalid |
24 |
Injected time is invalid |
Com port not supported |
25 |
The COM or USB port is not supported |
Message is incorrect |
26 |
The message is invalid |
Invalid PRN |
27 |
The PRN is invalid |
PRN not locked out |
28 |
The PRN is not locked out |
PRN lockout list is full |
29 |
PRN lockout list is full |
PRN already locked out |
30 |
The PRN is already locked out |
Message timed out |
31 |
Message timed out |
Unknown COM port requested |
33 |
Unknown COM or USB port requested |
Hex string not formatted correctly |
34 |
Hex string not formatted correctly |
Invalid baud rate |
35 |
The baud rate is invalid |
Message is invalid for this model |
36 |
Message is invalid for this model of receiver |
Could Not Save Configuration |
38 |
Could Not Save Configuration |
Too Many Configuration Items |
39 |
Too Many Configuration Items |
Command only valid if in NVM Fail mode |
40 |
Command is only valid if NVM is in fail mode |
Invalid offset |
41 |
The offset is invalid |
File conflict |
43 |
File conflict |
File not found |
44 |
File not found |
File open |
45 |
File open |
File not open |
46 |
File not open |
Invalid DOS FileName |
47 |
Invalid DOS File name |
File channel in use |
48 |
File channel in use |
File close fail |
50 |
File close fail |
Disk not present |
51 |
Disk not present |
Disk error |
52 |
Disk error |
Disk full |
53 |
Disk full |
NVM Write Fail |
74 |
NVM Write Fail |
NVM Read Fail |
75 |
NVM Read Fail |
Not allowed for input |
77 |
Not allowed for input |
Maximum number of user messages reached |
78 |
Maximum number of user messages has been reached |
User message decryption failed |
79 |
User message decryption failed |
GPS precise time is already known |
84 |
GPS precise time is already known |
The message could not be created |
87 |
The message could not be created |
Not enough memory to start application |
113 |
Not enough memory to start application |
No data available |
114 |
No data available |
Invalid handshaking |
117 |
Invalid handshaking |
Message name already exists |
118 |
Message name already exists |
Invalid message name |
119 |
Invalid message name |
The datatype is invalid |
120 |
The data type is invalid |
Message ID is reserved |
121 |
Message ID is reserved |
Message size too large |
122 |
Message size too large |
Invalid Security Key |
126 |
Invalid security key |
Hardware not available |
127 |
Hardware not available |
Requested pulse width is invalid |
131 |
Requested pulse width is invalid |
Coarse time is not achieved yet |
133 |
Coarse time is not achieved yet |
Invalid Config Code |
134 |
Invalid Config Code |
ConfigCode table full - Reload Software |
135 |
Config Code table is full. Reload the software. |
Unknown Object Type |
136 |
Unknown object type |
This operation is not valid at this time |
137 |
This operation is not valid at this time |
User VARF in use |
140 |
User VARF in use |
Must enable CLOCKADJUST |
141 |
Must enable CLOCKADJUST. See the CLOCKADJUST command for information about enabling. |
Disk busy |
142 |
Disk busy |
Invalid Word Input Argument |
143 |
Invalid Word Input Argument |
Parameter %d is not valid for this model |
148 |
The parameter specified is not valid for this model |
IMU SPECS LOCKED FOR THIS IMU TYPE |
150 |
SPAN allows the default specifications for a select few IMUs to be modified to support different variants. However, most IMU specifications are not allowed to change. |
Invalid interface mode. Parameter %d |
151 |
The specified Interface mode parameter is not valid. |
COMMAND INVALID FOR THIS IMU |
154 |
The entered command cannot be used with the configured IMU. |
IMU protocol is locked for this IMU type |
155 |
IMU protocol is locked for this IMU type |
IMU TYPE IS NOT SUPPORTED WITH CURRENT MODEL |
157 |
A firmware model upgrade is required to use the requested IMU (CONNECTIMU command). |
Trigger start time is invalid |
159 |
Trigger start time is invalid |
Sensor is not initialized |
160 |
Sensor is not initialized |
TRIGGER BUFFER IS FULL |
161 |
The TIMEDEVENTPULSE command limit of 10 events has been reached, and a new event cannot be set until an event is cleared. |
Board has not achieved finesteering |
162 |
The receiver has not achieved finesteering |
SETUPSENSOR COMMAND IS LOCKED |
163 |
The SETUPSENSOR command cannot be modified because there are remaining trigger events queued. |
Invalid Profile Name |
165 |
Invalid Profile Name |
Maximum Number Profiles Exceeded |
166 |
The maximum number of profiles is exceeded |
Failed To Delete Profile |
167 |
Failed to delete the profile |
Profile Name Already Exists |
168 |
Profile name already exists |
Total Profile Commands Size Over Limit |
169 |
Total Profile commands size over limit |
Cannot Change Profile When Activated |
170 |
Cannot change a Profile when it is activated |
Signature Authcode Copy Fail |
171 |
Signature Authcode copy fail |
Maximum Number of Profile Commands Exceeded |
172 |
The maximum number of PROFILE commands exceeded |
Profile Active, Could Not Save Configuration |
173 |
Profile active, could not save configuration |
Current PPP position has bad status and cannot be used for seeding |
178 |
Current PPP position has bad status and cannot be used for seeding |
PPP seed position failed integrity check |
179 |
PPP seed position failed integrity check |
Invalid password |
180 |
Invalid password |
Too many files |
181 |
Too many files |
Encryption key output is not allowed |
186 |
Encryption key output is not allowed |
Secure port requires login |
187 |
Secure port requires login |
NMEA2000/J1939 stack is already running on the CAN port |
188 |
NMEA2000/J1939 stack is already running on the CAN port |
No saved PPP seed position |
191 |
No saved PPP seed position |
System type is invalid for this model |
192 |
System type is invalid for this model |
Command is not supported for this model |
193 |
Command is not supported for this model |
Position Averaging Not Started |
194 |
Position averaging not started |
Not in GLIDE mode |
200 |
Not in GLIDE mode |
PPP seeding invalid in forced dynamics mode |
201 |
PPP seeding invalid in forced dynamics mode |
Wrong combination of parameters |
202 |
Wrong combination of parameters |
Invalid Calibration Request |
203 |
Invalid calibration request |
Active Gimbal Detected |
204 |
Active gimbal detected |
Authcode table full - Use auth erase_table |
205 |
Authcode table full. An authcode must be removed before another authcode can be added. Refer to the AUTH command for instructions on removing authcodes and cleaning up the authcode table. |
Profile Not Running - Profile should be activated |
206 |
Profile not running - Profile should be activated |
ID provided is already in use |
208 |
ID provided is already in use |
ID provided does not exist |
209 |
ID provided does not exist |
Calibration already in progress |
210 |
Calibration already in progress |
Filter cannot be enabled due to channel speed settings |
211 |
Filter cannot be enabled due to channel speed settings |
Notch Filter and Frequency are mismatching |
212 |
Notch filter and frequency are mismatching |
Filter can not cascade |
213 |
Filter can not cascade |
There is no RF filter applied |
214 |
There is no RF filter applied |
ID provided should be 4 character long |
215 |
ID provided should be 4 characters long |
Invalid subscription code |
216 |
Invalid subscription code |
Subscription table full |
217 |
Subscription table full |
Network id does not match subscription code |
218 |
Network ID does not match the subscription code |
Subscription not found |
219 |
Subscription not found |
Subscription not active |
220 |
Subscription not active |
Cannot activate expired subscription |
221 |
Cannot activate expired subscription |
Maximum number of logs exceeded. No new log added. |
222 |
Maximum number of logs exceeded. No new log added. |
Seed is too far in the past |
223 |
Seed is too far in the past |
Final log request must use the ONCE trigger |
224 |
Final log request must use the ONCE trigger |
Channel invalid for region x |
225 |
Channel invalid for region x |
Region not set |
226 |
Region not set |
Estimated RBV must be entered first |
227 |
Initial RBV estimate is required before RBV calibration |
Command failed because WIFIALIGNAUTOMATION is enabled |
240 |
Command failed because WIFIALIGNAUTOMATION is enabled. See the WIFIALIGNAUTOMATION command. |
Specified network not enabled with WIFINETCONFIG command |
241 |
Specified network not enabled with WIFINETCONFIG command. See the WIFINETCONFIG command. |