issue in Serial LTE Modem v22.04

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Wed, 24 Jun 2020 08:11:10 GMT

Hi Praveen,
The features requested are now in NCS: https://github.com/nrfconnect/sdk-nrf/pull/2508

Please update to the latest master to get the features.
For your convenience I have made a precompiled .hex --> devzone.nordicsemi.com/.../slm_5F00_tcp_5F00_proxy_5F00_24_5F00_06.hex

Now support for:

AT#XTCPRECV

AT#XTCPCLI?

AT#XTCPSVR?

Here you can see how the new commands functions:

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Fri, 12 Jun 2020 13:04:20 GMT

Thanks for the feedback.
We are working on getting this in the Serial LTE Application, should come a Pull Request in the near future to address this.

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Fri, 29 May 2020 12:45:41 GMT

Hi Martin,

1. For this unsolicited RX data, is it possible to have "OK" string at the end.

As in our application we will copy data which is between #XTCPRECV: <datatype>, <size> and OK string.

2. Is it possible to support these commands also

AT#XTCPSVR?

AT#XTCPCLI?

which will help us to know whether server is started or already client is connected to server.

What happening is after few minutes of enabling server or client, we are not able to know whether server is running or client - server connection is still active. If we give command to start server or client mode getting error as a response.

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Fri, 29 May 2020 11:00:29 GMT

Hi Praveen,

TCP Client:
1.

From the documentation:

Data receiving is automatic, report to client as:
#XTCPRECV: <datatype>, <size>
<data>

So the RX data are considered "unsolicited data" so therefore it does not have "OK/ERROR".

The command AT#XTCPCLI? is an unsupported command, so therefore it throws an error when issuing it.

TCP Server:

The same applies here as described in 1. for TCP Client

2.
The command AT#XTCPSVR? is an unsupported command, so therefore it throws an error when issuing it.

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Thu, 28 May 2020 14:46:31 GMT

Hi Martin,

Today I got chance to test proxy TCP AT commands with the hex file SLM_tcpproxy_ftp_28_05.hex shared.

Below are our AT commands responses and their observations

TCPIP Client AT commands and responses: (nRF9160 is client and Hercules is in server mode)

Hercules Utility info: https://www.hw-group.com/software/hercules-setup-utility

AT#XTCPCLI?

ERROR

AT#XTCPCLI=?

#XTCPCLI: (0, 1),<url>,<port>,<sec_tag>

AT#XTCPCLI=1,"192.168.1.21",50505

#XTCPCLI: 2 connected

AT#XTCPSEND=1,"Hi Server"

#XTCPSEND: 9

#XTCPRECV: 1, 12 // Receiving message from server directly without URC. We have to read #XTCPRECV: string

Hello client // There is no “OK” string indicating end of data or command response.

#XTCPRECV: 1, 14

Hello client-1

#XTCPRECV: 1, 14

Hello client-1

AT#XTCPSEND=1,"Hi Server"

#XTCPSEND: 9

AT+CESQ

+CESQ: 99,99,255,255,28,77

AT#XTCPCLI=0 //Connection closed

AT#XTCPSEND=1,"Hello Server" //Error expected as Connection closed

ERROR

TCPIP Server AT command responses: (nRF9160 is server and Hercules is client)

AT#XTCPSVR=1,50505

#XTCPSVR: 1 started // Device is server mode.

#XTCPSVR: 192.168.1.21 connected // Client request Connection accepted automatically

AT#XTCPSEND=1,"hELLO"

#XTCPSEND: 5

#XTCPRECV: 1, 5

Hello // There is no “OK” string indicating end of data or command response

#XTCPRECV: 1, 5

hello

#XTCPRECV: 1, 5

hello

#XTCPRECV: 1, 5

hello

AT#XTCPSVR=0,50505 //Server session closed

TCPIP client Observations:

1.After client is connected to server, Data is automatically received from server. Client received data in the format:

#XTCPRECV: 1, 12

