![]() |
Re: New robot rules at Peachtree
OK - as the LRI who "started" this, some background.
When I saw the designs of a number of teams at our scrimmage, I became concerned about the potential for injury due to the potential for the "stored energy" mechanisms to accidentally deploy while being handled. In discussions among the LRI's, it became apparent that I was not alone. Week 1 events announced the "requirement" for a safety interlock if the robot was to be moved in a stored energy state. I proposed this to my Regional Committee who decided to await further developments before announcing the policy. As results of injuries - even minor ones - began to come in, and bolstered by the GDC's Team Update - we decided to emphasise the need for a safety device. As noted previously by Dr. Bob, who worked with me to develop the wording of the announcement, this was not a decision taken lightly. His post accurately describes the thinking behind the process It is not my nor the Peachtree Committee's intention to place an undue burden on teams, but as noted earlier, the intent was merely to inform teams that the inspection team would be looking for safe operation of the teams' robots - particularly when being transported. As stated in the notice to the teams, recognizing the implications after Stop Work day, the implementation of a "safety device" - probably better wording in hind sight than "safety interlock" - the weight of the device wouldn't be counted in the 45 pound limit for fabricated parts and as long as it was "removed" from the robot in the starting configuration, would not be counted in the robot weight. I also noted that the inspection team would be open and receptive to innovative safety devices. As has been noted, the expectation is that the device would be as simple as a bolt through a rod, a strap or tie-down to restrain the mechanism, or any equivalent simple device - not to require some elaborate device that would place a burden on teams. Also, as has been noted, my intent was to get the word to the teams prior to the event so they could think about it and develop a simple, basic device to assure the safety of their mechanism and to meet the intent of this policy. Suggestions in this thread alone are basic, easily implemented devices for many designs. If a team's device is inherently "safe," the inspection team will require nothing more. I trust that teams will agree with the intent of the policy. My and the Committee's only intent is the safety of the participants. Jeff Rees LRI Peachtree Regional |
Re: New robot rules at Peachtree
Quote:
None of these "unofficial" updates where conveyed to us before the event. |
Re: New robot rules at Peachtree
Quote:
|
Re: New robot rules at Peachtree
I applaud everyone involved in this decision for pushing for changes to help ensure the safety of all participants. Considering the inherent risks of transporting a loaded stored energy device, in the interest of safety wouldn't the best solution be to not allow these devices to be transported in a loaded state at all? Especially considering the concerns expressed by some regarding the safety of actually applying the lockout device to a loaded stored energy device, it seems that the safest solution would be to transport your robot to the field while the device is not loaded, then tether up and load the device once on the field.
|
Re: New robot rules at Peachtree
Quote:
Our main breaker was installed about an inch in from our chassis perimeter out of reach of any moving mechanism. We where told to move it within 2 inches of our shooter arms. |
Re: New robot rules at Peachtree
Quote:
FYI, if you disagree with an inspector, ask to see the LRI, and the copy of the Manual the LRI should have with him. |
Re: New robot rules at Peachtree
Quote:
|
Re: New robot rules at Peachtree
Quote:
|
Re: New robot rules at Peachtree
Quote:
|
Re: New robot rules at Peachtree
Quote:
On the practical side, there is not enough setup time on the field to allow some robot designs to fully charge their air systems. Charging while in the queue line doesn't help since the most dangerous time, in my opinion, is between removing the robot from the cart and placing it on the field; here is where kids are in close contact with the robot. Likewise for some spring systems. The compromise is to design the robot so it can't accidentally deploy while being moved. |
Re: New robot rules at Peachtree
Quote:
Quote:
Quote:
|
Re: New robot rules at Peachtree
Quote:
|
Re: New robot rules at Peachtree
Quote:
|
Re: New robot rules at Peachtree
Quote:
Quote:
|
Re: New robot rules at Peachtree
And Tristan - isn't it nice to know how a rule as vague and all encompassing as R08 is going to be handled before you actually get to the venue?
The LRI here could have just kept quiet until the event, then walked around telling teams they needed to rig something at the event, and there would have been no room for complaining. Instead, a pro-active approach to the issue is raising complaints here. |
| All times are GMT -5. The time now is 16:40. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi