Application Builder - I just get NaN when I run the install. Help!

[MikeBrengartner]

I've done a build and an installer in 8.5.1. I've moved the installer over to another machine, run the NI-DAQmx setup, rebooted, and run my setup.  The app launches, then when I go to sample, I get nothing but a bunch of NaNs.  Any idea what I might be missing?  The hardware box is a USB-6229 and plugging it into my dev laptop works just ducky.

Thanks in advance,

Mike

[jon_mcbee]

I have seen a similar problem, atleast the symptoms sound the same.  After reboot, try unplugging and then plugging back in the USB cable.  For some reason the USB device wont register after boot up, but needs to be unplugged and plugged back in to work.  Like I said the symptoms are the same but I cant gaurantee that this quick fix applies.

Good Luck

[MikeBrengartner]

Thanks, but no luck with that 😞 Is there anything else I need to install on a clean machine to get it to run?  NI-DAQmx, my install, ???

Thanks

Mike

[jon_mcbee]

Just so I am on the same page.  Your installed program looks for an existing task by name.  You install the program on the target machine, build the task and give it the correct name on the target machine.  When you run on the target machine it accesses the task but does not read the hardware correctly?  Are you sure that the tasks are the exact same between target and original machine?

[MikeBrengartner]

I'm not sure what "give it the correct name on the target machine" means.  But I do a build, build the install, copy it over to another machine to test, and run the install.  After the install, reboot, and run the program.  I then hit the sample button, which goes out to the daq assist and samples the data from the hardware.  But the only thing that displays is NaNs.

I installed http://joule.ni.com/nidu/cds/view/p/id/965 on the test machine, but I've uninstalled and reinstalled once.  Not sure if that matters.  I do not get anything in Vista's device manager like I do on the XP dev laptop I created this all on.

Thanks,

Mike

[jon_mcbee]

Are you using DAQmx tasks to control your hardware?  If so are you building the tasks programmatically in the code or do you call a task by name (a pre-built task that already exists)?  If you are creating tasks programmatically be sure that your device ID does not change between computers, I have seen this happen.  I dont know much about how building on XP and running on Vista could change things, somebody with more experience in that will have to let you know if they think that could be the root of your problem.

[MikeBrengartner]

I'm using the DAQ Assistant to get access to my channels.

[jon_mcbee]

This is my guess.  When you use DAQ Assistant to set up your task in the vi (on the XP machine) it asks you to select the hardware and channels.  It is possible that the device ID on the XP machine when you configure your task is different from the device ID on the Vista machine when you are running your task.  If this is the case then the best way to fix it is to programatically build your task so that it can handle a change in device ID number.  I would be curious to hear other opinions though as I am not positive this is your problem.

[StevenD]

Using the DAQ Assist is probably your problem. Someone correct me if I'm wrong, but I'm pretty sure the DAQ Assistant just helps write code based on what you select, but will not function dynamically. Once the device/channels are picked, they are hard coded into the VI. You need controls on the front panel to select the correct device and channel(s) if you want to use it on a different machine with different hardware (or even the same hardware with any difference in configuration). I believe there is an option to change the DAQ Assistant to actual code on the block diagram, from there you can change the device/channel(s) to controls and when you run the program on the other computer, you should be able to select the device/channel(s).

[MikeBrengartner]

This app is designed to be identical across machines - I unplugged the hardware box from one machine and plugged it into the other.  The exact same configuration.  Do you still think this might be a problem?  If so, what do I do to fix it?