Hy, I just saw I sent the msg on the wrong thread but my reply is the same to you as to Doug (
I think I damaged the RA-gears of the mount (too long to explain the circumstances ). I'll contact the repair people to-morrow.
Thanks for the help and -again- thanks for the beautiful work you've done on the Internal Guider.
Have a nice day.
Doug, I'm afraid I messed the mount mechanically.
Last night I did again a PEC recording and got also fancy curves and period.
I'll get in touch with the repair people.
I would like to share the setup that I installed recently, when I retired.
I live in the French Alps at an altitude of 800m. Light pollution is limited to the West from a middle size city at 30km.
I had the opportunity to buy a used Sirius 2.3m dome. The rotation of the dome is slaved to the scope. The shutters are opened manually.
The dome is equipped with a Celestron EdgeHD 11” optical tube assembly + a Celestron CGE Pro mount.
I run all my astrophotography under macOS which is quite possible nowadays ( www.macobservatory.com ). As software I use the excellent KStars of course, and Siril ( www.siril.org ).
I record only color frames (color camera ZWO ASI1600 cooled).
I can control everything from home through screen sharing.
Advice : if you don’t have time and money, please do not go into this adventure !
Since KStars v. 3.4.0, the INDI Control Panel includes a Periodic Error Correction (PEC) in the Mount / Motion Control panel.
I found the documentation at: indilib.org/devices/mounts/celestron/celestron-nexstar.html
It is recommended to follow this procedure :
The record process is:
Seek PEC Index
Start PEC recording
Wait until it has completed.
Further PEC records can be done, collecting multiple PEC record cycles and averaging them can produce a better PEC record.
Thus I recorded 3 consecutive PEC files to be averaged.
However these files are so much different that their average would be meaningless.
I attach the content of these 3 files
Has someone got some experience in averaging these .csv files ?
My mount is a Celestron CGE Pro.
dmsummers wrote: @jcj: re: "The reason I wanted still to use PHD2 is because the GPG RA Guider asks for the Major Period . How do I get it ?"
Open the PHD2 Log Viewer, select a guide interval, right click in the graph and select "analyze selected raw RA". In next pop-up window, select frequency analysis button (top left). The period will be obvious. Use the mouse to mouse-over at the exact location of the major period, and see the value in the bottom left of the GUI.
Thanks but I'm running macOS.
Hi kross, Paul + Mike,
After changing the port to 4400 and saving, it returns to 0 !
This doesn't prevent the use of PHD2 but the error remains.
When you talk about "nightly build" , you mean that you downloaded the last code and compile it ?
I'm afraid I can't do that.
I find also the new Internal Guider improvements very impressive and so easy to use. Thanks again !!!
The reason I wanted still to use PHD2 is because the GPG RA Guider asks for the Major Period . How do I get it ?
My idea was to use PHD2 : Brain / Algorithms / Predictive PEC : is Period Length (PHD2)= Major Period (EKOS) ?
Finally, I would suggest an improvement about GPG RA Guider.
This is a long dialog which needs to be scrolled . But scrolling with two fingers on a trackpad might change the fields values without notification.
This is really annoying and I suggest to inhibit that field property.
This only occurs since KStars v. 343, not in previous versions
The error msg in the EKOS guider pane
I'm not running the scheduler but I guide before I finish carefully my focusing.
hy wrote: Jean_Claude,
That calibration (and guiding) looks great to me.
PS That other thing on your screenshot (how you lost track of the guidestar right after starting to guide) happens to me too I assume you're running the scheduler, and that what happens is it starts guiding, then interrupts guiding right away to focus. I've looked at the images and during my initial focusing, sometimes particularly at the start, it seems to "move the image" significantly. The result is that you may guide well, but your image is moved a bit from where the alignment put it. Is that your situation too? If so, curious what mount and focuser you have.
Good idea but both values are set to 133.3%
(I would not have dared changing these values !)
As suggested by Hy I set the iteration number to the max 10 and this improved a bit the calibration plot (see attached)
Hy, you've done a beautiful job and the guider interface has substantially improved (it was already simple to use).
The calibration plot and the New Detection Algorithm SEP MultiStar are my favorites.
I have a question concerning the calibration plot