Hello client

There is no “OK” string at the end of data from the server to client.We expect "OK" string at the end of response. In other vendors radio modules like Telit we use to get OK after response.

We are expecting response like shown below, if data sent by server to Client:

#XTCPRECV: 1, 12\r\n

Hello client\r\n

OK\r\n

2.Status check AT command AT#XTCPCLI? is throwing error, due this not able to know whether module is already connected to server or not.

TCP server Observations:

1. Data sent by client is automatically received, no receive AT command. Note that there is no “OK” string at the end of data from client to server. Same expectation as mentioned in TCP client observation.

2.Status check AT command AT#XTCPSVR? is throwing error, due this not able to know whether server session is already started or not.

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Wed, 27 May 2020 10:22:22 GMT

Hi Praveen,
It's under development and not yet released.
I will provide you the draft over mail.

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Wed, 27 May 2020 08:21:21 GMT

Hi Martin,

Can you please share the update TCP proxy AT command document to test the shared build.

with regards,

Praveen P

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Mon, 25 May 2020 13:17:28 GMT

Hi Praveen,
I am very sorry for the confusion.
You should not use need to use xsend/xrecv, but instead the commands for when enabled TCP proxy service.

AT#XTCPSVR=<op>[,<port>[,[sec_tag]]
AT#XTCPCLI=<op>[,<url>,<port>[,[sec_tag]]
AT#XTCPSEND=<datatype>,<data>

Attached is a precompiled Serial LTE modem .hex with TCP proxy enabled (and the fix from earlier).

devzone.nordicsemi.com/.../serial_5F00_lte_5F00_modem_5F00_25_5F00_05_5F00_tcpproxy.hex

Please flash this one and do the following when testing the TCP client with your server:

Ready
at+cfun=1
OK
at+cereg?
+CEREG: 0,5,"0CE9","02151012",9
OK
at#xsocket=1,1,0
#XSOCKET: 1, 1, 0, 6
OK
AT#XTCPCLI=1,"77.68.25.xxx", 50xxx
#XTCPCLI: 2 connected
OK
AT#XTCPSEND=1,"hello from client"
#XTCPSEND: 18
OK
#XTCPRECV: 1, 18
hello from client

Here you can see that you get a response automatically and do not have this blocking effect as you see with #xrecv

I will share some updated documentation as soon as possible that describes this in more detail.

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Fri, 22 May 2020 10:43:18 GMT

Hi Martin,

There was some firewall issue in our setup at office due to this we are unable to open any TCP IP port.

We sorted it out and now we are able to open TCP IP client socket and also TCP server socket and also able to send data to and fro.

We are having few observation in serial LTE modem build shared by nordic recently-serial_lte_modem_15_05.hex

In TCP IP Client mode, after establishing connection with server.When data is sent by server we are not receiving any message saying data received in buffer from server.

AT#RECV command is in waiting/polling mode to receive data from server, in this mode we are not able to send any other AT command until data received from the server.

From the LOGS below:

