Am I allowed to click a button during Driving Teamwork that will run a quick automatic drive sequence? So when I click a button on the controller it will drive the robot automatically to a certain place on the field.
This would definitely be allowed, but youâll want to carefully consider any sort of triggered routines you implement for use during driver-control. To take your example of driving to a specific point on the field, that could be incredibly difficult to achieve in a teamwork match (or even a driver skills match) unless it was the very first action taken from the start. Even then it would likely only be reliable if it was the very first action you took with the robot from the start and the other teamâs robot didnât interfere with the path or landmarks youâd use to navigate to that fixed point.
The advantage of drivers controlling the robots is that they can react in real-time to the unpredictable (especially this year in Rapid Relay) conditions on the field in ways that the IQ platform simply wouldnât be capable of using automation.
That said, there can be a lot of value in building semi-automation into the non-driving/navigation mechanisms on your robot so that you can have a single button press perform reliably repeatable sequences of actions so the drivers can focus on getting the driving âclose enoughâ to let those mechanisms do what they need to do.
I was really just looking to align the robot perfectly for a shot, in Rapid Relay.
So Thank You!
Autonomous in my opinion would be more inconsistant than humans. This is because human driving is faster and more polished and you would half to align in a specific spot originally either way.
(disclaimer: I have never competed in VIQRC and my answer here relates mostly to my VRC experiences)
The success and effectiveness of any autonomous routine will depend on its optimization, meaning that for an idea like this to be successful, you will need to make a great deal of effort to identify potential sources of errors and make provisions to correct them. Depending on what task youâre looking to accomplish with this routine, it is possible (but very difficult, especially in VIQRC) that autonomous routines could be more accurate than human drivers. Competing in VRC, some teams have optimized autonomous routines (both in skills and matches) that are more optimized than if these routines were performed by human drivers.
Even if there are limitations to the IQ platform, I think that exploring an idea like this could be useful if it is optimized enough. I would only consider spending any significant time on this after working more on the robot itself and human driving.
I think if you have an odometry running while your Teamwork Matches are running so the robots knows where it is. Then, the robot can calculate the distancce and angle it needs to travel to reach the point to chore the balls.It will be complicated but it might be quicker than driving.
Maybe I am wrong but the game manual seems pretty clear about this
You would also have to explain this to the judges. I suppose you could get away with it and it might be good if you donât have a good driver but I feel itâs not quite in the spirit of the game and thereâs a reason that driver skills scores more points than autonomous majority of the time
I donât see anything in your screenshot that says anything about using an autonomous portion during driver control.
The answer is yes, this is allowed. It sounds like a very promising idea.
You would certainly want to discuss this with the judges during your interview: using semiautomatic routines to assist the driver is clever and innovative, and demonstrates programming skill.
The referees would be concerned with rule SC1 in the game manual, where it addresses a pre-programmed routine running after the timer reaches zero.
I somewhat agree with you. Never in the manual does it say anything that would prohibit you from running an autonomous during a skills match however the handy table there shows that for driver skills it is 1:00 of driver controlled period. I assume that this is mostly theoretical though, as I would say most drivers are probably going to be better. Where I could see this working is trying to line up a shot if the driver(s) donât feel confident in their ability to line up the shot. It would be interesting but I feel like even less confident drivers could still improve enough to not need an autonomous to assist them.
I suppose if someone wanted to, they could submit a Q and A but it seems probably legal is there is no rule against it.
Vex IQ doesnât have rotational sensors.
The VIQ Brain has an inertial sensor and a rotational sensor.
Wait what? Vex IQ has rotational sensors? I can code odometry??
The IQ (v2) brain has an inertial sensor, and individual gyro sensors are also available. Iâm quite sure IQ does not have rotational sensors.
You mightâve confused the ârotational sensorâ with the heading/rotation recorded by the inertial sensor. Everything the brain records in terms of heading/direction/etc. is part of its inertial sensor.
(sadly, odometry will probably not happen in IQ anytime soon)
Then please refrain from answering IQ threads.
Others who know what they are talking about have given good answers. If you know that answer, put that and move on. If you donât know the answer or you donât have any relevant experience, just move on. This thread is now less useful to the community because of all of the extra stuff. If someone wanted to know the answer to the question that is in the title of this thread it should be very easy to find.
This thread should be two posts long. That would have made it more useful to those that come after us.
Well, I am trying to do this for Rapid Relay. What is the bare minium for an odometry to work?
The IQ Smart Motors can be used as sensors showing how much rotation theyâve completed, at least under power. I havenât tried it, but you might well be able to have a free-wheeling sensor by setting the motor stopping to coast, but Iâve not tried it to say for sure. As others have noted the Gen2 Brain has a 3 axis inertial sensor, and there are single-axis gyro sensors from the Gen1 era.
The Autonomous Period defines when the robot is only allowed to operate autonomously. Programming a routine and binding it to a button is still absolutely driver control. I would argue even that having a pre-programmed routine that triggers based on sensor input or some other less-explicit action would also be fine.
I think it would be fair to say that the intent of having separate Autonomous Periods is not to prevent more complex programming in Driver Controlled Periods, but to encourage teams to dive into more complex programming, rather than just building fancy RC cars.
For somebody who didnât do IQ, he was to my knowledge actaully correct. There is no reason if hes helping people out he canât be a part of the discussion
Thats true, Iâv made an odometry with motors I was just very curious as to if there were actual rotation sensors, this would change everything.