Function Calls for Special Processing

Most API function in the WMX3 library are processed by the API process thread (see Devices). However, a few API functions are not processed by the API process thread. These API functions may have special properties when used with certain functions. For example, the GetStatistic function will be unable to obtain statistics data for these functions.

The following are special processing functions.

• StartEngine

• RestartEngine

• StopEngine

• CreateDevice

• CloseDevice

• GetDeviceID

• AutoQuitWithoutActiveDev

• SetWatchdog

• GetWatchdog

• ResetWatchdogTimer

• SetStatistic

• GetStatistic

• GetAllDevices

• SetDeviceName

• GetDeviceName

• RecordWindowsUpdates

• CompareWindowsUpdates

• Io::SetOutBitEx

• Io::SetOutByteEx

• Io::SetOutBytesEx

• Io::SetOutBitsEx

• Io::SetOutAnalogDataCharEx

• Io::SetOutAnalogDataUCharEx

• Io::SetOutAnalogDataShortEx

• Io::SetOutAnalogDataUShortEx

• Io::SetOutAnalogDataIntEx

• Io::SetOutAnalogDataUIntEx

• Io::GetInBitEx

• Io::GetInByteEx

• Io::GetInBytesEx

• Io::GetInAnalogDataCharEx

• Io::GetInAnalogDataUCharEx

• Io::GetInAnalogDataShortEx

• Io::GetInAnalogDataUShortEx

• Io::GetInAnalogDataIntEx

• Io::GetInAnalogDataUIntEx

• Io::GetOutBitEx

• Io::GetOutByteEx

• Io::GetOutBytesEx

• Io::GetOutAnalogDataCharEx

• Io::GetOutAnalogDataUCharEx

• Io::GetOutAnalogDataShortEx

• Io::GetOutAnalogDataUShortEx

• Io::GetOutAnalogDataIntEx

• Io::GetOutAnalogDataUIntEx

• UserMemory::SetMBitEx

• UserMemory::SetMByteEx

• UserMemory::SetMBytesEx

• UserMemory::SetMBitsEx

• UserMemory::SetMAnalogDataCharEx

• UserMemory::SetMAnalogDataUCharEx

• UserMemory::SetMAnalogDataShortEx

• UserMemory::SetMAnalogDataUShortEx

• UserMemory::SetMAnalogDataIntEx

• UserMemory::SetMAnalogDataUIntEx

• UserMemory::GetMBitEx

• UserMemory::GetMByteEx

• UserMemory::GetMBytesEx

• UserMemory::GetMAnalogDataCharEx

• UserMemory::GetMAnalogDataUCharEx

• UserMemory::GetMAnalogDataShortEx

• UserMemory::GetMAnalogDataUShortEx

• UserMemory::GetMAnalogDataIntEx

• UserMemory::GetMAnalogDataUIntEx

• UserMemory::GetUserMemoryAddress

• Log::GetMemoryLogData

• ApiBuffer::CreateApiBuffer

• ApiBuffer::FreeApiBuffer

• ApiBuffer::StartRecordBufferChannel

• ApiBuffer::EndRecordBufferChannel

• ApiBuffer::GetRecordingBufferChannel

• ApiBuffer::GetStatus

• CyclicBuffer::AddCommand

• CyclicBuffer::Execute

• CyclicBuffer::Abort

• CyclicBuffer::GetStatus

• Config::Export

• Config::Import

• Config::GetAndExportAll

• Config::ImportAndSetAll

• ErrorToString (of each module)

Functions that are normally processed by the API process thread may return certain errors before the data is passed to the API process threads. For example, if a device has not been created with the CreateDevice function, most API functions will return the DeviceIsNull error without passing the data to the API process threads. These API function calls may also not be supported by certain functions such as GetStatistic.