LabVIEW
16640 and 16409 errors
From a very old faq I found the following text:
4019:--> you had receive buffer overrun,framing error and a break
and the other 4100 shows transmitbuffer full while trying to send.
Hex Value Error Name Meaning
0x0001 CE_RXOVER Receiving queue overflowed. There was either no room in the input queue or a character was received after the end-of-file character was received.
0x0002 CE_OVERRUN Character was not read from the hardware before the next character arrived. The character was lost.
0x0004 CE_RXPARITY Hardware detected a parity error.
0x0008 CE_FRAME Hardware detected a framing error.
0x0010 CE_BREAK Hardware detected a break condition.
0x0020 CE_CTSTO CTS (clear-to-send) timeout. While a character was being transmitted, CTS was low for the d
uration specified by the fCtsHold member of COMSTAT.
0x0040 CE_DSRTO DSR (data-set-ready) timeout. While a character was being transmitted, DSR was low for the duration specified by the fDsrHold member of COMSTAT.
0x0080 CE_RLSDTO RLSD (receive-line-signal-detect) timeout. While a character was being transmitted, RLSD was low for the duration specified by the fRlsdHold member of COMSTAT.
0x0100 CE_TXFULL Transmission queue was full when a function attempted to queue a character.
0x0200 CE_PTO Timeout occurred during an attempt to communicate with a parallel device.
0x0400 CE_IOE I/O error occurred during an attempt to communicate with a parallel device.
0x0800 CE_DNS Parallel device was not selected.
0x1000 CE_OOP Parallel device signaled that it is out of paper.
0x8000 CE_MODE Requested mode is not supported, or the idComDev parameter is invalid. If set, CE_MODE is the only valid error.
To use this table, take the error number and disect it into its error components. Fo
r example, if Serial Port Write.vi returns the error 16,408, then the errors returned are CE_BREAK and CE_FRAME (16,408 = 16,384 + 16 + 8 = 0x4000 + 0x0010 + 0x0008).
4019:--> you had receive buffer overrun,framing error and a break
and the other 4100 shows transmitbuffer full while trying to send.
Hex Value Error Name Meaning
0x0001 CE_RXOVER Receiving queue overflowed. There was either no room in the input queue or a character was received after the end-of-file character was received.
0x0002 CE_OVERRUN Character was not read from the hardware before the next character arrived. The character was lost.
0x0004 CE_RXPARITY Hardware detected a parity error.
0x0008 CE_FRAME Hardware detected a framing error.
0x0010 CE_BREAK Hardware detected a break condition.
0x0020 CE_CTSTO CTS (clear-to-send) timeout. While a character was being transmitted, CTS was low for the d
uration specified by the fCtsHold member of COMSTAT.
0x0040 CE_DSRTO DSR (data-set-ready) timeout. While a character was being transmitted, DSR was low for the duration specified by the fDsrHold member of COMSTAT.
0x0080 CE_RLSDTO RLSD (receive-line-signal-detect) timeout. While a character was being transmitted, RLSD was low for the duration specified by the fRlsdHold member of COMSTAT.
0x0100 CE_TXFULL Transmission queue was full when a function attempted to queue a character.
0x0200 CE_PTO Timeout occurred during an attempt to communicate with a parallel device.
0x0400 CE_IOE I/O error occurred during an attempt to communicate with a parallel device.
0x0800 CE_DNS Parallel device was not selected.
0x1000 CE_OOP Parallel device signaled that it is out of paper.
0x8000 CE_MODE Requested mode is not supported, or the idComDev parameter is invalid. If set, CE_MODE is the only valid error.
To use this table, take the error number and disect it into its error components. Fo
r example, if Serial Port Write.vi returns the error 16,408, then the errors returned are CE_BREAK and CE_FRAME (16,408 = 16,384 + 16 + 8 = 0x4000 + 0x0010 + 0x0008).
