This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF9160 DK - Asset Tracker Application - Connect to EMEA nRF Cloud?

Hi,

I am testing the nRF9160 DK and used the asset tracker application with the IBasis SIM.
Application works fine under CAT M1 network (IBasis SIM is roaming on o2/Telefonica in Germany), but I can't connect to the MQTT broker / nRF cloud on NB-IoT.
(Modem is attached on NB-IoT, signal level (RSRP, RSRQ) is good).

Most likely, this is due to latency issues, as MQTT runs on TCP, which already fairly heavy for NB IoT.

Secondly, I noticed that the application uses a NRF cloud / MQTT server in the US (east coast, Virgina).
Domain: a2n7tk1kp18wix-ats.iot.us-east-1.amazonaws.com

I can connect to MQTT brokers nearby in Europe on NB-IoT (used for example the MQTT sample application), TCP connection was stable enough to support MQTT.
Question is hence, is there a server/gateway for the nRF cloud MQTT broker in Europe or other regions than US East?

Thanks.

BR
Kevin

Parents
  • Hello again Kevin,

    My apologies for the delayed answer. It took me some time double-checking this internally.

    TCP is not always supported in NB-IoT networks, and that is generally a known issue in some networks in Germany.

    But we might need modem traces here to find the root cause of the issue, as we are not sure what the root cause could be.

    I don’t know if this is something you wanna try, but you can follow this guide to do so.

    Thanks and regards,

    Markus

  • Hi Markus,

    Sorry, I didn't get to that earlier, but I have just looked at what things I need to do. Currently, everything is prepared for the modem tracing, I am using the asset tracker v1.

    However, it seems modem traces are on the first COM port, same as my application log. On the nRF9160 DK, this seems to be UART1 (within Zephyr called UART0?), nRF91 UART2 (within Zephyr called UART1) is disabled on the DK (DTS file states: /* Disable UART1, because it is used by default in TF-M */).

    It seems as if I need to flip more than just one switch.
    What is the recommended setup, naturally I want to keep my application UART console?

    ADDING: Does it not cause issues if the modem trace + application logs & AT command interface are on the same COM port?

    BR
    Kevin

Reply
  • Hi Markus,

    Sorry, I didn't get to that earlier, but I have just looked at what things I need to do. Currently, everything is prepared for the modem tracing, I am using the asset tracker v1.

    However, it seems modem traces are on the first COM port, same as my application log. On the nRF9160 DK, this seems to be UART1 (within Zephyr called UART0?), nRF91 UART2 (within Zephyr called UART1) is disabled on the DK (DTS file states: /* Disable UART1, because it is used by default in TF-M */).

    It seems as if I need to flip more than just one switch.
    What is the recommended setup, naturally I want to keep my application UART console?

    ADDING: Does it not cause issues if the modem trace + application logs & AT command interface are on the same COM port?

    BR
    Kevin

Children
No Data
Related