Re: Settings for use of AutoGUIDE

#7428
Edited

Update:

?

I have come to the conclusion that 7 arc seconds per second in ServoCAT sky is not fast enough to calibrate or guide well between 160 Az? and 200 az (so +/- 20 degrees of south), same to the north 330 - 30 az. So in other words, stay away from the Meridian and 20 degrees on either side of it.

?

At 75 z and 37 Alt i get a perfect calibration in PHD2 with 7 arc seconds / second set in ServoCAT Sky.

?

Due to field rotation one would want to stay away from the meridian anyway, also considering objects are the highest above the horizon when passing the meridian.

?

This is not really an issue if one plans the session: To give an example:

?

If i was to image M106 tonight, and i would begin imaging at around 8 PM when it is at 67 az and 42 alt, i will still get 5 hours of imaging time before it reaches 160 az and 75 alt.

?

I don't think it's worth changing the guidespeed for imaging around the meridian since, the span is a short, as mentioned field rotation and at least from my experience a fast guidespeed does not work well, at least with my Starstructure.

?

/Gabriel?

Re: My first ServoCAT Autoguide "production" images

#7427

Thank you Raphael!

Re: My first ServoCAT Autoguide "production" images

#7426

Congratulations Gabriel !

Really great?

My first ServoCAT Autoguide "production" images

#7425

As the weatherman promised our skies cleared up Wednesday and yesterday Thursday so i was finally able to test Autoguiding on actual capture.

It works well and i can confirm that dither also works very well with ServoCAT. It almost always settled from a dither without messsing up the next sub which was often not the case with my Sky-Watcher mount even though i used "Spiral" instead of "Random" for dither there as well (to avoid backlash).

?

I dither 1 pixel on my guidecamera which is 4.30 arc seconds = about 14 pixels on my DSLR, it problably would not hurt to dither more than every 10 frames as i did.

?

241 x 15s (1h 15s) on The Sunflower Galaxy. Large view on Astrobin recommended:

?

449 x 20s (2.5h) on NGC 3180 (looks like a flower too in my opinion). Large view recommended:

?

Astrobin link to a PHD2 screenshot: (the total RMS there is 0.94" arc seconds, for the most part during capture it was around 1.2 -1.3" arc seconds).

?

PHD2 calibration (no warnings):

?

At the moment i use a guidespeed of 7 arc seconds per second in ServoCAT Sky and 0.20 x Sidereal in PHD2.

?

/Gabriel

?

Re: Settings for use of AutoGUIDE

#7424
Edited

Your welcome Raphael, thank you. Happy to help!

?

I don't see any advantage of imaging with autoguiding in combination with easytrack except if your DSC is not working, so a good backup solution!

PHD2 will not have to work/correct as much when you have done the 2-star alignment because of more accurate tracking, but it could potentially still correct to the same RMS error.

?

PHD2 is very good, and made for correcting low frequency errors like slow drift. Which is the case when using easytrack compared to a good 2-star alignment.

?

Edit: It is not possible to point at all with Easytrack, you would have to use a Telrad or similar, just like when doing visual.

?

/Gabriel

?

Re: Settings for use of AutoGUIDE

#7423

Thanks Gabriel

Even if don’t understand everything detail you explain, all this will be of great use for community including me when I have a higher level in astrophotography

One question :?

With the very good result you have with auto guiding + easy track, do you see any advantage to make auto guiding with 2 alignment star versus auto guiding+ easy track ?

Pointing is more accurate with 2 stars alignment, but appart from this, any advantage of 1 method versus the other ?

thanks

Rapha?l?

?

Re: Settings for use of AutoGUIDE

#7422
Edited

I made some new discoveries this morning when creating a new profile to improve my understanding of PHD2.

?

1. It is not possible, when creating a new profile to enter a mount speed less then 0.20 x Sidereal. It's only possible when changing the settings later. (that would be 3.01 arc seconds per second in the Meade Generic driver (if used) before creating a new profile in PHD2 change that in the driver)

?

2. The calibration step size is not only calculated from guidespeed, focal length, and pixel size but also which declination the calibration will be performed, this can be set under Advanced settings.

?

This explains why the calibration step size suddenly changed for me, i was calibrating at a different declination and PHD2 used the pointing information from the Meade driver to use "dec compensation".

?

Since the PHD2 documentation advises against changing guidespeed after creating a new profile, it's probably best to go with 0.20 x Sidereal from the start and leave it.

?

The last calibration that i did, which was Orthogonal, completed in both axis within 8-12 steps and produced good guiding results was done at about 60 AZ and 38 ALT and declination of 46.

?

I had changed guidespeed to 0.18 x Sidereal in PHD2 and as usual 6 arc seconds per second in Servocat Sky, Calibration step size was 4900 ms.

With the new profile i set all the values the same, including declination 46 for the calibration, produced a step size of 4300 ms, since guidespeed had been raised from 0.18 to 0.20 Sidereal.

?

Since the step size is reduced, in order to not slow down the measured guidespeed with 0.20 x Sidereal set in PHD2 it's probably a good idea to use 7 arc seconds per second in ServoCAT sky instead of 6 arc seconds per second, i have changed this in ServoCAT sky.

?

Will be interesting to see next clear night when i will be using the DSC Pro and hopefully do actual capture.

?

Here is an extreme crop (to see the stars better) of 180 stacked subs, 20 seconds each processed in Siril on a random part of the sky near Ursa Major, it is from the night when i got around 0.95" RMS guiding with EasyTrack.

?

The stack had a FWHM of 3.4 arc seconds, which is what i get when looping 1 second exposures on a night when seeing is above average from this location.

?

Edit (correction): The measured guidespeed will not slow down because of increasing the guidespeed from 0.18 to 0.20 in PHD2, but it will send shorter pulse commands and that will increase the number of steps used during calibration, and to compensate for that it would not hurt to increase the guidespeed in ServoCAT Sky if the number of steps are more than 12.

?

/Gabriel

Re: Local SYNC activated or not ?

#7421

开云体育

Thanks Gary

"Try this as well: hold the CW and CCW buttons for I think it is 3 seconds - the yellow LED next to the CCW should come on. You can do this same test using the UP/DWN buttons (where the DWN comes on)"

I do this from time to time to reverse the guiding direction as my dob is a little special : it has 37° secondary angle + a 120° diagonal => from time to time I try to reverse the up/down or right/left guiding direction?

And yes, the yellow light near the CCW is then on (or the one near the down if I reverse up/down)

But I didn’t do this for 2-3 months => maybe something happened since 2-3 month

Anyway, I will redo all the test and make videos in 3 weeks:?

LEDs during startup?
up+down or CW+CCW for 3 seconds
press the local synch button

Thanks Gary for giving each time your kind support !

Regards

De :[email protected] <[email protected]> de la part de K9RX - Gary via groups.io <amateurK9RX@...>
Envoyé :?samedi 22 février 2025 16:50
? :[email protected] <[email protected]>
Objet :?Re: [ServoCAT] Local SYNC activated or not ?

?

try to be sure to hold the HC perpendicular to the camera - and in focus.?

That stated I suspect you are right. It however doesn't make sense that it powers up correctly (showing the lights as a check on their operation) and doesn't in use. Unless the other lights aren't working. Try this as well: hold the CW and CCW buttons for I think it is 3 seconds - the yellow LED next to the CCW should come on. You can do this same test using the UP/DWN buttons (where the DWN comes on).

g.

Show quoted text

------ Original Message ------

From "Raphael Guinamard via groups.io" <rguinamard@...>

To [email protected]

Date 2/22/2025 10:15:44 AM

Subject Re: [ServoCAT] Local SYNC activated or not ?

Thanks Gary for quick answer !

Enclosed another video made the same day.

I'm not aware of any color shift affected my eye. I clearly see the yellow LS light on when turning on the servocat handpad with the same condition as video : in the dark, with my red headlamp on

It's difficult to make the video in the dark with 1 hand on handpad and 1 hand on cellphone. ;-)?

The thing is even when led are off, with my red headlamp on you could think that the yellow LED is on. Dim but on. For example see in the begininng or end of the below video : we could imagin that this led is on, but it is not.

Anyway I will carefully recheck next time I go to observatory (in 3 weeks) and will ask someone to hold the camera to have better quality vidéo.

I will also check if local synch is activated or not when pressing LC button, because at the end of the day, the important thing is the good activation of LC.... Even if my handpad yellow led is not activated, if the local synch is on (and on servocat, the yellow LC LED IS on), it's ok. Just a little bit less friendly to use, but OK.

I will repost in 3 weeks with more accurate video

Regards

Re: Settings for use of AutoGUIDE

#7420
Edited

Hello Gary,

?

