During Driver control, is there a certain amount of programming that is not allowed? Just trying to think of the Driver Control definition. Can the entire match or even half of the match be programmed autonomously if one student is “holding” the controller but still passes it off to another student even if they are not “actively” driving the robot?
Idk if it’s possible in iq but you can code a button macro which allows you to press a button and run an autonomous code (100% legal). Also, the longest code I’ve seen (edr) is like 5,000 lines. There’s no limit to how much code you have other than the capabilities and the speed of the system.
Wouldn’t you be concerned about the partner team accidentally interrupting the program?
not if it’s during the skills period that way it would be fine.
If you check page 7 of the game manual (https://content.vexrobotics.com/docs/vrc-tower-takeover/GameManual.pdf), look at the definitions of “Driver Controlled Period” and “Autonomous Period.” As you can see, there is no wording in the game manual that restricts what you can do during “Driver Control.” Since the game manual is the only source of rules for the game, then it’s legal (provided you don’t break any other rules). As you read the manual, remember that for the game, the manual generally tells you what you can’t do. If the manual doesn’t say you can’t, then go ahead. If you do some programming that gives you a semiautomatic control system, be sure to tell the judges during your interview–it might lead to an award.
That’s true (20 char)
Yes. That is the main issue. This is mainly for IQ and it was tough for our kiddos to strategize. They managed and did fine, but I wanted to see if this is common amongst other.
It is possible in IQ and many of our teams do code certain buttons to make it more efficient for them. But not and entire 35 seconds worth of code.
I’m just curious to see if anyone else does it.
But what about in IQ? There is no autonomous portion during the team alliance.
I was refering to the skills portion of the game. But what this topic was refering to was if a team were to use an autonomous program in driver control.
I thought I saw a team from New Zealand did this last season (Next Level) an posted on youtube. First driver had a preset button that ran the 8 point portion of their autonomous program. I think it ran like for 25 seconds or so and scored the 8 points on the square building zone, then the driver took over.
It was possible with Next Level because alliance teams at the beginning went in 2 different directions, so this team had 1 whole section of the field to themselves while their partner was working on the other side.
But the question to ask is whether or not running an autonomous program instead of driver control is more effective and efficient. Typically autonomous can’t react and adjust like humans, and most teams will program their autonomous to drive slower with more wait time so they’re more accurate. This will mean your team is wasting precious time running an autonomous instead of driver control.
Programmed button moves and sensor responses, imo, are legal and good to any level of complexity and duration that the team members can understand and defend to the judges. (Student Oriented)
We have to sequences on our controller that places the cubes on low / high towers and picks up ball and it works 95% of the time, I would only use programming during driver to do simple tasks that have a success rate of over 95%,last year at nationals in NZ nakibots C had there first 30 s of the match completely autonomous, becausw they couldn’t find a good enough partner driver
Yes, this is what happened here as well.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.