Not really a reveal, just me being bored with a video editor.
Could you explain some of your design choices? Most specifically the mobile goal “lift”, which seems like more of a cage.
Why plates instead of c-chan
At the start of the season, our sister team had a 4-bar goal lift like a lot of teams are using. We decided to avoid copying that. We built this with the idea that it would be easier to tilt the goal and push it over than to pick it up.
It didn’t turn out as well as we hoped. I think we can change the gear ratio to increase the speed. We might be able to get it into the 20-point zone(right now, the robot can get the goal in, but it gets stuck on the bar).
With the gears up high, and wheels down low, we wouldn’t have been able to use the x2 channel, and the x5 channel is really bulky.
Also, our sister teams (like most teams) use c-channel for their frames, using plates means we’re not fighting over those parts as much.
when the bot is more suited for the ftc competition than the vex competition
nice
So do you ever use the unique design of the mogo lift to tip opposing mobile goals in actual match play?
“over 500 lines of code”
how???
I haven’t seen another robot even remotely like this for this years game, +1 for originality, Robot is one of a kind. Although the design does not look the best suited to this year’s game, it is very well executed, that robot is not going to break easily.
There have been past VEX robots with over 2000 lines of code
i know that, but the auton that their robot has does not seem that complicated. must just have a really good PID system
No. It can tip back cones that have fallen over pretty well though.
I’ve put the auton code in functions. I think these take up more lines than they should, but they work okay. I also have some extra control on the cone claw to prevent it from stalling.
I can upload the code if anyone is interested(it’s not well commented though).
We have ~1600+ in ours…
The functions don’t have to be pretty, they save space if you use them for lots cycles.
all steel xdxdxdxdxdxd
Sure 500 lines of code isn’t a record or anything, but it’s still a pretty decent amount. Our code for Worlds last year wasn’t much more than that and I was pretty proud of that. This shouldn’t be a competition for “I can write my code in twice as many lines as you!” Too much verbosity is not a good thing, especially when programming something (relatively) weak like the Cortex.
sniff… 20 lines of code for my team’s world bot. that should be a record in short length
Teach me the ways of the ultra compact code
stabilize everything mechanically, and be like
motor[base left1] = motor[base left2] = vexRT[Ch2];
motor[base right] = motor[base right] = vexRT[Ch3];
if(vexRT[BtnU]) motor[lift 1] = motor[lift2] = motor[lift3] = motor[lift4] = motor[lift5] = motor[lift6] = 127;
else if(vexRT[Btn5D]) motor[lift 1] = motor[lift2] = motor[lift3] = motor[lift4] = motor[lift5] = motor[lift6] = -127;
Why stop there? Just put everything on one line
motor[base left1] = motor[base left2] = vexRT[Ch2]; motor[base right] = motor[base right] = vexRT[Ch3]; if(vexRT[BtnU]) motor[lift 1] = motor[lift2] = motor[lift3] = motor[lift4] = motor[lift5] = motor[lift6] = 127; else if(vexRT[Btn5D]) motor[lift 1] = motor[lift2] = motor[lift3] = motor[lift4] = motor[lift5] = motor[lift6] = -127;
its hard to read then…
our programming computer is hard to scroll, so we make the code as compact as possible