LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

My Application gets Error 37 when using Serial Port VIs.

My Application works fine developed with LV 6.1. Then I updated to LV 7.1 and now the Executable of my application gets error 37 when using the old serial port functions. The "serpdrv" file is located in the application directory and is from 02/2002. The application runs well in the development environment after I placed the "serpdrv" file in the LabView directory. I tried to put a line with "serialDevices=..." in the .ini-file of my application but this did not cause an improvement. I also tried to rebuild the EXE with this line in the "labview.ini" file but nothing changes.

Does anybody have another idea ?

Many thanks for help
Thomas
0 Kudos
Message 1 of 4
(2,795 Views)
Did you actually replace the old serial functions that come with 7.1 with the functions from 6.1? The old serial driver serpdrv was dropped in LabVIEW 7 and the compatability functions of the same name actually use VISA. Open the serial functions in your VI and see if they're calling VISA at the lower levels. If that's the case, you need to install VISA. When you build an app, you can choose to include serial support when you create the installer. Click the Advanced button on the Installer tab.
0 Kudos
Message 2 of 4
(2,794 Views)
>Did you actually replace the old serial functions that come with 7.1 with the functions from 6.1?
Yes. E.g. "open serial driver.vi" uses "open device" with "serpdrv" as device string.

I had the same problem running my application as VI´s. After the copy of serpdrv into the LV 7.1 directory everything works fine.
I don´t understand why the application running as a .exe doesn´t find the serpdrv when it is in the same directory....

Nevertheless many thanks for your answer
Thomas
0 Kudos
Message 3 of 4
(2,776 Views)
Now i have the solution.
It is necessary to copy the serpdrv file into the 7.1-Runtime Engine directory under "NI/shared..."

Therefore the information to put this file into the application directory is wrong. (a little change with a big effect...)

Thomas
0 Kudos
Message 4 of 4
(2,763 Views)