Skip to content

ASCOM Platform 7.1 - Update 2

Choose a tag to compare

View all tags
@Peter-Simpson Peter-Simpson released this 09 Feb 09:45
· 28 commits to main since this release
v7.1.2
c38fc77
This commit was signed with the committer’s verified signature.
Peter-Simpson Peter Simpson
GPG key ID: D9AE8431D54C3154
Verified
Learn about vigilant mode.

Installer

The installer has been removed from this release because of reports that it causes serious instability. Please install a later version or stay on your present Platform until we are sure we have a fix.

The Platform requires the following Windows and .NET versions:

  • Windows 10 build 1809 (October 2018 release) or later
  • .NET 3.5 to be installed (this will be installed automatically on Windows 10 and 11.)
  • .NET 4.8 to be installed

This release is primarily to address issues that occurred when installing Platform 7.1 - Update 1.

Changes and fixes in Platform 7.1 Update 2

  • Added a work-round for a .NET bug that impacted ASCOM COM object reliability in Platforms 7.1 and 7.1 Update 1.
    • The .NET bug caused susceptible drivers to fail in some environments, particularly Windows ARM 64bit.
    • The bug also caused the 64bit Platform installer validation test to report a -1073741819 error in some environments.
  • Fixed a Platform installer issue that caused some installs to stop while registering the Omni-Simulators.
  • Fixed the Alpaca Dynamic Clients so they no longer use the 100-Continue HTTP protocol when sending data to Alpaca devices. Commands are now sent directly in one packet, eliminating an un-necessary network round trip.
  • Fixed the Utilities.Serial.ReceiveTerminatedBinary(System.Byte[]) method so that it operates correctly in locales that use double byte character sets, such as Japan and China.
  • Fixed the Profile Explorer About box to display correct information.
  • Fixed a Platform camera simulator array index out of bounds error when returning images smaller than 601 pixels wide that was introduced in Platform 7.1.
  • The Platform and ASCOM Library Help files are now online rather than being stored locally in the outdated Microsoft help format.
  • Revised the update checker message to refer to 'Updates' rather than 'Service Packs'.
  • Changed Alpaca Dynamic Driver log file names from ASCOM.AlpacaSim... to ASCOM.DynamicDriver...

Changes and fixes in Platform 7.1 Update 1

  • Installer - Fixed an issue that occasionally prevented the OmniSim COM proxy drivers from registering.
  • Device Hub
    • Added a dome safety feature to prevent sudden changes in rotation direction. This ensures that a configurable minimum time period passes between a slew completing, and the next slew starting.
    • Fixed issue where dome synchronisation failed when the controlled dome did not support opening the dome aperture.
    • Fixed an issue where the new "two axis offsets" dome slaving calculation was not selected by default.
    • The user guide has been updated with consistent language for optical offset names and other terms.

