Skip to content

@Peter-Simpson Peter-Simpson released this Mar 10, 2019 · 3 commits to master since this release

The installer is located in the "Assets" section at the end of these release notes


Breaking Changes

  • As of version 1.5.0, URLs are case sensitive in line with the revised Alpaca API definition
    • This will only be of concern if you have created your own Alpaca client and are issuing mixed case URLs or you are testing with a browser and are reusing mixed case URLs that were permitted in earlier versions.
  • The Remote Server executable has been renamed from ASCOM.RESTServer.exe to ASCOM.RemoteServer.exe for consistency with documentation and general usage.
    • The impact is that any desktop shortcuts or script references that you have created will no longer find the Remote Server executable, these will need to be updated to use the new executable name.

Other Changes

  • IP addresses and host names are now validated on Remote Client Setup dialogues, preventing incorrect values from being entered.
  • The Remote Server will now log messages indicating whether or not each configured device initialised correctly.
  • Naming of Start menu shortcuts has been made consistent

Issues Fixed

  • Remote clients will no longer fail if unsupported device types are present in the ASCOM Profile.
  • Error messages with HTTP status 400 now display the returned message instead of the error status header description
  • The Remote Server will now prevent devices being used when drivers do not initialise correctly.
  • Firewall rules for the Remote Server are now set correctly
  • Documentation
    • Correct HTTP parameter separator character from "," to "&" in several places.
    • Correct Client and ClientTransaction parameter names to ClientID and ClientTransactionID in two places.
Assets 3

@Peter-Simpson Peter-Simpson released this Feb 15, 2019 · 18 commits to master since this release



  • 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.

Issues Fixed

  • 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.

Notes - Upgrading from Version 1.0

  • 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.
Assets 3
You can’t perform that action at this time.