2020-05-22T06:24:10.009Z DEBUG modem >> at#xsocket?\x0D\x0A
2020-05-22T06:24:10.020Z DEBUG modem << #XSOCKET: 0\x0D\x0A
2020-05-22T06:24:10.022Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:24:19.240Z DEBUG modem >> at#xsocket=1,1,0\x0D\x0A
2020-05-22T06:24:19.257Z DEBUG modem << #XSOCKET: 1, 1, 0, 6\x0D\x0A
2020-05-22T06:24:19.259Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:24:46.875Z DEBUG modem >> at#xconnect="192.168.1.21",50505\x0D\x0A
2020-05-22T06:24:47.564Z DEBUG modem << #XCONNECT: 1\x0D\x0A
2020-05-22T06:24:47.567Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:25:12.344Z DEBUG modem >> at#xsend=1,"Hello server"\x0D\x0A
2020-05-22T06:25:12.365Z DEBUG modem << #XSEND: 12\x0D\x0A
2020-05-22T06:25:12.367Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:25:44.508Z DEBUG modem >> at#xrecv\x0D\x0A
2020-05-22T06:25:44.524Z DEBUG modem << Hello serverHello clientHello client\x0D\x0A
2020-05-22T06:25:44.526Z DEBUG modem << #XRECV: 1, 36\x0D\x0A
2020-05-22T06:25:44.528Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:26:16.828Z DEBUG modem >> at#xrecv\x0D\x0A
2020-05-22T06:26:17.830Z ERROR Error: 'at#xrecv
' timed out
2020-05-22T06:27:05.478Z DEBUG modem << Hello client\x0D\x0A
2020-05-22T06:27:05.482Z DEBUG modem << #XRECV: 1, 12\x0D\x0A
2020-05-22T06:27:05.485Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:27:20.032Z DEBUG modem >> at#xsocket=0\x0D\x0A
2020-05-22T06:27:20.050Z DEBUG modem << #XSOCKET: 0, closed\x0D\x0A
2020-05-22T06:27:20.054Z DEBUG modem << OK\x0D\x0A

The same with the TCP IP server mode, there is no indication that data is in buffer to read.

2020-05-22T06:30:35.550Z DEBUG modem >> at#xsocket=1,1,1\x0D\x0A
2020-05-22T06:30:35.568Z DEBUG modem << #XSOCKET: 1, 1, 1, 6\x0D\x0A
2020-05-22T06:30:35.570Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:30:52.047Z DEBUG modem >> at#xbind=50505\x0D\x0A
2020-05-22T06:30:52.105Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:31:18.767Z DEBUG modem >> at#xlisten\x0D\x0A
2020-05-22T06:31:18.783Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:32:35.143Z DEBUG modem >> at#xaccept\x0D\x0A
2020-05-22T06:32:35.156Z DEBUG modem << #XACCEPT: connected with 192.168.1.21\x0D\x0A
2020-05-22T06:32:35.158Z DEBUG modem << #XACCEPT: 2\x0D\x0A
2020-05-22T06:32:35.159Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:33:30.071Z DEBUG modem >> at#xrecv\x0D\x0A
2020-05-22T06:33:31.071Z ERROR Error: 'at#xrecv
' timed out
2020-05-22T06:33:44.865Z DEBUG modem << hello\x0D\x0A
2020-05-22T06:33:44.884Z DEBUG modem << #XRECV: 1, 5\x0D\x0A
2020-05-22T06:33:44.890Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:34:05.331Z DEBUG modem >> at#xsend=1,"Hello"\x0D\x0A
2020-05-22T06:34:05.346Z DEBUG modem << #XSEND: 5\x0D\x0A
2020-05-22T06:34:05.348Z DEBUG modem << OK\x0D\x0A
2020-05-22T06:39:03.189Z DEBUG modem >> at#xsocket=0\x0D\x0A
2020-05-22T06:39:03.205Z DEBUG modem << #XSOCKET: 0, closed\x0D\x0A
2020-05-22T06:39:03.209Z DEBUG modem << OK\x0D\x0A

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Wed, 20 May 2020 09:08:06 GMT

Hi Praveen,
I am not familiar with that setup.

Please follow the instructions given in the link provided in my last reply, since that is what we have tested and know works, then if you have any issues with that we can much easier support you.

BR,
Martin L.

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Wed, 20 May 2020 08:40:51 GMT

Hi Martin,

Checked at server it is not closed.Its in listening mode.

We are using Hercules application- TCP server as shown in below picture.

Here I am also attaching our Call-box profile file. Please rename the file to *.dfl

devzone.nordicsemi.com/.../kk_5F00_nRF91.txt

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Wed, 20 May 2020 06:14:47 GMT

Hi Praveen,
Please follow the instructions given here:

https://devzone.nordicsemi.com/f/nordic-q-a/60456/ftp-support-for-nrf9160/250823#250823

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Tue, 19 May 2020 18:04:07 GMT

