The problem is that when I set the value using the method in this post, the mangOH Yellow will not enter PSM after the active time I set, even the “status” already changed to “8 - PSM is enabled.”
I am using an AT&T LTE-M sim. I can confirm that the active time and PSM time I set are valid since they’re already tested on some other LTE-M/NB-IoT testbeds under the same network.
Has anyone successfully setup the PSM on this testbed? Any help will be much appreciated.
I just tried some commands but I found at!powerwake and at!powermode not working on my side. I can set the AT+CPSMS successfully, but still, it’s not going into PSM…
AT!POWERWAKE=1,108000
ERROR
at
OK
AT!POWERWAKE=?
ERROR
AT!POWERWAKE?
ERROR
AT!POWERMODE?
ERROR
AT+CPSMS?
+CPSMS:1,“00111110”,“00001000”
I reflashed the firmware and finally can set the timers and power mode. Here are the logs:
at!powermode?
!POWERMODE: mode=2-PSM_ONLY, status=8-PSM enabled
But I still feel confused about this PSM status. I couldn’t find any ‘sign’ of PSM mode even waited for a very long time. I can still send AT commands and get responses, the PDP context is also activated and the testbed can access the internet.
On other testbeds, they would just go completely power off when entered PSM. Did the testbed already enter PSM? If not, do I need to disconnect the USB and CON and use the battery?
I rechecked the log and I think I found the problem.
After I set up the PSM timer and active timer through AT!POWERWAKE (e.g AT!POWERWAKE=1,3600,30) and activate the PSM using AT!POWERMODE=2, the modem will try to process the timer setting, and there will be an error
" swimcu_active_time_attr_store: invalid input -1",
and the active timer will be reset to “2880”(maybe a default value). So it seems that the active timer I set is recognized as “invalid input”. But the value has no problem on other testbeds with the same SIM. It’s weird that CPSMS is correct, which means the modem did translation correctly (from integer to GPRS timer form).
Probably a firmware bug? Couldn’t find any information about this error code…