Anyone know why error 37 occurs for Serial port vis using LabVIEW 5.1.1 under Windows 2000? The serpdrv file is in the directory.

[jkj]

Is there something else I need to set for the operating system? I am running LabVIEW 5.1.1 under WINDOWS 2000. Serpdrv is in the directory.

[Niko]

I run a labview runtimeapplication using a COM port in Win2000 and do not
get any error. Are you sure the problem is in win2000? Error 37 is "port not
available", may be the port is used by an other program, does't exist, ...

Niko

[franckfischer]

Hello Niko,

In your VI, you are asked of the port number, what have you specified ? On my PC/notebook, I have only COM1, so I suppose that the port number was 0 but I always get error 37.
Thank you for your help.

Franck.

[MartinP]

Franck
See below.
Martin
*****


Subject: LabVIEW 6.1 serial port issue
From: "Brian H. Powell"
Date: Fri, 25 Jan 2002 15:04:12 -0600

Thanks to a lot of help from Lew Drake, we figured out what's happening
with his serial port not working with the serial compatibility VIs. The
problem only occurs if you install the LabVIEW Datalogging and Supervisory
Control (DSC) add-on product to LabVIEW.
It turns out that the LabVIEW DSC module inserts an incorrect line
into the labview.ini file. This causes us to try to open the wrong COM
port.
Specifically, the DSC installer adds:

serialDevices="COM1;COM2;COM3;COM4;COM5;COM6;COM7;COM8;COM9;LPT1;LPT2;LPT3;L
PT4;

(That should be all on one line, but I'm not sure if it'll be word-w
rapped
when I send this message.)

Anyway, there's a leading quote on that line, but no trailing quote, so we
don't strip the leading quote. Thus, we try to open "COM1 (with a leading
quote). This doesn't work and you get the all-time-favorite serial error
37.
The fix for most people is to remove this line from your labview.ini
file after DSC is installed. If you don't have the DSC module, you won't
see this problem at all.

I will again encourage people to use VISA for all future serial port
development. At some point, I would like to see the "serpdrv" VIs go
away. (And since I'm the decision-maker on this, it'll probably
happen. 🙂
There'll be a Knowledgebase article for this soon, and it should be
fixed in the next release of the DSC module. (There are no immediate
plans to re-release it since this issue has a simple workaround.)

Brian




"franckfischer" wrote in message
news:506500000005000000CD5B0000-1011517314000@exchange.ni.com...
> Hello Nik
o,
>
> In your VI, you are asked of the port number, what have you specified
> ? On my PC/notebook, I have only COM1, so I suppose that the port
> number was 0 but I always get error 37.
> Thank you for your help.
>
> Franck.

[franckfischer]

This line wasn't it my labview.inifile. Even if DSC module isn't installed on my PC, I have tried to add this line in labview.ini file but there is no change.

[abrause]

Perhaps there is a conflict with another process using the port, like your modem for instance? Is
the port functioning properly? Can you use HyperTerminal to talk to your device to your instrument
to test the port?

Make sure the port is working before you attempt to use LabVIEW.


"franckfischer" wrote in message
news:506500000005000000525C0000-1011517314000@exchange.ni.com...
> This line wasn't it my labview.inifile. Even if DSC module isn't
> installed on my PC, I have tried to add this line in labview.ini file
> but there is no change.

[jcrooke]

I'm concerned about the non-VISA serial port functions going away. For one thing, the VISA serial functions don;t allow longer than 0.5 seconds of break length.
-jayme

[Parks]

"jcrooke" wrote in message:

> I'm concerned about the non-VISA serial port functions going away.

Simple fix, never upgrade. That'll make'em think twice about eliminating
Serpdrv.

> For one thing, the VISA serial functions don;t allow longer than 0.5
> seconds of break length.

Only one of the issues.

Join the "Save our Serpdrv Foundation" today.