Date   

Re: Hand controller is stuck on AP Ver 4.19.3 screen

steven ho
 

The red wire is disconnected from the post in the plug, I assume that must be re-soldered.  I am a HAM and know how to solder.


Thank you!


steve hoffman



From: ap-gto@... on behalf of chris1011@... [ap-gto]
Sent: Monday, April 3, 2017 12:30 PM
To: ap-gto@...
Subject: Re: [ap-gto] Hand controller is stuck on AP Ver 4.19.3 screen
 
 

No, you did not lose your database. You have lost connection on the plug to the keypad or internally inside the keypad and that means a lost communication between keypad and mount servo. The pins are probably slightly corroded and are not making good connection. You can start by unplugging the cable and running the plug in and out of the mating plug on the CP3, which might rub off some of the corrosion. You can try using fine sandpaper on the exposed pins on the connector plug. If that's not enough, you may have to go inside the keypad (take the back off) and unplug the cable from that end. use fine sandpaper on those pins. Once you get communication, put some connector grease on the pins. This will prevent future corrosion - it seals out the oxygen from the air.

Rolando





-----Original Message-----
From: stevenhoffman53@... [ap-gto]
To: ap-gto
Sent: Sun, Apr 2, 2017 3:11 pm
Subject: [ap-gto] Hand controller is stuck on AP Ver 4.19.3 screen



Can anyone help?

Did I cream my database?

It worked last time about 2 months ago.

Thanks 
Steve Hoffman



Re: Hand controller is stuck on AP Ver 4.19.3 screen

Don Anderson
 

Good quality electrical contact cleaner
 
Don Anderson



From: "chris1011@... [ap-gto]"
To: ap-gto@...
Sent: Monday, April 3, 2017 11:24 AM
Subject: Re: [ap-gto] Hand controller is stuck on AP Ver 4.19.3 screen

 
Ok, ink eraser.

Rolando



-----Original Message-----
From: 'Joseph Zeglinski' J.Zeglinski@... [ap-gto]
To: ap-gto
Sent: Mon, Apr 3, 2017 12:06 pm
Subject: Re: [ap-gto] Hand controller is stuck on AP Ver 4.19.3 screen



Rolando,
 
... Sandpaper on gold pins? Shouldn’t you recommend using a  more friendly, less damaging,  “ink eraser” instead ? I assume they still make those, along with lead pencils :-)
 
Joe





Re: Hand controller is stuck on AP Ver 4.19.3 screen

Roland Christen
 

Ok, ink eraser.

Rolando



-----Original Message-----
From: 'Joseph Zeglinski' J.Zeglinski@... [ap-gto]
To: ap-gto
Sent: Mon, Apr 3, 2017 12:06 pm
Subject: Re: [ap-gto] Hand controller is stuck on AP Ver 4.19.3 screen



Rolando,
 
... Sandpaper on gold pins? Shouldn’t you recommend using a  more friendly, less damaging,  “ink eraser” instead ? I assume they still make those, along with lead pencils :-)
 
Joe



Re: Hand controller is stuck on AP Ver 4.19.3 screen

steven ho
 

Don't worry Joe I have been using a Ruby Red eraser for years.


steve hoffman



From: ap-gto@... on behalf of 'Joseph Zeglinski' J.Zeglinski@... [ap-gto]
Sent: Monday, April 3, 2017 1:05 PM
To: ap-gto@...
Subject: Re: [ap-gto] Hand controller is stuck on AP Ver 4.19.3 screen
 
 

Rolando,
 
... Sandpaper on gold pins? Shouldn’t you recommend using a  more friendly, less damaging,  “ink eraser” instead ? I assume they still make those, along with lead pencils :-)
 
Joe


Re: Hand controller is stuck on AP Ver 4.19.3 screen

Joe Zeglinski
 

Rolando,
 
... Sandpaper on gold pins? Shouldn’t you recommend using a  more friendly, less damaging,  “ink eraser” instead ? I assume they still make those, along with lead pencils :-)
 
Joe


Re: Hand controller is stuck on AP Ver 4.19.3 screen

steven ho
 

I did replace the battery a couple months ago. 


Thank you!


steve hoffman



