YeeP
Red Skull Member
yes sirDo you mean the link ends?
yes sirDo you mean the link ends?
Should be pretty easy. Side view max positive and negative deflection, relative to ride. And top view angle relative to axle tube. Top view shouldn't change, so just at ride. Should just be a little bit of trig. I'll add it to the to do list for v7.0.yes sir
The current version, v6 doesn't have articulation. V7, which is currently in development, will not either. It will show up in some manner in version 8. It may show up in a prototype form in V7.x depending on what sort of testing it needs, but probably not.I haven't used the calculator in years and when I did, the version I used didn't have the capability of articulating the axle in question to see the arc in which the links would travel as one side was fully compressed and the other side fully drooped.
I'm at a point designing a chassis on paper (I'm compooter illiterate so modeling is outside my wheelhouse) and I'm not sure if I need to narrow up the front frame rails to ensure the upper link mounts/captures at the axle end (XX 4 link) in the front clear the frame on articulation. The upper link mounts will clear the frame rails on both sides on full compression/bump with some amount of 'cushion' to allow for the link/capture/joint/bolt/hardware to still clear it during articulation should my chosen link geometry pull the tire and link inboard on compression. The question I need to answer is: how much 'cushion' do I need?
Any guidance is appreciated.
I very much appreciate the response and am even more appreciative of the work that's already gone into the calculator as it is. Thank you.The current version, v6 doesn't have articulation. V7, which is currently in development, will not either. It will show up in some manner in version 8. It may show up in a prototype form in V7.x depending on what sort of testing it needs, but probably not.
I currently don't have plans to release the full solver that I used to generate some plots for the 4 link bible. It is not written in free to use software, it takes a long time to run, and it would require lots of work to get to a state that is user friendly.
Unfortunately, I don't have anything on rules of thumb for how far in it goes.
Thanks for the feedback.A couple more observations over my second cup of coffee...
Traditionally, the layout of the 4-Link Calculator has always put the "Front" of the vehicle on the left side of the screen, and "Rear" on the right.
This felt natural as being the "drivers side" view of the truck that we were originally designing for. In this V7.0 screenshot it appears that the rear suspension and details are on the left and front suspension details are on the right.
This also makes some of the scales on the graphs seem a bit odd... for example: the center views showing the vehicle in a profile view start measuring the wheelbase at 0" (rear wheel) and the actual wheelbase number is shown at the front wheel (at the right of the graph). While the number is accurate, it doesn't feel like the way that people actually conceptualize wheelbase. We think of a measurement from the front wheel center to the rear wheel center, not the other way around.
It seems like a relatively simple fix, as the two center columns of data remain in place and only the outer two columns (REAR and FRONT) get swapped visually on your screen layout.
The consistency in use of color seems good. We had always tried to make sure that colors assigned made sense (lower links were always red, upper links were always blue, panhard was always yellow). For a lot of the other calculated lines (roll centers, IC, AS) we tried to keep them in the same color families (greens, light blues, oranges) depending on what the attribute was. You have a lot of new visualizations now, so it's probably worth looking at how the colors used in all of those peripheral graphs associate with the color of the originally plotted line. I know that after a while you just run out of colors to choose from, but if you are using light green for roll center consistently in the calculator... it can be distracting to see that same color for something unrelated (like a pinion angle change graph).
A few things to consider as you continue to refine the V7.0 and as mentioned before, it does look very slick. :)
-G
Thanks for the feedback.
Thanks for catching those spelling errors.
I'll take a look into the color scheme. It hadn't occurred to me to match plot and line colors. I never noticed that similar things were in the same color family. Thanks for the insight on the creation of the calculator.
Moving sections around is pretty straight forward. I don't mind doing so. But with how it's set up, positive X is going from the rear forward. It seems that is more intuitive than flipping everything around. But you've got me a bit confused. The earliest version I have been able to find only has the rear suspension and forward was to the right. When somebody on PBB added the front in v4.0, it was to the right, so I kept using that layout.
Thank you for the insight. I always wondered about how it came about.Hi Treefrog,
You are right! Looking back at some of the oldest versions of the calculator what you say is true. The development of the original 4-Link calculator started out when I was designing the rear suspension for my 1st Gen Blazer (Dan also owned a 1st Gen Blazer back then which is how we initially met - here is the event: BlazerFest 2001 in Hollister Hills, CA)
Dan Barcroft (aka Triaged) - Second from left in yellow 1st Gen
Greg Blanchette (aka Greg72) - Center in grey primer 1st Gen
Fun trivia for those that never knew much of the original story.... :) For the first few months of its development the link calculator barely even had any graphical interface. It was literally just a page of numbers and calculations.
Makes sense.Here a screenshot of the very first 4-Link Calculator built on September 4th, 2003.
In retrospect, it was just a matter of convenience at the time. We put the axle at 0" on the X-axis and then just started doing the geometry off that point using positive numeric values which caused all the links to be calculated and drawn over on the right-hand side. At the time, this was all just a "quick and dirty" exercise to speed up the process of figuring out a rear link suspension.
Funny how things can snowball.Neither of us had any way of predicting what would happen to this little Excel worksheet over the next few months, years and decades....
I'm still a bit worried about it all being readable. I've been working on larger screens and will have to check it on a smaller ones.When the 3-Link Calculator came out several months later, I used that one for my front suspension design, and it made a lot more sense visually as it was pointing the "correct" way (driver's side view) and since the rear suspension for my truck had already been finalized, it was easy to lose track of the fact that the 4-Link calculator was actually drawing everything backwards for most people.
As years went by, it always felt like it would have been great to combine both the front and rear suspension designs onto a single graphical worksheet, but the screen resolutions available at the time never allowed it to work in a practical way. You could either get the graphical image, or the input cells and the calculations.. but never both. It was just too small and hard to read... and jumping between worksheet tabs to view the rendering vs data would have been miserable to work with.
The nice thing is that it is just a matter of flipping the graphics. Flipping the signs inputs will take a bit longer, but that can be done if front left is better. I'll make a test screen and post it for comparison.So, perhaps maybe it's not a simple matter of flipping the graphic around or relabeling a few cell values.... apologies for that. Ultimately, it feels like it would be a nicer looking layout if it were done that way but I'm not the one doing the work anymore. It's just some feedback to use at your own discretion.
-G
Thank you for the insight. I always wondered about how it came about.
Makes sense.
Funny how things can snowball.
I'm still a bit worried about it all being readable. I've been working on larger screens and will have to check it on a smaller ones.
The nice thing is that it is just a matter of flipping the graphics. Flipping the signs inputs will take a bit longer, but that can be done if front left is better. I'll make a test screen and post it for comparison.
One reason I am hesitant to switch it besides it being different from the previous versions is that positive X being forward and positive z being up make sense from a driver standpoint and play well from a math standpoint. The math is easy to handle with an intermediate step, which is already done for the front.
Thanks for the feedback, I really appreciate it.
If you don't mind me asking, were there any features that you and Dan wanted to add back then? And would you be willing to share any of the early versions if you still have them? The earliest I have been able to find is 2.1
So, V7.0 is no longer in Excel. I am writing it in Python. That's why I am able to do stuff like completely rearrange the page quickly. I am aiming to have it be a standalone version that requires no other software. I think a smaller screen will be fine, its more limited on aspect ratio. But most things are 16:9. Being in Python makes simple view very doable, but I am not sure I want to. More on that below.Hi Treefrog,
Yeah, the internet stil felt pretty "new" back then and it was exciting connecting with people who shared a common hobby. This was back in the early days with Jason Payne (willyswanter) setting up online clubs for the So Cal Big Dawgs (where Dan lived) and the NorCal Big Dawgs in the Bay Area where I lived. The BlazerBash event may have first started in 2000... but I didn't have a my truck until 2001 so that was the first event that I attended. All the SoCal guys made that long drive all the way up to Hollister Hills to meet up with the guys who they'd only ever spoken to in online message forums... but it ended up being totally natural and awesome having everyone together. I kept in touch with Dan after that event and would bounce ideas off him. The catalyst for the 4-Link Calculator was an article by Fred Williams (4W&OR, July 2003)... where a lot of the "rules of thumb" were described.... (a couple of pages for historical context are inserted below)
It was really fascinating to read about the proportions of the upper links to the lower links, and all the ways you could figure out so much with a tape measure and a few formulas. So I basically dissected that article and put all of the math into a spreadsheet and sent it to Dan asking him what he thought. His response was something like: "Yeah, this is pretty good but you know.... there is a much better way to figure out some of this stuff". He was maybe in his sophomore year at CalPoly in this time period, but he was studying mechanical engineering so he had all sorts of cool formulas and ways to figure things out. He sent me some better formulas and suggestions and I kept messing around with it... but it wasn't until I sent him the .XLS with the side profile image of the tire, links and extrapolated lines showing AS and IC value traces that he got really excited and saw the potential of what our conversations could become. The rest, as they say, is history... :)
The idea of being able to cram a lot of data on a single page is really nice for guys with the large monitors and 4K displays... but you're right to consider that not everyone is going to be set up like that. Perhaps a simple option is to build out a few different "views" in the Excel worksheet tabs? They could be labelled as "MAX VIEW", "TYP. VIEW" and "CLASSIC VIEW" The max view would assume the user has lots of viewing space and would be laid-out with every possible graph available on a single sheet. The Typical View might have to remove some of the more esoteric items to allow for the most criical graphics to remain.. and a classic view could literally just be more of an OG-style layout with the link views and only the most critical of calculated values (AS%, Roll Center, IC, Link Lengths, etc) If you offer a few options in different tabs they really all just reference the same data so it's no extra effort in terms of the math... just filtered views of what has already been figured out.
I was thinking more along the lines of new pages. Like the driveshaft one that was a work in progress. I completely agree about not over complicating it. Using your shock example, it is on another page, so the user doesn't see it or use it unless they want to.The hardest question is "what to add next"? This ultimately is the one I'd struggle with the most. At the outset, my whole motivation for the 4-Link Calculator was to create something approachable and simple. I wasn't going to learn SolidWorks just to build a suspension model... and even that wouldn't help me understand whether it was a "good" design or a "bad" one. I think the biggest reason that people liked this calculator is because you only needed to fill in a few pieces of data in those light blue cells ("mess with these cells" as Dan liked to describe it) and you could generate a simple model showing link position, tire size and after that you could change a single value for a link position and watch all of the important attributes change... personally, being able to experiment and see which values could reduce an insanely high AS% value was the exact kind of insight that I needed to start wrapping my brain around general link suspension theory.
Obviously, as the user gets more comfortable and sophisticated, there are other attributes that they'd probably like to consider as well... but if you force the user to add dozens of required values before getting any kind of a useful model, it ruins a lot of the appeal. Especially difficult is when, as a new user, you don't even understand the interrelationships between those attributes so making guesses at values can really give you an end-result that is pretty inaccurate or useless.
Perhaps the best option is some sort of "greyed out" options that can be activated with checkboxes? Initially, the program opens up with very simple link design model, but once that is comfortably established the user can enable the spring/shock options checkbox and start filling in the relevant data there? It seems like giving a brand new user access to hundreds of options right away is a bit of a disservice and is just intimidating. Letting them ease into the program a little at a time and only make a few decisions at a time... build some confidence and understanding of the relationships between all of those link positions, angles and lengths. Then let them enable a few more features and play with some new features, and learn some more.
It would be a cool feature, and would be pretty easy to add. Or even just having a gradient on the AS plot that gets redder the high it gets. I am hesitant with that for the exact reason you said, who or what decides what is good.The most lofty goal might be some kind of feature that would examine actual designs and could highlight poor choices by changing cell shading from black (or white, depending on the background color of the worksheet) to yellow or red as the particular attribute moved further from an "ideal" or at least "acceptable" parameter....simplest example: A suspension design where the user has created a vehicle with 100% AS... but starts moving link positions and is cranking up the AS% to 200% or more.... if the program could use some simple conditional formatting for the AS% cell, it could slowly change that color from light yellow to brighter yellow to orange to red... indicating that the value probably isn't in an acceptable range anymore. The biggest problem is of course, who decides what a "good" value is... and if it is not declared anywhere in the program, the user may not even trust the feedback the are getting.
That is a good label to put on that button... Maybe I'll have a new project before starting IFS and 3d viewing.Of course, logically.... that's only a small step away from just having a button called "Optimize" and letting the program go through iteratively and try to make changes to remove any unusual values so that the entire design has been cleared of obvious design mistakes. Let the user set the optimization criteria used, or the specific items that are allowed to be changed.. certain other values could be "locked" to force the optimization to work around those non-negotiable design choices.
You too. Thank you so much for taking the time to respond. It is greatly appreciated.More than I was expecting to write when I first sat down here... but maybe some of that is interesting, or gets the discussion moving or just triggers a few new thoughts of your own.
Enjoy your weekend, thanks for listening.
-G
so missed that it is moving from excel? to what then.I'm excited to see this moving away from Excel since I am not willing to pay Microsoft's subscription price for office. Looking good as always Treefrog
The new one is written in Python. But I plan to release it as a standalone application.so missed that it is moving from excel? to what then.
It is a programming language. The only thing you should have to download is the calculator.so is plython something i down load on PC?