Serial Framework
ContentsIndexHome
PreviousUpNext
Variables

The following table lists variables in this documentation.

Name 
Description 
The base error code for Serial Framework errors.  
Configuration Manager DLL was not found.  
Required Configuration Manager functions (API) are not available.  
The ClearCommBreak method failed.  
The given Device Class Guid was not found.  
No one device's interface was found for specified device's instance ID.  
A serial device has been removed.  
Write operation was timed out on wait. Probably device is disconnected or not available.  
The EscapeCommFunction has been failed.  
The FlushBuffers method failed.  
The GetCommStatus method failed.  
Monitoring is not running.  
Monitoring is running.  
The PurgeComm operation was failed.  
Read operation failed.  
The SetCommBreak method failed.  
The TransmitCommChar method failed.  
Unable clear input and output buffers.  
Unable create overlapped operation event.  
Unable create communication restart event.  
Unable to read COM port configuration.  
Unable to read COM port timeouts.  
Unable to locate specified device's node.  
Unable to get read buffer size.  
Unable to get write buffer size.  
Unable to initialize the overlapped IO operation.  
The device's registry key was not found or not enough privilegies.  
The device's parameters registry key was not found or not enough privilegies.  
Unable to open the specified COM port.  
Unable to read a device's friendly name.  
Unable to read a device's port name.  
Unable to write COM port configuration.  
Unable to write COM port timeouts.  
Unable to set COM potr events mask.  
Unable to set read buffer size.  
Unable to set write buffer size.  
Write data to the serial port was failed.  
Timeout appeared during write operation. That doe snot mean real error. That just means that some bytes were sent but time out appeared before all bytes are sent. You can retry to send remaining bytes or terminate connection.  
The base erorr code for USB monitor errors.  
No USB devices found on this system.  
Monitoring is not running.  
Monitoring is running.  
The base error code for all WinUSB subsystem errors.  
WinUSB subsystem was not loaded.  
Unable create WinSUB subsystem synchronization mutex.  
WinUSB subsystem is not available on your system.  
Unknown or unexpected WinUSB error.  
Copyright (c) 2006-2018. All rights reserved.