• State Verified Answer
  • Locked Locked
  • Replies 13 replies
  • Subscribers 87 subscribers
  • Views 2704 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 272683
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RAI feature with LTE-M and MQTT

Frikkie Badenhorst

Hi there,

We are currently conducting tests on the nRF9160 using the LTE Serial Modem app. We do however have issues testing the RAI feature on the device with an LTE-M network. The network does indeed support the RAI feature, as we have been able to test this using different devices.

According to the AT commands reference manual, the %XRAI command is not supported in a LTE-M network? Is that indeed the case?

We then refer to the %RAI (8.17 in AT commands reference manual) and %REL14FEAT (8.18). However, we are not able to use any of these 2 features? We continuously get the "ERROR" response when trying to active the REL 14 features. We have set CFUN to 0,1 and 4 to attempt this. 

Can you please assist with instructions on how to enable this feature on a LTE-M network so that we can test it? 

This is very urgent as we need to decide on which hardware we will use in our product today/Monday.

Parents
  • 0

    I the meantime, could you please provide me with a full application log showing the configuration attempts with both %RAI, %XRAI and %REL14FEAT and its responses? 

    According to the AT commands reference manual, the %XRAI command is not supported in a LTE-M network? Is that indeed the case?

    I might especially be interested in a log showing that %XRAI is supported when using a LTE-M network. 

    Thanks and regards,

    Markus

Reply
  • 0

    I the meantime, could you please provide me with a full application log showing the configuration attempts with both %RAI, %XRAI and %REL14FEAT and its responses? 

    According to the AT commands reference manual, the %XRAI command is not supported in a LTE-M network? Is that indeed the case?

    I might especially be interested in a log showing that %XRAI is supported when using a LTE-M network. 

    Thanks and regards,

    Markus

Children
  • 0 in reply to Albrecht Markus Schellenberger

    Hi Markus, 


    Fullscreen 1104.2021-07-02T10_08_15.439Z-log.txt Download 
    2021-07-02T10:08:17.332Z INFO Application data folder: C:\Users\..\pc-nrfconnect-linkmonitor
2021-07-02T10:08:17.366Z DEBUG App pc-nrfconnect-linkmonitor v1.1.10 official
2021-07-02T10:08:17.367Z DEBUG App path: C:\Users\FrikkieBadenhorst\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-07-02T10:08:17.367Z DEBUG nRFConnect 3.7.0, required by the app is (^3.6.0)
2021-07-02T10:08:17.367Z DEBUG nRFConnect path: C:\Users\..\resources\app.asar
2021-07-02T10:08:17.367Z DEBUG HomeDir: C:\Users\.......
2021-07-02T10:08:17.367Z DEBUG TmpDir: C:\Users\.........
2021-07-02T10:08:17.377Z VERBOSE Could not fetch serial number for serial port at COM6
2021-07-02T10:08:21.861Z INFO Modem port is opened
2021-07-02T10:08:21.873Z DEBUG modem >> AT+CFUN?
2021-07-02T10:08:21.913Z DEBUG modem << : 0
2021-07-02T10:08:21.917Z DEBUG modem << OK
2021-07-02T10:08:27.344Z DEBUG modem >> at+cereg=5
2021-07-02T10:08:27.359Z DEBUG modem << OK
2021-07-02T10:08:34.545Z DEBUG modem >> at%xrai?
2021-07-02T10:08:34.564Z DEBUG modem << %XRAI: 4
2021-07-02T10:08:34.566Z DEBUG modem << OK
2021-07-02T10:08:41.833Z DEBUG modem >> at+cfun=1
2021-07-02T10:08:41.885Z DEBUG modem << OK
2021-07-02T10:08:42.754Z DEBUG modem << +CEREG: 2,"0001","01A2D001",7,0,0,"11100000","11100000"
2021-07-02T10:08:43.015Z DEBUG modem << +CEREG: 1,"0001","01A2D001",7,,,"01001010","11100000"
2021-07-02T10:08:43.037Z DEBUG modem >> AT+COPS=3,2
2021-07-02T10:08:43.047Z DEBUG modem << OK
2021-07-02T10:08:43.052Z DEBUG modem >> AT+COPS?
2021-07-02T10:08:43.062Z DEBUG modem << +COPS: 0,2,"00101",7
2021-07-02T10:08:43.066Z DEBUG modem << OK
2021-07-02T10:08:43.088Z DEBUG modem >> AT%XCBAND
2021-07-02T10:08:43.101Z DEBUG modem << %XCBAND: 20
2021-07-02T10:08:43.106Z DEBUG modem << OK
2021-07-02T10:08:43.117Z DEBUG modem >> AT+CGDCONT?
2021-07-02T10:08:43.130Z DEBUG modem << +CGDCONT: 0,"IP","default","XXX.XXX.X.X",0,0
2021-07-02T10:08:43.132Z DEBUG modem << OK
2021-07-02T10:08:43.143Z DEBUG modem >> AT+CGACT?
2021-07-02T10:08:43.152Z DEBUG modem << +CGACT: 0,1
2021-07-02T10:08:43.166Z DEBUG modem << 
2021-07-02T10:08:43.168Z DEBUG modem << OK
2021-07-02T10:08:53.624Z DEBUG modem >> at+cfun=0
2021-07-02T10:08:53.768Z DEBUG modem << +CEREG: 0,"0001","01A2D001",7,0,0,"11100000","11100000"
2021-07-02T10:08:55.192Z DEBUG modem << OK
2021-07-02T10:08:58.786Z DEBUG modem >> at+cereg=5
2021-07-02T10:08:58.801Z DEBUG modem << OK
2021-07-02T10:09:11.186Z DEBUG modem >> AT%XRAI=0
2021-07-02T10:09:11.201Z DEBUG modem << OK
2021-07-02T10:09:14.738Z DEBUG modem >> AT%XRAI?
2021-07-02T10:09:14.754Z DEBUG modem << %XRAI: 0
2021-07-02T10:09:14.768Z DEBUG modem << OK
2021-07-02T10:09:19.249Z DEBUG modem >> AT+CFUN=1
2021-07-02T10:09:19.298Z DEBUG modem << OK
2021-07-02T10:09:20.194Z DEBUG modem << +CEREG: 2,"0001","01A2D001",7,0,0,"11100000","11100000"
2021-07-02T10:09:20.380Z DEBUG modem << +CEREG: 1,"0001","01A2D001",7,,,"01001010","11100000"
2021-07-02T10:09:20.388Z DEBUG modem >> AT+COPS=3,2
2021-07-02T10:09:20.399Z DEBUG modem << OK
2021-07-02T10:09:20.401Z DEBUG modem >> AT+COPS?
2021-07-02T10:09:20.411Z DEBUG modem << +COPS: 0,2,"00101",7
2021-07-02T10:09:20.414Z DEBUG modem << OK
2021-07-02T10:09:20.420Z DEBUG modem >> AT%XCBAND
2021-07-02T10:09:20.434Z DEBUG modem << %XCBAND: 20
2021-07-02T10:09:20.436Z DEBUG modem << OK
2021-07-02T10:09:20.441Z DEBUG modem >> AT+CGDCONT?
2021-07-02T10:09:20.457Z DEBUG modem << +CGDCONT: 0,"IP","default","XXX.XXX.X.X",0,0
2021-07-02T10:09:20.461Z DEBUG modem << OK
2021-07-02T10:09:20.478Z DEBUG modem >> AT+CGACT?
2021-07-02T10:09:20.489Z DEBUG modem << +CGACT: 0,1
2021-07-02T10:09:20.493Z DEBUG modem << OK
2021-07-02T10:09:53.640Z DEBUG modem >> at+cfun=0
2021-07-02T10:09:53.745Z DEBUG modem << +CEREG: 0,"0001","01A2D001",7,0,0,"11100000","11100000"
2021-07-02T10:09:55.224Z DEBUG modem << OK
2021-07-02T10:10:03.160Z DEBUG modem >> AT%XRAI?
2021-07-02T10:10:03.176Z DEBUG modem << %XRAI: 0
2021-07-02T10:10:03.178Z DEBUG modem << OK
2021-07-02T10:10:12.332Z DEBUG modem >> AT%RAI?
2021-07-02T10:10:12.347Z DEBUG modem << ERROR
2021-07-02T10:10:12.351Z ERROR Error: AT%RAI?
 failed
2021-07-02T10:10:26.716Z DEBUG modem >> AT%REL14FEAT?
2021-07-02T10:10:26.732Z DEBUG modem << ERROR
2021-07-02T10:10:26.733Z ERROR Error: AT%REL14FEAT?
 failed
2021-07-02T10:10:39.515Z DEBUG modem >> AT%REL14FEAT=1,0,0,0,1
2021-07-02T10:10:39.533Z DEBUG modem << ERROR
2021-07-02T10:10:39.535Z ERROR Error: AT%REL14FEAT=1,0,0,0,1
 failed
2021-07-02T10:16:04.072Z INFO Modem port is closed
2021-07-02T10:18:19.633Z INFO Restoring from C:\Users\..\pc-nrfconnect-linkmonitor\logs\2021-07-02T10_08_15.439Z-log.txt
     Here is a full at log of attemps to use the RAI functionality. We are able to use the XRAI feature, however we see no difference in the join power profiles (In the below profile, XRAI=4 in the first join as XRAI=0 in the seconds join - 4 seconds inactivity timer still present in both):

    With XRAI disabled, we then try to use the %RAI and %REL14FEAT commands with %XRAI set to 0. But as can be seen from the log, we are not able to even read these values.

    Maybe we are using the XRAI feature complete wrong? When exactly should we send the XRAI command to the modem?

Related
Terms of service