C# 클래스 NGIOdotNET.NGIO

Send a command to the specified device hardware and wait for a response.

Each device type has a command protocol that is unique to that device type. The command protocol used by NGIO_DEVTYPE_LABQUEST_AUDIO devices is a subset of the protocol used by NGIO_DEVTYPE_LABQUEST devices. This protocol is documented in the NGIOSourceCmds class. Additional documentation can be found in NGIOSourceCmds.h.

Note that NGIO_Device_SendCmdAndGetResponse() will fail if you send a NGIO_CMD_ID_START_MEASUREMENTS command while NGIO_Device_GetNumMeasurementsAvailable() says measurements are available.

So...if you are restarting measurements, you should clear any old measurements in the NGIO Measurement Buffer first by reading in the measurements until the Buffer is empty, or you should call NGIO_Device_ClearIO().

Every command supported by NGIO_Device_SendCmdAndGetResponse() has an associated response. If no response specific to a command is defined, then the format of the response is NGIODefaultCmdResponse. Some commands have associated parameter blocks defined for them.

If NGIO_Device_SendCmdAndGetResponse() returns -1, additional information about a NGIO_Device_SendCmdAndGetResponse() error may be obtained by calling NGIO_Device_GetLastCmdResponseStatus().

Device_SendCmdAndGetResponse2() is the same as Device_SendCmdAndGetResponse1() except that no response block is returned by the function(even though some sort of response always comes back from the device unless there is a communication failure). This is reasonable if the caller only cares about when the function succeeds or fails, which can be determined from the return value.

Device_SendCmdAndGetResponse3() is the same as Device_SendCmdAndGetResponse1() except that no parameter block is sent to the device. That works fine for commands that do not require parameters.

Device_SendCmdAndGetResponse4() is the same as Device_SendCmdAndGetResponse1() except that no parameter block is sent to the device and no response block is returned by the function. That works fine for commands that do not require parameters when the caller is only interested in success or failure.