Error 42 at init serial port

I built a simple application using LabView 7.1 using serial ports and using VISA . I finish the project and built the installer. on the development PC I test the application (from the "start" menu, and it run correctly. when I try to insall it at another PC (after checking that the appropirate port is valid) I have got an error message "Error 42 occured at Init Serial Port"what could be the reason for this problem
Haim

I am using 7.0 but have never used 7.1. But check out this setting. It may help
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)
Attachments:
sample.PNG ‏32 KB

Similar Messages

Strange init serial port issue

Hello:
My Labview application is reading data from the COM1..COM6 ports (I have
added a MOXA serial board to get 4 more ports). I am using RS232 reading
on each port (old legacy Vis, 9m long communication cables). The devices to which I am connected are weigh scale that continuously send weight readings to the Labview app through 3-wires RS232 (RD, TX and GND). Everything goes well for hours and hours. Then after a while (maybe after power is cut and restarted on the PC side?) I restart the PC and launch Labview. If I try to init the serial port that I use to connect to the weigh scale I get an error 37. I also tried to init thru HyperTerminal right after restarting the PC and could not. The only thing that works to unlock the port is
this:
- unplug the weigh scale communication cable from the Moxa connector
- restart the PC
- relaunch LV or HyperTerminal
Unplug then restart Labview or HyperTerminal is not sufficient.
To the same Moxa board I connect other devices such as PLC or PC through serial ports but never see any problems even after restarting the Host PC. So there is something strange with weigh scales (I tried two different brands) but what? I cannot use the built-in serial port as it is already in use by another application.
Does someone out there have an explanation and ways to avoid this very annoying problem?
Thank you very much, I am completely lost,
Christophe

Chris:
Thank you for your help. I investigated the problem further and this is what I found. I am still clueless so if you think of other tracks that I might explore I would be glad to hear them.
- Hard boot (power off, remove power cord, restart) does not release the port
- I change the port ie. I used the built-in COM1 PC port, got the communication, could read char, then restarted the PC and fell into the same trap: could not init the port (Labview). I did the same after restarting and could not open the port with HyperT. Hence it is not a Moxa issue.
- The question is: how can I resolve that, is it an HW or SW issue, a combination of the two, has it got something to deal with WIndows 2K, are there some tools that allow to diagnose whi
ch service or application grasps the serial port during the boot sequence? Or is it a problem during the shutdown sequence that the port is not released properly?
TIA,
Christophe

Error 37 with serial port / no with hyperterminal

I have added to my Pc a card with two serial port, I can access to them by hyperteminal or by labview but only at port 0 and 1 at the same time or 2 and 3, if not I have an error 37. What can I do?

Error 37 means that LabVIEW cannot find the appropriate serial device. This indicates that one of the following conditions exists:
LabVIEW cannot open the specified serial port;
LabVIEW cannot find the file serpdrv.
Make sure that the serial driver was installed before the board, and that the com ports appear normally in the control panel. If you cannot get it working, contact NI through either phone or email support. Since there are several potential causes, this is difficult to diagnose without more information. You can contact NI using the following webpage.
http://sine.ni.com/apps/we/niae_asc.main
Kim L.
Applications Engineer
National Instruments

Error 37 using serial port with an executable file

Hi all,
I have developed a VI that controls a setellite receiver using RS232
serial port (LabVIEW 5.1.1).
The VI program run properly, but when I compile it and try to run the
executable file I receive an "Error 37, Device not found" error message.
I have already put serpdrv and my_file.ini files in the same directory
of my executable program my_file.exe, but I have not been able to solve
the problem.
Any help greatly appreciated.
Regards
Antonio
Sent via Deja.com http://www.deja.com/
Before you buy.

[email protected] wrote:
>
> Hi all,
> I have developed a VI that controls a setellite receiver using RS232
> serial port (LabVIEW 5.1.1).
> The VI program run properly, but when I compile it and try to run the
> executable file I receive an "Error 37, Device not found" error message.
> I have already put serpdrv and my_file.ini files in the same directory
> of my executable program my_file.exe, but I have not been able to solve
> the problem.
> Any help greatly appreciated.
>
> Regards
>
> Antonio
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Maybe you used the serpdrv from an older version of LV
Regards, Roland
Roland Lampka - Nortel Dasa - ESN 565-7257 - FAX 8160

Street Atlas 6.0 error message No Serial Ports Available (have Keyspan 19)

Each year we travel the Pacific Northwest most of the summer in our motorhome.(To hot down here in Texas) I have been using Street Atlas USA 6.0 on my G3 366 IBook with a Garmin E-Map and a Keyspan USA-19 USB to Serial adaptor for five years. This version runs only on OS9. Garmin refuses to produce a OS 10 version. Worked well. Last year had problem with IBook including failed CD Drive. (IBook has traveled 85,000 miles in the motorhome) Had to replace CD drive, and did a clean install of OS10.2.6 and updated it to 10.2.8. (Need OSX for WiFi access when traveling) Did clean install of OS 9.2.2. Reinstalled Street Atlas, Keyspan driver (2.5) and extension and control panel, and reconnected the EMap GPS receiver. Inserted the Keyspan device into the USB port. (USB works with printing, scanning, etc.) Executed Street Atlas, and attempted to initalize the GPS, received error message from Street Atlas 'There are no serial ports available'. Replaced the Keyspan adaptor, reloaded software, same problem.
Question: Has anyone else had the same problem, and resolved it? Does anyone know of potential extensions which would cause a conflict causing this?
I have looked in Route 66, but the reviews on Amazon are pretty bad, calling it crap software. Has anyone had experience with it on a similar hardware/software set up?
I considered buying a new i-book, but without an acceptable application to run under OS X, that would be useless.
Help
G5-20"IMac & G3-I-Book Mac OS X (10.4.3) I-Book runs OS X 10.2.8 and OS9.2.2

Hi, I had the same configuration and problem, I hope a simalar fix will work for you. In classic Search for "Keyspan USA-19W Manager", open it up and check the box for "Emulate Printer Port". Go back and try Street Atlas 6.
Regards, Kirhofer

An error about reading serial port

Hi,
I have sent 5 bytes(for example: "0","2","F","1","/n") to serial port and used VISA Read. But I only can read 0. The right result is in the second line of the read string window, The first line is void. Generally speaking, "02F1" should in the first line,then I can read them correctly. The following picture is the result.
Thank you!
帖子被hengfo在09-17-2007 03:57 AM时编辑过了
Attachments:
read string.JPG ‏6 KB

Hello,
you should add a flat sequence with some extra e.g. 50ms delays between the visa writes and reads, that helped us a lot.
You should also specify a large enough buffer. And don't forget to send the terminating CR and LF.

Build Error: "VISA Configure Serial Port"

Hi,
I want to upgrade some old 6.i vi's to 8.5
But on building the project i am getting an Error:
Please take a look in to the screenhots
Greetings from the lake of Constance, Germany
juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=
Attachments:
MESSAGE.jpg ‏106 KB
VI-LIB.jpg ‏783 KB

Hi j_dodek, there is a function called "mass compile", did yoou already try this option?
Please select Tools»Advanced»Mass Compile and choose the directory containing your old VI's. This will upgrade all the files in the directory or library.
Please also have a look at the linked document that describes what the function mass compile does:
http://digital.ni.com/public.nsf/websearch/654877E62A97B72986256C95006F9B24?OpenDocument

[SOLVED] How to set non-root access to serial ports?

I have this device which is listed as
/dev/ttyUSB0
I need to
sudo chown sms /dev/ttyUSB0
every time I reboot. Normally I would think to add myself to some group but "tty" group is not doing the trick... proof:
[sms@sms-linux ~]$ groups sms
tty wheel sms
[sms@sms-linux ~]$ MinOZW
Starting MinOZW with OpenZWave Version 1.0.758
2014-03-15 06:32:07.921 Cannot find a path to the configuration files at ../../../config/, Using /usr/local/etc/openzwave/ instead...
2014-03-15 06:32:07.928 mgr, Added driver for controller /dev/ttyUSB0
2014-03-15 06:32:07.929 Opening controller /dev/ttyUSB0
2014-03-15 06:32:07.931 Trying to open serial port /dev/ttyUSB0 (attempt 1)
2014-03-15 06:32:07.933 ERROR: Cannot open serial port /dev/ttyUSB0. Error code 13
2014-03-15 06:32:07.935 ERROR: Failed to open serial port /dev/ttyUSB0
2014-03-15 06:32:07.936 WARNING: Failed to init the controller (attempt 0)
^C
[sms@sms-linux ~]$ sudo MinOZW
[sudo] password for root:
Starting MinOZW with OpenZWave Version 1.0.758
2014-03-15 06:32:23.776 Cannot find a path to the configuration files at ../../../config/, Using /usr/local/etc/openzwave/ instead...
2014-03-15 06:32:23.782 mgr, Added driver for controller /dev/ttyUSB0
2014-03-15 06:32:23.784 Opening controller /dev/ttyUSB0
2014-03-15 06:32:23.786 Trying to open serial port /dev/ttyUSB0 (attempt 1)
2014-03-15 06:32:23.794 Serial port /dev/ttyUSB0 opened (attempt 1)
Edit: yes, it was after logout and even reboot.
Last edited by smsware (2014-03-15 15:07:15)

