• State Verified Answer
  • Replies 17 replies
  • Subscribers 74 subscribers
  • Views 1694 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 312769
Options

LTE-M on nrf9160 custom PCB

DunKCubik

Hi,

 I am currently writing the firmware for a custom PCB with the nrf9160 SOC onboard.

I did much of the development work on the nrf9160dk dev kit.

I am running into issues getting LTE-M and MQTT working on the custom PCB.

To test I have used the "cellfund_less4_exer1" basic LTE-M and MQTT example and it works fine on the dev kit but not on the custom PCB.

I have 2 sims (the included ibasic one and a "simhero" card) - both work fine on dev kit but neither on the custom PCB.

I've read a few posts that suggest that the reason it won't work on the custom PCB because of the device ID and certificate issues - I'm a bit confused about this and not sure what to do to resolve it. Any help would be gratefully received.

On the nrf9160dk I get the following...

 

00> [00:00:00.634,307] <inf> Lesson4_Exercise1: Connecting to LTE network
00> [00:00:02.264,862] <inf> Lesson4_Exercise1: RRC mode: Connected
00> [00:00:04.353,698] <inf> Lesson4_Exercise1: Network registration status: Connected - roaming
00> [00:00:04.353,820] <inf> Lesson4_Exercise1: Connected to LTE network
00> [00:00:04.481,811] <inf> Lesson4_Exercise1: IPv4 Address found 91.121.93.94
00> [00:00:05.050,872] <inf> Lesson4_Exercise1: MQTT client connected
00> [00:00:05.050,903] <inf> Lesson4_Exercise1: Subscribing to: cubik/subscribe/topic len 21
00> [00:00:05.370,788] <inf> Lesson4_Exercise1: SUBACK packet id: 1234
00> [00:00:10.347,778] <inf> Lesson4_Exercise1: Publishing: {"heater_on":true,"heater_temp":{"unit":"f","value":280,"humidity":450,"moisture":46}}
00> [00:00:10.347,808] <inf> Lesson4_Exercise1: to topic: cubik/publish/topic len: 19
00> [00:00:10.685,913] <inf> Lesson4_Exercise1: PUBACK packet id: 14289
(Connection lost)

Using the same code on the custom PCB I get RCC connected then straight to idle, sometimes toggling between the two states..

00> [00:00:00.614,624] <inf> Lesson4_Exercise1: Connecting to LTE network
00> [00:00:05.951,477] <inf> Lesson4_Exercise1: RRC mode: Connected
00> [00:00:07.269,378] <inf> Lesson4_Exercise1: RRC mode: Idle

What am I doing wrong with my custom PCB??

Cheers

Duncan

Parents
  • 0

    Not sure what I've done now but getting these errors on the dev kit now when I'm trying "cellfund_less4_exer1" the simple MQTT example!

    00> [00:00:00.253,906] <inf> Lesson4_Exercise1: Connecting to LTE network
00> [00:00:00.253,906] <err> lte_lc: Failed to get system mode, error: -1
00> [00:00:00.253,936] <err> lte_lc: Could not get current system mode, error: -14
00> [00:00:00.253,936] <inf> Lesson4_Exercise1: Modem could not be configured, error: -14
00> [00:00:00.254,058] <err> Lesson4_Exercise1: getaddrinfo failed: -11

    Can't see that I've changed anything at all, so very weird. 

    Any ideas?

  • 0 in reply to DunKCubik

    Hello, 

    I have 2 sims (the included ibasic one and a "simhero" card) - both work fine on dev kit but neither on the custom PCB.

    Can you verify that both SIM card have data available? I'm not familiar with simhero, do they support LTE-M and NB-IoT?

    DunKCubik said:
    Can't see that I've changed anything at all, so very weird. 

    With regards to your last comment, can you please download our pre-compiled firmware package from the nRF9160DK download page and program the AT Client (img_app_bl\nrf9160dk_at_client_2023-06-01_0677b099.hex)

    Then open the Cellular Monitor in nRF Connect for Desktop. First connect to the nRF9160DK, and then click on open Serial Terminal. In the Terminal type AT and hit send to verify function. It should respond with OK. Next you need to click on Refresh Dashboard in the Cellular Monitor. This will issue several commands in the Serial Terminal. Copy the output and paste here, please. 

    Thanks.

    Kind regards,
    Øyvind

  • 0 in reply to DunKCubik

    So far there seems to be an issue with the SIM. 

    The reason I wanted to you to test with the AT client was to get more information regarding the network status. How old is the iBasis SIM, have you verified that this has prepaid data? This SIM is delivered with 10Mb. You should be able to see status on nRF Cloud if you have registered it there.

    Do you see the same on the custom board as well? Can you connect to your custom board?

  • 0 in reply to Øyvind

    Ok that makes sense, although it has been working fine up until Yesterday. I did update the modem firmware and loaded asset tracker into the dev board and it could have been after this that I noticed the issues.

    I have plenty of data on the ibasis SIM but have just noticed it says not connected to a device.. could this be the issue?

  • 0 in reply to DunKCubik

    The custom board has the same issue. It was talking to the LTE-M network as I showed in my 1st post (RCC connected -> RCC idle), but now same as dev kit.

  • 0 in reply to DunKCubik

    Can you please provide a modem trace from the custom board? If you are seeing the same issue on the DK it would be good to have a modem trace from this as well.

  • 0 in reply to Øyvind

    Hi, sorry I have got sidetracked with other issues at the moment.

    We have bought a new nr9160 devkit so I'll try that with the new ibasis SIM later on today if I can.

    Regarding the modem trace...can this be done over RTT as I do not have a UART free on the custom PCB?

    Cheers

    Duncan

Reply Children
Related
Terms of service