From: ap-gto@... on behalf of chris1011@... [ap-gto]
Sent: Monday, April 3, 2017 12:30 PM
To: ap-gto@...
Subject: Re: [ap-gto] Hand controller is stuck on AP Ver 4.19.3 screen
 
 

No, you did not lose your database. You have lost connection on the plug to the keypad or internally inside the keypad and that means a lost communication between keypad and mount servo. The pins are probably slightly corroded and are not making good connection. You can start by unplugging the cable and running the plug in and out of the mating plug on the CP3, which might rub off some of the corrosion. You can try using fine sandpaper on the exposed pins on the connector plug. If that's not enough, you may have to go inside the keypad (take the back off) and unplug the cable from that end. use fine sandpaper on those pins. Once you get communication, put some connector grease on the pins. This will prevent future corrosion - it seals out the oxygen from the air.

Rolando





-----Original Message-----
From: stevenhoffman53@... [ap-gto]
To: ap-gto
Sent: Sun, Apr 2, 2017 3:11 pm
Subject: [ap-gto] Hand controller is stuck on AP Ver 4.19.3 screen



Can anyone help?

Did I cream my database?

It worked last time about 2 months ago.

Thanks 
Steve Hoffman



Re: Hand controller is stuck on AP Ver 4.19.3 screen

Roland Christen
 

No, you did not lose your database. You have lost connection on the plug to the keypad or internally inside the keypad and that means a lost communication between keypad and mount servo. The pins are probably slightly corroded and are not making good connection. You can start by unplugging the cable and running the plug in and out of the mating plug on the CP3, which might rub off some of the corrosion. You can try using fine sandpaper on the exposed pins on the connector plug. If that's not enough, you may have to go inside the keypad (take the back off) and unplug the cable from that end. use fine sandpaper on those pins. Once you get communication, put some connector grease on the pins. This will prevent future corrosion - it seals out the oxygen from the air.

Rolando





-----Original Message-----
From: stevenhoffman53@... [ap-gto]
To: ap-gto
Sent: Sun, Apr 2, 2017 3:11 pm
Subject: [ap-gto] Hand controller is stuck on AP Ver 4.19.3 screen



Can anyone help?

Did I cream my database?

It worked last time about 2 months ago.

Thanks 
Steve Hoffman



Re: Hand controller is stuck on AP Ver 4.19.3 screen

Suresh Mohan
 

Ps the hand controller is virtually indestructible , don't worry 
Suresh


On 03-Apr-2017, at 8:48 AM, Suresh Mohan Neelmegh <drsureshmohan@...> wrote:

Yes I can try , first there is a method described in the website ie connecting to the sky etc , if that fails try re installing again , if that fails open the hand controller and clean the pins where the coiled cable connects , be sure not to loose those small washers under those screws when u fix back . For me none of the above worked and I changed the coiled cable and update happens like a charm and works fine 
Suresh



On 03-Apr-2017, at 1:41 AM, stevenhoffman53@... [ap-gto] <ap-gto@...> wrote:

 

Can anyone help?


Did I cream my database?


It worked last time about 2 months ago.


Thanks 

Steve Hoffman


Re: Shortening the height of G11 tripod

Dean S
 

Also look at the parallax piers.  Have decent amount of adjustments for level.  Can order any height. 

Dean



On Apr 2, 2017, at 11:10 PM, Fred Lusen fl.lusen@... [ap-gto] <ap-gto@...> wrote:

John,

Another option would be to look for a pier like the old Mountain Instruments MI-8P.  The pier is 30" high and is 8" diameter 1/8" wall thickness steel.  You could then have it cut down to a height that is acceptable to you.  I am in the process of doing that myself.

Fred

-----Original Message-----
From: jshutz@... [ap-gto] <ap-gto@...>
To: ap-gto <ap-gto@...>
Sent: Sun, Apr 2, 2017 4:25 pm
Subject: Re: [ap-gto] Shortening the height of G11 tripod

 
Even if I had a 31" tall tripod, I would only realize 3" off the total height, which would be then around 50". No problem either way setting up my 106 refractor, it's the big 11"EdgeHD with the ST80 guide scope on top that presents the problem.  I thought about this later and came to the conclusion why proceed solely because of the EdgeHD when I know I'll rarely use it compared to the 106.  For one reason or another, mostly weather, I don't have as many clear and moonless nights as I expected and when I do, my first interest is deep sky imaging.  I bought the EdgeHD thinking I'll dabble with planetary imaging, but soon realized I got way ahead of myself when I've got a long way to go learning deep sky imaging and processing.  

For me, imaging time is a premium and collecting data helps the overall learning process, buying the EdgeHD was more emotion than logic from a timing standpoint.  Thanks for the input anyway, appreciate the information.

John   


Re: Hand controller is stuck on AP Ver 4.19.3 screen

Suresh Mohan
 

Yes I can try , first there is a method described in the website ie connecting to the sky etc , if that fails try re installing again , if that fails open the hand controller and clean the pins where the coiled cable connects , be sure not to loose those small washers under those screws when u fix back . For me none of the above worked and I changed the coiled cable and update happens like a charm and works fine 
Suresh



On 03-Apr-2017, at 1:41 AM, stevenhoffman53@... [ap-gto] <ap-gto@...> wrote:

 

Can anyone help?


Did I cream my database?


It worked last time about 2 months ago.


Thanks 

Steve Hoffman


Re: Shortening the height of G11 tripod

fl.lusen
 

John,

Another option would be to look for a pier like the old Mountain Instruments MI-8P.  The pier is 30" high and is 8" diameter 1/8" wall thickness steel.  You could then have it cut down to a height that is acceptable to you.  I am in the process of doing that myself.

Fred

-----Original Message-----
From: jshutz@... [ap-gto]
To: ap-gto
Sent: Sun, Apr 2, 2017 4:25 pm
Subject: Re: [ap-gto] Shortening the height of G11 tripod

 
Even if I had a 31" tall tripod, I would only realize 3" off the total height, which would be then around 50". No problem either way setting up my 106 refractor, it's the big 11"EdgeHD with the ST80 guide scope on top that presents the problem.  I thought about this later and came to the conclusion why proceed solely because of the EdgeHD when I know I'll rarely use it compared to the 106.  For one reason or another, mostly weather, I don't have as many clear and moonless nights as I expected and when I do, my first interest is deep sky imaging.  I bought the EdgeHD thinking I'll dabble with planetary imaging, but soon realized I got way ahead of myself when I've got a long way to go learning deep sky imaging and processing.  

For me, imaging time is a premium and collecting data helps the overall learning process, buying the EdgeHD was more emotion than logic from a timing standpoint.  Thanks for the input anyway, appreciate the information.

John   


Re: AP portable pier vs ATS portable pier

Wayne Hixson
 

It took several months to get my ATS pier, but it's very nice. 




On Sunday, April 2, 2017, 7:28 PM, JASillasen@... [ap-gto] wrote:

 

If you're serious about an ATS Portable Pier - Rubber feet, Clear coat and all, start budgeting for it.
They are built to order and take weeks to months to get.  Weeks at minimum with a deposit with order - not the full purchase price, if memory serves  I could be wrong about that but you will wait some piece of time for it.  Not like an APO of course but you can call Daleen to get a rough idea of how far their order backlog is.
It could be 14-30 days or more depending on how many orders are ahead of yours.

John Sillasen


Re: AP portable pier vs ATS portable pier

John A. Sillasen
 

If you're serious about an ATS Portable Pier - Rubber feet, Clear coat and all, start budgeting for it.
They are built to order and take weeks to months to get.  Weeks at minimum with a deposit with order - not the full purchase price, if memory serves  I could be wrong about that but you will wait some piece of time for it.  Not like an APO of course but you can call Daleen to get a rough idea of how far their order backlog is.
It could be 14-30 days or more depending on how many orders are ahead of yours.

John Sillasen


Re: Shortening the height of G11 tripod

John Shutz
 

Even if I had a 31" tall tripod, I would only realize 3" off the total height, which would be then around 50". No problem either way setting up my 106 refractor, it's the big 11"EdgeHD with the ST80 guide scope on top that presents the problem.  I thought about this later and came to the conclusion why proceed solely because of the EdgeHD when I know I'll rarely use it compared to the 106.  For one reason or another, mostly weather, I don't have as many clear and moonless nights as I expected and when I do, my first interest is deep sky imaging.  I bought the EdgeHD thinking I'll dabble with planetary imaging, but soon realized I got way ahead of myself when I've got a long way to go learning deep sky imaging and processing.  

For me, imaging time is a premium and collecting data helps the overall learning process, buying the EdgeHD was more emotion than logic from a timing standpoint.  Thanks for the input anyway, appreciate the information.

John   


Re: Shortening the height of G11 tripod

fl.lusen
 

John,

I had a similar delemma with my setup.  When I got my AP1100 my setup wound up being to high.  My setup includes a TEC-140, a 60 or 70mm guide scope on top plus the usual accumulation of accessories.  What I did was acquire a Meade field tripod, not the Giant one.  Measurement to the top of the tripod with feet retracted is 30.750".  With the interface I made, measurement from the top of the tripod to the top of the AP adapter for the 1100 is an additional 2.750".  So total is 33.500".  Once everything is mounted I am at a comfortable height.  No more step stools.

You should be able to pick up an older Mead field tripod for somewhere around $100.00.

Fred

-----Original Message-----
From: jshutz@... [ap-gto]
To: ap-gto
Sent: Sun, Apr 2, 2017 4:41 am
Subject: Re: [ap-gto] Shortening the height of G11 tripod

 
I must be doing something wrong here, why is it each message or response is repeated constantly?

Anyway, Dean and Chris gave me some food for thought so I'll take a look at the measurements and go from there.  At this point I'm not as committed to this idea, so I'll look into other options.  Thank you.

John 


Hand controller is stuck on AP Ver 4.19.3 screen

steven ho
 

Can anyone help?


Did I cream my database?


It worked last time about 2 months ago.


Thanks 

Steve Hoffman


Chip Revisions

Mike C
 



I have a "V" chip in one of my GTOCP3 and a "V1" in another. For an AP1200 with APCC, are any of these chips essentially identical or are there pressing reasons to upgrade them to V2?


Thanks,
Mike in Alaska


Re: AP portable pier vs ATS portable pier

cford81@...
 

Hi Hemant - my pleasure. Yes I was surprised when George told me to swap the metal for rubber pads, but as soon as I did the egg shaped stars I was getting at 10+ minutes exposures went away.

I will likely sell that Pier shortly.

Chris Ford


From: "Hemant Hariyani hemanthariyani@... [ap-gto]"
To: ap-gto@...
Sent: Monday, March 27, 2017 11:00:25 PM
Subject: Re: [ap-gto] AP portable pier vs ATS portable pier

 

Hello Chris,

Thanks a lot for sharing your experience. I would have never imagined something like rubber pads making that sort of a difference. Certainly something to keep in mind. ATS would be a dream pier. I will need to see if I can budget for it. If you are putting your ATS on astromart or something let me know, Buying used may be an option to consider.

Thanks again for your help.

Regards
Hemant


On Sun, Mar 26, 2017 at 8:16 PM, cford81@... [ap-gto] <ap-gto@...> wrote:
 

I used a portable 10" ATS pier for a while with my AP1600GTO before moving to a permanent ATS pier in my observatory. I also have used the AP Pier in the past. (My portable 10" ATS Pier I will sell shortly)

The big difference as you observe is that the ATS Pier can be leveled much more easily as each of the legs is adjustable over a greater range. It is certainly quite transportable but it is very solid and robust as well. It is also quicker to setup as you don't need to assemble the legs and turnbuckles, you just swing out the legs and secure them. Once assembled you could probably anchor a ship to an ATS pier and it would not move. In general for extreme stability at long focal lengths I found the ATS pier a more robust portable solution compared to the AP pier. (Which is certainly adequate for most uses) I remember once when doing long focal length work observing a slight shift as the mount shifted weight distribution because the metal pads were sliding on my patio slightly. When I changed the pads from metal to the hard rubber pads the problem went away. That is an option (I believe) you have with the ATS pier you don't with the AP pier. In general, I think the ATS pier is worth the additional expense.

Chris




From: "Hemant Hariyani hemanthariyani@... [ap-gto]" <ap-gto@...>
To: ap-gto@...
Sent: Sunday, March 26, 2017 12:57:12 PM
Subject: [ap-gto] AP portable pier vs ATS portable pier


 


Hello all,

I am new to the group and this is my first post. I am also considering purchasing an AP 1600 and this will be my first AP product. I have heard a lot of good things and am looking forward to getting one myself. George at Astrophysics was extremely helpful in clarifying my questions regarding the mount and the AP customer service is the single biggest reason why I am opting for AP over other mounts.

