First, let me say that this forum is a wealth of knowledge on most subjects Uniden-related. I purchased my BCD536HP about a month ago, and since then have been around and around with the typical issues of SD card "file errors" and software install problems - most of it user error and all have been resolved by reading these forums. The scanner is working great now, except that I'm unable to update the database.
Here in the more remote parts of Alaska, we don't have MB or GB internet. We are using Hughes Net over satellite, which is plenty fast enough for everything we do. But we have latency to deal with. Whenever I open Sentinel and try to "Update Master HPDB" it opens the typical box "checking Uniden server". I can see the network traffic, but the connection times out in 9-10 seconds and says "The Operation Timed Out" and closes without updating. The same thing happens if you try to update firmware.
To test my theory that the timeout was too short, I drove 80 miles to the nearest 4GLTE tower to test the update on a faster system and it worked just fine. I'll spare you the details on how difficult "driving" 80 miles was just for a software test.
I can ping the update server but latency is about 800 ms typical. Evidently the timeout in the software is too short to allow a satellite connection to come back. Is there a way to lengthen the timeout? Driving 80 miles for an update is not an option. No other software has any issue with updates or timeouts, as normally they seem to have 60 second timeouts. Is there another way to manually update the database without Sentinel?
Thanks in advance,
Joe in AK
Here in the more remote parts of Alaska, we don't have MB or GB internet. We are using Hughes Net over satellite, which is plenty fast enough for everything we do. But we have latency to deal with. Whenever I open Sentinel and try to "Update Master HPDB" it opens the typical box "checking Uniden server". I can see the network traffic, but the connection times out in 9-10 seconds and says "The Operation Timed Out" and closes without updating. The same thing happens if you try to update firmware.
To test my theory that the timeout was too short, I drove 80 miles to the nearest 4GLTE tower to test the update on a faster system and it worked just fine. I'll spare you the details on how difficult "driving" 80 miles was just for a software test.
I can ping the update server but latency is about 800 ms typical. Evidently the timeout in the software is too short to allow a satellite connection to come back. Is there a way to lengthen the timeout? Driving 80 miles for an update is not an option. No other software has any issue with updates or timeouts, as normally they seem to have 60 second timeouts. Is there another way to manually update the database without Sentinel?
Thanks in advance,
Joe in AK