• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Adams Car
  3. Can someone suggest me the easiest way or the flow chart...

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 Verified Answer
  • Replies 30
  • Subscribers 1
  • Views 8
  • Members are here 0
More Content

Can someone suggest me the easiest way or the flow chart of converting a demo vehicle into an All Wheel Drive vehicle?

rohan.tiwari
rohan.tiwari over 7 years ago
Can someone suggest me the easiest way or the flow chart of converting a demo vehicle into an All Wheel Drive vehicle?
  • Sign in to reply
  • Cancel
  • rohan.tiwari
    0 rohan.tiwari over 7 years ago
    Car
    Error1
    Hello Derbas, The older task was getting little complicated, So I have started with the simple task by making the demo vehicle into a front wheel drive because it uses the same template for the suspensions subsystem. And I was able to connect all the connections. But now the problem is rear tire and rear suspension both are colliding with the front tire and suspension. I hope you can help me with this.
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • m.derbas
    0 m.derbas over 7 years ago
    ​They aren't really colliding, from the Looks of it they are completely overlapping from the beginning ?
     
    In Standard Mode, open the following Subsystems:
     
    YOUR: Front and rear tires and suspension
    Shared: Front and rear tires and Suspension
     
     
    Under adjust, hardpoints, table you will find the coordinates of all the hardpoints
     
    Copy from the shared subystems into your Subsystems and click apply, the components should be then positioned correctly
     
    P.S: If an error occurs, make sure that the copying process didn't add spaces after every value on the last column (Z Values). If so then delete them and press apply again !
     
    Best of luck !
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • rohan.tiwari
    0 rohan.tiwari over 7 years ago
    Hello, thank you for your reply.
    that worked perfectly, but i don't know why it is not simulating,
    i am getting this error-
     
     
    FUNCTION : VAR1251
    PROBLEMS GETTING TIRE PARAMETER
    VARIABLE ID : 7
    TIRE ID : 1
    ** STOPPING ADAMS SOLVER **
    Static Solution converged in 7 iterations
    Residual imbalance is less than 6.10733E-08
     
    End Static Solution
     
    Simulate status=0
     
    command: DEACTIVATE/JPRIM,ID=2
    Deactivated model.testrig.josinl_body_stake, force/torque values will be zero in function-expression references.
    command: DEACTIVATE/JPRIM,ID=3
    Deactivated model.testrig.josper_yaw_stake, force/torque values will be zero in function-expression references.
    command: DEACTIVATE/JPRIM,ID=5
    Deactivated model.test_five_FT.jolper_sse_jprim, force/torque values will be zero in function-expression references.
    command: DEACTIVATE/JPRIM,ID=6
    Deactivated model.test_five_FT.jorper_sse_jprim, force/torque values will be zero in function-expression references.
    command: DEACTIVATE/JPRIM,ID=7
    Deactivated model.five_six_RT.jolper_sse_jprim, force/torque values will be zero in function-expression references.
    command: DEACTIVATE/JPRIM,ID=8
    Deactivated model.five_six_RT.jorper_sse_jprim, force/torque values will be zero in function-expression references.
     
     
    fdm::ActVar
    Setting function on: driver_demand::clutch
    command: VARIABLE/96, FUNCTION=0.0
    command: ACTIVATE/JPRIM,ID=2
    command: ACTIVATE/SFORCE,ID=1
    command: ACTIVATE/JPRIM,ID=5
    command: ACTIVATE/JPRIM,ID=6
    command: ACTIVATE/JPRIM,ID=7
    command: ACTIVATE/JPRIM,ID=8
    command: DEACTIVATE/MOTION,ID=4
    Deactivated model.testrig.jms_steering_wheel_angle.motion, force/torque values will be zero in function-expression references.
     
    acar/vdm_gra_mod
     
    Setting gravity vector in g's to: 0.00000E+00 0.00000E+00 -1.00000E+00
    command: accgrav/igrav= 0.00000E+00,jgrav= 0.00000E+00,kgrav=-9.80665E+03
     
    Apply a two steps statics:
     
     
    Begin Static Solution
     
    *********************************************** >> A/Car-MS Error>> AMS_GET_TIREDATA : wrong input parameters *********************************************** MODULE A/Car-MS ERROR MESSAGE
    FUNCTION : VAR1251
    PROBLEMS GETTING TIRE PARAMETER
    VARIABLE ID : 6
    TIRE ID : 1
    ** STOPPING ADAMS SOLVER **
    *********************************************** >> A/Car-MS Error>> AMS_GET_TIREDATA : wrong input parameters *********************************************** MODULE A/Car-MS ERROR MESSAGE
    FUNCTION : VAR1251
    PROBLEMS GETTING TIRE PARAMETER
    VARIABLE ID : 7
    TIRE ID : 1
    ** STOPPING ADAMS SOLVER **
     
     
    ---- START: ERROR ----
    VARSUB(281, 1004, 811, 517, 517, 1) has been illegally defined. A new functional dependency on the measure
    DIF(-1) has been encountered during execution.
     
    ---- END: ERROR ----
     
     
    ---- START: ERROR ----
    Error call SYSFNC for DIFF in flt_whlvel.f
    ID = -1
     
     
    ---- END: ERROR ----
     
    Adams Solver (C++) run terminating due to STOP requested by user.
     
    Static Solution failed to converge
     
    End Static Solution
     
    Simulation failed
     
     
     
    ---- START: ERROR ----
    Sim/stat cannot be achieved ...Stopping in <apre_ssssta>
    ID = 1020
     
     
    ---- END: ERROR ----
     
     
    ---- START: ERROR ----
     
    Adams Solver (C++) run terminating due to STOP requested by user.
     
     
    ---- END: ERROR ----
     
    Termination status=-995
     
     
     
    ---- START: ERROR ----
    VARSUB(282, 1004, 800, 496, 496, 1) has been illegally defined. A new functional dependency on the measure
    DIF(-1) has been encountered during execution.
     
    ---- END: ERROR ----
     
     
    ---- START: ERROR ----
    Error call SYSFNC for DIFF in flt_whlvel.f
    ID = -1
     
     
    ---- END: ERROR ----
     
     
    ---- START: ERROR ----
    Unknown exception caught in SYSFNC
     
    ---- END: ERROR ----
     
     
    fdm::ActPoiTor
    Failed to get actuator force: rear_brake_torque::single_component_force
     
     
    ---- START: ERROR ----
    VARSUB(281, 1004, 811, 517, 517, 1) has been illegally defined. A new functional dependency on the measure
    DIF(-1) has been encountered during execution.
     
    ---- END: ERROR ----
     
     
    ---- START: ERROR ----
    Error call SYSFNC for DIFF in flt_whlvel.f
    ID = -1
     
     
    ---- END: ERROR ----
     
     
    ---- START: ERROR ----
    Unknown exception caught in SYSFNC
     
    ---- END: ERROR ----
     
     
    fdm::ActPoiTor
    Failed to get actuator force: rear_brake_torque::single_component_force
    Terminating Adams Car usersubs...
     
     
    Finished -----
    Elapsed time = 3.86s, CPU time = 1.47s, 38.00%
     
    Simulation is complete.
     
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • m.derbas
    0 m.derbas over 7 years ago
    As it clearly says, something is wrong with the tires
     
    Check them out​, re-assign to them a .tir file
     
    If that doesn't work, run the Simulation in the Event builder rather than other places.
    If you deactivate the static solution there and give it proper Parameters, it will maybe at least simulate the first steps
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
  • rohan.tiwari
    0 rohan.tiwari over 7 years ago
    Ok thank you, i will try that and let you know.
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
<>
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.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information