Click or drag to resize

IFocuserV3TempComp Property

The state of temperature compensation mode (if available), else always False.

Namespace:  ASCOM.DeviceInterface
Assembly:  ASCOM.DeviceInterfaces (in ASCOM.DeviceInterfaces.dll) Version: 3c9121baba46811fe6e53a58a05935662261416d
bool TempComp { get; set; }

Property Value

Type: Boolean
PropertyNotImplementedExceptionIf TempCompAvailable is False and an attempt is made to set TempComp to true.
NotConnectedExceptionIf the device is not connected and this information is only available when connected.
DriverExceptionMust throw an exception if the call was not successful

TempComp Read must be implemented and must not throw a PropertyNotImplementedException.

TempComp Write can throw a PropertyNotImplementedException.

If the TempCompAvailable property is True, then setting TempComp to True puts the focuser into temperature tracking mode; setting it to False will turn off temperature tracking.

If temperature compensation is not available, this property must always return False.

A PropertyNotImplementedException exception must be thrown if TempCompAvailable is False and an attempt is made to set TempComp to true.


Prior to Platform 6.4, the interface specification mandated that drivers must throw an InvalidOperationException if a move was attempted when TempComp was True, even if the focuser was able to execute the move safely without disrupting temperature compensation.

Following discussion on ASCOM-Talk in January 2018, the Focuser interface specification has been revised to IFocuserV3, removing the requrement to throw the InvalidOperationException exception. IFocuserV3 compliant drivers are expected to execute Move requests when temperature compensation is active and to hide any specific actions required by the hardware from the client. For example this could be achieved by disabling temperature compensation, moving the focuser and re-enabling temperature compensation or simply by moving the focuser with compensation enabled if the hardware supports this.

Conform will continue to pass IFocuserV2 drivers that throw InvalidOperationException exceptions. However, Conform will now fail IFocuserV3 drivers that throw InvalidOperationException exceptions, in line with this revised specification.

See Also