Best posts made by MarPi

Hi all,

I would like to share a small web tool to help you in T3412, T3324 - PSM - at+cpsms command generation and especially decoding.

As you might have recognized the mobile network is the master - has the last word regarding your PSM timer settings for your application. The device sends a PSM setting request via at+cpsms (in attach request and/or TAU) and the network will reply in the related accept message (reflected in at+cereg=4/at+cereg? output or URC) with the ‘granted’ value.
One reason for this is to prevent overload situations in the network if e.g. 10000 smart meters wake up from PSM at the same time in the same cell.

https://www.thalesgroup.com/en/markets/digital-identity-and-security/iot/resources/developers/psm-calculation-tool

Using the sliders on this page you can change your desired T3412 and T3324 values and copy the at+cpsms from the shown table.
In the buttom section you can enter the at+cpsms? command output as well as the at+cereg? output (after setting at+cereg=4) to get the values decoded. These are the value the network will finally use and your NB-Iot or CatM module has to use.

I hope it will help you a little bit.
Best regards,
Markus

@bertrik The most basic protocol which can be used @iotcreators.com from my point of view is NIDD or ‘nonIP’ (which is not really a protocol).
Using nonIP you will have no protocol overhead and from power consumption point of view this will be a benefit as well.
The sent data will, as usual, end up in the iotcreators backbone and can then be processed/pushed into a cloud.
Regarding the interval - collecting 3 measurements and sending them ev. 15 minutes is as well better for your power consumption in case you e.g. plan to operate a battery driven device somewhere in the woods.
BR, Markus

@Uta said in MFF2 + eSIM for IoT device (with end users owning subscriptions):

https://www.thalesgroup.com/en/markets/digital-identity-and-security/mobile/connectivity/esim/what-is-an-esim

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.

Hi @Stefan-de-Lange …from my point of view it might not be such a big difference if you look at a single shot.
But if you plan to operate a device with one battery lasting 7-10 years, every single saving is welcome.
I made measurements as well and as example for sending my 40Bytes of data I got:

           nonIP + RAI --> 0,303mWh
           nonIP       --> 0,314mWh
           UDP         --> 0,647mWh  (20Byte IP + 8Byte UDP header overhead)

But that might differ between different setups and scenarios.

Hi,
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:

./qcsuper.py --usb-modem /dev/ttyUSB0 --wireshark-live --decrypt-nas --reassemble-sibs --include-ip-traffic

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

You may try it!