Hi Praveen,
I just tested on a live network with my own TCP server:

Here you can see the server connects and receives the message from the TCP client.

However, if I shut down the TCP server and try to connect, I get the same error as you see:

XSOCKET: -116. closed

So please make sure that you have a TCP server up and running that has the correct port open.

We will also replicate this on the callbox, but this may help you a bit comparing live network results vs. callbox.

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Tue, 19 May 2020 13:16:01 GMT

In addition to my previous response, TCP server is working fine.Attached complete log for referencedevzone.nordicsemi.com/.../2020_2D00_05_2D00_19T06_5F00_34_5F00_09.339Z_2D00_log.txt

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Tue, 19 May 2020 13:14:35 GMT

Hi Martin,

I have flashed the HEX file serial_lte_modem_15_05.hex and tried to test TCP CLient AT commands, but was not successful. Yes, the given hex file is not hanging with AT+CFUN=0.

I am facing the issue with TCP CLIENT devzone.nordicsemi.com/.../serial_5F00_lte_5F00_modem_5F00_15_5F00_05_2D00_log.txtat the AT command AT#XCONNECT="IP address",Port

at#xconnect="192.168.1.80",3442\x0D\x0A
#XSOCKET: -116, closed\x0D\x0A
ERROR\x0D\x0A

I have tried to activate PDP contect with IP4 only but still the same problem at AT#XCONNECT at command.

Attached complete log for your reference.

Have you faced the same issue at your end with call box?

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Tue, 19 May 2020 07:40:10 GMT

Hi Praveen,
It could be the issue, (we will verify it today on a callbox as well) but I would recommend using this version: devzone.nordicsemi.com/.../serial_5F00_lte_5F00_modem_5F00_15_5F00_05.hex
Since it does not hang the serial communication if you get an error.

The error CME:3 means "Operation not allowed", but please retry to activate PDP Context with IPv4 only when the modem is OFF (AT+CFUN=4) and when you turn it ON (AT+CFUN=1) it should use the updated CGDCONT values.

Please provide the full log output if you have any issues.

Best regards,

Martin L.

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Mon, 11 May 2020 04:23:35 GMT

Hi Martin,

Any update for me regarding this.

with regards,

Praveen P

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Thu, 30 Apr 2020 14:13:44 GMT

Hi Martin,

I checked AT+CGDCONT AT command response

AT+CGDCONT?\x0D\x0A
+CGDCONT: 0,"IPV4V6","cmw500.rohde-schwarz.com","192.168.1.30 FC01:ABAB:CDCD:EFE0:0000:0000:0000:0001",0,0\x0D

I found that R&S CMW500 BTS is assigning IP address to module as highlighted above.

It is combine IP address of IPV4 and IPV6. I was able to put break point .in do_connect() function in serial LTE monitor and found that due to this combined IP address it is returning with error as not a valid IP format.

Do you think is this the problem?

Why IP address assigned to module is combined IPV4 and IPV6 "192.168.1.30 FC01:ABAB:CDCD:EFE0:0000:0000:0000:0001".

I tried to set to:

AT+CGDCONT = 0,"IP","cmw500.rohde-schwarz.com"

but received CME: 3 error and hanged serial communication.

With regards,

Praveen

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Thu, 30 Apr 2020 06:52:07 GMT

Hi Praveen,

Since we are able to get it working on the live network at our side, we will get a hold on a CMW500 to try to reproduce the issue you are seeing.

note:

The reason xbind command worked in NCSv1.2 is that it binds to any address (local.sind_addr.s_addr = htonl(INADDR_ANY);)

Later introduced in master branch is the support of TCP/IP server, where the Serial LTE modem sample (the sample attached in this thread) uses modem info to fetch the allocated IPv4 address and bind to it. So in your test case, the nRF91 might not get a valid IPv4 address.

