hexagon logo

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

 
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
Parents
  • 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)
Reply
  • 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)
Children
No Data