USB Drivers (WinXP,7,8,10 Compatible) ASCOM UPB Focuser Driver v1.6 (Jun/20) ASCOM Observing Conditions Driver v1.5 (Jun/20) ASCOM Powerbox Switch Driver v2.2 (Jun/20) Indigo Astronomy. INDI Open Astronomy Instrumentation. ASCOM.DSLR - ASCOM driver for dslr cameras (Canon, Nikon, Pentax, Sony) - DSLR, Mirrorless & General-Purpose Digital Camera DSO Imaging - Cloudy Nights ASCOM.DSLR - ASCOM driver for dslr cameras (Canon, Nikon, Pentax, Sony) Started by FearL0rd, May 15 2020 10:43 PM astrophotography CMOS ccd dslr.

This web page describes the ASCOM driver for Astro-Physics telescope mounts.

Quick Start - For Experienced ASCOM Users::

Follow these steps to Install the Astro-Physics ASCOM V2 Driver

Go to the ASCOM website and determine the required updates to Windows and DotNet for the latest ASCOM Platform Updates.
Update your Windows OS and DotNet as recommended on the ASCOM site.
Return to the ASCOM site and update your platform to the latest version including all platform updates.
Once the ASCOM Platform is fully updated, review and possibly download the documentation and instructional videos if needed using the Quick Links section below.
Install the latest ASCOM V2 Driver in the Quick Links table.
Run the setup screen either directly through the installer or through Start => Programs => Astro-Physics => ASCOM Driver
In the ASCOM Telescope Chooser of your ASCOM client program, select 'Astro-Physics GTO V2 Mount'

The ASCOM Platform and the Astro-Physics ASCOM V2 Driver will provide you with more comprehensive and fail safe control of your Astro-Physics GTO mount. We encourage you to use this interface for PC-based control of your mount!

Quick Links:

Details	Date	Link
Latest Released Version: 5.30.10 (recommended for all A-P GTO Mounts: supports GTOCP1, GTOCP2, GTOCP3, GTOCP4, and GTOCP5 control boxes). NOTE: This version (or later) is required for APCC v1.7.x or later. IMPORTANT: if you are upgrading from version v5.08.01 or earlier you must uninstall the earlier driver first from Control Panel. IMPORTANT: if you later downgrade from v5.08.03 or later driver you MUST uninstall the newer driver first from Control Panel.	April 7, 2020	AstroPhysics V2 Setup v5.30.10 NOTE: Version 5.20.07 and later have been tested in Europe and work when regional settings have ',' and '.' swapped compared to USA settings. If you are upgrading from version v5.08.01 or earlier you must uninstall the earlier driver first from Control Panel. This is required because the location of the driver and supporting applications has changed so as not to potentially interfere with other ASCOM drivers.
Please use one of these versions if you are in Europe and have ',' and '.' swapped in your regional settings, compared to the USA settings).	(none)	AstroPhysics V2 Setup v5.30.10 AstroPhysics V2 Setup v5.21.01 AstroPhysics V2 Setup v5.20.09 AstroPhysics V2 Setup v5.09.09 AstroPhysics V2 Setup v5.09.07
Online Web Help	March 18, 2020	AstroPhysics V2 ASCOM Driver Documentation (v5.30.xx)
ASCOM Conformance validation file:	March 18, 2020	AstroPhysicsV2.Telescope.Validation.txt (For v5.30.09)
PDF Documentation	March 18, 2020	AstroPhysics V2 ASCOM Driver PDF (v5.30.xx)
Amazon Kindle format (.mobi)	March 18, 2020	APV2_Driver_5.30.xx.mobi
Apple ePub format	March 18, 2020	APV2_Driver_5.30.xx.epub
Video Tutorials at Screencast.com	June 2010	Video Tutorials at Screencast.com

Park 4 and Park 5

Park 4 and Park 5 have been added to APCC and the latest version of the driver. Park 4 parks the scope on the opposite side of the pier facing south to the horizon. Park 5 parks the scope on the opposite side of the pier facing north to the horizon.

This was done to overcome a potential Park 1 issue. The issue would occur if the mount is allowed to track into a counterweight up position (i.e., telescope lower than counterweights) before initializing from the Park 1 position. Because the mount tracks west when powered there is only a minute or two before it will move into that counterweight up position, so it is critical to promptly initialize the mount.

The need to promptly initialize is because a 'Sync' command is sent which always assumes the mount is in a counterweight-down position. If the mount has tracked into the counterweight-up position when the Sync occurs the mount controller will think the RA Axis is 180 degrees off from the current position so the mount will appear to be lost and dive under the mount when commanded to go to any sky target. It is not actually lost, it was just incorrectly initialized.
Note that while you can still use Park 1, do so at your own risk. We think that Park 4/5 instead of Park 1 is a superior solution. Park 4 and Park 5 have the advantages of Park 1 (e.g. scope is level) but none of the disadvantages.

Here is a comparison of Park 1 to Park 4 for the Northern hemisphere:

For Those Requiring (or wanting) a Bit More Information about ASCOM:

NOTE: Links to third party sites were current at the time of webpage publication, but are not under the control of Astro-Physics.

ASCOM Standards for Astronomy - The ASCOM Initiative

What is ASCOM?

ASCOM (AStronomy Common Object Model) is a go-between to allow different software packages to talk to different pieces of astronomical equipment. The ASCOM platform provides a common language for all the software, and then each individual driver translates that common language into the specific command laguage needed to make the equipment do what we want it to do.

The ASCOM initiative began in 1999 as new mounts and CCD cameras, each with their own unique control systems came on the market. Bob Denny of DC3-Dreams and others realized the complexity of developing mount and camera control software that could be used with a wide variety of instruments. The task of software developers to keep up with new mounts, cameras, focusers, etc. as they came on the market, or to stay abreast of revisions to the code of existing equipment was an enormous (or more correctly: insurmountable) task. So, the ASCOM Initiative was born to establish, develop and promote a driver-client architecture just as the computer industry had done earlier with printers, cameras and other peripherals. For even more information, check the following link: About ASCOM.

Why should I use ASCOM and the Astro-Physics ASCOM V2 Driver?
The ASCOM platform and the ASCOM V2 AP driver are not required to run PulseGuide, and they are certainly not required for control of the mount with the Astro-Physics GTO Keypad. However, the platform and driver are required for PEMPro, ACP (by DC3 Dreams), and other programs, and are extremely useful for anyone wishing to control their mount from an external Windows computer. Most advanced planetarium and telescope control software packages have an option to use the ASCOM platform, or else they require it outright. (Note that these options are referred to as 'telescope' control, but the telescope is just along for the ride. It is the mount that is being controlled.) We recommend that you select the ASCOM interface if it is an option in your software. The ASCOM option will be called the Telescope API (Application Programming Interface) This API will then allow you to use the Astro-Physics V2 Driver. The ASCOM Platform and the AP V2 driver will provide you with more comprehensive and fail-safe control of your mount.

The Astro-Physics V2 driver has been developed specifically for Astro-Physics by Ray Gralak. Unlike the earlier driver, this V2 driver is now fully owned and supported by Astro-Physics. It has been through rigorous testing and is being treated as an on-going project. We thank Ajai Sehgal for the first drive

Ascom Driver