• 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. How can I trigger an external action from within the driver...

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 6
  • Members are here 0
More Content

How can I trigger an external action from within the driver control file?

o.jonson
o.jonson over 6 years ago
Hello,
 
I want to trigger an action from within the driver control files that is not an standard output (throttle/steering/clutch etc). Basically I want to do some minimaneuvers to achieve a certain vehicle state, then activate a parking lock torque in the gearbox, then deactivate it and continue the simulation.
 
Of course I could use some STEP(time) functions in the torque expression to activate the torque at the right moment, but that solution wouldn't be general for different driver control files . Any ideas on how to trigger such an action from within the driver control file?
 
Thanks
/Oskar
 
 
 
 
 
 
 
  • Sign in to reply
  • Cancel
Parents
  • o.jonson
    0 o.jonson over 6 years ago
    I'd like to avoid all solutions where manual editing of the .acf file done since all our simulations are automatically generated. My idea was (as Thomas mentioned) to try to get hold of the name of the minimanouver by calling some varsub routine. I could then match the manouver name (or id or something similar) from the variable , then latch some variables and step up a locking torque. This would avoid any manual work in the .acf files and would work for any driver control file.
     
    However if there is no routine that can get hold of this info from the driver control file, I guess the next best thing is to modify the .acf file with EventRunNext  and an activate command for the torque. Maybe I can call a script with the --pre command that rewrites the .acf based on event type
     
    @Thomas Nygards​ I couldn't find any mac_ana_ful_sub_custom_pos under the ACAR library?
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • o.jonson
    0 o.jonson over 6 years ago
    I'd like to avoid all solutions where manual editing of the .acf file done since all our simulations are automatically generated. My idea was (as Thomas mentioned) to try to get hold of the name of the minimanouver by calling some varsub routine. I could then match the manouver name (or id or something similar) from the variable , then latch some variables and step up a locking torque. This would avoid any manual work in the .acf files and would work for any driver control file.
     
    However if there is no routine that can get hold of this info from the driver control file, I guess the next best thing is to modify the .acf file with EventRunNext  and an activate command for the torque. Maybe I can call a script with the --pre command that rewrites the .acf based on event type
     
    @Thomas Nygards​ I couldn't find any mac_ana_ful_sub_custom_pos under the ACAR library?
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
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.

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

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