Software and Protocols - All Comments

RE: Field verification of GNSS on the nRF91 Series

JaniM — Thu, 08 May 2025 12:32:13 GMT

Hello,

Cold start is one example, first fix is very different measurement than the following TTFF measurements if device/GNSS receiver is kept up and running and no acquired information by the GNSS receiver (Ephemerides, Time and TCXO offset etc) has been tampered/removed intentionally by the user.

Depending then on the measurement interval the GNSS received is then either in Hot Start or Warm Start mode after the initial Cold Start fix.

Having TTFF measurements performed with A-GNSS included (A-GPS, if there's not assistance data for other constellations) it is then something in between Cold Start and Hot Start operating modes, something similar to Warm Start roughly.

I hope this helps!

Br,

Jani M

RE: Field verification of GNSS on the nRF91 Series

Roman Veselskyi — Thu, 10 Apr 2025 14:59:11 GMT

"Please note that the very first fix after device start-up is a rather different measurement than any of the following consecutive fixes. "

May you please tell more about it? Does it also relate to the A-GPS?

RE: The four kinds of data you need to consider when developing an IoT product

CallumGriffiths — Mon, 27 May 2024 05:21:45 GMT

The author of the topic offers some good ideas. Personally, I used the blog article https://www.mightycall.com/blog/call-management-system/ to improve the performance of my business. The article helped me better understand how to effectively manage calls, streamline processes, and improve customer service. I implemented several recommendations from the article, such as using modern call management systems and automating some processes, which allowed me to improve communication and increase customer satisfaction.

RE: Connecting to AWS cloud services using the nRF9160

Hakon — Fri, 19 Apr 2024 08:48:22 GMT

I updated the sample again to be compatible with NCS 2.6.0.

RE: Monitoring nRF9160 data usage with connectivity statistics

J0sh1101 — Fri, 24 Feb 2023 13:53:15 GMT

Hey, I tried your approach, but the header modem/at_cmd.h is not available anymore in the SDK 2.2.99-dev3. Is there any other way of doing it?

RE: nRF Cloud Access Provisioning

Torje — Wed, 07 Dec 2022 14:52:46 GMT

Thanks for making this guide. Its been hard to read up on these things, but the guide and flowchart made it all a bit clearer!

RE: Connecting to AWS cloud services using the nRF9160

johnwest — Wed, 03 Nov 2021 17:06:53 GMT

Hello Hakan,
Any updates?
Can you please try to run with the latest (1.3.1) firmware drop?
Thanks!
John

RE: nRF9160 DK: Offloading Bluetooth Low Energy related tasks to nRF52840 SoC

dtquang89 — Mon, 05 Jul 2021 09:47:14 GMT

I have questions regarding the communication between nRF52 and nRF91.

1. Is this UART connection similar to enable interface between two chips, by adding the below line on overlay file?

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:17099f24-56d9-4914-8463-48a5b76e9b75:type=c_cpp&text=%23include%20%3Cnrf9160dk_uart1_on_if0_3.dtsi%3E]

2. In my application, I am using NUS service, and using uart0. Now I want to create another uart, uart1, in order to pass the data I received from BLE on nRF52 to nRF91, and send it over LTE network. But on the nRF52 side, I think it is not working. Probably there is something wrong with the device tree or configuration, since I got the device.

Do you have any idea? Thank you very much.

RE: nRF9160 DK: Offloading Bluetooth Low Energy related tasks to nRF52840 SoC

dtquang89 — Mon, 05 Jul 2021 07:55:29 GMT

Thank you for interesting approach.

RE: nRF9160 DK: Offloading Bluetooth Low Energy related tasks to nRF52840 SoC

Brett — Mon, 31 May 2021 10:33:47 GMT

Not sure if I should post here, or to the community in general, but .....

What you have created is basically what I am looking for, a simple way to pass data between the 9160 & 52840. I have pulled the above code, where the 9160 compiles and installs fine, but the 52840 gives an error with respect to CONFIG_BOARD_NRF9160DK_INTERFACE0_MCU=y and CONFIG_BOARD_NRF9160DK_INTERFACE1_MCU=y

/code/sdk-nrf/samples/nrf9160/nrf9160dk_serial/nrf52840/prj.conf:7: warning: attempt to assign the value 'y' to the undefined symbol BOARD_NRF9160DK_INTERFACE0_MCU

Did you run into this error - as I didnt see anything in the community when I searched for the error.

I am running on the 9160dk.

RE: nRF9160 DK: Offloading Bluetooth Low Energy related tasks to nRF52840 SoC

Thomas Page — Fri, 15 Jan 2021 15:05:30 GMT

This is a really interesting article. How difficult would it be to have a similar approach to other HA protocols?

RE: Enabling and testing TLS in mqtt_simple

paul_tanner — Wed, 25 Nov 2020 12:44:18 GMT

I have followed these instructions and got to the point where it says "At this point the sample should compile but won't use TLS". It does compile but does not make a connection. I am building for 9160-DK (ns) on the command line on MacOS. I suspect that the problem may be that I am trying to use the supplied iBasis SIM straight out of the box.

RE: Monitoring nRF9160 data usage with connectivity statistics

Tjaz — Wed, 09 Sep 2020 11:55:17 GMT

Is there a way to determine air time? Aka how long the modem was in an active state of communications?
AT%XCONNSTAT? only tells you how much data was transmitted.

RE: How to connect nRF9160 DK to Google Cloud

mcallistertad — Tue, 28 Jul 2020 20:33:54 GMT

Thanks for the tutorial Marte!

For anyone interested, I've ported the gcloud library to the latest ncs version and the Thingy91.

This application gets readings from the onboard environmental sensor and publishes to an MQTT topic as described in the post above.

https://github.com/mcallistertad/nrf_google_iot_core/

RE: Enabling and testing TLS in mqtt_simple

m9th — Wed, 18 Mar 2020 18:22:28 GMT

I added all of the code snippets above to the files indicated. I reloaded the project from the open nfrconnect sdk project. When I look in main.c all of the conditionals for CONFIG_MQTT_LIB_TLS remain grayed out. prj.conf has CONFIG_MQTT_LIB_TLS=y. What am I missing?