We are using a 9-bit protocol which sometimes sends a mark state and sometimes sends a space stage. When a space state is sent we want to be able to get a parity error in SDK. We can see the parity error in the hardware register but we want to be able to see the error with Windows SDK software. When we connect to a standard 232 serial port on a PC we are able to see the errors in SDK but when we add serial ports with the PCI card we are having unable to see the parity errors with the SDK software from Windows.
- We are using the OVERLAPPED I/O functions from the windows SDK.
- Parity errors are not detected by the driver. When using the SDK function "ClearCommError", we get no parity errors in the status flags.
- The characters are received very slow. When sending for example +/-25 characters at once. It takes about 500 milliseconds, before the driver has given the characters to the windows SDK. When sending a lot of data we detected delay's of more than a minute. And no, this has nothing to do with the limited baudrates. When disconnecting the serial cable, we still receive data from the serial port for more than a minute. Please check yourself using the OVERLAPPED I/O functions of windows.
We get the impression that the hardware is OK, but the driver has bugs in it. Any ideas?
June 1, 2006 2:26 PM
June 6, 2006 6:37 PM