VI executable runs differently on a target machine

[Modusincertum]

I created a VI that accesses a USB-6003 and a USB-6212. From that, I built an executable. The executable runs fine on my LV development machine, but when ported to a target machine that has only the LV runtime and the NI drivers loaded, the VI seems to run, but it will not access the DAQ devices. The DAQ devices show up in MAX on the target machine, and both work fine in a MAX test panel. I have a controls on the front panel to select the devices, and both devices show up in the drop down lists, but the VI shows no data from the DAQ devices. 

Is this a build parameter issue? Did I forget to check something when I built the executable?

Any thoughts would be very much appreciated.

[GerdW]

Hi modus,

---

@Modusincertum wrote:

Any thoughts would be very much appreciated.

---

How do you define the DAQmx tasks in your EXE?

How do you reference the DAQmx devices?

Did you set the very same labels for those devices as was used on your development computer?

Which errors do you get in your EXE?

You do some error handling, don't you?

[Modusincertum]

Hi GerdW,

I created the tasks using the DAQmx VIs. I used MAX to ensure that the devices were labeled the same on both computers. As I stated, when I search for the devices in the physical channels control, they are detected and I'm able to select the appropriate channels. However, the DAQ devices show no data in the associated indicators when running on the target PC.

I don't get any errors, and I do have error handling. I appreciate that reminder.

Regards,

[NIquist · Accepted solution]

Hmmm, we may need to see your project. If it's not too big, post it here. 

One thought, are you using any filepaths for config files or anything like that?  Remember that you need to adjust the path between dev mode and EXEs. 

Error 7 in Executable When Using the Current VI's Path Constant - NI

How Do I Construct a Path to a Directory in LabVIEW? - NI

[Yamaeda]

Did you create tasks in MAX and not export them to the new computer? That's a classic.

[Modusincertum]

Thank  you NIquist,

you sent me down the right path. I had selected a local file, but for some reason, the app wouldn't open it and did not report an error. I deleted the file and recreated it and now the app is working. Start with the simple things first...right.

Thanks for mentioning that.

Regards,

[billko]

---

@Modusincertum wrote:

Thank  you NIquist,

you sent me down the right path. I had selected a local file, but for some reason, the app wouldn't open it and did not report an error. I deleted the file and recreated it and now the app is working. Start with the simple things first...right.

Thanks for mentioning that.

Regards,

---

An executable is built with debugging off, so if you are relying on popup errors to do your error trapping, you will have to implement real error handling instead.  (Popup error dialogs are part of debugging.)