• State Not Answered
  • Replies 13 replies
  • Subscribers 91 subscribers
  • Views 3167 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 287857
Options

MQTT connect error -45

Jagruti

Hello,

I am using MQTT+TLS on nRF9160DK. In the development stage, I followed this link https://devzone.nordicsemi.com/guides/cellular-iot-guides/b/software-and-protocols/posts/enabling-and-testing-tls-in-mqtt_5f00_simple to use MQTT+TLS. Everything worked properly without any errors.

Now we are in the pre production. We have created 50 custom boards with nRF9160 on it. I created the tls certificates and programmed in the similar manner. All the custom boards could connect to the mqtt server and there was the communication between nRF9160 and the mqtt server.

After 3-4 months of testing, on few cards there is mqtt connect -45 error. Before few days these cards were completely functional.

I am using sec_tag 16842753. Can I use this sec_tag? What might be the cause of this error?

I re-programmed few non-functional cards by putting the application file + certificates in this way:

cred.py --CA_cert root.crt --client_cert BT36-chain.crt --client_private_key BT36.key --sec_tag 16842753 --program_app nRF9160.hex

These cards are working again.

So the question is why the cards doesn't connect to the mqtt server after few days even after the application hex file and the certificates are same?

Parents Reply Children
  • 0 in reply to Jagruti

    Hello, 

    Can you please provide some more details on what modem fw and nRF Connect SDK version you are running on your device? It would also be good to have full log output from the device when you get the error. We might also need a modem trace

    Jagruti said:
    1. Is it possible that the certificates are deleted from the modem at the given security tag after the ON/OFF of the nRF9160 various times?

    No, the certificate should stay in that security tag as long as you have not deleted them. Please see AT command  Credential storage management %CMNG.

    Jagruti said:
    2. Is this https://devzone.nordicsemi.com/guides/cellular-iot-guides/b/software-and-protocols/posts/enabling-and-testing-tls-in-mqtt_5f00_simple the correct method to store the tls certificates and use them?

    This looks correct, but I have not tested this way myself. One way to verify on your side is to provision the certificates using the Certificate Manager in LTE Link Monitor. In our documentation you should be able to follow the Provisioning the nRF Cloud certificate

    After 3-4 months of testing, on few cards there is mqtt connect -45 error. Before few days these cards were completely functional.

    Have you updated anything on your devices? Are the SIMs the same, any updates on the network? What about the MQTT server? 

    I am using sec_tag 16842753. Can I use this sec_tag? What might be the cause of this error?

    This sec tag is used to store the certificates for nRF Cloud. If you are not expecting to connect to nRF Cloud then it's OK to use this.

    Kind regards,
    Øyvind

  • 0 in reply to Øyvind

    Hello,

    Modem firmware version used is 1.2.0

    ncs version v1.0.0

    I checked with AT command %CMNG. All the certificates are deleted from the sec tag.

    I have not updated anything related to my devices. SIM cards and mqtt server, everything is same.

    If I put the same certificates which were used previously on the custom board, it starts working.

    So the question is why these certificates are deleted. I checked my application program, I never delete these certificates.

    This behaviour is seen on various boards.

    At every power on of nRF9160, I configure the modem, read imei number with cgsn command and check the presence of the SIM with xsim command, then turn off the modem. These are the operations which are carried out each time.

    All the boards are used for around 2-3 months by our testers and they were powered on for around 200-300 times.

    The boards which are not used by the testers but were programmed at the same time, have their certificates and are working normally.

    So I really don't understand what is the cause of this problem.

  • 0 in reply to Jagruti

    Is there a reason for working with an old modem FW and NCS version? Several improvements have been introduced, specifically for NCS i.e. currently at v1.9.1

    -Øyvind

  • 0 in reply to Øyvind

    I had started development 2 years ago, at that time I started working with ncs v1.0.0

    To update to other ncs versions, I had to change various functions in my program as the libraries were changed. To avoid this I rested on the v1.0.0.

    Is there any guide to know which libraries were modified for certain ncs version, so that it might help to change the program.

    This current batch of custom boards had nRF9160 revision 1 Build code B0.

    For the next batch, we have used nRF9160 revision 2 Build code B1. Modem firmware will be 1.3.1. Do I need to update ncs version v1.9.1?

    Do you think the certificates are deleted because of the older versions of modem firmware and ncs?

  • 0 in reply to Jagruti

    Can you please provide an image of the device markings? Also, can you please run at client and issue the command AT+CFUN?.

    Jagruti said:
    For the next batch, we have used nRF9160 revision 2 Build code B1. Modem firmware will be 1.3.1. Do I need to update ncs version v1.9.1?

    Yes, please use latest version of nRF Connect SDK with nRF9160 Rev 2.

    Jagruti said:
    Do you think the certificates are deleted because of the older versions of modem firmware and ncs?

    No, I don't think so, however, we know that earlier versions pre modem 1.0.0 had issues with file system.

    Jagruti said:
    Is there any guide to know which libraries were modified for certain ncs version, so that it might help to change the program.

    There is no guide unfortunately, other than the release notes. I would strongly encourage you update your application to a newer version of NCS.

Related
Terms of service