Thanks for the thought, rdw. I'll keep that in mind, but I think the issue is actually what gmiller said. Poor view of the sky. That said, Yikes! this is one deaf GPS module. I am NOT impressed.
I got a short USB extension cable, and positioned the GPS module on top of the scope, and rolled the scope out to a place where it has a better view of the sky (it was partly under a fluffy tree). After a while, it did get a fix on the sky. Then lost it. Then found it again. And so it went. Sort of settled down for a while, then lost it again. Sheesh...
So, I think there's nothing about Astroberry that prevents it from working.
But, we're not done yet... Drifting the thread slightly, next issue...
During the time the GPS has a fix, running cgps in a terminal window shows the correct lat / lon for my location, just as it did on the other system. However, indi-gpsd displays the correct latitude, but incorrect longitude. It's 360 degrees off (shows 238 instead of the expected -121). Configuring the mount's indi driver (indi-celestron-gps) to use the GPSD location, I see that the odd location is fed across to it. So, apparently the display is not exactly cosmetic.
Fortunately (I think), the mount still believes it's standing in front of me, i.e. the "updated" location hasn't made it to the hand controller. So, two questions:
1. Before I log a bug against indi-gpsd, has anyone else seen this? Is it, in fact, cosmetic (i.e. a valid way to display latitude as a positive number instead of +/- for E/W), or will it mess up my GoTo slews?
2. What is the GPS time / location used for in indi_celestron_gps? When a slew is commanded, it's the mount hand controller's perception of time and location that is used, and that doesn't seem to be updating, so why does the Celestron indi driver even care about the GPS?
Edited by TelescopeGreg, 08 June 2021 - 03:23 PM.