LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

application does not run on target system

Solved!
Go to solution

Hello, This is my first attempt at using this forum & creating a LV standalone application and I have encountered a brick wall.

 

I have created a simple VI to display some T/C readings that runs fine on the (LV prof 8.5) development system, but not on a different target PC.

The target PC does not have LV installed, just DAQ-MX software for Windows V8.6

 

The DAQ hardware is a SCXI-1000 chassis with SCXI-1600 USB interface, taking data with SCXI 1102.  I am using the same hardware on both

the development PC and the target PC.  The DAQ hardware works correctly on the target PC (using MAX).  My application loads, but just does

not run on the target pc.

 

0 Kudos
Message 1 of 5
(3,087 Views)

You are sure you've installed the (correct) run-time engine?

 

Do you have any screenshots of the application  load process?

Regards,
André (CLA, CLED)
0 Kudos
Message 2 of 5
(3,082 Views)

Hello André

I am not sure.  On my last attempt, I had included "additional installers" Run-Time Engine(s) 8.0.1, 8.2.1, and 8.5.1.

 

The application seems to load.  The screen looks normal, it just doesn't seem to acquire any data (although it appears to be running).

The VI is very simple.  I have attached it (didn't realize I could do this before).  I hope this answers your questions.

 

Thanks,

Bob

 

 

0 Kudos
Message 3 of 5
(3,076 Views)
Solution
Accepted by topic author bobdaq

Hi Bob,

 

  1. Ensure that you have included NI-DAQmx drivers and Measurement and Automation Explorer (MAX) with your installer.
  2. Use MAX on the target machine to check if you are able to see the device.
  3. Ensure that the device name of the card in MAX matches its device name in the program i.e. Dev1 in MAX = Dev1 in the program
  4. Also check the device names between the development system and the target system. i.e Dev1 on dev system = Dev1 on target.
Hope this helps!
Warm regards,
Karunya R
National Instruments
Applications Engineer
Message 4 of 5
(3,050 Views)

Hello Karunya R,

 

Thank you for your help.  The problem is solved now.   The device names were not the same on both systems.  When I renamed the device(s) on the target system (to Dev2) the program works now.

 

Thanks again,

Bob

 

0 Kudos
Message 5 of 5
(3,044 Views)