Hi,
We are currently evaluating the NRF9151 for asset tracking using the AT firmware on the NRF9151 evk and an external MCU for the application firmware, emulating the final use case.
We have encountered this modem error several times: #XMODEM: SHUTDOWN,0 and would like to know if there are common causes for this we can investigate first, or we require setting up a trace to find the issue. We are resetting as needed to restart tracking, but we get a hole in the location data.
Unfortunately this has only been encountered during testing without tracing so far, while using the external MCU and AT firmware.
The setup in terms of AT commands looks like this:
AT
AT+CFUN=0
AT%XCONNSTAT=0
AT+CMEE=1
AT+CEREG=5
AT%MDMEV=1
AT+CESQ=1
AT+CEMODE=2
AT+CIND=1,1,1
AT+CSCON=1
AT+COPS=3,2
AT+CGEREP=1
AT%XPOFWARN=0,30
AT%XMODEMTRACE=0
AT%XSYSTEMMODE=1,0,1,1
AT+CPSMS=0
AT+CEDRXS=0
AT+CGDCONT=0,"IP","APN"
AT%XCOEX0=1,1,1570,1580
AT%XMAGPIO=1,1,1,1,7,1574,1577
AT+CFUN=1
AT#XSOCKET=1,1,0
AT#XSOCKETOPT=1,20,60
AT#XCONNECT="URL",PORT
AT#XNRFCLOUD=1
AT#XSMS=1,20,60
Then normal operation begins.
When this is recieved: #XNRFCLOUD: 1,0, we start the GNSS with: AT#XGPS=1,1,11
During normal operation we send GNSS positions (as they come) and AT%XMONITOR results (every 30 seconds) with AT#XSMS, and receive a few messages from our server.
The socket connection will be used in later testing as the primary communication line.
I hope to find some hints/help from you.
Note: I am going on holiday week 28 and 29.