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

More Content

Initialization commands in FMU and Matlab plant export

jozef.bucha
Hello I fully do not understand role of initialization commnad during export of control plant from Acar. Adm 711 says in lecture 6, that it is mandatory to define this as:
– The initialization command field uses the ‘file/command’ command to load the special _controls.acf file. This initializes the vehicle model and is essential for proper operation.
 
but here in this article:
 
 
they do not use initialization command.
 
My question is during FMI1 or FMI2 export from ACAR, are those Initialization Commands also mandatory using Control/Plant Export?
 
In this article the also do not use them:
 
 
Thanks
 
Jozef
  • 0
    Hi Jozef,
     
    I am quite certain that the FMU method does this for your automatically - you do not need to specify the ADAMS_init command. Here is another article about a new FMU export interface:
     
    You can see in this article that there is not even a way to specify the init command, so I'm quite certain that it does it automatically. If you change the .fmu to be .zip and then open the archive and look in the /resources directory you will see that the xxxx_controls.acf file gets automatically put into the fmu and is automatically called at the beginning of a full-vehicle event.
     
    HTH,
    Kent
     
  • 0
    Thanks Kent,
     
    For FMU i will use new export interface
     
    but i still not understand init command for matlab plant export. ADM711 in abs brake example uses init command to call ***_control.acf:
     
    file/command=abs_brake_control.acf, KBKB8021668, do not.
     
    Both simulations produce exactly same results. So why and when is needed to use such init command and when not.
     
    Thanks
     
    Jozef
     
     
  • 0
    Also I do not understand why from some models i am able to get *.m, _controls.acf, *.inf file. I.E. convertible model from acar_concept database.
     
    Crossover from same database using same procedure did not produce *.m, _controls.acf, *.inf file.
    MDI_demo_vehicle directly from shared database also not. Publishing assembly with everything to private database did not fix this problem.
     
    I was trying to export files from double lane change using files_only Adams 2020 fp1, with same results in win10 and rhel7.5
     
    jozef
  • 0
    Hi Jozef,
     
    You will get the .m file produced if you have:
    • the Controls plugin loaded,
    • AND you have plant input/output structures in the model (the testrig has a number of plant outputs, but not a plant input)
    So that is the logic that we use before exporting the "Controls" files. These files should be:
    • .m file for Matlab
    • .inf for Easy5
    • xxx_controls.acf to *initialize* your vehicle for a full-vehicle (dynamic) simulation.
     
    The xxx_controls.acf contains all of the initialization commands that you would see for a full-vehicle event, but omits the "SIM/DYN" command that advances time. So it gets the vehicle setup for the event, but does not advance time. You MUST call this _controls.acf file using ADAMS_init with standard Adams Controls, or your vehicle might not start properly. With FMU we have recognized that that command is needed and we put it in automatically for you.
     
    Regards,
    Kent
    Kent
     
  • 0
    Thanks a lot,
    ​
    I​ guess this was missing.
    ​
    • AND you have plant input/output structures in the model (the testrig has a number of plant outputs, but not a plant input)
    I​ will try
    ​
    Thanks again
    ​
    Jozef​
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.