1629's Tripple-shot from center zone in Autonomous.

[dodar]

Our robot in autonomous is MONEY!

from all 3 zones

[PhilBot]

Originally Posted by Kage

how consistent is your kicker?
our robot has been landing shots continuously from all zones, without a camera in autonomous mode...
as long as it had a "drive perfecly straight" code using some encoders on the wheels, it usually kicks straight as an arrow...

Show me the video.....

[PhilBot]

Originally Posted by dodar

Our robot in autonomous is MONEY!

from all 3 zones

Talk's cheap... Show me the video..... (super )

[Greg McKaskle]

Phil, for the issues with the target in the far zone, what image size are you using?

Greg McKaskle

[fordchrist675]

That video was legit. I like your robot as well. Where are you guys competing?

[waialua359]

Originally Posted by Ricksta

True. But I go by the saying "You play how you practice".

True. But not everyone goes by your saying either.

Good job 1629! I suspect many are planning to do this just in case their alliance partners cant. 5 would be impressive and common at CMP.

[PhilBot]

Originally Posted by Greg McKaskle

Phil, for the issues with the target in the far zone, what image size are you using?

Greg McKaskle

Just the default... 240x160 I think.

Target size was OK, but I just don't think there was enough contrast.

[PhilBot]

Originally Posted by fordchrist675

That video was legit. I like your robot as well. Where are you guys competing?

Chesapeake & Buckeye (Baltimore & Cleaveland)

[sportzkrazzy]

It may be "money" from those zones but we can't get it to cross a berm and find the balls. Get your head out of the clouds dodar they one upped us there. nice work guys.

[Greg McKaskle]

You may need sleep, there is no 240x160 image size. Anyway, the reason I ask is that small images have bigger pixels which average over a bigger area. That means that automatically have a blurrier edge and a somewhat lower score. I think that the small image size works fine for close, but is difficult to work for third zone. Medium image works well for third zone, and you may be able to get small to work, but it is at a disadvantage.

Greg McKaskle

[PhilBot]

Originally Posted by Greg McKaskle

You may need sleep

Ain't that the truth! Anyway... It's the default that's used in the default program for vision tracking... 320x240 maybe...

On another topic... sorry to disrupt this thread....

We pass some status info back to the Driver Station to be displayed on the Cypress LEDs.

We've noticed a large delay in those status LEDs changing.

Eg: We have a "Compressor on " feedback light to indicate that the compressor has been "Enabled" by the operator.

The "Compressor On" status is simply the input (switch) bit echoed to the output (LED) bit inside the 100ms Periodic Loop.

In watching the I/O screen, and listening to the compressor we see a minimal delay between presing the Compressor On switch, seeing the DS Dig-In LED go on, and the compressor starting. However, there is an appreciable delay before the Robot returns a "Compressor On" feedback to the operator. It's not the Cypress because the DS I/O Screen Dig-Out LED shows the same delay.

The delay can be upwards of 2 seconds.

We can press and release the compressor ON button, hear the compressor start and stop, before the status LED changes. After about a second, we see the LED go on, and then off, so it seems like there is a message Queue that is full, and is taking about a second+ for any messages to pass through. (it takes me back to FTC Bluetooth issues)

This delay only seems to be related to uplink traffic, and based on the visual delay on the camera may also be effecting camera packets.

As far as I can see, Digital IO Output bits are sent with every uplink packet... so is there anything else that could be causing this lag?

Note: It happens even if we are running a BUILT program (not debugging)

Phil.

[Joe Ross]

How did it work at competition?

[PhilBot]

Originally Posted by Joe Ross

How did it work at competition?

Which "it"?

Never got a chance to try the tripple shot. We were having trouble holding pressure for the pre-match waiting period, so we knew we wouldn't have time to get off all three shots. Also, the approach ramps to the the bumps were changing our up and over speed requirements so that didn't help.

Maybe in Cleveland this weekend.

As for the Driver station feedback... I don't think the kids look down enough during a real competition for it to matter too much

[tim-tim]

Yea, we had several different indicators on the classmate to show our drivers what was going on, but reality was, they became too focused on the field. So what did we do, cut or losses and forgot about it? Not quite, we actually are going to place LED's on the robot as specific indicators of what is going on with the robot. Hopefully this will trigger faster response from the drivers.

Next up, a full head's up display integrated into a pair of safety glasses. Should be interesting.

See you in Cleveland in a few days

[PhilBot]

I heard you were fielding a smaller team for Cleveland. Need any specific help? (eg: programming or electrical etc?)

Also, as the only two MD teams, there was talk of splitting scouting duties.... We should sit together in the stands.

Phil.