Got it. Thank you. It looks like it will be very useful but will take some practice to learn how it works.
I found the bug report list but it requires an account to post.
Thanks for the response. Since my station has limited automation it is not a high priority here. But I can't even enter objects into the scheduler manually. It appears to require a sequence name but does not permit me to enter it. What am I missing?
I noticed a couple ideosyncrasies in the sorting of objects in the session plan. The dec sorting goes from the ecliptic to the north then from the ecliptic south. And the magnitude sorting appears to be an alphanumeric sort rather than a numerical sort. So mag 2 - 9 comes after mag 10 - 19. Is there a location on this site for bug reports?
I assume this bridge from the Observation Planner Session Plan to the Ekos Scheduler has not been implemented yet. I look forward to this implementation.
I have saved the Session Plan and have verified that the file does appear in the File Manager list. But when I try to open the plan file, it does not appear in the selection list. Is there something missing in the implementation?
Is there documentation on how to use the Ekos Scheduler? I have not figured out to enter objects into the list.
I have found the 'What's up Tonight" tool and the "Observation Planner" to be very helpful for selecting objects. It is very helpful to see the most relevant information about the objects of interest in one table and to be able to sort the objects by the data columns. One other piece of information that would be helpful for selecting objects in the list is the apparent size of the object.
A general question about Kstars/Ekos: Is there a reason why the windows are not independent - minimizing a sub window also minimizes the Kstars screen. Ekos and the Indi Control Panel can be configured to be independent but that option apparently is not available for other windows. The most common default behavior of programs is for the sub windows to be independent of the main window.
Thank you for an excellent product. After using it for over a year, I am still learning new things.
My primary mount is a Celestron AVX. I don't think it reports HA or the pier side.
I have been doing the testing during the daytime without a doing an accurate alignment to real objects. Some of the differences between the mount and Kstars/Ekos should be reduced after doing a real alignment with stars.
I have been doing some experimenting with the meridian flip for the past few days. I have found that the meridian line on the Kstars map does not match the HA displayed in the Ekos telescope window. It can be a few minutes off. Also the telescope meridian flip point can be several degrees from the actual telescope meridian point and several degrees from the Kstars/Ekos meridian. To enable an automatic meridian flip, an object must be selected that is East of meridian for both the telescope mount and Ekos. And the flip is executed successfully only if the mount is West of the mount meridian point when the meridian flip goto command is sent to the mount.
Things to do to investigate the issue:
1) In Kstars select an object just East of the meridian line and note the HA time when that object actually crosses the line. HA = 0 is the reference time for the triggering of the goto command that causes the meridian flip. The goto command is sent to the mount when the HA>xx limit is reached.
2) Manually move the telescope with the hand controller or the Kstars telescope movement controls to the point where the counterweight bar is perfectly horizontal. The difference between the telescope location and the meridian line on the Kstars map can be determined by noting the RA position of the cursor on the map in the lower right corner of the map. This may not be the telescope meridian flip point.
3) To determine the telescope mount meridian flip point. select an object sufficiently far to the East that causes the mount to slew to that object with the telescope on the West side of the mount. Periodically press the Kstars goto button until the mount actually does the flip. Watch the HA position in the Ekos telescope window and note the HA position when the flip occurs.
I have both a GPS receiver and a real time clock on my Stellarmate/Astroberry. I don't know if that would solve your problem because I don't know how it is used. I would like to hear an explanation from the developers how the realtime clock and the GPS are handled. Specifically:
- Is the real time clock updated if there is time available from the GPS or the network?
- If all 3 time sources (RTC, GPS, Network) are available, which does Kstars use?
- Does Kstars do any evaluation of the quality of the time (latency) from the GPS?
- Is the RTC updated when time is set manually in Kstar or in the operating system?
- Does the system time get updated if the GPS reports time?
- Where does the system get the time if there is no network time server available?
I have also been experiencing problems with the gpsd driver. On Stellarmate and Astroberry, Indi often has difficulty connecting reading from the GPS. Running cgps in a terminal window shows the GPS reporting data continuously but Indi shows no data. When it does show position and time fix from the GPS, cgps shows the time updating continuously, but when the GPS refresh button is pressed, the Indi control panel time is unchanged but the Kstars time is reset to the time in the Indi control panel. I think the Indi control panel time may be updated but very rarely. Once the GPS connection stops updating, the Indi server must be stopped and restarted to reestablish the connection. For that reason, the refresh interval must always be set to 0. Does this sound similar or related to your issue?
What is chronyc and what is the Astroberry virtual GPS service?
I found that the hotspot was not set to start automatically. I will leave it that way.
Apparently the real time clock did not have a battery. I replaced it with one that does have a battery.
The Canon T7i appears to have some control of the sensitivity for the live view operation. Adjusting the shutter speed - not using the bulb mode - changes the sensitivity without changing the frame rate.
I installed a real time clock last week and it worked perfectly. However, late in the photo session I noticed the OS date and time were way off - December 31, 1999. I was unable to set the OS date and time using the OS tool. What is the procedure for manually setting the date and time on the RTC? Is that normally updated when the RPi is connected to a time server on the internet? There is a GPS connected to the RPi which usually sets the kstars time but not the OS time.
Success! Spent an all-night session in the mountains of southern CA under a Bortle 4 sky. Temperature was forecast to be in the 40's F according to Clear Outside but in the morning there was frost on the keyboard and 27F temp. This was the first time I was able to use Stellarmate for finding objects with kstars and scheduling the photographing session with Ekos. Also used the live view for manually adjusting the focus. I was able to monitor the progress and take a nap inside in front of an electric heater during the photographing sessions. Those were the primary reasons for using the Stellarmate.
The RPi 4 often does not boot up when the USB mouse is plugged in. There is no problem with the dongle for the wireless keyboard.
Still having difficulty connecting to the Canon T7i DSLR. All the OS updates were installed last week but not SM 1.4.5. I will try reinstalling the custom gphoto2 which resolved the issue before the OS updates.
When using the live view for focusing and framing objects the frame rate is around 15 fps which results in low sensitivity that is adequate only for very bright stars. There does not appear to be a way to set the frame rate in Ekos for the Canon DSLR. I think I have found a way to control the frame rate on the camera which I will try that the next time we have clear skies.
There was no WiFi available but the hotspot did not start automatically. It had to be manually started. It is possible there was a WiFi visible from a neighbor.
The image download time was around 3 seconds and storing the images on a USB 3.0 thumb drive worked perfectly. The actual total delay between exposures was about 10 seconds.
Thank you again to the SM team for a great product and excellent support.
That appears to have solved the problem. Thank you very much for your help, Wouter.
After I executed this command:
sudo apt-get install software-properties-common
Then the add-apt-repository command was successful.
But when I executed:
sudo apt-get install -y indi-libgphoto2
E: Unable to locate package indi-libgphoto2