Thanks Fabrizio! So this is supported in StellarMate, but the Guiding is a problem, but you're working on this, as I hopefully understood right
Please let me know if I'm wrong.
Thanks a lot for your help!
Best regards
Frederik
I did some test today with your latests celestronaux_eqtrack branch and:
1. Cord wrap even if it is "green" and OFF, I have to turn it ON and OFF to take effect.
2. If my first sync point is on ALT = 0 (any AZ) then alignment seams to work fine.
3. If my first sync point is on higher ALT then alignment is a mess. Adding second sync helping much, but I can not tell more about it's accuracy because of those clouds from over two months now :-/
If I can do any more tests without a sky please let me know.
It appears more users are reporting incorrect position on startup. Just wondering, is this perhaps because the driver relies on INDI::Alignment subsystem, while the mount is already aligned and is sending the *raw* encoder values to the driver while the transformed coordinates are sent off to Celestron/SkySafari software? Not sure if this make sense, this is one of the few mount drivers which I'm not familiar with how it works.
Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.
Hey Fabrizio, I've been digging into the alignment subsystem a lot lately, and I've found that I think you DO need to interact with it in either equatorial coords with an EQ mount OR alt/az coords for an alt/az mount.
I'm not sure if it has made it into a release yet, but I added some helper methods to the alignment subsystem to make it easier to deal with. You can see them in use in the tests created here: github.com/indilib/indi/tree/master/test/alignment
Basically having an issue where KStars won't sync up with the mounts known sky position.
Some logs attached after a 1 star align with Acturus (~ 327:26 / +30:01 right now during the day).. so it thinks its pointing there. But after connecting KStars it's showing due south on the horizon as the scopes position in the sky.
Very strange, any help would be appreciated!
Edit: Mount is a Celestron Astro Fi 5, iOS app i'm using for alignment is Sky Safari Pro
Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.
Thanks Fabrizio! Sounds like i've just been missing a step.
When you say HC here "using the Motion Control HC of Kstars".. could you just clarify what you mean by that? I may just be a bit daft but unsure where exactly I should be looking!
You have to (1) launch Kstars, (2) open Ekos, (3) start INDI, (4) connect to your scope. Now it should appear the mount tab in Ekos. (5) Open it and click on the (6) "Mount Control" button. At this point, the window of the "Mount Control" appears, a sort virtual hand control. To make the requested SYNC operations, put the RA/DE coordinates given by the other system into the RA/DE text boxes of Mount Control and click there on the "SYNC" button.
I ignored any external alignment (it's now daytime) and just tried to sync two approximate sky points within KStars as described. This started with the scope pointing approximately toward menkar, aligning that, then slewing it (using kstars) to the west approximately where Enif would be and doing a second sync.
The telescope pointer within kstars started due north on the horizon, then swung west when i slewed the scope west. However it has not taken into account either sync point.
I've attached the log for the quick test run. Also added a picture of the (i think) relevant sections cut out if thats easier. And finally have added the alignment section of the indi control panel, showing 3 sync points registered.. and the alignment subsystem active.. but not much else?
Edit: Just in case 2 points wasn't enough.. added another vague sync point at Apheratz.
Thanks for the pointers so far... hopefully I can get things sorted eventually!
Cheers,
Jack
The following user(s) said Thank You: Jasem Mutlaq