Intresting Autonomous

[Vikesrock]

Originally Posted by Hazmatt

Ideally we would have had a "field position switch" which would allow us 3 different autonomous modes, but unfortunately a firmware update disabled this ability for us. Also unfortunate was that we already had the control panel made with the switch mounted.

Switches on the DS side can still be read and used to select Autonomous modes. The difference is that they now cannot be read in Autonomous/Enabled mode. Read them in Autonomous/Disabled and cache the values for use during Autonomous/Enabled. Also, there are reports that the values return incorrectly from the last cycle of Autonomous Disables, so make sure your code has a way of dealing with this.

[rrossbach]

Originally Posted by Vikesrock

Switches on the DS side can still be read and used to select Autonomous modes. The difference is that they now cannot be read in Autonomous/Enabled mode. Read them in Autonomous/Disabled and cache the values for use during Autonomous/Enabled. Also, there are reports that the values return incorrectly from the last cycle of Autonomous Disables, so make sure your code has a way of dealing with this.

Our team did some experimenting and found that at least in LabView, the last time Auto Disabled runs the DS input values are in fact zeroed out just like they are if you try to read them during Auto Enabled. I assume the C++ handling is similar but we have not checked that.

It's hard to handle this in the LabView Basic Framework, but is pretty straightforward in the Advanced Framework - attached is an example Disabled.vi for the advanced framework that shows this, hope it's useful! The AutonMode.vi also attached is just a simple "functional global" variable. Autonomous Independent just reads the cached value.

Ron
Team 2607 - software mentor

[Hazmatt]

Originally Posted by Vikesrock

Switches on the DS side can still be read and used to select Autonomous modes. The difference is that they now cannot be read in Autonomous/Enabled mode. Read them in Autonomous/Disabled and cache the values for use during Autonomous/Enabled. Also, there are reports that the values return incorrectly from the last cycle of Autonomous Disables, so make sure your code has a way of dealing with this.

Where exactly in the labview code should we read the analog inputs? Should we read them in the basic robot main vi under the "Other" section? Or is there somewhere in the autonomous independent code that we should put it? Thanks!

[IceStorm]

Originally Posted by TVan

we did not make this autonomous up and were scored on in autonomus,
and we were on the winning alliance. Selected by 2645 (a Great Team, thank you ) and played with 247 (The Bears rock )

The most intresting or gut wrenching was our robot taking off at a slow speed than insted of one side forward and one backward both forward full speed into the driver station on the other side of the field. who ever thought up the bumpers on the driver station wall thank you. ( did you flash it )

Tim

Team BOB! You guys have an awesome robot. It was a blast to have been picked to play in the quarter finals with you and look forward to seeing you again over at West Michigan.

[scoutmasterlord]

http://s255.photobucket.com/albums/h...City%20Videos/


this is alot of team #201 matches.

[raffi383]

Originally Posted by scoutmasterlord

http://s255.photobucket.com/albums/h...City%20Videos/


this is a lot of team #201 matches.

scoutmasterlord,

Thanks for posting the link to the 201 website. I have more videos to upload but converting them from 265Mb avi to smaller mpeg is taking a while.


I also want to thank TVan from team 85 for admitting that they did not invent "auto-spin".

I can't say that we invented it either but it was programmed in the robot when we got to Traverse City and we used it in every match.

I haven't counted how many balls landed in the trailer during autonomous but it wasn't very many.

I especially like the video of Qualifying Match 38 where 85 and 201 were doing synchronized spinning.

It seemed like more and more teams used auto-spin as the weekend went on.

By the time we get to the Detroit regional, there will probably be six spinning robots in each match.

Raffi

[raffi383]

I had to do it. I watched all the videos to see how many times we were scored on in autonomous.

I don't have video of match 1 or 8 but I have the rest.

I counted all the balls that landed in the trailer from the start until the buzzer at the end of autonomous when the robot stops spinning.

Here they are listed by match number and ball count:

18: 0
21: 0
27: 0
38: 0
43: 2 we got trapped
47: 0
55: 0
59: 0
68: 0
72: 0
Qtr 4-1: 0
Qtr 4-2: 0
Semi 2-1: 0
Semi 2-2: 1
Semi 2-3: 2, one was scored by our own alliance member


Raffi

[Alex Dinsmoor]

Originally Posted by raffi383

I had to do it. I watched all the videos to see how many times we were scored on in autonomous.

I don't have video of match 1 or 8 but I have the rest.

I counted all the balls that landed in the trailer from the start until the buzzer at the end of autonomous when the robot stops spinning.

Here they are listed by match number and ball count:

18: 0
21: 0
27: 0
38: 0
43: 2 we got trapped
47: 0
55: 0
59: 0
68: 0
72: 0
Qtr 4-1: 0
Qtr 4-2: 0
Semi 2-1: 0
Semi 2-2: 1
Semi 2-3: 2, one was scored by our own alliance member


Raffi

I can tell you that in match #1 that we didn't get a single ball scored on us during auto. I was reviewing the crude video that I took, and I didn't see any balls go into it.

And for future reference try to edit your earlier post to include the extra info if no one has replied after you.

[scoutmasterlord]

if u can get my status in to the green

[Chris Hibner]

Originally Posted by raffi383

By the time we get to the Detroit regional, there will probably be six spinning robots in each match.

Raffi

A lot of teams might incorporate that, but we will never use that - our autonomous has been pretty unique and is key to our strategy. I also don't see 70/494 spinning in auton.

[DtD]

That's basically what ours did.
It went forward for a few seconds then spun around. It also calibrated our ball dumper (which is kinda cool to watch btw, I might upload a video when our bot gets back.)

~DtD