I would like to know how to properly define dual wheels in acar. There is no problem when I create single wheels(left and right) and simulate them. The wheels remain stationary on the ground with the reaction force equal to the weight of the wheel. But whenever I create dual wheels either in a single template or by assembling single wheels from two individual templates and simulate them, the force on the wheels is shown as 1e6 N in the postprocessor and in the animation too, I can see the wheels flying off vertically upwards at tremendous speed. I am using PAC2002 tire property file for defining the wheels. In the simulation, I simply create a generic assembly using only the wheel subsystem that I created, There are no constraints (not even fixed joints between the two wheels) except the contact force with the ground that is created by default by acar (til and tir) ). Then I simply run a general actuation analysis for 2 seconds and 200 steps) and get the result as described earlier.
Can anybody give me any pointers as to what I might be doing wrong?
The sse_jprim is responsible for locking the tire rotation (finding static equillibrium) and later being deactivated in order to give the tire the required initial rotation. It's used by the related consubs called in the acf.
BTW: In the dark medieval times this was done by a static_lock rotational force in the suspension template.
I wonder that someone labeld as "MSC Software" has to ask this in a public forum insted of asking the developers.
My preferred method to create "own" templates is simple and leaves most of the maintenance and "you have to know" work to MSC:
Open the base template from the acar_shared (handling_tire in your case)
Use a command file / macro to modify the tire (things like deleting the original graphic, adding imbalance masses, force transducer or a second til_/tir_ tire UDE)
Save the modified template in your own database and use it
Now imgine someone doing this with the existing dual tire template from the truck database to get rid of the few things not being required.
The sse_jprim is responsible for locking the tire rotation (finding static equillibrium) and later being deactivated in order to give the tire the required initial rotation. It's used by the related consubs called in the acf.
BTW: In the dark medieval times this was done by a static_lock rotational force in the suspension template.
I wonder that someone labeld as "MSC Software" has to ask this in a public forum insted of asking the developers.
My preferred method to create "own" templates is simple and leaves most of the maintenance and "you have to know" work to MSC:
Open the base template from the acar_shared (handling_tire in your case)
Use a command file / macro to modify the tire (things like deleting the original graphic, adding imbalance masses, force transducer or a second til_/tir_ tire UDE)
Save the modified template in your own database and use it
Now imgine someone doing this with the existing dual tire template from the truck database to get rid of the few things not being required.