![]() |
Re: Al's Annual Inspection Thread
This sounds like a robot the Green shirts will love.
|
Re: Al's Annual Inspection Thread
We where initially going with the pressure loaded catapult in the disabled state. We have switched to disabled vents the cylinders. For us, the safety benefits out weighs the pressure on when disabled benefits. Obviously you don't have that choice with springs. Having a secondary locking system is a really good idea for those cases.
|
Re: Al's Annual Inspection Thread
Quote:
Quote:
Quote:
Quote:
Doesn't this also then exclude an amplifier for a [legal] pressure transducer? </rhetorical> What I'm really asking is "How do I get the GDC to clarify the distinction between the mechanical and the electrical aspects of pneumatics in section 4.10?", since it, with the exception of R76-B and R88-B, appears to focus on the mechanical side. -Karlis |
Re: Al's Annual Inspection Thread
Quote:
|
Re: Al's Annual Inspection Thread
Al, for some clarification: does a custom circuit have to be controlled by the cRio, if it's controlled at all?
That is, if we have an LED ring on our camera, and LED lights elsewhere for blinging-up purposes, can they just be powered by the PD board (which jives with the 2014 wiring diagram), or must they have some kind of active control? |
Re: Al's Annual Inspection Thread
Karlis,
The wording has remained relatively unchanged for many years re: power pathway and custom circuit. I spot checked the 2008 rules and the only difference there is reference to hardware that was used in that year. What you are asking (in my mind and Jon's as well I suspect) is that limit switches in series with pneumatic valves alter the power pathway between "elements of the robot control system". The intent has been, and will remain to be, to prevent any robot action after the FMS has issued a stop command other than that which results from the action of gravity on robot parts. Potentially, limit switches could be satisfied by this condition resulting in the moving of robot parts under pressure after a stop has been issued. As to the amp for the pressure transducer, it is the transducer that is pneumatic and the amp as Custom Circuit. They have to satisfy that part of the rules to which each is identified. Pat, There is no rule that states that a Custom Circuit has to be controlled by the cRio or send data to it unless that data is used for robot control. In the case of an LED Ring, it may be connected directly to the PD and turned on with the robot. If it is extremely bright and other participants complain that it is obstructing vision during most of the match, we can ask that it be wired to a control device and only illuminated during the period you really need it. We want you to play but not at the detriment of other participants. The same rule applies to power supplies that are part of a Custom Circuit, they may be powered when the robot is turned on directly from the PD. As always, they must meet all other electrical rules that apply. (breaker size, wire, insulation, etc.) |
Re: Al's Annual Inspection Thread
Quote:
|
Re: Al's Annual Inspection Thread
Pat and everyone,
Please, please, please, if an inspector tells you to do something and it sounds weird, ask for clarification to be sure. The rules allow you to ask for the LRI to make a decision if you suspect some decision is in error. Every LRI has my email, cell phone and other contact info. I try to be available during the event season for questions. Again, this decision may be different once an onsite inspector sees your robot, your implementation and the effect on other teams. I see teams every year, all the way to the Champs, that have to make a change because something was missed at previous events or decisions were made based on specific circumstances at that previous event. Illumination has been an issue many times in the past, including a specific complaint on a robot aiming system last year at Champs. Yes it was bright, but it was not blinding unless you were right on the robot looking into it. It was aimed at the sky. |
Re: Al's Annual Inspection Thread
Well to get back on track sort of...
Team Update posted yesterday: As we approach competition season, we wanted to remind Teams to prioritize safety when transporting their ROBOT on and off the FIELD, to include transporting the ROBOT in its lowest potential energy state and/or including lockouts to help mitigate unexpected release of stored energy. Inspectors will ensure ROBOTS comply with R8 and do not create unsafe conditions. If inspectors feel your ROBOT is unsafe to be transported while storing energy, they will work with you to add lockouts to help mitigate the unexpected release of stored energy. If you are unsure as to whether or not you need lockouts, it’s best to be on the safe side and assume you do. Per T12, the Team should be able to safely release stored energy and be able to demonstrate this during Inspection. If the ROBOT creates an unsafe condition for people to be around it, on-FIELD troubleshooting prior to the MATCH will be limited to that which can be achieved safely. I do not expect this to be a great issue for inspections or teams. The majority of teams have already designed their robot to be safe, release energy in a controlled way and transport in a zero or near zero state of stored energy. Many of you have experience watching matches from the stands or seeing robots in the pit, but only the drive team and coaches have that intimate knowledge of what it is like in a crowded queue waiting to get on the field with a programmer who is making last minute changes with a powered robot. Anyone who has been around for a while can relate something scary that has happened in the queue. While safety is a high priority, we inspectors also want everyone to have a great event. That means we want to help make the match fun for everyone and watch for things that could ruin a team's day. While we are looking at your robot, we are thinking about your alliance partners as well. Getting all teams inspected is our goal to insure that everyone has a full alliance in every match. So this post should be a request to teams to get inspected early and help us get everyone inspected. At the top of the list of items teams need to complete inspections is bumpers that meet the rules and the BOM. No BOM, no sticker. Please don't leave it in your hotel room, don't let the dog eat it, don't give it to your teacher who won't be there until later in the day, don't leave it on the workbench at your build space. Make several copies, put it on a couple of thumb drives and on your driver station computer. I only have to be able to read it and compare the list with what I see on your robot. You don't have to include the candy you bought for the pit crew but you do have to list the no cost items that are KOP or First Choice. There is a template on the FRC site, this is preferred. |
Re: Al's Annual Inspection Thread
Al, I know this is really a Q&A type question, but... Are voucher items considered KOP in terms of cost accounting?
Bimba Cylinders? Bane bot vouchers? So on. Does this leave open the barn door? |
Re: Al's Annual Inspection Thread
Quote:
Kit of Parts (KOP): the collection of items listed on any Kit of Parts Checklist, has been distributed via FIRSTŪ Choice, or obtained via a Product Donation Voucher (PDV) |
Re: Al's Annual Inspection Thread
Thanks. I should have looked there. I guess my confusion is anything that was available on first choice or KOP checklist can be used with $0 cost without regard to how it was actually purchased. A cash value PDV or the Bimba cylinder list would open up the entire website.
I guess the key word is obtained by the PDV as opposed listed or distributed for first choice or KOP checklist. Sort of q fine distinction. |
Re: Al's Annual Inspection Thread
Quote:
|
Re: Al's Annual Inspection Thread
Quote:
|
Re: Al's Annual Inspection Thread
Quote:
|
| All times are GMT -5. The time now is 10:57. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi