Click or drag to resize

ITelescopeV4CommandBlind Method

Transmits an arbitrary string to the device and does not wait for a response. Optionally, protocol framing characters may be added to the string before transmission.

Namespace: ASCOM.DeviceInterface
Assembly: ASCOM.DeviceInterfaces (in ASCOM.DeviceInterfaces.dll) Version: 7.0.0-rc.0+0
Syntax
void CommandBlind(
	string Command,
	bool Raw = false
)

Parameters

Command  String
The literal command string to be transmitted.
Raw  Boolean  (Optional)
if set to true the string is transmitted 'as-is'. If set to false then protocol framing characters may be added prior to transmission.
Exceptions
ExceptionCondition
MethodNotImplementedExceptionIf the method is not implemented
NotConnectedExceptionIf the device is not connected
DriverExceptionAn error occurred that is not described by one of the more specific ASCOM exceptions. Include sufficient detail in the message text to enable the issue to be accurately diagnosed by someone other than yourself.
Remarks

May throw a NotImplementedException.

The CommandXXX methods are a historic mechanic that provides clients with direct and unimpeded access to change device hardware configuration. While highly enabling for clients, this mechanic is inherently risky because clients can fundamentally change hardware operation without the driver being aware that a change is taking / has taken place.

The newer Action / SupportedActions mechanic provides discrete, named, functions that can deliver any functionality required.They do need driver authors to make provision for them within the driver, but this approach is much lower risk than using the CommandXXX methods because it enables the driver to resolve conflicts between standard device interface commands and extended commands provided as Actions.The driver is always aware of what is happening and can adapt more effectively to client needs.

Revision History
DateVersionDescription
ITelescopePlatform 3.0Member present.
ITelescopeV4Platform 7.0Deprecated, see note above.
See Also