sethro5hc
Mechanical
- Sep 9, 2009
- 35
Hey guys,
As a quick background I'm designing a kayak rack for suv's. We're working to find the perfect material and to do so I need to know what all the rack will be put through. My question is what sort of G forces do trucks/suv's go through on a day to day basis? I don't mean the g's of starting, stopping, or crashing. But the vertical g-forces associated with hitting a pot hole, driving off a curb perhaps, or maybe even just driving right up to the river on an old dirt path with its bumps and things. Would would be the best way for me to find this out? I don't want to design a rack that's just fine and then snaps when somebody hits a pothole. Is there a fairly standard assumption for the largest G's they would see in day to day driving (again talking about potholes and curbs here, not crashes).
Should I just pick a pretty heavy truck and assume it runs off a 6" curb and use that or what? Any help is greatly appreciated here, I just don't want to make too large of an assumption and overdesign this thing, we're trying to cut costs on it as is.
As a quick background I'm designing a kayak rack for suv's. We're working to find the perfect material and to do so I need to know what all the rack will be put through. My question is what sort of G forces do trucks/suv's go through on a day to day basis? I don't mean the g's of starting, stopping, or crashing. But the vertical g-forces associated with hitting a pot hole, driving off a curb perhaps, or maybe even just driving right up to the river on an old dirt path with its bumps and things. Would would be the best way for me to find this out? I don't want to design a rack that's just fine and then snaps when somebody hits a pothole. Is there a fairly standard assumption for the largest G's they would see in day to day driving (again talking about potholes and curbs here, not crashes).
Should I just pick a pretty heavy truck and assume it runs off a 6" curb and use that or what? Any help is greatly appreciated here, I just don't want to make too large of an assumption and overdesign this thing, we're trying to cut costs on it as is.