That is correct.

?

However, when guiding at the bottom to the right you can set MAX pulse duration in AZ and ALT, default is 2500 ms which i have not found a reason to change.

?

Even if you would change the calibration step size on brain -> guiding ->calibration step (ms): next to Advanced it will automatically change back to the value calculated by the values entered when creating the profile and also depending on guidspeed entered which is found when clicking on Advanced.

?

You have to keep an eye on what the number is on calibration step (ms): since it could suddenly change for example if there is a different guidespeed in the Meade Generic driver if connected so the guidespeed there could overwrite the guidespeed in PHD2.

?

It once changed to 2300ms for me and i am not sure why. PHD2 recommends that you should create a new profile if a parameter has changed and not do manual changes, pherhaps that is the reason.

?

However i have found that, as long as you keep an eye on that number and it works i have not found a reason to create a profile from scratch.

?

Best regards

Gabriel

Re: Local SYNC activated or not ?

#7419

try to be sure to hold the HC perpendicular to the camera - and in focus.?

That stated I suspect you are right. It however doesn't make sense that it powers up correctly (showing the lights as a check on their operation) and doesn't in use. Unless the other lights aren't working. Try this as well: hold the CW and CCW buttons for I think it is 3 seconds - the yellow LED next to the CCW should come on. You can do this same test using the UP/DWN buttons (where the DWN comes on).

g.

Show quoted text

------ Original Message ------

From "Raphael Guinamard via groups.io" <rguinamard@...>

To [email protected]

Date 2/22/2025 10:15:44 AM

Subject Re: [ServoCAT] Local SYNC activated or not ?

Thanks Gary for quick answer !

Enclosed another video made the same day.

I'm not aware of any color shift affected my eye. I clearly see the yellow LS light on when turning on the servocat handpad with the same condition as video : in the dark, with my red headlamp on

It's difficult to make the video in the dark with 1 hand on handpad and 1 hand on cellphone. ;-)?

The thing is even when led are off, with my red headlamp on you could think that the yellow LED is on. Dim but on. For example see in the begininng or end of the below video : we could imagin that this led is on, but it is not.

Anyway I will carefully recheck next time I go to observatory (in 3 weeks) and will ask someone to hold the camera to have better quality vidéo.

I will also check if local synch is activated or not when pressing LC button, because at the end of the day, the important thing is the good activation of LC.... Even if my handpad yellow led is not activated, if the local synch is on (and on servocat, the yellow LC LED IS on), it's ok. Just a little bit less friendly to use, but OK.

I will repost in 3 weeks with more accurate video

Regards

Re: Local SYNC activated or not ?

#7418

oups forgot to put the video

here it is

IMG_E3054.mp4

Re: Local SYNC activated or not ?

#7417

Thanks Gary for quick answer !

Enclosed another video made the same day.

I'm not aware of any color shift affected my eye. I clearly see the yellow LS light on when turning on the servocat handpad with the same condition as video : in the dark, with my red headlamp on

It's difficult to make the video in the dark with 1 hand on handpad and 1 hand on cellphone. ;-)?

The thing is even when led are off, with my red headlamp on you could think that the yellow LED is on. Dim but on. For example see in the begininng or end of the below video : we could imagin that this led is on, but it is not.

Anyway I will carefully recheck next time I go to observatory (in 3 weeks) and will ask someone to hold the camera to have better quality vidéo.

I will also check if local synch is activated or not when pressing LC button, because at the end of the day, the important thing is the good activation of LC.... Even if my handpad yellow led is not activated, if the local synch is on (and on servocat, the yellow LC LED IS on), it's ok. Just a little bit less friendly to use, but OK.

I will repost in 3 weeks with more accurate video

Regards

Re: Local SYNC activated or not ?

#7416

Although the video is not in focus it seems like I do see the LS light on the HC come on when you press the LS button! I can see at the instant you are pressing it a slight change in the LS light and you show the HC after that - it appears to be on. It is just very dim. Is it possible you are light challenged in the yellow spectrum? (slightly color blind or color shifted - ps it is more common in men than in women).?

It seems like the yellow is on at the very end of the video - literally the last second - as well.?

It might also be I'm seeing things...? ?:?- )?

g.

Show quoted text

------ Original Message ------

From "Raphael Guinamard via groups.io" <rguinamard@...>

To [email protected]

Date 2/22/2025 9:16:26 AM

Subject Re: [ServoCAT] Local SYNC activated or not ?

Dear Gary, dear all,

I red in the servocat guide that when powering the handpad, the leds are on for a short period of time (like in a car)

Yesterday I was at observatory so I checked and I saw that the yellow local synch led on handpad was on during this short period of time.

So it is not damaged !

You will see in the video in my message 7337, /g/ServoCAT/message/7337 that when I Press the local synch bouton, the yellow led local synch on main unit turn on (and the red Aux also), but the yellow led on the hand pad don't turn on while I know now from yesterday test that this yellow handpad led is NOT damaned...

?

Note that since it is currently bad weather in France I couldn't check if local synch is really activated or not.?

?

Any idea what could explain the behavior in my video in message 7337 ?

Regards

Rapha?l

Re: Local SYNC activated or not ?

#7415

Dear Gary, dear all,

I red in the servocat guide that when powering the handpad, the leds are on for a short period of time (like in a car)

Yesterday I was at observatory so I checked and I saw that the yellow local synch led on handpad was on during this short period of time.

So it is not damaged !

You will see in the video in my message 7337, /g/ServoCAT/message/7337 that when I Press the local synch bouton, the yellow led local synch on main unit turn on (and the red Aux also), but the yellow led on the hand pad don't turn on while I know now from yesterday test that this yellow handpad led is NOT damaned...

?

Note that since it is currently bad weather in France I couldn't check if local synch is really activated or not.?

?

Any idea what could explain the behavior in my video in message 7337 ?

Regards

Rapha?l

Re: Settings for use of AutoGUIDE

#7414

Gabriel,?

So - you are not setting "5000" anywhere?

It is a result of or what is used by the program when doing autocalibrate??

I ask because I don't remember anywhere to set the pulse duration.?

Gary

Show quoted text

------ Original Message ------

From "Gabriel Wiklund via groups.io" <gabriel.wiklundholeshot@...>

To [email protected]

Date 2/22/2025 7:02:36 AM

Subject Re: [ServoCAT] Settings for use of AutoGUIDE

[Edited Message Follows]

Yes i was surprised too,

?

Thank you!

?

The calibration in PHD2 is automatic, so you just press and wait. PHD2 calculates the pulse to be sent for each calibration step from the values you have entered in the Profile, such as FL of the guidescope and guidespeed.

?

If the values are correct, the automatic PHD2 calibration will take 8-12 steps to complete in AZ and 8-12 steps to complete in ALT.?

?

However If it takes 50 steps or 5 steps then something entered when creating the profile like the guidespeed is incorrect.

?

When PHD2 is performing the calibration it is moving the mount pretty fast West then East, North then South (in order to understand how the mount is behaving), that's why the pulse is 5000ms with a slow guidespeed.

?

During guiding the pulses will be very small, yes below 500 ms, (even though i have a very slow guidespeed).

?

Best Regards

Gabriel

?

?

Re: Settings for use of AutoGUIDE

#7413
Edited

Yes i was surprised too,

?

Thank you!

?

The calibration in PHD2 is automatic, so you just press and wait. PHD2 calculates the pulse to be sent for each calibration step from the values you have entered in the Profile, such as FL of the guidescope and guidespeed.

?

If the values are correct, the automatic PHD2 calibration will take 8-12 steps to complete in AZ and 8-12 steps to complete in ALT.?

?

However If it takes 50 steps or 5 steps then something entered when creating the profile like the guidespeed is incorrect.

?

When PHD2 is performing the calibration it is moving the mount pretty fast West then East, North then South (in order to understand how the mount is behaving), that's why the pulse is 5000ms with a slow guidespeed.

?

During guiding the pulses will be very small, yes below 500 ms, (even though i have a very slow guidespeed).

?

Best Regards

Gabriel

?

Re: Settings for use of AutoGUIDE

#7412

Waouh !!

Just amazing what accuracy you get from just a 180 mm focal length guiding your 2700 mm focal length scope !!!!

and in easy track mode !!!

A friend of mine was saying to me yesterday that auto guiding is normally done with a FL of 1/4 of the main scope FL that would be 2700/4=675 mm FL !

Congratulations !!

You indicate

??With 6 arc seconds per second in ServoCAT Sky for the GUIDE 2 value and a calibration step size of around 5000 ms (pulse) results in 8-12 steps ?

What is a ? step ? ?

and how do you calculate 8-12 steps ?

I’m ?also surprised by the 5000 ms pulse?

you mean PHD2 is sending a correction a track rate for 5 seconds ?! I thought it was only correcting with small pulses like <500 ms…

thanks for reply

Raphael

?

Re: Settings for use of AutoGUIDE

#7411

Needed !!

Cheers

Wes Smith?

On Tue, Feb 18, 2025 at 4:03?AM Gabriel Wiklund via <gabriel.wiklundholeshot=[email protected]> wrote:

Show quoted text

Here comes a description of the hardware and settings i have used to successfully Autoguide with my ServoCat driven Starstructure:

?

?

1. Hardware:

- Generic 50mm/180mm Guidescope, i ordered this one:

it's very light and stiff, comes with mounting options so i even could use one of the threads for the Telrad base to mount it.?

It is almost a crime in imaging to guide with 180mm focal length on 2725mm FL that i am using, but it is enough to provide corrections for and verify guiding down to 0.8" arc seconds total RMS.

?

- 5 meter ST4 cable, if you can find the right length RJ12 6P6C in a local store it will be much cheaper, at least here 3 meters was in stock.

- ZWO ASI 120 MM Mini Guidecamera (comes with a 2 meter ST4 and USB cable). Touptek or a similar brand could have a cheaper alternative.

?

The above hardware was selected because it was the lowest cost alternative that i could find which did not require any modification to my telescope.

?

1. Software?

- PHD2

?

After mounting the Guidescope, connecting the ST4 cable from the Guidecamera to the back of the ServoCAT AUX/AG port and connecting the USB cable from the Guidecamera to your PC you are ready to go from a hardware standpoint except aligning the guidescope with the main scope.

?

In ServoCAT sky i use 6 arc seconds per second for the GUIDE 2 value (0.40 x Sidereal).

?

Download PHD2 and the camera driver, start PHD2 and follow the instructions. When choosing mount select "On camera" and for the Mount guide speed enter 0.30 x Sidereal since the measured guidespeed at least in my case has been lower.

?

The instructions will end with creating a dark library where it asks you to cover the scope, after that the setup is done!

?

Click on the brain icon and choose Algorithms at the top of the window. Change the declination Algorithm to "Hysteresis" like is already selected on RA and make sure dec mode is on auto. In our case RA is AZ and DEC is ALT. Now click on Global and uncheck "use multiple stars" and uncheck Star mass detection.

?

I then pointed the main scope at the moon with a 28mm eyepiece and the guidecamera looping exposures connected to SharpCap. I then adjusted the Guidescope untill the moon was centered in the guidescope as well. You could align the guidescope off center with regards to the main scope as long as the main scope is pointing within the guidescope field of view, and as long as the guidestar you choose when imaging is as close to that point as possible since the field will appear to rotate around the guidestar. PHD2 has a crosshair overlay that can be used.

?

You can now focus the guidecamera on the moon by slightly moving it in or out before locking the lock screws. Personally i reached better focus later on by doing the same on stars (the guide assistant will tell you if you need to focus), be aware that the movements required to reach focus are very small.

?

Make sure that the "Guide" button on the ServoCAT handpad is selected or PHD2 will not be able to send pulse commands.

?

Slew the scope to the South about 35 degrees above the horizon, PHD2 recommends that the calibration should be done close to the Celestial Equator. Begin looping 1s exposures, now slew the scope UP in Alt untill it moves to resolve backlash.

?

At the bottom of the window hit Guide, now the calibration will start. PHD2 will move the mount East, Weast, North, and South in order to understand how the mount behaves. When the calibration is done click on tools at the top of the window then "review" calibration data.? Verify that between 8-12 steps where used on either axis during the calibration.

?

If much more than 12 steps where used the guidespeed entered when creating the PHD2 profile is faster than the actual guidespeed, that will result in PHD2 not moving the mount enough, the reason being PHD2 sending short guide pulses assuming a fast guidespeed.

?

If less than 8 steps where used that means the entered guidespeed when creating the PHD2 profile is slower than the actual guidespeed, causing PHD2 to send long guidepulses moving the mount to much = same distance covered but with fewer steps.

?

If the guidespeed is incorrect PHD2 advises not to change that manually, but to create a new profile. In the new profile enter the measured guidespeed you got from the calibration.

?

The scope will already have begun guiding after the calibration, and don't worry if the guiding is bad, since the scope is only 35 degrees above the horizon the atmosphere will cause the guidestar to bounce around causing the scope to chase the seeing if it is bad with the 1s exposures from the calibration.

?

Stop guiding and slew to the object, loop 2s exposures and begin guiding and wait a minute or so, then click tools on the top of the window then choose "Guiding assistant". PHD2 will stop guiding and measure the mounts unguided tracking performance/behaviour. Uncheck "Measure declination backlash" in the lower left corner.

?

PHD2 recommends waiting 2 minutes, click on "STOP" and follow the recommendations, you don't have to go and change the settings, you simply press on "apply" for the suggestions PHD2 comes up with, with the exception of improving guidescope focus which it may suggest, or polar alignment which is not relevant for us.

?

If you after all this see very large guidestar deflections especially after corrections, the PHD2 documentation recommends that you should not wildly begin changing settings, you should however take a closer look at how the guidescope is mounted.

?

Just a few microns of flexure is capable of throwing of the guidestar by 6 arc seconds, several star diameters, a human hair is 50 microns thick.

?

I followed that recommendation and tightened the adjustments screws as best i could on the Guidescope, it did change the pointing of the guidescope slighlty but my main scope is still pointing in the lower right corner of the Guidescope field of view so i just select guidestars there instead. It helped a lot taming the deflections.

?

Besides that seeing plays a huge roll, if the seeing is really bad guiding will be bad since the stars will move even if the scope is not moving.

?

If the seeing is good, guiding should work very well, If the guiding looks bad but the exposures look good, don't worry about the guidegraph, if the guidegraph looks bad and the exposures are bad then it's worth taking a look at.

?

I tested this 2 days ago for 1 hour on M106 and it stayed locked with M106 exactly in the center for 1 hour with 1-1.3 arc seconds total RMS guiding with round stars.

?

I did not mention the following above to not complicate things but it is possible to connect the Meade Generic or ServoCAT? driver to PHD2 in order to provide PHD2 with pointing information so that it can use dec compensation. If you use "On Camera" like i have suggested above you will have to enter the DEC (ALT) manually before calibration and before guiding on a new object.

?

?

Clear skies!

Gabriel

?

?

?

?

?

?

?

?

Re: Settings for use of AutoGUIDE

#7410

Update:

?

I got sub arc second guiding with Easytrack and Autoguide when i was out a few days ago: (Graph uploaded on Astrobin)

?

Even though it is possible to calibrate (with a warning from PHD2 after the result) and also guide at the celestial equator, i get? a much better calibration at for example 60 degrees azimuth and 30-40 degrees in altitude. Probably beacuse the Altitude rate is almost zero at the celestial equator.

?

It's probably best to calibrate at the same azimuth as the object that will be imaged and at 30-40 degrees above the horizon with dec compensation.

?

The key to get a good calibration in PHD2 is to make sure it uses 8-12 steps per axis. With 6 arc seconds per second in ServoCAT Sky for the GUIDE 2 value and a calibration step size of around 5000 ms (pulse) results in 8-12 steps.

?

If the calibration step size is say 2300 ms you simple change the guidespeed x sidereal in the box above when on the guiding tab in PHD2 untill you get a step size of around 5000ms (not necessary to create a new profile). However, if i was to lower or increase the GUIDE 2 value in ServoCAT Sky, 5000ms steps size would no longer result in 8-12 steps. Also not sure if the GUIDE 2 value on a Starstructure would translate to other dobs.

?

Here is how my latest calibration looks like:

?

/Gabriel

?

Re: Settings for use of AutoGUIDE

#7409
Edited

Thank you Gary, happy to help!

?

Great tip, this also means you will visually get a rough idea/understanding of the guide calibration, so when PHD2 moves the scope east, back west, north back to south the path in a perfect calibration should create a 90° degree angle. (also visualized in review calibration data).

?

In other words in such a scenario the scope is fully responsive to PHD2 pulse commands, if the angles are questionable it could be because of backlash or poor unguided tracking.

?

With a good 2-star alignment i get a very good calibration, yesterday with EasyTrack i got the warning: "RA and DEC angles are questionable guiding may be impaired" but as you can see guiding can still work well despite a warning.

?

If tracking is slightly off prior to performing the calibration, click on the brain icon and then on guiding? at the top of the window if I remember correctly, then check "assume RA/AZ orthogonal to DEC/ALT" so that the RA/AZ tracking error does not affect the DEC/ALT calibration.

?

/Gabriel?

?