View Single Post
  #2   Spotlight this post!  
Unread 25-01-2013, 01:06
Doc Wu's Avatar
Doc Wu Doc Wu is offline
Registered User
AKA: Al Gritzmacher
FRC #1507 (Warlocks)
Team Role: Mentor
 
Join Date: Jan 2004
Rookie Year: 2003
Location: Lockport NY
Posts: 207
Doc Wu has a brilliant futureDoc Wu has a brilliant futureDoc Wu has a brilliant futureDoc Wu has a brilliant futureDoc Wu has a brilliant futureDoc Wu has a brilliant futureDoc Wu has a brilliant futureDoc Wu has a brilliant futureDoc Wu has a brilliant futureDoc Wu has a brilliant futureDoc Wu has a brilliant future
Re: Vision Processing VI Problem

Quote:
Originally Posted by wdburk3160 View Post
Well, I'm not going to ask about tracking. I have simply been opening a new cRIO project and while it is configuring it pops up a message about some Vision subVI that i don't have permission to use. I don't have the specific computer available at this moment, so I don't have the exact message. I can still configure the project, but in robot main, it says the Vision VI is not executable. I have tried other computers and they configure and don't open with any errors. I have a feeling that it might be something that happened during installation, but I am not absolutely sure. Does anyone have a suggestion as to what might have happened and/or a way to fix it?
I have installed LabVIEW and it's various FRC Updates on six laptops we use for our LabVIEW class, the laptop we use for our driver station, two laptops of my own and several students laptops. When a message like that pops up, it's often some piece of the programming system (LabVIEW is far from 'a' program, it's a large number of small programs working together) that didn't get installed correctly, or has become corrupted.

Usually, a reinstall fixes it. I can hear you groaning, but fortunately, a reinstall usually goes fast, as the installer is smart enough to skip over the parts that are already there and only does the missing pieces.

Sometimes, the message gives you a clue about where the missing piece comes from and you can go straight to say, the FRC LabVIEW Updates. Otherwise start with the main LabVIEW and then go through the update installs. This type of error is usually not the Utilities or Driver Station Updates.

I have been carrying the updates as well as an ISO image of the LabVIEW disk on a thumb drive and it comes in handy when fixing these sort of problems.
__________________
-= Mentor Lockport Warlocks -=- Team 1507 =-
Amateur Radio Callsign: AE2T

2016 Robot Inspector - Fingerlakes, Pittsburgh
2015 Robot Inspector - Pittsburgh, Champs. Judge Observer - Champs
2014 Robot Inspector - Tech Valley, Fingerlakes, Buckeye, Championship
2013 Robot Inspector - Fingerlakes, Buckeye, Championship
2012 Robot Inspector - Fingerlakes, Buckeye, Championship - Website Evaluator - Fingerlakes, Buckeye, Championship
2011 Robot Inspector - Fingerlakes 2011 Safety Advisor - Fingerlakes

Reply With Quote