I think that GPG could be saved for next session. But you need to have a mount with encoders or at least with an index on the RA axis, e.g.: SW EQ6-R. Because the algorithm needs to know at which RA possition is the mount. This is how it works for PPEC.
I have just "hacked" it to use my master dark created in PixInsight. Here is how i have done it (some steps are the same as you just mentioned):
1) Go to guiding tab of Ekos and enable Dark checkbox
2) Click on Capture button. This will create one dark
3) Go co Capture tab, select your guiding camera. Create sequence for 20 (or more if you want) darks with the same exposure time used in first step. Dont forget to select Type: Dark. Execute the sequence
4) Stack these 20 captured darks in your favourite software. Resulting image must have the same bit depth as single sub (in my case it is 8bit)
5) Possibly optional step: change content of FITS header for stacked master darkto be exactly the same as has the one dark from step 2
6) Go to /.local/share/kstars/darks/ folder and rename the original dark from step 2. For example from "darkframe_2021-01-21T20-28-28.fits" to "darkframe_2021-01-21T20-28-28.fits.old"
7) To the folder above copy stacked master dark and change its name to be the same as the dark from step 2 (in my case "darkframe_2021-01-21T20-28-28.fits")
Go to KStars/Settings/Configure KStars/Ekos/Dark Library. Now if you double click on the record for dark from step 2 it will open the stacked master dark.
Most of guiding cameras are uncooled, so take the darks in step 3 in similar conditions as you will have during real-time guiding.
This is still a theory, I currently don't have conditions to test it outside, but I will report once done so
Ok, so what I can see in the code, and if I understand it correctly, I need to match these parameters:
1) name of the CCD is the same
2) binning mode is the same
3) temperature is within a configured range
4) duration is within a configured range
I expect that these parameters are stored in FITS, and then it can be easily changed to match needed values
And what if I capture one using the current method, then create manually master dark and finally replace the one from dark library with created master dark. Will it work then? Which parameters needs to match? Name is sufficient?
The tab could be used for two things:
1) Start programming PPEC into the mount
2) Enable PPEC once it is recorder in the mount
Once you click on one of these two options in that tab, it will simply turn ON (or OFF) a flag in the mount's electronic. Nothing more, nothing less.
Hi, I have also the issue with darks, but dithering is working correctly, so I think these two issues are not connected.
Hi Rene, I have spend some time with research about PPEC. The fact is, that it is not usable in Ekos if you also want to use guiding. Those two functions ara fighting against each other. But if I summarize it, how to use PPEC:
1) You will need to record correction curve. For this, you will need to switch from INDI to ASCOM, because INDI driver for EQDir is simple, and it doesn't have this capability.
2) Once your curve is recorded, you can smooth it in PECPrep. This step is optional, but I would recommend to do it.
3) You will need to replay the (smoothed) curve from EQDir under ASCOM. At the same time, you will need to learn the mount the curve. This can be done in Ekos, with one of those two buttons in PPEC tab.
4) Finally, you can enable PPEC during your imaging session. RA periodic error will be automatically corrected by the mount itself, as the correction curve is now recorded in its EEPROM.
As I said, it is way too complicated, and GPG for this purpose is definitely better solution, as it is able to cooperate with guiding.
So here is my testing done yesterday:
I even don't know that there is such upgrade, this is cool
What happens if you connect this mount to a Windows PC? Is there a new COM device in Device manager detected?
Have you tried to set the hand controller into DirectPC mode?
This thread on CN can help you: www.cloudynights.com/topic/644409-eq6-r-pro-pc-connection/