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

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

Parents

0 o.jonson over 5 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

0 o.jonson over 5 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