It is a bug. I have attempted to raise the issue before but it did not get resolved at the time because the forum posts got merged and mixed up.
I noted it will synchronize to GPS time once, but each refresh will set the clock back to that first sync rather than update it.
You can set refresh to 0. Thus never updating the time after the first sync. Or, My workaround is to set up the system clock to sync to GPS time and use System as the time source in the INDI GPSD driver.
Enter the set focal length in the EKOS Mount tab, you can also create a few presets. Once you click Save Telescope Info it should update the calculated focal length in the Align Tab.
It's worse than you think. The smallest significant figure I provided was Minutes, not Seconds.
Cartes Du Ciel 1:38:ss
Also I live at Longitude 75°W, just a few kilometers from the Eastern Time Zone Meridian. So Time Zone offset is not a factor at play here.
AradoSKYindi wrote: Hello,
No mention was given of syncronized clocks in these findings.
I had each application open at once with common location and time settings. Then quickly noted their figures to within the minute.
I have seen this before. Often different polar finder apps calculate a different PHA. Without understanding what they are doing under the hood I can only guess as to why. But I've always suspected some do not factor in the Time Zone Meridian offset correctly.
Turn on the horizon layer
Try switching from FITS to Native
The resolution should be entered into the Width and Height fields of the Image Info tab. The Frame portion of Image Settings I believe is for subframing.
To save to the SD card, choose SD Card as the Target.
You might also want test the cameras with the GPhoto driver.
I am attempting to set up a way to monitor a second setup to display that mount's pointing location in one instance of KStars running on my main setup.
I am able to run all my main drivers and then connect the secondary remote drivers by way of the Device Manager - Client.
This imports all drivers running remotely. For clarity, all remote drivers have custom labels.
'driver1@remotehost:port' In the profile editor also works, but it has another conflict regarding which mount KStars commands among other hindrances
Either way I can get the mount to show up.
The issue is, INDI is setup to automatically populate the Snoop Device with the details of a locally running GPS INDI Driver; issue is I have GPS in both setups. The result is the main setup attempts to override the remote GPS INDI driver snoop device, then the remote setup automatically overwrites it again. This causes an endless loop
... 2020-06-26T13:38:45: [INFO] Observer location updated: Longitude (-**.7954) Latitude (**.3629) 2020-06-26T13:38:44: [INFO] Observer location updated: Longitude (-**.7954) Latitude (**.3629) 2020-06-26T13:38:44: [INFO] Observer location updated: Longitude (-**.7954) Latitude (**.3629) 2020-06-26T13:38:44: [INFO] Observer location updated: Longitude (-**.7954) Latitude (**.3629) ...
It is possible to avoid the loop by using the default GPSD label rather than a custom one. But that has a lot ambiguity involved.
El Corazon wrote: The problem with the original design of the adapter is that it is held in by the rubber O-rings, not by a secure clamp. That probably makes it shift as the mount rotates. If a clamp solution can be incorporated into the design that prevents shifting as the mount turns, it will work fine.
Indeed. I did modify my design quite a bit after those earlier posts.
What do you require exactly?
Set the resolution in the /boot/config.txt file.
You should bear in mind that there are two view modes, Equatorial Coordinates and Horizontal Coordinates and they behave differently in the same sense that an EQ mount rotates with the sky, while an Alt-Az maintains level to the horizon. The space key will switch between them. The Lock To Celestial Pole option in the FOV settings will display the orientation with regards to Equatorial mounts while in the Horizontal Coordinates view mode. With this in mind, you do not have to work out the orientation for different parts of the sky as the mechanics of the mount get taken into account for you. You only have to enter a rotation value relative to the OTA.