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

Modifying Hard Points in an assembly has made most of the related properties lose their link the subsystem?

Woz
 
This was my new start point, but when I modified the hard points of the front suspension subsystem it lost most/all of its links with the property files? Here's what I did:
 
  1. Created a new subsystem, using the template _fsae_frontsusp.
  2. Modified the hard points to reflect the teams current car setup, placing the zero reference on the ground with y=0 and x=0, which is the xy coord of the CoG, and all dimentions taken from there.
  3. Applied the changes and looked at the graphical representation (looked good).
  4. Saved the subsystem and got a huge list of property file warnings (attached)?
  5. Did the same for the ARB and steering and got similar issues.
  6. Created a new assembly with the front susp, arb and steering, got some more property wanings.
  7. Tried to run a front suspension assembly simulation, but unsurprisingly it wouldn't run.
 
It looks similar to the above problem in that all of the property files are a lot older (2012/2013)?
 
I'm not sure why this would happen? Am I missing a step?
 
Warren
  • 0
    Hi Woz.
    What is the name of the database you are using ? if it for example is called fsae_2018
    then check if the property files mentionen in the file you attached exist in the newer fsae database that you are using?
    If so then just rename the property file database from
    mdids://fsae_2013/bushings.tbl/fsae_control_arm_bushing.bus
    to
    mdids://fsae_2018/bushings.tbl/fsae_control_arm_bushing.bus'
    inside the subsystem files (.sub) referenced by the assembly (.asy)
    This is done with a text editor which can search through a folder and replace in multiple files in the genral case but for you maybe there are not so many subsystems to look through.
     
    Regards
    Thomas
     
  • 0
    Thomas,
    The database is called 'academy_racing_2019' and when I look into the subsystems they all appear to be right, so I'm not sure I'm checking the right thing? Example:
     
    'academy_racing_2019/assemblies/sp18_front_susp' contains the correct subsystems, i.e.
     
    '<academy_racing_2019>/subsystems.tbl/sp18_frontsusp.sub'
     
    The susbsystem 'academy_racing_2019/subsystems.tbl/sp18_frontsusp.sub' uses the template 'mdids://fsae_2018/templates.tbl/_fsae_frontsusp.tpl'
     
    Should this use the 'academy_racing_2019/templates.tbl/_fsae_frontsusp.tpl' template?
     
    I don't understand why anything '2013' is being searched for? Can you maybe explain how the assembly pieces itself together when it is first opened so I can direct my search into the right area? Also, what does the "mdids://" signify?
     
    Woz
  • 0
    Did you get these warnings when you SAVED the subsystem, not when you opened it?
    The warnings are really a reflection of a minor problem in ADAMS/Car. The warnings are about files that are referenced in the template, even though all are replaced in the subsystem.
     
    It doesn't matter what warnings you get when you open or save a subsystem, all that matters is any errors that comes when you start the simulation.
     
    It is hard to say but if you have a 'academy_racing_2019/templates.tbl/_fsae_frontsusp.tpl' template it is likely that it should be used, but that all depends on who built the database.
  • 0
    mdids:// is just one of the ways to say that whatever comes after is a database alias.
    you can also enclose in <>
    mdids://private/ and <private>/ is a way to to point to a physical path defined eg. your .acar.cfg file
    DATABASE private c:\users\thomas\private.cdb
     
    An assembly (.asy) normally contains several subsystems (.sub), they in turn are built from templates (tpl).
    When an assembly is opened then all of the templates used (referenced in each .sub) are opened and the entities that are described in the .sub files are updated with the values in the sub.
     
    Run the attached script with the asembly opened and see what files are used. Hope it helps you forward!
    Regards
    Thomas
     
    Attached Files (1)
  • 0
    JSlatten, thanks for your input. I am the sole user on the team (at the moment) and I installed the software and created the database. However, when I created the database (following a tutorial) the fsae_2018 database that it was based on wasn't quite right (not sure what the issue was), but Rishi (support) sent me a new fsae_2108 database and that worked perfectly? Maybe I need to undo the database I created and start from scratch to ensure there isn't any crossover issues?
     
    Thomas, I will run the script you've sent and see what happens. Hopefully it will point to the issue. Also, thanks for the mdids:// explanation.
     
    Thanks both for your help.
     
    Woz
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.