Using Sodaq SARA-AFF-R410M in Singapore

SARA AFF
1

Hi,
We are using Sodaq SARA-AFF-R410M in Singapore and since there is no Vodafone coverage here, I am trying with local SIM from M1. We have the NB-IOT SIM cards. I tried to enable band 8 as Singapore uses band 8, but the csq still always returns 99,99. Any input?
OK
AT+CSQ

+CSQ: 99,99

OK
AT+CREG?

+CREG: 0,0

OK

I have configured the band as below:

AT+UBANDMASK?

+UBANDMASK: 0,128,1,128

Regards,
PK

2

Hi @pkz,

This is indeed the way to enable only band 8

It can take a while before the modem sees the network.
Just give it a minute and send AT+CSQ again.

Some network don’t allow the force operator selection.
Use AT+COPS=0 to use the automatic operator selection.

Best regards,
Jan

3

Hi Jan,

Thanks for the reply.

It turns out that the URAT was 7. After changing to 8 and also changing to another SIM, it can now register.

Sander mentioned that I can get the souce code for pre-loaded firmware…
“The source code can be found on the following link:
pre-loaded firmware: Maker Software https://vodafoneiot.sodaq.com/quick-start/next-steps/ “

I don’t see the source code for pre-loaded firmware, it’s only binary (exe) that loads the firmware to the board.

Do you have the sketch for the pre-loaded firmware?
The reason is that changing the APN in setting does not work as we need IPV6 (the SIM we are using only supports IPV6).

Regards,
PK

4

Hi @pkz,

We are not allowed to share the sketch from Vodafone, only the upload tool to load the original software.

The most complete software we are allowed to share is the “Universal Tracker” sketch.
More info can be found on this page:
https://support.sodaq.com/Boards/Sara_AFF/Examples/universal_tracker/

Best regards,
Jan

5

Noted, Jan.

Thanks,
PK

7

Hi Jan,

I just noticed that the pre-loaded firmware and the one loaded by factory reset are not same!
I did factory reset to one board and here is the debug output:

VODAFONE MAKER 20181029.1
Booting up…

Commands:
AT Command Mode (CMD):
Init network (INIT):

Settings:
IMEI : 352753098583014
All Things Talk Token (att=): Db3Kgh68
Sensor Type (sty=): 0
Upload Interval (min) (sri=): 5
GPS Fix Timeout (sec) (gft=): 120
Minimum sat count (sat=): 6
APN (apn=): nb.inetd.gdsp
Force Operator (opr=): 20404
Network (LTE-M=7, NB-Iot=8) (rat=): 8
Band Mask (bnm=): 524288
Server URL/IP (url=): 40.68.172.187
Server port (prt=): 8891
GPS (OFF=0 / ON=1) (gps=): 0
Debug (OFF=0 / ON=1) (dbg=): 1
High temperature trigger (hgh=): 29
Low temperature trigger (low=): 10

On-the-move Functionality
Acceleration% (100% = 8g) (acc=): 25
Acceleration Duration (acd=): 0
Accelerator Trigger
Sensitivity (1-50) (act=): 10
Back-off time (sec) (bot=): 10

Enter command:

Wherease, the pre-loaded firmware gives:

SODAQ SARAR4 MAKER 20181029.1
Booting up…

Commands:
AT Command Mode (CMD):
GPS Dump (GPSDUMP):
Init network (INIT):

Settings:
IMEI : 352753098582834
Telco (tmobile=0, vf-n=1, vf-m=2, kpn=3, mono=4) (tlc=): 1
Upload Interval (min) (sri=): 5
GPS Fix Timeout (sec) (gft=): 120
Minimum sat count (sat=): 6
APN (apn=): nb.inetd.gdsp
Force Operator (opr=): 20404
Network (LTE-M=7, NB-Iot=8, 2G=9) (rat=): 8
Band Mask (bnm=): 524288
Server URL/IP (url=): 40.68.172.187
Server port (prt=): 8891
Send ATT header (OFF=0 / ON=1) (ahd=): 1
All Things Talk Token (att=): 6tu5XKGx
Payload type (0=cbor, 1=hex, 2=json) (pld=): 0
Temperature offset (tof=): 0
GPS (OFF=0 / ON=1) (gps=): 1
Debug (OFF=0 / ON=1) (dbg=): 1

On-the-move Functionality
Acceleration% (100% = 8g) (acc=): 25
Acceleration Duration (acd=): 0
Accelerator Trigger
Sensitivity (1-50) (act=): 10
Back-off time (sec) (bot=): 10

Enter command:

Also, I noticed most of the library for R4 does not support IPV6.
The telco we are using here in Singapore supports IPV6 only!
Do you know of any library with IPV6 support?

Regards,
PK

8

Hi @pkz,

We indeed only support IPv4 at the moment.
Our library is opensource https://github.com/SodaqMoja/Sodaq_R4X
A quick change for your project would be to hardcode change “IP” to “IPV6” and add also your IPv6 ip address there.

Thanks for reporting the issue that the pre-loaded firmware and firmware in the factory reset tool are not the same.
We will investigate the issue.

Best regards,
Jan