Problem adding Thingy:91 in the nRF Cloud

[T1mS_]

Hello,

I try to add a Thingy:91 to the nRF Cloud after I received it today. The sim card got's activated without a problem. When I try to key in my IMEI and the Pin which is printed on the label I receive this error: "There was an error adding your device. It wasn't found. Is it connected?"

How to solve this and add the device to my account?

[Heidi-Irene Harvey Sollie]

Hi! 

Can you confirm that the Thingy:91 is on and the LED is blue and blinking.

Best regards,

Heidi

[T1mS_]

Hi Heidi, 

I think it is more like a blue-withe breathing in a two seconds on and around 5 seconds off interval. 

[T1mS_]

Now it stopped working almost completely. The LEDs are not blinking anymore and in the LTE Link monitor nothing happens. I still can flash it with the jlink device and it also gets recognized in the seriel monitor and also sometimes get some output in the serial monitor.

Now I reflashed the modem and also your thingy91_at_client.hex file.

Still the same result.

I'm now a bit disappointed by the device....

[Heidi-Irene Harvey Sollie]

I'm sorry to hear that. The LED is not supposed to flash with the at_client example.

When you connect it to the COM port in the LTE Link Monitor do you get the log message "Modem port is opened"?

There are two COM ports when the Thingy:91 is connected. Are you sure you are connected to the correct one? Have you tried both?

[T1mS_]

Ok, got it with the LED.

I can not switch between the COM ports. I only can select the device. (See picture)

To get serial output the COM17 is the correct one.

Beside what is shown in the picture, nothing happens, no matter how often I repeat it...

[Heidi-Irene Harvey Sollie]

Try unchecking this selection in the bottom right corner.

[T1mS_]

ok.

All commands still time out.

But doesn't it makes sense, because the modem is not turned on so I can not get a response on my requests? (top right corner - can't make it to turn on...)

2019-08-30T12:56:12.455Z INFO Application data folder: C:\Users\TimSahr\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2019-08-30T12:56:12.521Z DEBUG App pc-nrfconnect-linkmonitor v1.1.0 official
2019-08-30T12:56:12.521Z DEBUG App path: C:\Users\TimSahr\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2019-08-30T12:56:12.521Z DEBUG nRFConnect 3.1.0 is supported by the app (^3.0.0)
2019-08-30T12:56:12.521Z DEBUG nRFConnect path: C:\Users\TimSahr\AppData\Local\Programs\nrfconnect\resources\app.asar
2019-08-30T12:56:12.521Z DEBUG HomeDir: C:\Users\TimSahr
2019-08-30T12:56:12.521Z DEBUG TmpDir: C:\Users\TimSahr\AppData\Local\Temp
2019-08-30T12:56:20.280Z INFO Modem port is opened
2019-08-30T12:56:20.286Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:56:31.327Z INFO Modem port is closed
2019-08-30T12:56:31.334Z INFO Modem port is opened
2019-08-30T12:56:31.338Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:56:43.078Z DEBUG modem >> AT%XSYSTEMMODE = 0,1,1,0\x0D\x0A
2019-08-30T12:56:44.091Z ERROR Error: 'AT%XSYSTEMMODE = 0,1,1,0
' timed out
2019-08-30T12:56:46.397Z DEBUG modem >> AT%XSYSTEMMODE = 0,1,1,0\x0D\x0A
2019-08-30T12:56:47.402Z ERROR Error: 'AT%XSYSTEMMODE = 0,1,1,0
' timed out
2019-08-30T12:56:52.040Z INFO Modem port is closed
2019-08-30T12:56:52.044Z ERROR Open (SetCommState): Unknown error code 433
2019-08-30T12:56:59.029Z INFO Modem port is opened
2019-08-30T12:56:59.034Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:57:02.002Z DEBUG modem >> AT%XSYSTEMMODE = 0,1,1,0\x0D\x0A
2019-08-30T12:57:03.009Z ERROR Error: 'AT%XSYSTEMMODE = 0,1,1,0
' timed out
2019-08-30T12:57:11.293Z INFO Modem port is closed
2019-08-30T12:57:11.300Z INFO Modem port is opened
2019-08-30T12:57:11.304Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:57:14.964Z DEBUG modem >> AT%XSYSTEMMODE = 0,1,1,0\x0D\x0A
2019-08-30T12:57:15.965Z ERROR Error: 'AT%XSYSTEMMODE = 0,1,1,0
' timed out
2019-08-30T12:57:17.549Z DEBUG modem >> AT%XSYSTEMMODE = 0,1,1,0\x0D\x0A
2019-08-30T12:57:18.554Z ERROR Error: 'AT%XSYSTEMMODE = 0,1,1,0
' timed out
2019-08-30T12:57:20.288Z DEBUG modem >> AT%XSYSTEMMODE = 0,1,1,0\x0D\x0A
2019-08-30T12:57:21.299Z ERROR Error: 'AT%XSYSTEMMODE = 0,1,1,0
' timed out
2019-08-30T12:57:22.093Z DEBUG modem >> AT%XSYSTEMMODE = 0,1,1,0\x0D\x0A
2019-08-30T12:57:23.094Z ERROR Error: 'AT%XSYSTEMMODE = 0,1,1,0
' timed out
2019-08-30T12:57:34.269Z DEBUG modem >> AT%XPCO=0\x0D\x0A
2019-08-30T12:57:35.281Z ERROR Error: 'AT%XPCO=0
' timed out
2019-08-30T12:57:39.776Z INFO Modem port is closed
2019-08-30T12:57:39.782Z INFO Modem port is opened
2019-08-30T12:57:39.785Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:57:42.543Z DEBUG modem >> AT%XPCO=0\x0D\x0A
2019-08-30T12:57:43.545Z ERROR Error: 'AT%XPCO=0
' timed out
2019-08-30T12:57:44.279Z DEBUG modem >> AT%XPCO=0\x0D\x0A
2019-08-30T12:57:45.295Z ERROR Error: 'AT%XPCO=0
' timed out
2019-08-30T12:58:00.818Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:58:01.819Z ERROR Error: 'AT+CFUN?
' timed out
2019-08-30T12:58:03.346Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:58:04.352Z ERROR Error: 'AT+CFUN?
' timed out
2019-08-30T12:58:05.834Z INFO Modem port is closed
2019-08-30T12:58:05.841Z INFO Modem port is opened
2019-08-30T12:58:05.844Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:58:07.387Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:58:08.397Z ERROR Error: 'AT+CFUN?
' timed out
2019-08-30T12:58:11.682Z INFO Modem port is closed
2019-08-30T12:58:11.689Z INFO Modem port is opened
2019-08-30T12:58:11.692Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:58:13.803Z INFO Modem port is closed
2019-08-30T12:58:13.808Z INFO Modem port is opened
2019-08-30T12:58:13.811Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:58:15.547Z INFO Modem port is closed
2019-08-30T12:58:15.553Z INFO Modem port is opened
2019-08-30T12:58:15.557Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:58:20.217Z INFO Modem port is closed
2019-08-30T12:58:22.846Z INFO Modem port is opened
2019-08-30T12:58:22.849Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:58:31.073Z INFO Modem port is closed
2019-08-30T12:58:31.075Z ERROR Opening COM4: Access denied
2019-08-30T12:58:34.740Z ERROR Opening COM3: Access denied
2019-08-30T12:58:36.457Z INFO Modem port is opened
2019-08-30T12:58:36.460Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-08-30T12:58:40.620Z DEBUG modem >> AT\x0D\x0A
2019-08-30T12:58:41.623Z ERROR Error: 'AT
' timed out

[Heidi-Irene Harvey Sollie]

I got the 'timed out' error a few times too and restarting my computer fixed the issue. 

In addition, the modem has to be off to set the system mode, so run AT+CFUN=4 first. Sorry, I should have clarified that earlier.

[T1mS_]

Still the same after rebooting my pc.

IS there a way to reset the modem completely?

[T1mS_]

I also tried a SODAQ (https://shop.sodaq.com/sodaq-sara-sff-r412m.html) board today with LTE-M and NB-IoT capabilities. I was able to connect to the telekom network from exact the same spot like I'm trying to connect the thingy:91...

[Heidi-Irene Harvey Sollie]

There a few ways to reset the modem. However, the best way is just power cycling the Thingy:91, switching it off and on while trying to connect. 

[T1mS_]

I will reset my notebook today and check if anything will change after that.

I'm trying to find out if thingy:91 would be a suitable solution for our startup for the iot solution. At the moment I'm having a hard time with it, because the startup was very tough or actually not possible at all. Do you have any more ideas on how we can reach a satisfactory point for both of us?