|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#12
|
|||
|
|||
|
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 |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Encoder causes 24 bit relocation error | pafwl | C/C++ | 3 | 28-01-2010 08:53 |
| Screwing Encoder into Encoder Mount? | Adrien | Electrical | 3 | 25-01-2009 18:14 |
| GTS Encoder Compilation Error | Guru | Programming | 10 | 14-02-2008 12:11 |
| Encoder Error | Anime-niac_2.9 | Programming | 1 | 27-01-2007 16:23 |
| stupid Array error: Error [1300] stack frame too l | Validius | Programming | 7 | 27-01-2006 10:53 |