Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Extra Discussion (http://www.chiefdelphi.com/forums/forumdisplay.php?f=68)
-   -   pic: Custom Chassis 2576 (http://www.chiefdelphi.com/forums/showthread.php?t=125333)

lucas.alvarez96 27-01-2014 16:31

pic: Custom Chassis 2576
 

cbale2000 27-01-2014 16:32

Re: pic: Custom Chassis 2576
 
What thickness is that polycarbonate?

josemagr 27-01-2014 16:34

Re: pic: Custom Chassis 2576
 
Quote:

Originally Posted by cbale2000 (Post 1333267)
What thickness is that polycarbonate?

6 millimeters = 0.236220472 inches

Damiaen_Florian 27-01-2014 17:00

Re: pic: Custom Chassis 2576
 
Was the only reason to switch the outer plates to polycarbonate because of the weight? Also let me say that the polycarbonate chassis aesthetically speaking is amazing as well

josemagr 27-01-2014 17:37

Re: pic: Custom Chassis 2576
 
Quote:

Originally Posted by Damiaen_Florian (Post 1333283)
Was the only reason to switch the outer plates to polycarbonate because of the weight? Also let me say that the polycarbonate chassis aesthetically speaking is amazing as well

We believe that the weight reduction was an attractive detail, so that made us switch the outer plates.

We wanted a square chasis because of the systems that we were prototyping and designing. If we use the AM14U by AndyMark, our team would need to have cut the plates and we didn't have the correct machines. Since 2010 Sabic Polymershapes Chile was one of our best sponsors and they are available to support us with materials and machining.

The polycarbonate is a special material, very strong and esthetically amazing. Because we had the oportunity to work with this material, we tried something new on the chassis, and the result was a strong and attractive chassis.

Boe 27-01-2014 17:41

Re: pic: Custom Chassis 2576
 
One step closer to having a transparent robot which is one of the cooler looks a robot can have

http://www.chiefdelphi.com/media/photos/37570
http://www.chiefdelphi.com/media/photos/36596
http://www.chiefdelphi.com/media/photos/34998
http://www.chiefdelphi.com/media/photos/32862

Gregor 27-01-2014 22:23

Re: pic: Custom Chassis 2576
 
It looks like this frame is in violation of R26.

Quote:

R26
BUMPERS must be supported by the structure/frame of the ROBOT (see Figure 4-10). To be considered supported, a minimum of ½ in. at each end of the BUMPER must be backed by the FRAME PERIMETER.
You're not supporting the edge of your bumper by at least 1/2".

TheMadCADer 27-01-2014 22:47

Re: pic: Custom Chassis 2576
 
Quote:

Originally Posted by Gregor (Post 1333462)
It looks like this frame is in violation of R26.



You're not supporting the edge of your bumper by at least 1/2".

The way I understand it, you could make every robot compliant with R26 by putting a string all the way around the Frame Perimeter.

The string is now your Frame Perimeter. There are no gaps at all in the frame perimeter, so you don't need to worry about the 8" gaps or 1/2" edge gaps, and the 1/4" gap doesn't come into play either. There is nothing about structural integrity in their definition of "supported".

Gregor 27-01-2014 22:57

Re: pic: Custom Chassis 2576
 
Quote:

Originally Posted by TheMadCADer (Post 1333475)
The way I understand it, you could make every robot compliant with R26 by putting a string all the way around the Frame Perimeter.There is nothing about structural integrity in their definition of "supported".

Would your grandmother, or a reasonably astute observer define a string as supporting your bumper? This rule exists for a very good reason.

Whippet 27-01-2014 22:59

Re: pic: Custom Chassis 2576
 
Quote:

Originally Posted by TheMadCADer (Post 1333475)
The way I understand it, you could make every robot compliant with R26 by putting a string all the way around the Frame Perimeter.

The string is now your Frame Perimeter. There are no gaps at all in the frame perimeter, so you don't need to worry about the 8" gaps or 1/2" edge gaps, and the 1/4" gap doesn't come into play either. There is nothing about structural integrity in their definition of "supported".

Quote:

Originally Posted by Rule R2
The ROBOT must have a FRAME PERIMETER, contained within the BUMPER ZONE, that is comprised of fixed, non-articulated structural elements of the ROBOT. Minor protrusions no greater than 1⁄4 in. such as bolt heads, fastener ends, and rivets are not considered part of the FRAME PERIMETER.

(Emphasis mine.)

I would't consider a string to be structural element. However, if they put something like churro tube on it at the corners, it would probably be rigid enough to be considered structural.

Woolly 27-01-2014 23:01

Re: pic: Custom Chassis 2576
 
Quote:

Originally Posted by Gregor (Post 1333480)
Would your grandmother, or a reasonably astute observer define a string as supporting your bumper? This rule exists for a very good reason.

So, how about a stand-off from the inner poly-carbonate plate to the outer poly-carbonate plate? One could even have the bumper mounts such that they hook over said standoff.

Gregor 27-01-2014 23:03

Re: pic: Custom Chassis 2576
 
Quote:

Originally Posted by Woolly (Post 1333487)
So, how about a stand-off from the inner poly-carbonate plate to the outer poly-carbonate plate? One could even have the bumper mounts such that they hook over said standoff.

Perfect.

TheMadCADer 27-01-2014 23:58

Re: pic: Custom Chassis 2576
 
Quote:

Originally Posted by Whippet (Post 1333482)
Quote:

The ROBOT must have a FRAME PERIMETER, contained within the BUMPER ZONE, that is comprised of fixed, non-articulated structural elements of the ROBOT. Minor protrusions no greater than 1⁄4 in. such as bolt heads, fastener ends, and rivets are not considered part of the FRAME PERIMETER.
I would't consider a string to be structural element. However, if they put something like churro tube on it at the corners, it would probably be rigid enough to be considered structural.

R2 apparently differs from the definition given in the glossary. The manual should probably be edited to provide a more consistent definition of the Frame Perimeter.

Quote:

FRAME PERIMETER: the polygon defined by the outer-most set of exterior vertices on the ROBOT (without
the BUMPERS attached) that are within the BUMPER ZONE. To determine the FRAME PERIMETER, wrap a
piece of string around the ROBOT at the level of the BUMPER ZONE - the string describes this polygon.
Also, I wouldn't put it past some students to find a way to use structural string (it can be done, see: suspension bridges). That'd really tie the robot together.

Quote:

Originally Posted by Gregor (Post 1333480)
Would your grandmother, or a reasonably astute observer define a string as supporting your bumper? This rule exists for a very good reason.

As far as this observer goes, it depends what part of the manual you quote for them. Glossary or R2? Because using the glossary to determine that the string is the Frame Perimeter, any observer can see that the string obeys the 3 stipulations of R26. If you look at R2, then you get a whole bunch of other questions. Just how thick of a string are we talking about here? Does the string provide structure to any part of the robot (since the determination of an item being structural in R2 is independent of supporting the bumpers. The string doesn't need to support your bumpers to be your Frame Perimeter).

The rule exists so you don't wreck your bumpers in a collision. However, there are many ways to wreck more than just your bumpers in a match. Why are bumpers special? This year, if a team's bumpers break they are disabled for the match (G20). If something like your drivetrain or scoring mechanism breaks during a match, you may not be disabled, but it's close to it.

It is absolutely possible to make bumpers that will withstand the collisions in a match without following these rules. Why not let teams try? I fully support maintaining a set of guidelines similar to the current rules, but I'd like to see people get a bit creative with more parts of their robot. One of my favorite things to see is a team with bumpers that provide structure for their robot, rather than the other way around, using the bumpers to offload some weight from the robot.

EricH 28-01-2014 00:13

Re: pic: Custom Chassis 2576
 
Quote:

Originally Posted by TheMadCADer (Post 1333530)
R2 apparently differs from the definition given in the glossary. The manual should probably be edited to provide a more consistent definition of the Frame Perimeter.

It doesn't. The string is a visual aid. If I wrap a string around the exterior vertices of the frame and stretch it tight, the string describes the frame perimeter. Not "is", "describes". A suitable comparison: You getting fitted for a suit--are you trying to say that because a tape measure is wrapped around your waistline, it is your waistline? Didn't think so.

Bear in mind, I've been dealing with bumper rules since '06. Some things are obvious to me because I've been dealing with 'em so long, but that particular definition/description has been in there since at least '08, if not '06. (I can't quite remember whether "bumper zone" or "frame perimeter" came into play first, or if they came in at the same time.) The key thing about the bumpers is that they serve 3 purposes: Protect the robot against impact with other robots/field elements, Identify the team by number, and Identify the alliance by color. If you've got a suggestion for the GDC that will result in looser bumper rules, while still fulfilling these three purposes, I suggest that you let them know. With all the restriction-easing going on, they might welcome the suggestion as one less place the inspectors have to inspect.

TheMadCADer 28-01-2014 00:39

Re: pic: Custom Chassis 2576
 
Quote:

Originally Posted by EricH (Post 1333536)
It doesn't. The string is a visual aid. If I wrap a string around the exterior vertices of the frame and stretch it tight, the string describes the frame perimeter. Not "is", "describes". A suitable comparison: You getting fitted for a suit--are you trying to say that because a tape measure is wrapped around your waistline, it is your waistline? Didn't think so.

Bear in mind, I've been dealing with bumper rules since '06. Some things are obvious to me because I've been dealing with 'em so long, but that particular definition/description has been in there since at least '08, if not '06. (I can't quite remember whether "bumper zone" or "frame perimeter" came into play first, or if they came in at the same time.) The key thing about the bumpers is that they serve 3 purposes: Protect the robot against impact with other robots/field elements, Identify the team by number, and Identify the alliance by color. If you've got a suggestion for the GDC that will result in looser bumper rules, while still fulfilling these three purposes, I suggest that you let them know. With all the restriction-easing going on, they might welcome the suggestion as one less place the inspectors have to inspect.

You've misunderstood what I'm talking about regarding the string. This string is a fixed part of the robot, not the visual aid. The string used to identify and measure the Frame Perimeter is different and irrelevant. By your suitable example this would be more of a belt for your pants than a measuring tape for the fitting of said pants.

I'd suggest removing the need for specific supports for the bumper (basically removing R26) by opting for a rule more similar to the safety of robot mechanisms, like G3.

Quote:

G3
ROBOTS whose operation or design is unsafe are not permitted.
Violation: FOUL & DISABLED. If the issue is due to design: Re-Inspection.
Or, modified for bumpers:

Quote:

G20
ROBOTS must be in compliance with Section 4.6: BUMPER Rules throughout the MATCH.
Violation: DISABLED. If the issue is due to design: Re-Inspection.
We're already doing the first half by disabling failed bumpers. All we need to do is implement the second half (teams need to prove the problem is solved to re-enter match play) if we want to allow more restriction-easing.


All times are GMT -5. The time now is 20:46.

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