Can not use NRF_SO_RAI_LAST with SLM/nRF9160

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Hakon — Tue, 18 Oct 2022 11:19:50 GMT

They commented;

Basically, afaik RAI_NO_DATA sends a dummy packet with an indication to the NW.
The problem is that the UDP socket is not connected, so libmodem doesn't know who to send the message to and -EDESTADDREQ is returned (as expected).
The solution is to connect the UDP socket thus setting the default destination for the datagram.

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Hakon — Wed, 12 Oct 2022 11:59:30 GMT

I have notified the modem team.

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Michal Mühlpachr — Mon, 10 Oct 2022 19:10:16 GMT

With prj.conf

CONFIG_LOG_DEFAULT_LEVEL=4

I got:

00> [00:00:00.487,182] <inf> nrf_modem_lib_trace: Trace tread ready
00> [00:00:00.494,537] <inf> nrf_modem_lib_trace: Trace level override: 2
00> *** Booting Zephyr OS build v3.1.99-ncs1  ***
00> 
00> [00:00:00.499,114] <inf> slm: Serial LTE Modem
00> [00:00:00.599,792] <inf> slm_at_host: at_host init done
00> [00:00:07.324,645] <inf> slm: Exit idle
00> [00:00:12.081,817] <err> slm_sock: setsockopt(50) error: -121

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Hakon — Mon, 10 Oct 2022 13:21:36 GMT

[quote user="michalm"]Did you (or modem team) tried to replicate issue?[/quote]

At the moment there seems to be a lack of SIM cards supporting the RAI functionality in the office, so I haven't been able to reproduce it. I will let you know if I can obtain one.

[quote user="michalm"]I will try to collect DBG, but there were another issue preventing that.[/quote]

You can also run the code through a debugger if that's a better option for you.

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Michal Mühlpachr — Mon, 10 Oct 2022 12:53:15 GMT

Are you (or modem team) able to use AT#XSOCKETOPT=1,50 in any working scenario without ERROR?

How do you test AT#XSOCKETOPT=1,50 before SLM release?

Did you (or modem team) tried to replicate issue?

I will try to collect DBG, but there were another issue preventing that.

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Hakon — Mon, 10 Oct 2022 11:15:43 GMT

You will need to to turn on logging in the application and put the log level to DBG.

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Hakon — Mon, 10 Oct 2022 11:14:19 GMT

That's fine. Are you gonna answer my question or not? I asked what function is returning the error, not what at cmd returns the error. Again, the modem team wants to know this.

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Michal Mühlpachr — Mon, 10 Oct 2022 09:37:34 GMT

Hi,

it is clear from AT dialogue, as you can see it in ticket already:
16.38 [TX] AT#XSOCKETOPT=1,50
16.38 [RX] ERROR

Why do you struggle to see that?

SO_RAI_LAST and SO_RAI_ONE_RESP works fine.

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Hakon — Mon, 10 Oct 2022 08:59:29 GMT

The modem team wants to know which function call is returning the error. Are you able to identify this?

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Michal Mühlpachr — Thu, 06 Oct 2022 01:43:55 GMT

Sure, attached.
devzone.nordicsemi.com/.../trace_2D00_2022_2D00_10_2D00_06T01_2D00_40_2D00_20.128Z.bin

