Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   General Forum (http://www.chiefdelphi.com/forums/forumdisplay.php?f=16)
-   -   2046 robot stolen (http://www.chiefdelphi.com/forums/showthread.php?t=146329)

Alicia V 27-03-2016 22:47

Re: 2046 robot stolen
 
Wow! Thank you all so much for the support. We will be busy this week building up our practice bot and I am confident we will be able to do this. A local news station is covering this and we are using it as an opportunity to spread the message of FIRST instead of get pity from the public. The only changes that need to be made on our practice bot is gonna be the hubs on our drive train and a more robust pneumatics and electrical. Our shooter and collector were taken off before packing in the trailer so we have those to work with. Code will be tweaked but we can definitely do it. Team 2907 had a majority of their tools stolen from our trailer as well as batteries. Thank you all so much and we hope to see you this weekend with a competitive bot!

Bearium 27-03-2016 22:56

Re: 2046 robot stolen
 
1 Attachment(s)
Thanks to everyone willing to help us in one of greatest times of need. We know that everything that is happening is a huge potentially crippling blow to our team. However, we will not let this hinder our abilities as a team, we are simply going to pick ourselves up and keep moving forward, it is the best for us and is best for what we need to do right now.
We do have possession of our collect/defense defeater and our shooter from our competition bot and we will have our local news get our story out. Hopefully we will be able to recover whatever we can of Xcalibear. For now, we are going to simply keep going and compete with what we have, Sir Bearington, our practice bot.
It will be a hard road ahead of us and we are going to to take on this challenge headfirst and jump back into competition this weekend at Auburn High, then Portland and ultimately to St. Louis. We plan on doing what we do best and keep on going til the end of the season.
Again, thank you all for lending a kind word or a helping hand. We are grateful for what you all are trying to do for us and we will certainly let you know if we need anything.

pntbll1313 27-03-2016 23:18

Re: 2046 robot stolen
 
That's awful. Your team has a great attitude and seems to be pushing forward! Since you have a practice robot you may want to ask some local teams with spare withholding weight if they can bring in some items for you. R18 gives a little leeway as long as they give you permission to use things they bring in.

R18 At an Event, Teams may have access to a WITHHOLDING ALLOWANCE of FABRICATED ITEMS, not bagged per R15, to be used to repair and/or upgrade their ROBOT. The WITHHOLDING ALLOWANCE is a static set of items that shall not exceed 30 lbs. With permission from another Team, Teams may also have access to FABRICATED ITEMS that are part of that other Team’s WITHHOLDING ALLOWANCE to repair and/or upgrade their ROBOT. The WITHHOLDING ALLOWANCE may only be brought into the Venue when the Team initially loads in at the Event. Items made at an Event do not count towards this weight limit.

EricH 27-03-2016 23:24

Re: 2046 robot stolen
 
Quote:

Originally Posted by pntbll1313 (Post 1563896)
That's awful. Your team has a great attitude and seems to be pushing forward! Since you have a practice robot you may want to ask some local teams with spare withholding weight if they can bring in some items for you. R18 gives a little leeway as long as they give you permission to use things they bring in.

No offense, but this particular event type (robot missing, presumed scrap) would generally cause R18 enforcement to be "temporarily suspended" for that particular team, as long as HQ was notified. Also, they've got an unbag window.

There are protocols in place. They just aren't usually used because there isn't much cause to use them.

acstaton99 27-03-2016 23:39

Re: 2046 robot stolen
 
I am saddened to hear about this loss. My team is relatively small so the best we can offer is our best wishes. My advice would be to file a police report and to try to come back from this stronger. Best of Luck.

Sean4488 27-03-2016 23:49

Re: 2046 robot stolen
 
This is awful to hear, especially for such a talented and friendly (not to mention successful) team. Hopefully the robot can be found in time for auburn next week, or district champs, best of luck guys. If there is anything that we can do to help let us know.

nedwards28 28-03-2016 00:09

We are super bummed to hear what happened! I always get worried when we travel. It's too easy for a trailer to get hijacked. What's I find odd is it would seem selling a robot and the parts on the back market wouldn't seem profitable. The tools and pit items sure but, a robot? It's sad that this would ever be an issue. :(

Team 4980 is happy to offer help as well, even if it's something as small as a selection of nuts and bolts for the pit. Those things add up! Cheers to your incredible team. We enjoyed watching you online this weekend!

Jsteel 28-03-2016 00:28

2046 robot stolen
 
To our fearless alliance leader from the Stormbots - we are saddened by your news and willing to do anything needed to help. However, getting to know you a little at Philomath, we learned just how good your team is - you are already champions and we have full faith you will return in full Bear Metal form.

Bob Steele 28-03-2016 01:36

Re: 2046 robot stolen
 
You guys were great on Saturday and claimed a well deserved blue banner it was great competing with you.

What is ours is yours. Just let us know. We are always next to you in the pits and your team is next to us in our hearts too. I know you can do it, you are a wonderful team.

Skunk Works.

rich2202 28-03-2016 07:09

Re: 2046 robot stolen
 
It is not an R18 exception you want (withholding), it is a R16 exception (bag and tag rules). With no robot in a bag with a correct seal number, you will fail R15/R16.

What i would do is email First HQ with the following:

1) Explain the situation
2) Include a copy of the police report, or if that is not yet available, the report number (proof of event)
3) Explain what you would like to do:
a) use the practice robot for your Robot
b) Perform the following modifications in order to make it functionally identical to the robot that was bagged
c) Bag the robot by <date>
d) Use the following withheld parts for the R18 rule.
4) Request an exception to R15/R16 for the above due to the unusual circumstance.

Assuming that First e-mail's you an exception, I would then print out your original e-mail, First's email giving you the exception, and attach that to your lock/unlock form that has the current tag number.

Type 28-03-2016 07:20

Re: 2046 robot stolen
 
Quote:

Originally Posted by rich2202 (Post 1563991)
It is not an R18 exception you want (withholding), it is a R16 exception (bag and tag rules). With no robot in a bag with a correct seal number, you will fail R15/R16.

What i would do is email First HQ with the following:

1) Explain the situation
2) Include a copy of the police report, or if that is not yet available, the report number (proof of event)
3) Explain what you would like to do:
a) use the practice robot for your Robot
b) Perform the following modifications in order to make it functionally identical to the robot that was bagged
c) Bag the robot by <date>
d) Use the following withheld parts for the R18 rule.
4) Request an exception to R15/R16 for the above due to the unusual circumstance.

Assuming that First e-mail's you an exception, I would then print out your original e-mail, First's email giving you the exception, and attach that to your lock/unlock form that has the current tag number.

I'm assuming they already called First. My team has called First (in Michigan) to see if we could open our bag before because of something before that we left in, or something odd like that. I'm pretty sure they would make an exception to that rule since their robot was stolen, it's not like they will be opening their bag to make their robot better. I don't think First will care, but of course they still need to check but I wouldn't be surprised if they did already.

Too bad your team isn't closer, I talked to a lot of my team and I'm pretty sure half of us, if not all, would be doing whatever we could to help you. I know all the team's in the area where my team competes would send help just because it's how the First Community is. Good luck with your robot! I can't imagine hown it would feel for somebody to steal your robot...

Mr. Ackroyd 28-03-2016 08:07

Re: 2046 robot stolen
 
So sorry to read about this. I hope everything turns out for the better. I would encourage all teams to access twitter and retweet Bear Metals posting. The more this gets out, news agencies will see the posts.

InFlight 28-03-2016 08:32

Re: 2046 robot stolen
 
3574 will be with you in Auburn. Would be happy to help with anything you need. Our pit is your pit.
If you need any driver station setups or cots parts we could bring those too.

xmutantson 28-03-2016 09:59

Re: 2046 robot stolen
 
5683 will be with you as well in your auburn event. look for the ravens. our pit is your pit, we will help as much as possible. don't expect too much, we're a second year team.

philso 28-03-2016 10:19

Re: 2046 robot stolen
 
Quote:

Originally Posted by rich2202 (Post 1563991)
Assuming that First e-mail's you an exception, I would then print out your original e-mail, First's email giving you the exception, and attach that to your lock/unlock form that has the current tag number.

Sorry to hear about the theft of your great looking, and performing, robot and support materials. It is great to see your team's positive attitude in this difficult situation.

It would probably be a good idea to confirm that FIRST will also send a copy of any exceptions to the organizers of the Auburn Event and any subsequent events that your team may be going to so they will be expecting you and won't feel the need to confirm with HQ when they see your exception printed out.

Best of luck.


All times are GMT -5. The time now is 08:38.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi