Dome shut off

[leon shaddick]

Dome disconnects after opening and closing with using #136 and #137

|ERROR|DeviceUpdateTimer.cs|Start|91
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: 5 is not an expected value
at NINA.Equipment.Equipment.MyDome.ShutterStateExtensions.FromASCOM(ShutterState shutterState) in E:\Projects\nina\NINA.Equipment\Equipment\MyDome\AscomDome.cs:line 46
at NINA.WPF.Base.ViewModel.Equipment.Dome.DomeVM.GetDomeValues() in E:\Projects\nina\NINA.Core.WPF\ViewModel\Equipment\Dome\DomeVM.cs:line 196
at NINA.Core.Utility.DeviceUpdateTimer.<<Start>b__16_0>d.MoveNext() in E:\Projects\nina\NINA.Core\Utility\DeviceUpdateTimer.cs:line 77

‌

[Stefan B]

The driver is reporting an invalid shutter state.

the valid range is from 0 to 4, but it reports a value of 5 which is invalid.

See: https://ascom-standards.org/Help/Developer/html/T_ASCOM_DeviceInterface_ShutterState.htm

[George Hilios]

I agree - this looks like a driver bug. Even the latest version of ASCOM only has values up to 4: https://github.com/ASCOMInitiative/ASCOMPlatform/blob/platform6.5/ASCOM.DeviceInterface/Enumerations.cs#L314

[leon shaddick]

Strange no issues with earlier versions started around about #129 and up

[George Hilios]

Leon, nothing changed in NINA with respect to this since the I introduced the Dome interface with the maiden version of 1.11. My spidey sense suspects the dome driver developer is treating this field as a “bit field” where 4 (error) and 1 (closed) combine to value 5. If that’s the case, this is a bug in their driver, as that doesn’t conform to spec.

[Stefan B]

seems to be a driver issue. if not - reopen

[Stefan B]

Removing version: 1.11 Nightly (automated comment)