Hi,
I also have a similar problem. I added myself to uucp group, but I still cannot access the serial port.
[manjaro@mycomp work]$ sudo gpasswd -a manjaro uucp
[sudo] password for manjaro:
Adding user manjaro to group uucp
[manjaro@mycomp work]$ groups manjaro
lp wheel uucp network video audio storage users
[manjaro@mycomp work]$ ls -l /dev/ttyUSB0
crw-rw---- 1 root uucp 188, 0 23.06.2014 21:32 /dev/ttyUSB0
[manjaro@mycomp work]$ lpc21isp firmware.hex /dev/ttyUSB0 19200 11059
lpc21isp version 1.97
File firmware.hex:
loaded...
Start Address = 0x00004F9C
converted to binary format...
image size : 30304
Image size : 30304
Can't open COM-Port /dev/ttyUSB0 ! (Error: 13d (0xD))
But when I try as root, it works:
[manjaro@mycomp work]$ sudo lpc21isp firmware.hex /dev/ttyUSB0 19200 11059
[sudo] password for manjaro:
lpc21isp version 1.97
File firmware.hex:
loaded...
Start Address = 0x00004F9C
converted to binary format...
image size : 30304
Image size : 30304
Synchronizing (ESC to abort)..... OK
Read bootcode version: 13
Download Finished... taking 27 seconds
Now launching the brand new code
Do you have any idea what I am doing wrong?
Last edited by manjaro (2014-06-23 19:57:40)

List serial port fail in and I have exhausted all combination

Background: If admintool can set serial I could have set it with a click.
The error is "list serial port fail in "
url:geocities.com/worldlinking/index.htm
SO please help and guide.
sunlearner.

I have exactly the same problem:
ASUS A7V133 Motherboard, Athlon 1.33Ghz
Solaris 8 Release 10/01.
ALL Recommended and Security patches installed.
Device Config Assistant lists the ports as standard 16550 UARTS, which is correct - ASUS mention nothing 'special' about them.
prtconf shows both ports with asy not attached.
devfsadm does not change that. ports command has no effect.
No /dev/tty/ttya or /dev/tty/ttyb or /dev/term/a etc.
admintool says 'list serial port failed'
ttymon has service entries for ttya and ttyb :
#pmadm -l -s ttya
zsmon ttymon ttya u root /dev/term/a I - /usr/bin/login - 9600 ldterm,ttcompat ttya login: - tvi925 y
Any help greatly appreciated,
--john

Connection to serial port via USB adapter- error -2147221503

I am trying to drive a stepper motor provided with possible Labview or VB programs. This motor is supposed to be connected via serial port, but the computer has not some, so I bought an USB adpater to connect my motor via USB. I am using the labview programs provided (Labview 8.0). The program cannot connect to the port and returns error -2147221503. Where may I find some help with that ?
Thanks
Attachments:
error labview.JPG ‏234 KB

I see references to 'Luminos'. Is this the provider of the stepper motor and LabVIEW code? If so, your first step should be to contact them. The whole VI is nothing but ActiveX properties and methods and the vendor would be the only one who knows what is going on.

Getting error in call library node when establishing communication with MAX1452 on serial port using dll

I want to communicate with MAX1452 in labview on PC serial port. Maxim provides dll file which has functions to communicate with device.It says first two functions should be findcom port and initialization sequence where findcom port returns PC's serial port address while initialization sequence helps device to learn baud rate.Iam not getting exception error in call library node.i have kept dll file in the same location as VI.

Labview verison is 7.1 and os is win xp.
The data types are according to the dll functions defined in functions definitions( attached previously).
I'd put dll in the same directory where the code resides.
Attachments:
Code.vi ‏23 KB

How can I define the start bit in Serial Port Init VI?

I don't know if the number of start bits of the Serial Port Init VI match with the serial communications requirements of the device I need to communicate with.
Is there any way of modifying this parameter?

LabVIEW uses the standard WindowsAPI for all of its serial functions. As such, LabVIEW does not support a customizable start bit since the native serial driver does not.

I CAN NOT find serial port init.vi

In labview8.6 , I CAN NOT find serial port init.vi.
Other lots of icon can be found.....

Dennis Knutson wrote:
for(imstuck) wrote:
That's because it is called VISA Configure Serial Port. It is located in Instrument I/O->Visa->Visa->Visa Advanced-> Bus Interface Specific -> serial.
And there it is. Sometimes you really gotta dig!
You enjoy taking the long way there?
Message Edited by Dennis Knutson on 05-20-2010 05:48 PM
I just did a search of the palette and thats where it took me so thats what i posted to help the OP. Besides, sometimes the scenic route is nice. You pass lots of beautiful VIs on the way to your destination that you may have never known existed. And, I actually prefer the quick drop way .
Message Edited by for(imstuck) on 05-20-2010 08:35 PM
CLA, LabVIEW Versions 2010-2013

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

>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

Serial port init frequency

I currently use LV to dialog with an RS232 device via the serial port.
How often does I have to re-init he serial port?
For the moment, I do it each time I want to send a string to the device.

perform a "dummy" read of the serial port and throw away the data before
sending the serial command.
that way you know the buffer is empty before you expect data.
Stu
"Zen" wrote in message
news:[email protected]..
>
>
> Johannes Niess a écrit :
>
> >
> > In theory: Once. It depends on whether you have an initialisation
> > phase or want to avoid it. If you don't need high speeds, you can
> > leave it the way it is.
>
> I send a string everery two seconds, and raed the reponse from the
> device. I just don't know if the serial buffer is emptied before
> receiving the response string. If not, there might be left old caracters
> causing a wrong response string.
Stu McFarlane
Viewpoint Systems, Inc.

Error 42 at init serial port

Similar Messages

Maybe you are looking for