We don't get response of exit from data mode.

RE: We don't get response of exit from data mode.

dejans — Thu, 13 Jun 2024 11:09:21 GMT

Hi,

It is great to hear that you found the source of the problem. Thank you for the update.

Best regards,
Dejan

RE: We don't get response of exit from data mode.

Dmitry Krol — Thu, 13 Jun 2024 10:41:52 GMT

We found the problem in our side (We sent "+++" inside the trace)

RE: We don't get response of exit from data mode.

Dmitry Krol — Thu, 13 Jun 2024 09:10:56 GMT

Hi.

In order to compile it, I need to add "zephyr,console = &uart2;" to overlay, but it says compile error: "malformed value"

/ {
chosen {
ncs,slm-uart = &uart2;
zephyr,console = &uart2;
};
};

devicetree error: C:/ncs/v2.5.2/nrf/applications/serial_lte_modem/boards/nrf9160dk_nrf9160_ns.overlay:10 (column 19): parse error: malformed value

RE: We don't get response of exit from data mode.

dejans — Thu, 06 Jun 2024 19:56:17 GMT

Hi,

Could you please provide similar log to what you have already done and RTT traces (have a look at modem tracing with RTT) with Kconfig option CONFIG_SLM_LOG_LEVEL_DBG=y enabled?

Best regards,
Dejan

RE: We don't get response of exit from data mode.

dejans — Thu, 06 Jun 2024 08:26:12 GMT

Hi,

Thank you for providing the log. We will look into it internally. I will get back to you by the end of the next week at the latest.

Best regards,
Dejan

RE: We don't get response of exit from data mode.

Dmitry Krol — Tue, 04 Jun 2024 07:51:23 GMT

devzone.nordicsemi.com/.../live_5F00_log5.txt

RE: We don't get response of exit from data mode.

dejans — Fri, 31 May 2024 09:12:59 GMT

Hi,

Thank you for providing additional information.

Could you send your application log?

Best regards,
Dejan

RE: We don't get response of exit from data mode.

Ofir_A — Thu, 30 May 2024 09:38:43 GMT

Hi Dejan,

I'll try to elaborate the situation

Currently we are using MFW 1.3.5 with SLM 2.4.0 and we have no problem at all

We have 3 types of data sending (all of them are in data mode)

regular data

raw data

trace data

now we want to advance to SLM 2.5.2 and we encounter problems sending data in data mode

1. After sending number of messages we don't receive the confirmation of exiting data mode (we exit every message and then publish again the next message). the modem seems to stay in data mode since we receive the confirmation 3,0. we tried to resend the '+++' termination with no success. so in order to exit this mode we reset the modem and afterwards we not succeeding in transmission anything until we clear our data in flash (the modem never return data mode: 0 and not answering to AT ping command)

2. We occasionally receive error on the connection to MQTT or subscribe and we need to reset our product to resolve this until the next time

these 2 major problems didn't happen in SLM 2.4.0
So we would like to know what would be the reason to this

RE: We don't get response of exit from data mode.

dejans — Thu, 30 May 2024 09:02:05 GMT

Hi,

Can you elaborate what happens with the modem?

Best regards,
Dejan

RE: We don't get response of exit from data mode.

Dmitry Krol — Wed, 29 May 2024 13:57:17 GMT

From problem where we don't get "#XDATAMODE: 0" and modem stuck

RE: We don't get response of exit from data mode.

dejans — Wed, 29 May 2024 13:27:51 GMT

Hi,

[quote user=""]In order to exit from this problem, we need to rebuild our JSON data (resend doesn't help)[/quote]

If you look at MQTT client AT commands, you can see that <evt_type> 3 in the response syntax of #XMQTTPUB command represents the acknowledgement for the published message with QoS 1. Value 0 indicates success. In other words, there is no failure. From which specific problem do you try to exit? Can you elaborate?

Best regards,
Dejan

RE: We don't get response of exit from data mode.

Dmitry Krol — Wed, 29 May 2024 12:31:02 GMT

After that we don't get "#XDATAMODE: 0", modem doesn't respond to "AT" command. Reset modem is required