• State Not Answered
  • Replies 2 replies
  • Subscribers 69 subscribers
  • Views 51 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 337132
Options

Monitoring LTE-M/NB-IoT Packets from Thingy:91

Roshan Nepal

Hi,

I’m looking to monitor LTE-M or NB-IoT packets sent by the Thingy:91 in real-time using an app or software. Currently, I’m using the Thingy:91 to send temperature logs to Microsoft Azure Cloud. However, during the development phase, I’d prefer not to wait for Azure Cloud notifications to verify the logs. Instead, I’d like to confirm the operation immediately, especially since I’m experimenting with different configurations using an external power supply instead of the built-in battery.

I’m looking for an app or tool that lets me observe the LTE packets being sent and received—similar to how the nRF Connect mobile app displays BLE beacons. Connecting the Thingy:91 to a computer via a serial port isn’t feasible, as it would then draw power from the computer rather than the external power source.

Looking forward to your suggestions!

Parents
  • 0

    > However, during the development phase, I’d prefer not to wait for Azure Cloud notifications to verify the logs.

    Not sure, what "wait" means in seconds?

    I use CoAP/DTLS 1.2 CID and Eclipse/Californium CoAP-S3-Proxy , that works within a few seconds. For LTE-M from the Thingy:91 to the web-browser it takes about 4s (average). For NB-IoT it's about 8s, but there especially the worse cases may got up to 15-20s mainly for the radio-network reattach. Viewing the log on the cloud vm that time is slightly shorter.

    > I’m looking for an app or tool that lets me observe the LTE packets being sent and received

    I tried to use SDR (software defined radio), but at that time it was only possible to see some initial traffic from a base-station, but nothing related to a device. See  Does someone has experience with SDR analyzing a nRF9160 ?

    I guess, you're interested in the power consumption?

    What do you want to show?

    The lowest power consumption possible? Forget all the TCP stuff. That's ways worse than UDP.

    The lowest power consumption for TCP? You don't need to do some research, just use a large battery :-).

    Do you want your own numbers? Or just a "good point to start"? In a common radio environment indoor, my client is able to send data every hour for a year. Outside it may be longer (better radio). In the basement shorter (worse radio). Using Jared's nrf9160-feather and a 3000mAh battery, outside, shows a forecast of about 5 years.

Reply
  • 0

    > However, during the development phase, I’d prefer not to wait for Azure Cloud notifications to verify the logs.

    Not sure, what "wait" means in seconds?

    I use CoAP/DTLS 1.2 CID and Eclipse/Californium CoAP-S3-Proxy , that works within a few seconds. For LTE-M from the Thingy:91 to the web-browser it takes about 4s (average). For NB-IoT it's about 8s, but there especially the worse cases may got up to 15-20s mainly for the radio-network reattach. Viewing the log on the cloud vm that time is slightly shorter.

    > I’m looking for an app or tool that lets me observe the LTE packets being sent and received

    I tried to use SDR (software defined radio), but at that time it was only possible to see some initial traffic from a base-station, but nothing related to a device. See  Does someone has experience with SDR analyzing a nRF9160 ?

    I guess, you're interested in the power consumption?

    What do you want to show?

    The lowest power consumption possible? Forget all the TCP stuff. That's ways worse than UDP.

    The lowest power consumption for TCP? You don't need to do some research, just use a large battery :-).

    Do you want your own numbers? Or just a "good point to start"? In a common radio environment indoor, my client is able to send data every hour for a year. Outside it may be longer (better radio). In the basement shorter (worse radio). Using Jared's nrf9160-feather and a 3000mAh battery, outside, shows a forecast of about 5 years.

Children
  • 0 in reply to Achim Kraus

    Thanks. For now, I’m interested in knowing the total energy consumed by the device from the moment it’s turned on until I receive a message in the cloud.

    Also, does the Thingy:91 automatically select between LTE-M and NB-IoT based on network availability? Since LTE-M connection is faster than NB-IoT, can I stick to LTE-M by setting these tags in the prj.conf?

    CONFIG_LTE_NETWORK_MODE_LTE_M=y

    CONFIG_LTE_NETWORK_MODE_NBIOT=n

Related