Thank you for your elaborate reply. I think I understand now. We produce a device which is aimed at staying in the same place so the choice for automatic selection seems most appropriate.
Kind regards, Maarten Wolzak
@trick2011 , to help you troubleshoot your problem, you can also refer to our docs here that explains eDRX: https://docs.iotcreators.com/docs/nb-iot-network-information, and also here on the official gsma website you can find infos about the edrx parameters in europe https://www.gsma.com/iot/mobile-iot/roaming/ . Also, to be able to send data to your device through eDRX, you will need to send at least one payload from the device to our platform, because the mobile network needs to know the ip address of your device in order to correctly forward the message through eDRX.
Hope this helps!
I want to share a tool which I love and I think it will be very useful for many of you using a cellular module which has a Qualcomm based chipset (like EXS82 and EXS62 from Thales or BG95,BG96 from Quectel or uBlox Sara R410 etc.). There is even an LTE dongle available having an open diagnostic port.
This tool for me is a substitute to the QXDM tool from QCT which has high license fees - this is why I even love it more:
It is called QCSuper available on Github.
It is a python based tool which is able to decode the debug interface stream.
A simple call like:
and a working wireshark installation is enough to start it.
It will show you all the NAS messages, SIBs, pagings and even the IP traffic sent from the module.
For some modules, the needed dignostic port (DM port) needs to be enabled by some extra at-cmds.
For Quectel it is e.g.:
to enable modem log ， pls send AT+QCFG="dbgctl",0
to disbale modem log ，pls send AT+QCFG="dbgctl",1
Maybe this is even the complete solution which is needed here.
With that solution, there is not even the need to pass the QRcode data to the application as the module will download the prepared profile using a QRcode entered on a web portal. Even a change later on to another provider is possible by assigning a new profile to the eUICC which is downloaded by the module later on.
hello, i have no direct experience with that but maybe you mean something like quecopen? i found this on the internet for the bg95 https://forums.quectel.com/t/bg95-m3-ciot-on-quecopen-latest-sdk/11574 , for further informations and software i suggest you to directly inquire quectel.
Hope this was useful a bit!
I recently discovered a book called “NB-IoT Use Cases and Devices”. It is focussing on device design aspects, esp. low consumption features of the NB-IoT network and how to leverage them. several network interface modules are being mentioned and reviewed, e.g. from Nordic, Telit, Quectel, u-blox. It helped me when I started my last project, so maybe you would like to look at it.
@magnatron yes this is a known bug unfortunately and we already requested a fix from our vendor. In case that the device is not functional at the moment or the device data aren’t forwarded to the correct application URL please send the IMEI to our support mailbox, we’ve got a workaround to fix it for you.
placing back the jumper to initial VEXT status - what is the behavior?
Pushing the ignition button can take 1-2secs until power LED is on.
You can repeat the flashing procedure to make sure it went well.
For update procedure there is the need to continuous power the serial levelshifters. That’s why the VEXT jumper should be moved to the 1st pin pair in “levelshifter” section.
The device will be started and powered as soon as you plug the USB cable into ASC0=serial FTDI.
After starting the update SW, push reset to trigger a restart of the device.
The update procedure will run in 4 parts.
ASC0 and TXD0 LEDs will start flashing for around ~6secs (core B will be updated).
A ~4secs pause will come next
ASC0 and TXD0 LEDs will start flashing for ~2secs followed by a small pause ~1sec.
Then core A will be flashed for ~6secs (ASC0 and TXD0 LEDs will be flashing).
After these sequences flashing tool should show 100%.
Then replace the jumper to intial VEXT and startup device normally.
Be aware, that entering the value via at+cpsms is only a request towards the network. The network decides if your values are committed. To check the network reply, use
and check the values via:
You can paste the reply in the above mentioned web page as well to get the values ‘decoded’.
My recommendation: set the active time (T3324) to a minimum and use the ‘RAI’ - release assistance indicator after sending data to shorten the RRC connected mode to a minimum. Then your device will enter PSM faster.