×

INDI Library v1.9.1 Released (26 Jun 2021)

Bi-monthly INDI Library v1.9.1 is released bringing a few new drivers and improvements to existing drivers.

Save PEC from GPG to the mount

  • Posts: 117
  • Thank you received: 1
Hi,

I'm loving GPG as it really helps with my mounts periodic error and improves my guiding. What I don't like is having to redo it every session. Would it be possible to have some sort of PPEC that is encoded on the mount that is persistent between sessions?

Rene
Sky-Watcher AZ-EQ6
Sky-Watcher Esprit 100
Sky-Watcher EvoGuide 50 (guide-scope)
ZWO ASI294MC Pro
ZWO ASI120MM mini (guide cam)
Pegasus PPB
Pegasus Focus Cube v2
3 months 1 week ago #70278

Please Log in or Create an account to join the conversation.

  • Posts: 585
  • Thank you received: 279
Rene,

You can save the overall period, details here:
indilib.org/forum/mounts/8645-how-does-p...uiding.html?start=12

Unfortunately, you can't save the GPG model at this point:
indilib.org/forum/mounts/8645-how-does-p...a-guiding.html#66295

I agree it would be great, but apparently it's not a straight-forward task. 

Do you have a background in signal processing? 
Hy
 
Orion Atlas Pro, William Optics ZS105, Moonlight V2 focuser
ZWO ASI1600, OAG & Filterwheel, Astronomik Filters, QHY 5L-IIm guidecam.
KStars/Ekos/Indi on RPi4 w/SSD
Ekos Projects: Terrain Backgrounds, Polar Alignment, Analyze, Linear Focuser, SEP MultiStar & GPG Guiding, FITS autostretch.
3 months 1 week ago #70280

Please Log in or Create an account to join the conversation.

  • Posts: 117
  • Thank you received: 1

Replied by Rene on topic Save PEC from GPG to the mount

I assumed it could be done the way something like PemPro or PecPrep are able to write the corrections back to the mount.

And no I don't have any experience in signal processing. Sorry.

Rene
Sky-Watcher AZ-EQ6
Sky-Watcher Esprit 100
Sky-Watcher EvoGuide 50 (guide-scope)
ZWO ASI294MC Pro
ZWO ASI120MM mini (guide cam)
Pegasus PPB
Pegasus Focus Cube v2
3 months 1 week ago #70282

Please Log in or Create an account to join the conversation.

  • Posts: 585
  • Thank you received: 279
Well, as I mentioned, I asked Edgar and he said it's possible but not straight-forward.
FYI, here's a technical paper explaining what he did:
ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7105398

Best,
Hy
Orion Atlas Pro, William Optics ZS105, Moonlight V2 focuser
ZWO ASI1600, OAG & Filterwheel, Astronomik Filters, QHY 5L-IIm guidecam.
KStars/Ekos/Indi on RPi4 w/SSD
Ekos Projects: Terrain Backgrounds, Polar Alignment, Analyze, Linear Focuser, SEP MultiStar & GPG Guiding, FITS autostretch.
3 months 1 week ago #70283

Please Log in or Create an account to join the conversation.

  • Posts: 30
  • Thank you received: 5
Hello,

I have looked into this for the iOptron mounts, because you cannot load a PECPREP file into chip via the firmware.
ie. you need to do a old school recording on these mounts. So i just let GPG run for 60min, then i record a smooth run.
(re-record if guiding outside 2 arc seconds, also a windless full moon night is preferable)

The issue with this is 2 fold, GPG includes other periodic errors from polar misalignment, from balance issues and from PEC.
So for a permanently mounted observatory mount, this will work quite well, but for tear down mounts this is a major issue.
If you move your mount, then this is not a good solution as each setup, the balance and the polar align will be different.

Another solution you can test, if you are technically inclined, is to take the log from your guiding session and load it into PECPREP.
Then look for the best cycle, smooth it out and load it into your mount. (if your mount supports PEC file loading.)
I have managed to load the logs and generate a smooth cycle myself, but alas, i cannot load it into my mount.
Christopher | Sussex England | n2042.blogspot.com
iOptron GEM45 | Altair Mobile Pier | TSPhoton 154 @ F3.7
ASI 294MM Pro | ASI EFW | ASI EAF | ASI 120MM
Mini PC | Quad 4GB 64GB 5G | Juice USB Harness
3 months 1 week ago #70290

Please Log in or Create an account to join the conversation.

Time to create page: 0.407 seconds