Hi Collin, no, I am not sure. I have tried this on a fresh installation on my Intel NUC. Previously I have tested on a laptop. How can I find out if these two libraries are installed?
Anyway, I have tried to connect the camera and it worked. I have created darks library and also checked if camera reacts in different light conditions.
Hi Collin, I am getting this error:
lukas@astrotracker:~/SVBony$ cmake ../indi-3rdparty/indi-sv305/
-- CFITSIO not found.
CMake Error at /home/lukas/indi-3rdparty/cmake_modules/FindINDI.cmake:285 (message):
Could not find INDI include directory
Call Stack (most recent call first):
-- Configuring incomplete, errors occurred!
See also "/home/lukas/SVBony/CMakeFiles/CMakeOutput.log".
Hi Collin, thank you for all your effort, I appreciate it. How can I now compile it?
Please, read this: indilib.org/forum/mounts/10662-eq6-r-ppec-questions.html#77323
Hi Collin, these are great news, I am loking forward for the update.
I have DeepSkyDad AF3 focuser with NEMA stepper motor. I will try to test both algorithms tomorrow
Thanks Jasem, I will then try to switch the algorithm to Polynomial
I have been imaging last night and observed, that DEC backlash is still a problem for my mount. I have disable DEC guide in South direction (unticked - checkbox). For few expositions it was working good. But once the dithering moved the DEC axis in "wrong" direction, Ekos was not able to return the axis to previous position - probably because disabled south direction corrections. Is it possible to somehow disable guiding corrections in one direction but let dithering still work in both directions?
My setting for "Out step multiple" is 3. But I don't understand why there is 10+ iterations for first right-left cycle? Is it possible to made it more "inteligent" and once there is an obvious curve, the algorithm will do second cycle?
Based on screenshot from Peter, the second cycle could start right after 8th iteration has been done.
Hi Tom, I will try to answer some of your questions:
1) PPEC and guiding is fighting each other. The fact is when you enable PPEC, the corrections are managed by mounts electronic and Ekos/INDI don't know, which corrections is the mount doing. So if you also turn on guiding, and Ekos is sending the corrections to the mount, they fight each other. It is possible to enable PPEC wth guiding, but this PPEC will not be the one which is ctored in the mount. For this purpose ther is a GPG RA algorithm in Ekos, or altenatively VS-PEC in ASCOM (EQmod driver). The reason why your PPEC was turned on and of was that the guiding pulses from Ekos tried to compensate while PPEC was runing.
2) There is no PPEC file stored in Ekos so far. The best way, how to create nice PPEC curve is to record it under ASCOM with PHD2 and EQmod. Then, as you mentioned, you will need to average and smooth the curve in the PECPrep and record it again using PHD2 and EQmod under ASCOM. After this, you will be able to enable it under INDI/Ekos, but don!t try to enable aslo guiding (as I mentioned in previous text).
I hope that I have answered your questions.
In case you are sure about the worm period, yes.
Permanent means that the correction curve is stored in the mount and you can use it without PC connected. For this to work, you need to record this curve into the mount. This can be done manually doing a correction while looking into eyepiece (old fashioned way), or you can let a software, like PHD2, do the corrections while the mount is recording them. Once there is a curve recorded in the mount, you can enable the PPEC (PEC playback in the menu). But there is a one major problem: while a mount is playing a PEC curve back, the guiding pulses will be mostly canceled by the corrections done by mount's internal electronics.
The best way how to use PEC is with GPG RA algorithm, as it was said earlier. The PEC curve will not be stored in the mount or in the Ekos, it will be freshly recorded once the algorithm is used.