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

How can I open an adams car 2019 model in adams car 2016?

vivek.bardia
How can I open an adams car 2019 model in adams car 2016?
  • 0
    I was partially successful in opening the models by saving all the templates in ascii and changing the file version. Then changed all the subsystems file versions as well. But since adams car 2019 has some new features like "property_file_list", "property_file_index", etc which were not present in Adams2016, all the property files (like bushing, springs, dampers, etc) were are not assigned. This means assigning these property files in Adams2016 again.
     
    Does somebody know a better way?
     
    Thanks in advance,
    Vivek
     
  • 0
    No, I don't think there's a better way. We don't support going backwards, only forwards (old models should open in new versions).
  • 0
    You would have to "step back" all the new things in ACar by hand. The property_file_list stuff could be fixed in a text editor if you look at how these things are defined in a 2016-template.
    But it may lead to a lot of work and maybe it still doesn't work properly ...
    As Greg mentioned - it is not supported.
  • 0
    You could try by exporting the model as a .cmd file and trying to import it ​in adams 2016 (at least this is what I used to do in view 2018 to 2017)
     
    Other than that there's what @Vivek Bardia​  said
     
    best of luck !
  • 0
    You may try to write a command file or macro that loops over all UDEs and perform a
    var set var = ude_instance.property_file string = (eval(ude_instance.property_file))
    The eval() get's rid of the paramatrization to the property_file_list[index] parametrization.
     
    Could look like this:
    for var=.acar.loopObj obj=* type=ude_instance
     acar toolkit message &
          message=(eval(" - Converting: "//.acar.loopObj[1].name//"..."))
     if cond = (db_exists( .acar.loopObj.object_value //".property_file"))
       var mod var = (.acar.loopObj.object_value.property_file) string = (eval(.acar.loopObj.object_value.property_file.string_value))
     end
    end
     
    You apply this to the template in v2019 and then save it. Then change the version number, open in 2016 and ignore the warnings/errors.
    That should do the job.
     
    Other than that one trick to accomplish parts of this is to set the template file version one step lower than in the ADAMS version you want to use it.
    In that case the automatic conversion macro is started and (some) UDE's are converted.
    But I'm pretty sure that the property_file_list will not be converted this way.
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.