ASCOM 'SupportedActions' are not read from the drivers

Issue #1268 resolved
Peter De Groot created an issue

[Y ] Is the issue reproducible?
[Y ] Are all prerequisites that are mentioned inside the manual met?

Which Version are you running? V3.0 #085

Description

During loading of the ASCOM drivers the ‘SupportedActions' are not read from the driver(s).
In NINA 2 this works perfectly.

Discovered this while using the ‘Device Actions and Commands’ plugin.
First I was thinking it was the plugin but after checking the logs I found the following:

In log NINA v2

14:00:54.344 Description ASCOM SafetyMonitor Driver for OTSRSafetyHub
14:00:54.347 DriverInfo Information about the driver itself. Version: 1.1
14:00:54.349 DriverVersion 1.1
14:00:54.352 SupportedActions Returning 2 actions.
14:00:54.357 DriverVersion 1.1
14:00:54.361 IsSafe False
14:00:55.870 IsSafe False
14:00:57.374 IsSafe False


in log NINA v3.0

14:03:25.170 Description ASCOM SafetyMonitor Driver for OTSRSafetyHub
14:03:25.171 DriverInfo Information about the driver itself. Version: 1.1
14:03:25.172 DriverVersion 1.1
14:03:25.173 InterfaceVersion 1
14:03:25.173 DriverVersion 1.1
14:03:25.174 IsSafe False
14:03:26.176 IsSafe False


No SupportedActions enumerations in V3.0

Steps to Reproduce

  • Use a ASCOM SafetyMonitor Driver.
  • Start NINA
  • Connect to device
  • check log.
  • Check ‘Device Actions and Commands’ plugin. → No Actions in enumeration List of available actions.

Expected behaviour

  • ‘Device Actions and Commands’ plugin → List of available actions.

Actual behaviour

Blank Actions list.

Comments (7)

  1. Stefan B repo owner

    Not able to reproduce. Device actions are called in the same way for all ascom devices and it works for the simulators that i’ve tested.

  2. Peter De Groot reporter

    Hi Stefan, Found the issue. Driver was a legacy (V1) driver and returned InterfaceVersion == 1. NINA V2.x does not care about the InterfaceVersion it seems, V3.x does and did not read the property. I updated the InterfaceVersion to 2 and now it does work. (The ASCOM driver creation template still keeps putting 1 in it, but that’s not your problem.) So problem solved. Sorry for wasting your time!

  3. Log in to comment