• 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
  3. Tire Force and Moment Reporting

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 8
  • Subscribers 3
  • Views 19
  • Members are here 0
More Content

Tire Force and Moment Reporting

slee
slee over 8 years ago
From A/Chassis, I am referring Req/1051~43 for Tire Force & Moment data from vehicle data set. When I checked these Lateral Forces at 4 corners during a constant radius, they were shown as sine-wave-like oscillation around zero-value with a sizeable magnitude equivalent to a given slip angles.  (same for Fx, except values for z-axis) I believe this is caused from these F&M values are being reported with a global reference marker... not a vehicle-fixed marker like a CG.  Any thought on this? And what to do if F&M data is wanted to be reported in vehicle orientation? (No source code of Req/Subroutine is open to public.)      
  • Sign in to reply
  • Cancel
  • Yuan.Lyu
    0 Yuan.Lyu over 8 years ago
    Hi,
     
    Could you please provide the REQ and user routine number in the ADM file? I could help you to check the routine source.
     
    Regards,
    Yuan
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • slee
    0 slee over 8 years ago
    They are REQ/1050 ~1053 under 'user defined' group as LR/RR/LF/RF Tire Force.
    When these F&M is plotted by the '(dynamic) constant radius' event, they are seen as oscillating about their neutral positions corresponding to vehicle position in on a circle, esp Lateral Force. This may have not been obvious in other events.
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Yuan.Lyu
    0 Yuan.Lyu over 8 years ago
    I have checked "REQ/1150, USER(20,...)" request routine, and find that the forces and torques are calculated at the wheel center with respect to a coordinate system whose Z axis is aligned with GlobalZ, and X and Y are shadow vector of spindle axes on the road. This routine only reads and returns results from the Tire output array, so my guess is that the coordinate system selection is hard coded somewhere in ATire solver. I will contact our tire developer to see if there is a workaround for this.
     
    Regards,
    Yuan
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Micha
    0 Micha over 8 years ago
    Slee (BTW: would be nice to know where you are and whom you are working for): ever thought about using FTire? It gives you tire/forces and moments both in contact patch and spindle (no, they are *not* the same) in nearly every coordinate system you might think about.
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • slee
    0 slee over 8 years ago
    Thanks Micha for your input. I am aware of FTire. When needed, it will be considered.
    • 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