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?
I had a look on the issue now, and here are my findings:
(1) MSC 's usage of our CTI interface seems to be lacking a (necessary) call to ctiGetOperatingConditions(). This call however is included in good old STI interface. So my advice: use the STI interface for your pressure drop simulation, until the Adams glue code to CTI is fixed by MSC. To do so, set the respective environmental variable: MSC_ADAMS_USE_CTI=NO
(2) there is a small typo in FTire's docu chapter on operating condition specification. The line with (TIME_TABLE_INFLATION_PRESSURE_WHEEL_1) must start in column 1. So, this snippet of a tir-file will do the trick:
(3) as of our next release 2019-2 (to come in 3..4 weeks), there is a completely new and much more powerful mechanism of defining operating conditions and more, in terms of so-called cti-files. Stay tuned for more to come.
I had a look on the issue now, and here are my findings:
(1) MSC 's usage of our CTI interface seems to be lacking a (necessary) call to ctiGetOperatingConditions(). This call however is included in good old STI interface. So my advice: use the STI interface for your pressure drop simulation, until the Adams glue code to CTI is fixed by MSC. To do so, set the respective environmental variable: MSC_ADAMS_USE_CTI=NO
(2) there is a small typo in FTire's docu chapter on operating condition specification. The line with (TIME_TABLE_INFLATION_PRESSURE_WHEEL_1) must start in column 1. So, this snippet of a tir-file will do the trick:
(3) as of our next release 2019-2 (to come in 3..4 weeks), there is a completely new and much more powerful mechanism of defining operating conditions and more, in terms of so-called cti-files. Stay tuned for more to come.