The only advantage of serial compatibility is cross-platform, and you
get this with visa too. If you are creating an exe then you have to
install the visa runtime engine. If you want to stick with Windows
programs I have found that the MSComm control called with activex is
much more flexible. Also, in order to get write access to the MS Comm
control (writing a LabVIEW program) you have to install some trivial
microsoft enviroment like visual basic, this licenses the control for
both writing and using. When you distribute the application the control
is automatically licensed for use.
Anyway, thanks for the app note on serpdrv.
Tom at Onset wrote:
> I recently upgraded from Labview 6.02 to Labview 7.0 and found that my
> application could no longer open or commu
nicate via a serial port.
>
> My application uses and I prefer the old serial compatibility VI's
> because I had trouble with the VISA serial VI's. And the new, Labview
> 7.0 turned the old serial compatibility VI's into VISA serial VI's.
>
> For anyone interested in using the old serial compatibility VI's, here
> is one way to get them back, and working properly.
>
> 1) Find a computer with an older version of Labview, probably 6.02 or
> older.
>
> 2) Replace the following v 7.0 *.llb files: "_sersup.llb" and
> "serial.llb" with these v 6.* or earlier files: "_sersup.llb" and
> "Serial.llb".
>
> 3) Also copy this file "serpdrv" from your root v 6.* or earlier
> folder into your root v 7.0 folder.
>
> That worked for me.
>
> I sincerely hope that Labview will consider replacing the serial
> compatibility vi's in any future versions or patches with the original
> ones.
>
> Tom