Weird output from serial port

RE: Weird output from serial port

Håkon Alseth — Tue, 05 Dec 2023 08:34:29 GMT

Hi Ivan,

Thank you for summarizing. I'm glad to hear that you got things working with a newer version.

[quote user="Ivan Popov"]As for the sample build - after the build with the 2.5.0 version was successful I haven't tried to go back and test if would fail again with the 2.4.x versions - should I?[/quote]

If you have a working setup with a newer NCS version, I would recommend that you go forward with this one.

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Mon, 04 Dec 2023 12:52:10 GMT

Hi Håkon,

Let me summarise the issues I had while you were helping me:

The weird output in the Serial Terminal - it was quickly revealed that it was a misconfiguration on my side and I was trying to use an already occupied (or wrong) port.
The build failure of the Asset Tracker sample (with Thingy:91 as a target board) - the SDK/toolchain upgrade (to v.2.5.0) solved exactly that - this time the build failure just didn't happen and I was able to flash the resulting HEX file on the Thingy:91. As a result I'm able to see the default telemetries being uploaded to our system through the AWS IoT Core. Next step for me here is to enable the suppressed by default sampling of the ADXL362 accelerometer for the simplest possible use case but that is another story.
The inability of the Thingy:91 to connect to the AWS cloud despite the fact that everything was configured by-the-book - here you helped to find out that our certificate policy was too restrictive, and after fixing that I closed the ticket.

As for the sample build - after the build with the 2.5.0 version was successful I haven't tried to go back and test if would fail again with the 2.4.x versions - should I?

Regards,

Ivan

RE: Weird output from serial port

Håkon Alseth — Mon, 04 Dec 2023 12:32:19 GMT

Hi Ivan,

[quote user="Ivan Popov"]

I'm not reopening the ticket, I just have a thing to share. Last week after I switched to version 2.5 of the SDK and the toolchain I was already able to flash a customised version (AWS IoT enabled) of the Asset Tracker v2. The build passed successfully.

Any idea what have changed?

[/quote]

When you updated to ncs v2.5.0, did everything work as expected? Were you still having issues on ncs v2.4.x, and updating to ncs v2.5.0 fixes those issues?

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Mon, 04 Dec 2023 08:55:47 GMT

Hello Håkon,

Any idea what have changed?

Best regards,

Ivan

RE: Weird output from serial port

Ivan Popov — Thu, 26 Oct 2023 13:42:03 GMT

Thank you very much, Håkon!

On a first glance this guide looks promising - I'll dig into it.

Thanks for all your support and best of luck!

Best regards,

Ivan Popov

RE: Weird output from serial port

Håkon Alseth — Thu, 26 Oct 2023 13:35:21 GMT

Hi Ivan,

I'm glad to hear that you were able to get a successful connection towards AWS!

[quote user="Ivan Popov"]

Now this seems to resolve our problem and I see two further points to follow:

Modify the policy in order to make it more restrictive to the point where it has the minimum rights that let the device connect properly.
To see how to add the telemetry data from the sensors to the output ... I saw somewhere an example withe the older version of the Asset tracker (v1.6) - it probably should be enough. (I'd appreciate if you can confirm this.)

But these are further steps, and since we already have the basic connectivity I think the current issue is resolved. And if you don't have anything else to add I can close the ticket?

[/quote]

I just want to mention that there are some limited information on handling user data in this guide:

Connecting to AWS cloud services using the nRF9160

See the chapter named "Handling MQTT messages in AWS".

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Wed, 25 Oct 2023 07:32:07 GMT

Hello Håkon,

I spoke to my colleague responsible for the AWS infrastructure and (this time) we both looked at the instructions from the article you shared. We found difference only in the given policy example. We provided to our policy the options from the given example (the least restrictive variant!) and the result can be seen bellow (in ST and in our system):

Now this seems to resolve our problem and I see two further points to follow:

Modify the policy in order to make it more restrictive to the point where it has the minimum rights that let the device connect properly.
To see how to add the telemetry data from the sensors to the output ... I saw somewhere an example withe the older version of the Asset tracker (v1.6) - it probably should be enough. (I'd appreciate if you can confirm this.)

But these are further steps, and since we already have the basic connectivity I think the current issue is resolved. And if you don't have anything else to add I can close the ticket?

Best regards,

Ivan

RE: Weird output from serial port

Håkon Alseth — Tue, 24 Oct 2023 14:10:22 GMT

Hi Ivan,

It is a certificate generated from aws iot core, just from a different account (thus different client/private key, root ca is the same), where the guide here is followed:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/libraries/networking/aws_iot.html#setting-up-aws-and-configuring-permissions

[quote user="Ivan Popov"]Then if I continue to have the same problem, what would that mean? That the procedure under which I register the devices towards AWS is somewhat flawed, for instance? Something with the policies probably? [/quote]

It is hard to say what can be the root problem. Have you checked that all the steps in the above link is performed?

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Mon, 23 Oct 2023 13:50:06 GMT

Hi Håkon,

[quote user="hkn"]Are you 100% certain that the credentials, static client id, and hostname is correct?[/quote]

Checked them around fifty times - for every of the two devices I registered. Moreover the other types of devices we test with (some Shellys, an M5Stack unit, some Pythons scripts) work under the same conditions: the broker host name is the same for all, and the Client IDs have the same format.

Umm, ... our credentials (mine vs yours) - do they differ only by values?
I mean, for instance you don't have some extra property that I've missed?

...

Let's say only the values are to problem on my side. Then I register another device in AWS IoT Core to get all values afresh - Client ID, and certificates. Then I provide the new values in the same way:

Provision the certificates;
Change the configuration and flash the new build on the Thingy.

Then if I continue to have the same problem, what would that mean? That the procedure under which I register the devices towards AWS is somewhat flawed, for instance? Something with the policies probably?

A lot of questions, I know but at this point anything is possible.

Best regards,

Ivan

RE: Weird output from serial port

Håkon Alseth — Mon, 23 Oct 2023 13:06:18 GMT

Hi Ivan,

Thanks for the files.

Are you 100% certain that the credentials, static client id, and hostname is correct?

I see the same behavior on my side:

But, if I change my credentials to my own aws iot setup, I can connect without problems, with the same log output as I showed last week.

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Fri, 20 Oct 2023 15:24:12 GMT

Hi Håkon,

Making the archive, I excluded the build folder from the tree and added another one (with descriptive name) containing the three certificates generated by Amazon IoT Core.

Please let me know if you need something else.

I removed the content, so I can return the ticket back to public (I need this for documentation).

Best regards,

Ivan

RE: Weird output from serial port

Håkon Alseth — Fri, 20 Oct 2023 15:16:17 GMT

Hi Ivan,

I made this case private.

Please share your whole project .zip, including all your credentials so I can try it on my side.

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Fri, 20 Oct 2023 13:50:55 GMT

Hi Håkon,

Since I've read in many places that the only limitation for the SEC_TAG's value is to be different than the one reserved for the nRF Cloud (the one already filled in when you open the Certificate Manager), I've used different values. But I've always been careful to keep the tag the same in both the certificates I provision, and the code sample I'm building (in the prj.conf).

So now I just returned the value everywhere to 201, reprovisioned the three certificates the same way you describe it, and flashed the newly built app_signed.hex file. The result unfortunately was all the same:

If I'm missing something I already have no idea what it might be ...

Actually, I noticed something at some point. I'm not sure if it is relevant at all but at in all other cases we had (with other types of devices, including virtual ones - python scripts) it was always mandatory to specify the default secure MQTT port (8883). I've never found a related property in the code samples - is it something hardcoded deeper in the firmware?

Best regards,

Ivan

RE: Weird output from serial port

Håkon Alseth — Fri, 20 Oct 2023 12:48:39 GMT

Hi Ivan,

Are you targeting the correct SEC_TAG?

In the aws_iot sample, this is by-default set to '201' - what is it set to in your firmware?

[quote user="Ivan Popov"]Could you please provide a procedure for provisioning the certificates that is correct? Because out of the several variants available in different part of the Nordic documentation, so far nothing changes the end result and I always end up with the ENOTCONN (-128) error which according to its comment is related to some socket and not with the credentials (I saw many cases where people get error 111, regarding the credentials). [/quote]

This highly depends on how you've setup the project to load certificates.

I used AT%CMNG, via the "certificate manager", where I manually copied in each certificate:

[quote user="Ivan Popov"]with and without an empty new line after the closing line (-----END CERTIFICATE-----)[/quote]

Do not remove these, or alter the certificate in any way.

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Thu, 19 Oct 2023 15:15:29 GMT

Hi Håkon,

Could you please provide a procedure for provisioning the certificates that is correct? Because out of the several variants available in different part of the Nordic documentation, so far nothing changes the end result and I always end up with the ENOTCONN (-128) error which according to its comment is related to some socket and not with the credentials (I saw many cases where people get error 111, regarding the credentials).

I worked exclusively with the Certificate Manager (in the Cellular Monitor application) and rewrote the certificates several times with:

different security tags (never the one reserved for the nRF Cloud)
with and without an empty new line after the closing line (-----END CERTIFICATE-----)
I even tried to add them into the dedicated files in the source tree (perfectly realising that this is most probably a deprecated practice)

Beyond that I tried your proposal:

[quote userid="2115" url="~/f/nordic-q-a/104132/weird-output-from-serial-port/450966"]Note that you should set your client id + hostname according to the AWS IoT settings, similar to this (XXYYZZ11 used as example here):[/quote]

although it doesn't make sense for the following reasons:

As AWS describe it in their own documentation - the first part of the broker host name is "an account specific prefix" and can't be matched to an individual devise (but even it it could then which one of the myriad registered devices?)
In our system we've registered so far some other types of devices too and the and it always worked this way: the Client ID is the unique ID given to the device by the AWS IoT Core registry and the broker host name is an MQTT endpoint for all the devices to connect to and is expected to always have the same constant value.

Eventually, I'm still revolving around this state:

and wonder how this socket connection requirement can be satisfied.

Best regards,

Ivan

RE: Weird output from serial port

Håkon Alseth — Wed, 18 Oct 2023 07:42:05 GMT

Hi Ivan,

I believe that the certificates are not correctly provisioned.

You should have seen something like this in the log:

I: AWS_IOT_EVT_CONNECTING
+CSCON: 1
I: RRC mode: Connected
I: AWS_IOT_EVT_CONNECTED
I: Publishing: {
        "state":        {
                "reported":     {
                        "app_version":  "v1.0.0",
                        "batv": 4414,
                        "ts":   1697613890218
                }
        }
} to AWS IoT broker
+CEREG: 5,"08FF","0201EE0C",7,,,"00100001","00000110"
I: PSM parameter update: TAU: 3600, Active time: 60
I: AWS_IOT_EVT_READY
I: AWS_IOT_EVT_PUBACK, message ID: 38561
I: AWS_IOT_EVT_DATA_RECEIVED
I: Data received from AWS IoT console: Topic: $aws/things/client-id/shadow/get/accepted Message: {
        "state":        {
                "desired":      {
                        "welcome":      "aws-iot"
                },
                "reported":     {
                        "welcome":      "aws-iot",
                        "app_version":  "v1.0.0",
                        "batv": 4414,
                        "ts":   1697613890218
                }
        },
        "metadata":     {
                "desired":      {
                        "welcome":      {
                                "timestamp":    1611324816
                        }
                },
                "reported":     {
                        "welcome":      {
                                "timestamp":    1611324816
                        },
                        "app_version":  {
                                "timestamp":    1697613890
                        },
                        "batv": {
                                "timestamp":    1697613890
                        },
                        "ts":   {
                                "timestamp":    1697613890
                        }
                }
        },
        "version":      241,
        "timestamp":    1697613891
}
+CSCON: 0
I: RRC mode: Idle
I: Publishing: {
        "state":        {
                "reported":     {
                        "batv": 4414,
                        "ts":   1697613950219
                }
        }
} to AWS IoT broker
I: Next data publication in 60 seconds

Could you try to reprovision your certificates?

You should provide the "*-certificate.pem", "*-private.pem" and "AmazonRootCA1.pem" while provisioning.

Note that you should set your client id + hostname according to the AWS IoT settings, similar to this (XXYYZZ11 used as example here):

CONFIG_AWS_IOT_CLIENT_ID_STATIC="XXYYZZ11"
CONFIG_AWS_IOT_BROKER_HOST_NAME="xxyyzz11-ats.iot.eu-north-1.amazonaws.com"

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Tue, 17 Oct 2023 08:13:24 GMT

Hello Håkon,

As you can see from the AWS' MQTT Client the communication goes successfully in both directions, which means the certificates and the security tag can not be the problem:

Here is the log you requested:

2023-10-17T07:44:22.207Z DEBUG Application data folder: /home/jp/.config/nrfconnect/pc-nrfconnect-linkmonitor
2023-10-17T07:44:22.288Z DEBUG App pc-nrfconnect-linkmonitor v2.0.4 local
2023-10-17T07:44:22.289Z DEBUG App path: /home/jp/.nrfconnect-apps/node_modules/pc-nrfconnect-linkmonitor
2023-10-17T07:44:22.289Z DEBUG nRFConnect 4.2.1, required by the app is (>=4.0.0)
2023-10-17T07:44:22.289Z DEBUG nRFConnect path: /tmp/.mount_nrfcon9UKuUf/resources/app.asar
2023-10-17T07:44:22.289Z DEBUG HomeDir: /home/jp
2023-10-17T07:44:22.289Z DEBUG TmpDir: /tmp
2023-10-17T07:44:22.307Z INFO Using nrf-device-lib-js version: 0.6.12
2023-10-17T07:44:22.307Z INFO Using nrf-device-lib version: 0.15.3
2023-10-17T07:44:22.307Z INFO Using nrfjprog DLL version: 10.19.1
2023-10-17T07:44:22.307Z INFO Using JLink version: JLink_V7.80c
2023-10-17T07:44:50.227Z INFO Modem port is opened
2023-10-17T07:44:50.252Z DEBUG modem >> AT+CFUN?
2023-10-17T07:44:50.279Z DEBUG modem << +CFUN: 1
2023-10-17T07:44:50.285Z DEBUG modem << OK
2023-10-17T07:44:50.311Z DEBUG modem >> AT+CGSN=1
2023-10-17T07:44:50.323Z DEBUG modem << +CGSN: "-------------"
2023-10-17T07:44:50.328Z DEBUG modem << OK
2023-10-17T07:44:50.334Z DEBUG modem >> AT+CGMI
2023-10-17T07:44:50.351Z DEBUG modem << Nordic Semiconductor ASA
2023-10-17T07:44:50.358Z DEBUG modem << OK
2023-10-17T07:44:50.366Z DEBUG modem >> AT+CGMM
2023-10-17T07:44:50.376Z DEBUG modem << nRF9160-SICA
2023-10-17T07:44:50.382Z DEBUG modem << OK
2023-10-17T07:44:50.392Z DEBUG modem >> AT+CGMR
2023-10-17T07:44:50.403Z DEBUG modem << mfw_nrf9160_1.3.4
2023-10-17T07:44:50.414Z DEBUG modem << OK
2023-10-17T07:44:50.421Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.4] SerNr: ------------
2023-10-17T07:44:50.426Z DEBUG modem >> AT+CEMODE?
2023-10-17T07:44:50.437Z DEBUG modem << +CEMODE: 0
2023-10-17T07:44:50.445Z DEBUG modem << OK
2023-10-17T07:44:50.467Z DEBUG modem >> AT%XCBAND=?
2023-10-17T07:44:50.481Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)
2023-10-17T07:44:50.485Z DEBUG modem << OK
2023-10-17T07:44:50.503Z DEBUG modem >> AT+CMEE?
2023-10-17T07:44:50.513Z DEBUG modem << +CMEE: 0
2023-10-17T07:44:50.517Z DEBUG modem << OK
2023-10-17T07:44:50.525Z DEBUG modem >> AT+CMEE=1
2023-10-17T07:44:50.533Z DEBUG modem << OK
2023-10-17T07:44:50.541Z DEBUG modem >> AT+CNEC?
2023-10-17T07:44:50.551Z DEBUG modem << +CNEC: 0
2023-10-17T07:44:50.557Z DEBUG modem << OK
2023-10-17T07:44:50.565Z DEBUG modem >> AT+CNEC=24
2023-10-17T07:44:50.575Z DEBUG modem << OK
2023-10-17T07:44:50.580Z DEBUG modem >> AT+CGEREP?
2023-10-17T07:44:50.591Z DEBUG modem << +CGEREP: 0,0
2023-10-17T07:44:50.596Z DEBUG modem << OK
2023-10-17T07:44:50.600Z DEBUG modem >> AT+CGDCONT?
2023-10-17T07:44:50.616Z DEBUG modem << +CGDCONT: 0,"IP","iot.1nce.net","10.137.163.1",0,0
2023-10-17T07:44:50.623Z DEBUG modem << OK
2023-10-17T07:44:50.650Z DEBUG modem >> AT+CGACT?
2023-10-17T07:44:50.664Z DEBUG modem << +CGACT: 0,1
2023-10-17T07:44:50.668Z DEBUG modem << OK
2023-10-17T07:44:50.681Z DEBUG modem >> AT+CGEREP=1
2023-10-17T07:44:50.690Z DEBUG modem << OK
2023-10-17T07:44:50.695Z DEBUG modem >> AT+CIND=1,1,1
2023-10-17T07:44:50.706Z DEBUG modem << OK
2023-10-17T07:44:50.712Z DEBUG modem >> AT+CEREG=5
2023-10-17T07:44:50.720Z DEBUG modem << OK
2023-10-17T07:44:50.728Z DEBUG modem >> AT+CEREG?
2023-10-17T07:44:50.742Z DEBUG modem << +CEREG: 5,5,"00C7","011707CB",9,,,"11100000","11100000"
2023-10-17T07:44:50.746Z DEBUG modem << OK
2023-10-17T07:44:50.761Z DEBUG modem >> AT+COPS=3,2
2023-10-17T07:44:50.771Z DEBUG modem << OK
2023-10-17T07:44:50.776Z DEBUG modem >> AT+COPS?
2023-10-17T07:44:50.786Z DEBUG modem << +COPS: 0,2,"28401",9
2023-10-17T07:44:50.791Z DEBUG modem << OK
2023-10-17T07:44:50.809Z DEBUG modem >> AT%XCBAND
2023-10-17T07:44:50.819Z DEBUG modem << %XCBAND: 8
2023-10-17T07:44:50.824Z DEBUG modem << OK
2023-10-17T07:44:50.845Z DEBUG modem >> AT+CGDCONT?
2023-10-17T07:44:50.864Z DEBUG modem << +CGDCONT: 0,"IP","iot.1nce.net","10.137.163.1",0,0
2023-10-17T07:44:50.869Z DEBUG modem << OK
2023-10-17T07:44:50.890Z DEBUG modem >> AT+CGACT?
2023-10-17T07:44:50.900Z DEBUG modem << +CGACT: 0,1
2023-10-17T07:44:50.904Z DEBUG modem << OK
2023-10-17T07:44:50.918Z DEBUG modem >> AT%CESQ=1
2023-10-17T07:44:50.929Z DEBUG modem << OK
2023-10-17T07:44:50.934Z DEBUG modem >> AT+CESQ
2023-10-17T07:44:50.944Z DEBUG modem << +CESQ: 99,99,255,255,26,60
2023-10-17T07:44:50.951Z DEBUG modem << OK
2023-10-17T07:44:50.974Z DEBUG modem >> AT%XSIM=1
2023-10-17T07:44:50.984Z DEBUG modem << OK
2023-10-17T07:44:50.995Z DEBUG modem >> AT%XSIM?
2023-10-17T07:44:51.009Z DEBUG modem << %XSIM: 1
2023-10-17T07:44:51.013Z DEBUG modem << OK
2023-10-17T07:44:51.027Z DEBUG modem >> AT+CPIN?
2023-10-17T07:44:51.039Z DEBUG modem << +CPIN: READY
2023-10-17T07:44:51.043Z DEBUG modem << OK
2023-10-17T07:44:51.059Z DEBUG modem >> AT+CPINR="SIM PIN"
2023-10-17T07:44:51.078Z DEBUG modem << +CPINR: "SIM PIN",3
2023-10-17T07:44:51.083Z DEBUG modem << OK
2023-10-17T07:44:51.103Z DEBUG modem >> AT+CIMI
2023-10-17T07:44:51.113Z DEBUG modem << ---------
2023-10-17T07:44:51.118Z DEBUG modem << OK
2023-10-17T07:44:51.122Z INFO IMSIdentity: ----------
2023-10-17T07:44:51.161Z DEBUG modem << %CESQ: 60,3,27,3
2023-10-17T07:44:52.232Z DEBUG modem >> AT+CESQ
2023-10-17T07:44:52.247Z DEBUG modem << +CESQ: 99,99,255,255,24,60
2023-10-17T07:44:52.254Z DEBUG modem << OK
2023-10-17T07:45:02.611Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:45:02.616Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:45:08.352Z DEBUG modem << +CSCON: 0
2023-10-17T07:45:08.361Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:45:08.712Z DEBUG modem << %CESQ: 62,3,21,3
2023-10-17T07:45:18.601Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:45:18.623Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:45:18.709Z DEBUG modem << %CESQ: 60,3,27,3
2023-10-17T07:45:18.927Z DEBUG modem << +CSCON: 1
2023-10-17T07:45:18.948Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:45:22.232Z DEBUG modem >> AT+CESQ
2023-10-17T07:45:22.259Z DEBUG modem << +CESQ: 99,99,255,255,24,59
2023-10-17T07:45:22.272Z DEBUG modem << OK
2023-10-17T07:45:23.068Z DEBUG modem << %CESQ: 59,2,22,3
2023-10-17T07:45:26.519Z DEBUG modem << %CESQ: 61,3,27,3
2023-10-17T07:45:32.388Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:45:32.408Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:45:38.113Z DEBUG modem << +CSCON: 0
2023-10-17T07:45:38.119Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:45:38.472Z DEBUG modem << %CESQ: 61,3,21,3
2023-10-17T07:45:47.499Z DEBUG modem << %CESQ: 59,2,26,3
2023-10-17T07:45:48.603Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:45:48.615Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:45:49.007Z DEBUG modem << +CSCON: 1
2023-10-17T07:45:49.013Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:45:52.232Z DEBUG modem >> AT+CESQ
2023-10-17T07:45:52.256Z DEBUG modem << +CESQ: 99,99,255,255,24,58
2023-10-17T07:45:52.266Z DEBUG modem << OK
2023-10-17T07:46:05.491Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:46:05.500Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:46:11.233Z DEBUG modem << +CSCON: 0
2023-10-17T07:46:11.252Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:46:13.067Z DEBUG modem << %CESQ: 60,3,20,2
2023-10-17T07:46:18.605Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:46:18.611Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:46:18.709Z DEBUG modem << %CESQ: 62,3,27,3
2023-10-17T07:46:18.928Z DEBUG modem << +CSCON: 1
2023-10-17T07:46:18.934Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:46:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:46:22.259Z DEBUG modem << +CESQ: 99,99,255,255,25,61
2023-10-17T07:46:22.268Z DEBUG modem << OK
2023-10-17T07:46:32.851Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:46:32.860Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:46:38.595Z DEBUG modem << +CSCON: 0
2023-10-17T07:46:38.615Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:46:43.783Z DEBUG modem << %CESQ: 64,3,20,2
2023-10-17T07:46:48.607Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:46:48.622Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:46:48.709Z DEBUG modem << %CESQ: 62,3,27,3
2023-10-17T07:46:49.007Z DEBUG modem << +CSCON: 1
2023-10-17T07:46:49.023Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:46:52.236Z DEBUG modem >> AT+CESQ
2023-10-17T07:46:52.258Z DEBUG modem << +CESQ: 99,99,255,255,25,63
2023-10-17T07:46:52.265Z DEBUG modem << OK
2023-10-17T07:47:02.291Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:47:02.312Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:47:08.033Z DEBUG modem << +CSCON: 0
2023-10-17T07:47:08.053Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:47:08.395Z DEBUG modem << %CESQ: 60,3,22,3
2023-10-17T07:47:18.611Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:47:18.630Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:47:18.690Z DEBUG modem << %CESQ: 62,3,28,4
2023-10-17T07:47:18.929Z DEBUG modem << +CSCON: 1
2023-10-17T07:47:18.950Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:47:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:47:22.282Z DEBUG modem << +CESQ: 99,99,255,255,29,62
2023-10-17T07:47:22.288Z DEBUG modem << OK
2023-10-17T07:47:33.011Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:47:33.019Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:47:38.753Z DEBUG modem << +CSCON: 0
2023-10-17T07:47:38.773Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:47:40.107Z DEBUG modem << %CESQ: 62,3,22,3
2023-10-17T07:47:48.612Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:47:48.616Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:47:48.709Z DEBUG modem << %CESQ: 59,2,27,3
2023-10-17T07:47:49.007Z DEBUG modem << +CSCON: 1
2023-10-17T07:47:49.012Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:47:52.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:47:52.280Z DEBUG modem << +CESQ: 99,99,255,255,25,61
2023-10-17T07:47:52.289Z DEBUG modem << OK
2023-10-17T07:48:02.131Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:48:02.148Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:48:07.873Z DEBUG modem << +CSCON: 0
2023-10-17T07:48:07.880Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:48:08.235Z DEBUG modem << %CESQ: 61,3,22,3
2023-10-17T07:48:18.614Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:48:18.634Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:48:18.928Z DEBUG modem << +CSCON: 1
2023-10-17T07:48:18.939Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:48:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:48:22.283Z DEBUG modem << +CESQ: 99,99,255,255,24,60
2023-10-17T07:48:22.290Z DEBUG modem << OK
2023-10-17T07:48:27.522Z DEBUG modem << %CESQ: 62,3,27,3
2023-10-17T07:48:33.624Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:48:33.645Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:48:39.393Z DEBUG modem << +CSCON: 0
2023-10-17T07:48:39.415Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:48:46.678Z DEBUG modem << %CESQ: 61,3,21,3
2023-10-17T07:48:48.616Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:48:48.635Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:48:48.709Z DEBUG modem << %CESQ: 61,3,29,4
2023-10-17T07:48:49.007Z DEBUG modem << +CSCON: 1
2023-10-17T07:48:49.027Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:48:52.236Z DEBUG modem >> AT+CESQ
2023-10-17T07:48:52.262Z DEBUG modem << +CESQ: 99,99,255,255,27,63
2023-10-17T07:48:52.271Z DEBUG modem << OK
2023-10-17T07:48:52.842Z DEBUG modem << %CESQ: 62,3,24,3
2023-10-17T07:49:03.236Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:49:03.243Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:49:03.410Z DEBUG modem << %CESQ: 64,3,29,4
2023-10-17T07:49:08.993Z DEBUG modem << +CSCON: 0
2023-10-17T07:49:09.013Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:49:09.355Z DEBUG modem << %CESQ: 62,3,23,3
2023-10-17T07:49:17.397Z DEBUG modem << %CESQ: 57,2,22,3
2023-10-17T07:49:18.618Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:49:18.624Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:49:18.712Z DEBUG modem << %CESQ: 60,3,28,4
2023-10-17T07:49:18.929Z DEBUG modem << +CSCON: 1
2023-10-17T07:49:18.941Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:49:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:49:22.281Z DEBUG modem << +CESQ: 99,99,255,255,25,59
2023-10-17T07:49:22.287Z DEBUG modem << OK
2023-10-17T07:49:23.068Z DEBUG modem << %CESQ: 59,2,23,3
2023-10-17T07:49:31.851Z DEBUG modem << %CESQ: 54,2,22,3
2023-10-17T07:49:31.908Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:49:31.913Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:49:37.633Z DEBUG modem << +CSCON: 0
2023-10-17T07:49:37.652Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:49:48.621Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:49:48.636Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:49:49.008Z DEBUG modem << +CSCON: 1
2023-10-17T07:49:49.024Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:49:52.239Z DEBUG modem >> AT+CESQ
2023-10-17T07:49:52.285Z DEBUG modem << +CESQ: 99,99,255,255,22,56
2023-10-17T07:49:52.291Z DEBUG modem << OK
2023-10-17T07:49:53.402Z DEBUG modem << %CESQ: 59,2,24,3
2023-10-17T07:50:03.908Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:50:03.914Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:50:07.971Z DEBUG modem << %CESQ: 62,3,29,4
2023-10-17T07:50:09.633Z DEBUG modem << +CSCON: 0
2023-10-17T07:50:09.651Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:50:09.837Z DEBUG modem << %CESQ: 61,3,21,3
2023-10-17T07:50:18.623Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:50:18.644Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:50:18.789Z DEBUG modem << %CESQ: 61,3,27,3
2023-10-17T07:50:19.087Z DEBUG modem << +CSCON: 1
2023-10-17T07:50:19.096Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:50:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:50:22.284Z DEBUG modem << +CESQ: 99,99,255,255,26,62
2023-10-17T07:50:22.290Z DEBUG modem << OK
2023-10-17T07:50:33.332Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:50:33.351Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:50:39.073Z DEBUG modem << +CSCON: 0
2023-10-17T07:50:39.092Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:50:39.275Z DEBUG modem << %CESQ: 61,3,22,3
2023-10-17T07:50:48.625Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:50:48.644Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:50:48.730Z DEBUG modem << %CESQ: 66,3,29,4
2023-10-17T07:50:49.007Z DEBUG modem << +CSCON: 1
2023-10-17T07:50:49.014Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:50:52.239Z DEBUG modem >> AT+CESQ
2023-10-17T07:50:52.285Z DEBUG modem << +CESQ: 99,99,255,255,27,65
2023-10-17T07:50:52.292Z DEBUG modem << OK
2023-10-17T07:50:52.850Z DEBUG modem << %CESQ: 64,3,24,3
2023-10-17T07:50:58.587Z DEBUG modem << %CESQ: 65,3,29,4
2023-10-17T07:51:02.451Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:51:02.471Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:51:08.193Z DEBUG modem << +CSCON: 0
2023-10-17T07:51:08.198Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:51:08.395Z DEBUG modem << %CESQ: 64,3,22,3
2023-10-17T07:51:18.627Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:51:18.648Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:51:18.709Z DEBUG modem << %CESQ: 63,3,27,3
2023-10-17T07:51:18.927Z DEBUG modem << +CSCON: 1
2023-10-17T07:51:18.946Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:51:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:51:22.285Z DEBUG modem << +CESQ: 99,99,255,255,25,64
2023-10-17T07:51:22.292Z DEBUG modem << OK
2023-10-17T07:51:32.388Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:51:32.393Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:51:38.113Z DEBUG modem << +CSCON: 0
2023-10-17T07:51:38.134Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:51:40.747Z DEBUG modem << %CESQ: 65,3,20,2
2023-10-17T07:51:48.630Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:51:48.651Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:51:48.730Z DEBUG modem << %CESQ: 64,3,26,3
2023-10-17T07:51:49.007Z DEBUG modem << +CSCON: 1
2023-10-17T07:51:49.028Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:51:52.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:51:52.249Z DEBUG modem << +CESQ: 99,99,255,255,26,64
2023-10-17T07:51:52.256Z DEBUG modem << OK
2023-10-17T07:52:04.036Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:52:04.042Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:52:09.793Z DEBUG modem << +CSCON: 0
2023-10-17T07:52:09.814Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:52:10.154Z DEBUG modem << %CESQ: 61,3,21,3
2023-10-17T07:52:18.631Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:52:18.637Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:52:18.729Z DEBUG modem << %CESQ: 63,3,26,3
2023-10-17T07:52:18.927Z DEBUG modem << +CSCON: 1
2023-10-17T07:52:18.932Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:52:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:52:22.295Z DEBUG modem << +CESQ: 99,99,255,255,25,61
2023-10-17T07:52:22.305Z DEBUG modem << OK
2023-10-17T07:52:32.388Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:52:32.413Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:52:38.113Z DEBUG modem << +CSCON: 0
2023-10-17T07:52:38.133Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:52:48.635Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:52:48.656Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:52:49.007Z DEBUG modem << +CSCON: 1
2023-10-17T07:52:49.028Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:52:52.238Z DEBUG modem >> AT+CESQ
2023-10-17T07:52:52.287Z DEBUG modem << +CESQ: 99,99,255,255,26,62
2023-10-17T07:52:52.294Z DEBUG modem << OK
2023-10-17T07:53:03.093Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:53:03.100Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:53:07.611Z DEBUG modem << %CESQ: 58,2,27,3
2023-10-17T07:53:08.835Z DEBUG modem << +CSCON: 0
2023-10-17T07:53:08.847Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:53:09.035Z DEBUG modem << %CESQ: 61,3,22,3
2023-10-17T07:53:18.636Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:53:18.642Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:53:18.729Z DEBUG modem << %CESQ: 60,3,27,3
2023-10-17T07:53:18.927Z DEBUG modem << +CSCON: 1
2023-10-17T07:53:18.933Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:53:22.236Z DEBUG modem >> AT+CESQ
2023-10-17T07:53:22.266Z DEBUG modem << +CESQ: 99,99,255,255,25,61
2023-10-17T07:53:22.273Z DEBUG modem << OK
2023-10-17T07:53:33.959Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:53:33.979Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:53:39.713Z DEBUG modem << +CSCON: 0
2023-10-17T07:53:39.729Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:53:43.627Z DEBUG modem << %CESQ: 61,3,19,2
2023-10-17T07:53:48.638Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:53:48.644Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:53:48.829Z DEBUG modem << %CESQ: 62,3,27,3
2023-10-17T07:53:49.007Z DEBUG modem << +CSCON: 1
2023-10-17T07:53:49.018Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:53:52.236Z DEBUG modem >> AT+CESQ
2023-10-17T07:53:52.247Z DEBUG modem << +CESQ: 99,99,255,255,24,62
2023-10-17T07:53:52.255Z DEBUG modem << OK
2023-10-17T07:54:02.469Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:54:02.492Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:54:08.193Z DEBUG modem << +CSCON: 0
2023-10-17T07:54:08.200Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:54:14.347Z DEBUG modem << %CESQ: 63,3,21,3
2023-10-17T07:54:18.641Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:54:18.649Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:54:18.730Z DEBUG modem << %CESQ: 61,3,28,4
2023-10-17T07:54:18.927Z DEBUG modem << +CSCON: 1
2023-10-17T07:54:18.949Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:54:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:54:22.268Z DEBUG modem << +CESQ: 99,99,255,255,24,61
2023-10-17T07:54:22.275Z DEBUG modem << OK
2023-10-17T07:54:22.362Z DEBUG modem << %CESQ: 61,3,23,3
2023-10-17T07:54:28.295Z DEBUG modem << %CESQ: 56,2,23,3
2023-10-17T07:54:31.891Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:54:31.897Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:54:37.633Z DEBUG modem << +CSCON: 0
2023-10-17T07:54:37.640Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:54:37.995Z DEBUG modem << %CESQ: 62,3,23,3
2023-10-17T07:54:48.643Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:54:48.651Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:54:49.007Z DEBUG modem << +CSCON: 1
2023-10-17T07:54:49.012Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:54:51.588Z DEBUG modem << %CESQ: 62,3,28,4
2023-10-17T07:54:52.236Z DEBUG modem >> AT+CESQ
2023-10-17T07:54:52.288Z DEBUG modem << +CESQ: 99,99,255,255,27,62
2023-10-17T07:54:52.295Z DEBUG modem << OK
2023-10-17T07:54:53.442Z DEBUG modem << %CESQ: 60,3,23,3
2023-10-17T07:55:02.235Z DEBUG modem << %CESQ: 61,3,28,4
2023-10-17T07:55:03.588Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:55:03.595Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:55:09.313Z DEBUG modem << +CSCON: 0
2023-10-17T07:55:09.320Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:55:10.678Z DEBUG modem << %CESQ: 60,3,20,2
2023-10-17T07:55:18.645Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:55:18.660Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:55:18.729Z DEBUG modem << %CESQ: 60,3,27,3
2023-10-17T07:55:18.928Z DEBUG modem << +CSCON: 1
2023-10-17T07:55:18.955Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:55:22.236Z DEBUG modem >> AT+CESQ
2023-10-17T07:55:22.269Z DEBUG modem << +CESQ: 99,99,255,255,26,61
2023-10-17T07:55:22.276Z DEBUG modem << OK
2023-10-17T07:55:33.474Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:55:33.480Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:55:39.233Z DEBUG modem << +CSCON: 0
2023-10-17T07:55:39.245Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:55:39.435Z DEBUG modem << %CESQ: 60,3,21,3
2023-10-17T07:55:48.647Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:55:48.656Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:55:48.749Z DEBUG modem << %CESQ: 60,3,28,4
2023-10-17T07:55:49.007Z DEBUG modem << +CSCON: 1
2023-10-17T07:55:49.013Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:55:52.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:55:52.297Z DEBUG modem << +CESQ: 99,99,255,255,24,62
2023-10-17T07:55:52.303Z DEBUG modem << OK
2023-10-17T07:56:02.133Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:56:02.142Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:56:07.874Z DEBUG modem << +CSCON: 0
2023-10-17T07:56:07.889Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:56:08.235Z DEBUG modem << %CESQ: 63,3,22,3
2023-10-17T07:56:18.649Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:56:18.667Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:56:18.749Z DEBUG modem << %CESQ: 60,3,27,3
2023-10-17T07:56:18.928Z DEBUG modem << +CSCON: 1
2023-10-17T07:56:18.949Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:56:22.236Z DEBUG modem >> AT+CESQ
2023-10-17T07:56:22.284Z DEBUG modem << +CESQ: 99,99,255,255,26,61
2023-10-17T07:56:22.289Z DEBUG modem << OK
2023-10-17T07:56:37.491Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:56:37.500Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:56:43.233Z DEBUG modem << +CSCON: 0
2023-10-17T07:56:43.249Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:56:47.948Z DEBUG modem << %CESQ: 62,3,19,2
2023-10-17T07:56:48.652Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:56:48.659Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:56:48.749Z DEBUG modem << %CESQ: 62,3,29,4
2023-10-17T07:56:49.008Z DEBUG modem << +CSCON: 1
2023-10-17T07:56:49.030Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:56:52.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:56:52.289Z DEBUG modem << +CESQ: 99,99,255,255,26,63
2023-10-17T07:56:52.295Z DEBUG modem << OK
2023-10-17T07:56:55.908Z DEBUG modem << %CESQ: 62,3,24,3
2023-10-17T07:57:02.435Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:57:02.455Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:57:08.194Z DEBUG modem << +CSCON: 0
2023-10-17T07:57:08.215Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:57:18.654Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:57:18.675Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:57:18.719Z DEBUG modem << %CESQ: 61,3,19,2
2023-10-17T07:57:18.753Z DEBUG modem << %CESQ: 62,3,26,3
2023-10-17T07:57:18.928Z DEBUG modem << +CSCON: 1
2023-10-17T07:57:18.950Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:57:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:57:22.291Z DEBUG modem << +CESQ: 99,99,255,255,23,59
2023-10-17T07:57:22.297Z DEBUG modem << OK
2023-10-17T07:57:32.854Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:57:32.878Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:57:38.593Z DEBUG modem << +CSCON: 0
2023-10-17T07:57:38.615Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:57:44.280Z DEBUG modem << %CESQ: 59,2,21,3
2023-10-17T07:57:48.657Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:57:48.676Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:57:48.750Z DEBUG modem << %CESQ: 60,3,26,3
2023-10-17T07:57:49.008Z DEBUG modem << +CSCON: 1
2023-10-17T07:57:49.025Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:57:52.236Z DEBUG modem >> AT+CESQ
2023-10-17T07:57:52.272Z DEBUG modem << +CESQ: 99,99,255,255,26,60
2023-10-17T07:57:52.278Z DEBUG modem << OK
2023-10-17T07:58:04.037Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:58:04.059Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:58:09.794Z DEBUG modem << +CSCON: 0
2023-10-17T07:58:09.814Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:58:14.988Z DEBUG modem << %CESQ: 62,3,18,2
2023-10-17T07:58:18.658Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:58:18.666Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:58:18.749Z DEBUG modem << %CESQ: 59,2,24,3
2023-10-17T07:58:18.928Z DEBUG modem << +CSCON: 1
2023-10-17T07:58:18.950Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:58:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:58:22.296Z DEBUG modem << +CESQ: 99,99,255,255,24,61
2023-10-17T07:58:22.302Z DEBUG modem << OK
2023-10-17T07:58:32.853Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:58:32.878Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:58:35.730Z DEBUG modem << %CESQ: 64,3,28,4
2023-10-17T07:58:38.593Z DEBUG modem << +CSCON: 0
2023-10-17T07:58:38.613Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:58:38.955Z DEBUG modem << %CESQ: 61,3,21,3
2023-10-17T07:58:45.739Z DEBUG modem << %CESQ: 61,3,26,3
2023-10-17T07:58:48.660Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:58:48.721Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:58:49.008Z DEBUG modem << +CSCON: 1
2023-10-17T07:58:49.028Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:58:52.236Z DEBUG modem >> AT+CESQ
2023-10-17T07:58:52.248Z DEBUG modem << +CESQ: 99,99,255,255,24,61
2023-10-17T07:58:52.258Z DEBUG modem << OK
2023-10-17T07:59:02.469Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:59:02.492Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:59:08.193Z DEBUG modem << +CSCON: 0
2023-10-17T07:59:08.213Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:59:11.307Z DEBUG modem << %CESQ: 63,3,19,2
2023-10-17T07:59:16.459Z DEBUG modem << %CESQ: 62,3,24,3
2023-10-17T07:59:18.663Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:59:18.685Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:59:18.928Z DEBUG modem << +CSCON: 1
2023-10-17T07:59:18.949Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:59:22.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:59:22.294Z DEBUG modem << +CESQ: 99,99,255,255,26,61
2023-10-17T07:59:22.301Z DEBUG modem << OK
2023-10-17T07:59:33.012Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T07:59:33.020Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T07:59:38.491Z DEBUG modem << %CESQ: 62,3,29,4
2023-10-17T07:59:38.754Z DEBUG modem << +CSCON: 0
2023-10-17T07:59:38.775Z DEBUG modem << I: RRC mode: Idle
2023-10-17T07:59:39.115Z DEBUG modem << %CESQ: 64,3,23,3
2023-10-17T07:59:48.666Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T07:59:48.688Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T07:59:48.749Z DEBUG modem << %CESQ: 64,3,29,4
2023-10-17T07:59:49.008Z DEBUG modem << +CSCON: 1
2023-10-17T07:59:49.029Z DEBUG modem << I: RRC mode: Connected
2023-10-17T07:59:51.642Z DEBUG modem << %CESQ: 62,3,24,3
2023-10-17T07:59:52.237Z DEBUG modem >> AT+CESQ
2023-10-17T07:59:52.293Z DEBUG modem << +CESQ: 99,99,255,255,25,62
2023-10-17T07:59:52.299Z DEBUG modem << OK
2023-10-17T08:00:02.277Z DEBUG modem << I: AWS_IOT_EVT_DISCONNECTED
2023-10-17T08:00:02.289Z DEBUG modem << E: Cloud MQTT input error: -128
2023-10-17T08:00:03.763Z DEBUG modem << %CESQ: 64,3,29,4
2023-10-17T08:00:08.033Z DEBUG modem << +CSCON: 0
2023-10-17T08:00:08.054Z DEBUG modem << I: RRC mode: Idle
2023-10-17T08:00:08.235Z DEBUG modem << %CESQ: 63,3,24,3
2023-10-17T08:00:12.747Z DEBUG modem << %CESQ: 62,3,19,2
2023-10-17T08:00:18.667Z DEBUG modem << I: Next connection retry in 30 seconds
2023-10-17T08:00:18.672Z DEBUG modem << I: AWS_IOT_EVT_CONNECTING
2023-10-17T08:00:18.769Z DEBUG modem << %CESQ: 61,3,27,3
2023-10-17T08:00:19.087Z DEBUG modem << +CSCON: 1
2023-10-17T08:00:19.096Z DEBUG modem << I: RRC mode: Connected
2023-10-17T08:00:22.236Z DEBUG modem >> AT+CESQ
2023-10-17T08:00:22.266Z DEBUG modem << +CESQ: 99,99,255,255,25,62
2023-10-17T08:00:22.274Z DEBUG modem << OK


And it goes like this. The error seems to persist but it obviously doesn't hinder the communication.

It looks like some sort of handshake fails.

One question: In the Asset Tracker code sample I see there is a lot of features added for different purposes. Can you tell me which part of the code (and on what configuration it depends) is responsible for reading the the sensor outputs (+ the battery state) and prepares the data for the cloud?

Regards,

Ivan Popov

RE: Weird output from serial port

Håkon Alseth — Mon, 16 Oct 2023 12:29:11 GMT

Hi Ivan,

It successfully connects to a network now, but you get a -128 return, which resolves to ENOTCONN, ie. not connected.

Can you share a log from reset and to the point where the problem occurs?

All certifications etc are provisioned correctly to the configured SEC_TAG?

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Mon, 16 Oct 2023 07:35:27 GMT

Hi Håkon,

This is a promising start of the week. Maybe we're onto something with it.

The UART indicator is still blinking between yellow and red, after I added this property tothe configuration but at least there is more significant info in the interface and the log (Operator, MQTT status, etc.):

Regards,

Ivan

RE: Weird output from serial port

Håkon Alseth — Mon, 16 Oct 2023 07:04:50 GMT

Hi Ivan,

Thanks for the added info. The screenshots still show no coverage.

Have you ensured at NB-IoT is enabled in firmware?

