hexagon logo
Register Sign in
  • State Not Answered
  • Replies 4 replies
  • Subscribers 7 subscribers
  • Views 141 views
  • Users 0 members are here
Options
Related

amech default database files could not be find in my binary

MKvist
I want to use an acar model including default actuator and transducer property files. The model is stored in a binary file to give a quicker opening of the model when I do a design study. The problem is that when I do my analysis full vehicle submit, I get errors complaining about "ERROR: The property file referenced by the following element was not found:". I get the same error if I run the command "acar toolkit read property_files".
 
 
I just saw that the amech_shared database is not in the list from "Database Management -> Database Info ...".
 
 
 
To repeat the error:
 
  1. Start A/Car
  2. Activate mechatronics and save a binary. Use following commands:
  • plugin load plugin_name = amech
  • file binary write file_name = acar_amech_on
3. Close the A/Car session
 
4. Restart A/Car
5. Open the binary and list database info. Use following commands:
  • file binary read filename = acar_amech_on.bin
  • acar toolkit database database info
 
Do you see the same kind of error?
Does anyone have a clue on how I should progress?
 
A/Car version: 2017.2, 2019.2
Attached Files (2)
  • 0
    Maybe you should use the "Save Session" option instead of the basic AView way of saving a binary.
    Reloading a binary the AView way will not reload the previously loaded plugins correctly. The "File - Open - Session" will do this.
  • 0
    That solved my problem :-)
     
    The command is a little bit different in 2017.2 compared to 2019.2, so from now on I will use 2019.2 or later.
     
    Thanks!
  • 0
    You are aware that you can flag "load at startup" in
    Tools -> Plugin Manager ?
    That'd load amech automatically each tome you start ADAMS
     
    Or that you have the variable "plugin_list" in your assembly file , where you just need to add amech ?
    That'll load amech automatically when opening the assembly
     
    Generally I'd prefer loading a plugin the regular way over having it included in binaries.
    Why ? Because the load macro can contain a lot of stuff that may or may not be saved in a session binary.
    Explicitely executing the load macro ensures that you initialize the plugin the proper way.
     
    And even worse: A binary always contains an "old" acar.bin. If there'd be a patch on the installation that affects the acar.bin, your custom acar.bin won't have that patch included until you re-create it.
     
  • 0
    I'm aware of the plugin manager.
     
    There are amech objects in my assembly and it automaticly load the plugin if I'm opening the assembly. So that part is okay. In my case here, I want to have a binary including the assembly so I have a fairly quick open of an adams session including the assembly. The reason for this is to do a larger design study or optimization where I open the assembly, modify some objects, creates the adams solver files and run the simulations on my cluster. This could be done in parallel and to always have a base model that I modify for each design.
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement