Frequently Asked Questions — ASCOM Alpaca and Classic ASCOM COM

NOTE: Alpaca is 100% independent of Windows. Nowhere in the Alpaca ecosystem is Windows (or COM) needed. Please look over About Alpaca and ASCOM if you haven't yet.

Where can I learn about ASCOM Alpaca vs Classic ASCOM COM?
See the About ASCOM section. This is a highly recommended first step.
Why Can't Astronomy Programs Just Compensate For My Device's Problem?
See the Correcting for Problems (also in the menu on the left).
How can I get support for my ASCOM compatible device or application?
See the Support page for details.
What's the difference between a Classic ASCOM DLL driver and an EXE driver?
See "Two Types of COM Drivers" in ASCOM-COM Connectivity in the About Ascom section.

Frequently Asked Questions - Alpaca Cross-Platform and Internet

What is Alpaca?
The answer in context is given in the About ASCOM section here. Take just a bit of time to understand our mission and how Alpaca takes it into the future.
Will Alpaca change or break my existing Windows ASCOM-compatible astronomy applications?
No. Windows ASCOM programs will remain compatible with no changes whatsoever. However, with the release of ASCOM Platform 6.5 and its new Alpaca-aware Chooser, your unmodified Windows ASCOM programs will be able to use devices and their Alpaca drivers on other platforms as they become available in the future. For example, you will be able to use a self-contained WiFi-connected focuser running on an Arduino or other embedded controller, again with no modifications to your Windows programs.
Will Alpaca change or break my existing ASCOM-compatible devices and their drivers or control programs?
No. Windows Classic ASCOM drivers will remain compatible with no changes whatever. However, if you install ASCOM Remote, an add-on middleware package, your unmodified Windows devices and their drivers will become accessible from from Alpaca-compatible astronomy programs on other platforms such as iOS, Android, Mac, and Linux as become available in the future. For example, you will be able to control your unmodified Windows-connected telescope mount and driver from an Alpaca-enabled iOS astronomy program.
Will the ASCOM Platform be changed by Alpaca? Will the tools go away or change?
No. The Windows ASCOM Platform will continue as it is. The beauty of Alpaca is that the expansion of the ASCOM-COM ecosystem is provided by the ASCOM Remote middleware, a layered add-on that provides transparent access to the Alpaca-extended environment from the existing Windows ASCOM environment, with no changes needed to any Windows programs or drivers.
When will Alpaca-compatible devices and programs be available?
It's a chicken-and-egg situation. We have the eggs and a few new chickens, now we need more chickens. The astronomy software and device suppliers that use the other platforms will incorporate Alpaca to gain access to and from the Windows ASCOM environment. Other than using the Alpaca-aware ASCOM Chooser on Windows and optionally installation and configuration of ASCOM Remote, nothing needs to change on the Windows side, however the non-Windows devices will need to add Alpaca interfaces, and non-windows astronomy programs will need to add the ability to use Alpaca to control devices. This should make life easy for mobile astronomy programs because Alpaca makes unmodified Windows-connected devices like telescope mounts, imagers, etc. directly accessible from WiFi.

Frequently Asked Questions — Classic ASCOM COM

What is a Classic ASCOM Hub?
A hub is an executable program that allows multiple ASCOM astronomy programs to share a device which has a DLL driver (which could ordinarily serve only a single app at a time). For details in context see ASCOM-COM COnnectivity in the About section. A hub can allow more than one program to connect to it just like an EXE driver, and it in turn provides sharing of the DLL driver for the real device. Hubs can exist for any type of device. The diagram below shows a telescope hub only as an example. The ASCOM Platform comes with a useful hub. See Using DeviceHub (also in the menu on the left).
Diagram
As explained in the previous question, a hub is not needed for an EXE (Local Server) driver. An EXE driver is itself a hub since it is able to serve multiple apps.
What is DeviceHub? What Can I Use it For?
See Using DeviceHub (also in the menu on the left).
How can I use TheSky™ in the Classic ASCOM Environment?
TheSky is compatible with the ASCOM environment. Software Bisque mounts controlled by TheSky may be accessed from ASCOM compatible programs via the Software Bisque supplied ASCOM 2x Mount Adaptor. From within TheSkyX's device control panels, ASCOM-compatible devices (focusers, cameras, domes, mounts, etc) are accessible via the Chooser. Furthermore, the Chooser's Alpaca support can provide access to Alpaca-based devices from within TheSkyX. For more info contact Software Bisque.