Alpaca through the Chooser
Alpaca devices are network connected, communicate through ASCOM's HTTP/REST Alpaca protocol and can be built in any technology that provides an HTTP based interface. They are quite different to the previous generation of devices that could only be connected directly to a Windows PC and that communicated with clients through Microsoft's Component Object Model (COM) technology.
ASCOM Remote Clients have been used since May 2018 to enable clients to communicate with Alpaca Devices . However, the Remote Clients are no longer needed because new Alpaca Dynamic Clients are built right into the Platform and can be created on demand through the Chooser. These dynamically created clients:
The remainder of this section shows how to create and use Alpaca Dynamic Clients to communicate with networked Alpaca devices.
In its default state Chooser works as it always has.
Click the Enable Discovery item to make Chooser search for Alpaca devices and a discovery status LED will appear and flash amber while the discovery is undertaken. If devices are discovered, the LED will become green and the discovered devices will appear in the Chooser list
Discovery must be enabled separately for each device type. This is so that you don't have to wait for discovery to complete when you don't have any Alpaca devices of that particular type.
If no devices respond in time the LED will become red.
To create a dynamic driver for the newly discovered Alpaca device, select it from the drop-down list as usual and press the OK button. Visual confirmation to press the OK button is provided by a balloon message that appears for a few seconds when the device is selected. Please note that the Properties button will be greyed out because the driver hasn't yet been created.
After pressing the OK button the dialogue below will appear advising that Administrator level approval is required. Click the dialogue's "Do not show this message again" check box if you no longer wish to see this dialogue or the earlier balloon message. This setting can be reset through the Chooser Configuration menu if required.
After clicking OK the normal Administrator security dialogue will appear and, if approved, the driver will be created and you will be returned to the Chooser with the new dynamic driver selected.
There is no need to change the driver’s Properties because these will already have been set using information from the discovered device, but they can be inspected and changed if you wish.
Now press the Chooser OK button to select the newly created dynamic driver as normal.
The created driver will be available to all ASCOM clients on this PC - there is no need to rediscover the device on every client, you just need to select the device’s dynamic COM driver from the list as shown below.
TThe Configure Chooser and Discovery dialogue enables you to set:
Example of the Chooser dialogue with width set to 400
Example of the Chooser dialogue with “List known devices” on
Example of the “manage devices dialogue