I do know that an ATS portable pier would probably be the best portable pier that I can get for the mount but it is considerably more expensive than the AP pier. I was wondering if I could get some help comparing these two options? My setup would spend a lot of time in my backyard observatory with occasional trips to a dark site and long focal length astrophotography is what the mount would primarily be used for.

Does ATS offer any more stability than AP pier does for the max load capacity of the mount?

I understand that leveling the AP pier can be a problem? Can this be solved by providing some sort of a base/platform or modification? Concrete leveling blocks etc?

What about the ease of setup? How difficult is it to transport and setup an AP pier?

If AP solves the problem and provides just as much stability, I would rather go for it but at the same time, I would hate to buy something and then be left wanting more.

I will appreciate any help I can get here.

Regards
Hemant






Older versions of the AP V2 ASCOM Driver that are still available

Ray Gralak
 

In case anyone ever wants to rollback to an earlier version of the ASCOM
driver, here are the links of available older versions (version is in the
filename). Eventually we will put this up on a web page.

V5.09.09 - 2017-Mar-15 Release - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.09.09.exe (Latest
version)

- IMPROVEMENT - Allow for mount responses with extended precision.
- BUG FIX - when connected via APCC, get ALT/AZ from APCC so that if a
pointing model is being used the corrected ALT/AZ coordinates will be
displayed by the driver.
- BUG FIX - Time Sync response from APCC was handled as having failed even
if it was successful.

V5.09.08 - 2017-Jan-31 Release - Ray Gralak
-------------------------------------------------------------------
- BUG FIX - Park status was not always reported correctly.

V5.09.07 - 2017-Jan-23 Release - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.09.07.exe

- BUG FIX - if APCC sequence numbers get out of sync, a the response to a
possibly different command could be wrongly get used. Fixed by clearing the
response string when the sequence number is incorrect, so the response
cannot be used. Also, cleared the internal send/receive buffers to empty all
older sequence number responses. The following commands should then have the
correct sequence number.

V5.09.06 - 2017-Jan-19 Release - Ray Gralak
-------------------------------------------------------------------
- IMPROVEMENT - the Time Zone offset in the user interface now reflects the
generally accepted time zone polarity instead of the value returned from the
mount.

V5.09.05 - 2017-Jan-01 Release - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.09.05.exe

- BUG FIX - Longitudes less than 10 degrees would not match correctly in
Site info group.

V5.09.04 - 2016-Nov-12 Release - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.09.04.exe

- BUG FIX - Updated use of old ASCOM DriverHelper/DriverHelper2.Util to use
the newer ASCOM.Utilities.Util. The legacy version was not updating the Time
Zone correctly on a time change.
- BUG FIX - Prevent Time Zone from being updated when "keep Time Synced to
PC" is not enabled.

V5.09.03 - 2016-Nov-03 Beta - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.09.03.exe

- BUG FIX - Fixed a case missed in 5.09.02 where a time zone less than -12
was logged as an error.

V5.09.02 - 2016-Oct-31 Beta - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.09.02.exe

- IMPROVEMENT - the controller type is now shown in the main window (slight
user interface changes).
- IMPROVEMENT - If the controller is a GTOCP4 then hide the backlash setting
controls, since backlash is not used.
- IMPROVEMENT - When connected to APCC, the "keep time synced" feature is
now delegated to APCC. If APCC has its own "keep time sync" feature enabled,
it will override the same setting in the driver. If APCC has "keep time
synced" disabled then the driver will be able to override APCC and enable
"keep time sync" until the next time that APCC is run.
- BUG FIX - Time Zones less than -12 were not being handled correctly.
- BUG FIX - Getting ASCOM DeclinationRate no longer throws an exception when
tracking is disabled.
- BUG FIX - AP1100 was missing from mount types.
- BUG FIX - Fixed several ASCOM Conformance issues when running driver
through APCC.

- EXPERIMENTAL - When used with APCC 1.5.0.15 and later, the driver will now
use a different COM port for the user and administrator accounts, allowing
two instances of the driver to connect simultaneously to APCC. This will
allow a mix of applications running under the user account and "as
administrator" to connect to the mount through APCC.

