开云体育

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

[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

?

?

[Edited Message Follows]

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 slightly east of the meridian 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. Make Sure you are on the east side of the Meridian since Alt will change directions and move down after the meridian.

?

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

?

?

?

?

?

?

?

?

Just for fun this evening i tried using Easytrack on it's own without any DSC just to see if autoguiding is able to compensate for such basic tracking. I have marks on my scope so i manually can point it at roughly 0 az and 63 alt, so with SPEED 2 i pressed the CCW button on the handpad, switched on the ServoCAT and let go of the button when the yellow SPM light turned on = scope is tracking.

?

Here is a 60 second sub (crop of the very center), i just slewed the scope randomly to the north east at about 50 degrees in altitude. In actual capture i would of course never use that kind of exposure time since my scope is sky fog limited after only 20 seconds.

?

?

Here is the graph in PHD2:

?

?

Pherhaps hard to see but total RMS is 1.28" arc seconds, not bad for only using Easytrack if you ask me.

?

So in other words, the 2-star alignment is less critical when using autoguiding.

?

/ Gabriel

?

?

Dear both,

Thanks to your message, I realise I made a confusion :

I though the guide 1 was used for guide fast value and guide 2 for guide slow value. But this is completely wrong as you explained and as written in the manual :

"Guide speeds:
With SPEED 1/2 set to 1: GUIDEslow = GUIDE1 GUIDEfast = 2X GUIDE1
With SPEED 1/2 set to 2: GUIDEfast = GUIDE2 GUIDEslow = 1/2 x GUIDE2"

?

Sorry for my mistake and thanks for explanations !

Regards

Rapha?l

?

?

My theory is that the unguided tracking already is so good that the corrections need to be very subtle to make things better instead of worse.

?

?

/Gabriel

?

?

Dear all,

Thanks Gary to have explained the way the guiding correction works.

You say "The way ST4 applies guiding is to add a fixed amount (programmed in GUIDE 2 speed value....".?

OK

Then in his message /g/ServoCAT/message/7395 I see Gabriel has lowered the guidespeed in ServoCAT Sky to 6 arc seconds per second to achieve a good auto guiding

But I see at same time the classical guide2 values are around 160 arc sec/sec for obsessions scopes, whatever their diameter, which is very far away from the 6 arc sec/sec that found Gabriel.

There is a conflict here : if the guide2 value is 6 arc sec/sec for autoguiding, it will be way too slow for visual observing.

Gabriel, how do you manage this if you want to observe visually ?

Changing the rate settings in servocat sky each time you change from autoguiding to visual would be boring...

With your guide 2 being 6 arc seconds/sec, did you change your guide 1 speed -which is classicaly in the 250-280 arc sec/sec - to 160 arc sec/sec to use it for visual observation ? Then you also need to reajust the slew and jog rates also to have smooth ratio change...

In this case the guide 2 will be only allocated to autoguiding and guide 1, slew, jog for visual observing.... Right ???

Unless I miss something ???

Regards?

Rapha?l

Gabriel : I send you a private email to discuss your scope settings and avoid polluting this group. I hope you have received it.

?