Date   

Re: Error in AP driver

Pierre Henrotay
 

Hi Ray,

This is Rev L. CP3 (this is a brand new Mach1).
In my latest tests, I used PulseGuide and only PulseGuide (1.30).

This is the exact sequence to show the value is not retained after
power cycle:
- set the longitude to W 6 50 via the keypad for location 1
- power cycle
- start PulseGuide and get Site Long: all fine
- set longitude via PulseGuide to E 5 50, then click "send to mount"
button
- observe that PulseGuide reads back the value correctly
- exit PulseGuide
- power cycle
- select location 1 via the keypad
- shown: W 6 50 ... too bad ...

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

Hi Pierre,

I am using Rev I of the firmware (CP3) and the value sent to the
mount IS
retained after a power cycle. Which Rev are you using?

Also, if there is a bug in the hand controller firmware, it may be
wrong
reading as well as writing. If I use PulseGuide and only Pulseguide
to read
and write the Longitude looks correct with Rev I controller
firmware.

Can you try a test using only PulseGuide to read/write and look at
the
serial log?

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Monday, December 17, 2007 8:45 AM
To: ap-gto@...
Subject: [ap-gto] Re: Error in AP driver

Hi Ray,

No: unfortunately, the value written by PulseGuide is _not_
retained
properly after a power cycle if the longitude is East.
Last test I did was to set the longitude to W 6 50 then change
the
longitude via PulseGuide to E 5 50, then click "send to mount"
button, then power cycle then select location 1 again on the
controller.
Then I inspected the longitude: back to W 6 50 - so the value was
sent but not accepted.

I'd appreciate to have AP to check what is going on: I am now
thinking that the AP controller returns an incorrect string for
east
longitude when the Gg command is issued.

Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Ray Gralak" <rgr@> wrote:

Hi Pierre,

So it seems that the problem might be fixed by changing the
keypad
firmware
to write in the range -180 to 180 instead of 0-360. I think
because
Pulseguide writes in the range -180 to 180 the value is
retained
properly
after a power cycle.

-Ray

-----Original Message-----
From: ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
[mailto:ap-gto@... <mailto:ap-gto%
40yahoogroups.com> ]
On Behalf Of phenrotay
Sent: Monday, December 17, 2007 6:12 AM
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Subject: [ap-gto] Re: Error in AP driver

Chuck,

