|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
VIs stop running after two seconds
On one laptop I am having a problem with VI's terminating a couple of seconds after deployment.
For instance, when running the Analog Input example I can deploy the VI, and it appears to run, but then it just stops after a couple of seconds. No error dialog box comes up - apparently the VI goes from running mode to stopped mode. Other symptoms: - the status led on the cRIO will start to intermittently blink three times (i.e. blink-blink-blink, pause, blink-blink-blink, pause, ...) - the driver station indicates there is no communication with the cRIO - if I single step through the code, I never make it through one iteration of the inner while loop; the top branch of the OR operator connected to the stop condition becomes true right away; if I remember the VI correctly, this is an error condition, but I haven't been able to figure out what the error is. However, I don't have these problems on another laptop. The main difference between the two is that on the one that works I installed Windows 7 myself and the one that doesn't has a factory installed Windows 7. Any ideas of what the problem is? Is there more I can do to diagnose the problem? Thanks! |
|
#2
|
|||
|
|||
|
Re: VIs stop running after two seconds
Since it sounds like single stepping is an easy and quick way to reproduce the issue, I'd recommend placing probes on a few wires, or perhaps turning on execution hilighting (the light bulb on the toolbar), and stepping through the code to determine if there is a logic issue, what error may be reported, etc.
By the way, if there is an error you'd like to look up, there is a tool in the Help menu called Explain Errors which lets you type in the code and get some additional info. If it still doesn't make sense, post a screenshot or attach a VI to help narrow it down. Just guessing, it sounds like the VI is finishing because the loop and all other code has completed. When a LV VI terminates, there are no lights or dialogs, it simply set the arrow back so that you can run again. Greg McKaskle |
|
#3
|
|||
|
|||
|
Re: VIs stop running after two seconds
One other thing to add:
According to http://digital.ni.com/public.nsf/all...256FDB00681951, a sequence of three flashes on the status LED indicates safe mode -- check the DIP switches (is the safe mode one different from the rest)? This might not apply to the FRC cRIO, but it probably does. I hope this helps. |
|
#4
|
||||
|
||||
|
Re: VIs stop running after two seconds
You can find how to configure your dip switches on page 12 of the crio-frc_Operating_Instructions.pdf.
You can get to this from the start menu by going to Programs > National Instruments > CompactRIO > CompactRIO Manuals This will open up the CompactRIO Manuals folder containing the crio-frc_Operating_Instructions.pdf, found at C:\Program Files\National Instruments\CompactRIO\manuals |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Problem with breakout box after update two | Sarah348 | Control System | 1 | 12-02-2010 12:18 |
| TeleOp Init/Stop vs. Auton-Iterative Init/Stop | Ziaholic | NI LabVIEW | 11 | 07-02-2010 22:19 |
| Any teams build two robots to practice with after build season. (6 weeks) | GVDrummer | General Forum | 42 | 24-01-2008 21:34 |
| pic: 166 Before and After: All in Two Hours | Dan Petrovic | Extra Discussion | 3 | 30-06-2006 16:43 |
| Stop The "Lesser of two evils" | MattK | Chit-Chat | 8 | 07-08-2004 23:31 |