Importing Tire Model

Altair Forum User

I am having trouble importing only a tire model. I see how to access a full vehicle assembly through Assembly Wizard but I would like to know where those model are coming from and if I can use one of the individual models. Is this something that is possible?

 

Also I have tried making my own tire model by using the Grasub method but I do not know what to do once I have created the template with the script inside.

 

Any help would be very appreciated. Thank you.

Praful

Hi Emilio - In the same 'Model' menu where you access the Assembly Wizard, there is 'Set Wizard Paths' option. It will show a default locations for

• model wizard file  - This is the wizard file that contains the code to drive the Assembly Wizard.
• task wizard file- This is the wizard file that contains the code to drive the Task Wizard
• wizard library directory - This is the location from where the model & task wizard can access the needed system definition files 
• std_inc.mdl - This is the file that contains default entities when MV is launched. ( I strongly recommend not to change this)
• .reports - Location for .report file. What is this? I explain later below

Now, coming to your specific questions

 if I can use one of the individual models. - Yes. You can. by Importing the system definition individually using the Import tab in the Systems entity panel. Note that many of the systems take attachments, so you might have to resolve these attachments manually.

 

Also I have tried making my own tire model by using the Grasub method but I do not know what to do once I have created the template with the script inside

If you have saved the system definition, you can always import it whenever needed as explained above. 

You can also create your own wizard library and make modifications such as adding a new tire system definition.

I recommend that you copy the existing library files to a different location, add/change system definition as needed change model & task wizard as needed. Then change the path using the Set Wizard Path.

 

Regarding .reports

One can build a post processing template consisting of plots and animation and save as a .tpl file

This tpl can then be linked to the model using *Report statement.

When MV exports or runs the model, the *Report information is written to the .report file mentioned in the Set Wizard Path

Analysis > View Reports tool accesses this .report so that the report can then be loaded.

 

Hope this helps

 

Regards

Praful

Altair Forum User

I got help from here, thank you!