rns.recipes

Does anyone know of a way to reduce GPS polling time on RNode? On my current setup, my node can last a week without GPS enabled, with it enabled, maybe 2 days. I tried the RNode firmware from https://flasher.rns.moscow/ as it added an on-screen configuration for GPS polling, but I consistently get a firmware corrupted message after setting it and restarting the node.

A. Non wrote:

Does anyone know of a way to reduce GPS polling time on RNode? On my current setup, my node can last a week without GPS enabled, with it enabled, maybe 2 days. I tried the RNode firmware from https://flasher.rns.moscow/ as it added an on-screen configuration for GPS polling, but I consistently get a firmware corrupted message after setting it and restarting the node.

GNSS support is kinda rudimentary at the moment, I am sorry. They are so frequent because we are currently experiencing region-wide GNSS jamming.

I will reduce the polling rates.

Oops, posted as anon. Are you running a Heltec T114?
The main reason for implementing GNSS is to implement wardriving coverage metrics.

Nickie wrote:

Oops, posted as anon. Are you running a Heltec T114?
The main reason for implementing GNSS is to implement wardriving coverage metrics.

Thanks for replying! You're doing great work! I am running a T114. GNSS works great when it's enabled, but trying to turn it off using the on screen menu will cause the firmware corrupt message to appear after the next restart. Sorry, my first message didn't provide that detail.

A. Non wrote:

Nickie wrote:

Oops, posted as anon. Are you running a Heltec T114?
The main reason for implementing GNSS is to implement wardriving coverage metrics.

Thanks for replying! You're doing great work! I am running a T114. GNSS works great when it's enabled, but trying to turn it off using the on screen menu will cause the firmware corrupt message to appear after the next restart. Sorry, my first message didn't provide that detail.

Thank you, my bad, it was fixed earlier, I will upload shortly. I am still planning on how to better utilize GNSS though. It doesn't have any KISS-commands or anything as of yet, I was mostly busy with incorporating LXMF messaging using Chad Atterman's brilliant uReticulum/microStore to regular ESP32-S3 nodes as it seems to be a popular request to be able to ping/send a quick message "in the field".

A disclaimer, though: I do use LLMs to speed up development but I don't employ any automated test harnesses and tend to verify code and functionality manually and it takes time and bugs creep through.

Nickie wrote:

A. Non wrote:

Nickie wrote:

Oops, posted as anon. Are you running a Heltec T114?
The main reason for implementing GNSS is to implement wardriving coverage metrics.

Thanks for replying! You're doing great work! I am running a T114. GNSS works great when it's enabled, but trying to turn it off using the on screen menu will cause the firmware corrupt message to appear after the next restart. Sorry, my first message didn't provide that detail.

Thank you, my bad, it was fixed earlier, I will upload shortly. I am still planning on how to better utilize GNSS though. It doesn't have any KISS-commands or anything as of yet, I was mostly busy with incorporating LXMF messaging using Chad Atterman's brilliant uReticulum/microStore to regular ESP32-S3 nodes as it seems to be a popular request to be able to ping/send a quick message "in the field".

A disclaimer, though: I do use LLMs to speed up development but I don't employ any automated test harnesses and tend to verify code and functionality manually and it takes time and bugs creep through.

Amazing, I'll keep an eye out. Appreciate it! :)

@Nickie

Just flashed the latest and can confirm reboots are successful without the firmware corrupt message after enabling GPS and setting the polling interval. Thank you so much!