Connection issue with SARA R410 AFF FW 05.08

SARA AFF
1

Hello, I’ve encountered an issue with connecting to the network using the latest FW version for SARA R410 (SARA-R410M-02B-01-L0.0.00.00.05.08)

I have also added the latest Sodaq_R4X library to 2.0.0 (at least I believe so, please correct me if something is wrong based on the log below)

12:46:42.507 -> Settings:
12:46:42.507 ->
12:46:42.507 -> GPS
12:46:42.507 -> GPS (OFF=0 / ON=1) (gps=): 1
12:46:42.507 -> Fix Interval (min) (fi=): 15
12:46:42.507 -> Alt. Fix Interval (min) (afi=): 0
12:46:42.507 -> Alt. Fix From (HH) (affh=): 0
12:46:42.507 -> Alt. Fix From (MM) (affm=): 0
12:46:42.507 -> Alt. Fix To (HH) (afth=): 0
12:46:42.507 -> Alt. Fix To (MM) (aftm=): 0
12:46:42.507 -> GPS Fix Timeout (sec) (gft=): 120
12:46:42.507 -> Minimum sat count (sat=): 4
12:46:42.507 -> Num Coords to Upload (num=): 1
12:46:42.507 ->
12:46:42.507 -> On-the-move Functionality
12:46:42.507 -> Acceleration% (100% = 8g) (acc=): 0
12:46:42.507 -> Acceleration Duration (acd=): 0
12:46:42.507 -> Fix Interval (min) (acf=): 1
12:46:42.507 -> Timeout (min) (act=): 10
12:46:42.507 ->
12:46:42.507 -> Cellular
12:46:42.507 -> Network Type (N2xx NB-IoT = 2, R4xx NB-IoT = 3, R4xx LTE-M = 4, R412 2G = 5, 2G/3G = 6) (ntype=): 3
12:46:42.507 -> All Things Talk Token (att=):
12:46:42.507 -> APN (apn=): lpwa.telia.iot
12:46:42.507 -> Force Operator (opr=): 24202
12:46:42.507 -> CID (cid=): 1
12:46:42.507 -> APN user (apnu=):
12:46:42.507 -> APN password (apnp=):
12:46:42.507 -> Band (bnd=): 20
12:46:42.507 -> Target IP (ip=): 40.68.172.187
12:46:42.507 -> Target port (prt=): 8891
12:46:42.507 -> Response Timeout (rxto=): 15
12:46:42.507 ->
12:46:42.507 -> Misc
12:46:42.507 -> Cayenne LPP (OFF=0 / ON=1) (cay=): 0
12:46:42.507 -> Status LED (OFF=0 / ON=1) (led=): 0
12:46:42.507 -> Debug (OFF=0 / ON=1) (dbg=): 1
12:46:42.507 -> Initializing R4X…
12:46:42.507 -> [init] started.
12:46:42.507 -> [initBuffer]
12:46:44.531 -> >> AT
12:46:44.531 ->
<< timed out
12:46:45.021 -> >> AT
12:46:45.021 ->
<< timed out
12:46:45.535 -> >> AT
12:46:45.535 ->
<< timed out
12:46:46.042 -> >> AT
12:46:46.042 ->
<< timed out
12:46:46.545 -> >> AT
12:46:46.545 ->
<< AT

12:46:46.818 -> << OK
12:46:47.054 -> << timed out
12:46:48.058 -> << timed out
12:46:48.058 -> >> AT+CMEE=2
12:46:48.058 ->
<< AT+CMEE=2

12:46:48.105 -> << OK
12:46:48.105 -> >> AT+UGPIOC=16,255
12:46:48.105 ->
<< AT+UGPIOC=16,255

12:46:48.105 -> << OK
12:46:48.105 -> >> ATE0
12:46:48.105 ->
<< ATE0

12:46:48.105 -> << OK
12:46:48.105 -> >> AT+CFUN?
12:46:48.105 ->
<< +CFUN: 1
12:46:48.152 -> << OK
12:46:48.152 -> >> AT+UMNOPROF?
12:46:48.152 ->
<< +UMNOPROF: 0
12:46:48.152 -> << OK
12:46:48.152 -> >> AT+COPS=2
12:46:48.152 ->
<< OK
12:46:48.199 -> >> AT+UMNOPROF=1
12:46:48.199 ->
<< OK
12:46:48.199 -> >> AT+CFUN=15
12:46:48.199 ->
<< OK
12:46:49.480 -> >> AT+CPIN?
12:46:49.480 ->
<< timed out
12:46:54.543 -> >> AT+CPIN?
12:46:54.543 ->
<< AT+CPIN?

12:46:54.543 -> << +CPIN: READY
12:46:54.587 -> << OK
12:46:54.587 -> >> ATE0
12:46:54.587 ->
<< ATE0

