|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Basic VI's ????
Hey everyone,
I am trying to access the Basic VI's from the Project Explorer, but I can't seem to find any. Like I can't even find the Basic Robot Main. vi in our project explorer. Please help!! |
|
#2
|
|||||
|
|||||
|
Re: Basic VI's ????
List what you do see or post a snaphot of the screen.
Check under Help -> About FIRST Robotics Competition Software... to see if it says "Software Update 2.0". Did you apply the LabVIEW Update? Create a new "FRC cRIO Robot Project"? Do you see "Team Code" in your listing? (Expand it to see the vi's) |
|
#3
|
||||
|
||||
|
Re: Basic VI's ????
I went to about and it says Software Update 2.0. On the Project Explorer it shows,
RT Compact RIO (10.32.83.02) and all the files underneath including Team Code but I don't see any Basic VI's |
|
#4
|
|||||
|
|||||
|
Re: Basic VI's ????
What do you call "Basic" files. Give us an example.
In this year's LabVIEW teams are supposed to put all their code under Team Code in the vi's there, or in vi's that they create and add to those there. Begin.vi - open all your devices Teleop.vi - your driving code of choice Finish.vi - close all your devices Autonomous Independent.vi - your autonomous code If you are looking for simple Example code, you get to that from the very first screen LabVIEW goes to when you start it up. Last edited by Mark McLeod : 21-01-2010 at 22:49. |
|
#5
|
||||
|
||||
|
Re: Basic VI's ????
well right now I am talking about Basic Robot Main.vi and there is also Robot Main.vi
and also, I have been using Robot Main. vi to deploy the code and it works fine, Do I have to use the Team Code? |
|
#6
|
||||
|
||||
|
Re: Basic VI's ????
Never mind I figured it out, but I have a new question.
So I just modified the Joystick Input Example.vi, to make 2 joysticks for for our robot. My question is which folder should I put this VI into? The Team Code Folder? If so, then don't I have to modify the other VI's in the Team Code folder for both of the joysticks to work? |
|
#7
|
|||
|
|||
|
Re: Basic VI's ????
If you intend to use the VI, then put it with your team project code. Otherwise, you may want to open the team TeleOp code and make similar edits there -- or cut and paste.
Greg McKaskle |
|
#8
|
||||
|
||||
|
Re: Basic VI's ????
So when you put it with the Team Code Folder, should I just put that VI under the folder? will that work?
|
|
#9
|
|||
|
|||
|
Re: Basic VI's ????
Honestly, you can put it anywhere, but the team code folder is where I'd put it. If you are already calling it from your other code, then when loading the calling code, LV will start searching, and you can show it where the new location is.
Greg McKaskle |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| passing image data through vi's | Christine_Ilich | Programming | 2 | 07-02-2009 15:37 |
| LabView Functions Palette missing WPI VI's | ksquared | NI LabVIEW | 1 | 31-01-2009 15:03 |
| Using the analog sensor .vi's | Hazmatt | NI LabVIEW | 5 | 13-01-2009 22:57 |
| Basic Question | Wompas | Programming | 4 | 20-01-2007 14:33 |
| BASIC stamps | [527]phil | Technical Discussion | 1 | 09-05-2005 09:04 |