[PPK2] DUT Powered, Measurement started
   0.15 <RESET> Thu Oct  6 03:40:23 2022
   1.02 [PPK2] 100k/s AVG   4.27 mA    Max  34.0  mA
   1.25 <INDICATE transition> -> High
   2.02 [PPK2] 100k/s AVG   2.75 mA    Max  30.5  mA
   3.02 [PPK2] 100k/s AVG   0.002mA    Max   0.008mA
   4.03 [PPK2] 100k/s AVG   0.002mA    Max   0.008mA
   5.02 [PPK2] 100k/s AVG   0.002mA    Max   0.008mA
   5.05 <WAKEUP>
   6.03 [PPK2] 100k/s AVG   1.33 mA    Max  24.3  mA
   6.42     [RX] Ready
   6.42 [TX] AT
   6.44     [RX] OK
   6.44 [TX] AT%XMODEMTRACE=1,2
   6.45     [RX] OK
   6.45 [TX] AT%MDMEV=1
   6.46     [RX] OK
   6.46 [TX] AT%HWVERSION
   6.47     [RX] %HWVERSION: nRF9160 SICA BQA
   6.47     [RX] OK
   6.47 [TX] AT%SHORTSWVER
   6.48     [RX] %SHORTSWVER: nrf9160_1.3.2
   6.48     [RX] OK
   6.48 [TX] AT#XSLMVER
   6.49     [RX] #XSLMVER: "2.1.0"
   6.49     [RX] OK
   6.49 [TX] AT%XPOFWARN=1,30
   6.51     [RX] OK
   6.51 [TX] AT%XSYSTEMMODE=0,1,0,0
   6.51     [RX] OK
   6.51 [TX] AT%REL14FEAT=1,1,1,1,0
   6.52     [RX] OK
   6.52 [TX] AT+CNEC=24
   6.54     [RX] OK
   6.54 [TX] AT+CMEE=1
   6.54     [RX] OK
   6.54 [TX] AT+CEPPI=1
   6.56     [RX] OK
   6.56 [TX] AT%RAI=1
   6.57     [RX] OK
   6.57 [TX] AT%XDATAPRFL=0
   6.57     [RX] OK
   6.59 [TX] AT%XNETTIME=1
   6.59     [RX] OK
   6.59 [TX] AT%XSIM=1
   6.61     [RX] OK
   6.61 [TX] AT+CEREG=5
   6.61     [RX] OK
   6.61 [TX] AT+CGEREP=1
   6.62     [RX] OK
   6.62 [TX] AT+CSCON=1
   6.64     [RX] OK
   6.64 [TX] AT%XTIME=1
   6.64     [RX] OK
   6.64 [TX] AT%XMODEMSLEEP=1,0,10240
   6.66     [RX] OK
   6.66 [TX] AT+CPSMS=1,,,"00111000","00000000"
   6.66     [RX] %XMODEMSLEEP: 4
   6.67     [RX] OK
   6.67 [TX] AT#XSLEEP=2
   6.67     [RX] OK
   7.02 [PPK2] 100k/s AVG   4.32 mA    Max  30.5  mA
   8.02 [PPK2] 100k/s AVG   0.025mA    Max   4.53 mA
   9.01 [PPK2] 100k/s AVG   0.021mA    Max   0.032mA
  10.01 [PPK2] 100k/s AVG   0.021mA    Max   0.032mA
  10.81 [PPK2] ====== SUM: INIT   0.004uA/h ======
  11.59 <WAKEUP>
  11.59     [RX] Ready
  11.69 [TX] AT%XMODEMTRACE=1,2
  11.71     [RX] OK
  11.71 [TX] AT%XBANDLOCK=1,"0000000000000000000000000000000000000000000000000000000000001000000010000000100010011010"
  11.74     [RX] OK
  11.74 [TX] AT+COPS=1,2,"23003"
  11.76     [RX] OK
  11.76 [TX] AT+CGDCONT=1,"IP","hardwario.com"
  11.76     [RX] OK
  11.76 [TX] AT+CFUN=1
  11.81     [RX] OK
  11.81     [RX] %XMODEMSLEEP: 4,0
  12.01 [PPK2] 100k/s AVG   5.65 mA    Max  51.2  mA
  12.73     [RX] %XSIM: 1
  12.73 [TX] AT+CGSN
  12.73     [RX] 352656106109476
  12.73     [RX] OK
  12.73 [TX] AT+CIMI
  12.74     [RX] 901288000012723
  12.74     [RX] OK
  13.01 [PPK2] 100k/s AVG  33.3  mA    Max  42.3  mA
  14.01 [PPK2] 100k/s AVG  31.2  mA    Max 383mA
  14.65     [RX] +CEREG: 2,"AE38","000AC51F",9
  14.99     [RX] +CSCON: 1
  15.01 [PPK2] 100k/s AVG  26.7  mA    Max 1021mA
  16.02 [PPK2] 100k/s AVG  37.2  mA    Max 256mA
  16.31     [RX] +CGEV: ME PDN ACT 0,0
  16.31     [RX] +CNEC_ESM: 50,0
  16.31     [RX] %MDMEV: SEARCH STATUS 2
  16.31     [RX] +CEREG: 5,"AE38","000AC51F",9,,,"00000000","00111000"
  16.33 [TX] AT+COPS?
  16.33     [RX] +COPS: 1,2,"23003",9
  16.33     [RX] OK
  16.33 [TX] AT%XCBAND
  16.33     [RX] %XCBAND: 20
  16.33     [RX] OK
  16.33 [TX] AT+CEINFO?
  16.35     [RX] +CEINFO: 0,1,C,8,1,-90,15
  16.35     [RX] OK
  16.35 [TX] AT+CGDCONT?
  16.36     [RX] %XTIME: ,"22016010048380","01"
  16.36     [RX] +CGDCONT: 0,"IP","hardwario.com","10.0.0.157",0,0
  16.36     [RX] +CGDCONT: 1,"IP","hardwario.com","",0,0
  16.36     [RX] OK
  16.36 [TX] AT#XDATACTRL=40
  16.36     [RX] OK
  16.36 [TX] AT#XSOCKET=1,2,0
  16.38     [RX] #XSOCKET: 0,2,17
  16.38     [RX] OK
  16.38 [TX] AT#XSOCKETOPT=1,50
  16.38     [RX] ERROR
  17.02 [PPK2] 100k/s AVG  36.5  mA    Max 218mA
  18.02 [PPK2] 100k/s AVG  36.8  mA    Max  50.6  mA
  19.02 [PPK2] 100k/s AVG  36.8  mA    Max  50.7  mA
  20.02 [PPK2] 100k/s AVG  36.0  mA    Max  50.7  mA

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Hakon — Tue, 04 Oct 2022 10:18:26 GMT

It's possible that your network does not support it. Can you do a modem trace so it can be checked?

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Michal Mühlpachr — Mon, 03 Oct 2022 23:43:22 GMT

Hi,

it is sufficient to just open UDP socket and do AT#XSOCKETOPT for SO_RAI_LAST to reproduce the issue.

I tested that with NCS 2.1.0, SO_RAI_LAST is 50 there based on https://github.com/nrfconnect/sdk-zephyr/blob/main/include/zephyr/net/socket_ncs.h#L58

Regards,
Michal

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Hakon — Thu, 22 Sep 2022 11:17:26 GMT

Hey. I have been out of office for 2 weeks now, so I haven't had much time to look at this. I will try to find some time to reproduce this in the near future.

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Michal Mühlpachr — Fri, 16 Sep 2022 00:19:10 GMT

Hello, is there any update on this issue please ?

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Michal Mühlpachr — Wed, 31 Aug 2022 19:51:21 GMT

Hello,

as you can see from AT dialogue above %SHORTSWVER: nrf9160_1.3.1, same behaviour with 1.3.2.

SIM is Vodafone as can see from AT dialogue above +COPS: 1,2,"23003",9.

You can probably find other useful info in attached AT dialogue also.

RE: Can not use NRF_SO_RAI_LAST with SLM/nRF9160

Hakon — Mon, 29 Aug 2022 09:05:27 GMT

Hello,

what modem firmware version and SIM are you using?