![]() |
Who Has Programmed From Scratch?
Well since the eclipse detection demo worked out of the box, my mentor said to just add on to it and I just added maybe 8 lines of code and we got a fully functional robot, the kicker, compressor and camera and drive all working right... :confused: :confused: Why does FIRST do this? its too $@#$@#$@#$@# easy, I think they should just give the API and the Libraries next time with no demos and make us figure it all out... My mentor says he knows how I feel, but he is more worried about a functional robot than "The feeling of satisfaction you get from programming"
|
Re: Who Has Programmed From Scratch?
I guess we know which team will be scoring 6 balls in autonomous mode at the LA regional this year!
:ahh: There's a world of difference between just getting a robot to work versus producing a world-class robot. The mediocre do the minimum, then exclaim how easy it is. The exceptional never stop to gloat... they're too busy figuring out new ways to make it even better... |
Re: Who Has Programmed From Scratch?
Quote:
Our team focused too much on the hardware itself, but my self was saying software first from the beginning, taking into stanford's philosophy of software first. I wanted to focus on the software to handle almost every thing, but too bad that didnt happen |
Re: Who Has Programmed From Scratch?
You might seriously consider applying the "student designed, student built, mentor approved rule. As it would seem you are having some instances of mentors being a bit too over-bearing, perhaps. Another useful rule our team has it the "mentors hands off policy." They don't have anything to do with the bot other than random pieces of advice here and there.
|
Re: Who Has Programmed From Scratch?
Quote:
|
Re: Who Has Programmed From Scratch?
Does the demo code work out of the box for detecting soccer balls? I haven't been able to get that to work.
|
Re: Who Has Programmed From Scratch?
Quote:
|
Re: Who Has Programmed From Scratch?
I HATE this year's robot, the kicker does not kicker over even one bump... Its unpredictable kicking too. I just hate it... It doesnt even drive over a bump... The middle wheel prevents it, and I was warning about it since the idea was introduced... $@#$@#$@#$@# no one listens to the sophomore...
I am definitely running for Team leader next year... I think we have to work harder next year |
Re: Who Has Programmed From Scratch?
yes, the demo code will work for a simple robot, but if you want to go beyond that you have the option. the code for 706's robot recently broke 500 lines (i started with the example "simple robot template", which was around 40 lines to begin with). it all depends on how many features you want and the amount of control you want on each one. i find that if programming has become to repetitive or too easy, i can just come up with a couple more sensors to add to take that extra load off the driver, or make an awesome autonomous mode.
some great ways to challenge your programming skills: write an autonomous mode that automatically aims at the target give your robot a swerve drive and make your own steering wheel use a custom controller (something beside the joysticks) write debugging code/add diagnostic sensors to see if any part of your robot is malfunctioning all of these things are very possible but cant be done by copying and pasting demo code, and of course you can always write your own commands instead of using the ones built into the WPI library (i for one really dont like the PID controller) |
Re: Who Has Programmed From Scratch?
Quote:
|
Re: Who Has Programmed From Scratch?
Being a SW guy myself, I can understand your frustration when everything else still has issues, but I'd encourage you to focus it in a more positive way.
Perhaps you can approach your mentor with some projects that you can work on that will not add too much risk to the robot. For one thing, you can easily make alternative code that you can test against the built-in. When yours is better and you convince your team and mentor, you can switch over. You can also switch back if you discover issues with yours. It is pretty safe to develop a nice dashboard to give the drivers more info. And if you don't have an autonomous routine, yet, that is like the SW freebie. Figure out a way to score from at least the front field position in auto. And good luck. Greg McKaskle |
Re: Who Has Programmed From Scratch?
Quote:
The consequences of that decisioin might even involve an apology or two. Many people want to be successful, but mistake that goal for the similar goal of being RIGHT. Blake |
Re: Who Has Programmed From Scratch?
Quote:
As for mentors, our team has always believed strongly that FIRST is an organization for students. We (the students) design the robot, we build the robot, and we code the robot. The mentors are there for our assistance when we ask for it. If this isn't how your team works and the mentors make the decisions, I'd strongly suggest doing something about this. FRC is a program for students, and your team should be for the students too. |
Re: Who Has Programmed From Scratch?
To answer your question directly: the only things left from the default code in the Begin and Finish vi's of this year's TechnoKats programming are the camera initialization and cleanup. Aside from the framework, everything else in them and in the entire Teleop is custom. We also played a little trick of our own that prevents typos in the RefNum Registry names.
Naturally, a twelve-wheel holonomic drivebase with full pushing power will tend to need completely different code than what the default 2-motor arcade drive has. |
Re: Who Has Programmed From Scratch?
Well its my first time working on a robot, I have written tons of code thats way past the 1000 lines, but they were games on the computer, its just a different feel
Well enough complaining, have a meeting in like 1.5 hours |
| All times are GMT -5. The time now is 06:03. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi