|
|
|
#1
|
|||||
|
|||||
|
Al's Annual Inspection Thread 2015
OK, it is that time again so I will start here with Bumpers (Yes, I have had several teams report that they intend to add bumpers this year).
Yes, you can add bumpers this year but they are entirely optional and... 1. They must be weighed as part of the robot weight, and that total cannot exceed 120 Lbs, R4. 2. The bumpers when attached must also fit in the TRANSPORT CONFIGURATION R3. 3. Bumper construction will be inspected for potential safety hazards and attachments like any other robot parts. 3. As bumpers are entirely optional, they do not need to cover specific areas of the frame perimeter. 4. Bumpers do not need to be constructed as suggested in the Bumper Design Guide found here. Be aware that the guide is a tried and tested design. In addition to the rules as published, Team Updates come out on Tuesday and Friday each week. If Team Update changes or modifies a robot rule, that change will be part of the inspection process at subsequent events. I would like to point out a Team Update was published Friday, 2/6/2015, concerning custom MXP boards. This is not a change in the rule but a clarification to make it easier to understand and flow chart is included. Restated, if you have any active components on your custom made MXP board and you are using any of the PWM outputs on the MXP connector for controlling motors or servos, the board can only be one of the three pre-approved boards listed in R58. More to come later... |
|
#2
|
|||||
|
|||||
|
Re: Al's Annual Inspection Thread 2015
Unless you're going to install the bumpers (in under 60 seconds) once you reach the playing field.
|
|
#3
|
|||
|
|||
|
Re: Al's Annual Inspection Thread 2015
Quote:
Maybe delete "when attached" from the bullet point. |
|
#4
|
|||
|
|||
|
Re: Al's Annual Inspection Thread 2015
Quote:
Any thoughts on why Custom Circuits cannot be used for PWM, but are allowed on the CAN Bus, and thus might be controlling the Motor Controllers? |
|
#5
|
|||||
|
|||||
|
Re: Al's Annual Inspection Thread 2015
Quote:
Quote:
|
|
#6
|
||||
|
||||
|
Re: Al's Annual Inspection Thread 2015
Because R59 say all motor controllers on the CAN Bus must be controlled by the RoboRIO and R62 says CUSTOM CIRCUITS or other devices that interfere with those communications are not allowed.
|
|
#7
|
|||||
|
|||||
|
Re: Al's Annual Inspection Thread 2015
Gus,
The TRANSPORT CONFIGURATION will be determined during inspection at the same time as weight. Under Tournament rule T6 there is no provision for removing bumpers to determine size limits. T6 While transferring the ROBOT throughout the event (e.g. between the Team’s Pit, Practice Field, ARENA, Inspection Station, etc.), the ROBOT must not exceed a volume that is 28 in. wide x 42 in. long x 78 in. tall (the TRANSPORT CONFIGURATION). (Emphasis is mine.) Safety is our prime concern for everyone involved. As such, nothing may cause robot movement until and during the times the robot is enabled by the Field Management System. |
|
#8
|
|||
|
|||
|
Re: Al's Annual Inspection Thread 2015
There is also no rule requiring bumpers be attached at their operating position for Transport Configuration. During TC, the bumpers could be sitting inside the robot, and on the field quickly attached with pins.
|
|
#9
|
|||
|
|||
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
|
#10
|
|||||
|
|||||
|
Re: Al's Annual Inspection Thread 2015
John and Rich,
It is my understanding, that bumpers, if used, are part of the robot, just like an arm, a pickup device or the control system. That means that the bumpers are not considered separate of the ROBOT and all rules apply. As such, the bumpers need to be mounted on the robot for weight and size. I suppose you can (for this year only) have bumpers on moveable parts that retract the bumpers into the robot for determining the TRANSPORT CONFIGURATION. Just as in the past, if you have multiple devices that can be used on your robot, all mechanisms must be weighed together, and the overall size will need to be determined for each configuration under R4. The change in the bumper rules applies to this season. There is no telling what next season will bring. |
|
#11
|
|||||
|
|||||
|
Re: Al's Annual Inspection Thread 2015
Quote:
R3 allows for minor disassembly to be made to get the robot into its transportation configuration. This would allow them to take the bumpers off and place them somewhere on the robot inside the size constraints. Then when they get on the field they would be allowed to reattach them prior to the match. |
|
#12
|
|||||
|
|||||
|
Re: Al's Annual Inspection Thread 2015
Quote:
Quote:
|
|
#13
|
|||
|
|||
|
Re: Al's Annual Inspection Thread 2015
I can't see how the GDC could suddenly declare the optional non defined bumpers to be required to be attached AND within the Transport Config at this point. I suspect a fair number of teams have quick attach/detach bumpers outside the TC that might also have integrated into them other critical mechanisms/purposes.
But I'm guessing since Al is in contact with headquarters, we'll see something about it either way on Tuesday or Friday, if not before from Al on this thread. |
|
#14
|
||||
|
||||
|
Re: Al's Annual Inspection Thread 2015
Quote:
We have also come in a little bit underweight, so we do plan on removable bumpers this year that are bungeed to the elevator tower when not in use, and dropped into place when the robot's on the field. |
|
#15
|
|||||
|
|||||
|
Re: Al's Annual Inspection Thread 2015
Quote:
Let me put it this way: Right now, my team is considering pinning an item or two onto our robot. Push item onto robot, push pin in, compete, remove pin, remove item and stick in robot, away we go. If minor disassembly is not allowed, we will have to add or modify a full subsystem to accomplish the same task. In one week. It would have been nice to know this, say, two weeks ago. I also agree that we'll probably hear back either from Al or from an Update very shortly. *If an inspector (or ref, or field staff) does override the Manual, we can usually expect a blog post in apology if it's anything like a major incident, and a Q&A clarifying if it's not a major incident. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|