stand alone application with DAQ

[jcraffael]

Hello all,

I got a problem with my stand alone application in the target computer.

My program has a sub vi named Igenerator, which generates current with the connected NI 9265 with all 4 channels.

When building the installer of the application, I already included NI-DAQmx application development support, and with this

installer my application could be opened in the target computer correctly.

however when running the application in my target computer (with NI 9265 connected), from the result of the program I can

see that there's no current output from NI 9265, so it is an issue of transfer the DAQ settings from my original computer where

the project was generated to my target computer, isn't it?

To solve the problem I found this link: http://www.ni.com/white-paper/5406/en, seems that the trick is in the last step of building

the installer I should include a hardware configuration. But how? this link fails to clarify this point to me, and I tried to do 'configure',

and export all my current generation task from MAX to the file 'configdata.exe', and I clicked 'Build', it seemed fine, but in my target

computer after I setup the installer, my application again has no current output from NI 9265.

Someone got any idea about how could I achive that? And any mistake of my procedures I've done? thanks

Chao

[JÞB]

[Edit] I just learned something.  Prior data was incorrect.

Does the configuration appear correct in MAX after the installer runs on the target machine?

[jcraffael]

Well I'm not sure if I got your question. I set up the installer successfully in the target computer and the stand alone

application runs well. But i don't know how to check the configuration in my installer with MAX.

Yes I did export the current tasks from the MAX in my original computer to the installer, but how could

I check that in MAX in my target computer?

[mknix]

Just a thought...

did you check that the device name is the same in MAX in both the target and the developpement computer?

regards

antoine

 edit:  devive name is the one between "" character in max, like "cDAQ1"

[JÞB]

Open MAX on the target PC after the installer runs.

Do Tasks, System devices and Scales match the setting from the development PC?

[jcraffael]

Ok I got it. After I reset the configuration in MAX and re-installed the installer, I checked MAX, and found that the

NI-DAQmx tasks are the same as they are in my original computer, but under the option 'Device and interfaces' I

see 2 NI 9265! 'Dev 1' and 'Dev 2', one has green icon and one has yellow icon on the left. And it shows that my

PC could communicate successfully with both!

Anyway this time I failed again, after checking MAX only Device part is odd. So any idea?

[jcraffael]

Hi Antoine, my reply is above as it's also for Jeff.

Thanks.

[0utlaw]

Hello jcraffael,

The yellow icon indicates that the device is simulated rather than physically present.  You'll need to delete this device and rename the physical device to match the configured task.

Regards,

[JÞB]

One small problem with Simulated devices:

You Cannot assign a new real device to the alias of a simulated device.

See Here- I probably should have reported this as a bug a long time ago

The workaround is obvious:  Clear simulated devices from targets before installing applications that need that alias or running a system configuration API utility to assign a application specific alias

[jcraffael]

Hi Tom! Thanks for the explanation. I deleted the device with yellow icon 'Dev 1', and renamed the device with green icon 'Dev 1' from 'Dev 2', and the system asked me to assign the tasks related to the old 'Dev 1' to the new 'Dev 1' and I did it.

However, it still didn't work. I think probably I made mistake in implementing the procedure above....