Changes for Everyone in Platform 7.1

  • JustAHub
    • The 32bit version of JustaHub now supports all ASCOM device types including SafetyMonitor, CoverCalibrator, Focuser, ObservingConditions, Rotator and Switch.
    • A new 64bit version of JustAHub has been added to host 64bit in-process DLL drivers.
  • Device Hub
    • A new dome synchronisation algorithm from Patrick Wallace that adds support for L mount and more complex mount types.
    • Dome synchronisation support for mounts with multiple observing telescopes. Device Hub can now store offsets for up to 5 telescopes, mounted in different positions, and the dome will slew to the appropriate position depending on the configured offsets for the selected telescope. The selected telescope can be changed in real time without needing to disconnect the telescope or dome devices.
    • A wider range of telescope axis movement rates in the Direct Slew tab drop-down including: the minimum available rate, the maximum available rate, minimum + 25% of range, minimum + 50% of range and minimum + 75% of range.
    • The user guide has been expanded to include full instructions on setting up dome synchronisation for multiple mount types and telescope configurations.
  • The Omni-Simulators have the following new features: ◦A tray icon is now provided to enable the console to be shown or hidden and the web UI to be launched.
    • The generated ASCOM API swagger documentation has been greatly improved.
    • Individual device configuration can be changed programmatically through a new JSON API to support test requirements. Further information is provided in the developer changes section.
    • The Dome, FilterWheel, Focuser, Rotator, and Safety Monitor devices have been completely rewritten (the remaining device types will be updated in a future release). This provides several new features:
      • Each device type now supports multiple instances.
      • The interface version can be set so that each device can simulate behavior for different ASCOM interface versions.
      • Each device's configuration can be changed through a new JSON API, see developer changes for more information.
      • Each device instance now creates its own log file whose log level can be set independently.
      • Asynchronous connects now take a short time to complete enabling asynchronous connect code to be tested more effectively.
  • Diagnostics has a new feature to log and report use of .NET 3.5 based components by clients and drivers. This is enabled through the Diagnostics / Tools menu.
  • Links to both 32bit and 64bit connection testers have been added to the Start/ASCOM Platform menu.
  • Installation speed has been improved by omitting NGEN optimisation by default. This can be enabled through the installer UI if required by older, less performant, PCs.
  • The built-in Delta UT predictions have been updated to January 2027.
  • Online help has been switched to a more modern format that works well on both phone and desktop screen sizes: Online Help

Platform Issues fixed in Platform 7.1

  • Installer
    • The VB6 support DLLs are now registered by the installer as well as being installed.
    • The error message when installing on a non-supported OS has been improved.
    • An issue that listed only the last error encountered rather than all errors encountered has been fixed.
    • Ensure that all required PlatformUpdateChecker DLL files are installed.
    • An unnecessary message box has been removed when uninstalling the Platform update checker.
  • Device Hub
    • Only one app log file is created rather than two.
    • Telescope.Slewing and Dome.Slewing are polled more frequently to ensure that accurate values are returned by Device Hub.
    • Fixed an issue that sometimes prevented Device hub from responding to a telescope slew when dome synchronisation was enabled.
  • Dynamic Clients
    • Fixed an issue where multiple ? characters were sent in GET calls that have parameters.
    • Fixed an issue where Dynamic Drivers created under Platform 6 fail after update to Platform 7.
    • The Action method once again supports strings in excess of 65,535 characters as it does in Platform 6.
  • Chooser - Devices that are not registered correctly, and that have missing CLSID values, are now handled cleanly.
  • Diagnostics - Diagnostics can now handle values stored as multi-strings correctly.
  • Astrometry - Fixed an "Unknown update type value" error message from the DeltaT function when earth rotation parameter updates are configured as "manual internet update".

Changes for Developers in Platform 7.1

  • Each Omni-Simulator device configuration can be changed programmatically through a new JSON API that enables the simulators to be configured to support a variety of client testing requirements.
    • This Omni-Simulator specific API can be explored by clicking the "View Swagger docs and interactive queries" link on the main page of the Omni-Simulator browser interface and selecting the "OmniSim only endpoints" definition from the drop-down selector at the top of the page.
    • Please note that the API may be refined in future and that some implementations and capabilities could change.
  • Driver Templates
    • The hardware class comments have been improved to aid implementation.
    • The main form has been removed because it was not adding any value and appeared as a minimised Window.
  • TraceLogger.LogMessage now accepts null strings for the test name and message fields, which are now treated empty strings rather than throwing exceptions.

Development Issues fixed in Platform 7.1

  • Driver Templates
    • Fixed logic and messaging errors in the Disconnect() method.
    • Fixed an issue causing the generated hardware class to have two dots separating the file name and the file extension. e.g. CoverCalibratorHardware..cs
    • Fixed an issue in the hardware class SetupDialog method where unnecessary error messages were displayed when the device was already connected.

Installer SHAs

The installer has been removed because of reports of serious instability. Please update to a later version or stay on your current release.

Assets 3
Loading