LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

When running a LabView exe, I get Error 10001

Ultimately, I am trying to copy a stand-alone executable labview program from one computer to another. When I try to run the program and acquire data through the DAQ, I get "Error -10001 occured at AI Group Config." The code was written by an engineer who is no longer here.
 
Specs on computers:
Original: Windows 98 platform, no LabView installed
New: Windows XP platform, no LabView installed
 
Specs on executable:
Originally written using LabView 6.0. I've updated the Run-Time Engine in the new computer with RTE 6.1. There is also no "install" file included, only an "uninstall" file.
 
Components: In order to duplicate the original computer setup, we recently purchased identical components.
BNC-2120
NI PCI-6023E... installed Traditional (Legacy) driver in new computer using XP platform
 
-How can I resolve this without being able to modify the code itself?
-What am I missing here?
-Do I need to use Windows 98 on the new computer in order for this stand alone exe to work?
I have minimal experience in LabView, so any assistance is useful.
0 Kudos
Message 1 of 8
(4,695 Views)

If the original executable was written in LabVIEW 6.0, then you must have the LabVIEW6.0 runtime engine installed. The 6.1 engine will not work. But since it sounds like the application is running (you're getting a DAQ error), then I'm guessing that the 6.0 RTE has been installed, or the code was actually written in 6.1.

My best guess for the DAQ error is probably in the configuration of the DAQ card. If you go to the Win98 machine, you should find a program called "Measurement and Automation" Explorer. Normally there's an icon on the desktop. If not, look in the Start Menu>Programs>National Instruments. This is an application that gets installed with the DAQ driver that is used to configure the DAQ devices.

Open this and look in the tree on the left. Expand the "Devices and Interfaces" category. There should be a subcategory named "Traditional DAQ Devices" or something like that. Expand that and you should see the PCI-6023E card. After the card, there's another name. Possibly "Dev1", but it could be anything.

Now go the WinXP machine and look in the "Measurement and Automation" explorer for the DAQ card. Make sure it has the same name after the card name. Right click and Rename if it's not.

Give that a look and let us know if that takes care of it or not.

Ed



Ed Dickens - Certified LabVIEW Architect
Lockheed Martin Space
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
0 Kudos
Message 2 of 8
(4,684 Views)

Hi Ed,

Thanks for your reply. Unfortunately, there was no difference in the labeling of the devices. In the Win98 and XP computer, the PCI-6023E are aleady both labeled as Device 1.

Any other suggestions or next steps to try?

One thing I am going to try is instead of using an XP computer, I will use another Win98 computer and duplicate the original system. Do you think the computer's platform has any bearing on whether this executable will work or not?

Regards,

Ken

0 Kudos
Message 3 of 8
(4,665 Views)
 

MagCor:

As Ed eluded to earlier, if you created an executable using LabVIEW 6.0, only a computer with the RTE 6.0 installed will be able to run the application. Furthermore, if your application uses Traditional DAQ drivers, you will need to make sure that those drivers are installed on the other computer. The LabVIEW Run-Time Engine gives you the ability to access all native LabVIEW functions. To use applications that rely on the DAQ drivers, you can either install the Traditional DAQ driver or create an installer instead so that you can include the DAQ driver in it.

I hope this helps and please let me know how I can help you further.

Regards,

Rudi N.

0 Kudos
Message 4 of 8
(4,658 Views)
Hi Rudi,
 
I've created another computer using Win98 platform, instead of XP, so I can duplicate the exact setup.
  • I verified the DAQ driver on the original computer, which is Traditional NI-DAQ 6.9.1, and downloaded that software and installed it into the duplicate computer.
  • I verified the PCI device number; they are both "Device 1".
  • I installed LabView RTE 6.0.2, which is the requested RTE in order for the executable to open, which it does. The exe will not let me open it until I've downloaded the 6.0.2 RTE
Result:  I still get the same error.
The only difference I see in the MAX software tree in the original (working exe) versus the duplicate (non working exe) is that the original also has LabVIEW Run Time 7.0. Could this be the problem? Other than that, everything is the same. Please help. I really don't know what I'm missing.
 
Thanks,
Ken
0 Kudos
Message 5 of 8
(4,640 Views)

I've gotten that error when the channels aren't set up in Measurement & Automation Explorer. With traditional NI-DAQ, you need to set up virtual channels. You can do this by right clicking on Data Neighborhood and selecting "Create New..." Then pick "Traditional NI-DAQ Virtual Channel." You can use this to set up all the channels on the new computer, or you can just copy the configuration over by doing the following:

Got to the old computer and open Measurement & Automation Explorer. Go to Tools -> Traditional NI-DAQ Configuration -> Save Configuration As...

Copy the file to the new computer. Go to the same menu and select Set Active Configuration...

The virtual channels should be copied over and show up under "Data Neighborhood."

Message 6 of 8
(4,635 Views)
Hi MarcA and EVERYBODY else who contributed,
 
My problem has been resolved! I thank you all for your help. I think the last thing that I was missing was the virtual channels. However, without all the verification and clarification of drivers and updates, I would still be a lost soul.
 
Thanks again,
Ken
0 Kudos
Message 7 of 8
(4,628 Views)

MagCor:

It is great to know that things are now working fine. Please do not hesitate to post again if you need additional assistance.

Regards,

Rudi N.

 

0 Kudos
Message 8 of 8
(4,606 Views)