NRF9160 : New customized board can't connect to network

Hello, Nordic team

We have been studying Nordic for some time and are now in the stage of product research and development. We bought an nrf9160DK from a local agent at the earliest and then made several customized boards by ourselves. We now have a networked problems again, everything is okay before the custom board, including networking, positioning, local reason, can only buy local NB - IOT CARDS, now our second custom board out, hardware and peripheral circuit and the first edition, but the network problem is very big, specific as follows.

When we burn the HTTP/HTTPS/MQTT related routine, it always reports this error (Figure 1). The system mode of NB-IOT is also configured in prj. conf flie. After checking the LOG, it is found that "CEREG" returns "2" not registered on the network. I have tested the same program and card on other DK, including the customized board before, without any problems. I am not clear about what is going on at the moment, and it is a little confusing. I burned an instance of AT_Client, and the query through AT instruction is the same, but it can't be connected to the network. Now I don't know how to do it and what to test next. However, I tested the program of asset_cracker yesterday, and "LTE_Link Monitor" can search the network and connect to the network, but since it is not possible to register its own board on the cloud, it is also not possible. I would like to ask if there are other steps for registering the new board on the Internet. Or what is the network configuration of asset_cracker? thank you,Please reply as soon as possible.

Parents
  • Hello,

    what application are you running that is treating 0 as an error? According to getaddrinfo() documentation, 0 should be returned on success.

    Did you flash the modem firmware to the modem? What version?

    Can you show the Link Monitor log from the failed case as well?

    What is "asset_cracker"? Did you mean "asset_tracker"? There is no "asset_cracker" sample in the SDK.

  • Hi, thank you for your reply.

    It's Asset Tracker V2. Please ignore my mistake. Now we have found that this error is a DNS resolution error, after searching for a solution, we added "AT%XEPCO=0" AT command in each networking example in advance, changed the content of the protocol, now we have solved this problem. However, we still don't know how this reason can be generated, because we haven't encountered it before. Could you help me find the reason?

    I also want to ask, is there a command like "AT%XEPCO=0" configured in the prj.conf file?

  • Jerry zheng said:
    However, we still don't know how this reason can be generated, because we haven't encountered it before. Could you help me find the reason?

    What reason?

    Jerry zheng said:
    I also want to ask, is there a command like "AT%XEPCO=0" configured in the prj.conf file?

    Yes, you can set CONFIG_PDN_LEGACY_PCO=y in prj.conf.

Reply Children
No Data
Related