Skip to content

Releases: ASCOMInitiative/ASCOMRemote

ASCOM Remote - Version 6.7.1+4785

29 May 17:15
e854f1b
Compare
Choose a tag to compare

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

Highlights and Dependencies

This release fixes a bug in version 6.7.0 that prevented the network from being changed but is otherwise the same as 6.7.0.

Release 6.7.0 Release notes

The Remote Server can now be configured to run as either a 32bit or a 64bit application. 64bit mode will primarily benefit 64bit capable in-process DLL camera drivers that deliver large images. Other devices are not expected to see significant benefits from 64bit operation.

Please note that drivers implemented as 32bit in-process DLLs will fail if loaded in the 64bit Remote Server application.

The other significant change is an infrastructural switch from .NET Framework to ,NET 7.0, which has enabled the introduction of SEMVER version numbers and alerts when application updates are available.

Remote Server Changes

  • The Remote Server can run as either a 32bit or a 64bit application. The start-up bitness is configured through the Setup dialogue.
  • When an application update is available, a button will appear on the main server form that will open a browser at the GitHub release page from which the update can be downloaded.
    • Update alerts are enabled by default and can be configured off, if required, in the Setup dialogue.
  • Remote Server configuration is now split onto two tabs in the Setup dialogue.
  • Version numbering has changed to SEMVER format.
  • The application is now implemented using .NET 7.0 rather than .NET Framework.

Bugs Fixed

  • ClientID and ClientTransactionID are now treated as optional parameters in line with the Alpaca specification.
  • CORS support now works with pre-flighted requests.

Alpaca API Reference Documentation Updates

  • Section 2.2.2 was clarified to address casing of boolean and string parameter values.
  • Section 2.3.1 was clarified to confirm that ‘thousands’ separators must not be used.
  • Section 2.7 was updated to note the requirement to set a Content-Type header on JSON responses.
  • Section 6 - Merged the ImageBytes specification into the API Reference.
  • Section 6.7.1 was clarified to indicate that none of the fields should return negative values.
  • Section 6.10 was updated to describe support functions in the cross platform ASCOM Library for .NET users as well as approaches available to users of other languages.
  • Added a “Client Considerations” section that includes the recommended approach for handling errors from Alpaca devices.

Installer SHAs

SHA256: 6f94300681feab6c817a40ed9e5049b0b3c9628e54b5eddec2563181bc97c937
SHA1: c83b07902450a290719e9f05183db012baa12a1b

ASCOM Remote - Version 6.7.0+4779

29 May 13:03
142f7a8
Compare
Choose a tag to compare

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

Highlights and Dependencies

The Remote Server can now be configured to run as either a 32bit or a 64bit application. 64bit mode will primarily benefit 64bit capable in-process DLL camera drivers that deliver large images. Other devices are not expected to see significant benefits from 64bit operation.

Please note that drivers implemented as 32bit in-process DLLs will fail if loaded in the 64bit Remote Server application.

The other significant change is an infrastructural switch from .NET Framework to ,NET 7.0, which has enabled the introduction of SEMVER version numbers and alerts when application updates are available.

Remote Server Changes

  • The Remote Server can run as either a 32bit or a 64bit application. The start-up bitness is configured through the Setup dialogue.
  • When an application update is available, a button will appear on the main server form that will open a browser at the GitHub release page from which the update can be downloaded.
    • Update alerts are enabled by default and can be configured off, if required, in the Setup dialogue.
  • Remote Server configuration is now split onto two tabs in the Setup dialogue.
  • Version numbering has changed to SEMVER format.
  • The application is now implemented using .NET 7.0 rather than .NET Framework.

Bugs Fixed

  • ClientID and ClientTransactionID are now treated as optional parameters in line with the Alpaca specification.
  • CORS support now works with pre-flighted requests.

