Using Telia APN the following is added after bsd_init()
AT+CGDCONT=0,"IP","lpwa.telia.iot"
However, this AT command sent on the AT socket fails with "ERROR". Does the FW support this - or can this command only be sent in "thin client" mode?
Using Telia APN the following is added after bsd_init()
AT+CGDCONT=0,"IP","lpwa.telia.iot"
However, this AT command sent on the AT socket fails with "ERROR". Does the FW support this - or can this command only be sent in "thin client" mode?
Hey, try putting the line "CONFIG_LTE_AUTO_INIT_AND_CONNECT=n" in .conf, and run modem_configure() after sending the +CGDCONT command.
That does not seem to result in any kind of change... Anything else that I should try?
The problem got worse with latest version of firmware - where also ibasis sim fails massively. The ibasis card will find Telenor as operator - but not select it - alas - no:
+CEREG: 1 OR +CEREG:1 OR +CEREG: 5 OR +CEREG:5 OR
So lte_lc.c init code hangs hard. This is the same if tested with telia sim with apn changed and AT%XSYSTEMMODE=0,1,0,0. Seems like telenor only supports band20. Will the modem figure this or should one try to lock the channel mask? What about Telia?
Latest Fw (.29-alpha) used and v0.4.0 for SDK.
The problem got worse with latest version of firmware - where also ibasis sim fails massively. The ibasis card will find Telenor as operator - but not select it - alas - no:
+CEREG: 1 OR +CEREG:1 OR +CEREG: 5 OR +CEREG:5 OR
So lte_lc.c init code hangs hard. This is the same if tested with telia sim with apn changed and AT%XSYSTEMMODE=0,1,0,0. Seems like telenor only supports band20. Will the modem figure this or should one try to lock the channel mask? What about Telia?
Latest Fw (.29-alpha) used and v0.4.0 for SDK.
Have you done any other modifications to the sample code? Or are you writing a project from scratch?