I am trying to run a tire blow out simulation. I made some research and it seems the easiest way to use Ftire with inflation pressure around 0 bars.
I got an ftire data with pressures with the tire tests were performed at 8.5 and 10 bars.
I would like to get your opinions about making the analyses with the extrapolation form 8.5 to 10 bars to 0 bars inflation pressures would be realistic or not.
During my research I couldn't find any study with Adams in tire blow out analyses, have you seen any study on tire blow out analyses in Adams? Is there any easier way?
My guess of what Yahya.oz means is that for non advanced users this is not straight forward. I wonder if you guys could show a few screenshots of how to do it for anyone else to learn.
thanks for your advice. Screenshots about how to use Pac2002 for blow out simulations can only be provided by MSC support. Why not pointing out the limitations of Magic Formula at the same time then.
Simply scaling the Pacejka parameters during analysis is physically as realistic as Trump getting an Noble Price for communication skills.
Furthermore it involves a lot of additional elements and file hacking that is more complicated than changing a simple .tir-file and setting one environment variable.
I'd still recommend using FTire.
If you want it "easy", than get back to the GCON approach and simply uncouple the tire from the vehicle. If you want to "continue rolling on the rim", then you could use the new contact UDE's available in A/Car and set up a geometry contacting with the road after the original tire came loose. That'd be as (un)realistic as scaling the Pacejka parameters.
It is nearly impossible to add scaling Pacejka parameters from template builder, I tried with the help of KB8016467 but I couldn't, may be Trump can.
I gave a chance to MSC_ADAMS_USE_CTI=NO and it is working. It would be good if someone from MSC can guide me what kind of bugs I might face due to not using CTI for Ftire
provided your road is *not* attached to a moving (more precise: an *accelerated*) body (in which case the STI interface for mass-equipped tire models is simply wrong), you can use the STI interface w/o major disadvantages. Cosin's CTI interface, provided it is called correctly and completely, internally is the more versatile and modern kind of interfacing, but the end user will not see this directly in most standard situations.
yes, beginning with cosin version 2022-4, FTire no longer waits for Adams to evaluate time-varying operating conditions as specified in data block [OPERATING_CONDITIONS] in a CTI environment. CTI does this job now internally, and you can specify/use operating conditions in the same way as within STI.
By the way, there is another even more versatile way to control all features of CTI and FTire, including tools for post-processing, by means of so-called cti files rather than tir files.