Need Beginner Programming Tasks

[Allikan]

Hey everyone , I'm from team 5418. This year we are having an issue with certain people not "being productive" . I'm personally on build(which is in a separate room) so I can't always babysit the programmers( which like to sing , mess around, throw chairs at each other , exc;.) I don't know much about programming Labview, but I need to give them something to keep them busy. We don't have our robots chassis done yet ( it's a mecanum - first year building it ) so anything pertaining to that specific drive train would be great! I honestly don't think most of them even know how to code. Any ideas? Thanks!
-Captain of 5418

[whitetail]

I feel your frustration, the same thing happens on my team from time to time but you just have to lead by example. Can you explain more about what is happening? Where are your mentors when this is happening and have you talked to them about what is happening and how you find it very frustrating?

For tasks to give them I would say if you have a basic drive chassis give them that and then have them add sensors to it and do certain tasks. Ex: With a gyro make a corrective drive system where when the robot is bumped it goes back to where it was.

PS: The corrective gryo can be quite difficult to program depending on your programmers experience

[Jayd009]

Do you have any mentors who can teach programming? What I did with my team's rookies was use Google Hangouts on Air to record the session and basically told them to watch it. Afterwards, they were expected to know how to code and if they didn't, they would have to learn quickly.

Are there some basics that you know about your robot? If you think you're going to shoot, you could code a basic shooter with a flywheel. That would be very easy for a new programmer. You could also have them code a tank drive setup just to make sure they know how to code drivetrains in general.

[GRSICP]

I wrote up a document of small beginner tasks for our coding team. For each task, I provide a link to the api and/or a page from the wpilib screen steps. Sometimes I also included more detailed instructions if I thought a beginner programmer would need more than just the api and the screen steps. Tasks will depend on what your team has in terms of sensors and other things for the coders to test, but here are some examples:

1. code drive base with arcade drive
2. code drive base with tank drive
3. drive in a square in auto
4. drive in a square using the gyro sensor
5. read values from the sonar and convert them to inches
6. display the feed from a USB camera
7. write and then tune a PID controller using the gyro to drive straight
8. code a servo motor
9. code a pneumatic piston
10. read values from the encoder and convert them into inches
11. use the SmartDashboard to display data from the sensors
12. use the SmartDashboard to set robot preferences

So far this has worked well for my team! While making the list did take me a bit of time, it's helped our practices be much more productive because people know where they can find something to work on. I also feel like it has done a good job of bringing our new programmers up to speed with the basic skills it takes to program a robot. Good luck!

[Joe Derrick]

I would suggest setting up a test bed with a functional RIO, PDB, VRM, RADIO, joysticks and motor controller(s). Have them achieve tasks like. make a motor spin, make a motor spin forwards and backwards and stop. make a motor spin until a limit switch is tripped. or other thing that you are thinking about having your robot do.

TO a programmer having a testbed to test actual code is extremely useful!!

best of luck!

JOe

[AriMindell]

Dealing with new kids can be super frustrating, especially when they show up for the first time at kickoff, expecting to jump right in with 0 knowledge. I think to get things done as effectively as possible, you have to accept that not every single person can contribute directly to the final robot. By giving those new kids tasks, we are investing in them for future years. We just need to hold their interest so they keep coming back.

Here's what we came up with for new kids:
I know you said you program in LabView. We are a java team and I don't know LabView very well, but this may still be applicable.
I set up a simple Java project that runs on the computer and allows you to program a 2D "robot" to move around on the screen. The structure mimics that of the WPILib command-based system, so it's good practice for real FRC.
Originally I wrote the project to help them understand Command based programming, but now when I have inexperienced kids showing up looking for something to do, I just point them to that game.

Here is a link to the github repo for anyone interested (All the inner workings are hidden away in a jar)
The source for the back-side that makes it work is available here.

[Hess1113]

I would have them do simple takes such as get code ready for what ever type of robot your programming. If they don't know I would find some such as a mentor or programmer from (I know I would be happy to help teach other how to code). I am not sure what age you are dealing with or maturity but find some way to make it fun or interactive. I am currently from a Boy Scout troop where I am the Senior Leader and I work with other people like the ones you described and it takes a bit but after you give them some kind of way to have fun while programming(or in my task learning scout skills) it is worth it. Also as a side task do you have any old robots that are abled to be programmed in LabVIEW that could give them some great training. I hope everything works out for you and your team. Any questions just contact me. Happy Building

[Lili_1868]

Here's a list I came up with:
Get the framework ready.
If your team has decided on a drivetrain code arcade and tank.
Decide on an autonomous strategy.
If you guys are planning on doing vision, work with the camera and get the needed math and planning done.

Also, if most of them don't know how to code, have more experienced students teach workshops on coding using past robots.

[Eric Scheuing]

I'm not a programmer either, but a good activity could be to have them work on flowcharts for the code. For auto routines, have them diagram out each step the robot will have to take to complete your given task. For teleop, have them diagram out what each input will do, and see if they can work on automating certain tasks to ease the responsibility of the driver.

[Fields]

Originally Posted by GRSICP

I wrote up a document of small beginner tasks for our coding team. For each task, I provide a link to the api and/or a page from the wpilib screen steps. Sometimes I also included more detailed instructions if I thought a beginner programmer would need more than just the api and the screen steps. Tasks will depend on what your team has in terms of sensors and other things for the coders to test, but here are some examples:

1. code drive base with arcade drive
2. code drive base with tank drive
3. drive in a square in auto
4. drive in a square using the gyro sensor
5. read values from the sonar and convert them to inches
6. display the feed from a USB camera
7. write and then tune a PID controller using the gyro to drive straight
8. code a servo motor
9. code a pneumatic piston
10. read values from the encoder and convert them into inches
11. use the SmartDashboard to display data from the sensors
12. use the SmartDashboard to set robot preferences

This is a GREAT list for beginners to prepare during the early stages. Will you use all of it? Definitely not, get students looking at the different blocks of code early so they're not starting from scratch after time has gone by.

[KJaget]

If you're using LabView, this is full of programming exercises : https://www.chiefdelphi.com/forums/s...d.php?t=120756

[NathanStro]

Make them complete this course:
codecademy.com/learn/java