For instance by selecting:

CONFIG_LTE_NETWORK_MODE_NBIOT_GPS=y

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Fri, 13 Oct 2023 13:15:49 GMT

Oh, I'm sorry!

I probably had to share that information earlier (I guess I forgot about this because it was covered in a previous ticket) - there is not LTE-M coverage in the country. There is maybe like one and a half (the second one is not official) provision of NB-IoT from the local operators. So we used that in order to register the Thingy in the nRFCloud initially (we used 1nce, because iBasis provided only LTE-M here).

So, with that in the context, here are two more screenshots:

and

which I hope provide some relevant information. On the second one the UART indicator in the top-left corner constantly changes between yellow and red.

And no - there no any other logs in the console over time. I really hoped to see something like this already.

Regards,

Ivan

RE: Weird output from serial port

Håkon Alseth — Fri, 13 Oct 2023 10:54:16 GMT

Hi Ivan,

The output from the serial app shows that logs are now working.

The "I:" indicate that it is outputted from a LOG_INF() call.

The return from CEREG: 4 indicate that there's likely no cells in the area:

https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/nw_service/cereg_read.html?cp=2_1_7_6_1

Could it be that the modem reset loop restriction has occurred?

https://infocenter.nordicsemi.com/topic/nwp_042/WP/nwp_042/intro.html?cp=2_0_6_1

Is there any other logs that are printed over time?

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Fri, 13 Oct 2023 08:56:58 GMT

Well,

Adding those properties to the config file gives me the following warning:

But the build passed successfully, and I flashed the image.

The result was having the usual MQTT communication in AWS and only this output in the ST:

Trying with Putty again gives me nothing when clicking on the 'Open' button.

I was supposed to put those properties in the prj.conf file, right?

Best regards,

Ivan

RE: Weird output from serial port

Håkon Alseth — Fri, 13 Oct 2023 08:27:10 GMT

Hi Ivan,

No worries, keep the case open until we have all the issues ironed out.

Were you able to get the debug log output on UART with these configurations?

CONFIG_LOG=y
CONFIG_LOG_BACKEND_UART=y
CONFIG_UART_CONSOLE=y
CONFIG_CONSOLE=y

Kind regards,

Håkon

RE: Weird output from serial port

Ivan Popov — Fri, 13 Oct 2023 07:54:44 GMT

OK, I guess, I understand.

I think I should run a few tests first (may be for a day or two) and when I confirm that I really have the understanding, I will mark the case as closed. I hope this is OK with you.

Regards,

Ivan