We just detected a case where it appears that loading an example corrupted a robot project. WPI_DriverStationStartStop.vi had a bunch of code related to one of the examples in it, in the "execute" case, that was not the simple stuff that belonged there. I can imagine how in the examples messing with some of these VI's to run the examples is a really good idea. I am looking for the stupid user trick we pulled to cause it to happen. I'm kinda looking for you, NI Greg (please
Learning take-away: the deployment whined about a DIO collison; we went into begin and selected the DIO Open Vi, and fired off "Find All Instances' off the right mouse button. Bingo, all of out expected instances, plus two from the corrupted code. Worked again a few minutes later to find a collision on the analog inputs between the battery Vin on AI8 and the ultrasonic we plopped in on 8 because 2 had gone bad on our adapter (the voltage regulator smoked, too).
This is getting to be too much hardware for a software jock
The good news is we can get big scores two weeks before B&T for the first time in our history!
Tim
The pen [may be] mightier than the sword, but the bandsaw can chop them both. - Marc P. [more] 
Threaded Mode