Following Cadence Design Systems’ acquisition of the Design & Engineering (D&E) business, the D&E Community Forum on the Nexus Community Center has been migrated in the Cadence Physical System Simulation Community. For more details and if you have any questions, please refer to the FAQ.

Stats

  • State Not Answered
  • Replies 9
  • Subscribers 1
  • Views 2
  • Members are here 0
More Content

How to create jprim in wheel template as in handling_tire.tpl?

jozef.bucha
Hello i am trying to make wheel templte similiar as handling tire. Everything works fine, also jprim I am able to make, but how is this done?
 
Created forces elements ti[lr]_wheel has attached jprim:
 
Object Name : ._handling_tire.til_wheelObject Type : ac_tire
Parent Type : Model
Location : (LOC_RELATIVE_TO({0, 0, 0}, ._handling_tire.ground.origo)) mm, mm, mm
Orientation : (ORI_RELATIVE_TO({0, 0, 0}, ._handling_tire.ground.origo)) deg
 
General Parameters:
property_file (mdids://acar_shared/tires.tbl/mdi_tire01.tir (._handling_tire.til_wheel.property_file_list[._handling_tire.til_wheel.property_file_index]))
property_file_list (mdids://acar_shared/tires.tbl/mdi_tire01.tir)
property_file_index (1)
contact_type (handling)
configuration (single)
outside_tire (no value)
jprim_id (0.0 (._handling_tire.jolper_sse_jprim.adams_id))
center_offset (0.0)
high_performance (0 ("no" == "yes" ? 1 : 0))
 
Input Parameters:
i_marker (._handling_tire.whl_wheel.tire_i)
j_fmarker (._handling_tire.ground.FMA_1)
ref_marker (._handling_tire.ground.til_tire_ref_1)
 
Output Parameters:
None
 
How can I do such thing? I believe answer is in command navigator, but i am not able to find needed command
 
Thanks
 
Jozef
Parents
  • 0
    I am pretty sure that this jprim_id variables from the different wheels are put into an array during assembly.
    So looking at the acf-file, it starts with registering the different tires
    control/routine=abgTire::con901,func=user(901,1017,99,105,1,2)
    control/routine=abgTire::con901,func=user(901,1025,100,106,1,4)
    control/routine=abgTire::con901,func=user(901,1035,110,116,1,6)
    control/routine=abgTire::con901,func=user(901,1043,111,117,1,8)
    output/nosep
    control/routine=abgVDM::EventInit, function=user(5,1,8,0,3,6,8,17)
    control/routine=abgVDM::EventRunAll, function=user(0)
     
    If we focus on the first tire, front left, it references ARRAY/1017. Looking at that we see that element 14 is the id of that jprim. This is how the information is passed to CONSUB.
    !Input array for A/Tire in A/Car and A/Chassis
    ! p1 : id of ARRAY holding tire states
    ! p2 : number of tire states
    ! p3 : Side flag (0=left, 1=right)
    ! p4 : id of STRING statement holding role
    ! p5 : id of STRING statement holding tire property file name.
    ! p6 : id of STRING statement holding simulation name
    ! p7 : id of STRING statement holding road property file name.
    ! p8 : id of STRING statement holding contact type (HANDLING/DURABILITY)
    ! p9 : Tire radius for suspension analysis when a rigid wheel is used. 
    ! p10: id DIFF for sss, ssc, mmm analyses.
    ! p11: ISWITCH (0=static tire, 1=dynamic tire), if < 0 default: 1=dynamic
    ! p12: id of ARRAY holding scaling and drift factors
    ! p13: id of ARRAY holding user parameters.
    ! p14: id of jprim to lock wheel rotation (for steady state analysis).
    ! p15: RigK
    ! p16: initial speed
    ! p17: id of ARRAY holding doe parameters if applied
    ! p18: id of wheel part
    ! p19: tire load approximation (negative value to turn off ghost force)
    ! p20: high performance switch (0=off, 1=on)
    ! p21: origo marker of the model
    ! p22: id of ARRAY holding fmu road variable ids
    !       adams_view_name='TR_Front_Tires.til_wheel.input_array'
    ARRAY/1017
    , IC
    , SIZE = 22
    , NUMBERS = 1016, 2, 0, 84, 85, 88, 86, 87, 326, 0, -1, 1018, 1019, 6, 0, 0, 0
    , 99, 0, 0, 836, 1021
     
     
     
     
Reply
  • 0
    I am pretty sure that this jprim_id variables from the different wheels are put into an array during assembly.
    So looking at the acf-file, it starts with registering the different tires
    control/routine=abgTire::con901,func=user(901,1017,99,105,1,2)
    control/routine=abgTire::con901,func=user(901,1025,100,106,1,4)
    control/routine=abgTire::con901,func=user(901,1035,110,116,1,6)
    control/routine=abgTire::con901,func=user(901,1043,111,117,1,8)
    output/nosep
    control/routine=abgVDM::EventInit, function=user(5,1,8,0,3,6,8,17)
    control/routine=abgVDM::EventRunAll, function=user(0)
     
    If we focus on the first tire, front left, it references ARRAY/1017. Looking at that we see that element 14 is the id of that jprim. This is how the information is passed to CONSUB.
    !Input array for A/Tire in A/Car and A/Chassis
    ! p1 : id of ARRAY holding tire states
    ! p2 : number of tire states
    ! p3 : Side flag (0=left, 1=right)
    ! p4 : id of STRING statement holding role
    ! p5 : id of STRING statement holding tire property file name.
    ! p6 : id of STRING statement holding simulation name
    ! p7 : id of STRING statement holding road property file name.
    ! p8 : id of STRING statement holding contact type (HANDLING/DURABILITY)
    ! p9 : Tire radius for suspension analysis when a rigid wheel is used. 
    ! p10: id DIFF for sss, ssc, mmm analyses.
    ! p11: ISWITCH (0=static tire, 1=dynamic tire), if < 0 default: 1=dynamic
    ! p12: id of ARRAY holding scaling and drift factors
    ! p13: id of ARRAY holding user parameters.
    ! p14: id of jprim to lock wheel rotation (for steady state analysis).
    ! p15: RigK
    ! p16: initial speed
    ! p17: id of ARRAY holding doe parameters if applied
    ! p18: id of wheel part
    ! p19: tire load approximation (negative value to turn off ghost force)
    ! p20: high performance switch (0=off, 1=on)
    ! p21: origo marker of the model
    ! p22: id of ARRAY holding fmu road variable ids
    !       adams_view_name='TR_Front_Tires.til_wheel.input_array'
    ARRAY/1017
    , IC
    , SIZE = 22
    , NUMBERS = 1016, 2, 0, 84, 85, 88, 86, 87, 326, 0, -1, 1018, 1019, 6, 0, 0, 0
    , 99, 0, 0, 836, 1021
     
     
     
     
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.