Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Rules/Strategy (http://www.chiefdelphi.com/forums/forumdisplay.php?f=6)
-   -   <R08> Section M (http://www.chiefdelphi.com/forums/showthread.php?t=71766)

Craig Roys 10-01-2009 11:28

<R08> Section M
 
I know there is already a bumper thread out there, but I think this deserves a separate discussion.

<R08> Section M: The entire length of the BUMPER backing must be supported by the structure/frame of the ROBOT (i.e. the backing material must not be in “free space” between or beyond attachment points) (see Figure 8 – 3).

Many teams design their robots with the wheels being outside the frame using support posts to attach bumpers to (which is plenty strong), but according to this rule that would be illegal. I have asked the question in the forums and I'm waiting for an answer, but I'm not optimistic about the answer.

Am I missing something in the bumper rules or will we have to modify our chassis design?

Richard Wallace 10-01-2009 12:06

Re: <R08> Section M
 
Thanks for posting a question, Craig. Many teams (mine included) will be interested in the response.

I agree 3/4 x 5 inch plywood supported at two or more points per segment is plenty strong, and many teams used that approach in conjuction with cantilevered axles in previous years. <R08-M> appears to prohibit that approach this year, but hopefully the GDC will clarify that. My guess is that some kind of structure/frame, itself securely mounted in a fixed location w.r.t. the chassis at approximately mid-bumper height, will be required to contact the entire length of each segment of the BUMPER backing plywood.

What I'd like is for the GDC to provide some guidance for teams, and for robot inspectors, on what qualifies as structure/frame. Is a strip of 0.062" thick aluminum too flimsy to qualify? What about angle with a similar thickness? Or maybe 0.125" thickness is needed? What about other materials, such as plastic and wood -- can they qualify as structure/frame?

Tom Line 10-01-2009 20:13

Re: <R08> Section M
 
I'm a little stunned this fell off the front page. The sheer number of west-coast drive systems that this rule specifically invalidates is enormous.

Perhaps they haven't noticed, or perhaps they're all building crab drives. I guess we'll see.

Jon Stratis 10-01-2009 22:51

Re: <R08> Section M
 
I highly doubt that rule will be changed. As they said in the kickoff video, they are expecting a lot of high speed impacts this year. Because of that, I believe the GDC feels that the bumpers need to have plenty of support - support that won't risk cracking and breaking after a dozen matches.

Molten 10-01-2009 23:47

Re: <R08> Section M
 
This makes me glad to not be one of those west-coast teams.

Craig Roys 11-01-2009 14:06

Re: <R08> Section M
 
Quote:

Originally Posted by eagle33199 (Post 798226)
I highly doubt that rule will be changed. As they said in the kickoff video, they are expecting a lot of high speed impacts this year. Because of that, I believe the GDC feels that the bumpers need to have plenty of support - support that won't risk cracking and breaking after a dozen matches.

High speed in this game won't be more that 7 or 8 fps. You need traction to gain speed quickly. With 6 robots and trailers out there on a slippery surface, no one will be able to gain high speed for a collision. Collisions in the past 2 or 3 years were much higher. Also, it will take an awful lot of force to break 3/4" in plywood with padding in front - considering it will be hit with another padded bumper, I don't believe there is any way that a reasonbly supported bumper would break.

I am not anti-bumper here; in fact, I like being able to use bumpers. We've used bumpers every year since our rookie year in 2006; even when they were optional. They save a lot of robot wear-and-tear. What I do object to are bumper requirements that limit creativity with robot design due to the requirements. Take a look at the length of the bumper portion of the manual compared to other sections. In 2006 and 2007 the bumper requirements were two pool noodles covered by fabric, backed by 3/4" plywood securely attached to the robot. Last year they became a little more detailed due to the fact that everyone was required to use them. This year, they seem to have gone crazy with the bumper regulations.

Oh well, we'll deal with them whatever the rules are - some of the requirements just seem very unnecessary.

Daniel_LaFleur 11-01-2009 15:29

Re: <R08> Section M
 
Quote:

Originally Posted by Craig Roys (Post 798632)
High speed in this game won't be more that 7 or 8 fps. You need traction to gain speed quickly. With 6 robots and trailers out there on a slippery surface, no one will be able to gain high speed for a collision. Collisions in the past 2 or 3 years were much higher. Also, it will take an awful lot of force to break 3/4" in plywood with padding in front - considering it will be hit with another padded bumper, I don't believe there is any way that a reasonbly supported bumper would break.

I am not anti-bumper here; in fact, I like being able to use bumpers. We've used bumpers every year since our rookie year in 2006; even when they were optional. They save a lot of robot wear-and-tear. What I do object to are bumper requirements that limit creativity with robot design due to the requirements. Take a look at the length of the bumper portion of the manual compared to other sections. In 2006 and 2007 the bumper requirements were two pool noodles covered by fabric, backed by 3/4" plywood securely attached to the robot. Last year they became a little more detailed due to the fact that everyone was required to use them. This year, they seem to have gone crazy with the bumper regulations.

Oh well, we'll deal with them whatever the rules are - some of the requirements just seem very unnecessary.

During 'Rack and roll' our robot, with a maximum speed of 6.5 ft/sec broke our front bumper (38" long, only supported on the ends) 3 times. I'll grant you that we played a lot of defense (who doesn't up here in New England) but we never received any penalties for ramming / playing too aggressive defense.

Having an unsupported bumper this year will invite broken bumpers.

Cory 11-01-2009 15:40

Re: <R08> Section M
 
Quote:

Originally Posted by Daniel_LaFleur (Post 798683)
During 'Rack and roll' our robot, with a maximum speed of 6.5 ft/sec broke our front bumper (38" long, only supported on the ends) 3 times. I'll grant you that we played a lot of defense (who doesn't up here in New England) but we never received any penalties for ramming / playing too aggressive defense.

Having an unsupported bumper this year will invite broken bumpers.

There's a difference between a 38" long bumper segment only supported at the ends and a 38" long bumper segment supported every 12". The latter is never going to break if you're using high quality plywood.

The example I gave is what I believe Craig is referring to.

Daniel_LaFleur 11-01-2009 16:00

Re: <R08> Section M
 
Quote:

Originally Posted by Cory (Post 798690)
There's a difference between a 38" long bumper segment only supported at the ends and a 38" long bumper segment supported every 12". The latter is never going to break if you're using high quality plywood.

The example I gave is what I believe Craig is referring to.

I believe that the impacts will be faster than 6.5 ft/sec this year as well, considering the standard gears given.

And not everyone is going to use "high quality" plywood.

dlavery 11-01-2009 16:39

Re: <R08> Section M
 
Quote:

Originally Posted by Cory (Post 798690)
There's a difference between a 38" long bumper segment only supported at the ends and a 38" long bumper segment supported every 12". The latter is never going to break if you're using high quality plywood.

The example I gave is what I believe Craig is referring to.

I hate to "break" it to you, but that is not quite the case. During early testing, I was driving a robot with bumpers attached in exactly the manner you describe (rugged stiff fasteners, robust stanchions about every 12 inches, bumper proud of the robot frame by about three inches). In the very first drive-from-one-end-of-the-field-to-the-other-as-fast-as-you-can test, the bumper broke and splintered upon impact with another robot at the far end. Within just a few minutes, I did it again while pushing the robot around manually, just to see how fast I could push it against wheel slip.

/edit/I just ran a few numbers out of curiosity. In a "perfect collision" situation (two full weight 151 pound robots hitting head-on at 9 fps, with one of the robots skewed so it impacts the other "corner first") the impact forces get pretty impressive. As the robots collide, they compress the pool noodles down to 20% of their original thickness in about 0.009259 seconds. At a closure velocity of 18 fps, this is a peak change in velocity of 1944 ft/sec/sec, or a 60.75-G impact. Since I said the robot impacted "corner first" I will posit an impact area of 1.5 square inches. Assuming the pool noodles absorb about 18% of the impact energy during compression (not too bad for material of this type), that still means that the localized impact pressure is right around 10,000 pounds per square inch. I haven't looked at the bending moment of 3/4-inch plywood on 12-inch support centers yet. But I am now really not surprised by what happened to the bumpers. /edit/

There is a reason for that rule. Don't count on it changing.

-dave




.

Craig Roys 11-01-2009 18:17

Re: <R08> Section M
 
I'm not counting on the rule changing and we'll just go back to our previous chassis design - we just thought it might be nice to try something new (or at least new to us). That's not a real big deal. I am a little suspect of being able to break 3/4" plywood supported every 12". If you point the grain correctly and you use "plywood" (as opposed to OSB or something similar) it should be near impossible to splinter. 1/2" plywood is commonly used on roofs with 24" inch centers between trusses - again, if the grain is pointed correctly it is very strong. Keep in mind that roofs in MI need to hold a lot of snow at times. I don't know what your set up was and it's quite possible that I'm wrong - it wouldn't be the first time. I may have to set up and run some tests just to satisfy my curiosity and skepticism.

But that's not my main argument here. Every team knows (or at least learns quickly - sometimes the hard way) that you need to build a robot robustly to compete in a FIRST competition; especially in elimination rounds. If a robot is not robust enough you will spend your time fixing it as opposed to competing. If a team tries to cut corners to save weight or $$$, they do so at there own risk knowing that the robot needs to hold up to the rigors of competition. I think that the same should go for bumpers - if you choose not to follow the GDC's recommendations for installation you do so at your own risk knowing that you can't compete with broken bumpers.

But, like I said; life goes on - we'll just adjust our designs accordingly and move on.

eugenebrooks 11-01-2009 19:09

Re: <R08> Section M
 
The language of the bumper rules in the 2009 manual
has been clear from the start, although there is no specific
specific specification for the thickness of the support
for the bumper, only that it must be there.

Additionally, the manual has indicated that collisions are expected in
the game, Bill has advised us to put the velcro on the bottom
of the driver stations in his blog, and now Dave has posted his
60 G estimate for worst case collisions.

I guess the word to the wise is to design the
electronics and battery mounting carefully.

Eugene

dtengineering 16-01-2009 01:51

Re: <R08> Section M
 
Quote:

Originally Posted by dlavery (Post 798731)
During early testing, I was driving a robot with bumpers attached in exactly the manner you describe (rugged stiff fasteners, robust stanchions about every 12 inches, bumper proud of the robot frame by about three inches). In the very first drive-from-one-end-of-the-field-to-the-other-as-fast-as-you-can test, the bumper broke and splintered upon impact with another robot at the far end. Within just a few minutes, I did it again while pushing the robot around manually, just to see how fast I could push it against wheel slip.

-dave


.

And that is why NASA has NEVER let Dave drive Spirit or Opportunity! :ahh:

Nope... even better... "Well if you drive like THAT no WONDER your other car is on Mars."

Jason

Gdeaver 16-01-2009 08:02

Re: <R08> Section M
 
There are many grades and types of 3/4" plywood. From experience most plywood that teams buy at a typical home center is not the best for high impact and structural strength. A high grade Baltic or Finnish birch plywood would survive the impacts. How ever it is not normally locally available to all teams and is expensive. The average plywood teams use needs the reinforcement . I would agree with the GDC's assessment.

artdutra04 16-01-2009 10:58

Re: <R08> Section M
 
I decided to do some more math to see exactly how it would be possible to have robots carry out these super high speed colisions.

Using f=m•a and f=μ•fn, where fn = m•g on a level surface, solving into each other we get a=μ•g. Since gravity is 9.81 m/s2, and the given coefficient μ of static friction in the game manual is 0.06, we get a maximum robot acceleration this year of 0.5886 m/s2. It would take a robot ~4.66 seconds of maximum acceleration to reach 9ft/sec or ~2.74 m/s. During this time, the robots would each need ~6.39m to accelerate to this final velocity, or about 20ft. If their wheels were slipping the entire way, resolving for dynamic friction would give us about ~7.66m or ~25.1 ft covered while accelerating to top speed.

In order for this to happen, the two robots would have to be at opposite ends of the playing field, and simultaneously floor it and accelerate as fast as possible without wheel slip until then both hit each other head on. You know, kind of like what's going to happen in autonomous? ;-)

Matt C 16-01-2009 12:01

Re: <R08> Section M
 
Quote:

Originally Posted by artdutra04 (Post 802151)
In order for this to happen, the two robots would have to be at opposite ends of the playing field, and simultaneously floor it and accelerate as fast as possible without wheel slip until then both hit each other head on. You know, kind of like what's going to happen in autonomous? ;-)

Are you implying that with the way the robots are positioned at the beginning of a match, that autonomous is going to be like some . . Robot Demolition Derby?:ahh:

Richard Wallace 16-01-2009 12:18

Re: <R08> Section M
 
The 2003 game (Stack Attack) had four robots start the game by simulatenously charging up a ramp, trying to be first to hit a wall of bins and knock/plow as many as possible into their own scoring zones. The frequent result was high-speed collisions, mitigated (i.e., damped) in most cases by bins interposed between the colliding robots. Bumpers were not required back then so most robots didn't have them. Fortunately, many robots also lacked sufficiently powerful drivetrains to develop significant kinetic energy at the moment of impact; however, in a few cases the crashes were spectacular. :cool:

Lunacy will provide much more frequent crash opportunities. Bumpers designed to mitigate the effects of those crashes are not just a good idea, they are the law.

Jon Stratis 16-01-2009 12:32

Re: <R08> Section M
 
Quote:

Originally Posted by Matt C (Post 802174)
Are you implying that with the way the robots are positioned at the beginning of a match, that autonomous is going to be like some . . Robot Demolition Derby?:ahh:

yeah... it should be fun to watch! Everyone's autonomous mode is going to be "get away from the guy right behind me chucking balls into my trailer"... and on top of that, everyone starts out pointed straight at the center point!

johnr 19-01-2009 21:44

Re: <R08> Section M
 
So the gdc probably isn't going to come out with a minimum requirement for bumper backing. So i say leave it up to the teams to decide how to protect their robot,but have a test at inspection. Maybe a 120 pound weight with a six inch bumper on it. Pull it back(to a set distance) and let it fly. If your bot 's bumper survives your good to go. If not ,at least your in the pits.

Karthik 19-01-2009 21:48

Re: <R08> Section M
 
Quote:

Originally Posted by Richard (Post 797540)
What I'd like is for the GDC to provide some guidance for teams, and for robot inspectors, on what qualifies as structure/frame. Is a strip of 0.062" thick aluminum too flimsy to qualify? What about angle with a similar thickness? Or maybe 0.125" thickness is needed? What about other materials, such as plastic and wood -- can they qualify as structure/frame?

The following Q&A entry addresses some of your concerns, in regards to one specific example.

http://forums.usfirst.org/showthread.php?t=11349

Richard Wallace 19-01-2009 22:07

Re: <R08> Section M
 
Thanks, Karthik.

I am glad that the GDC addressed this issue with a specific example. To me, their response makes it clear that "structure/frame" is intended to mean "the strong part of your robot at bumper level"; i.e., the part that carries the load, not something you added in an attempt to satisfy <R08-M>.

eugenebrooks 19-01-2009 22:28

Re: <R08> Section M
 
Perhaps it is time to think inside the box.

Cantilever wheels pointed in from the frame, instead of out?

Eugene

BJT 19-01-2009 23:58

Re: <R08> Section M
 
So now we know that 1/8 inch flat aluminum isn't enough to support bumpers. It would seem difficult for the GDC to make that decision without knowing a few more things about the setup in question. How far does it span between other support, how wide is it?
We have been building a west coast style frame with 2 standoffs between each wheel leaving about 7 inches between each. I'm not sure what to do with it now. Is 3/16 plate between them enough to satisfy the rule?

eugenebrooks 20-01-2009 01:01

Re: <R08> Section M
 
One could ask the GDC how thick an aluminum plate needs to be,
mounted on standoffs shown, to satisfy the letter and intent of the
rules. Do that and carry a copy of the QandA to the inspectors at
the regional just in case.

One could also make the backing plate from stacked aluminum tubing,
stacked 4130 tubing that is available as small as 3/8 square, or laminated
carbon fiber panels. The tubing would certainly be considered structural,
and the carbon fiber would also be if it were laminated thick enough.

Eugene

dtengineering 20-01-2009 02:05

Re: <R08> Section M
 
Quote:

Originally Posted by dlavery (Post 798731)
/edit/I just ran a few numbers out of curiosity. In a "perfect collision" situation (two full weight 151 pound robots hitting head-on at 9 fps, with one of the robots skewed so it impacts the other "corner first") the impact forces get pretty impressive. As the robots collide, they compress the pool noodles down to 20% of their original thickness in about 0.009259 seconds. At a closure velocity of 18 fps, this is a peak change in velocity of 1944 ft/sec/sec, or a 60.75-G impact. Since I said the robot impacted "corner first" I will posit an impact area of 1.5 square inches. Assuming the pool noodles absorb about 18% of the impact energy during compression (not too bad for material of this type), that still means that the localized impact pressure is right around 10,000 pounds per square inch. I haven't looked at the bending moment of 3/4-inch plywood on 12-inch support centers yet. But I am now really not surprised by what happened to the bumpers. /edit/

There is a reason for that rule. Don't count on it changing.

-dave




.

Okay... seeing as how my other car is still on this planet, I'm a bit hesitant to question these numbers, but I was doing some calculations with our programmers this evening to figure out peak velocities and such and have to question the assumed closure velocity cited here.

We used the published value of static coefficient (.06) of friction to determine that a 150 lb (68kg) robot would have a normal force of 668n and a peak forward force of 40N. The mass of the robot, plus trailer, is 186lb, or 84kg, giving a peak accelleration of 0.47 m/s/s

Next we assumed that the effective length of the playing field was 15m. Although 54 feet works out to be 16.5m, or thereabouts, the length of the robot and trailer, as well as the driver station bumpers must be subtracted from the space available for picking up speed.

Assuming constant acelleration, of .47m/s/s over 15m, it should take a minimum of 8 seconds to cross the playing field from one end to the other, with a peak impact velocity of 3.76 m/s or... 12.3 feet per second.

Now this is the peak velocity of a robot hitting the end... but it is also the maximum impact velocity that any two robots could sustain. If each started out at one end of the playing field, they would meet in the middle, and would each only have reached 6.15 fps each, for a closing velocity of 12.3 fps, which is just 2/3 of the assumed 18 fps velocity impact. (Actually it would be lower than 12.3fps, as the effective length of the playing field would again be diminished by the length of the second robot/trailer combo unit.)

That isn't to say that some robots might not exceed the published coefficient of friction as the playing field wears, or that a 12 fps impact is something to be laughed off without concern... we'll be building a solid robot and strapping solid bumpers on it... we agree with the point of the post and if this were anything but FRC would probably just say "close enough, good enough" on the calculations, but the peak closure speed and resulting extreme G-forces didn't mesh with our calculations and we were wondering if we had somehow missed something.

Or, perhaps, if the 18fps impact velocity is based on actual testing of robots on regolith, then the published coefficients of friction don't provide an accurate estimation of robot performance. I know a few teams have posted suggesting that their experimental results for coefficients of friction are much higher than the published values.

Any suggestions?

Jason

<Edit> first assumption... that is not quite right. We assumed all of the weight of the trailer would be over the trailer wheels. Some of it will contribute to the normal force of the robot and thus improve traction and accelleration. Even assuming 100% of the trailer weight does so, however, peak accelleration is just .6 m/s/s and it takes 7 seconds to make the trip with a peak velocity of 14 fps. We're getting closer...

second assumption... we were assuming a straight line path from one end to the other... it may be possible to achieve a slightly higher peak velocity by taking a curved path along the playing surface... </edit>

<edit 2> third assumption in these calculations is that accelleration will take place on the regolith. Maybe, just maybe, if everything is right and teams are driving at least partly on the carpet, an 18 fps impact speed is a theoretically possible event </edit>

eugenebrooks 20-01-2009 02:49

Re: <R08> Section M
 
Use the measured figures for the coefficient of friction and you will be closer to reality with your estimates. Several teams have posted measured figures on CD, and their measurements are roughly twice the inline published values.

I would also like to say that a driver who accelerates all the way down the field and then crashes into the back wall, or into another robot near the back wall, is not engaging in an accident. A reasonable expectation is that drivers will be required to attempt to maintain control of their robots, and will be expected to plan their acceleration and braking so that they arrive at their destination without a high speed crash. I would at least hope that this will be the case, although I have not yet run across this expectation spelled out as I read the rules. I will have to read the rules a little more closely, I guess...

Eugene


Quote:

Originally Posted by dtengineering (Post 804244)
Okay... seeing as how my other car is still on this planet, I'm a bit hesitant to question these numbers, but I was doing some calculations with our programmers this evening to figure out peak velocities and such and have to question the assumed closure velocity cited here.

We used the published value of static coefficient (.06) of friction to determine that a 150 lb (68kg) robot would have a normal force of 668n and a peak forward force of 40N. The mass of the robot, plus trailer, is 186lb, or 84kg, giving a peak accelleration of 0.47 m/s/s

Next we assumed that the effective length of the playing field was 15m. Although 54 feet works out to be 16.5m, or thereabouts, the length of the robot and trailer, as well as the driver station bumpers must be subtracted from the space available for picking up speed.

Assuming constant acelleration, of .47m/s/s over 15m, it should take a minimum of 8 seconds to cross the playing field from one end to the other, with a peak impact velocity of 3.76 m/s or... 12.3 feet per second.

Now this is the peak velocity of a robot hitting the end... but it is also the maximum impact velocity that any two robots could sustain. If each started out at one end of the playing field, they would meet in the middle, and would each only have reached 6.15 fps each, for a closing velocity of 12.3 fps, which is just 2/3 of the assumed 18 fps velocity impact. (Actually it would be lower than 12.3fps, as the effective length of the playing field would again be diminished by the length of the second robot/trailer combo unit.)

That isn't to say that some robots might not exceed the published coefficient of friction as the playing field wears, or that a 12 fps impact is something to be laughed off without concern... we'll be building a solid robot and strapping solid bumpers on it... but the peak closure speed and resulting extreme G-forces didn't mesh with our calculations and we were wondering if we had somehow missed something.

Or, perhaps, if the 18fps impact velocity is based on actual testing of robots on regolith, then the published coefficients of friction don't provide an accurate estimation of robot performance. I know a few teams have posted suggesting that their experimental results for coefficients of friction are much higher than the published values.

Any suggestions?

Jason

<Edit> first assumption... that is not quite right. We assumed all of the weight of the trailer would be over the trailer wheels. Some of it will contribute to the normal force of the robot and thus improve traction and accelleration. Even assuming 100% of the trailer weight does so, however, peak accelleration is just .6 m/s/s and it takes 7 seconds to make the trip with a peak velocity of 14 fps. We're getting closer...

second assumption... we were assuming a straight line path from one end to the other... it may be possible to achieve a slightly higher peak velocity by taking a curved path along the playing surface... </edit>


dtengineering 20-01-2009 03:07

Re: <R08> Section M
 
I'm not counting on drivers being expected to do anything... in fact I would suggest that from the laissez-faire attitude of the head ref at kickoff to the repeated "build for impact" rules and recommendations that we should be ready for a full contact, full-bore, game.

Jason

Daniel_LaFleur 20-01-2009 09:43

Re: <R08> Section M
 
Quote:

Originally Posted by dtengineering (Post 804252)
I'm not counting on drivers being expected to do anything... in fact I would suggest that from the laissez-faire attitude of the head ref at kickoff to the repeated "build for impact" rules and recommendations that we should be ready for a full contact, full-bore, game.

Jason

I agree with Jason here. I fully expect very high speed collisions this year. FIRST seems to be taking off the gloves this year and actually encouraging vigorous robot to robot interaction. Build it to withstand this contact or play at your own peril.

And, Jason, I expect impacts that will be far higher than both you and Dave have calculated ;)

johnr 20-01-2009 10:12

Re: <R08> Section M
 
Where and when is this perfect collision going to happen. Everyone seems to agree that every robot should at least move forward at the beginning. So in auto five bots would have to be dead and one runs across the field and hits the one in the oppisite corner. Even then it would be a head on hit. That might cause the dead bot to jack knife or worse case to form an upside down v and snap trailer hitch. During regular play you would need another bot dead in a coner,sideways to fueling station,and all the other bots out of the way. This collision would be head-to-side, maybe causing bot to tip over that bar. Never mind ,this game is starting to sound like fun.:)

dlavery 20-01-2009 10:52

Re: <R08> Section M
 
Quote:

Originally Posted by dtengineering (Post 804244)
Okay... seeing as how my other car is still on this planet, I'm a bit hesitant to question these numbers, but I was doing some calculations with our programmers this evening to figure out peak velocities and such and have to question the assumed closure velocity cited here.

We used the published value of static coefficient (.06) of friction to determine that a 150 lb (68kg) robot would have a normal force of 668n and a peak forward force of 40N. The mass of the robot, plus trailer, is 186lb, or 84kg, giving a peak accelleration of 0.47 m/s/s...

Jason-

Some of my numbers are based on empirical observations rather than theoretical values. During early development, we used standard kit-bots with prototype trailers for concept testing. We were regularly able to make the robots accelerate from the end of the field to reach top speed (9-11 fps, depending on the gearing installed) well before reaching the mid-field line. I understand that these observations may not agree with the theoretical performance calculated with the given COF. But the observed results were consistent and repeatable. So I am going to go with those.

There is one mistake in my calculations. I forgot to add the mass of the trailer into the impact calculations. With the trailer included, the localized instantaneous impact pressure is in the range of 12,300 psi.

-dave



.

JVN 20-01-2009 12:28

Re: <R08> Section M
 
I hope the GDC leaves it in the hands of the inspectors to determine whether something is "structural". Through the magic of engineering we have a pretty strong box structure made from .090 aluminum with bent flanges and standoffs. I'm worried about meeting an inspector who says: "The Q&A says .125" plate isn't strong enough, so why should we allow your .090?"

Common sense?

-John

Jonathan Norris 20-01-2009 13:32

Re: <R08> Section M
 
Quote:

Originally Posted by JVN (Post 804391)
I hope the GDC leaves it in the hands of the inspectors to determine whether something is "structural". Through the magic of engineering we have a pretty strong box structure made from .090 aluminum with bent flanges and standoffs. I'm worried about meeting an inspector who says: "The Q&A says .125" plate isn't strong enough, so why should we allow your .090?"

Common sense?

-John

John, I am also a little frustrated/concerned about that Q&A answer, the GDC shouldn't be defining what parts of our robot's frame is structural and not. The outside of our frame is a 1/8" AL sheet supported buy three 2"X1" square supports and 4 standoffs on each side, and by my experience more then strong enough, but by the Q&A definition this could not be a solid enough structure to mount our bumpers. I find it absurd that they are defining how solid of a 'frame structure' we have to mount our bumpers to. Where I would be comfortable running our robot without bumpers in its current configuration, but by that definition it is not be strong enough to support bumpers???

MrForbes 20-01-2009 13:37

Re: <R08> Section M
 
Keep in mind the question that was asked...it was "We plan to place aluminum plate (say 1/8in in thickness) across standoffs along the length of the robot so to meet the intent of this rule."

It was not: "We are making our robot chassis of thin aluminum that extends along the bumper perimeter in all areas where the bumper will be attached".

In other words, the GDC was answering a question about adding something to the robot chassis to satisfy the rule, they were not answering a question about what the chassis needs to be made of.

I agree it might take some engineering knowledge on the part of the inspectors to figure this out. Hopefully they'll have some guidelines (and we'll get to see those guidelines).


All times are GMT -5. The time now is 15:31.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi