![]() |
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... |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
Maybe delete "when attached" from the bullet point. |
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? |
Re: Al's Annual Inspection Thread 2015
Quote:
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
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. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
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. |
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. |
Re: Al's Annual Inspection Thread 2015
Al - Is the only option retraction for bumpers? The blue box under R3 states the TRANSPORT CONFIGURATION size constraints can be met with "minor disassembly"., And references G10, which gives a guideline of 60 seconds for on field configuration. I guess the question boils down to the definition of "minor disassembly". Having a set of bumpers that can be removed and placed inside the robot for transport, then attached quickly with a couple of wing nuts seems to me to meet the intent of the rules.
|
Re: Al's Annual Inspection Thread 2015
Al,
I can see situations where the only time certain parts, not limited to bumpers, are mounting on the robot is outside of transportation configuration. The rules allow for pieces to be removed from the robot to make it fit in the TC. If all parts of the robot are to be attached at weighing, the robot should not be expected to be within TC. Simply put, being within the TC and having all parts attached might be mutually exclusive for some robots. |
Re: Al's Annual Inspection Thread 2015
'Bumper' is not even a glossary item and as such appears to have no special distinction as compared to other attachments or robots components/assemblies/mechanisms. In fact, there is no definition of where the boundary between a bumper and a non-bumper element is. If I want to call my steel bar located in the center of my robot a bumper, there is no rule that says I can't do so, and doing so has no impact on any aspect of the rules, as near as I can tell. Heck, I can claim my RoboRio is doing double duty as my bumper.
Edit: Having said all that, there is much practical benefit to not having teams remove and attach bumpers for every match. We've seen how that works in the past for many teams, but I don't think the rules speak to the issue. |
Re: Al's Annual Inspection Thread 2015
Hi Al,
I am a bit confused. I thought that bumpers could be attached on the field as long as they go on within 60 seconds (or reasonable time) G10 & G11 and fit within the TRANSPORTATION CONFIGURATION. For example, if I have an upright on the robot (that only rises 6ft) and I use a bungie cord to temporarily secure my bumpers to that upright that is legal within the rules? Does Q&A Q189 say that that bungie cord would not count against the total robot weight? Thanks, Austin |
Re: Al's Annual Inspection Thread 2015
I have a specific pneumatics question - can air cylinders be plumbed with no control valving (solenoid or otherwise)? I.e. always pressurized in a given configuration so they act as a constant-force spring.
Related to bumpers - I wouldn't even call them "bumpers" anymore, as that term is associated with a part or parts subjected to specific rules and exempt from volume and weight rules. Bumpers, as in BUMPERS specifically defined by the manual, do not exist in this year's game. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
James, I'm not aware of any rules that would prohibit that, providing you meet all rules, of course (the cylinder is on the low pressure side, you have all required components for a pneumatic system, everything is properly rated, etc)
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
I am not referring to a permanently sealed or pressurized air cylinders. I just want to put 60psi into one side of an air cylinder without a solenoid valve in the way. The air will vent when the pneumatic system is de-pressurized. |
Re: Al's Annual Inspection Thread 2015
So Q&A 312 refers to a cylinder plugged at both ends. You cannot vent it with the pressure release valve so that is not legal. The Q&A does not address directly plumbing the cylinder to the working pressure line.
Unless there is a rule stating cylinders must be plumbed through a control valve, I don't see how it could not be legal. (Q&A unless Q&A rules otherwise) The pressure regulator is self relieving by rule so over pressurizing the system is not an issue. Now if you where to add a couple of check valves & turned it into a air pump... But check valves are not allowed by rule. Nevermind. On the subject of bumpers. For this year only you can put lead-iron rods in your pool noodles? :yikes: |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
;) |
Re: Al's Annual Inspection Thread 2015
So everyone, I am in contact with HQ now over this question. Give me a day or so to straighten this out.
James, while there is no pneumatic rule that this violates what you will have is essentially a device that moves on it's own without being enabled by the FMS. Potentially that could be a violation of R8. |
Re: Al's Annual Inspection Thread 2015
Thanks Al!
Quote:
|
Re: Al's Annual Inspection Thread 2015
It's common practice on our robots to plumb pneumatic cylinders so they are pressurized when there is system pressure, and it's also common for there to be a way to have them be "actuated" mechanically, which will increase system pressure momentarily so that the regulator will have to vent it. The only difference he is proposing, is not having a solenoid valve in the system.
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
I have thought about this and I would suggest that it is no different from a typical air cylinder in most regards. It will not change state unless (a) the compressor kicks on and charges air, which only happens when enabled; or (b) the venting valve is opened, in which case ANY air cylinder could move. The only functional difference I can come up with is compared to 'one-way' solenoid valves, that default to a given state when disabled or de-powered, in which case the 'always connected' air cylinder is safer, because it doesn't change rapidly or without explicit input (venting air pressure or charging air pressure). |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
Quote:
|
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. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
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. |
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. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
There's a tiny ir reciever on our robot to control the leds. During matches do you think I will be allowed just to put electric tape over it.
|
Re: Al's Annual Inspection Thread 2015
Quote:
I would suggest aluminum foil instead. But... I would also suggest, and probably more strongly, finding another way to control the LEDs in question. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
Here's the result if I do think you're triggering something: I've got my choice of G21 (if during auto), G32 (if the coach sticks it in his pocket), R84 triggering T8 (potential), T21. Almost all of which are cardable (T21 being the unknown factor, but probably a yellow for egregious behavior). That's anything from a disable to a foul+yellow to an alliance red to a yellow. Not a fun combination, should a referee decide that those lights changed because your hand brushed your pocket. Please don't put the referees in that position. Cover it, or use something else. Use the remote stuff at demos. |
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
If the LEDs will work without the receiver, I'm willing to bet that you can get some help to hook them up to another coprocessor, or the roboRIO itself. If not, my suggestion is this: You could either fasten the remote into the robot (securely), but that runs the risk of breaking a few robot rules about wireless transmission and batteries, OR put the remote on the robot cart and one or more of its batteries into your pocket (or elsewhere on the cart--this part is ideal and depends on the type of battery in question). If that latter method doesn't disable the transmitter effectively, I don't know what will--and it removes the chance of the refs thinking that you're changing the lights and thus possibly violating a bunch of rules. |
Re: Al's Annual Inspection Thread 2015
Quote:
The other easy thing would be, if the lights change color during a match then the ref would take action. That's seems pretty open and shut to me. |
Quote:
|
1 Attachment(s)
|
Re: Al's Annual Inspection Thread 2015
Guys,
What I am worried about with an uncontrolled cylinder is the fact that most teams (perhaps all that use pneumatics) pressurize their robot in the pits or in queue prior to going on the field. As always, we are concerned for the safety of the teams and robots near your robot when in these areas. As I stated, on it's own there doesn't seem to be a violation of any rules. It will be inspected at any events you attend just like any other robot parts. Any regulator you use must be a relieving regulator which is intended to vent any excess pressure on the working side of the regulator. R71 “Working” air pressure on the ROBOT must be no greater than 60 psi and must be provided through one primary adjustable, relieving, pressure regulator. And if you ask "Have you seen any accidents or near misses with pneumatics in the pits or queue?". The answer is an emphatic "YES!!!" I do not sit on the GDC. I make inspection decisions based on an understanding of what the GDC intent is for a particular rule. I will have an answer soon on bumpers. Please keep this in mind. If you look at the field and the number and complexity of the field objects, this will be one of those years where timing between matches is going to be dominated by field reset. I expect that G10 & G11 will be fully in force at events as I stated above. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
There is no difference, it will still be inspected for pneumatic rules and safety.
|
Re: Al's Annual Inspection Thread 2015
Quote:
Thank you for looking into this, we appreciate the extra effort you put in to inform the CD community every year. |
Re: Al's Annual Inspection Thread 2015
Q&A got back to my question here.
Sounds like we'll be set to go, assuming all pneumatic system rules are met. |
Re: Al's Annual Inspection Thread 2015
Quote:
Now quick question, if you power down the LEDs do they remember their color? If not, I wouldn't recommend this method as you will burn battery while in line just for your lights. Also if the goal is just alliance colors, you can just hard wire the black(power) wire of the LEDs to the PDB and then wire the blue and red wires (grounds) to a switch and then the switch to PDB. So the lights would be red or blue based on the switch. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
Edit: THIS IS NOT TRUE. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
This would then be illegal. Thank you for the check Ether. |
Re: Al's Annual Inspection Thread 2015
Quote:
Viewed a different way - an IR remote has no functional value to any team at competition whereas a camera does. With a camera the risk of cheating is worth the added functionality that many teams gain, whereas the risk of cheating with an IR remote is not worth the ability to turn decorative LEDs on and off. To take your hyperbole-ridden example even further: wifi security is never 100% secure! We should make all of the robots drive around on tethered connections. Obviously this is totally impractical, at some point we must assume some risk because it is worth the reward. I can very clearly see why an IR remote would be disallowed and why cameras are allowed. |
Quote:
|
Re: Al's Annual Inspection Thread 2015
OK,
Here it is... I screwed up. As people have pointed out earlier in this thread, objects that fit within the 28" x 42" x 78" high size limitation are legally within the TRANSPORT CONFIGURATION even when the team intends to attach those parts to the robot on the field. Inspection will likely check your TRANSPORT CONFIGURATION as defined in T6 & R3, when checking that all of your robot (and additional mechanisms) is weighed. To remind everyone, bumpers are not BUMPERS and only 2015 rules apply. As such B&T and withholding are affected as well. I am very sorry for any additional ulceration this may have caused. |
Re: Al's Annual Inspection Thread 2015
As to IR devices on the robot, this seems to be the defining rule.
R52 No form of wireless communication shall be used to communicate to, from, or within the ROBOT, except those required per R46 and R51 (e.g. radio modems from previous FIRST competitions and Bluetooth devices are not permitted on the ROBOT during competition). |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
The rules are simple: NO wireless communication to the robot except via the field wireless (or by signal placards etc. outside of automode, should you choose to use that method--but I call it more trouble than it's worth). That being said, leaving the remote in the pits would--to me--do the trick, at least as far as on-field activity is concerned. Now the whole "wireless within the robot" part of the deal is another story. So let's see if we can get you running without the wireless, and save the wireless part of the cool factor for demos. |
Re: Al's Annual Inspection Thread 2015
Quote:
DriverStation::Alliance DriverStation::GetAlliance() Return the alliance that the driver station says it is on. http://first.wpi.edu/FRC/roborio/rel...72988 3ce9855 Positives: no dispute with inspectors, always tracks color correctly. |
1 Attachment(s)
This was my solution. I just soldered on some pwm connections. This way we can change the leds in the pit by attaching the ir putting on the robot changing the color then taking the ir receiver off. It takes about 11 seconds.
Attachment 18278 |
Re: Al's Annual Inspection Thread 2015
OK Round 2.
1. With the new control system there will be a need to see all of the components. Please don't hide the RoboRio, PDP and other modules. Inspectors need to see the breakers and the wires that attach to them. Field people need to see all indicators including the radio. 2. Speaking of the radio, if you want reliable operation, be sure to secure the power connector on the radio. A piece of tape works OK but a adhesive backed anchor for a wire tie works best. Either place the anchor on the radio or on your robot near the radio mounting point. If the power connector moves a lot during operation, noise is introduced to the radio power. 3. The radio works best when mounted in the clear on your robot. When you surround the radio with metal it tends to block the antennas inside the box and/or detune them to the point that your connection and bandwidth are affected. 4. The Ethernet connections to your radio should also be secure and mindful of the minimum bend radius of the cable you use. In most cases that is two inches minimum radius. When you bend the cable, bad things happen to bandwidth and the wires can be forced to migrate through their insulation. 5. All teams must connect the CAN buss from RoboRio to the PDP even if you do not use CAN or pneumatics. This connection will be used to log PDP voltage. (R61 & R62) 6. Don't forget the Robot Signal Light. At least one RSL must be mounted on the robot and visible when standing three feet in front of your robot. R54 |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
We usually don't follow wires for their entire length. It's important that we can tell the gauge of the wires, however, and ensure other rules are being met (for example, R42). So make sure we can see an inch or two of the wire on either end, that wire gauge marks are visible if we need to double check them (sometimes your eyes play tricks on you, and you need to read the markings to make sure it's legal).
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
If I can add my .02
We're aren't necessarily looking to make sure you wire your compenents correctly to make them work, that's your job, we need to see potential hazards, chafing points, etc... Also, when mounting the radio, the best orientation is horizontal, due to antennae "radiating" out in a "dome." If you are mounting sideways or vertical , the "dome" will be facing one way, decreasing reception. Sorry for the non technical terms, I"m a nuts and bolts guy. Al's the antennae guy. |
Re: Al's Annual Inspection Thread 2015
Quote:
We have never had a plug pop out or any kind of intermiitent failure |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
We have always mounted our radio verticaly and have never had a connection problem but we have also always mounted it up high and unobstructed away from motors and other electronics.
Also a strip of gaffers tape keeps the connecton snug. |
Re: Al's Annual Inspection Thread 2015
Quote:
<R55> F. Fasteners (including adhesives) may be used to attach the device to the OPERATOR CONSOLE or ROBOT or to secure cables to the device. |
Re: Al's Annual Inspection Thread 2015
Quote:
Glad to see this change but of course it comes AFTER we leave the era of using the old style motor controllers with loose PWMs (at least for most teams). |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Hot glue is used by some teams but I really frown on it for a variety of reasons.
1. Unless the parts are near the melting temperature, the bond fails. I see that as giving a false sense of security. Others will surely write that they have had no problems, i bet I can pull more than 50% of those connectors out without difficulty. 2. Hot glue tends to migrate places you don't want it. That make the radio unrepairable for a failed power connector. 3. It is "ugly", that's all I have to say. Others have stated what I would in response to seeing wires. However, we train our LRIs and RIs to see potential problems so that we can help you be more competitive. So while we are looking at for compliance, we are also seeing other issues. Help us help you. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
What is important, as Dana suggested, is that the radio is mounted clear of metal or other 5 Ghz RF-opaque objects, which on most robots, is typically higher up. It's also possible that noise introduced by being in extreme proximity to motors may be a factor, however, keeping clear of large, plate-like structures of metal would be my #1 priority. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
Just make sure you can show that the wire is the correct gauge! |
Re: Al's Annual Inspection Thread 2015
It's not an unusual issue, even for experienced teams.
I was inspecting the wiring from our CIM motors back to the speed controllers, and asked whether they had looked at the wiring table. Turns out they matched the wire off of the CIMs, rather than using the table. Fixing it is now on our punch list. |
Re: Al's Annual Inspection Thread 2015
Another pneumatic system question: does the steel NPT fitting, standard on the Viair compressors, need to be installed?
It is the compressor's fitting that typically comes with a plastic plug in it, seen here: ![]() |
Re: Al's Annual Inspection Thread 2015
Quote:
The pressure relief valve must be attached to the compressor with legal hard (non tube) fittings, so if you chose to install the NPT to plastic plug fitting, it must be past the pressure relief valve. Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
Why don't you want it? It doesn't add much weight, and it gives you an easy adaptation to a tee fitting for the relief valve. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
Re: Al's Annual Inspection Thread 2015
Quote:
Quote:
The steel coupler pushes a few fittings and a gauge to a spot that's less accessible (and makes the gauge less readable) so it is handy to not have it in place. The port in the compressor is 1/8NPT, so attaching normal hard-fittings and tees is the same as attaching to the steel part, it just fits into our robot a bit more easily. |
Re: Al's Annual Inspection Thread 2015
Quote:
How does it make sense that I would have to crimp 12 AWG wire to 14 AWG wire after the speed controller to be legal? How does that help? |
Re: Al's Annual Inspection Thread 2015
Quote:
R65 C might give you a little leeway with that idea though since you are using the existing threads. |
Re: Al's Annual Inspection Thread 2015
Quote:
R65-C is why I assume our actions are legal, but I just want to double-check with the in-field experts. |
Re: Al's Annual Inspection Thread 2015
Quote:
|
| All times are GMT -5. The time now is 15:27. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi