|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#31
|
||||
|
||||
|
Re: Team Update #18
Our minibot is not particularly fast but is getting better. During Week 1 at Alamo, it tripped the sensor every time. But at the next event it will be lighter and faster (a design which we built before we shipped but had no time to test due to weather-related delays). After some complaints on Thursday, the few teams with really light and fast minibots got the referees to manually judge the minibot race. It seemed fair to us, those light minibots are great machines.
I want to point out a common engineering practice. If my company had to build a minibot that triggered the sensor EVERY time in order to get PAID, we would build something with a 2:1 margin for error - something that would under nominal conditions exert 8N of force. And I think that minibots reversing direction too quickly may play a bigger role that we think. We may add a spring in the lever that depresses the switch in our newer design. |
|
#32
|
||||
|
||||
|
Re: Team Update #18
That's a great point. Our minibot just turns off when it hits the top. (And usually comes back down because of the impact with the plate -- meaning that the plate is providing the impulse to reverse the momentum). If some teams are actually reversing their wheel direction before the impact is finished, this could have a dramatic effect on the overall force (and the maximum force) with which they are hitting the plate.
|
|
#33
|
||||
|
||||
|
Re: Team Update #18
"Week 2 results indicated that this change was successful."
Hmmm. Like many others who have commented, our 1.2 sec. minibot smacked the target with a substantial impact in Week 2 (my calculations say in excess of 100 N), and yet did not result in a trigger light a couple of times. Clearly with all the antecdotal evidence there is still a phenomenon occuring which can miss an impact of adequate force. Any mechanical action has both a time and force component, and perhaps the rules should have specified both. Like any control system the field system has a controller with a finite scan rate, and any control system is capable of missing a signal if it is short enough. I am a little nervous about a statement that essentially says "we have determined the system is now perfect" if that means no provision will ever be made for correcting a result when it is clearly wrong. I'm grateful we are not playing again until Week 6 to give some time for this issue to get sorted out. Let's hope no Week 3 teams experience any problems which effect their results. |
|
#34
|
|||
|
|||
|
Re: Team Update #18
2 observations:
1.) Design the mini-bot so that it can't hit the bolt first. Honestly, I think the bolt pattern was the cause of most of the times it didn't trigger at Pittsburgh. We personally checked every single contact point on the towers before each day and they all triggered with minimal force. 2.) Make sure there is a delay between when you hit the top and when you start reversing the wheels. I think this is a necessary rule for the Championships. Mini bot races are very soon going to get too close to call and we need to perfect the tower designs and also for the teams to perfect their mini-bot designs so they do not hit the bolts and provide the necessary amount of force. I think thats the only path to reliable calls at the championships. |
|
#35
|
||||
|
||||
|
Re: Team Update #18
Forgive my tired brain, but is the bolt pattern in the field drawings?
|
|
#36
|
|||||
|
|||||
|
Re: Team Update #18
Quote:
Teams made their minibots to FIRST's rules. They should fix their (still) not fully functional system, or put measures in place to ensure that minibots conforming to their published rules actually get scored. Instead they just say "our system is perfect, so if you don't trigger it, even if you blast the darn plate off the top of the pole entirely, you still don't get the points". If the system is proven to have any flaws then FIRST ought to recognize that it is possible for mistakes to be made. Anyone seriously arguing whether a 2.5 lb minibot going 6-10 ft/s will impart 4 N of force or not is just being a FIRST apologist. This is simple physics and some efficiency losses due to friction, etc aren't going to change much. Perhaps we should take some video of our official competition towers being repeatedly triggered by our minibot to silence the doubters? |
|
#37
|
|||
|
|||
|
Re: Team Update #18
Quote:
Grrrr. |
|
#38
|
||||
|
||||
|
Re: Team Update #18
One obvious omission is that you did not account for the mass of the plate. The plate must be violently accelerated in the short amount of contact time it has with the minibot in order to move it enough to trip the sensor(s).
How much does a 12" diameter 0.25" thick polycarbonate plate weigh? My quick calculation says it's more than 4 Newtons (please check my math). So obviously 4 Newtons is not enough force to move the plate at all, let alone violently accelerate it. So where did the 2-4 Newton number in the manual come from? The specification of what exactly is required of the minibot in order to trip the sensors is inadequate to allow accurate analysis. What exactly is being sensed? Proximity? Rate of change? Dwell time? Some combination? Does anyone know? |
|
#39
|
|||
|
|||
|
Re: Team Update #18
I am not apologizing for FIRST, I am just advocating pragmatism from the teams. The bolt pattern was definitely not obvious and I don't remember seeing it anywhere in the official rules. They are in the official field drawings in sections 37, 38 and 69 of the Game Field Elements but I know most teams (including my own) don't check those.
Believe me I sympathize with any team who's bot successfully climbs the pole but doesn't get the points for it. I know that it must be immensely frustrating. I want to eliminate that from ever happening. Thats why I think that with a few small minibot modifications, this will become simply a non-issue and the tower results will match everyones expectations. I know there were cases where the minibots reached the top of the tower but it didn't trigger. I am just being honest and did not see any of those cases where it was completely obvious that the bolt was not hit and that it delivered enough force and still did not trigger. Quote:
|
|
#40
|
||||
|
||||
|
Re: Team Update #18
Quote:
What's annoying is that this means that the rules have changed, as you suggested. The de-facto rule now appears to be 4 newtons for 75 milliseconds. |
|
#41
|
||||
|
||||
|
Re: Team Update #18
Quote:
|
|
#42
|
|||||
|
|||||
|
Re: Team Update #18
my math agrees with yours. And I know the off switch on our minibot takes much less force than that to actuate.
Interesting.....the rules have been that the tower sensor must be triggered for it to count. Just because teams got away without triggering the first week or two, doesn't mean the rule doesn't apply. I wonder how many slow heavy minibots will win races now? |
|
#43
|
||||
|
||||
|
Re: Team Update #18
Assuming the minibot stays on the pole after impact, the trick is to make the cut-off switches either slow (not a quick flip) or require more than 4N of force to push. Either will increase contact time with the top plate. Squishy surgical tubing comes to mind.
Design is iterative, right? |
|
#44
|
|||
|
|||
|
Re: Team Update #18
Quote:
Most importantly, I want you to account for the drift in the motors due to momentum after the limit switch shuts down the motors at the top of the pole. Do you know, for a fact, the robot has enough speed/momentum to continue to carry itself upwards despite non-powered motors and gravity contributing to rapid deceleration? As pointed out in this thread, the non-powered motors might even stop the robot on a dime... (For the record, I think there should be enough force too, but I think is not good enough in engineering, and FIRST hasn't given me good enough reason not to trust them) |
|
#45
|
|||
|
|||
|
Re: Team Update #18
I don't know about the towers at other regionals, but at Florida, for our 3 lb/1.6 second minibot, the tower triggered every time. Granted we didn't get our minibot and deployment working until our last qualifier, so it only had 4 goes at it, but it triggered it four out of four times. And for the most part, the towers there were registering minibots, both slow and fast.
However, being on the drive team leaves me with little time to watch matches, so I am not sure if every other team had this success rate, feel free to correct me if you minibot experienced a false negative at Florida. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|