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 …

Name: Fully autonomous driver control
Uploaded: 2019-08-29T00:11:49Z
Description: [Fully autonomous driver control]

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 Cont…

[image] WPI1 Reveal Here is a reveal and explanation of Vex U team WPI1’s completely autonomous robot that we competed at worlds with. [image] WPI1 Reveal Here is also one of the matches I filmed. [Fully autonomous driver control]

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.