Alpaca API Reference Documentation Updates

  • Section 2.2.2 was clarified to address casing of boolean and string parameter values.
  • Section 2.3.1 was clarified to confirm that ‘thousands’ separators must not be used.
  • Section 2.7 was updated to note the requirement to set a Content-Type header on JSON responses.
  • Section 6 - Merged the ImageBytes specification into the API Reference.
  • Section 6.7.1 was clarified to indicate that none of the fields should return negative values.
  • Section 6.10 was updated to describe support functions in the cross platform ASCOM Library for .NET users as well as approaches available to users of other languages.
  • Added a “Client Considerations” section that includes the recommended approach for handling errors from Alpaca devices.

Installer SHAs

SHA256: 8106362dff83a5c1ee188048d1a68ab1b242bc440ae8288b5b87b1591a041c59
SHA1: 8fdeb32d2470c25411fdb5ffb3b13fcbfc8038ce

ASCOM Remote - Version 6.6.8419.36633

20 Jan 12:56
b76e8e6
Compare
Choose a tag to compare

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

Highlights and Dependencies

This release tightens handling of parameters for PUT operations to align behaviour with the Alpaca specification. The specification requires PUT parameters to be case sensitive and to be sent as form parameters in the body of the request. Previously parameters were accepted in any casing and also if supplied in the query string.

Documentation

  • No changes.

ASCOM Remote Changes

  • Improved resilience when rolling over log files,
  • Handling of PUT operation parameters now aligns with Alpaca Specification requirements.

Bugs Fixed

  • The Switch Id parameter was previously accepted as 'ID' whereas it is specified in the Alpaca API reference as 'Id'. Now only 'Id' is accepted.
  • In release 6.6.8417.19289 the management API Location field always contained an empty string, it now contains the configured location value.

API Reference Documentation Updates

  • The Camera.Offset method name casing was corrected from 'ofset' to 'Ofset'.
  • The Camera.ImageArray and Camera.ImageArrayVariant description text was clarified to align with the interface specification.
  • The Camera.ImageArrayVariant response description was clarified to align with the interface specification.

Installer SHAs

SHA256: b35a4ea1e97fd72633c3f5f48c4e45ba59704617a3fb2bb9474ab89fa7c3a314
SHA1: 40eddf81eb0552c0b8f079ac3d967b1a1b6dc6fa

ASCOM Remote - Version 6.6.8417.19289

17 Jan 12:18
3be22d4
Compare
Choose a tag to compare

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

Highlights and Dependencies

This release tightens handling of parameters for PUT operations to align behaviour with the Alpaca specification. The specification requires PUT parameters to be case sensitive and to be sent as form parameters in the body of the request. Previously parameters were accepted in any casing and also if supplied in the query string.

Documentation

  • No changes.

ASCOM Remote Changes

  • Improved resilience when rolling over log files,
  • Handling of PUT operation parameters now aligns with Alpaca Specification requirements.

Bugs Fixed

  • The Switch Id parameter was previously accepted as 'ID' whereas it is specified in the Alpaca API reference as 'Id'. Now only 'Id' is accepted.

API Reference Documentation Updates

  • The Camera.Offset method name casing was corrected from 'ofset' to 'Ofset'.
  • The Camera.ImageArray and Camera.ImageArrayVariant description text was clarified to align with the interface specification.
  • The Camera.ImageArrayVariant response description was clarified to align with the interface specification.

Installer SHAs

SHA256: 649f9d6932b68ff08bdb019764b28f84512da9bf93a7b021710f1e171624baf8
SHA1: 5929fabed2b104462b58319c1f4a7268533d4b23

ASCOM Remote - Version 6.6.8324.21963

16 Oct 12:03
02444d5
Compare
Choose a tag to compare

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

Highlights and Dependencies

Documentation

ASCOM Remote Changes since version 6.6.8322.17754

  • Revised minimise to system tray functionality to be more "service like" by hiding the application from ALT/TAB when the Remote Server is minimised to the system tray,

Bugs Fixed

  • The application no longer shows in the task bar when initially started and the option to minimise to system tray has been selected.

API Reference documentation updates since version 6.6.8048.20286

  • None.

Installer SHAs

SHA256: e4f522ec796ddf2666e18ab5601a58acaa7f128a12954b165029e7f18852c405
SHA1: a88ef1bfc91ad51a2e911881b965c45a438cbf58

ASCOM Remote - Version 6.6.8321.14755

