Re: Intresting Autonomous
 

It's Team 1760. They're our physical neighbor in the same county, not a numeric one.

They weren't using the DS display when I saw their system. The "fancy readout" is a very nice knob with special gearing and a mechanical attachment to the shaft. They're common in applications using ten-turn pots. Here's one such device: http://parts.digikey.com/1/parts/746...-011-1-11.html

Re: Interesting Autonomous
 

If anyone gets a chance to watch the NYC Regional webcast (Saturday & Sunday), check out our auto-mode.
We're very proud of it, & it's completely intergrated into the drive system of the robot using a gyro as an assist, & is very cool in my opinion, but I'll let you all decide.
Comments welcome if you see it btw!
Thanks!

Re: Intresting Autonomous
 

Yep, we're both describing the same behavior - in LV the framework calls the Disabled.vi one time (at least) when the "derived robot state" is "stop", and at that point the DS inputs are read as zero. This is similar to that IterativeRobot race condition in C++.

I haven't looked at the DS packets to see whether the DS is actually reporting the state to be "enabed" or "disabled" when this happens, but we plan to check into it - it's a fun way to teach the kids about comm protocols and network analysis.

[EDIT: For anyone interested, after a quick glance at the LV WPI library code, it seems clear that the DS is actually reporting the state as enabled, the framework just intentionally runs the disabled vi an extra time to allow for clean up. So not a "race condition" but something to be aware of in the framework. You'll see what I'm talking about in the "Get Competition Mode.vi" which the framework uses to figure out what mode to run]

Ron
Team 2607 - software mentor

Re: Intresting Autonomous
 

It seems to me that, owing to symmetry, there are only three starting positions, so that with six autonomy choices a robot could have two options for each starting position.

Re: Intresting Autonomous
 

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

Re: Intresting Autonomous
 

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

Re: Intresting Autonomous
 

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.

Re: Intresting Autonomous
 

if u can get my status in to the green

Re: Intresting Autonomous
 

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!

Re: Intresting Autonomous
 

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.

Re: Intresting Autonomous
 

It's not straightforward to do with the LV basic framework. Take a look at the example code (using the LV advanced framework) attached to this post:

http://www.chiefdelphi.com/forums/sh...2&postcount=26

It shows reading the digital inputs, but the same principle applies to the DS analog inputs as well.

Thanks,
Ron
Team 2607 - software mentor

Re: Intresting Autonomous
 

You can read them in the Basic Robot Main outside the big case block, and store their values in a control in Basic Robot Global. Read the Global in Autonomous Independent to decide what to do with it.

You will need to delay storing by one loop time, because the Main gets called one extra time after Autonomous is enabled, with all the analog inputs at zero. I'd use a feedback node to pass the value to the next iteration of the loop. I think the other alternative, a shift register, clutters up the block diagram more.

Re: Intresting Autonomous
 

Team 904 is scoring autonomously as this video begins. This is a match in week 1 at the Traverse City District event in Michigan. The rest of the match is primarily focused on our team.

Re: Intresting Autonomous
 

Does anyone have a picture of 1254 if u do please post it. thanx:cool:

Re: Intresting Autonomous
 

My team has been searching for analog switches of the variety you speak of, but we haven't been able to locate anything that we were certain was what we were looking for. Could you please post a link to somewhere that we could purchase those switches? Thanks!