Here is more info:
http://forums.ni.com/ni/board/message?board.id=170&message.id=117853
Look at the post from Dennis:
" I always thought that the old ones were confusing with Com1 being port 0, Com2 is port 1, etc. ...
As far as conversion, in the majority of cases I've seen, the conversion was transparent. Loading an old program with the traditional functions will have VIs with the old names but with VISA calls internally. The old port numbers get converted to VISA Resource Names, etc. "
So I would look at the VISA Resource naming of the serial ports. That may be where your problem resides..
However, if you plan to redo the serial communication "from scratch" in LV7.x, then here is a bit of info:
++++++++++++++++++++++++
Initializing the serial Port in LV7:
1. Go to the block diagram.
2. In the Functions Palette, select => Instrument IO => VISA => VISA Advanced and place the VISA Open vi on the block diagram.
3. Wire a "VISA resource name" control to the VISA Open vi. Also wire the Error-IN / OUT clusters appropriately.
4. Select the COMM port that you wish to use to connect to your instrument. (ex: COM1).
5. In the Functions Palette, select => Instrument IO => Serial; this is where you will find most of the useful VISA vi's relating to the serial communication.
6. Place the VISA Configure Serial Port.vi on the block diagram. You can wire the settings to this vi. You can use the Context Help for details (it is useful to show the connectors on the vi).
You can start with the following vi's:
a) "VISA Bytes At Serial Port" which indicates how many bytes are available top be read at the serial port buffer.
b) "VISA Write" Wire the string that you want to transmit to this vi. This vi also provides a return count for the number of bytes at the serial port (echoed data for instance).
c) "VISA Read" Reads the serial buffer as an output string. This is where you will want to wire the byte count (as an input) from the two vi's above.
d) "VISA Close" A very important vi, because it closes the communication session to the COMM port. Very useful if you switch back and forth with a software like HyperTerminal.
I think that this should get you going with the serial port communication. You may want to implement some sort of a loop (while for instance) in order to read the data from the serial port buffer until it is empty. Depending on the speed of the communication, you may also want to place a delay within the loop.
Ray
Message Edited by JoeLabView on 11-04-2005 10:33 AM
