When will there be certification and support for the ublox SARA-N3? I’m trying to connect it to the network but the how-to is set up for N2 features that cannot be used for the N3.
Thanks for this question, I will try to find this information for you today.
@afzal_m did you find any information? I will be attending the hello world next friday so it would be awesome if the information to connect my sara n3 will be known then to the organizers so they can help me.
Not yet, in our internal organization we do not have experience with it yet. That will change soon!
I will ask if someone of Sodaq nows the commands for this module.
SODAQ will soon get the first boards with the prototype N3 modules.
We expect to have the production N3 modules and boards ready for the webshop at the end of July.
From that point we will support these new modules.
Since there is one command reference for the N2 and the N3 modules, I expect an easy software integration.
I will look into the differences between the N2 and N3 modules when I get my hands on the new hardware.
The first hardware with the N3 will be a SODAQ SARA SFF with the necessary modification to place the N3 module.
mmh that’s odd, I would’ve thought that SODAQ would’ve had a dev board early january already.
The main difference I found between the tutorial (N2) and the N3 is the move from
USOSTbut I haven’t figured out as how to connect it to the network.
@afzal_m is there any filtering happening based on the type of module that is trying to connect?
best regards Tarick
@trick2011 I have uBlox Sara N310 modules already for months in my products up and running, what would you like to know? In fact there are a lot of differences between the N211 and the N310!
@Inducon-Hans Thats great to hear, do you have the following startup and connection sequence?
+CFUN=0 +CGDCONT? +CGDCONT=1,\"IP\",\"cdp.iot.t-mobile.nl\" +CFUN=1 +COPS=1,2,\"20416\" +CGACT=1,1, +CGPADDR= +CGDCONT? // open UDP socket and transmit
from a factory default uBlox N311 this should do the job on the T-mobile NL network.
In fact you should only set the APN, not the country and network code. This makes it much more flexible.
// now the connection is open for a UDP datagram…
After sending: AT+USORF=0,127\r
You will get the following message, if data available
+USORF: 0,“172.27.131.100”,15683,17,“return message in ascii”\r\n
That seems weird as the manual states for the socket parameter:
SARA-N3 - The range goes from 1 to 8.
If I execute it on my sara-n3, I get:
+CME ERROR: Operation not supported. So I’m a bit confused.
@trick2011 I use the following sequence:
<rx socket number>
<wait for @>
<send user data>
AT+USORF=<socket>,127 #127 is max rx length, depends on yr buffers
+USORF: <socket>,“172.27.131.100”,15683,17,“downstream data”
AT+USOCL=<socket> # close socket