Did the workshop last week in Hilversum where I got this board.
Got it working there and also back at work, but it is so annoying that I have to reset the board a couple of times before it will start recognizing the modem.
In other cases I get the error: No connection to phone, Failed to create socket.
This problem was known to the people at Sodaq. Is there a decent solution already?
Hopefully this issue is solved in the next version of the u-blox firmware.
We will send an email to all customers when a new firmware version is available.
Same issue here, very unstable behaviour of the SARA R412M that I recently bought.
I made a sketch to repeatedly run the same sequence of AT commands to check signal quality, connect to NB-IoT, send an HTTP get and disconnect again.
In 8 out of 10 times the connection setup fails (AT+CGACT=1) or UHTTPC for the GET request fails when having a good connection which makes it impossible to use in production environment
I totally agree that the R4 modules of ublox are not ready yet te be used in production.
I am in contact with Adelco, the Dutch supplier of ublox in The Netherlands about these issues.
We recently have received a new firmware version for the R412, we are currently testing this version.
We are not allowed to share firmware in an easy way.
Richard is very kind, he is willing to send everyone an email with the download url.
Richard has provided the FW update, thanks for that.
On the SODAQ website there’s a picture showing how to connect the 2nd USB for the FW installation, but that’s a Rev 1, while mine is a Rev 2 with different PCB layout and not the same solder points.
Can you provide details how to connect the USB for a R412M Rev 2 ?
For the older versions you need to load the passthrough sketch to turn on the module.
You need to use two usb cables, one connected to the regular usb port.
The 2nd USB needs to be soldered on to the back of the board.
That’s for the AFF form-factor, can you please provide the points for the SFF ?