Skip to content

@Peter-Simpson Peter-Simpson released this Jul 16, 2020

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

Highlights and Dependencies

Includes support for IRotatorV3.

Documentation

Changes since version 1.6.7424.28304

  • DriverVersion responses are now consistent, identifying the Remote Client and hosted device versions
  • Device Descriptions are now passed on verbatim, without additional descriptive text, so that the full 64 character length is available to devices.
  • Now supports IRotatorV3 devices
  • The Remote Server can now be restarted remotely via the /server/v1/restart API command

Bugs Fixed

  • A bug that stopped HTTP/1,0 clients from using fast camera image array download has been fixed
  • A bug that stopped Camera.ImageArray from working with colour data has been fixed
Assets 3

@Peter-Simpson Peter-Simpson released this Apr 29, 2020

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

Highlights and Dependencies

Includes support for ICameraV3 and Alpaca device discovery over IPv6.

The Alpaca PI reference has been updated and now includes the specification for the Alpaca discovery protocol.

Documentation

Changes since version 1.6.7360.22073

  • Added support for Alpaca device discovery through IPv6.
  • Improved display of IP addresses in the setup GUI.
  • Improved messaging when the Remote Server's bound IP address is changed.
  • The Remote Server's HTML setup pages now include more information on configured drivers.
  • The Alpaca API reference document now includes the device discovery specification.
  • Added support for the new ICameraV3 interface members.
Assets 3

@Peter-Simpson Peter-Simpson released this Feb 26, 2020

Highlights and Dependencies

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

  • This release requires ASCOM Platform 6.5

The Platform 6.5 Chooser can now discover and create drivers for devices presented by the Remote Server.

Cover calibrator devices and IRotatorV3 rotators introduced in Platform 6.5 are supported by the Remote Server.

Performance of Camera.ImageArray when handling large images has been significantly improved.

Documentation

Changes

  • The Remote Server supports the Alpaca discovery protocol.
    • This is enabled by default and can be turned off through the configuration dialogue.
  • Camera.ImageArray performs significantly faster and uses less memory.
    • The faster mechanic is enabled by default and can be disabled through the Camera client setup dialogue.
  • The Remote Server has improved support for multi-threaded drivers.
    • Commands are now forwarded to a driver immediately on receipt, enabling the driver to decide when to process them. Previously, commands were serialised and sent to the driver one at a time.
    • The new concurrent behaviour is enabled by default, but the previous synchronous behaviour can be restored through the Remote Server setup dialogue if required.
  • Added support for CoverCalibrator devices
  • Added support for rotators that implement the IRotatorV3 interface
  • The Remote Server can now handle up to 100 devices
  • The Remote Server has CORS support.
  • Configuration storage and retrieval is more robust if it encounters corrupt values.
  • The installation and configuration document has been extensively updated.

Issues Fixed

  • Form parameter parsing has been made more robust.
  • Permissions are now correctly set for user's whose accounts don't have admin privilege and who use a different Admin account name to authorise configuration changes.
  • The Start menu ASCOM Remote documentation link now works correctly.
  • A rare un-handled application exception when closing the Remote Server has been fixed.
  • The Setup button now works correctly with early Focuser drivers that implement IFocuserV1
Assets 3
Jul 10, 2019
Fix bug when logging form parameters for PUT requests.
Parsing of form parameters has been made more robust and parameter logging has been introduced.

@Peter-Simpson Peter-Simpson released this Jun 19, 2019

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

Documentation

Changes

  • The Remote Server now handles drivers more gracefully when they don't initialise correctly.
  • The inbound firewall rule now supports edge traversal.
  • Remote clients now include retry logic to deal with transient networking issues
  • Implemented a more flexible approach to extracting the image array type and rank from the JSON response.
  • The Alpaca management HTML and JSON APIs have been implemented in line with the Alpaca standard.

Issues Fixed

  • Firewall rules are now correctly applied for the Remote Server.
  • SetNetworkRules will now work when .NET 4.6 is installed but .NET 4.7 is not.
  • Parameter handling has been revised to be consistent with the API specification. Now, query parameters will only be honoured on HTTP GET operations and Body parameters will only be honoured on HTTP PUT operations. Previously, query parameters were accepted for PUT operations and merged with any parameters supplied in the body.
  • The installer now installs the SetNetworkPermissions exe and support files if the user just selects the Remote Clients for install and does not select the Remote Server option.
Assets 3
May 16, 2019
Add retry logic to remote clients.
Remote clients will now attempt to send a command two further times if they receive active refusals from the server. This is to improve resilience if the server is transiently unable to accept a command for some reason.
Remote client setup dialogue screens now show the ASCOM Remote version number.

@Peter-Simpson Peter-Simpson released this Mar 10, 2019

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

Documentation

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
Mar 10, 2019
Rename Remote Server executable
BREAKING CHANGE - The Remote Server executable has been renamed from ASCOM.RESTServer.exe to ASCOM.RemoteServer.exe to align with naming in documentation. This will break any desktop shortcuts or command scripts.
Internally the Remote Server project name and source file directory name have also been aligned.
Mar 4, 2019
Improved Remote Server resilience
The Remote Server will now record when drivers do not initialise correctly and will reject attempts to call methods on failed devices.
The Remote Server configuration is now recorded in the log on start-up and after Setup is run.
Logged information has been improved as well as log formatting.
Feb 20, 2019
Fix issue when a Profile contains unsupported device types
Device types are defined in the Profile as folders with the name "XXXXX Drivers". ASCOM Remote only supports specific device types and fell over if it encountered a device type in the user's profile that was not supported.
Fix exception reporting issue in main program.
Correct spelling errors in source code
Improve reporting of errors to the user and subsequent application behaviour