|
|
|
 Just goes to show that you don't need to be like everyone else to make it to Einstein. - O'Sancheski [more] |
 |
|
|||||||
|
||||||||
 |
| Thread Tools | Rate Thread | Display Modes |
|
|
|
| Just goes to show that you don't need to be like everyone else to make it to Einstein. - O'Sancheski [more] |
|
|
|||||||
|
||||||||
|
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Problems Deploying Code At Regional
At the Bayou regional, I was having trouble deploying Labview code as startup from my coding laptop. The IP settings were configured correctly and I didn't seem to have any problems deploying code at our shop or at the San Antonio Regional. Is there any explanation as to why this is happening? The only way that I was able to get this to work was to plug my computer directly into the cRIO ethernet port, and even that was iffy.
Thanks Patrick 
|
|
#2
17-03-2012, 19:14
|
|||
|
|||
|
Re: Problems Deploying Code At Regional
One thing that I've seen is when the disabled VI hasn't been updated and throws lots of errors. Since the booted controller is disabled while code is being downloaded, that makes it take far longer and iffy to complete. You may even want to disable the RobotDrive Safety Config.
Greg McKaskle
|
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Linear Mode
