Thank you. For that i couldn't create something like your tiresize tool, in excel-format and with the diagram-preview-picture.
Hi, First of all thank you for your online tools! very useful indeed! Just want to report a bug on the inertia calculator, the result are always the same on the 3 values! View attachment 15760 Mass (Kg) of the car + Driver, except fuel: 1285 Length (mm) of the car: 4527 Width (mm) of the car : 1937 Height (mm) of the car: 1163 The result is: Mass=1285 // all mass except fuel Inertia=(2339.4, 2339.4, 2339.4) // all inertia except fuel
Thank you for reporting Bugs, it helps me a lot to try to make things better. I will take a look at the Inertia Calculation soon and report here when i have fixed it. EDIT Problem fixed. Was a stupid copy/paste mistake from me. Sorry for that. I hope that nobody has entered wrong calculated Values into his HDV file.
Hey redapg, I've been using your tools all the time for all the little tinkering i like to do. Excellent stuff and thanks for that. I do have a small question/request. As I'm not too well versed in the whole TGM thing do you know if your tire size changer works with the new CPM tires? I noticed the new tires have more nodes then what your tool can handle. Is that the only limitation? Or is there more to it then that. And then, obviously if possible, would you consider updating the tool whenever you get a chance? Either way again thanks for all your work. TK
Thank you Slamfunk3 for the supporting words. To be honest, i did not notice that tires with using the CPM do have more Nodes than 49. The last tires i was working with, did have 49 and used the CPM. So i didn't change something. But i will take a look at it and see if i can integrate it into the existing Script without getting crazy. Do you know a tire with more than 58 Nodes? That was the highest Number i could find yet. And BTW, you are not alone with beeing not well versed with the whole tire thing, i definately also count me in.
Hopefully it's not big a pain in the a**. Thanks for looking into it. TK Sent from my SAMSUNG-SM-G800A using Tapatalk
Unfortunately i ran into a "little" Problem. The FISI, that Lazza reported to use 63 Nodes at the Front and 65 at the rear Tires, gives me some headache. I hope i can describe the Problem in an understandable way. In my Script i use the Node where the Sidewall of the Tire meets the Tread, as border for the calculation of e.g the width. With the Tires, that i took as Pattern when i created the Script, it was always the scheme that the more Nodes a Tire had, the higher was the Number of the Node that i used as that border. And it was always the same, if e.g. a Tire had 49 Nodes, the Border-Node was the 13th. And with 45 Nodes, let's say it was the 12th. Now the FISI is different: The Front-Tire with 63 Nodes has the 18th Node as Border. The Rear-Tire with 65 Nodes has the 16th Node as Border. So i can not use my old Scheme anymore. The Problem is, that i don't see a way to get the information which Node the Border-Node is, from the TGM file, neither from somewhere else. Now i have to find a way to keep my Script working, though. Merry Christmas to all
Maybe if you use the third geometry value, starting with the centre node as a reference, and when the values get below a percentage of the centre value (maybe 40% or something) you can consider that the beginning of the sidewall... of course that does depend on tyres having a similar structure to each other. I haven't looked too closely at the geometry of different tyres, just the FISI ones now, so maybe that wouldn't work at all
Unfortunately won't that work. When i created the Script, the Tires have been more "round" and it was impossible to find an attribute, by using all available Values, that made it possible to use it as definate attribute for e.g. "the most outside Nodes of the Tread". Maybe i can add an option to give the User a possibility to change the Node that is taken as this one and really needed for the following Resizing-Calculations.
Don't nodes have XYZ coordinates so that you can detect which is the outermost one? Enviado desde mi GT-I9505 mediante Tapatalk
But the most outside Node of the whole Tire isn't the most outside one of the Tread in each case. Visit my Site and you will see how it works.
They have X and Y, but the tread ones aren't all in a nice straight line so it's not necessarily easy to work out which ones they are. The outermost ones (greatest X values) are halfway up the sidewall. The Z isn't actually a Z (no point; you're defining the tyre section, so you don't need 3D) so it instead defines the overall thickness of the tyre wall at that point. This thickness drops back markedly in the FISI tyres, and I think some others, but if that's not a universal thing then it's not much good either.
Outermost means highest x^2+y^2. I refer to distance to the origin. Edit: Probably using abs(X)+abs(Y) would perform the same but easier to program. Enviado desde mi GT-I9505 mediante Tapatalk
Here is a picture of what I mean. https://www.dropbox.com/s/t6tywod8meym5dx/20151225_105941_resized-1.png?dl=0 I just visited your site. Very nice presentation and useful tools. I also make my tools in excel for similar things. Should I take a look at something special. I am not a car modder. I just tweak some vehicles from time to time to fit them to our league necessities. So probably I will not use the tire resizing utility. But if I can help with something I'll be glad to. Enviado desde mi GT-I9505 mediante Tapatalk
