Date   

Re: PASILL4 on Mach1, update

Pierre Henrotay
 

I placed a drawing, not meant to be 100% accurate but it gives a fair
idea of the respective positions: look in the files section:
http://tech.groups.yahoo.com/group/ap-gto/files/phenrotay/
with name
PASILL4-2.jpg

This is +- what it looks like when the alignment is accurate (< 1
arcmin) and when Polaris brought in its gap after rotating the
reticle housing.

Pierre

--- In ap-gto@..., "Jeff" <jlc@...> wrote:

The stars are off in the same direction, correct?

Is the star even within the marks for precession?

I have a pasill4 on a 1200 but usually just always do drift
alignment when
imaging. For visual it doesnt have to be very accurate.

Right now, the mount is stowed, but if I get out soon I'll check it.
(Planning on it, but work is distracting me.)

jeff


Re: PASILL4 on Mach1, update

Jeff <jlc@...>
 

The stars are off in the same direction, correct?

Is the star even within the marks for precession?

I have a pasill4 on a 1200 but usually just always do drift alignment when
imaging. For visual it doesnt have to be very accurate.

Right now, the mount is stowed, but if I get out soon I'll check it.
(Planning on it, but work is distracting me.)

jeff



_____

From: ap-gto@... [mailto:ap-gto@...] On Behalf Of
phenrotay
Sent: Sunday, April 27, 2008 8:58 AM
To: ap-gto@...
Subject: [ap-gto] PASILL4 on Mach1, update



Dear,

I started a few weeks ago a long thread concerning the usage of the
PASILL4 polar scope on my Mach1 (starting with post #21642).

Hereby the updated status.

I got the chance yesterday night to test my PASILL4 on a friend's
900GTO.
We rechecked that the reticle was aligned with the optical axis of
the polar scope (by rotating the reticle housing) and was aligned
with the RA axis of the 900GTO (by rotating the RA axis).
All was fine, no need for any change.

We reproduced equivalent results as the ones that I previously
obtained on my Mach 1, that is:
- using the PASILL4 - 3 stars visible -, we end up about 10
arcminutes from the pole
- after a computer assisted polar alignment (bringing us about 1
arcminute from pole), the position of the 3 stars do not match the
one expected from the engravings:
when Polaris is brought within its gap by rotating the reticle
housing, the 2 other stars are at about 20 degrees hour angle from
their expected position
I think we can exclude operator error - we double checked what we
were doing.

So it seems that the problem lies in my PASILL4 itself. Unless anyone
has a better idea.

I hesitate in asking my dealer for a replacement, as I do not know if
10 arcminutes misalignment is out of specs. Maybe I am expecting too
much accuracy from it - I am used to the Vixen Atlux polar scope,
which allowed me to be routinely under 5 arcminutes
and under 2 arcminutes when used carefully, in a matter of seconds of
time.

Also, Roland mentioned that if one reticle was defective, all would
be. So, if out of specs, it might be worth to have a global check
anyway from AP about this issue (potentially, it could be a general
error in the engravings ? such thing can happen, someone mentioned a
problem in the past with scope magnification).

Unfortunately I have no way to access a "good working" PASILL4, as
someone suggested.
There is none close to where I live, only non-rotating (pre-PASILL3)
models - these are difficult to use on the Mach1 and a test would not
be representative.

For the moment, I will thus concentrate on using other techniques
(the quick drift, as explained in the manual, which now has
additional drawings and detailed lists of candidate stars, thank for
this) and use the PASILL4 only for a coarse start.

Again, not a major issue but a bit frustrating.
I think AP mounts deserve a first-class polar scope (as Takahashi and
Vixen do have), and - unless mine is specifically a lemon - this one
does not match up.

Pierre

PS:
Some info to avoid repostings:
- the model is the newest one (with engravings till 2030)
- PoleAlignMax was used for achieving precise alignment and measuring
misalignment


PASILL4 on Mach1, update

Pierre Henrotay
 

Dear,

I started a few weeks ago a long thread concerning the usage of the
PASILL4 polar scope on my Mach1 (starting with post #21642).

Hereby the updated status.

I got the chance yesterday night to test my PASILL4 on a friend's
900GTO.
We rechecked that the reticle was aligned with the optical axis of
the polar scope (by rotating the reticle housing) and was aligned
with the RA axis of the 900GTO (by rotating the RA axis).
All was fine, no need for any change.

We reproduced equivalent results as the ones that I previously
obtained on my Mach 1, that is:
- using the PASILL4 - 3 stars visible -, we end up about 10
arcminutes from the pole
- after a computer assisted polar alignment (bringing us about 1
arcminute from pole), the position of the 3 stars do not match the
one expected from the engravings:
when Polaris is brought within its gap by rotating the reticle
housing, the 2 other stars are at about 20 degrees hour angle from
their expected position
I think we can exclude operator error - we double checked what we
were doing.

So it seems that the problem lies in my PASILL4 itself. Unless anyone
has a better idea.

I hesitate in asking my dealer for a replacement, as I do not know if
10 arcminutes misalignment is out of specs. Maybe I am expecting too
much accuracy from it - I am used to the Vixen Atlux polar scope,
which allowed me to be routinely under 5 arcminutes
and under 2 arcminutes when used carefully, in a matter of seconds of
time.

Also, Roland mentioned that if one reticle was defective, all would
be. So, if out of specs, it might be worth to have a global check
anyway from AP about this issue (potentially, it could be a general
error in the engravings ? such thing can happen, someone mentioned a
problem in the past with scope magnification).

Unfortunately I have no way to access a "good working" PASILL4, as
someone suggested.
There is none close to where I live, only non-rotating (pre-PASILL3)
models - these are difficult to use on the Mach1 and a test would not
be representative.

For the moment, I will thus concentrate on using other techniques
(the quick drift, as explained in the manual, which now has
additional drawings and detailed lists of candidate stars, thank for
this) and use the PASILL4 only for a coarse start.

Again, not a major issue but a bit frustrating.
I think AP mounts deserve a first-class polar scope (as Takahashi and
Vixen do have), and - unless mine is specifically a lemon - this one
does not match up.


Pierre

PS:
Some info to avoid repostings:
- the model is the newest one (with engravings till 2030)
- PoleAlignMax was used for achieving precise alignment and measuring
misalignment


Focuser Backlash

Larry Phillips
 

After using FocusMax with my new AP 140 4" focuser using a FeatherTouch
motor, I am wondering if there is anyway to adjuct the focuser backlash.

Larry


Re: DEC Backlash and RA "Drift" on AP1200GTO

Joe Mize
 

Jim & Richard, I saved a post from Roland back on 02-19 in "Re: [ap-gto] Guide star drifting in RA" thread.

At the time it made since but reading it now it's a little convoluted without knowing went on beforehand. The important two things I saved it for was what Roland said,

1) In his first paragraph he said don't use the Guider Tab's DEC Co-ordinate box. I do this myself. If you're unfamiliar with this technique I'll 'try' to explain. Set the DEC box to '0' and Uncheck the "Use Scope DEC" in the Guider dropdown list. Then calibrate my Guider on the Equator near the Meridian where the sky moves its fastest. The further away form the Equator you are guiding the slower the sky moves and the smaller the deviations. With the Calibration on the Equator the numbers generated are sufficient to correct those larger deviations yet when deviations occur further away from the Equator the same numbers are used to make smaller corrections. (hope you get jist of what I'm trying to say) My Calibration lasts as long as I don't make changes to my imaging train. The last time I Calibrated my Guider was months ago. This method works even if you're not permanently mounted, works great. My RMS' are usually in the lower 0.0xx's. You should be able to do so too.

2) I believe what Roland says in his second paragraph: "...(p.s. you didn't bin the guider by any chance?)." means when you Calibrate your Guider you need to do so in Bin-1 scale. MaximDL says the same thing and goes further by saying to turn off Backlash in the Guider settings while Calibrating.

The following is Roland's response. I hope I interpreted correctly. HTH...joe :)

===
I looked at Maxim and do not see what you are talking about on the uncheck
"use Scope Dec" Is this by chance the make simultaneous corrections?
No, It's under Options. If you have an older version of the software, there
is a place for you to enter the Dec co-ordinate. Always use zero here,
otherwise the software will reduce the correction level by the cosine of the angle
that you enter, and this is not good.

If you look in your parameters, it should tell you what te pixel scale is,
and that should be somewhere close to what you calculate for your focal length
and pixel size (p.s. you didn't bin the guider by any chance?). If it isn't,
then indeed the software will make smaller corrections than is needed to bring
the star back to zero.

In order for you to guide successfully, you need to know what every number
means. If you do not, you will never be able to troubleshoot the guide loop, and
certainly I cannot do it very well for you because I have no idea what is in
your various parameter windows.

Roland Christen
===


"May You Go Among The Imperishable Stars"
Joe Mize www.cav-sfo.com
Chiefland Astronomy Village, Fla.

----- Original Message -----
From: "Richard Seavey" <reseavey@...>
To: <ap-gto@...>
Sent: Saturday, April 26, 2008 11:03 PM
Subject: Re: [ap-gto] Re: DEC Backlash and RA "Drift" on AP1200GTO


Hi Jim
Your rms guiding errors are quite similar to what I get. I image at 0.72
arc-sec per pixel, so on nights when the seeing is 2.5 arc-sec or better, I
need to keep the errors below about 0.3 arc-sec rms. Even more important is
to get the same error in both axis so that the stars aren't elongated. For
me, oval stars are a lot more annoying than slightly bigger stars. I am
using MaxIm to control the guiding and usually turn on the feature that
plots the guiding errors in real time. I know I have backlash in the DEC
axis, but need to measure it again so I can compare it to what you are
getting. My sub exposures are 10 minutes and guide exposures are usually
between 2 and 6 seconds. I have been using 3 pixels of dither and my max
move is 0.13 sec. It would be very interesting to see what others are
getting for guiding errors.

Richard


At 03:06 AM 4/26/2008 +0000, you wrote:

Hi Richard,

It varies. And CCDSoft doesn't provide those numbers in a convenient
fashion, so I have to go through each 8min exposure to mine them.

Here are a couple of samples from last night. All are 8min imaging
exposures, with 4sec guide exposures. The numbers are in arc-seconds:

1. RAmax = 0.824, RArms = 0.252, DECmax = 0.705, DECrms = 0.303
2. RAmax = 1.337, RArms = 0.323, DECmax = 1.054, DECrms = 0.329
3. RAmax = 1.970, RArms = 0.666, DECmax = 1.967, DECrms = 0.524

These were: (1) the best image of the night (perhaps the best result
I've EVER seen at my site with my gear), (2) a more typical image of
the night, and (3) the worst image of the night, respectively. CCDI
says the FWHMs were 1.94", 3.07", and 4.25", for the actual images,
respectively.

To be fair, the seeing did seem to change over the course of the
night, starting and ending reasonably well but deteriorating for 45min
or so in the middle.

I'm not sure how representative the above numbers truly are. Most
times I bother to calculate out this stuff the DEC rms errors are
actually larger than the RA rms errors (and both are generally larger
than the numbers shown above) which suggests to me that DEC errors are
going uncorrected for one reason or another, and I personally believe
that reason to be DEC backlash.

This was also shooting M81, which is pretty far north, and so the
periodic error is only 1/3 what it would be at the equator, in terms
of "true sky angle".

Cheers,
JS

--- In <mailto:ap-gto%40yahoogroups.com>ap-gto@..., Richard
Seavey <reseavey@...> wrote:

Jim
What are your typical peak and rms guide errors in DEC and RA when your
seeing is in the 2-3 arc-sec range?

Richard



------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list
see http://groups.yahoo.com/group/ap-gtoYahoo! Groups Links




Re: DEC Backlash and RA "Drift" on AP1200GTO

Richard Seavey
 

Hi Jim
Your rms guiding errors are quite similar to what I get. I image at 0.72
arc-sec per pixel, so on nights when the seeing is 2.5 arc-sec or better, I
need to keep the errors below about 0.3 arc-sec rms. Even more important is
to get the same error in both axis so that the stars aren't elongated. For
me, oval stars are a lot more annoying than slightly bigger stars. I am
using MaxIm to control the guiding and usually turn on the feature that
plots the guiding errors in real time. I know I have backlash in the DEC
axis, but need to measure it again so I can compare it to what you are
getting. My sub exposures are 10 minutes and guide exposures are usually
between 2 and 6 seconds. I have been using 3 pixels of dither and my max
move is 0.13 sec. It would be very interesting to see what others are
getting for guiding errors.

Richard

At 03:06 AM 4/26/2008 +0000, you wrote:

Hi Richard,

It varies. And CCDSoft doesn't provide those numbers in a convenient
fashion, so I have to go through each 8min exposure to mine them.

Here are a couple of samples from last night. All are 8min imaging
exposures, with 4sec guide exposures. The numbers are in arc-seconds:

1. RAmax = 0.824, RArms = 0.252, DECmax = 0.705, DECrms = 0.303
2. RAmax = 1.337, RArms = 0.323, DECmax = 1.054, DECrms = 0.329
3. RAmax = 1.970, RArms = 0.666, DECmax = 1.967, DECrms = 0.524

These were: (1) the best image of the night (perhaps the best result
I've EVER seen at my site with my gear), (2) a more typical image of
the night, and (3) the worst image of the night, respectively. CCDI
says the FWHMs were 1.94", 3.07", and 4.25", for the actual images,
respectively.

To be fair, the seeing did seem to change over the course of the
night, starting and ending reasonably well but deteriorating for 45min
or so in the middle.

I'm not sure how representative the above numbers truly are. Most
times I bother to calculate out this stuff the DEC rms errors are
actually larger than the RA rms errors (and both are generally larger
than the numbers shown above) which suggests to me that DEC errors are
going uncorrected for one reason or another, and I personally believe
that reason to be DEC backlash.

This was also shooting M81, which is pretty far north, and so the
periodic error is only 1/3 what it would be at the equator, in terms
of "true sky angle".

Cheers,
JS

--- In <mailto:ap-gto%40yahoogroups.com>ap-gto@..., Richard
Seavey <reseavey@...> wrote:

Jim
What are your typical peak and rms guide errors in DEC and RA when your
seeing is in the 2-3 arc-sec range?

Richard


Re: DEC Backlash and RA "Drift" on AP1200GTO

Bill Bradford
 

Glad you posted this, Anthony. I was going to ask you in your previous post if you were dithering.

Joe's post was of great benefit to me since (now that I have a Mach1, my tracking and guiding will be good enough to NEED dithering, unlike with my previous mount :>), and I would have gone crazy trying to dither with so short a max move.

I have always used about .3 secs as max move on my old mount and would have used that with the Mach1 while trying to dither.

Bill

----- Original Message -----
From: ayiomamitis
To: ap-gto@...
Sent: Saturday, April 26, 2008 2:47 AM
Subject: [ap-gto] Re: DEC Backlash and RA "Drift" on AP1200GTO


--- In ap-gto@..., "JoeMize" <jmize@...> wrote:
>
> Jim, change you Max Move from 0.2sec to 2.0sec. 0.2sec limits the
> correction to a Maximum drive time of 0.2sec. Changing to 2.0sec will allow
> you to correct longer excursions and Dither moves. I actually have mine set
> to 3.0sec because of the size of my Dither moves...joe :)

Aha! Now perhaps I see why the Dither plugin for CCDSoft was hanging on my machine. I
will go back and check but this time using a purposely much higher setting for MAX.

Thanks Joe!

Anthony.

>
>
> "May You Go Among The Imperishable Stars"
> Joe Mize www.cav-sfo.com
> Chiefland Astronomy Village, Fla.
>
> ----- Original Message -----
> From: "Jim S." <blues_rule_solomon_1999@...>
> To: <ap-gto@...>
> Sent: Friday, April 25, 2008 3:53 PM
> Subject: [ap-gto] DEC Backlash and RA "Drift" on AP1200GTO
>
>
> > Hi,
> >
> > I've got some questions about getting the best possible guiding
> > results out of my AP1200. It's performing better than any mount I've
> > ever owned, by a mile, but there might be some room for me to improve
> > my results, which is the topic of this post.
> >
> > Dec Backlash:
> >
> > First, I've measured my DEC backlash at mean = 12.55", sigma = 3.59".
> > (See below for the method I'm using.) A friend and I removed the DEC
> > cover and one of the reduction gears, and could not "feel" any
> > backlash in the worm gear to worm wheel mesh. Rather, it looked to us
> > as if all or most of that backlash was in the mesh among the reduction
> > gears, in which we could indeed feel some slop.
> >
> > DEC Backlash is causing me some grief in guiding, as I can see the
> > tell-tale signs of the DEC axis "wandering between the rails" when
> > looking at the Autoguider.log file in CCDSoft, with the result that
> > DEC errors take many guide-exposure periods to correct. Sometimes it
> > takes CCD Commander a long time to "dither" because it has to unwind
> > the backlash, and sometimes it gives up because it takes too long to
> > reach my minimum-error threshold before kicking off an exposures. And
> > in so dithering in the DEC direction, it almost always overshoots.
> >
> > I'm using the "Roland-approved" guiding parameters: guide rate = 1x
> > Sidereal, min = 0.02s, max = 0.2s, backlash compensation = OFF, and
> > calibration time = 30s, guide exposures = 4s (sometimes longer), PEC =
> > ON, Aggressiveness = 8; and my polar alignment error is VERY small,
> > well less than an arc-minute according to PAM and verified with a
> > drift. The measured calibration speeds agree with the analytical
> > computed values to within tenths of a percent, so indeed the
> > calibration results are "correct".
> >
> > My question is thus: Is it possible on the AP1200 to adjust the
> > reduction-gear mesh to trim some of this backlash? If indeed the
> > "slop" is in the reduction gears, then I don't believe "intentional
> > DEC misbalance" will help as a "solution" to this problem, though
> > perhaps intentional polar misalignment -- to induce some drift in a
> > constant direction -- might help. I think this latter case, however,
> > is inevitable when atmospheric refraction and ANY polar alignment
> > error is taken into account. And there will be an inevitable
> > "reversal" when dithering.
> >
> > RA "Drift":
> >
> > My long-term RA "drift" has an odd shape that I can't quite explain,
> > and fitting a curve to that "drift" is imperative when using PEMPro to
> > dial in an optimal PE curve. I've uploaded a chart to my web site for
> > inspection:
> >
> > http://www.SaratogaSkies.com/tmp/ra-drift.gif
> >
> > The spot data is the instantaneous RA error (with PEC off) measured by
> > PEMPro. The solid line is a "curve fit" I've done which is simply a
> > moving average of the instantaneous errors, wherein the "window" of
> > that moving average is equal to the worm period (382.95 seconds).
> >
> > Can someone explain why the "RA drift" curve has the odd shape it
> > does? I would expect it to be roughly monotonically increasing or
> > decreasing, as polar misalignment and/or atmospheric refraction affect
> > the apparent RA of the star.
> >
> > Could this be the reduction gears at work? Or perhaps flexure/sagging
> > of the camera/focuser? I'm using a 6" refractor with the FT3545
> > focuser, and an all-threaded coupling between a ST-2000XM camera and
> > the focuser, and the data was collected at DEC=0 beginning JUST west
> > of the Meridian and running for roughly 8 worm periods.
> >
> > More importantly, is this indicative of any issue with the mount? Or
> > is it just a long-term, slowly varying "drift", that I shouldn't sweat
> > because it can be easily guided out?
> >
> > Backlash Measurement Method:
> >
> > For those interested, here's how I'm measuring DEC Backlash:
> >
> > 1. Preload the DEC gear by moving (at 1x Sidereal) in the Y+ direction
> > (I use the "move" buttons in PulseGuide for this).
> > 2. Do a calibration in CCDSoft of a specified calibration time.
> > 3. Derive DEC backlash from the measured Y+ and Y- speeds.
> >
> > Note: Y+ is the first direction that CCDSoft moves in DEC, and then it
> > moves the same amount in Y-.
> >
> > I then compute the DEC Backlash as follows:
> >
> > DEC backlash = (Y+ - Y-) * Tc * Res
> >
> > where:
> >
> > o Y+ and Y- are the speeds in pixels/second measured by CCDsoft (px/s)
> > o Tc is the calibration time in seconds (s)
> > o Res is the imaging scale produced by my scope/camera combination in
> > arc-seconds/pixel ("/s)
> >
> > Is this method valid? If not, why not?
> >
> > Thanks for any help/advice you folks might be able to offer.
> >
> > Cheers,
> > Jim S.
> >
> >
> > ------------------------------------
> >
> > To UNSUBSCRIBE, or for general information on the ap-gto list
> > see http://groups.yahoo.com/group/ap-gtoYahoo! Groups Links
> >
> >
> >
> >
>


Re: DEC Backlash and RA "Drift" on AP1200GTO

ayiomamitis
 

--- In ap-gto@..., "JoeMize" <jmize@...> wrote:

Jim, change you Max Move from 0.2sec to 2.0sec. 0.2sec limits the
correction to a Maximum drive time of 0.2sec. Changing to 2.0sec will allow
you to correct longer excursions and Dither moves. I actually have mine set
to 3.0sec because of the size of my Dither moves...joe :)
Aha! Now perhaps I see why the Dither plugin for CCDSoft was hanging on my machine. I
will go back and check but this time using a purposely much higher setting for MAX.

Thanks Joe!

Anthony.



"May You Go Among The Imperishable Stars"
Joe Mize www.cav-sfo.com
Chiefland Astronomy Village, Fla.

----- Original Message -----
From: "Jim S." <blues_rule_solomon_1999@...>
To: <ap-gto@...>
Sent: Friday, April 25, 2008 3:53 PM
Subject: [ap-gto] DEC Backlash and RA "Drift" on AP1200GTO


Hi,

I've got some questions about getting the best possible guiding
results out of my AP1200. It's performing better than any mount I've
ever owned, by a mile, but there might be some room for me to improve
my results, which is the topic of this post.

Dec Backlash:

First, I've measured my DEC backlash at mean = 12.55", sigma = 3.59".
(See below for the method I'm using.) A friend and I removed the DEC
cover and one of the reduction gears, and could not "feel" any
backlash in the worm gear to worm wheel mesh. Rather, it looked to us
as if all or most of that backlash was in the mesh among the reduction
gears, in which we could indeed feel some slop.

DEC Backlash is causing me some grief in guiding, as I can see the
tell-tale signs of the DEC axis "wandering between the rails" when
looking at the Autoguider.log file in CCDSoft, with the result that
DEC errors take many guide-exposure periods to correct. Sometimes it
takes CCD Commander a long time to "dither" because it has to unwind
the backlash, and sometimes it gives up because it takes too long to
reach my minimum-error threshold before kicking off an exposures. And
in so dithering in the DEC direction, it almost always overshoots.

I'm using the "Roland-approved" guiding parameters: guide rate = 1x
Sidereal, min = 0.02s, max = 0.2s, backlash compensation = OFF, and
calibration time = 30s, guide exposures = 4s (sometimes longer), PEC =
ON, Aggressiveness = 8; and my polar alignment error is VERY small,
well less than an arc-minute according to PAM and verified with a
drift. The measured calibration speeds agree with the analytical
computed values to within tenths of a percent, so indeed the
calibration results are "correct".

My question is thus: Is it possible on the AP1200 to adjust the
reduction-gear mesh to trim some of this backlash? If indeed the
"slop" is in the reduction gears, then I don't believe "intentional
DEC misbalance" will help as a "solution" to this problem, though
perhaps intentional polar misalignment -- to induce some drift in a
constant direction -- might help. I think this latter case, however,
is inevitable when atmospheric refraction and ANY polar alignment
error is taken into account. And there will be an inevitable
"reversal" when dithering.

RA "Drift":

My long-term RA "drift" has an odd shape that I can't quite explain,
and fitting a curve to that "drift" is imperative when using PEMPro to
dial in an optimal PE curve. I've uploaded a chart to my web site for
inspection:

http://www.SaratogaSkies.com/tmp/ra-drift.gif

The spot data is the instantaneous RA error (with PEC off) measured by
PEMPro. The solid line is a "curve fit" I've done which is simply a
moving average of the instantaneous errors, wherein the "window" of
that moving average is equal to the worm period (382.95 seconds).

Can someone explain why the "RA drift" curve has the odd shape it
does? I would expect it to be roughly monotonically increasing or
decreasing, as polar misalignment and/or atmospheric refraction affect
the apparent RA of the star.

Could this be the reduction gears at work? Or perhaps flexure/sagging
of the camera/focuser? I'm using a 6" refractor with the FT3545
focuser, and an all-threaded coupling between a ST-2000XM camera and
the focuser, and the data was collected at DEC=0 beginning JUST west
of the Meridian and running for roughly 8 worm periods.

More importantly, is this indicative of any issue with the mount? Or
is it just a long-term, slowly varying "drift", that I shouldn't sweat
because it can be easily guided out?

Backlash Measurement Method:

For those interested, here's how I'm measuring DEC Backlash:

1. Preload the DEC gear by moving (at 1x Sidereal) in the Y+ direction
(I use the "move" buttons in PulseGuide for this).
2. Do a calibration in CCDSoft of a specified calibration time.
3. Derive DEC backlash from the measured Y+ and Y- speeds.

Note: Y+ is the first direction that CCDSoft moves in DEC, and then it
moves the same amount in Y-.

I then compute the DEC Backlash as follows:

DEC backlash = (Y+ - Y-) * Tc * Res

where:

o Y+ and Y- are the speeds in pixels/second measured by CCDsoft (px/s)
o Tc is the calibration time in seconds (s)
o Res is the imaging scale produced by my scope/camera combination in
arc-seconds/pixel ("/s)

Is this method valid? If not, why not?

Thanks for any help/advice you folks might be able to offer.

Cheers,
Jim S.


------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list
see http://groups.yahoo.com/group/ap-gtoYahoo! Groups Links




Re: DEC Backlash and RA "Drift" on AP1200GTO

ayiomamitis
 

--- In ap-gto@..., "Jim S." <blues_rule_solomon_1999@...> wrote:

Hi Joe,
Jim,


Thanks for the suggestion. I hesitate to do that, though, due to a
rare anomaly which can cause a huge, instantaneous, guide error. Wind
gusts, cosmic ray hits, a momentary fade from a cloud, a satellite
trail ... all of these things can cause a very large instantaneous
error, the damage of which I prefer to limit with that relatively
small maximum move. I certainly see the upside of increasing it though.
I am with you on this one as well ... my MIN is 0.01 sec and my MAX is 0.2 sec .... my
guiding results are stunning.

Anthony.


JS

--- In ap-gto@..., "JoeMize" <jmize@> wrote:

Jim, change you Max Move from 0.2sec to 2.0sec. 0.2sec limits the
correction to a Maximum drive time of 0.2sec. Changing to 2.0sec
will allow
you to correct longer excursions and Dither moves. I actually have
mine set
to 3.0sec because of the size of my Dither moves...joe :)


Re: DEC Backlash and RA "Drift" on AP1200GTO

Jim S.
 

Hi Richard,

It varies. And CCDSoft doesn't provide those numbers in a convenient
fashion, so I have to go through each 8min exposure to mine them.

Here are a couple of samples from last night. All are 8min imaging
exposures, with 4sec guide exposures. The numbers are in arc-seconds:

1. RAmax = 0.824, RArms = 0.252, DECmax = 0.705, DECrms = 0.303
2. RAmax = 1.337, RArms = 0.323, DECmax = 1.054, DECrms = 0.329
3. RAmax = 1.970, RArms = 0.666, DECmax = 1.967, DECrms = 0.524

These were: (1) the best image of the night (perhaps the best result
I've EVER seen at my site with my gear), (2) a more typical image of
the night, and (3) the worst image of the night, respectively. CCDI
says the FWHMs were 1.94", 3.07", and 4.25", for the actual images,
respectively.

To be fair, the seeing did seem to change over the course of the
night, starting and ending reasonably well but deteriorating for 45min
or so in the middle.

I'm not sure how representative the above numbers truly are. Most
times I bother to calculate out this stuff the DEC rms errors are
actually larger than the RA rms errors (and both are generally larger
than the numbers shown above) which suggests to me that DEC errors are
going uncorrected for one reason or another, and I personally believe
that reason to be DEC backlash.

This was also shooting M81, which is pretty far north, and so the
periodic error is only 1/3 what it would be at the equator, in terms
of "true sky angle".

Cheers,
JS

--- In ap-gto@..., Richard Seavey <reseavey@...> wrote:

Jim
What are your typical peak and rms guide errors in DEC and RA when your
seeing is in the 2-3 arc-sec range?

Richard


Re: DEC Backlash and RA "Drift" on AP1200GTO

Richard Seavey
 

Jim
What are your typical peak and rms guide errors in DEC and RA when your
seeing is in the 2-3 arc-sec range?

Richard

At 07:53 PM 4/25/2008 +0000, you wrote:

Hi,

I've got some questions about getting the best possible guiding
results out of my AP1200. It's performing better than any mount I've
ever owned, by a mile, but there might be some room for me to improve
my results, which is the topic of this post.

Dec Backlash:

First, I've measured my DEC backlash at mean = 12.55", sigma = 3.59".
(See below for the method I'm using.) A friend and I removed the DEC
cover and one of the reduction gears, and could not "feel" any
backlash in the worm gear to worm wheel mesh. Rather, it looked to us
as if all or most of that backlash was in the mesh among the reduction
gears, in which we could indeed feel some slop.

DEC Backlash is causing me some grief in guiding, as I can see the
tell-tale signs of the DEC axis "wandering between the rails" when
looking at the Autoguider.log file in CCDSoft, with the result that
DEC errors take many guide-exposure periods to correct. Sometimes it
takes CCD Commander a long time to "dither" because it has to unwind
the backlash, and sometimes it gives up because it takes too long to
reach my minimum-error threshold before kicking off an exposures. And
in so dithering in the DEC direction, it almost always overshoots.

I'm using the "Roland-approved" guiding parameters: guide rate = 1x
Sidereal, min = 0.02s, max = 0.2s, backlash compensation = OFF, and
calibration time = 30s, guide exposures = 4s (sometimes longer), PEC =
ON, Aggressiveness = 8; and my polar alignment error is VERY small,
well less than an arc-minute according to PAM and verified with a
drift. The measured calibration speeds agree with the analytical
computed values to within tenths of a percent, so indeed the
calibration results are "correct".

My question is thus: Is it possible on the AP1200 to adjust the
reduction-gear mesh to trim some of this backlash? If indeed the
"slop" is in the reduction gears, then I don't believe "intentional
DEC misbalance" will help as a "solution" to this problem, though
perhaps intentional polar misalignment -- to induce some drift in a
constant direction -- might help. I think this latter case, however,
is inevitable when atmospheric refraction and ANY polar alignment
error is taken into account. And there will be an inevitable
"reversal" when dithering.

RA "Drift":

My long-term RA "drift" has an odd shape that I can't quite explain,
and fitting a curve to that "drift" is imperative when using PEMPro to
dial in an optimal PE curve. I've uploaded a chart to my web site for
inspection:

<http://www.SaratogaSkies.com/tmp/ra-drift.gif>http://www.SaratogaSkies.com/tmp/ra-drift.gif

The spot data is the instantaneous RA error (with PEC off) measured by
PEMPro. The solid line is a "curve fit" I've done which is simply a
moving average of the instantaneous errors, wherein the "window" of
that moving average is equal to the worm period (382.95 seconds).

Can someone explain why the "RA drift" curve has the odd shape it
does? I would expect it to be roughly monotonically increasing or
decreasing, as polar misalignment and/or atmospheric refraction affect
the apparent RA of the star.

Could this be the reduction gears at work? Or perhaps flexure/sagging
of the camera/focuser? I'm using a 6" refractor with the FT3545
focuser, and an all-threaded coupling between a ST-2000XM camera and
the focuser, and the data was collected at DEC=0 beginning JUST west
of the Meridian and running for roughly 8 worm periods.

More importantly, is this indicative of any issue with the mount? Or
is it just a long-term, slowly varying "drift", that I shouldn't sweat
because it can be easily guided out?

Backlash Measurement Method:

For those interested, here's how I'm measuring DEC Backlash:

1. Preload the DEC gear by moving (at 1x Sidereal) in the Y+ direction
(I use the "move" buttons in PulseGuide for this).
2. Do a calibration in CCDSoft of a specified calibration time.
3. Derive DEC backlash from the measured Y+ and Y- speeds.

Note: Y+ is the first direction that CCDSoft moves in DEC, and then it
moves the same amount in Y-.

I then compute the DEC Backlash as follows:

DEC backlash = (Y+ - Y-) * Tc * Res

where:

o Y+ and Y- are the speeds in pixels/second measured by CCDsoft (px/s)
o Tc is the calibration time in seconds (s)
o Res is the imaging scale produced by my scope/camera combination in
arc-seconds/pixel ("/s)

Is this method valid? If not, why not?

Thanks for any help/advice you folks might be able to offer.

Cheers,
Jim S.


Re: DEC Backlash and RA "Drift" on AP1200GTO

Jim S.
 

Hi Joe,

Thanks for the suggestion. I hesitate to do that, though, due to a
rare anomaly which can cause a huge, instantaneous, guide error. Wind
gusts, cosmic ray hits, a momentary fade from a cloud, a satellite
trail ... all of these things can cause a very large instantaneous
error, the damage of which I prefer to limit with that relatively
small maximum move. I certainly see the upside of increasing it though.

JS

--- In ap-gto@..., "JoeMize" <jmize@...> wrote:

Jim, change you Max Move from 0.2sec to 2.0sec. 0.2sec limits the
correction to a Maximum drive time of 0.2sec. Changing to 2.0sec
will allow
you to correct longer excursions and Dither moves. I actually have
mine set
to 3.0sec because of the size of my Dither moves...joe :)


Re: DEC Backlash and RA "Drift" on AP1200GTO

Joe Mize
 

Jim, change you Max Move from 0.2sec to 2.0sec. 0.2sec limits the correction to a Maximum drive time of 0.2sec. Changing to 2.0sec will allow you to correct longer excursions and Dither moves. I actually have mine set to 3.0sec because of the size of my Dither moves...joe :)


"May You Go Among The Imperishable Stars"
Joe Mize www.cav-sfo.com
Chiefland Astronomy Village, Fla.

----- Original Message -----
From: "Jim S." <blues_rule_solomon_1999@...>
To: <ap-gto@...>
Sent: Friday, April 25, 2008 3:53 PM
Subject: [ap-gto] DEC Backlash and RA "Drift" on AP1200GTO


Hi,

I've got some questions about getting the best possible guiding
results out of my AP1200. It's performing better than any mount I've
ever owned, by a mile, but there might be some room for me to improve
my results, which is the topic of this post.

Dec Backlash:

First, I've measured my DEC backlash at mean = 12.55", sigma = 3.59".
(See below for the method I'm using.) A friend and I removed the DEC
cover and one of the reduction gears, and could not "feel" any
backlash in the worm gear to worm wheel mesh. Rather, it looked to us
as if all or most of that backlash was in the mesh among the reduction
gears, in which we could indeed feel some slop.

DEC Backlash is causing me some grief in guiding, as I can see the
tell-tale signs of the DEC axis "wandering between the rails" when
looking at the Autoguider.log file in CCDSoft, with the result that
DEC errors take many guide-exposure periods to correct. Sometimes it
takes CCD Commander a long time to "dither" because it has to unwind
the backlash, and sometimes it gives up because it takes too long to
reach my minimum-error threshold before kicking off an exposures. And
in so dithering in the DEC direction, it almost always overshoots.

I'm using the "Roland-approved" guiding parameters: guide rate = 1x
Sidereal, min = 0.02s, max = 0.2s, backlash compensation = OFF, and
calibration time = 30s, guide exposures = 4s (sometimes longer), PEC =
ON, Aggressiveness = 8; and my polar alignment error is VERY small,
well less than an arc-minute according to PAM and verified with a
drift. The measured calibration speeds agree with the analytical
computed values to within tenths of a percent, so indeed the
calibration results are "correct".

My question is thus: Is it possible on the AP1200 to adjust the
reduction-gear mesh to trim some of this backlash? If indeed the
"slop" is in the reduction gears, then I don't believe "intentional
DEC misbalance" will help as a "solution" to this problem, though
perhaps intentional polar misalignment -- to induce some drift in a
constant direction -- might help. I think this latter case, however,
is inevitable when atmospheric refraction and ANY polar alignment
error is taken into account. And there will be an inevitable
"reversal" when dithering.

RA "Drift":

My long-term RA "drift" has an odd shape that I can't quite explain,
and fitting a curve to that "drift" is imperative when using PEMPro to
dial in an optimal PE curve. I've uploaded a chart to my web site for
inspection:

http://www.SaratogaSkies.com/tmp/ra-drift.gif

The spot data is the instantaneous RA error (with PEC off) measured by
PEMPro. The solid line is a "curve fit" I've done which is simply a
moving average of the instantaneous errors, wherein the "window" of
that moving average is equal to the worm period (382.95 seconds).

Can someone explain why the "RA drift" curve has the odd shape it
does? I would expect it to be roughly monotonically increasing or
decreasing, as polar misalignment and/or atmospheric refraction affect
the apparent RA of the star.

Could this be the reduction gears at work? Or perhaps flexure/sagging
of the camera/focuser? I'm using a 6" refractor with the FT3545
focuser, and an all-threaded coupling between a ST-2000XM camera and
the focuser, and the data was collected at DEC=0 beginning JUST west
of the Meridian and running for roughly 8 worm periods.

More importantly, is this indicative of any issue with the mount? Or
is it just a long-term, slowly varying "drift", that I shouldn't sweat
because it can be easily guided out?

Backlash Measurement Method:

For those interested, here's how I'm measuring DEC Backlash:

1. Preload the DEC gear by moving (at 1x Sidereal) in the Y+ direction
(I use the "move" buttons in PulseGuide for this).
2. Do a calibration in CCDSoft of a specified calibration time.
3. Derive DEC backlash from the measured Y+ and Y- speeds.

Note: Y+ is the first direction that CCDSoft moves in DEC, and then it
moves the same amount in Y-.

I then compute the DEC Backlash as follows:

DEC backlash = (Y+ - Y-) * Tc * Res

where:

o Y+ and Y- are the speeds in pixels/second measured by CCDsoft (px/s)
o Tc is the calibration time in seconds (s)
o Res is the imaging scale produced by my scope/camera combination in
arc-seconds/pixel ("/s)

Is this method valid? If not, why not?

Thanks for any help/advice you folks might be able to offer.

Cheers,
Jim S.


------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list
see http://groups.yahoo.com/group/ap-gtoYahoo! Groups Links




DEC Backlash and RA "Drift" on AP1200GTO

Jim S.
 

Hi,

I've got some questions about getting the best possible guiding
results out of my AP1200. It's performing better than any mount I've
ever owned, by a mile, but there might be some room for me to improve
my results, which is the topic of this post.

Dec Backlash:

First, I've measured my DEC backlash at mean = 12.55", sigma = 3.59".
(See below for the method I'm using.) A friend and I removed the DEC
cover and one of the reduction gears, and could not "feel" any
backlash in the worm gear to worm wheel mesh. Rather, it looked to us
as if all or most of that backlash was in the mesh among the reduction
gears, in which we could indeed feel some slop.

DEC Backlash is causing me some grief in guiding, as I can see the
tell-tale signs of the DEC axis "wandering between the rails" when
looking at the Autoguider.log file in CCDSoft, with the result that
DEC errors take many guide-exposure periods to correct. Sometimes it
takes CCD Commander a long time to "dither" because it has to unwind
the backlash, and sometimes it gives up because it takes too long to
reach my minimum-error threshold before kicking off an exposures. And
in so dithering in the DEC direction, it almost always overshoots.

I'm using the "Roland-approved" guiding parameters: guide rate = 1x
Sidereal, min = 0.02s, max = 0.2s, backlash compensation = OFF, and
calibration time = 30s, guide exposures = 4s (sometimes longer), PEC =
ON, Aggressiveness = 8; and my polar alignment error is VERY small,
well less than an arc-minute according to PAM and verified with a
drift. The measured calibration speeds agree with the analytical
computed values to within tenths of a percent, so indeed the
calibration results are "correct".

My question is thus: Is it possible on the AP1200 to adjust the
reduction-gear mesh to trim some of this backlash? If indeed the
"slop" is in the reduction gears, then I don't believe "intentional
DEC misbalance" will help as a "solution" to this problem, though
perhaps intentional polar misalignment -- to induce some drift in a
constant direction -- might help. I think this latter case, however,
is inevitable when atmospheric refraction and ANY polar alignment
error is taken into account. And there will be an inevitable
"reversal" when dithering.

RA "Drift":

My long-term RA "drift" has an odd shape that I can't quite explain,
and fitting a curve to that "drift" is imperative when using PEMPro to
dial in an optimal PE curve. I've uploaded a chart to my web site for
inspection:

http://www.SaratogaSkies.com/tmp/ra-drift.gif

The spot data is the instantaneous RA error (with PEC off) measured by
PEMPro. The solid line is a "curve fit" I've done which is simply a
moving average of the instantaneous errors, wherein the "window" of
that moving average is equal to the worm period (382.95 seconds).

Can someone explain why the "RA drift" curve has the odd shape it
does? I would expect it to be roughly monotonically increasing or
decreasing, as polar misalignment and/or atmospheric refraction affect
the apparent RA of the star.

Could this be the reduction gears at work? Or perhaps flexure/sagging
of the camera/focuser? I'm using a 6" refractor with the FT3545
focuser, and an all-threaded coupling between a ST-2000XM camera and
the focuser, and the data was collected at DEC=0 beginning JUST west
of the Meridian and running for roughly 8 worm periods.

More importantly, is this indicative of any issue with the mount? Or
is it just a long-term, slowly varying "drift", that I shouldn't sweat
because it can be easily guided out?

Backlash Measurement Method:

For those interested, here's how I'm measuring DEC Backlash:

1. Preload the DEC gear by moving (at 1x Sidereal) in the Y+ direction
(I use the "move" buttons in PulseGuide for this).
2. Do a calibration in CCDSoft of a specified calibration time.
3. Derive DEC backlash from the measured Y+ and Y- speeds.

Note: Y+ is the first direction that CCDSoft moves in DEC, and then it
moves the same amount in Y-.

I then compute the DEC Backlash as follows:

DEC backlash = (Y+ - Y-) * Tc * Res

where:

o Y+ and Y- are the speeds in pixels/second measured by CCDsoft (px/s)
o Tc is the calibration time in seconds (s)
o Res is the imaging scale produced by my scope/camera combination in
arc-seconds/pixel ("/s)

Is this method valid? If not, why not?

Thanks for any help/advice you folks might be able to offer.

Cheers,
Jim S.


Re: PEMPro AP: some more help needed!

Luca <darknrg@...>
 

Hello Joe,
once saved the curve can be re-loaded to the mount via the same procedure, i
e. (A) read PE curve; (B) choosethe option from File; (C) Load the uploaded
curve back to the mount by choosing the option To Mount in the Write Curve
and by choosing the option PE from Mount or File in the drop down window.
The graphical display is created from the raw data every time the curve is
uploaded by PEMPro, so only the data are saved.

Ciao
Luca

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

From: Joseph Zeglinski
Date: 25/04/2008 20.39.41
To: ap-gto@...
Subject: Re: [ap-gto] PEMPro AP: some more help needed!

Thanks Luca, Ray,

Final point. Once I have saved the original AP factory setup "curve" to
a File, can I then re-install it into the mount's GTO controller, if I want
to get back to the original setup?
Perhaps only the graphical display is saved, and not the raw data for
reload, if I am saying this right.

Somewhere I recall reading that once you mess up, or replace the
settings with a new tested curve, you could not get back into the
"as-delivered" factory set configuration. Maybe that assumed you didn't
first download and save the factory settings (for your specific mount). If
so, the AP user manual should specifically warn you to save the installed
curve, before learning how to create a new one. Here, I assume AP doesn't do

this for you (before shipping the mount), specific to your mount, and save
them there, in case you ever wanted a reset.

Joe

----- Original Message -----
From: "Luca" <darknrg@...>
To: <ap-gto@...>
Sent: Friday, April 25, 2008 1:40 PM
Subject: Re: [ap-gto] PEMPro AP: some more help needed!

Hello Joe,
I'm not Ray, but I may have an answer: in PEMPro AP (the only version I
have) you can read the curve in the mount from the PROGRAM MOUNT tab,
where
it says "Read PE Curve" giving you the option of reading it from (A) the
Created PE Curve; (B) From Mount; (C) From File. If you choose (B) PEMPro
will read the curve from the mount and display it in the graph area. After
this is completed the option "To File" in the "Write PE Curve" area will
be
enabled and you'll be able to save your data in a file. After pressing "To
File" the program will ask you which of the displayed curves you want to
save to file; just choose the "PE from Mount or File" and you're done.
I would wait for Ray's confirmation on this, but I'm 99% sure it would
work.

Ciao Joe

Luca

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

From: Joseph Zeglinski
Date: 25/04/2008 19.01.31
To: ap-gto@...
Subject: Re: [ap-gto] PEMPro AP: some more help needed!

Hi Ray,

Side line question about all this.
Is it possible to "download" the existing curve data - perhaps the AP
factory set table values, in order to preserve them for possible set back?

I would feel more comfortable if I had a text file that I could revert the
GTO back to, if I screw up somewhere, in all the PEC training, or want
just
to get back to the original settings for comparison.

Thanks,
Joe








------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list
see http://groups.yahoo.com/group/ap-gtoYahoo! Groups Links



Re: Latest version of PEMPro AP SE

Larry Phillips
 

Ray,
I have a Mach1 and the regular version of PemPro. Any reason to use
the AP SE version instead of the full version when using an AP mount?

Larry

--- In ap-gto@..., "Ray Gralak" <rgr@...> wrote:

Hello everyone,

The version of PEMPro AP that Luca is using is rather old. If you
are using
PEMPro AP please make sure you have v1.70 build 149 (click Help-
About).

If needed you can download the latest version from here:

http://www.siriusimaging.com/PEMPro/PEMPro-APSE-1.70.149.exe

-Ray Gralak
Author of PEMPro


Re: PEMPro AP: some more help needed!

Joe Zeglinski
 

Thanks Luca, Ray,

Final point. Once I have saved the original AP factory setup "curve" to a File, can I then re-install it into the mount's GTO controller, if I want to get back to the original setup?
Perhaps only the graphical display is saved, and not the raw data for reload, if I am saying this right.

Somewhere I recall reading that once you mess up, or replace the settings with a new tested curve, you could not get back into the "as-delivered" factory set configuration. Maybe that assumed you didn't first download and save the factory settings (for your specific mount). If so, the AP user manual should specifically warn you to save the installed curve, before learning how to create a new one. Here, I assume AP doesn't do this for you (before shipping the mount), specific to your mount, and save them there, in case you ever wanted a reset.

Joe

----- Original Message -----
From: "Luca" <darknrg@...>
To: <ap-gto@...>
Sent: Friday, April 25, 2008 1:40 PM
Subject: Re: [ap-gto] PEMPro AP: some more help needed!


Hello Joe,
I'm not Ray, but I may have an answer: in PEMPro AP (the only version I
have) you can read the curve in the mount from the PROGRAM MOUNT tab, where
it says "Read PE Curve" giving you the option of reading it from (A) the
Created PE Curve; (B) From Mount; (C) From File. If you choose (B) PEMPro
will read the curve from the mount and display it in the graph area. After
this is completed the option "To File" in the "Write PE Curve" area will be
enabled and you'll be able to save your data in a file. After pressing "To
File" the program will ask you which of the displayed curves you want to
save to file; just choose the "PE from Mount or File" and you're done.
I would wait for Ray's confirmation on this, but I'm 99% sure it would work.

Ciao Joe

Luca

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

From: Joseph Zeglinski
Date: 25/04/2008 19.01.31
To: ap-gto@...
Subject: Re: [ap-gto] PEMPro AP: some more help needed!

Hi Ray,

Side line question about all this.
Is it possible to "download" the existing curve data - perhaps the AP
factory set table values, in order to preserve them for possible set back?

I would feel more comfortable if I had a text file that I could revert the
GTO back to, if I screw up somewhere, in all the PEC training, or want just
to get back to the original settings for comparison.

Thanks,
Joe







------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list
see http://groups.yahoo.com/group/ap-gtoYahoo! Groups Links



Re: PEMPro AP: some more help needed!

Luca <darknrg@...>
 

Thanks Ray.
Alas, my mount was one of the few with the GTOCP3 with the "crazy chip" (don
t remember the letter identifying it)therefore it was replaced by AP and
doesn't have the pre-recorded PE. So I had no data to preserve :-(((

Luca

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

From: Ray Gralak
Date: 25/04/2008 19.44.01
To: ap-gto@...
Subject: RE: [ap-gto] PEMPro AP: some more help needed!

Hi Luca/Joe/Larry,

Yes, this is the correct procedure to save the mount's loaded PE curve.

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of Luca
Sent: Friday, April 25, 2008 10:41 AM
To: ap-gto@...
Subject: Re: [ap-gto] PEMPro AP: some more help needed!

Hello Joe,
I'm not Ray, but I may have an answer: in PEMPro AP (the only
version I
have) you can read the curve in the mount from the PROGRAM
MOUNT tab, where
it says "Read PE Curve" giving you the option of reading it
from (A) the
Created PE Curve; (B) From Mount; (C) From File. If you
choose (B) PEMPro
will read the curve from the mount and display it in the
graph area. After
this is completed the option "To File" in the "Write PE
Curve" area will be
enabled and you'll be able to save your data in a file. After
pressing "To
File" the program will ask you which of the displayed curves
you want to
save to file; just choose the "PE from Mount or File" and
you're done.
I would wait for Ray's confirmation on this, but I'm 99% sure
it would work.

Ciao Joe

Luca

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

From: Joseph Zeglinski
Date: 25/04/2008 19.01.31
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Subject: Re: [ap-gto] PEMPro AP: some more help needed!

Hi Ray,

Side line question about all this.
Is it possible to "download" the existing curve data - perhaps the AP
factory set table values, in order to preserve them for
possible set back?

I would feel more comfortable if I had a text file that I
could revert the
GTO back to, if I screw up somewhere, in all the PEC
training, or want just
to get back to the original settings for comparison.

Thanks,
Joe











Latest version of PEMPro AP SE

Ray Gralak <rgr@...>
 

Hello everyone,

The version of PEMPro AP that Luca is using is rather old. If you are using
PEMPro AP please make sure you have v1.70 build 149 (click Help->About).

If needed you can download the latest version from here:

http://www.siriusimaging.com/PEMPro/PEMPro-APSE-1.70.149.exe

-Ray Gralak
Author of PEMPro


Re: PEMPro AP: some more help needed!

Ray Gralak <rgr@...>
 

Hi Luca/Joe/Larry,

Yes, this is the correct procedure to save the mount's loaded PE curve.

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of Luca
Sent: Friday, April 25, 2008 10:41 AM
To: ap-gto@...
Subject: Re: [ap-gto] PEMPro AP: some more help needed!

Hello Joe,
I'm not Ray, but I may have an answer: in PEMPro AP (the only
version I
have) you can read the curve in the mount from the PROGRAM
MOUNT tab, where
it says "Read PE Curve" giving you the option of reading it
from (A) the
Created PE Curve; (B) From Mount; (C) From File. If you
choose (B) PEMPro
will read the curve from the mount and display it in the
graph area. After
this is completed the option "To File" in the "Write PE
Curve" area will be
enabled and you'll be able to save your data in a file. After
pressing "To
File" the program will ask you which of the displayed curves
you want to
save to file; just choose the "PE from Mount or File" and
you're done.
I would wait for Ray's confirmation on this, but I'm 99% sure
it would work.

Ciao Joe

Luca

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

From: Joseph Zeglinski
Date: 25/04/2008 19.01.31
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Subject: Re: [ap-gto] PEMPro AP: some more help needed!

Hi Ray,

Side line question about all this.
Is it possible to "download" the existing curve data - perhaps the AP
factory set table values, in order to preserve them for
possible set back?

I would feel more comfortable if I had a text file that I
could revert the
GTO back to, if I screw up somewhere, in all the PEC
training, or want just
to get back to the original settings for comparison.

Thanks,
Joe