For the past 6 days I’ve had an NTN device at a location~300km away. It is working fine, except the “best_lat” and “best_lon” have not updated. They still show as my old location, but the “best_location_when” shows as the current time with “best_location_type”: “gps”. Something is not right. Can you please help me understand what is going on? The device is running FW 8.1.4.17149.
Hi @rberkelm
If your device is currently on LTS 8.1.4, I recommend updating to LTS v8.2.2, which includes several improvements and fixes related to GPS and Starnote communication.
Please give the update a try and let us know if it resolves the behavior you’re seeing. If the issue persists after updating, we can look into the next steps together.
Thanks
Youssif
Hi @Youssif
I’ve only had one of two devices back from the field so far for a firmware update. I performed the update on this device and tested it for 3 days before sending it back into the field. Unfortunately, it will not connect at all. This site is ~300km from me as the crow flies. I’ve established that the antenna is properly connected and has a clear view of the sky. The battery is full. Any ideas?
Hi @rberkelm - thanks for the details. Since the device was working for 3 days after the update, the battery is full, and the antenna has a clear view of the sky, my initial guess is that this could be a coverage/signal problem.
To understand the situation better, did the device manage to connect at all after being deployed to the field, or has it been offline the entire time? Also, has this specific location worked for this device in the past? And is the other device currently in the same location, or deployed elsewhere?
Once we have a bit more context, we can help narrow it down.
Thanks
Youssif
Hi @Youssif
Unfortunately this device has not connected at all since being deployed in the field. This is the second time we’ve tried to connect from this site. The first time was also unsuccessful and I recalled the device for a FW upgrade. This device is now running 9.2.3.17324. I got my client to switch it off, wait 12 hours and then repower it. No connection after 90 minutes. I then got him to turn it off again for another 4 hours before turning it on again. Still no connect after 90 minutes. I’m beginning to think Starnote is a very flakey RAT!
I don’t know if this is related, but while building more devices for this customer, I have a another Starnote device that just wouldn’t connect at home base. I tried many times over several days and for many hours each time. It was running 9.2.3.17324. I wondered if changing to LTS 8.2.3.17326 would help it connect. I did the FW change and eventually it DID connect, but only after >hour. After the first connect, subsequent connections happen within minutes. See this log.
notecard_2025-08-22T04_54_56.log (297.7 KB)
I wonder if this helps narrow down what is going on?
Hi @rberkelm
Thanks for sharing the details and the log, this is very helpful. You’re right that Starnote can be more sensitive to deployment conditions compared to other RATs, since it depends on a clear, unobstructed view of the sky to connect with distant geostationary satellites. Other factors such as weather and the need for a GPS fix can also influence performance. That said, with the right setup in place, it has been reliable for many deployments.
From your log, the long initial connection followed by faster subsequent connections matches what we typically see with satellite devices. The first connection involves several time-consuming steps, including initial satellite acquisition and obtaining a GPS fix, so it usually takes the longest. Once established, follow-on connections are generally quicker.
I’ll follow up with you directly to gather more details about this particular deployment and to request access to your Notehub project so we can take a closer look. In the meantime, if you haven’t done so already, please check our Starnote Best Practices guide as it includes some useful tips to help optimize performance in the field.
Thanks
Youssif