13 Oct 11:24
b517d77
Compare
Choose a tag to compare

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

Highlights and Dependencies

Documentation

ASCOM Remote Changes since version 6.6.8048.20286

  • Added "Minimise to system tray" functionality.
    • ASCOM Remote's default behaviour is to minimise to the task bar, as in previous versions. Minimise to system tray can be enabled through the Server Configuration setup tab.
    • When minimised to the system tray a double click on the icon will restore the Remote Server
    • A right click on the icon will display a context menu displaying operational information
      • Click the context menu title to restore ASCOM Remote from its minimised state
      • Click the Exit item to close the Remote Server.
  • Added "Confirm close" option, which prompts the user to confirm that they really do want to close the Remote Server.
    • ASCOM Remote's default behaviour is not to request confirmation before closing, as in previous versions. The confirm close behaviour can be enabled through the Server Configuration setup tab.

Bugs Fixed

  • Improved handling of errors when reading ImageBytes headers.

API Reference documentation updates since version 6.6.8048.20286

  • Corrected the version number in the page footer to match the title page.
  • Section 2.1.3 - Clarified that the Alpaca device number starts at 0 for each device type.
  • Aligned text in section 2.7 with the equivalent text in the online API reference (https://ascom-standards.org/api/). This clarifies the requirement that ClientTransactionId, ServerTransactionId, ErrorNumber and ErrorText fields must be included in all Alpaca device JSON responses.
  • Corrected grammar in several paragraphs including the status code paragraph in section 2.5.

Installer SHAs

SHA256: 87d42c9b50a129efdd875ef7d38b8deb1fe4a0cf6872d408657f0d62bd0aac20
SHA1: 6043af42ac652b79b06b7bd7c5cf654b753df7fa

ASCOM Remote - Version 6.6.8048.20286

13 Jan 11:40
a2d60c4
Compare
Choose a tag to compare

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

Highlights and Dependencies

Documentation

Changes since version 1.6.7500.21910

  • Added ImageBytes support to Camera.ImageBytes and Camera.ImageBytesVariant
  • Major and minor version numbers aligned with current Platform.

Bugs Fixed

  • None.

SHA256: 8fcb92c2ade4418bd1b988e22c7b1ffa652b5a94790d30a64ddc28d6f839b95b
SHA1: f2cdf222b634a1289d9c2c03ab0633b92ab09499

ASCOM Remote - Version 1.6.7946.20070

03 Oct 11:16
d46fc82
Compare
Choose a tag to compare

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

Highlights and Dependencies

Documentation

Changes since version 1.6.7500.21910

  • Documentation revised to improve clarity and new Alpaca Introduction document added.
  • Missing or invalid parameters now return HTTP 400 status errors
  • Installers and executables are now code signed
  • Body parameter values with no name are now ignored
  • Client Accept values referencing text or html are now respected when returning error messages.
  • The + and * codes have been replaced by "All IP Addresses" text in the Setup IP address drop-down list.
  • The log folder location can now be customised from the setup dialogue.
  • Logs can now be configured to roll over at a specified time of day.
  • Logs can now be configured to report UTC rather than local time.
  • Form PUT parameters can now be supplied in scientific (exponent) format e.g. 0.984567E-02.
  • The Remote Server now restarts more quicly when the operating IP address is changed.

Bugs Fixed

  • Added missing support for writing to ICameraV3.Offset
  • HTTP status 404 error messages referenced 403 instead of 404 in their text.
  • Null values returned by drivers for Telescope.AxisRates and Telescope.TrackingRates are now handled gracefully.
  • The Camera.PulseGuide, Camera.StartExposure, Dome.SlewToAltitude, Dome.SlewToAzimuth, Dome.SyncToAzimuth, Focuser.Move now send parameters in the invariant culture as required by the API specification.
  • The connection log now contains the remote client address rather than the local server address.

ASCOM Remote - Version 1.6.7500.21910

16 Jul 09:28
d7c8731
Compare
Choose a tag to compare

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

ASCOM Remote - Version 1.6.7424.28304

29 Apr 16:29
98d8841
Compare
Choose a tag to compare

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.