This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SLM UDP proxy serial port

Hi

I'm testing the SLM application in nRF Connect SDK ver 1.3.1 on nRF9160 PDK ver 0.8.2 using the LTE Link Monitor v3.5.0

Giving the following commands, the UART stop working:

2020-10-07T11:30:58.750Z DEBUG modem >> at
2020-10-07T11:30:58.876Z DEBUG modem << OK
2020-10-07T11:31:03.833Z DEBUG modem >> AT+CFUN?
2020-10-07T11:31:03.957Z DEBUG modem << +CFUN: 0
2020-10-07T11:31:03.997Z DEBUG modem << OK
2020-10-07T11:31:05.703Z DEBUG modem >> AT+CFUN=1
2020-10-07T11:31:05.828Z DEBUG modem << OK
2020-10-07T11:31:13.421Z DEBUG modem >> at+cereg?
2020-10-07T11:31:13.539Z DEBUG modem << +CEREG: 0,1,"7851","0129B401",7
2020-10-07T11:31:13.578Z DEBUG modem << OK
2020-10-07T11:31:18.501Z DEBUG modem >> at#xudpcli=1,"xx.xxx.xx.xxx",xxxx
2020-10-07T11:31:18.618Z DEBUG modem << #XUDPCLI: 1 connected
2020-10-07T11:31:18.623Z DEBUG modem << OK
2020-10-07T11:31:22.477Z DEBUG modem >> at#xudpcli=0
2020-10-07T11:31:22.594Z DEBUG modem << OK
2020-10-07T11:31:25.456Z DEBUG modem >> at+cereg?
2020-10-07T11:31:25.575Z DEBUG modem << +CEREG: 0,1,"7851","0129B401",7
2020-10-07T11:31:25.614Z DEBUG modem << OK
2020-10-07T11:31:29.486Z DEBUG modem >> at#xudpcli=1,"xx.xxx.xx.xxx",xxxx
2020-10-07T11:31:29.606Z DEBUG modem << #XUDPCLI: 1 connected
2020-10-07T11:31:29.611Z DEBUG modem << OK
2020-10-07T11:31:31.755Z DEBUG modem >> at#xudpcli=0
2020-10-07T11:31:31.868Z DEBUG modem << OK
2020-10-07T11:31:34.931Z DEBUG modem >> at+cereg?
2020-10-07T11:31:35.931Z ERROR Error: 'at+cereg?
' timed out
 

Giving a proprietary AT cmd like at#xslmver work all the time:

2020-10-07T11:43:30.672Z DEBUG modem >> at
2020-10-07T11:43:30.678Z DEBUG modem << OK
2020-10-07T11:43:34.349Z DEBUG modem >> at+cereg?
2020-10-07T11:43:34.472Z DEBUG modem << +CEREG: 0,1,"7851","0129B401",7
2020-10-07T11:43:34.512Z DEBUG modem << OK
2020-10-07T11:43:38.357Z DEBUG modem >> at#xslmver
2020-10-07T11:43:38.471Z DEBUG modem << #XSLMVER: 1.2
2020-10-07T11:43:38.475Z DEBUG modem << OK
2020-10-07T11:43:41.016Z DEBUG modem >> at#xudpcli=1,"xx.xxx.xx.xxx",xxxx
2020-10-07T11:43:41.135Z DEBUG modem << #XUDPCLI: 1 connected
2020-10-07T11:43:41.139Z DEBUG modem << OK
2020-10-07T11:43:42.435Z DEBUG modem >> at#xudpcli=0
2020-10-07T11:43:42.555Z DEBUG modem << OK
2020-10-07T11:43:45.605Z DEBUG modem >> at#xslmver
2020-10-07T11:43:45.614Z DEBUG modem << #XSLMVER: 1.2
2020-10-07T11:43:45.728Z DEBUG modem << OK
2020-10-07T11:43:48.713Z DEBUG modem >> at#xudpcli=1,"xx.xxx.xx.xxx",xxxx
2020-10-07T11:43:48.828Z DEBUG modem << #XUDPCLI: 1 connected
2020-10-07T11:43:48.833Z DEBUG modem << OK
2020-10-07T11:43:51.361Z DEBUG modem >> at#xudpcli=0
2020-10-07T11:43:51.476Z DEBUG modem << OK
2020-10-07T11:43:53.397Z DEBUG modem >> at#xslmver
2020-10-07T11:43:53.405Z DEBUG modem << #XSLMVER: 1.2
2020-10-07T11:43:53.409Z DEBUG modem << OK
2020-10-07T11:43:56.797Z DEBUG modem >> at#xudpcli=1,"xx.xxx.xx.xxx",xxxx
2020-10-07T11:43:56.919Z DEBUG modem << #XUDPCLI: 1 connected
2020-10-07T11:43:56.925Z DEBUG modem << OK
2020-10-07T11:43:57.844Z DEBUG modem >> at#xudpcli=0
2020-10-07T11:43:57.976Z DEBUG modem << OK
2020-10-07T11:44:01.346Z DEBUG modem >> at#xslmver
2020-10-07T11:44:01.464Z DEBUG modem << #XSLMVER: 1.2
2020-10-07T11:44:01.468Z DEBUG modem << OK

Is there a way to allow for standard AT cmd's after the UDP proxy has been enabled/disabled?

Parents
  • Hello, Bard!

    My apologies for the lack of support on this case. I have started a process with the developers on hunting down the bug, and I'm looking at possible workarounds myself. It seems to be related to the UDP-commands locking up at_cmd.h, but that was probably clear to you aswell.

    I was also just informed that it could be an issue with your development kit version, so Magnus should have arrangef for a new one to be shipped to you.

    Will come back with more updates shortly.

    Best regards and thank you for the patience,
    Carl Richard

Reply
  • Hello, Bard!

    My apologies for the lack of support on this case. I have started a process with the developers on hunting down the bug, and I'm looking at possible workarounds myself. It seems to be related to the UDP-commands locking up at_cmd.h, but that was probably clear to you aswell.

    I was also just informed that it could be an issue with your development kit version, so Magnus should have arrangef for a new one to be shipped to you.

    Will come back with more updates shortly.

    Best regards and thank you for the patience,
    Carl Richard

Children
No Data
Related