V5.09.01 - 2016-July-19 Release - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.09.01.exe

- BUG FIX - GetAllValues was pulling entries from the old AP.INI .file
instead of
Settings.apdb (this is a fix for proper operation with APCC).

V5.09.00 - 2016-June-05 Release - Ray Gralak
-------------------------------------------------------------------
- IMPROVEMENT - Improved robustness of the driver starting APCC and
autoconfiguring the COM port.
- IMPROVEMENT - Improved robustness of the driver opening the correct APCC
virtual port.
- BUG FIX - Site latitude/longitude was not matching the mount if leading
zeros were not used. The driver now auto formats the latitude and longitude
with leading zeros if needed.
- BUG FIX - Under certain circumstances when parking from a counterweight up
position the driver was not able to stop the initial slew to a counterweight
down position, resulting in a potential equipment collision.
- BUG FIX - Force Meridian Delay to 0 before unparking (Rev S or later).

V5.08.09 - 2016-May-22 Release - Ray Gralak
-------------------------------------------------------------------
- BUG FIX - Throw error immediately if COM port does not exist.

V5.08.08 - 2016-April-24 Release - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.08.08.exe
- BUG FIX - Site Latitude/Longitude were not always being sent to the
mount when initializing through the driver.

V5.08.07 - 2016-April-07 Release - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.08.07.exe

- BUG FIX - Completely reworked site Latitude/Longitude Save/Restore
- BUG FIX - ASCOM RightAscensionRate and DeclinationRate were not being
enabled for GTOCP4
- BUG FIX - Show Virtual Hand box by default was not working correctly
- BUG FIX - Fixed a few minor ASCOM conformance issues
- IMPORTANT NOTE: this Build was checked and passes all ASCOM Conformance
tests with no Issues or Errors.

V5.08.06 - 2016-April-02 Beta - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.08.06.exe

- BUG FIX - Setting the Meridian limits in the user interface was not
working.
- BUG FIX - Time synchronization was not working.

V5.08.05 - 2016-February-06 Beta - Ray Gralak
-------------------------------------------------------------------
- BUG FIX - RA/DEC Bookmarks were not being displayed if no previous
bookmarks were set in the AP.INI when moving settings to the new database
settings storage.
- BUG FIX - In the setup window the site settings values could get out of
sync with the database if values were changed but not saved. The driver now
will now not allow the settings window to close until site settings have
been saved or canceled.
- The driver defaults have been changed to now show the driver when an
application connects.

V5.08.04 - 2016-January-18 Beta - Ray Gralak
-------------------------------------------------------------------
- BUG FIX - GTOCP4 mount type was not defined properly and this ultimately
caused an Error 380 in the setup window.

V5.08.03 - 2016-January-17 Beta - Ray Gralak
-------------------------------------------------------------------
- BUG FIX - in the driver setup window, when entering a decimal site
latitude or longitude value, if the decimal value had all zeros (e,g
"28.00") the minutes and seconds fields would not get filled in. Also a
carriage return was not being accepted to force the conversion from decimal
to hours, minutes, and seconds.

