SARA SFF R412 no network Universal Tracker

Hello,

I have a problem with the Universal Tracker sample with AllThingsTalk. Unable to find the LTE-M network with an iBasis sim card. The SIM card works well with another board …

Here are the logs of the Universal Tracker program :

Initializing R4X… [init] started. [initBuffer]

AT
<< timed out >> AT
<< timed out >> AT
<< timed out >> AT
<< timed out >> AT
<< AT
<< OK
<< timed out >> AT+CMEE=2
<< AT+CMEE=2
<< OK >> ATE0
<< ATE0
<< OK

AT+CFUN?
<< +CFUN: 1 << OK

AT+COPS?
<< +COPS: 0 << OK

AT+URAT?
<< +CME ERROR: Operation not supported >> AT
<< timed out >> AT
<< timed out

AT
<< timed out >> AT
<< timed out >> AT
<< AT
<< OK >> AT
<< AT
<< OK
<< timed out >> AT+CMEE=2
<< AT+CMEE=2
<< OK >> ATE0
<< ATE0
<< OK

AT+CFUN?
<< +CFUN: 1 << OK

AT+COPS?
<< +COPS: 0 << OK

AT+URAT?
<< +CME ERROR: Operation not supported >> AT
<< OK

AT+CGSN
<< 354679091133606
<< OK
** Boot-up completed successfully! Starting getGpsFixAndTransmit()… …10s…20s…30s
…40s…50s…60s …70s…80s…90s …100s…110s…120s
.Timestamp, BatteryVoltage, BoardTemperature, Lat, Long, Altitude, Speed, Course, SatelliteCount, TimeToFix
946684997, 113, 31, 0, 0, 0, 0, 0, 0, 255 >> AT+CGATT?
<< +CGATT: 0 << OK

AT
<< OK
<< timed out >> AT+CMEE=2
<< OK >> ATE0
<< OK

AT+CFUN?
<< +CFUN: 1 << OK

AT+COPS?
<< +COPS: 0 << OK

AT+URAT?
<< +CME ERROR: Operation not supported >> AT
<< timed out >> AT
<< timed out >> AT
<< timed out >> AT
<< timed out >> AT
<< timed out >> AT
<< AT
<< OK >> AT
<< AT
<< OK
<< timed out >> AT+CMEE=2
<< AT+CMEE=2
<< OK >> ATE0
<< ATE0
<< OK

AT+CFUN?
<< +CFUN: 1 << OK

AT+COPS?
<< +COPS: 0 << OK

AT+URAT?
<< +CME ERROR: Operation not supported
Sending message through UDP >> AT+USOCR=17,16666
<< +CME ERROR: Operation not allowed Failed to create socket

The command AT + URAT = 7 sends an error, is this normal?

  • CME ERROR: Operation not supported

Thanks for your help.

Hi @Pogprop,

It seems that you have the latest Ublox R412M firmware on your module.
The ublox firmware is not backward compatible, we are working on a software upgrade for the universal tracker.
For the new firmware setting the mno profile is required.

I will send you a stable version which we are currently testing, it will be also be available on GitHub soon.

Best regards,
Jan

I am having the exact same problem with my SFF R412. I’m attempting to connect with a Hologram sim card to LTE-M. My responses on the COM port are shown below. Not sure about my “Force Operator” setting.

Enter command: ntype=4
ntype=4

Commands:
Show IMEI (SI):
Show CCID (SC):
Show Module version (SV):
Commit Settings (CS):

Settings:

GPS
Fix Interval (min) (fi=): 15
Alt. Fix Interval (min) (afi=): 0
Alt. Fix From (HH) (affh=): 0
Alt. Fix From (MM) (affm=): 0
Alt. Fix To (HH) (afth=): 0
Alt. Fix To (MM) (aftm=): 0
GPS Fix Timeout (sec) (gft=): 120
Minimum sat count (sat=): 4
Num Coords to Upload (num=): 1

On-the-move Functionality
Acceleration% (100% = 8g) (acc=): 0
Acceleration Duration (acd=): 0
Fix Interval (min) (acf=): 1
Timeout (min) (act=): 10

Cellular
Network Type (N2xx NB-IoT = 2, R4xx NB-IoT = 3, R4xx LTE-M = 4, R412 2G = 5, 2G/3G = 6) (ntype=): 4
All Things Talk Token (att=):
APN (apn=): hologram
Force Operator (opr=): 310260
CID (cid=): 1
MNO Profile (mno=): 1
APN user (apnu=):
APN password (apnp=):
NB-IoT Band (bnd=): 20
Target IP (ip=): 0.0.0.0
Target port (prt=): 1
Response Timeout (rxto=): 15

Misc
Status LED (OFF=0 / ON=1) (led=): 0
Debug (OFF=0 / ON=1) (dbg=): 1
Enter command:

Settings:

GPS
Fix Interval (min) (fi=): 15
Alt. Fix Interval (min) (afi=): 0
Alt. Fix From (HH) (affh=): 0
Alt. Fix From (MM) (affm=): 0
Alt. Fix To (HH) (afth=): 0
Alt. Fix To (MM) (aftm=): 0
GPS Fix Timeout (sec) (gft=): 120
Minimum sat count (sat=): 4
Num Coords to Upload (num=): 1

On-the-move Functionality
Acceleration% (100% = 8g) (acc=): 0
Acceleration Duration (acd=): 0
Fix Interval (min) (acf=): 1
Timeout (min) (act=): 10

Cellular
Network Type (N2xx NB-IoT = 2, R4xx NB-IoT = 3, R4xx LTE-M = 4, R412 2G = 5, 2G/3G = 6) (ntype=): 4
All Things Talk Token (att=):
APN (apn=): hologram
Force Operator (opr=): 310260
CID (cid=): 1
MNO Profile (mno=): 1
APN user (apnu=):
APN password (apnp=):
NB-IoT Band (bnd=): 20
Target IP (ip=): 0.0.0.0
Target port (prt=): 1
Response Timeout (rxto=): 15

Misc
Status LED (OFF=0 / ON=1) (led=): 0
Debug (OFF=0 / ON=1) (dbg=): 1
Initializing R4X…
[init] started.
[initBuffer]

AT

<< timed out

AT

<< timed out

AT

<< timed out

AT

<< timed out

AT

<< AT

<< OK
<< timed out
<< timed out

AT+CMEE=2

<< AT+CMEE=2

<< OK

AT+UGPIOC=16,255

<< AT+UGPIOC=16,255

<< OK

ATE0

<< ATE0

<< OK

AT+CFUN?

<< +CFUN: 1
<< OK

AT+UMNOPROF?

<< +UMNOPROF: 0
<< OK

AT+COPS=2

<< OK

AT+UMNOPROF=1

<< OK

AT+CFUN=15

<< OK

AT+CPIN?

<< timed out

AT+CPIN?

<< AT+CPIN?

<< +CPIN: READY
<< OK

ATE0

<< ATE0

<< OK
<< timed out

AT+URAT?

<< +CME ERROR: Operation not supported

AT+CPWROFF

<< OK

AT

<< timed out

AT

<< timed out

AT

<< timed out

AT

<< timed out

AT

<< AT

<< OK
<< timed out

AT

<< AT

<< OK
<< timed out
<< timed out

AT+CMEE=2

<< AT+CMEE=2

<< OK

AT+UGPIOC=16,255

<< AT+UGPIOC=16,255

<< OK

ATE0

<< ATE0

<< OK

AT+CFUN?

<< +CFUN: 1
<< OK

AT+UMNOPROF?

<< +UMNOPROF: 0
<< OK

AT+COPS=2

<< OK

AT+UMNOPROF=1

<< OK

AT+CFUN=15

<< OK

AT+CPIN?

<< timed out

AT+CPIN?

<< AT+CPIN?

<< +CPIN: READY
<< OK

ATE0

<< ATE0

<< OK
<< timed out

AT+URAT?

<< +CME ERROR: Operation not supported

AT+CPSMS=0

<< OK

AT+CEDRXS=0

<< OK

AT+UPSV=0

<< OK

AT

<< OK

AT+CGSN

<< 354679091575301
<< OK
** Boot-up completed successfully!
Starting getGpsFixAndTransmit()…