(hence output log:

[00:12:56.948,455] [1;31m<err> tcpip: Invalid local address

This can be verified with the standard AT command: AT+CGDCONT?

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Tue, 28 Apr 2020 12:46:54 GMT

Hi Martin,

I have flashed debug_serial_lte_modem_27_04.hex file and tried TCP server mode, its failing at same AT command, AT#XBIND=5003.

I am attached log generated from serial tool for your reference.

devzone.nordicsemi.com/.../serial_5F00_ATCommand_5F00_Log_5F00_v27_5F00_04.txt

I got update from R&S CMW500 BTS support team is that, , The available port’s are 5001 to 5008.

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Mon, 27 Apr 2020 13:57:47 GMT

SIDENOTE:

Attached [[View:/cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-3c79b4b8fd1e4f4c8a9faf9bece29cc2/debug_5F00_tcp_5F00_proxy_5F00_serial_5F00_lte_5F00_modem_5F00_27_5F00_04.hex:320:240]] Is the Serial LTE modem application that supports TCP Server Proxy. (added CONFIG_SLM_TCP_PROXY=y in prj.conf)

Here is a TCP server proxy sample:

Test TCP server with TCP proxy service:



at#xtcpsvr=?

#XTCPSVR: (0, 1),<port>,<sec_tag>

OK

at#xtcpsvr=1,3442    //The TCP Server proxy do bind() in the server start command

#XTCPSVR: 2 started

OK

#XTCPSVR: 5.189.130.26 connected

#XTCPRECV: 1, 13

Hello, TCP#1!

#XTCPRECV: 1, 13

Hello, TCP#2!

at#xtcpsend=1,"TCP1/2 received"

#XTCPSEND: 15

OK

#XTCPRECV: 1, 13

Hello, TCP#3!

#XTCPRECV: 1, 13

Hello, TCP#4!

#XTCPRECV: 1, 13

Hello, TCP#5!

at#xtcpsend=1,"TCP3/4/5 received"

#XTCPSEND: 17

OK

at#xtcpsvr=0

OK

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Mon, 27 Apr 2020 12:48:10 GMT

Hi Praveen,
Yes, I would assume that the CMW500 has control/settings with regards to the available local ports.

From what I know you have this "Data Application Unit" in the callbox which is it's own part on the CMW500 that handles the IP layer. It also has its own ethernet port that you can hook up to the network. One other thing you need to take care of is that the Callbox is switched to "Data/application mode" and not "Test mode".

The modem firmware version should not have an effect on this exact issue, you should get it working with the 1.1.1 as well.

Please flash this application and run through the same commands, it should provide a much better log output. (please share the log output)devzone.nordicsemi.com/.../debug_5F00_serial_5F00_lte_5F00_modem_5F00_27_5F00_04.hex

(For reference, these are the changed prj.conf configurations:)

CONFIG_USE_SEGGER_RTT=n
CONFIG_RTT_CONSOLE=n
CONFIG_UART_CONSOLE=y
CONFIG_LOG_BACKEND_RTT=n
CONFIG_LOG_BACKEND_UART=y

CONFIG_BSD_LIBRARY_TRACE_ENABLED=y
CONFIG_SLM_LOG_LEVEL_DBG=y

RE: issue in Serial LTE Modem v22.04

praveenpalaparthi — Mon, 27 Apr 2020 12:26:33 GMT

Hi Martin,

Is the port number related to CMW500?

What I observed from your log is that your radio firmware version is:

AT+CGMR
mfw_nrf9160_1.2.0

where as my radio firmware version is

AT+CGMR
mfw_nrf9160_1.1.1

Will this make any difference.

RE: issue in Serial LTE Modem v22.04

Martin Lesund — Mon, 27 Apr 2020 12:00:25 GMT

Hi Praveen,

Here you can see my output testing the same exact application on a live network:

From your output, you are not connected to a live network, but a CMW500 callbox, and I, therefore, think that the reason why you cannot at#xbind ("bind the socket to a local port") maybe because of some settings in the callbox. I would assume you may need to allow/set up that local port in the CMW500.