![]() ![]() ![]() That would show you both which dims related to what, and where the handlebar / seat / footpegs were. The idea would be that you take a picture of your bike (or whatever bike you are entering dims for) and put it in the background at a scale / position where the tires etc match up. What I plan to do to make things easier / more useful is allow the user to load / scale / move a background image. That way its still just a line with two endpoints and an angle I already know. I could maybe draw it as an extension of the rake line that has a length equal to head tube length, and is drawn fat enough to look like a head tube. As would all those other image items like ergonomics. The top of the head crown is really not relevant to my math, and dealing with lines that have more points than just the endpoints defined is a HUGE pain in the ass for such a (supposedly simple) project. I see your point re the measurement descriptions being confusing, though there should be some clarifications visible when you hover on the form. This doesn't really show stance change and potentially makes calculating trail difficult, but made some of the math (much) easier and is, I assume, how modifications like up / out / neck angle change are described / measured, hence my questions above.īy dimensions, do you mean inch vs cm vs mm? It really doesn't matter what units you use (though they obviously all need to be the same). Obviously I still have some work - it draws the bikes correctly, but they are figured out such that both effectively are treated as being in a stand with the rear axle locked in place (or equivalently, held by the engine / trans mount). Is this a common understanding & use of the term? I'm also assuming that when people talk about a change to neck angle (such as +3 degrees) this is a chage to the frame itself, basically cutting the frame and inserting 3 degree wedge (which would also result in some small amount of up / out) and does not necessarily mean that the final stance has 3 degrees more rake. I have a few questions about what people might want from such a package.įirst, are the changes it calculates useful? In theory I think those are enough that you can set up a build jig, but I'm not sure just what values a jig uses. Its mostly aimed at chopper type mods (uses terms that make sense in that context) but would work fine for anybody doing custom trees, wheel swaps, fork swaps, etc. The software would then diagram either or both setups (overlayed) so you can get an vague idea of stance, etc. I'm working on some (free) software to calculate the changes to various dimensions (rake, trail, wheelbase, neck height, axle-crown length) that would result from fork length change, tree rake, neck chop / up / out, and wheel size changes. ![]()
0 Comments
Leave a Reply. |