12:46:54.587 -> << OK
12:46:54.821 -> << timed out
12:46:54.821 -> >> AT+URAT?
12:46:54.821 ->
<< +CME ERROR: Operation not supported
12:46:54.868 -> >> AT+CPWROFF
12:46:54.868 ->
<< OK
12:47:02.337 -> >> AT
12:47:02.337 ->
<< timed out
12:47:02.837 -> >> AT
12:47:02.837 ->
<< timed out
12:47:03.340 -> >> AT
12:47:03.340 ->
<< timed out
12:47:03.860 -> >> AT
12:47:03.860 ->
<< timed out
12:47:04.355 -> >> AT
12:47:04.355 ->
<< AT

12:47:04.589 -> << OK
12:47:04.823 -> << timed out
12:47:05.291 -> >> AT
12:47:05.291 ->
<< AT

12:47:05.338 -> << OK
12:47:05.560 -> << timed out
12:47:06.603 -> << timed out
12:47:06.603 -> >> AT+CMEE=2
12:47:06.603 ->
<< AT+CMEE=2

12:47:06.603 -> << OK
12:47:06.603 -> >> AT+UGPIOC=16,255
12:47:06.603 ->
<< AT+UGPIOC=16,255

12:47:06.603 -> << OK
12:47:06.603 -> >> ATE0
12:47:06.603 ->
<< ATE0

12:47:06.650 -> << OK
12:47:06.650 -> >> AT+CFUN?
12:47:06.650 ->
<< +CFUN: 1
12:47:06.650 -> << OK
12:47:06.650 -> >> AT+UMNOPROF?
12:47:06.650 ->
<< +UMNOPROF: 0
12:47:06.696 -> << OK
12:47:06.696 -> >> AT+COPS=2
12:47:06.696 ->
<< OK
12:47:06.696 -> >> AT+UMNOPROF=1
12:47:06.696 ->
<< OK
12:47:06.696 -> >> AT+CFUN=15
12:47:06.696 ->
<< OK
12:47:07.989 -> >> AT+CPIN?
12:47:07.989 ->
<< timed out
12:47:13.068 -> >> AT+CPIN?
12:47:13.068 ->
<< AT+CPIN?

12:47:13.068 -> << +CPIN: READY
12:47:13.068 -> << OK
12:47:13.068 -> >> ATE0
12:47:13.068 ->
<< ATE0

12:47:13.115 -> << OK
12:47:13.349 -> << timed out
12:47:13.349 -> >> AT+URAT?
12:47:13.349 ->
<< +CME ERROR: Operation not supported
12:47:13.349 -> >> AT
12:47:13.349 ->
<< OK
12:47:13.396 -> >> AT+CGSN
12:47:13.396 ->
<< 356726104410832
12:47:13.396 -> << OK
12:47:13.396 -> ** Boot-up completed successfully!
12:47:13.396 -> Starting getGpsFixAndTransmit()…
12:47:13.958 -> .
12:47:13.958 -> Setting RTC from 946684903 to 1568890036
12:47:14.052 -> 1s
12:47:14.099 -> Timestamp, BatteryVoltage, BoardTemperature, Lat, Long, Altitude, Speed, Course, SatelliteCount, TimeToFix
12:47:14.099 -> 1568890036, 117, 26, 588883757, 57034949, 46, 0, 0, 7, 1
12:47:14.099 ->
12:47:14.099 -> >> AT+CGATT?
12:47:14.099 ->
<< +CGATT: 0
12:47:14.146 -> << OK
12:47:14.146 -> >> AT
12:47:14.146 ->
<< OK
12:47:14.383 -> << timed out
12:47:15.424 -> << timed out
12:47:15.424 -> >> AT+CMEE=2
12:47:15.424 ->
<< OK
12:47:15.424 -> >> AT+UGPIOC=16,255
12:47:15.424 ->
<< OK
12:47:15.471 -> >> ATE0
12:47:15.471 ->
<< OK
12:47:15.471 -> >> AT+CFUN?
12:47:15.471 ->
<< +CFUN: 1
12:47:15.471 -> << OK
12:47:15.471 -> >> AT+UMNOPROF?
12:47:15.471 ->
<< +UMNOPROF: 0
12:47:15.517 -> << OK
12:47:15.517 -> >> AT+COPS=2
12:47:15.517 ->
<< OK
12:47:15.517 -> >> AT+UMNOPROF=1
12:47:15.517 ->
<< OK
12:47:15.551 -> >> AT+CFUN=15
12:47:15.551 ->
<< OK
12:47:16.794 -> >> AT+CPIN?
12:47:16.794 ->
<< timed out
12:47:21.896 -> >> AT+CPIN?
12:47:21.896 ->
<< AT+CPIN?

12:47:21.896 -> << +CPIN: READY
12:47:21.896 -> << OK
12:47:21.896 -> >> ATE0
12:47:21.896 ->
<< ATE0