V5.08.02 - 2015-December-29 Beta - Ray Gralak
-------------------------------------------------------------------
- Installer - Changed installation location to a sub-directory under
Telescope (e.g. "C:&#92;Program Files&#92;Common
Files&#92;ASCOM&#92;Telescope&#92;Astro-Physics")
- Digitally sign executables and installer for greater security.

V5.08.01 - 2015-December-22 Beta - Ray Gralak
-------------------------------------------------------------------
- Changed order of text ion a few controls to Latitude/Longitude instead of
Longitude/latitude.

V5.08.00 - 2015-November-23 Beta - Ray Gralak
-------------------------------------------------------------------
- BIG CHANGE -> Settings now saved to local shared (with APCC) database
file (Settings.apdb) instead of AP.INI. Old settings will be automatically
copied to the new database ("settings.apdb") the first time the driver runs.
- Site configuration now uses a single drop down list box for site names.
- Sites are now common between APCC and the driver.
- RA/Dec and Alt/Az Bookmarks are now saved and shared with APCC.
- Eliminated "Send Longitude/Latitude to Mount" buttons because this can
cause the mount to be unexpectedly re-oriented.
- IMPROVEMENT - Added Site name to Virtual Hand box window. It will be
highlighted if the site's lat/long coordinates do not match the mount's.
Clicking the site name will open the driver page up to view the difference.
- BUG FIX - Longitude/Latitude can no longer be changed after the mount has
been initialized. If set from the ASCOM driver the changes will take effect
the next full initialization.
- BUG FIX - retical brightness was not being saved.
- BUG FIX - Some settings were saved multiple times needlessly.

V5.07.02 - 2015-October-31 Release - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.07.02.exe

- BUG FIX - Safe Slewing did not operate correctly always when parking the
mount.
- Added option to not show the Park 1 warning any more.

V5.07.01 - 2015-August-30 Beta - Ray Gralak
-------------------------------------------------------------------
- BUG FIX - When decimal and comma are swapped because of regional settings
the driver was sometimes passing improperly formatted commands to APCC.

V5.07.00 - 2015-August-08 Beta - Ray Gralak
-------------------------------------------------------------------
- BUG FIX - After a slew completes set to Sidereal so driver does not set
tracking rate to custom rates. This was causing the driver to send custom
rates to APCC by accident.

V5.06.05 - 2015-April-25 Release - Ray Gralak
-------------------------------------------------------------------

http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.06.05.exe

- Replaced "Allow connect when mount not present" with a timeout value in
seconds. The new field is in the Advanced page of the driver's Initial Setup
dialog window. A value of "0" is an infinite timeout. Values from 1-600
seconds are also accepted. When a timeout occurs during an ASCOM Client's
connect attempt control is returned to the ASCOM client application.
Previously, if the "Allow connect when mount not present" was enabled,
control might not ever be returned to the driver if the mount is not
connected.

- Added a new variable "SafeSlewRaDec" that can be used in AP.INI. The
default if it is not present is that Safe Slews are enabled
(SafeSlewRaDec=1). To disable safe slews set SafeSlewRaDec=0 in AP.INI.

- On connecting to the mount the driver will now query the mount type and if
a fork mount only do raw RA/Dec slews (no safety slews even if
"SafeSlewRaDec=0" in AP.INI.

- Updated Windows version checking (in top of log files) to properly display
the Windows version through Windows 10

V5.06.04 - 2015-March-25 Release - Ray Gralak
-------------------------------------------------------------------
- Added a variable to enable old button down behavior found in 5.05.16 and
earlier drivers, which while being more responsive might not register button
up or down events when using remote desktop-like software..

This option is off by default. Add this line to AP.INI to enable it:

UseOldButtonBehavior=1

- Improved "Allow connection when mount not present". If not enabled and the
COM port not present or mount does not respond the driver will report
failure to connect. If present the driver keeps trying to connect.

V5.06.03 - 2015-March-13 Release - Ray Gralak
-------------------------------------------------------------------
- BUG FIX - Tracking sometimes stopped when connected in 05.06.02.
- ENHANCEMENT - ASCOM driver call to DoesRefraction call now reflects APCC's
refraction enabled checkbox.

V5.06.02 - 2015-January-16 Release - Ray Gralak
-------------------------------------------------------------------
- BUG FIX - Throw exception immediately if COM Port not available

V5.06.01 - 2014-December-30 Release - Ray Gralak
-------------------------------------------------------------------
- BUG FIX - Custom RA/Dec rates was always being set after a slew completed.

V5.06.00 - 2014-October-05 Release - Ray Gralak
-------------------------------------------------------------------
- Validate range of custom rate to -99.9999x to 99.9999x sidereal.
- Adjusted Park 4 location.

V5.05.41 - 2014-September-27 BETA - Ray Gralak
-------------------------------------------------------------------
http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.05.41.exe

- Prevent use of Tracking via PulseGuide if mount has a GTOCP3 controller.
- Stop popping up unpark dialog whenever user clicks "Don't Unpark" when
mount is uninitialized.

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma


New version of the ASCOM driver v5.09.09 is available

Ray Gralak
 

A new version of the ASCOM driver is available that should fix the
never-ending park problem (Howard has told me feedback was good from
testers). This version has a couple other minor fixes, including matching up
the Alt/Az values with APCC in the upcoming APCC v1.5.0.21 release.

As usual with releases, this version has been checked with the ASCOM
Conformance checker utility.

http://www.gralak.com/apdriver

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma