Competing in a Regional Soon ? - Watch out

[de_]

Make sure you have read and understood team update 14.

Today our robot was dead during part or all of 6 out of 8 matches even though it was completely mechanically functional. Twice it was caused by opponent teams robot smashing into the our wall in autonomous causing our laptop to blue screen and reboot and the second time crash on the floor and even after a reboot of the laptop, the robot autostart failed. Another team I am told had one or both of a laptop and tablet destroyed in a similar situation today. No penalty or consequences what so ever to the robots that caused it.

I think FIRST needs to immediately implement one or more of the following:

1) If a robot in autonomous crashes so out of control hard into the wall causing a driver station of the teams behind wall are immediately effected (ie their robot goes dead. a) the offending team should get no score for the match and or b) better still the match is immediately restarted.

2) Teams should be allowed to hold their laptop during autonomous so as to protect them.

All laptops are expensive fragile electronics. Velcroing them so they can be smashed about without consequence is ridiculous.

Dave Edwards
Mentor - Runnymede Robotics
Team 1310

[SenorZ]

Were you using the hook/loop on the station?
I recall some serious impacts in the past that didn't knock laptops over. Perhaps a foul for manhandling the field?

[ratdude747]

Teams should know that the driver's station will be slammed, hard. Sorry to be blunter than a dull chisel, but since it was in a team update, this was more or less to be expected.

[Sperkowsky]

Get some velcro. Enuff said.

[Ginger Power]

Originally Posted by de_

Make sure you have read and understood team update 14.

Today our robot was dead during part or all of 6 out of 8 matches even though it was completely mechanically functional. Twice it was caused by opponent teams robot smashing into the our wall in autonomous causing our laptop to blue screen and reboot and the second time crash on the floor and even after a reboot of the laptop, the robot autostart failed. Another team I am told had one or both of a laptop and tablet destroyed in a similar situation today. No penalty or consequences what so ever to the robots that caused it.

I think FIRST needs to immediately implement one or more of the following:

1) If a robot in autonomous crashes so out of control hard into the wall causing a driver station of the teams behind wall are immediately effected (ie their robot goes dead. a) the offending team should get no score for the match and or b) better still the match is immediately restarted.

2) Teams should be allowed to hold their laptop during autonomous so as to protect them.

All laptops are expensive fragile electronics. Velcroing them so they can be smashed about without consequence is ridiculous.

Dave Edwards
Mentor - Runnymede Robotics
Team 1310

We knocked a laptop off today. We apologized and made sure the teams laptop was ok. However, no penalty should be leveled against the team that knocks the laptop off, because the laptop won't fall off if you use the velcro. Simple solution: use the velcro. I think teams are also allowed to catch their laptop if it falls off (or if they're not, they should be).

[jajabinx124]

Originally Posted by Sperkowsky

Get some velcro. Enuff said.

Yea. We have velcro on our driver station now thankfully.. saw a couple driverstations fall down after robots just slammed into the wall.. pretty scary stuff for the driverstation laptop.

[Dezion]

Originally Posted by Sperkowsky

Get some velcro. Enuff said.

The velcro is exceptionally good.

You really want to punish the entire team for the thing one robot did? You really want to restart the entire match, despite how long and frustrating that would be?

Also, a rule would never be allowed that would let drivers hold their laptop. Way too much potential cheating involved in this.

I believe you're completely over-exaggerating the punishment and this scenario in general. StongHold is a very rough game, so it is your duty as a team to be prepared for it in all manners, not just preparing the robot.

[Dezion]

Originally Posted by Ginger Power

I think teams are also allowed to catch their laptop if it falls off (or if they're not, they should be).

They are:

Originally Posted by G14

During AUTO, DRIVE TEAMS may not directly or indirectly interact with ROBOTS or OPERATOR
CONSOLES unless for personal safety, OPERATOR CONSOLE safety, or pressing an E-Stop for
ROBOT safety.
Violation: FOUL and YELLOW CARD

[D.Allred]

What's wrong with G14? You can grab your laptop if someone is about to slam into the wall.

During AUTO, DRIVE TEAMS may not directly or indirectly interact with ROBOTS or OPERATOR CONSOLES unless for personal safety, OPERATOR CONSOLE safety, or pressing an E-Stop for ROBOT safety.

David

[orangemoore]

Originally Posted by Dezion

The velcro is exceptionally good.

You really want to punish the entire team for the thing one robot did? You really want to restart the entire match, despite how long and frustrating that would be?

Also, a rule would never be allowed that would let drivers hold their laptop. Way too much potential cheating involved in this.

I believe you're completely over-exaggerating the punishment and this scenario in general. StongHold is a very rough game, so it is your duty as a team to be prepared for it in all manners, not just preparing the robot.

How fair is it to have your robot not compete because someone's autonomous is intentionally(or not) written to run into the wall. It isn't fair to the team who can't play. Despite that team's best effort someone else's actions are what prevent them from playing.

[CalTran]

I mean, it's unfortunate, but you're also allowed to catch it if it's imminently falling.

[Anteprefix]

Originally Posted by de_

Make sure you have read and understood team update 14.

Today our robot was dead during part or all of 6 out of 8 matches even though it was completely mechanically functional. Twice it was caused by opponent teams robot smashing into the our wall in autonomous causing our laptop to blue screen and reboot and the second time crash on the floor and even after a reboot of the laptop, the robot autostart failed.

Dave Edwards
Mentor - Runnymede Robotics
Team 1310

I think this is a different situation if robots are running into walls so hard that the driver stations are BSoDing immediately without falling off. Velcro isn't going to prevent damage from blunt trauma to a hard drive.

[Dezion]

Originally Posted by orangemoore

How fair is it to have your robot not compete because someone's autonomous is intentionally(or not) written to run into the wall. It isn't fair to the team who can't play. Despite that team's best effort someone else's actions are what prevent them from playing.

It's really not fair to have your robot not compete because of this. I agree it is a huge issue for a lot of teams, but I don't believe punishing the team that did it in this scenario is the right response. I believe that it should be expected that this can occur, and teams should be prepared for this. Teams have to prepare for the game in all aspects. Having your driver station crash by being hit by the force caused by a robot prevents you from playing; having your robot break by bring hit by the force caused by another robot prevents you from playing. With the chance of a driver station crashing, causing the same effect as a robot breaking, shouldn't teams prepare for a robot hitting their castle wall as well as hitting their own robot?

Basically, I agree with this:

Originally Posted by ratdude747

Teams should know that the driver's station will be slammed, hard. Sorry to be blunter than a dull chisel, but since it was in a team update, this was more or less to be expected.

[orangemoore]

Originally Posted by Dezion

It's really not fair to have your robot not compete because of this. I agree it is a huge issue for a lot of teams, but I don't believe punishing the team that did it in this scenario is the right response. I believe that it should be expected that this can occur, and teams should be prepared for this. Teams have to prepare for the game in all aspects. Having your driver station crash by being hit by the force caused by a robot prevents you from playing; having your robot break by bring hit by the force caused by another robot prevents you from playing. With the chance of a driver station crashing, causing the same effect as a robot breaking, shouldn't teams prepare for a robot hitting their castle wall as well as hitting their own robot?

Basically, I agree with this:

If you are going to take this stance I have a question,

How do you plan to prevent your laptop from blue screening assuming your driver station is attached with velcro?


Currently the sentiment from FIRST would indicate to me that if I wrote an autonomous that ran our robot in the alliance wall on purpose there isn't much they would do to stop this.

FIRST has so far seems to have ignored the intent of someone hitting the wall. I'm sure if we blatantly hit the wall in an attempt to disable our opponents people wouldn't be very happy with us.

I'd like to see a change so that all teams shouldn't have to worry about this situation. As said in another thread

Originally Posted by Richard Wallace

Lazy auto programming should not be rewarded.

Most instances seem to be people not writing a proper autonomous code and ignoring the consequences by hiding behind the team update.

I want to see a better option than the current one.

[Kevin Sevcik]

I'll ditto the call for some intervention here. Velcro will keep a laptop from getting thrown to the ground, but it's entirely possible for a robot to hit the DS wall hard enough that it's equivalent to dropping the laptop on the ground. It seems like G24 (no strategies aimed at damage/disablement) should apply to repeat offenders. If your robot is slamming into the DS wall every match, it should be assumed your strategy is to disable your opponents' robots by damaging or dislodging their operator consoles.