12:47:21.945 -> << OK
12:47:22.167 -> << timed out
12:47:22.167 -> >> AT+URAT?
12:47:22.167 ->
<< +CME ERROR: Operation not supported
12:47:22.213 -> >> AT+CPWROFF
12:47:22.213 ->
<< OK
12:47:29.683 -> >> AT
12:47:29.683 ->
<< timed out
12:47:30.169 -> >> AT
12:47:30.169 ->
<< timed out
12:47:30.688 -> >> AT
12:47:30.688 ->
<< timed out
12:47:31.191 -> >> AT
12:47:31.191 ->
<< timed out
12:47:31.694 -> >> AT
12:47:31.694 ->
<< timed out
12:47:32.232 -> >> AT
12:47:32.232 ->
<< timed out
12:47:32.736 -> >> AT
12:47:32.736 ->
<< AT

12:47:32.736 -> << OK
12:47:32.983 -> << timed out
12:47:33.478 -> >> AT
12:47:33.478 ->
<< AT

12:47:33.478 -> << OK
12:47:33.744 -> << timed out
12:47:34.745 -> << timed out
12:47:34.745 -> >> AT+CMEE=2
12:47:34.745 ->
<< AT+CMEE=2

12:47:34.745 -> << OK
12:47:34.745 -> >> AT+UGPIOC=16,255
12:47:34.745 ->
<< AT+UGPIOC=16,255

12:47:34.745 -> << OK
12:47:34.745 -> >> ATE0
12:47:34.745 ->
<< ATE0

12:47:34.791 -> << OK
12:47:34.791 -> >> AT+CFUN?
12:47:34.791 ->
<< +CFUN: 1
12:47:34.791 -> << OK
12:47:34.791 -> >> AT+UMNOPROF?
12:47:34.791 ->
<< +UMNOPROF: 0
12:47:34.838 -> << OK
12:47:34.838 -> >> AT+COPS=2
12:47:34.838 ->
<< OK
12:47:34.838 -> >> AT+UMNOPROF=1
12:47:34.838 ->
<< OK
12:47:34.885 -> >> AT+CFUN=15
12:47:34.885 ->
<< OK
12:47:36.125 -> >> AT+CPIN?
12:47:36.125 ->
<< timed out
12:47:41.212 -> >> AT+CPIN?
12:47:41.212 ->
<< AT+CPIN?

12:47:41.212 -> << +CPIN: READY
12:47:41.212 -> << OK
12:47:41.212 -> >> ATE0
12:47:41.212 ->
<< ATE0

12:47:41.259 -> << OK
12:47:41.480 -> << timed out
12:47:41.480 -> >> AT+URAT?
12:47:41.480 ->
<< +CME ERROR: Operation not supported
12:47:41.527 ->
12:47:41.527 ->
Sending message through UDP
12:47:41.527 -> >> AT+USOCR=17,16666
12:47:41.527 ->
<< +CME ERROR: No connection to phone
12:47:41.527 -> Failed to create socket

2

UPDATE:

I tried to send AT commands directly to the UBLOX module through the USB SARA MODEM connector. The result I got from there was positive.

I used the program m-center and the result is seen below. As seen the module automatically connects to the network without having the URAT issues. What I found is that if any AT commands is set (configuration) before an URAT command then I recieve an +CME ERROR.

All information that I needed to get this up and running was from: https://www.u-blox.com/sites/default/files/SARA-R4-N4-Application-Development_AppNote_(UBX-18019856).pdf

Now this just needs to be added to Sodaq_R4X.h / Sodaq_R4X.cpp

AT

AT

OK

ATE0

ATE0

OK

AT+COPS?

+COPS: 0,0,“Telia N Telia”,9

OK

AT+URAT?

+URAT: 8

OK

AT+CGDCONT?

+CGDCONT: 1,“IP”,“lpwa.telia.iot”,“10.81.170.165”,0,0,0,0

OK

AT+USOCR=17

+USOCR: 0

OK

AT+USOST=0,“195.34.89.241”,7,2,“AB”

+USOST: 0,2

OK

AT+USORF=0,2

+USORF: 0,“195.34.89.241”,7,2,“AB”

OK

AT+USOCL=0

OK

AT+CPWROFF

OK

3

Hi @Anders_Nor,

The new modules from ublox with the latest firmware require you to set the MNO Profile before you are able to set the URAT. You only need to do this once. You can do this with u-center or with the AT command.
ublox isn’t backward compatible.

We are working on an update for the Universal_Tracker to support the new firmware.
The library from v2.0.0 and up support the mno profiles.

I cannot attach zip files here, I will send you an email with out latest dev branch of the Universal_Tracker.
It should be ready, but we are still doing some final tests.

Best regards,
Jan