Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

serial port init

I'm getting error 37 on Serial Port Init: Device not found.  Does anyone have a serial loopback VI?  I'm using LV 3.1.
Thanks
0 Kudos
Message 1 of 4
(3,682 Views)

Version 3.1!Smiley Surprised

One thing to be aware of is that with this old serial driver, you need to specify port 0 for Com1, port 1 for com2, etc.

I don't know of any existing examples in version 3.1 and there is no way to save a VI from a more recent version to 3.1. All a serial loopback VI has is a write followed by a wait, followed by byte count and read. Here's a picture.

0 Kudos
Message 2 of 4
(3,676 Views)

LV 3.1 .... o that sweet memories, when I had my first contact with LabVIEW ...... 

I can't lookup what error 37 means, but it's explained somewhere in the LV3.1 documentation, maybe even in paper, I remember the LV3.1 function reference manual  in paper ...

 

Common pitfalls:

COM1 is port 0    (Dennis already mentioned)

the port is blocked by the system (your device is recognized as a systemdevice (mouse)), diconnect the dev. on bootup.

the port is blocked by an other application

on notebook: powerup without powersupply disable the comport to save power

 

If it runs with hyperterm  (or terminal.exe??, LV3.1 was windows 3(.1)) , it will run with Labview  

A question I don't know: will the serdrv.dll of LV3.1 run with W2K and higher???

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 3 of 4
(3,656 Views)
If I am not mistaken, in those old days, a file called serpdrv was needed to use the serial and parallel ports with LabVIEW. Furthermore, it was sometimes necessary to edit WIN.INI. Therefore, the port could run with Hyperterminal and not with LabVIEW.

See the documents on this page for more details.
0 Kudos
Message 4 of 4
(3,651 Views)