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
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.
--- In ap-gto@..., "Ray Gralak" <rgr@...> wrote:
So it seems that the problem might be fixed by changing the keypad
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
after a power cycle.
From: ap-gto@... [mailto:ap-gto@...]
On Behalf Of phenrotay
Sent: Monday, December 17, 2007 6:12 AM
Subject: [ap-gto] Re: Error in AP driver
as the AP protocol is extending the LX200, I read back the LX200
This indicates the presence of the sign, and that East longitudes
negative (so -180 to 180 is the expected range).
The trace from ASCOM - and the log from PulseGuide both show a
near 360 (but wrong: 355*50 for E 5 50).
--- In ap-gto@...
<mailto:ap-gto%40yahoogroups.com> , "Chuck Faranda"
Okay, I guess the docs just left out the sign desination.
----- 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
Negative values work just fine in the test I just did.