Hi Nandini,
I'm trying to do this strictly through LabView. Here's the whole deal:
One of the guys I'm working with has a unique serial comm application. Some of our legacy equipment uses 9 bit serial data comm. Comm is one byte at a time, but the port must be serviced immediately. In the past, he was able to interpret the 9 bits by looking at the parity bit and attach it to the byte that came across the serial port. Now apparently, LV7 insists on replacing the byte sent with a "replacement byte" whenever there's a parity error (app previously built in an older version). He's tried a few workarounds with little success. Oh, and he has to do this on two serial ports simultaneously at 115K baud.
He's now using a third party serial port driver that he may have some success with by polling the ports. I'm trying to use the native Windows stuff and make it Event driven. The problem is I don't think I can uncover the OnComm Event through LabView. It looks like the event's available through .Net 2.0 (not available through .Net 1.1), but there are compatibility issues with 2.0 and 7.1. Compatibility issues are fixed in LV8 or with LV7.1.1 and patches.
At this point, I think we'll probably just wait for 8.0 to show up and take another swipe at it using .Net 2.0.