10-13-2005 05:42 PM
Thanks.
10-14-2005 05:13 PM
10-14-2005 05:30 PM
Don't use COM3 or COM4 strings, just use simple port no like:
OpenComConfig(3, "", 115200, 0, 8, 1, 4096, 4096);
10-17-2005 04:21 PM
I am using LabWindows/CVI version 6.0.
status = OpenComConfig( 3, "", 115200, 0, 8, 1, 32000, 3200 );
status2 = OpenComConfig( 4, "", 115200, 0, 8, 1, 32000, 3200 );
There seems to be no impact whether the "COM3" or "COM4" string names exist or not. I put that there due to help documentation for OpenComConfig() call. The value for <status2> is still "-7" (invalid port).
If I change the 2nd call to OpenComConfig() from 4 to 3, the error does not exist (status2==0), but writing to port 4 does not work - ComWrt(4, ...) fails.
status = OpenComConfig( 3, "", 115200, 0, 8, 1, 32000, 3200 );
status2 = OpenComConfig( 3, "", 115200, 0, 8, 1, 32000, 3200 );
Different/related question: A co-worker told me that since COM3 and COM4 are configured for two ports from the same card, that two different CVI applications cannot handle it? That OpenComConfig() takes hold of the handle for the card, so opening COM3 does not allow COM4 to be opened from a different CVI application? That is why I wanted to get this program with merged two apps together work. Thanks.
02-14-2007 05:03 AM
The CVI functions (OpenComConfig, ComWrt, ComRd, etc) works fine with my FastCOM PCI-422/4.
You can use the serial.exe program to verify that. The program is in the samples folder. Even if you run multiple instances (for my board max 4) of the program (each for a different port) there are no problems reported and you can do a loopback testing on all ports at the same time.