Thread: Encoder Error
View Single Post
  #12   Spotlight this post!  
Unread 31-01-2010, 00:11
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Encoder Error

Not to rain on the parade, but this doesn't really make sense. The cRIO does contain flash, and when code is deployed, it and all dependencies are stored in flash. But when executed using the run button, the VIs are saved locally to PC temp storage, and all VIs are downloaded. I think that VIs can reference .out files already on the flash, but I don't think that anything on the disk would have confused the deployment. If there were VI conflicts due to VIs already being in memory, that would have resulted in a different dialog. I don't really see why reimaging the cRIO would solve the issue.

Greg McKaskle
Reply With Quote