Good to hear your seeking is resolved.

Question though, in AltAz mode does it ever get to the actual requested position -exactly- ?
I found in EQ mode it would always be hunting in ALT, from a post I did earlier in this thread the ALT rate never went to 0 and the reported DEC never matched exactly the requested and would change over time
09:53:05.081: [INFO] ReadScopeStatus - RA 20.812913 hours DEC -9.423441 degrees
09:53:06.168: [INFO] Tracking - Calculated Alt -15.151356 deg ; Az 156.548387 deg
09:53:06.169: [INFO] Target (AltAz): -15.151356 156.548387 Scope (AltAz) -15.100665 156.304250
09:53:06.169: [INFO] TimerHit - Tracking AltRate -3040 AzRate 14647 ; Pos diff (deg): Alt: -0.052828 Az: 0.240476

Where are you getting this info from?
 

I took the existing Driver DEBUG outputs and put on INFO if (TraceThisTick) LOGF_DEBUG("TimerHit - Tracking AltRate %d AzRate %d ; Pos diff (deg): Alt: %f Az: %f", altRate, azRate, AltAz.alt - AAzero.alt, anglediff(AltAz.az, AAzero.az));
  github.com/indilib/indi-3rdparty/blob/ma...aux/celestronaux.cpp

Are you testing the main branch or the recent development branch (github.com/indilib/indi-3rdparty/pull/348)?

If possible, run the development branch - we have re-worked the tracking code. The old one is going to be replaced anyway - so your testing will be more useful with new code (and it seems to work better in my tests).

If I do a GoTo in Alt/Az mode and then look at the co-ordinates on the hand controller they match and do not change.

Hi Jochym, I have been testing the main branch, I will now clone your repo and test with that.

Ken

Sure:
For one time testing you can just get:
<code>
github.com/jochym/indi-3rdparty/archive/...ads/celestronAUX.zip
</code>
and unpack it always points to the head of the branch. Be warned, it is over 100MB and you will need to re-download it for every change you would like to test.
So it is *much* better to check out the branch with git:<code>
git clone github.com/jochym/indi-3rdparty.git
cd indi-3rdparty
git checkout celestronAUX
git pull
</code>
Each time you need to refresh the repo you just go to the directory and execute <code>git pull</code> the initial download is large (536MB at the moment) but each update is tiny. And you can switch to different branches and remote sources without downloading it again. Chose your poison - as they say [/code][/code]

Hi Jochym,
I have had two sessions now with your 0.9 version on my NexStar 6SE Alt/Az with no problems and the tracking seems a little better. I left the scope tracking for over two hours without much deviation.

One thing I have noticed that is a little strange is that on a goto sometimes the scope sets off in one direction and then after about 90 degrees in Azimuth reverses direction going back past the origin to the target. It is not a big deal just a little disconcerting when the scope sets off in the wrong direction initially.

This doesn’t appear to be related to the cable wrap position.

BTW cable wrap works well.

Ken

Hi I have a CGEM DX. I’m following the Equatorial sync instructions. I’m puzzled by the instruction to rotate by +6 hours HA. If you start at -3 hours HA, this will be a meridian flip correct? But it doesn’t say to change DE. How do I do this?

Hi Thomas,
when I wrote the equatorial alignment instructions, I was focused on my mount that is of fork type, so no meridian flip is required. For german equatorial mount any motion crossing the meridian obviously needs the meridian flip. This is your case. But even if you perform the meridian flip, you need to point at the same DE = 0. The 180 degrees of rotation of DE axis combined with the 180 degree of rotation of the polar axis done by meridian flip, keeps DE unchanged. DE intended as celestial coordinate. In any case, I will add a note for GEMs in the alignment instructions.

Fabrizio

Hi Fabrizio, 

OK, understand, and thank you for the clarifications. I tried that and it seems to basically work (that is after the two syncs, I did a goto to Arcturus and it was fairly close). When tracking see a fairly large amount of drift (approximately 1 min of arc in 1 minute of time). Does the tracking come from the mount or from EKOS?  I also saw a few times where I did a move with a joystick or the SW mount control, and then the mount kept moving after the move command from me stopped.  Is version 0.8 the correct one to be using or should I download the latest? 

Thanks again, 

Tom 

Hi Thomas,

do not mix motion commands from the telescope mount SW with motion control by celestron aux driver. The driver is not aware of commands coming from any other sources than an indi client like Kstars, do anything wrong can happen. To move the telescope, use the virtual hand control of Ekos instead. It integrates with the celestron aux driver.
As you can seen few posts above, Jockym, the main driver developer, has reworked the tracking part of the driver and suggests to use his last version 0.9. Download instructions also above.

Fabrizio