AT+CGATT?

<< +CGATT: 0
<< OK

AT

<< OK
<< timed out
<< timed out

AT+CMEE=2

<< OK

AT+UGPIOC=16,255

<< OK

ATE0

<< OK

AT+CFUN?

<< +CFUN: 1
<< OK

AT+UMNOPROF?

<< +UMNOPROF: 0
<< OK

AT+COPS=2

<< OK

AT+UMNOPROF=1

<< OK

AT+CFUN=15

<< OK

AT+CPIN?

<< timed out

AT+CPIN?

<< AT+CPIN?

<< +CPIN: READY
<< OK

ATE0

<< ATE0

<< OK
<< timed out

AT+URAT?

<< +CME ERROR: Operation not supported

AT+CPWROFF

<< OK

AT

<< timed out

AT

<< timed out

AT

<< timed out

AT

<< timed out

AT

<< AT

<< OK
<< timed out

AT

<< AT

<< OK
<< timed out
<< timed out

AT+CMEE=2

<< AT+CMEE=2

<< OK

AT+UGPIOC=16,255

<< AT+UGPIOC=16,255

<< OK

ATE0

<< ATE0

<< OK

AT+CFUN?

<< +CFUN: 1
<< OK

AT+UMNOPROF?

<< +UMNOPROF: 0
<< OK

AT+COPS=2

<< OK

AT+UMNOPROF=1

<< OK

AT+CFUN=15

<< OK

AT+CPIN?

<< timed out

AT+CPIN?

<< AT+CPIN?

<< +CPIN: READY
<< OK

ATE0

<< ATE0

<< OK
<< timed out

AT+URAT?

<< +CME ERROR: Operation not supported

AT+CPSMS=0

<< OK

AT+CEDRXS=0

<< OK

AT+UPSV=0

<< OK
.
Setting RTC from 946684947 to 1574728639
1s
Timestamp, BatteryVoltage, BoardTemperature, Lat, Long, Altitude, Speed, Course, SatelliteCount, TimeToFix
1574728639, 119, 20, 343999218, -838779817, 343, 0, 212, 6, 1

AT+CGATT?

<< +CGATT: 0
<< OK

AT

<< OK
<< timed out
<< timed out

AT+CMEE=2

<< OK

AT+UGPIOC=16,255

<< OK

ATE0

<< OK

AT+CFUN?

<< +CFUN: 1
<< OK

AT+UMNOPROF?

<< +UMNOPROF: 0
<< OK

AT+COPS=2

<< OK

AT+UMNOPROF=1

<< OK

AT+CFUN=15

<< OK

AT+CPIN?

<< timed out

AT+CPIN?

<< AT+CPIN?

<< +CPIN: READY
<< OK

ATE0

<< ATE0

<< OK
<< timed out

AT+URAT?

<< +CME ERROR: Operation not supported

AT+CPWROFF

<< OK

AT

<< timed out

AT

<< timed out

AT

<< timed out

AT

<< timed out

AT

<< timed out

AT

<< AT

<< OK
<< timed out

AT

<< AT

<< OK
<< timed out
<< timed out

AT+CMEE=2

<< AT+CMEE=2

<< OK

AT+UGPIOC=16,255

<< AT+UGPIOC=16,255

<< OK

ATE0

<< ATE0

<< OK

AT+CFUN?

<< +CFUN: 1
<< OK

AT+UMNOPROF?

<< +UMNOPROF: 0
<< OK

AT+COPS=2

<< OK

AT+UMNOPROF=1

<< OK

AT+CFUN=15

<< OK

AT+CPIN?

<< timed out

AT+CPIN?

<< AT+CPIN?

<< +CPIN: READY
<< OK

ATE0

<< ATE0

<< OK
<< timed out

AT+URAT?

<< +CME ERROR: Operation not supported

AT+CPSMS=0

<< OK

AT+CEDRXS=0

<< OK

AT+UPSV=0

<< OK

AT+CPWROFF

<< OK

Thanks for sharing your log, I see that the profile isn’t stored correctly in your module.
We are working on a fix for this issue.

Best regards,
Jan