|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Code Not Deploying
There was a bug in the RT runtime that kept LV from exiting out of deployed applications in order to start another. The LV 5.1 update works around this. The workaround until you install the update is to exit the dashboard, then deploy code, then launch the dashboard.
Greg McKaskle |
|
#2
|
|||
|
|||
|
Re: Code Not Deploying
Quote:
|
|
#3
|
|||
|
|||
|
Re: Code Not Deploying
Still isn't responding means it is waiting for ...
Also, the RT bug I described would peg the CPU when it was waiting for the deployed code to exit. The bug would occur when any SmartDashboard client was connected, I mention the dashboard because that is typically the only one teams run, but if you are running Smartdashboard, Table Viewer, RoboRealm, or other Smartdashboard clients exit those too. And better yet, install the LV5.1 update and the bug will go away. Greg McKaskle |
|
#4
|
|||
|
|||
|
Re: Code Not Deploying
It worked after I re-imaged the cRIO, if that helps in any way.
|
|
#5
|
|||
|
|||
|
Re: Code Not Deploying
If imaging the cRIO involves formatting it, then the deployed app will be deleted. So it is the other, much longer, workaround.
Greg McKaskle |
|
#6
|
|||
|
|||
|
Re: Code Not Deploying
Ok, I'll try updating the LabView code, thanks for your help!
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|