![]() |
Tips for first-year programmers
Hey there. I was on my school's robotics team last year, but we had a more experienced programmer so I was one of the many "help out where you can" guys. Well, he graduated, and now I'm the chief programmer for my team.
I do have a pretty good basis on how to set up and use coding I don't have almost any experience with LabVU, but I know it comes with some tutorials I'd appreciate any tips that would be helpful, whether it be a link to certain LabVU tutorials that actually relate to the robot, comments on how to program for robots specifically, or anything I may not know. Thanks! |
Re: Tips for first-year programmers
http://www.frcmastery.com/ - LabVIEW examples in a FRC context
http://ni.com/frc - NI's FRC Portal http://zone.ni.com - NI Developer Zone: help with general LV topics; is a great resource for anything LV A Post with some other great resources Learn LabVIEW in 3 hours Also, all of LabVIEW's example VIs (go Help->Find Examples) are extremely useful, and there's a whole section for common FRC tasks, as well |
Re: Tips for first-year programmers
It's easy to get overwhelmed. Don't get overwhelmed, just keep working at things a little bit at a time. (Oh, and don't forget to have fun!)
|
Re: Tips for first-year programmers
Comments and Documentation: Use them! You would never believe how fast you will forget how something works, especially when things are flying at you so fast. Other/future programmers will understand what you did and why you did it.
Become Intimately Familiar: The more you know how your system works and how it should work, the more help you can be in diagnosing problems down the road. Stay Open Minded: There will be times when everyone but you says "it's gotta be the code". You'll be 100% sure it isn't the code. Everyone else has to be wrong. Listen to them and give their theories a shot. It's probably the code. |
Re: Tips for first-year programmers
thanks for the links ^^ i'll check those out tonight
Quote:
Also, I forgot to mention: The last 2 years (our first 2), we've used Joysticks. However, being a huge gamer, I'm switching to the xbox360-like controller. So any tips on how this is different will help too! |
Re: Tips for first-year programmers
Quote:
Quote:
A gamepad puts more buttons within immediate reach of an operator's fingers than a joystick does. Some people find that useful. Others find it confusing, and prefer the more spread-out button layout of one of the USB joysticks from the Kit of Parts. On the other hand, sometimes the most intuitive and effective control scheme is neither a joystick nor a gamepad, but instead a custom array of buttons and/or switches and/or knobs. |
Re: Tips for first-year programmers
Anytime I see a thread list this, I can't help but think about a session I attended at Java one a few years ago by the "Diabolical Developer", in which he suggested we should teach programming by sitting someone down at a unix prompt, typing "man man", hitting enter, and then leaving the room!
My top, number 1 suggestion for you: Reprogram last year's robot this fall. Start from scratch, and don't reuse any code from last year. Once you can get it up and running again with all of your own code, you'll know you're ready to tackle the new robot on day 1 of the build season. |
Re: Tips for first-year programmers
Quote:
Quote:
|
Re: Tips for first-year programmers
Okay so my first REAL question question (for those of you that have used controllers before):
I'm looking for a controller as identical to an xbox 360 controller as possible. 1) I think I remember someone telling me you can use a normal x360 controller if you install a driver for it. Is this true? If so I'll just buy a cable to make my wireless controller wired, download the driver, and things'll be super easy! 2) If not, then is the controller on the right in the picture what I need to get? Is there something better? Any idea where I could buy this? http://techgage.com/reviews/logitech...m_07_thumb.jpg Once again, HUGE thanks to everyone for all the help! |
Re: Tips for first-year programmers
you can use a normal xbox controller with windows, but it can't be wireless. you have to actually have a wired only controller, as just connecting a cable won't route the data to the PC, for a wireless controller, you need the windows gaming adapter. If memory serves, that type of wireless network is not permitted on the field.
|
Re: Tips for first-year programmers
Quote:
P.S. We used a Dual Action gamepad for our manipulator control this year, and I really like it, but it doesn't have analog triggers. |
Re: Tips for first-year programmers
Quote:
Also keep in mind that the Xbox controller has a large deadzone in the middle of the stick that needs to be accounted for, otherwise it won't center properly. The logitech controllers and joysticks don't seem to have that issue so much. We haven't tried an Xbox controller yet, due to money issues and lack of a workable testbed robot, but I have the code complete for one. Keep in mind I haven't tested it yet. https://github.com/FRCTeam3737/2012-...aptors/OI.java |
Re: Tips for first-year programmers
Quote:
|
Re: Tips for first-year programmers
I finally put LabVIEW on my laptop yesterday and I'm currently looking around the forums to decide which controller I want to use. I'm an xbox guy, not a playstation guy, meaning I like the dpad and the left joystick switched -- it's much more comfortable! However I've read a lot of people say that the joysticks on xbox controllers don't center at 0. I don't know if it's a huge issue or an easy fix, and I don't know if there's other issues as well.
I already know it has to be a 100% wired controller and I have to download a driver for it, but that's no big deal 1) Are there any other issues with xbox controllers besides the centering issue? How do you fix this? 2) If this IS an issue large enough to mean that I shouldn't get an xbox controller, that leaves me between the Logitech F310 and F510. As far as I know, the only differences are that the F510 costs $10 more, has a 4th button in the middle, and can vibrate. Does the vibration ever come in handy that much? I could imagine it being useful for a wide variety of things, but I could also easily see us not using the feature at all. |
Re: Tips for first-year programmers
Quote:
|
| All times are GMT -5. The time now is 03:54. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi