Hi again Jared,
I’m having trouble registering this thing-plus at nrfcloud.com
I’ve tried using device ID’s in the formats…
I’m told you can provide a new certificate?
Thanks,
David
Can you run AT%CMNG=1 in LTE link monitor and share the results?
AT%CMNG=1
%CMNG: 0,6,“0606060606060606060606060606060606060606060606060606060606060606”
%CMNG: 16842753,0,“0000000000000000000000000000000000000000000000000000000000000000”
%CMNG: 16842753,1,“0101010101010101010101010101010101010101010101010101010101010101”
%CMNG: 16842753,2,“0202020202020202020202020202020202020202020202020202020202020202”
OK
Barliesque it’s already registered. So all you need to do is add it to your nrfcloud dashboard. The device ID should be thing-plus-<your IMEI> and make sure you use 7753 as the password
Hi again,
I’ve got a group of 20 boards that are all now flashed and appear to be working fine. However, I’m unable to register them at nrfCloud.com, as I did with the previous one. Running AT%CMNG=1 produces the same result as above. But when I try to register using thing-plus-<IMEI> and 7753 for the password, I get an Error 40412. I’ve also tried feather-<IMEI> with the same result.
Barliesque can you email me the list of IMEIs you’re trying to register? hello@jaredwolff.com
Sent.
Barliesque thanks!
In order to add them to your nRF Cloud account they must be configured and connected to nRF Cloud. (Yes, a bit goofy, I know)
Here’s someone else who had the same issue earlier: https://devzone.nordicsemi.com/f/nordic-q-a/56331/unable-to-add-lte-device-on-nrf-cloud
So, as far as I can tell, your devices have been provisioned correctly. So fingers crossed that it’s just this one problem. 
Hope that helps!
I’m not quite clear what I need to do. That thread talks about the modem not connecting and maybe needing an update? I have device #1 connected to LTE Link Monitor right now, and it says the Modem port is opened and five different networks are available. After a few minutes, though, it comes up saying “Not connected to cloud, abort cloud publication”.
Can you share your log?
A few more related questions:
Are you sure your SIM is provisioned, inserted and working? Make sure that the SIMs you’re using are capable connecting where you are located as well.
Okay, how can I best confirm those things? What would you like me to put into Link Monitor to produce a useful log?
SIM card is definitely inserted. I had to manually remove it to take down the SIM number, before re-inserting.
I would open up the at_client sample and make sure it makes a connection. Are you familiar with the process?
https://docs.jaredwolff.com/nrf9160-nrf-connect-desktop.html#using-with-lte-link-monitor
You’ll also need an antenna in the right place too. Hope you have one of those.
Okay. I’ll build and flash the at_client sample. Yes, all of these devices have LTE antennae and are connected to the correct socket.
Barliesque Okay. I’ll build and flash the at_client sample. Yes, all of these devices have LTE antennae and are connected to the correct socket.
jaredwolff
Okay, I’ve run the at_client sample and e-mailed you the log. Hopefully that’ll be illuminating!
Barliesque I replied but I’ll also put that here
It’s easier to look at the output and let LTE Link Monitor tell you what’s happening. Particularly the status icons (UART, Modem, UICC, LTE, PDN).
Hit the AT+CFUN=1 and then AT+CFUN=? occasionally to see if you connect. the LTE and PDN icons should turn green. The rework should also show up above the Search networks button.
Hi Jared,
Me again. I’ve got just one device left that I can’t seem to register on nRFCloud.com
Modem, UICC, LTE and PDN all light up green in LTE Link Monitor.
The SIM is registered and shows as connected on Hologram.io
When I try to register the device on nRFCloud.com with DeviceID: “thing-plus-[IMEI]” and PIN: 7753 (just as I have done successfully now with 20 other devices) this one comes up with the error 40412.
I’ve e-mailed you the IMEI of the device. Really hoping you can help me over this one final hurdle!
Thanks,
David
@Barliesque is this the same device you checked earlier with AT%CMNG=1? If not can you check if it has certs?
This is a different device.
2022-01-08T17:39:28.542Z DEBUG modem >> AT%CMNG=1
2022-01-08T17:39:28.554Z DEBUG modem << %CMNG: 0,6,"0606060606060606060606060606060606060606060606060606060606060606"
2022-01-08T17:39:28.556Z DEBUG modem << OK
How do I check if it has certs? Or does that log tell you what you need to know?
Looks different from the one I posted earlier for that other device, so I’m guessing this shows something’s not registered.
Ahh, ok. This one has no certs which is why you’re having such trouble!
Barliesque How do I check if it has certs? Or does that log tell you what you need to know?
The AT%CMNG=1 command lists all the certs in the secure store. The tag number is important to look at. The tag for Nordic’s service is 16842753. Yours doesn’t have the entry like before:
AT%CMNG=1
%CMNG: 0,6,“0606060606060606060606060606060606060606060606060606060606060606”
%CMNG: 16842753,0,“0000000000000000000000000000000000000000000000000000000000000000”
%CMNG: 16842753,1,“0101010101010101010101010101010101010101010101010101010101010101”
%CMNG: 16842753,2,“0202020202020202020202020202020202020202020202020202020202020202”
OKThat’s what it should look like 
Let me generate some credentials for it an I’ll send you the info.
Huzzah!!! Thank you so much for your help.
One question. It definitely appears to be working now, communicating through to nRFCloud.com just fine. In LTE Link Monitor, I’m seeing the following in the log, pinging away once per second…
2022-01-08T21:12:37.149Z DEBUG modem << +CESQ: 99,99,255,255,11,50
2022-01-08T21:12:37.154Z DEBUG modem << OK
2022-01-08T21:12:38.053Z DEBUG modem >> AT+CESQ
2022-01-08T21:12:38.160Z DEBUG modem << +CESQ: 99,99,255,255,12,49
2022-01-08T21:12:38.164Z DEBUG modem << OK
2022-01-08T21:12:39.047Z DEBUG modem >> AT+CESQ
2022-01-08T21:12:39.148Z DEBUG modem << +CESQ: 99,99,255,255,11,49
2022-01-08T21:12:39.153Z DEBUG modem << OK
2022-01-08T21:12:40.050Z DEBUG modem >> AT+CESQ
2022-01-08T21:12:40.060Z DEBUG modem << +CESQ: 99,99,255,255,11,49
2022-01-08T21:12:40.064Z DEBUG modem << OK
2022-01-08T21:12:41.048Z DEBUG modem >> AT+CESQ
2022-01-08T21:12:41.161Z DEBUG modem << +CESQ: 99,99,255,255,13,49
2022-01-08T21:12:41.166Z DEBUG modem << OK
2022-01-08T21:12:42.052Z DEBUG modem >> AT+CESQ
2022-01-08T21:12:42.150Z DEBUG modem << +CESQ: 99,99,255,255,14,49
2022-01-08T21:12:42.155Z DEBUG modem << OK
2022-01-08T21:12:43.047Z DEBUG modem >> AT+CESQ
2022-01-08T21:12:43.150Z DEBUG modem << +CESQ: 99,99,255,255,13,49
2022-01-08T21:12:43.155Z DEBUG modem << OK
2022-01-08T21:12:44.052Z DEBUG modem >> AT+CESQ
2022-01-08T21:12:44.160Z DEBUG modem << +CESQ: 99,99,255,255,10,49
2022-01-08T21:12:44.165Z DEBUG modem << OK
2022-01-08T21:12:45.047Z DEBUG modem >> AT+CESQ
2022-01-08T21:12:45.155Z DEBUG modem << +CESQ: 99,99,255,255,10,49
2022-01-08T21:12:45.159Z DEBUG modem << OK```Barliesque Huzzah!!! Thank you so much for your help.
Wooooo!
Barliesque One question. It definitely appears to be working now, communicating through to nRFCloud.com just fine. In LTE Link Monitor, I’m seeing the following in the log, pinging away once per second…
Those are the auto-updates. That’s a feature in LTE Link Monitor. You can turn them off here:
Ah ha! I thought it would be something coming from the monitor itself.
Thank you, so much for all your help.
Hey Jared,
That one device that needed credentials – seems to be working as expected. However, there’s fairly continuous activity across the network. In LTE Monitor, I see the following coming out of it every so often for no apparent reason. Could this be responsible for some unintended network traffic?
2022-01-18T20:41:47.977Z DEBUG modem << +CSCON: 1
2022-01-18T20:41:54.169Z DEBUG modem << %CESQ: 46,2,16,2
2022-01-18T20:41:54.786Z DEBUG modem << +CSCON: 0
2022-01-18T20:41:54.801Z DEBUG modem << %CESQ: 46,2,11,1
2022-01-18T20:42:47.986Z DEBUG modem << +CSCON: 1
2022-01-18T20:42:55.048Z DEBUG modem << %CESQ: 44,2,6,0
2022-01-18T20:42:55.345Z DEBUG modem << +CSCON: 0
2022-01-18T20:43:47.912Z DEBUG modem << %CESQ: 48,2,11,1
2022-01-18T20:43:48.255Z DEBUG modem << +CSCON: 1
2022-01-18T20:43:49.657Z DEBUG modem << %CESQ: 46,2,6,0
2022-01-18T20:43:51.111Z DEBUG modem << %CESQ: 46,2,13,1
2022-01-18T20:43:55.569Z DEBUG modem << +CSCON: 0
2022-01-18T20:44:48.453Z DEBUG modem << +CSCON: 1
2022-01-18T20:44:51.269Z DEBUG modem << %CESQ: 44,2,8,1
2022-01-18T20:44:51.909Z DEBUG modem << %CESQ: 44,2,13,1
2022-01-18T20:44:54.789Z DEBUG modem << %CESQ: 44,2,8,1
2022-01-18T20:44:56.047Z DEBUG modem << +CSCON: 0
2022-01-18T20:44:56.097Z DEBUG modem << %CESQ: 45,2,13,1
2022-01-18T20:45:48.662Z DEBUG modem << +CSCON: 1
2022-01-18T20:45:56.126Z DEBUG modem << +CSCON: 0
2022-01-18T20:45:59.764Z DEBUG modem << %CESQ: 47,2,8,1
2022-01-18T20:46:48.681Z DEBUG modem << +CSCON: 1Barliesque I would try to figure out what your RSRP is. (Reference Signal Received Power aka RSSI) Looks like maybe your device is jumping to another tower or connecting/reconnecting to the same one. It’s hard to tell here.
You can issue the %XMONITOR command to view the RSRP. (Or use the modem_info API to do the same) Here’s the latest AT commands reference:
https://infocenter.nordicsemi.com/pdf/nrf91_at_commands_v2.0.pdf
jaredwolff Looks like maybe your device is jumping to another tower or connecting/reconnecting to the same one.
Hmmm… Pressing on LTE Link Monitor’s “Show Serving Station Location” button, I get a map with a large blue ring–presumably representing the station’s signal radius? My location is actually just outside that blue ring. Sounds like something that might cause what you’re talking about.
2022-01-21T19:18:08.352Z DEBUG modem >> AT%XMONITOR
2022-01-21T19:18:08.422Z DEBUG modem << %XMONITOR: 5,"","","310260","3C7A",7,12,"013BCE04",129,5035,45,27,"","11100000","11100000","01001001"Looks like the RSRP is 27 which is fairly low.