After beating my head against the wall for a few hours, it "mysteriously started working". Right now I can't get it to fail. See some comments below
Quote:
Originally Posted by Greg McKaskle
Also, did your project build successfully?
|
Yes, built successfully no problem. I don't have a screenshot handy to prove it. The example begin.png was the smallest possible testcase that reproduced the problem. I could start with a default project, deploy fine, add two VIs, and deploy would fail with that screenshot.
Quote:
Originally Posted by Greg McKaskle
If you perform the smaller steps of build, connect, deploy, which steps work and which fail?
|
Build worked, not sure what you mean by connect, and deploy failed with that screenshot
only when the project included UDP Write. As mentioned our normal code (not containing that one VI) and a default arcade drive project (not containing that one VI) would repeatably deploy fine.
We tried various things like cycling the power, rebooting the laptop, multiple known good laptops, and trying to deploy multiple times.
Quote:
Originally Posted by Greg McKaskle
Also, what is the IP address of the target in the project?
|
10.12.50.2
Like I said it "mysteriously started working" after a couple hours of testing different things. What I'm monitoring right now:
- Our team has a mixture of systems with the release software (LabVIEW 2013) and which installed the NI Update Service update (LabVIEW 2013 f2). Maybe that was a factor?
- Not sure what the cRIO had originally. Somebody from NI warned us that existing, badly-behaved software might interfere with deploy unless you go into safe mode. I had not tested safe mode.
- I'm not certain if we were / weren't running driver station during all tests.
- This is our spare cRIO. We have no reason to believe it's faulty; but maybe it is.
I've got my fingers crossed right now that this keeps working.