|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Labview code not in realtime
Is is possible to run labview code on a robot without doing it in realtime.
What I want to do is make it so that you don't have to have a computer attached to the driver station to get the robot to work. |
|
#2
|
|||||
|
|||||
|
Re: Labview code not in realtime
See if I understand what you're asking.
You want to run your robot without having your laptop computer hooked up? In competition, the robot will never be attached to your PC if that's what you mean. There is a special way you have to download the code to your robot to get it to "stick" and work without your PC being attached. If this is what you mean we can explain further. (Real-time isn't the term you're looking for here.) |
|
#3
|
|||
|
|||
|
Re: Labview code not in realtime
Quote:
Yes, that's exactly what I am asking. What word should I use? |
|
#4
|
|||||
|
|||||
|
Re: Labview code not in realtime
Directions are given in the FRC_Programming_Guide, page 5-5,
Creating a Stand-Alone FRC Application You'll find your copy of this on your C drive at: C:\Program Files\National Instruments\LabVIEW 8.5\manuals In brief here's what you do... When you open your LabVIEW project you start with the Project Explorer window (I attached a snapshot below). On that window under "RT CompactRIO Target (10.15.99.02)" you'll see "Build Specifications" and under that "FRC Basic Robot Deployment" all the way at the very bottom. (It also might be "FRC Robot Boot-up Deployment" depending on which Framework you started with). Right click on "FRC Basic Robot Deployment" -- Choose "Build" When that's done right click on "FRC Basic Robot Deployment" again to -- Choose "Run as startup" When it's all done it'll ask you if you want to reset the cRIO. -- Choose Yes (or you can also cycle the power on your robot). Then your PC doesn't have to be attached anymore. ----------------- The PC is only necessary when you use the "Run" button to start everything. That's only intended to temporarily run your program on the robot just to check out changes quickly. P.S. Try it. There may be one or two settings you have to make depending on how you set things up, but you'll get a message about it and we can walk you through those if necessary. Deploy to run at startup. Real-Time just means the code can run fast enough to keep up with events in the real world. For example, turning when your joystick tells the robot to turn, not when it feels like it sometime later on. Last edited by Mark McLeod : 26-02-2009 at 16:38. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| LabVIEW annoyance. help( not a hater thread) | Stuart | NI LabVIEW | 15 | 20-02-2009 11:27 |
| custom C/C++ code in LabView? | Pneumaticsman | NI LabVIEW | 5 | 14-01-2009 23:05 |
| help me in LabView code | mahmosh | National Instruments LabVIEW and Data Acquisition | 3 | 11-01-2009 00:18 |
| Activation of LabView still not working | apollorest | National Instruments LabVIEW and Data Acquisition | 4 | 22-11-2008 21:09 |
| frc_camera not working but labview does | Issues | Programming | 7 | 18-01-2006 19:23 |