Thread: Problems Imaging the cRIO
View Single Post
  #11   Spotlight this post!  
Unread 31-01-2010, 09:34
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
  
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,855
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Problems re-reimaging again and again
Quote:
Originally Posted by BLProgram2010 View Post
We're use Labview. Every time we develop new code and try to deploy it or connect to the cRIO, there a error that says the vi's in the start up application will not open and will remain closed if you continue to apply and deploy. I found out the by using the 'cRIO Imaging Tool' and hitting 'Format controler', the pproblem is removed and we can deploy the code and run a drive test. But when we switch users back into the developer the same problem occurs and the cRIO needs to be re-imaged again. Running the 'cRIO imaging tool' with the format controler takes about seven minutes to finish; and ontop of that we still need to deploy and build the code which take another five to seven minutes. We seem to be spending a lot of time re-reimaging the cRIO to fix our problem. How do we fix it?
Next time that happens just click okay and let it continue to see what happens.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle
Last edited by Mark McLeod : 31-01-2010 at 09:40.