mfw 1.3.5, NCS 2.4.1
I received a
+CGEV: APNRATECTRL STAT 0,1,86307
from the modem.
I'm wondering, if that is processed by a pdn_event_handler_t.
If not, how does the application know that?
mfw 1.3.5, NCS 2.4.1
I received a
+CGEV: APNRATECTRL STAT 0,1,86307
from the modem.
I'm wondering, if that is processed by a pdn_event_handler_t.
If not, how does the application know that?
Hello Achim Kraus
currently there is no support for APN rate control notifications in the PDN library.
I will check if that can be added there and open a PR for that if possible.
Regardless, the application can subscribe to any AT notifications using the AT monitor library, which will also let you parse the AT command as necessary in your application to extract all the information you want from it.
Thanks!
One additional comment:
Using
AT%APNRATECTRL=0,0
helps also to read that. Once the rate limit is triggered, that's indicated there. The pain is unfortunately, if the modem is switched off CFUN=0 and one CFUN=1 again, that AT cmd reports inactive rate limit, but the modem continues to fail sending the data. If the device gets rebooted, it's able to send data again.
Not sure, what the nature of that "rate limit" should be. For now I only saw that from one SIM card provider. Maybe Nordic checks, what the right behavior for switching off and on would be. I guess either the modem should then continue to send data or the modem should continue to report, that the rate limit is triggered.
Thanks!
Please also try to forward my questions to the modem team. With the current API / implementation of the AT cmds, the "rate-limit" is more painful than helpful.
Thanks for the feedback. I have forwarded it to the team.
Hello Achim Kraus ,
the APN rate control feature is controlled by the network and not the device itself.
It is the network that toggles this feature to control how much data the device is allowed to send.
So the modem off/on will be required by the network spec?
OK, I guess, it's just an other "very useful" GSMA feature.
Hopefully is not used by too many SIM card-provider.
Solved with NCS 2.5.0
Solved with NCS 2.5.0