How to know if there are some error in Mobile connection to CORS or AutoCaster
How to know if there are some error in Mobile connection to CORS or AutoCaster
This document applies to SmarRTK and RTKite.
You can extract this error after a failed connection to Cors or AutoCaster.
In SmarRTK the error will be printed in the LCD screen for 5 seconds.
In both, SmarRTK and RTKite, after a failed connection, you can enter in the Mode Config of RTKite or the "Settings by App" Menu Screen of SmarRTK for use the SmartOS Config and read the error (press the button "Get Error Info" of Cors Tab)
|
ERROR CODE |
Description |
|
0000 |
- No error - Timeout of 3 minutes expired without get valid Autonomous location and “Use Location” enabled in the Cors settings - See also Note 1) |
|
0001 |
SIM PIN Error, must be 1111 or not PIN |
|
0002 |
Internal error, contact with Tech support |
|
0003 |
Internal error, contact with Tech support |
|
0004 |
Internal error, contact with Tech support |
|
0005 |
Internal error, contact with Tech support |
|
0006 |
Internal error, contact with Tech support |
|
0007 |
SIM card registration failed (Specify codes MCC/MCN and try again) |
|
0008 |
Wrong APN setup (Mobile Tab in App) |
|
0009 |
Wrong APN setup (Mobile Tab in App) or Unactivated SIM |
|
0011 |
- Connection refused by Server (Cors / AutoCaster) - Invalid Cors setup (URL, User, Password, Stream) |
|
0012 |
Internal error, contact with Tech support |
|
0013 |
Internal error, contact with Tech support |
|
0014 |
Internal error, contact with Tech support |
|
0015 |
Internal error, contact with Tech support |
|
0016 |
Internal error, contact with Tech support |
|
0017 |
Signal strength too weak |
|
0018 |
Need specify MCC and MNC for your SIM card (https://www.mcc-mnc.com) |
|
0019 |
Not registered on Network (Unactivated SIM) |
The second field (GSM) is the strenght of GSM/GPRS signal of device. This value is the CSQ (http://m2msupport.net/m2msupport/atcsq-signal-quality/)
|
CSQ |
RSSI dBm |
Condition |
|
2 |
-109 |
Marginal |
|
3 |
-107 |
Marginal |
|
4 |
-105 |
Marginal |
|
5 |
-103 |
Marginal |
|
6 |
-101 |
Marginal |
|
7 |
-99 |
Marginal |
|
8 |
-97 |
Marginal |
|
9 |
-95 |
Marginal |
|
10 |
-93 |
OK |
|
11 |
-91 |
OK |
|
12 |
-89 |
OK |
|
13 |
-87 |
OK |
|
14 |
-85 |
OK |
|
15 |
-83 |
Good |
|
16 |
-81 |
Good |
|
17 |
-79 |
Good |
|
18 |
-77 |
Good |
|
19 |
-75 |
Good |
|
20 |
-73 |
Excellent |
|
21 |
-71 |
Excellent |
|
22 |
-69 |
Excellent |
|
23 |
-67 |
Excellent |
|
24 |
-65 |
Excellent |
|
25 |
-63 |
Excellent |
|
26 |
-61 |
Excellent |
|
27 |
-59 |
Excellent |
|
28 |
-57 |
Excellent |
|
29 |
-55 |
Excellent |
|
30 |
-53 |
Excellent |
|
255 |
Note 1) |
Note 1) |
NOTES:
1) An read "Error: 0 GSM: 255" means that there no is error info to display because no Mobile connection was initiated. For example:
- in UHF modes you will get this message because this info does not apply.
- in Cors modes you can get this info if you are in indoor (or without antenna) and the setting "Use Location" is enabled. The setting "Use Location" requires satellites view.
Tech Support team