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

[Dmitry Krol]

Hi.

We moved to version 2.5.2. Here we encounter some problem with data mode. Sometimes we don't get response of exit from data mode.

We publish data, after we send "+++" and don't get "#XDATAMODE: 0", however we get  "#XMQTTEVT: 3,0"

In order to exit from this problem, we need to rebuild our JSON data (resend doesn't help)

Before in versions 2.1.2 and 2.4.0 everything worked fine.

[Dmitry Krol]

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

[dejans]

Hi,

In order to exit from this problem, we need to rebuild our JSON data (resend doesn't help)

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

[Dmitry Krol]

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

[dejans]

Hi,

Can you elaborate what happens with the modem?

Best regards,
Dejan

[Ofir_A]

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