Beginner Help w/ Labview

[novalily]

We are a rookie team this year from a tiny tiny school in Pensacola with 30 students. Our team has 7 people on it. I was picked head programmer because I have experience with Java and HTML, css and c++ and all of the sort. But not with labview, and godforbid I try to change the language. My mentor is set on using labview. But I have no idea what I'm doing, and I'm finding this impossible. My team is struggling and we can't even figure out how to get the ip address to the radio. I'm not worried about that, however. I just have no clue on how to start on labview. We have the chassis put together and we're just testing it before we build anything hoopdy doopdy, so all I need to do is get the movement programming down. But I have no idea what I'm doing. I've made myself familiar with labview but I'm still clueless on how about to begin. I'm so desperate for help, haha. Thanks in advance.

[Mark McLeod]

1. Start LabVIEW
2. Choose FRC roboRIO Project from the Getting Started window
3. Enter your Team Number where it has xxyy
4. Click Finish

This gets you to the project window

From there

1. Expand Build Specifications (see attached image)
2. Right click on FRC Robot Boot-up Deployment and choose Build (this compiles your default project)
3. Connect to the roboRio via Ethernet and power the roboRIO
4. right-click on FRC Robot Boot-up Deployment and chooseRun as startup (this transfers your program to the roboRIO)

You now have a program that drives Arcade-style with a single joystick plugged into USB 0 (see the Driver Station Setup tab and make sure the joystick appears in slot 0)
It assumes you have one motor on each side (or one PWM splitter for each side) and the left motor(s) are plugged into PWM 0, while the right motors are plugged into PWM 1.

Once that is running you can look into changing things to fit your more specific needs.

[xszym]

Nice choice. We use labview second year so you can text to me If you need help with something.

Best start here:
https://wpilib.screenstepslive.com/s/4485/m/13811

[mshafer1]

Mark McLeod and are both correct. Please feel free to private message or email me if you have any questions. I have also started to compile a list of available resources from the website I help run (frclabviewtutorials.com)

[JeffB]

It sounds like you've got a few resources from this thread looking to help. I wanted to hit on a few points as well.

In LabVIEW, there are some tutorials that walk through the basics of the project setup to help you get started.

As you have some experience programming, I'd suggest taking a look at the Command and Control framework ( https://forums.ni.com/t5/FIRST-Robot...l/ta-p/3534946 ) It's a bit more advanced than the typical architecture, but it eliminates a lot of the questions like "how do I add a delay to teleop without halting everything else about my robot?"

You're also free to call the NI Support staff Monday-Friday 1-7PM Central time. They'll do their best to take a look at your current questions and help you find your way through the new programming world. Their number is 866-511-6285

From a general experience point of view, I'd offer some outside feedback that may help the overall frustration a little bit. In programming, you're rarely going to get into a position you believe is ideal. There are almost always going to be some restrictions on your ability to program. These can come from hardware only working with a specific language, hardware not working with your OS, or bosses simply not allowing you to use some tools you'd prefer use. You're getting to experience that a little bit now. In the future, it's likely to help ease frustration when you run into this either in classes or in the workplace. Given the languages you know, I trust there's been a time when you've picked up a new language and had all of the algorithm ideas running through your head without knowing how to express them in your code. With text-based languages, most of this means getting used to the syntax and then moving forward. With the robot, it'll mean getting used to the way the code looks more so than syntax. But, it's the same general idea. You'll want to hold onto all of the ideas you already have and get used to how this language works with those ideas. You'll be surprised at how quickly you pick up any language once you let yourself get past the initial frustration and move towards finding a solution within the imposed limitations.

[Hess1113]

Hello Novalily I used to be in your position. I find that LabVIEW for me was mostly trial and error and after lots of example code and youtube videos of other teams demonstrating I was able to get it down. If you need any help please direct message me and i'm sure I can help you or find a way to get you the help you need from skype or email.

[Rsave7]

Originally Posted by Hess1113

Hello Novalily I used to be in your position. I find that LabVIEW for me was mostly trial and error and after lots of example code and youtube videos of other teams demonstrating I was able to get it down. If you need any help please direct message me and i'm sure I can help you or find a way to get you the help you need from skype or email.

^

What helped my when i first started was bits and bots' labview tutorials. they are pretty old, and im pretty sure he stopped halfway through, but a lot of the information is still relevant.

Trial and error works too. If you know how to program in text based languages, it can be quite a switch to visual based, but you can do it. its similar but you just use pictures instead of commands and functions.

Good luck!