09-12-2010 01:44 PM
I think I am running in circles trying to determine what my problem is. Please look at the screenshot I have attached.
I setup three different network shared variables (two in one library, the third in a second library) on my RT target. I have deployed them manually probably half a dozen times. I then build the executable, and tell it to make it a startup app.
I then created alias shared variables on my user computer. They are setup as PSP variables that I linked thru the dialog boxes NI provides. A sample URL of one of these variables is: \\169.254.0.2\rtDataRouter\Data
I deployed this library on my user computer. From what I was reading, I am not sure if that is the correct thing to do if I am having the RT target host the main variables (we want to be able to hook up multiple clients at remote locations, hence have the RT host them). So I tried it both ways, with the aliases deployed and without.
If everybody is still with me, when I run pure development environment, Labview 2009 SP1, deploys everything to the RT, I then run my local app, it says it is deploying items, and then it runs, shared variables seem to talk to no problem. Doesn't seem to matter if the aliases were deployed or not (I do have auto deploy turned off).
Next, I try deploying the RT startup app, it reboots, I hit the run arrow on local machine, and I get the conflict window! Again, I try manually deploying the libraries on both the RT and local machine, rebuilt the executable, reboot the RT, run the local app (still in development environment), and I get conflict window!
Part of me thinks, I am simply missing turning one thing on or off. From the tutorials on NI's site, I think I am in the ballpark, what am I missing???
My project is 99.99% done other than getting the executables done. Any insight and help you can give would be HUGE for me to get this out the door!!!
09-13-2010 10:15 AM
Make sure you have Autodeployment turned Off on your cRIO targets as well as your Windows Target.