serial port recognition issue in labview 7 (error -1073807343)

[DustinS]

I am getting error -1073807343 (Insufficient location information or the device or resource is not present in the system.) with a program written in labview 7 (installed on a different computer).
I installed drivers for a "legacy" DAQ card (from the disk that came with it), the labview runtime environment, and the serial port driver from the NI website.
I opened the Measurement & Automation explorer and made sure the serial port drivers were installed, and that the alias of serial port 1 was "COM1".

I noticed that a lot of the drivers go back to 7.1.  Do I have to install an earlier version of the serial drivers?

[Dennis_Knutson]

What serial port driver are you talking about? Unless you are using an NI serial card, the only driver you need to install is NI-VISA. It should not matter if you are using a newer version of NI-VISA.

For this other program, do you know what serial port it is trying to access? Do you have the option to select a port with the VISA Resource Name control? Is this other program an exe?

To see which port the program is actually trying to access, go to MAX and turn on NI-Spy. It will log the calls to the port. Attach the result of the NI-Spy capture if you want.

[dsoodak]

I tried NI spy and it was trying to access the correct serial port (COM1). I'm troubleshooting this remotely (with GOTOMEETING), and the other guy is currently out to lunch so I can't give the exact response.

Usually, the DAQ device driver CD installs everything needed for this program. For this particular computer, 2 dlls had to be manually put into the Windows system 32 folder before it ran at all.

Then I had to install a VISA driver from one part of the NI website and a serial/paralell driver from another part of the site before the Measurement & Automation Explorer would recognize the serial ports.

I'll post the NI spy output when I get re-connected to the customer's computer.

thanks for the reply,

Dustin

[dsoodak]

This is from the customer's computer when the labview executable tries to connect to COM1:

1.  viParseRsrc (0x015CB068, "COM1", 0, 65535)
Process ID: 0x000003B4         Thread ID: 0x00000434
Start Time: 13:33:48.266       Call Duration 00:00:00.015
Status: 0xBFFF0011 (VI_ERROR_RSRC_NFOUND)

2.  viOpen (0x015CB068, "COM1", 4, 0, 0x00000000)
Process ID: 0x000003B4         Thread ID: 0x00000434
Start Time: 13:33:48.281       Call Duration 00:00:00.000
Status: 0xBFFF0011 (VI_ERROR_RSRC_NFOUND)

3.  viParseRsrc (0x015CB068,
"COM1", 0, 65535)
Process ID: 0x000003B4         Thread ID: 0x000003DC
Start Time: 13:33:48.469       Call Duration 00:00:00.000
Status: 0xBFFF0011 (VI_ERROR_RSRC_NFOUND)

4.  viOpen (0x015CB068,
"COM1", 4, 0, 0x00000000)
Process ID: 0x000003B4         Thread ID: 0x000003DC
Start Time: 13:33:48.469       Call Duration 00:00:00.000
Status: 0xBFFF0011 (VI_ERROR_RSRC_NFOUND)

5.  viParseRsrc (0x015CB068, "COM1", 0, 65535)
Process ID: 0x000003B4         Thread ID: 0x000003DC
Start Time: 13:33:48.484       Call Duration 00:00:00.000
Status: 0xBFFF0011 (VI_ERROR_RSRC_NFOUND)

This is from my computer:

1.  viParseRsrc (0x0242E768, "COM1", 4, 1)
Process ID: 0x00000B88         Thread ID: 0x00001090
Start Time: 13:59:52.149       Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

2.  viOpen (0x0242E768, "COM1", 4, 0, 0x07614660)
Process ID: 0x00000B88         Thread ID: 0x00001090
Start Time: 13:59:52.149       Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

3.  viGetAttribute (COM1 (0x07614660), INTF_TYPE, 4)
Process ID: 0x00000B88         Thread ID: 0x00001090
Start Time: 13:59:52.149       Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

4.  viSetAttribute (COM1 (0x07614660), TMO_VALUE, 10000)
Process ID: 0x00000B88         Thread ID: 0x00001090
Start Time: 13:59:52.149       Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

5.  viSetAttribute (COM1 (0x07614660), ASRL_BAUD, 9600)
Process ID: 0x00000B88         Thread ID: 0x00001090
Start Time: 13:59:52.149       Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

[Dennis_Knutson]

It does look like the other computer is not recognizing com1. I'm curious about the manual installation of a couple of dlls and your statement that you had to install a serial/parallel driver. What were the dlls and what was this separate serial/parallel driver? There are no separate 'serial/parallel' drivers required and I don't know what you are referring to.

You might want to uninstall what you placed on this other pc and then try doing a reinstall.

[dsoodak]

The dlls were just for the data aquisition card (niidaq.dll and niidaq32.dll).

The strange thing is that "Measurement & Automation Explorer" is having no problem recognizing the serial port(after I installed the NI serial port driver).

Its just the labview(7.0) run-time environment that is having trouble.

[Ben]

Are you attempt ing to get an exe running?

Check if you have alias's defined in your app's ini file.

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

There was also a VISAconf.ini (?) that used to be used to map the ASRL to COM's

Ben

[dsoodak]

I just tried adding the serial port alias list to the ini file. didn't do anything.

I've run this on lots of computers and never had this problem before (usually, if there was an issue, it was with the DAQ card, not the serial port).

I might just have to start uninstalling and re-installing various combinations of drivers till I get one that works.

[Dennis_Knutson]

Ben's got a good  point. The visaconf.ini should be located in the \vxipnp\winnt\NIvisa folder. If you installed just the VISA run-time, then the aliases did not get set in older versions. I'm still curious about why you installed the NI serial driver. It is not required at all unless you are using an NI com port board. For com ports built-in the pc, it is not necessary to install it to see the ports in MAX