Re: Error in AP driver

Pierre Henrotay

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 ?

--- In ap-gto@..., "Ajai Sehgal" <ajai@...> wrote:


Silly question: Did you click the "Get Lat/Long" button in the
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
is very simple. The mount is reporting the CORRECT information
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
controller by hand but BEFORE A GET make sure that the controller
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


--- In ap-gto@..., "phenrotay" <Pierre.Henrotay@>

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


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

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


----- Original Message -----
From: phenrotay
To: ap-gto@...
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
for the driver. I suppose there is a trick.

--- In ap-gto@..., "Chuck Faranda" <mail_lists2@>
> I think a serial trace would identify what your mount is
> queried for the longitude.
> Chuck
> ----- Original Message -----
> From: phenrotay
> To: ap-gto@...
> Sent: Sunday, December 16, 2007 3:10 AM
> Subject: [ap-gto] Fw: [SPAM] Fw: [ASCOM] Re: Error in AP
> Hello,
> I am the one who identified the glitch and posted on ASCOM-
> If further information or tests are needed, do not hesitate
> 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]

Join to automatically receive all group messages.