View Issue Details

IDProjectCategoryView StatusLast Update
0002961CCdcielGeneralpublic26-11-17 09:26
ReporterRyan Hamilton Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Summary0002961: ASCOM rotator: V3 members used on IRotatorV2 drivers
DescriptionThe PWI4 rotator driver reports InterfaceVersion = 2 and exposes only the IRotatorV2 members, which I verified quickly from PowerShell Get-Member:

Action, CommandBlind, CommandBool, CommandString, Dispose, Equals, GetHashCode, GetType, Halt, Move, MoveAbsolute, SetupDialog, ToString, CanReverse, Connected, Description, DriverInfo, DriverVersion, InterfaceVersion, IsMoving, Name, Position, Reverse, StepSize, SupportedActions, TargetPosition

But, CCDciel 0.9.97-4213 reads MechanicalPosition (IRotatorV3 and later) while the rotator is connected, which produces this error about once a second:

2026-10-05T21:57:59.775 0: ASCOM.PWI4.Rotator: Get position error: Method 'MechanicalPosition' is not supported by automation object

This wasn't the case with 0.9.92-3775, or if it was, it was much more silent about the issue. This isn't PWI4-specific; I think any IRotatorV2 driver should hit it in the same way.

Also: the rotator input text box is difficult to use in practice since it's also updating with the current position. One has to be very quick to change the value, otherwise the new value gets clobbered by the next update! Changing the current position readout to be a text label instead of re-using the text input box would help a lot in practice.
Additional InformationEnvironment: CCDciel 0.9.97-4213 (Win64), ASCOM Platform 7.1.3, Windows 10 Pro, PlaneWave PW1000 with PWI4 [version] and its rotator driver ASCOM.PWI4.Rotator.
TagsNo tags attached.

Activities

Ryan Hamilton

26-10-08 00:37

reporter   ~0009972

This is with PWI4 version 4.1.8, but PlaneWave haven't updated their ASCOM drivers in a while it seems. I've bugged them to make an IRotatorV3 object while I had their ear about something else at least.

Patrick Chevalley

26-11-17 09:26

administrator   ~0009992

Hi,

This is now fixed, sorry for the long time it take.

There was a call to mechanicalposition at the wrong place, it must be only when software sync is activated.
The overwrite of the position input box is probably because the driver return a different floating point value even when the rotator do not move. I modify the test to not overwrite the value for very small change.

This is in version 0.9.97-4264 you can install from https://vega.ap-i.net/pub/ccdciel/daily_build/

And yes it is good if Planewave can update the driver, IRotatorV3 is now 6 years old and IRotatorV4 is available.

Issue History

Date Modified Username Field Change
26-10-08 00:34 Ryan Hamilton New Issue
26-10-08 00:37 Ryan Hamilton Note Added: 0009972
26-11-17 09:26 Patrick Chevalley Note Added: 0009992