Documentation

ASCOM Remote Concept: ASCOM Distributed Architecture - background and conceptual diagrams.
Installation: ASCOM Remote Documentation - how to install and configure ASCOM Remote.
ASCOM Alpaca API (for developers): ASCOM Alpaca API Reference - how to use and implement the API.

Changes

ASCOM Remote now uses the revised Alpaca API specification:
- The Reserved Alpaca error numbers (0x400 to 0xFFF) are supported when handling ASCOM exceptions.
- ClientID, ClientTransactionID and ServerTransactionID are now handled as unsigned 32bit integers.
- The redundant and unused "Method" response field has been removed.
- The Remote server will no longer send the Windows specific DriverException response field by default so that it is fully Alpaca compliant. However, this can be enabled to support client and driver development if required.
- URLs are now treated case sensitively. Remote Client requests are sent in lower case and the Remote Server will reject all URLs that are not completely lower case.
Client IP addresses can now be included in the Remote Server log
ClientIDs that are auto generated by Remote Clients have been reduced to the range 1::65536 so that they fit better in the allocated log space.
The Remote Server now logs all supplied parameters when debug tracing is enabled.
The Alpaca API documentation has been updated and extended.
The JSON name of the variable that holds the returned Telescope.TrackingRates collection has been changed from "Rates" to "Value" for consistency with all other responses.

A few inconsistencies between the ASCOM API Specification and it's representation in the Alpaca API on the ASCOM Standards web site have been fixed. The Alpaca API now correctly reflects the ASCOM API Specification.
ASCOM Remote will now work correctly in locale's where characters other than point are used as the decimal separator.
The unusable grey'd out Remote Configuration button has been removed from the Remote Client Setup.

The remote client ProgIDs have changed to reflect the new ASCOM Remote branding, which means that you will need to "re Choose" the remote client applications although the upgrade process will preserve existing settings. The drivers now appear as ASCOM Remote Client 1, 2, 3 etc. in the Chooser.
There is a new "Remote Client Configuration" utility in the ASCOM Remote folder with which you can control how many remote client drivers of each device type are available.