as the AP protocol is extending the LX200, I read back the
LX200
description
(http://www.meade.com/support/LX200CommandSet.pdf
<http://www.meade.com/support/LX200CommandSet.pdf>
<http://www.meade.com/support/LX200CommandSet.pdf
<http://www.meade.com/support/LX200CommandSet.pdf> > )
This indicates the presence of the sign, and that East
longitudes
are
negative (so -180 to 180 is the expected range).
The trace from ASCOM - and the log from PulseGuide both show
a
value
near 360 (but wrong: 355*50 for E 5 50).
Pierre

--- In ap-gto@... <mailto:ap-gto%
40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@> wrote:

Okay, I guess the docs just left out the sign desination.

Thanks Ray

----- Original Message -----
From: Ray Gralak
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%
40yahoogroups.com>
Sent: Sunday, December 16, 2007 2:59 PM
Subject: RE: [ap-gto] Re: Error in AP driver


Hi Chuck,

Negative values work just fine in the test I just did.

-Ray







Re: Error in AP driver

Ray Gralak <rgr@...>
 

Hi Konstantin,

The value is being rejected by PulseGuide I think because the keypad wrote a
value over 180 degrees to the mount. The range is -180 to 180 in the LX200
protocol so I that is the range PulseGuide validates.

In any case if I am understanding the problem correctly the keypad firmware
is not writing the correct value when above 180 degrees anyway... or the
firmware is wrongly converting it.

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of Poschinger Konstantin v.
Sent: Monday, December 17, 2007 8:51 AM
To: ap-gto@...
Subject: Re: [ap-gto] Re: Error in AP driver

Hi Ray,

I wrote about this two years ago. I managed it till that time by
starting only from the keypad.

Konstantin

Hammerichstr. 5
22605 Hamburg
040/8805747
01711983476

Am 17.12.2007 um 16:10 schrieb Ray Gralak:

Hi Pierre,

So it seems that the problem might be fixed by changing the keypad
firmware
to write in the range -180 to 180 instead of 0-360. I think because
Pulseguide writes in the range -180 to 180 the value is retained
properly
after a power cycle.

-Ray

-----Original Message-----
From: ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
[mailto:ap-gto@... <mailto:ap-gto%40yahoogroups.com> ]
On Behalf Of phenrotay
Sent: Monday, December 17, 2007 6:12 AM
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Subject: [ap-gto] Re: Error in AP driver

Chuck,

as the AP protocol is extending the LX200, I read back the LX200
description
(http://www.meade.com/support/LX200CommandSet.pdf
<http://www.meade.com/support/LX200CommandSet.pdf>
<http://www.meade.com/support/LX200CommandSet.pdf
<http://www.meade.com/support/LX200CommandSet.pdf> > )
This indicates the presence of the sign, and that East longitudes
are
negative (so -180 to 180 is the expected range).
The trace from ASCOM - and the log from PulseGuide both
show a value
near 360 (but wrong: 355*50 for E 5 50).
Pierre

--- In ap-gto@... <mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@...> wrote:

Okay, I guess the docs just left out the sign desination.

Thanks Ray

----- Original Message -----
From: Ray Gralak
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%40yahoogroups.com>
Sent: Sunday, December 16, 2007 2:59 PM
Subject: RE: [ap-gto] Re: Error in AP driver


Hi Chuck,

Negative values work just fine in the test I just did.

-Ray










Re: Error in AP driver

Ray Gralak <rgr@...>
 

Hi Pierre,

I am using Rev I of the firmware (CP3) and the value sent to the mount IS
retained after a power cycle. Which Rev are you using?

Also, if there is a bug in the hand controller firmware, it may be wrong
reading as well as writing. If I use PulseGuide and only Pulseguide to read
and write the Longitude looks correct with Rev I controller firmware.

Can you try a test using only PulseGuide to read/write and look at the
serial log?

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Monday, December 17, 2007 8:45 AM
To: ap-gto@...
Subject: [ap-gto] Re: Error in AP driver

Hi Ray,

No: unfortunately, the value written by PulseGuide is _not_ retained
properly after a power cycle if the longitude is East.
Last test I did was to set the longitude to W 6 50 then change the
longitude via PulseGuide to E 5 50, then click "send to mount"
button, then power cycle then select location 1 again on the
controller.
Then I inspected the longitude: back to W 6 50 - so the value was
sent but not accepted.

I'd appreciate to have AP to check what is going on: I am now
thinking that the AP controller returns an incorrect string for east
longitude when the Gg command is issued.

Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Ray Gralak" <rgr@...> wrote:

Hi Pierre,

So it seems that the problem might be fixed by changing the keypad
firmware
to write in the range -180 to 180 instead of 0-360. I think because
Pulseguide writes in the range -180 to 180 the value is retained
properly
after a power cycle.

-Ray

-----Original Message-----
From: ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
[mailto:ap-gto@... <mailto:ap-gto%40yahoogroups.com> ]
On Behalf Of phenrotay
Sent: Monday, December 17, 2007 6:12 AM
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Subject: [ap-gto] Re: Error in AP driver

Chuck,

as the AP protocol is extending the LX200, I read back the LX200
description
(http://www.meade.com/support/LX200CommandSet.pdf
<http://www.meade.com/support/LX200CommandSet.pdf>
<http://www.meade.com/support/LX200CommandSet.pdf
<http://www.meade.com/support/LX200CommandSet.pdf> > )
This indicates the presence of the sign, and that East longitudes
are
negative (so -180 to 180 is the expected range).
The trace from ASCOM - and the log from PulseGuide both show a
value
near 360 (but wrong: 355*50 for E 5 50).
Pierre

--- In ap-gto@... <mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@> wrote:

Okay, I guess the docs just left out the sign desination.

Thanks Ray

----- Original Message -----
From: Ray Gralak
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%40yahoogroups.com>
Sent: Sunday, December 16, 2007 2:59 PM
Subject: RE: [ap-gto] Re: Error in AP driver


Hi Chuck,

Negative values work just fine in the test I just did.

-Ray







Re: Error in AP driver

Poschinger Konstantin v. <KPoschinger@...>
 

Hi Ray,

I wrote about this two years ago. I managed it till that time by
starting only from the keypad.

Konstantin


Hammerichstr. 5
22605 Hamburg
040/8805747
01711983476

Am 17.12.2007 um 16:10 schrieb Ray Gralak:

Hi Pierre,

So it seems that the problem might be fixed by changing the keypad
firmware
to write in the range -180 to 180 instead of 0-360. I think because
Pulseguide writes in the range -180 to 180 the value is retained
properly
after a power cycle.

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Monday, December 17, 2007 6:12 AM
To: ap-gto@...
Subject: [ap-gto] Re: Error in AP driver

Chuck,

as the AP protocol is extending the LX200, I read back the LX200
description (http://www.meade.com/support/LX200CommandSet.pdf
<http://www.meade.com/support/LX200CommandSet.pdf> )
This indicates the presence of the sign, and that East longitudes
are
negative (so -180 to 180 is the expected range).
The trace from ASCOM - and the log from PulseGuide both show a value
near 360 (but wrong: 355*50 for E 5 50).
Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@...> wrote:

Okay, I guess the docs just left out the sign desination.

Thanks Ray

----- Original Message -----
From: Ray Gralak
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Sent: Sunday, December 16, 2007 2:59 PM
Subject: RE: [ap-gto] Re: Error in AP driver


Hi Chuck,

Negative values work just fine in the test I just did.

-Ray





Re: Error in AP driver

Pierre Henrotay
 

Hi Ray,

No: unfortunately, the value written by PulseGuide is _not_ retained
properly after a power cycle if the longitude is East.
Last test I did was to set the longitude to W 6 50 then change the
longitude via PulseGuide to E 5 50, then click "send to mount"
button, then power cycle then select location 1 again on the
controller.
Then I inspected the longitude: back to W 6 50 - so the value was
sent but not accepted.

I'd appreciate to have AP to check what is going on: I am now
thinking that the AP controller returns an incorrect string for east
longitude when the Gg command is issued.

Pierre


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

Hi Pierre,

So it seems that the problem might be fixed by changing the keypad
firmware
to write in the range -180 to 180 instead of 0-360. I think because
Pulseguide writes in the range -180 to 180 the value is retained
properly
after a power cycle.

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Monday, December 17, 2007 6:12 AM
To: ap-gto@...
Subject: [ap-gto] Re: Error in AP driver

Chuck,

as the AP protocol is extending the LX200, I read back the LX200
description (http://www.meade.com/support/LX200CommandSet.pdf
<http://www.meade.com/support/LX200CommandSet.pdf> )
This indicates the presence of the sign, and that East longitudes
are
negative (so -180 to 180 is the expected range).
The trace from ASCOM - and the log from PulseGuide both show a
value
near 360 (but wrong: 355*50 for E 5 50).
Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@> wrote:

Okay, I guess the docs just left out the sign desination.

Thanks Ray

----- Original Message -----
From: Ray Gralak
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Sent: Sunday, December 16, 2007 2:59 PM
Subject: RE: [ap-gto] Re: Error in AP driver


Hi Chuck,

Negative values work just fine in the test I just did.

-Ray




Re: foam for cases

astrokattner
 

I purchased cases from Scopeguard (I think AP uses them as well).
They are constructed very well and I have been pleased with them.
Scopeguard uses Ethafoam in the cases which is like the foam used to
ship the mount. The Ethafoam works great. I had custom cases built
with custom cutouts for the ethafoam so I would not have to remove
the dovetail when transporting the mount. You will probably need a
case for each axis.

HTH
Ken


--- In ap-gto@..., "Dean S" <dean@...> wrote:

I am going to make a set of cases for my 1200 and a couple sets for
friends with 900's. My thought was to use the polyethylene foam that
they shipped with but only use 1 layer of it to save space. I will
not be shipping with it but just moving it in and out of my truck for
the occasional star party so it will not have rough handling

I got a sample of the grey firm foam like found in most equipment
cases but it seems very mushy/ soft and would compress a great deal
with the weight of the mount and I fear offer little support unless I
use several inches. The foam that it came with is just the opposite,
very firm but if AP ships with it, it must be good.

I will build the boxes using Baltic Birch plywood with a removable
lid and had thought of making it so that the interior where the mount
sits is exactly the same size as it shipped, but the box ID size
using 1 less piece of the shipping foam. The Dec assembly is not
that large so original size is not a big deal, but it would be nice
to reduce the size for the RA assembly mainly.

Any thoughts or opinions from what others have done?

Thanks
Dean




foam for cases

Dean S
 

I am going to make a set of cases for my 1200 and a couple sets for friends with 900's. My thought was to use the polyethylene foam that they shipped with but only use 1 layer of it to save space. I will not be shipping with it but just moving it in and out of my truck for the occasional star party so it will not have rough handling

I got a sample of the grey firm foam like found in most equipment cases but it seems very mushy/ soft and would compress a great deal with the weight of the mount and I fear offer little support unless I use several inches. The foam that it came with is just the opposite, very firm but if AP ships with it, it must be good.

I will build the boxes using Baltic Birch plywood with a removable lid and had thought of making it so that the interior where the mount sits is exactly the same size as it shipped, but the box ID size using 1 less piece of the shipping foam. The Dec assembly is not that large so original size is not a big deal, but it would be nice to reduce the size for the RA assembly mainly.

Any thoughts or opinions from what others have done?

Thanks
Dean


Re: Error in AP driver

Ray Gralak <rgr@...>
 

Hi Pierre,

So it seems that the problem might be fixed by changing the keypad firmware
to write in the range -180 to 180 instead of 0-360. I think because
Pulseguide writes in the range -180 to 180 the value is retained properly
after a power cycle.

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Monday, December 17, 2007 6:12 AM
To: ap-gto@...
Subject: [ap-gto] Re: Error in AP driver

Chuck,

as the AP protocol is extending the LX200, I read back the LX200
description (http://www.meade.com/support/LX200CommandSet.pdf
<http://www.meade.com/support/LX200CommandSet.pdf> )
This indicates the presence of the sign, and that East longitudes are
negative (so -180 to 180 is the expected range).
The trace from ASCOM - and the log from PulseGuide both show a value
near 360 (but wrong: 355*50 for E 5 50).
Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@...> wrote:

Okay, I guess the docs just left out the sign desination.

Thanks Ray

----- Original Message -----
From: Ray Gralak
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Sent: Sunday, December 16, 2007 2:59 PM
Subject: RE: [ap-gto] Re: Error in AP driver


Hi Chuck,

Negative values work just fine in the test I just did.

-Ray




Re: Error in AP driver

Pierre Henrotay
 

Chuck,

as the AP protocol is extending the LX200, I read back the LX200
description (http://www.meade.com/support/LX200CommandSet.pdf)
This indicates the presence of the sign, and that East longitudes are
negative (so -180 to 180 is the expected range).
The trace from ASCOM - and the log from PulseGuide both show a value
near 360 (but wrong: 355*50 for E 5 50).
Pierre

--- In ap-gto@..., "Chuck Faranda" <mail_lists2@...> wrote:

Okay, I guess the docs just left out the sign desination.

Thanks Ray

----- Original Message -----
From: Ray Gralak
To: ap-gto@...
Sent: Sunday, December 16, 2007 2:59 PM
Subject: RE: [ap-gto] Re: Error in AP driver


Hi Chuck,

Negative values work just fine in the test I just did.

-Ray


Re: Broken clutch knob

Mark Squicquero
 

The previous post warning about glue in the threads is right on. There is no way to prevent "gluing" the broken piece to the mount with this technique. This will only work with an exposed broken segment. You have to protect the threaded hole no matter what you do in this case. The best suggestion so far was to use a left handed drill of the appropriate size. You must also protect the threaded hole with a small piece of tubing while drilling so that "when" the bit wanders it won't destroy the threads for the new clutch screw that you're going to put in. Just get a piece of brass tubing or similar, cut a small piece and place it in the hole. Then use it as a drill guide. As was previously mentioned, the increasing "bite" of the drill as it penetrates (with left handed torque of course) will eventually back the screw out. Use cutting oil, low rpm, moderate pressure. Worst case scenario: you'll need an extractor if it doesn't back out by itself, but the threads will
still be intact.

Mark


Re: Broken clutch knob

observe_m13
 

Hi Pete,

I have good nes and good news. I took one of the knobs out of my 900
and then took teh stainless screw out of the knob. The black knob
appears to be aluminum and the screw has been threaded in to give a
solid access point for a hex key in order to tighten down teh knob.
Aluminum would strip far too easily. What remains inside your mount is
about 1/2 inch of threaded aluminum and, lo and behold, since the
stainless screw was in there, there has to be a threaded hole in the
center of it. I should have looked more carefully but I am betting
that the stainless screw is either 8-32 or 10-32 thread, not that it
matters much. What you want to do is get an easy-out for the aluminum
stub stuck inside the mount. You will have to probe with some small
bits or a toothpick and see how deep the hole already is. Measure down
to the lip of the piece that remains inside and then measure inside
the existing hole. If it is of sufficient an easy out to fit that hole
should work just fine. If the easy-out requires more depth or a larger
hole, just carefully drill it deeper/larger with the required bit. The
hole itself will ensure that the bit remains centered.

An alternative would be to get a small bolt with the same thread and
size as the stainless bolt is. Carefully thread it into the existing
hole until it stops, noting how deep you can put it in. If it goes in
1/4 inch or so INTO THE STUB, then back it out, mix up the tiniest bit
of epoxy, apply even less than the tiniest bit to the threads of the
bolt you just removed with a toothpick and thread it back into the
stub in the mount. Let it set up until the epoxy is hard as nails and
back out the stub using the bolt. When I say the tiniest bit of epoxy,
I mean just that and I can highly recommend JB Weld. The smallest
swipe or dab, just barely filling the threads of the bolt on about 1/4
or less of the bolt surface area that will be inside the stub. You
want to ensure beyond any doubt that this stuff doesn't contact any
part of the mount itself. Once it sticks and sets, it is done,
virtually forever.

Again, if you don't feel comfortable about doing any of this DON'T do
it. Give AP a call tomorrow and see what they recommend.

Rick

--- In ap-gto@..., "Peter Santangeli" <peter@...> wrote:


Indeed the problem is bad... that part I'm holding is supposed to be
at least 3/4 of an inch long. The rest is in the mount.

Pete

--- In ap-gto@..., "Rick K" <JunkMailGoesHere@> wrote:

I am totally confused. If this is the problem, toss it in the garbage
and order a new one from AP on Monday.

I thought you were talking about the mount having a problem with a
broken off threaded section in the mount itself. That is serious and
is what a picture of would be worth a 1000 words.

Rick.


--- In ap-gto@..., "Peter Santangeli" <peter@> wrote:


Maybe a picture is indeed worth 1000 words... Here is a shot of the
broken knob:

http://www.santangeli.net/knob.jpg

As you can see, the device is actually a hollow threaded
aluminum tube
with the knob part screwed into it. The walls of the tube are
not that
thick, but should take quite a bit of torque without breaking. All I
can assume is that the knob got banged longitudinally somehow,
and the
tube broke.

The rest of the tube (with the "outer" thread) is unfortunately
still
in the mount.

Pete


--- In ap-gto@..., Gregory Nottingham <gnpnotti@> wrote:

My experience using Eazy Outs on exhaust studs on cylinder heads
has
not been good. I know that the telescope situation is
different.
What is the diameter of screw? As long as you are sure that
screw
isn't cross-threaded, you should be alright but every-time I've
used
one, I have gone in with the assumption that I will have to take
the
head to a machine shop to drill out the stud and the broken,
hardened
steel Easy Out.
Good luck.
Greg
On Dec 15, 2007, at 2:01, Peter Santangeli wrote:


Good suggestion. I was thinking about something like this.

Pete

--- In ap-gto@..., kawasaki99@ wrote:

Hello Strong Man,
Local hardware store ought to sell an (easy-out)
which is a
sort of a left hand thread tap and the proper size pilot
drill
for the
easy-out. If it's only hand tight to ought to come out.
Have an
assistant hold a
vacuum cleaner hose close to broken screw while drilling the
pilot
hole to
capture any small chips. A small center drill or sharp prick
punch
may be necessary
to ensure the pilot drill puts the hole close to the true
center of
the
broken screw. Sounds like a lot but it's generally easy.



**************************************See AOL's top rated
recipes
(http://food.aol.com/top-rated-recipes?NCID=aoltop00030000000004)






[Non-text portions of this message have been removed]


Re: Error in AP driver

Ray Gralak <rgr@...>
 

Yes, PulseGuide. Sorry!

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Sunday, December 16, 2007 12:14 PM
To: ap-gto@...
Subject: [ap-gto] Re: Error in AP driver

Hi Ray,

reading back from PEMPro ? You mean PulseGuide, or ?

Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Ray Gralak" <rgr@...> wrote:

Hi Pierre,

Yes, PulseGuide validates the return value in the range -180 to
180, so that
is why you are seeing 0's.

Can you try changing Longitude from the hand controller, power
cycling, and
reading it back from PEMPro? Do not connect with the AP ASCOM
driver at any
time when doing this test in case it tries to change Lat/Long. You
can even
open PulseGuide's Log window to see what commands are being
exchanged.

-Ray

-----Original Message-----
From: ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
[mailto:ap-gto@... <mailto:ap-gto%40yahoogroups.com> ]
On Behalf Of phenrotay
Sent: Sunday, December 16, 2007 11:32 AM
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Subject: [ap-gto] Re: Error in AP driver

This would explain why I get a longitude set to blank (for E/W)
and
all 0s when I retrieve the site info in PulseGuide, or ?

Pierre
--- In ap-gto@... <mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Ray Gralak" <rgr@> wrote:

FWIW, in PulseGuide I use a range of -180 to +180 for longitude
(not 0-360).


I wonder if the keypad sets the range 0-360?

-Ray

-----Original Message-----
From: ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com>
[mailto:ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%
40yahoogroups.com> ]
On Behalf Of phenrotay
Sent: Sunday, December 16, 2007 10:46 AM
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%40yahoogroups.com>
Subject: [ap-gto] Re: Error in AP driver

Not a silly question at all.
Yes, I:
- set the correct value in the controller (it shows E 5 50)
for
location 1
- select location 1
- start ASCOM tracing then MaxIm
- connect to the telescope (using MaxIm) and show setup
display
- I click "Get..."
- the setup display shows E 4 10

Confusing: the string returned by the mount for Gg as shown
in
the
trace is +355*50:00 ... which is definitely wrong (360 - 355
50
00
gives indeed 4 10, not 5 50 !!)

Something wrong in the firmware itself ?

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%
40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Ajai Sehgal" <ajai@>
wrote:

Pierre,

Silly question: Did you click the "Get Lat/Long" button in
the
setup
dialog? Please start a trace just before you do and send it
to
me.
Also please tell me what appears in the dialog afterwards.
This
code
is very simple. The mount is reporting the CORRECT
information
from
your trace below +355*50:00 in AP's format really means E
005:50:00
in standard terms (they measure 360deg positive westward
from
the
prime meridian).

Here is how the driver works: After putting in the correct
LAT
and
LONG settings in the dialog initially, click APPLY. This
will
set
the values into the mount controller (you can also set them
into
the
controller by hand but BEFORE A GET make sure that the
controller
is
initialized and you have selected the correct location (I
suspect
that you had not done this when getting the bogus values).
After
that, clicking on GET LAT/LONG should correspond to the
correct
values

Ajai


--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "phenrotay"
<Pierre.Henrotay@>
wrote:

Hereafter an extract of the file; puzzling !
[14:25:00] Transmit(":Gt#")...
[14:25:00] ...done
[14:25:00] ReceiveTerminated("#")...
[14:25:01] ...received "+50*35:00#"
[14:25:01] Transmit(":Gg#")...
[14:25:01] ...done
[14:25:01] ReceiveTerminated("#")...
[14:25:01] ...received "+355*50:00#"

When looking at location #1, it says
E 005:50:00
N 50:35:00
This is 4.12 revision L


Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@>
wrote:

Look in the folder ..&#92;Program Files&#92;Common Files&#92;ASCOM
for 'TraceOn.vbs'. Double click it, select yes to the
msg,
run
the
test. Double click 'TraceOff.vbs' in
the same folder to stop the logging. The log file
should be
in
C:&#92;SerialTrace.txt.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%
40yahoogroups.com>
Sent: Sunday, December 16, 2007 7:08 AM
Subject: [ap-gto] Re: Error in AP driver


Sure, but how can this done ? I see no trace check box
in
the
setup
for the driver. I suppose there is a trick.

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@>
wrote:

I think a serial trace would identify what your mount
is
sending
when
queried for the longitude.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%
40yahoogroups.com>
Sent: Sunday, December 16, 2007 3:10 AM
Subject: [ap-gto] Fw: [SPAM] Fw: [ASCOM] Re: Error in
AP
driver


Hello,
I am the one who identified the glitch and posted on
ASCOM-
Talk.
If further information or tests are needed, do not
hesitate
to
contact me.
This is a Mach1 mount, 4.12 GTO keypad. Driver is
4.1.25.
Helper2.dll is dated 7-apr-2005, 45056 bytes.
I wonder what is the impact. Any idea ?

Regards,
Pierre















Re: Error in AP driver

Pierre Henrotay
 

Hi Ray,

reading back from PEMPro ? You mean PulseGuide, or ?

Pierre

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

Hi Pierre,

Yes, PulseGuide validates the return value in the range -180 to
180, so that
is why you are seeing 0's.

Can you try changing Longitude from the hand controller, power
cycling, and
reading it back from PEMPro? Do not connect with the AP ASCOM
driver at any
time when doing this test in case it tries to change Lat/Long. You
can even
open PulseGuide's Log window to see what commands are being
exchanged.

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Sunday, December 16, 2007 11:32 AM
To: ap-gto@...
Subject: [ap-gto] Re: Error in AP driver

This would explain why I get a longitude set to blank (for E/W)
and
all 0s when I retrieve the site info in PulseGuide, or ?

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Ray Gralak" <rgr@> wrote:

FWIW, in PulseGuide I use a range of -180 to +180 for longitude
(not 0-360).


I wonder if the keypad sets the range 0-360?

-Ray

-----Original Message-----
From: ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
[mailto:ap-gto@... <mailto:ap-gto%
40yahoogroups.com> ]
On Behalf Of phenrotay
Sent: Sunday, December 16, 2007 10:46 AM
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Subject: [ap-gto] Re: Error in AP driver

Not a silly question at all.
Yes, I:
- set the correct value in the controller (it shows E 5 50)
for
location 1
- select location 1
- start ASCOM tracing then MaxIm
- connect to the telescope (using MaxIm) and show setup
display
- I click "Get..."
- the setup display shows E 4 10

Confusing: the string returned by the mount for Gg as shown
in
the
trace is +355*50:00 ... which is definitely wrong (360 - 355
50
00
gives indeed 4 10, not 5 50 !!)

Something wrong in the firmware itself ?

Pierre
--- In ap-gto@... <mailto:ap-gto%
40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Ajai Sehgal" <ajai@>
wrote:

Pierre,

Silly question: Did you click the "Get Lat/Long" button in
the
setup
dialog? Please start a trace just before you do and send it
to
me.
Also please tell me what appears in the dialog afterwards.
This
code
is very simple. The mount is reporting the CORRECT
information
from
your trace below +355*50:00 in AP's format really means E
005:50:00
in standard terms (they measure 360deg positive westward
from
the
prime meridian).

Here is how the driver works: After putting in the correct
LAT
and
LONG settings in the dialog initially, click APPLY. This
will
set
the values into the mount controller (you can also set them
into
the
controller by hand but BEFORE A GET make sure that the
controller
is
initialized and you have selected the correct location (I
suspect
that you had not done this when getting the bogus values).
After
that, clicking on GET LAT/LONG should correspond to the
correct
values

Ajai


--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "phenrotay"
<Pierre.Henrotay@>
wrote:

Hereafter an extract of the file; puzzling !
[14:25:00] Transmit(":Gt#")...
[14:25:00] ...done
[14:25:00] ReceiveTerminated("#")...
[14:25:01] ...received "+50*35:00#"
[14:25:01] Transmit(":Gg#")...
[14:25:01] ...done
[14:25:01] ReceiveTerminated("#")...
[14:25:01] ...received "+355*50:00#"

When looking at location #1, it says
E 005:50:00
N 50:35:00
This is 4.12 revision L


Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@>
wrote:

Look in the folder ..&#92;Program Files&#92;Common Files&#92;ASCOM
for 'TraceOn.vbs'. Double click it, select yes to the
msg,
run
the
test. Double click 'TraceOff.vbs' in
the same folder to stop the logging. The log file
should be
in
C:&#92;SerialTrace.txt.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%
40yahoogroups.com>
Sent: Sunday, December 16, 2007 7:08 AM
Subject: [ap-gto] Re: Error in AP driver


Sure, but how can this done ? I see no trace check box
in
the
setup
for the driver. I suppose there is a trick.

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@>
wrote:

I think a serial trace would identify what your mount
is
sending
when
queried for the longitude.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%
40yahoogroups.com>
Sent: Sunday, December 16, 2007 3:10 AM
Subject: [ap-gto] Fw: [SPAM] Fw: [ASCOM] Re: Error in
AP
driver


Hello,
I am the one who identified the glitch and posted on
ASCOM-
Talk.
If further information or tests are needed, do not
hesitate
to
contact me.
This is a Mach1 mount, 4.12 GTO keypad. Driver is
4.1.25.
Helper2.dll is dated 7-apr-2005, 45056 bytes.
I wonder what is the impact. Any idea ?

Regards,
Pierre




[Non-text portions of this message have been removed]







Re: Error in AP driver

Ray Gralak <rgr@...>
 

Hi Pierre,

Yes, PulseGuide validates the return value in the range -180 to 180, so that
is why you are seeing 0's.

Can you try changing Longitude from the hand controller, power cycling, and
reading it back from PEMPro? Do not connect with the AP ASCOM driver at any
time when doing this test in case it tries to change Lat/Long. You can even
open PulseGuide's Log window to see what commands are being exchanged.

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Sunday, December 16, 2007 11:32 AM
To: ap-gto@...
Subject: [ap-gto] Re: Error in AP driver

This would explain why I get a longitude set to blank (for E/W) and
all 0s when I retrieve the site info in PulseGuide, or ?

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Ray Gralak" <rgr@...> wrote:

FWIW, in PulseGuide I use a range of -180 to +180 for longitude
(not 0-360).


I wonder if the keypad sets the range 0-360?

-Ray

-----Original Message-----
From: ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
[mailto:ap-gto@... <mailto:ap-gto%40yahoogroups.com> ]
On Behalf Of phenrotay
Sent: Sunday, December 16, 2007 10:46 AM
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Subject: [ap-gto] Re: Error in AP driver

Not a silly question at all.
Yes, I:
- set the correct value in the controller (it shows E 5 50) for
location 1
- select location 1
- start ASCOM tracing then MaxIm
- connect to the telescope (using MaxIm) and show setup display
- I click "Get..."
- the setup display shows E 4 10

Confusing: the string returned by the mount for Gg as shown in
the
trace is +355*50:00 ... which is definitely wrong (360 - 355 50
00
gives indeed 4 10, not 5 50 !!)

Something wrong in the firmware itself ?

Pierre
--- In ap-gto@... <mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Ajai Sehgal" <ajai@> wrote:

Pierre,

Silly question: Did you click the "Get Lat/Long" button in the
setup
dialog? Please start a trace just before you do and send it to
me.
Also please tell me what appears in the dialog afterwards. This
code
is very simple. The mount is reporting the CORRECT information
from
your trace below +355*50:00 in AP's format really means E
005:50:00
in standard terms (they measure 360deg positive westward from
the
prime meridian).

Here is how the driver works: After putting in the correct LAT
and
LONG settings in the dialog initially, click APPLY. This will
set
the values into the mount controller (you can also set them
into
the
controller by hand but BEFORE A GET make sure that the
controller
is
initialized and you have selected the correct location (I
suspect
that you had not done this when getting the bogus values).
After
that, clicking on GET LAT/LONG should correspond to the correct
values

Ajai


--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "phenrotay"
<Pierre.Henrotay@>
wrote:

Hereafter an extract of the file; puzzling !
[14:25:00] Transmit(":Gt#")...
[14:25:00] ...done
[14:25:00] ReceiveTerminated("#")...
[14:25:01] ...received "+50*35:00#"
[14:25:01] Transmit(":Gg#")...
[14:25:01] ...done
[14:25:01] ReceiveTerminated("#")...
[14:25:01] ...received "+355*50:00#"

When looking at location #1, it says
E 005:50:00
N 50:35:00
This is 4.12 revision L


Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@>
wrote:

Look in the folder ..&#92;Program Files&#92;Common Files&#92;ASCOM
for 'TraceOn.vbs'. Double click it, select yes to the msg,
run
the
test. Double click 'TraceOff.vbs' in
the same folder to stop the logging. The log file should be
in
C:&#92;SerialTrace.txt.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%
40yahoogroups.com>
Sent: Sunday, December 16, 2007 7:08 AM
Subject: [ap-gto] Re: Error in AP driver


Sure, but how can this done ? I see no trace check box in
the
setup
for the driver. I suppose there is a trick.

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@>
wrote:

I think a serial trace would identify what your mount is
sending
when
queried for the longitude.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%
40yahoogroups.com>
Sent: Sunday, December 16, 2007 3:10 AM
Subject: [ap-gto] Fw: [SPAM] Fw: [ASCOM] Re: Error in AP
driver


Hello,
I am the one who identified the glitch and posted on
ASCOM-
Talk.
If further information or tests are needed, do not
hesitate
to
contact me.
This is a Mach1 mount, 4.12 GTO keypad. Driver is 4.1.25.
Helper2.dll is dated 7-apr-2005, 45056 bytes.
I wonder what is the impact. Any idea ?

Regards,
Pierre












Re: Error in AP driver

Chuck Faranda <mail_lists2@...>
 

Okay, I guess the docs just left out the sign desination.

Thanks Ray

----- Original Message -----
From: Ray Gralak To: ap-gto@... Sent: Sunday, December 16, 2007 2:59 PM
Subject: RE: [ap-gto] Re: Error in AP driver


Hi Chuck,

Negative values work just fine in the test I just did.

-Ray


Re: Error in AP driver

Ray Gralak <rgr@...>
 

Hi Chuck,

Negative values work just fine in the test I just did.

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of Chuck Faranda
Sent: Sunday, December 16, 2007 11:25 AM
To: ap-gto@...
Subject: Re: [ap-gto] Re: Error in AP driver

Hi Ray,

Odd, this is contrary to what the docs imply:
Command: :Sg DDD*MM# or :Sg DDD*MM:SS#

It does not indicate a 'sign' in front of the degrees like
other commands do. So, you are sending the 'SL' with strings
like -80*25:33 or 120*13:20, yes?

Chuck
----- Original Message -----
From: Ray Gralak
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Sent: Sunday, December 16, 2007 2:08 PM
Subject: RE: [ap-gto] Re: Error in AP driver

FWIW, in PulseGuide I use a range of -180 to +180 for
longitude (not 0-360).

I wonder if the keypad sets the range 0-360?

-Ray

-----Original Message-----
From: ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
[mailto:ap-gto@... <mailto:ap-gto%40yahoogroups.com> ]
On Behalf Of phenrotay
Sent: Sunday, December 16, 2007 10:46 AM
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Subject: [ap-gto] Re: Error in AP driver

Not a silly question at all.
Yes, I:
- set the correct value in the controller (it shows E 5 50) for
location 1
- select location 1
- start ASCOM tracing then MaxIm
- connect to the telescope (using MaxIm) and show setup display
- I click "Get..."
- the setup display shows E 4 10

Confusing: the string returned by the mount for Gg as shown in the
trace is +355*50:00 ... which is definitely wrong (360 - 355 50 00
gives indeed 4 10, not 5 50 !!)

Something wrong in the firmware itself ?

Pierre
--- In ap-gto@... <mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Ajai Sehgal" <ajai@...> wrote:

Pierre,

Silly question: Did you click the "Get Lat/Long" button in the
setup
dialog? Please start a trace just before you do and send
it to me.
Also please tell me what appears in the dialog afterwards. This
code
is very simple. The mount is reporting the CORRECT information
from
your trace below +355*50:00 in AP's format really means E
005:50:00
in standard terms (they measure 360deg positive westward from the
prime meridian).

Here is how the driver works: After putting in the
correct LAT and
LONG settings in the dialog initially, click APPLY. This will set
the values into the mount controller (you can also set them into
the
controller by hand but BEFORE A GET make sure that the controller
is
initialized and you have selected the correct location (I suspect
that you had not done this when getting the bogus values). After
that, clicking on GET LAT/LONG should correspond to the correct
values

Ajai


--- In ap-gto@... <mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "phenrotay" <Pierre.Henrotay@>
wrote:

Hereafter an extract of the file; puzzling !
[14:25:00] Transmit(":Gt#")...
[14:25:00] ...done
[14:25:00] ReceiveTerminated("#")...
[14:25:01] ...received "+50*35:00#"
[14:25:01] Transmit(":Gg#")...
[14:25:01] ...done
[14:25:01] ReceiveTerminated("#")...
[14:25:01] ...received "+355*50:00#"

When looking at location #1, it says
E 005:50:00
N 50:35:00
This is 4.12 revision L


Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda" <mail_lists2@>
wrote:

Look in the folder ..&#92;Program Files&#92;Common Files&#92;ASCOM
for 'TraceOn.vbs'. Double click it, select yes to the msg, run
the
test. Double click 'TraceOff.vbs' in
the same folder to stop the logging. The log file
should be in
C:&#92;SerialTrace.txt.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%40yahoogroups.com>
Sent: Sunday, December 16, 2007 7:08 AM
Subject: [ap-gto] Re: Error in AP driver


Sure, but how can this done ? I see no trace check box in the
setup
for the driver. I suppose there is a trick.

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com>
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda" <mail_lists2@>
wrote:

I think a serial trace would identify what your mount is
sending
when
queried for the longitude.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@...
<mailto:ap-gto%40yahoogroups.com> <mailto:ap-gto%40yahoogroups.com>
Sent: Sunday, December 16, 2007 3:10 AM
Subject: [ap-gto] Fw: [SPAM] Fw: [ASCOM] Re: Error in AP
driver


Hello,
I am the one who identified the glitch and posted on ASCOM-
Talk.
If further information or tests are needed, do not hesitate
to
contact me.
This is a Mach1 mount, 4.12 GTO keypad. Driver is 4.1.25.
Helper2.dll is dated 7-apr-2005, 45056 bytes.
I wonder what is the impact. Any idea ?

Regards,
Pierre














Re: Error in AP driver

Pierre Henrotay
 

This would explain why I get a longitude set to blank (for E/W) and
all 0s when I retrieve the site info in PulseGuide, or ?

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

FWIW, in PulseGuide I use a range of -180 to +180 for longitude
(not 0-360).


I wonder if the keypad sets the range 0-360?

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Sunday, December 16, 2007 10:46 AM
To: ap-gto@...
Subject: [ap-gto] Re: Error in AP driver

Not a silly question at all.
Yes, I:
- set the correct value in the controller (it shows E 5 50) for
location 1
- select location 1
- start ASCOM tracing then MaxIm
- connect to the telescope (using MaxIm) and show setup display
- I click "Get..."
- the setup display shows E 4 10

Confusing: the string returned by the mount for Gg as shown in
the
trace is +355*50:00 ... which is definitely wrong (360 - 355 50
00
gives indeed 4 10, not 5 50 !!)

Something wrong in the firmware itself ?

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Ajai Sehgal" <ajai@> wrote:

Pierre,

Silly question: Did you click the "Get Lat/Long" button in the
setup
dialog? Please start a trace just before you do and send it to
me.
Also please tell me what appears in the dialog afterwards. This
code
is very simple. The mount is reporting the CORRECT information
from
your trace below +355*50:00 in AP's format really means E
005:50:00
in standard terms (they measure 360deg positive westward from
the
prime meridian).

Here is how the driver works: After putting in the correct LAT
and
LONG settings in the dialog initially, click APPLY. This will
set
the values into the mount controller (you can also set them
into
the
controller by hand but BEFORE A GET make sure that the
controller
is
initialized and you have selected the correct location (I
suspect
that you had not done this when getting the bogus values).
After
that, clicking on GET LAT/LONG should correspond to the correct
values

Ajai


--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "phenrotay"
<Pierre.Henrotay@>
wrote:

Hereafter an extract of the file; puzzling !
[14:25:00] Transmit(":Gt#")...
[14:25:00] ...done
[14:25:00] ReceiveTerminated("#")...
[14:25:01] ...received "+50*35:00#"
[14:25:01] Transmit(":Gg#")...
[14:25:01] ...done
[14:25:01] ReceiveTerminated("#")...
[14:25:01] ...received "+355*50:00#"

When looking at location #1, it says
E 005:50:00
N 50:35:00
This is 4.12 revision L


Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@>
wrote:

Look in the folder ..&#92;Program Files&#92;Common Files&#92;ASCOM
for 'TraceOn.vbs'. Double click it, select yes to the msg,
run
the
test. Double click 'TraceOff.vbs' in
the same folder to stop the logging. The log file should be
in
C:&#92;SerialTrace.txt.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@... <mailto:ap-gto%
40yahoogroups.com>
Sent: Sunday, December 16, 2007 7:08 AM
Subject: [ap-gto] Re: Error in AP driver


Sure, but how can this done ? I see no trace check box in
the
setup
for the driver. I suppose there is a trick.

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
<mail_lists2@>
wrote:

I think a serial trace would identify what your mount is
sending
when
queried for the longitude.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@... <mailto:ap-gto%
40yahoogroups.com>
Sent: Sunday, December 16, 2007 3:10 AM
Subject: [ap-gto] Fw: [SPAM] Fw: [ASCOM] Re: Error in AP
driver


Hello,
I am the one who identified the glitch and posted on
ASCOM-
Talk.
If further information or tests are needed, do not
hesitate
to
contact me.
This is a Mach1 mount, 4.12 GTO keypad. Driver is 4.1.25.
Helper2.dll is dated 7-apr-2005, 45056 bytes.
I wonder what is the impact. Any idea ?

Regards,
Pierre




[Non-text portions of this message have been removed]




Re: Error in AP driver

Chuck Faranda <mail_lists2@...>
 

Meant "Sg"

----- Original Message -----
From: Chuck Faranda
To: ap-gto@...
Sent: Sunday, December 16, 2007 2:25 PM
Subject: Re: [ap-gto] Re: Error in AP driver


Hi Ray,

Odd, this is contrary to what the docs imply:
Command: :Sg DDD*MM# or :Sg DDD*MM:SS#

It does not indicate a 'sign' in front of the degrees like other commands do. So, you are sending the 'SL' with strings like -80*25:33 or 120*13:20, yes?

Chuck


Re: Error in AP driver

Chuck Faranda <mail_lists2@...>
 

Hi Ray,

Odd, this is contrary to what the docs imply:
Command: :Sg DDD*MM# or :Sg DDD*MM:SS#

It does not indicate a 'sign' in front of the degrees like other commands do. So, you are sending the 'SL' with strings like -80*25:33 or 120*13:20, yes?

Chuck

----- Original Message -----
From: Ray Gralak
To: ap-gto@...
Sent: Sunday, December 16, 2007 2:08 PM
Subject: RE: [ap-gto] Re: Error in AP driver


FWIW, in PulseGuide I use a range of -180 to +180 for longitude (not 0-360).

I wonder if the keypad sets the range 0-360?

-Ray

> -----Original Message-----
> From: ap-gto@... [mailto:ap-gto@...]
> On Behalf Of phenrotay
> Sent: Sunday, December 16, 2007 10:46 AM
> To: ap-gto@...
> Subject: [ap-gto] Re: Error in AP driver
>
> Not a silly question at all.
> Yes, I:
> - set the correct value in the controller (it shows E 5 50) for
> location 1
> - select location 1
> - start ASCOM tracing then MaxIm
> - connect to the telescope (using MaxIm) and show setup display
> - I click "Get..."
> - the setup display shows E 4 10
>
> Confusing: the string returned by the mount for Gg as shown in the
> trace is +355*50:00 ... which is definitely wrong (360 - 355 50 00
> gives indeed 4 10, not 5 50 !!)
>
> Something wrong in the firmware itself ?
>
> Pierre
> --- In ap-gto@...
> <mailto:ap-gto%40yahoogroups.com> , "Ajai Sehgal" <ajai@...> wrote:
> >
> > Pierre,
> >
> > Silly question: Did you click the "Get Lat/Long" button in the
> setup
> > dialog? Please start a trace just before you do and send it to me.
> > Also please tell me what appears in the dialog afterwards. This
> code
> > is very simple. The mount is reporting the CORRECT information
> from
> > your trace below +355*50:00 in AP's format really means E 005:50:00
> > in standard terms (they measure 360deg positive westward from the
> > prime meridian).
> >
> > Here is how the driver works: After putting in the correct LAT and
> > LONG settings in the dialog initially, click APPLY. This will set
> > the values into the mount controller (you can also set them into
> the
> > controller by hand but BEFORE A GET make sure that the controller
> is
> > initialized and you have selected the correct location (I suspect
> > that you had not done this when getting the bogus values). After
> > that, clicking on GET LAT/LONG should correspond to the correct
> values
> >
> > Ajai
> >
> >
> > --- In ap-gto@...
> <mailto:ap-gto%40yahoogroups.com> , "phenrotay" <Pierre.Henrotay@>
> > wrote:
> > >
> > > Hereafter an extract of the file; puzzling !
> > > [14:25:00] Transmit(":Gt#")...
> > > [14:25:00] ...done
> > > [14:25:00] ReceiveTerminated("#")...
> > > [14:25:01] ...received "+50*35:00#"
> > > [14:25:01] Transmit(":Gg#")...
> > > [14:25:01] ...done
> > > [14:25:01] ReceiveTerminated("#")...
> > > [14:25:01] ...received "+355*50:00#"
> > >
> > > When looking at location #1, it says
> > > E 005:50:00
> > > N 50:35:00
> > > This is 4.12 revision L
> > >
> > >
> > > Pierre
> > >
> > > --- In ap-gto@...
> <mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda" <mail_lists2@>
> > > wrote:
> > > >
> > > > Look in the folder ..&#92;Program Files&#92;Common Files&#92;ASCOM
> > > for 'TraceOn.vbs'. Double click it, select yes to the msg, run
> the
> > > test. Double click 'TraceOff.vbs' in
> > > > the same folder to stop the logging. The log file should be in
> > > C:&#92;SerialTrace.txt.
> > > >
> > > > Chuck
> > > >
> > > > ----- Original Message -----
> > > > From: phenrotay
> > > > To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
> > > > Sent: Sunday, December 16, 2007 7:08 AM
> > > > Subject: [ap-gto] Re: Error in AP driver
> > > >
> > > >
> > > > Sure, but how can this done ? I see no trace check box in the
> > > setup
> > > > for the driver. I suppose there is a trick.
> > > >
> > > > Pierre
> > > > --- In ap-gto@...
> <mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda" <mail_lists2@>
> > > > wrote:
> > > > >
> > > > > I think a serial trace would identify what your mount is
> > > sending
> > > > when
> > > > > queried for the longitude.
> > > > >
> > > > > Chuck
> > > > >
> > > > > ----- Original Message -----
> > > > > From: phenrotay
> > > > > To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
> > > > > Sent: Sunday, December 16, 2007 3:10 AM
> > > > > Subject: [ap-gto] Fw: [SPAM] Fw: [ASCOM] Re: Error in AP
> > driver
> > > > >
> > > > >
> > > > > Hello,
> > > > > I am the one who identified the glitch and posted on ASCOM-
> > Talk.
> > > > > If further information or tests are needed, do not hesitate
> to
> > > > > contact me.
> > > > > This is a Mach1 mount, 4.12 GTO keypad. Driver is 4.1.25.
> > > > > Helper2.dll is dated 7-apr-2005, 45056 bytes.
> > > > > I wonder what is the impact. Any idea ?
> > > > >
> > > > > Regards,
> > > > > Pierre
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
>
>
>
>


Re: Error in AP driver

Ray Gralak <rgr@...>
 

FWIW, in PulseGuide I use a range of -180 to +180 for longitude (not 0-360).


I wonder if the keypad sets the range 0-360?

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Sunday, December 16, 2007 10:46 AM
To: ap-gto@...
Subject: [ap-gto] Re: Error in AP driver

Not a silly question at all.
Yes, I:
- set the correct value in the controller (it shows E 5 50) for
location 1
- select location 1
- start ASCOM tracing then MaxIm
- connect to the telescope (using MaxIm) and show setup display
- I click "Get..."
- the setup display shows E 4 10

Confusing: the string returned by the mount for Gg as shown in the
trace is +355*50:00 ... which is definitely wrong (360 - 355 50 00
gives indeed 4 10, not 5 50 !!)

Something wrong in the firmware itself ?

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Ajai Sehgal" <ajai@...> wrote:

Pierre,

Silly question: Did you click the "Get Lat/Long" button in the
setup
dialog? Please start a trace just before you do and send it to me.
Also please tell me what appears in the dialog afterwards. This
code
is very simple. The mount is reporting the CORRECT information
from
your trace below +355*50:00 in AP's format really means E 005:50:00
in standard terms (they measure 360deg positive westward from the
prime meridian).

Here is how the driver works: After putting in the correct LAT and
LONG settings in the dialog initially, click APPLY. This will set
the values into the mount controller (you can also set them into
the
controller by hand but BEFORE A GET make sure that the controller
is
initialized and you have selected the correct location (I suspect
that you had not done this when getting the bogus values). After
that, clicking on GET LAT/LONG should correspond to the correct
values

Ajai


--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "phenrotay" <Pierre.Henrotay@>
wrote:

Hereafter an extract of the file; puzzling !
[14:25:00] Transmit(":Gt#")...
[14:25:00] ...done
[14:25:00] ReceiveTerminated("#")...
[14:25:01] ...received "+50*35:00#"
[14:25:01] Transmit(":Gg#")...
[14:25:01] ...done
[14:25:01] ReceiveTerminated("#")...
[14:25:01] ...received "+355*50:00#"

When looking at location #1, it says
E 005:50:00
N 50:35:00
This is 4.12 revision L


Pierre

--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda" <mail_lists2@>
wrote:

Look in the folder ..&#92;Program Files&#92;Common Files&#92;ASCOM
for 'TraceOn.vbs'. Double click it, select yes to the msg, run
the
test. Double click 'TraceOff.vbs' in
the same folder to stop the logging. The log file should be in
C:&#92;SerialTrace.txt.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Sent: Sunday, December 16, 2007 7:08 AM
Subject: [ap-gto] Re: Error in AP driver


Sure, but how can this done ? I see no trace check box in the
setup
for the driver. I suppose there is a trick.

Pierre
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda" <mail_lists2@>
wrote:

I think a serial trace would identify what your mount is
sending
when
queried for the longitude.

Chuck

----- Original Message -----
From: phenrotay
To: ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Sent: Sunday, December 16, 2007 3:10 AM
Subject: [ap-gto] Fw: [SPAM] Fw: [ASCOM] Re: Error in AP
driver


Hello,
I am the one who identified the glitch and posted on ASCOM-
Talk.
If further information or tests are needed, do not hesitate
to
contact me.
This is a Mach1 mount, 4.12 GTO keypad. Driver is 4.1.25.
Helper2.dll is dated 7-apr-2005, 45056 bytes.
I wonder what is the impact. Any idea ?

Regards,
Pierre