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
  • Hi All, I ran the ADAMS command file as described by JSlatten and it worked fine. I've attached the result of both the model that works (as supplied fsae_2018 and the file that doesn't (academy_racing_2019). It looks like the its looking for property files that don't exist!
     
    I thought this may have something to do with the team database being created while the old 'as supplied fsae_2018.cdb' was installed, but quickly saw that shouldn't make a difference.
     
    What I'm not sure of is how to change the properties as descibed by Thomas above. In which folder/file would I need to change the 2013 to 2018?
     
    I am right in thinking that this issue isn't normal? If I move the hard point positions even by a little bit (30mm), the moodel loses the property files?

    Attached Files (1)
Reply
  • Hi All, I ran the ADAMS command file as described by JSlatten and it worked fine. I've attached the result of both the model that works (as supplied fsae_2018 and the file that doesn't (academy_racing_2019). It looks like the its looking for property files that don't exist!
     
    I thought this may have something to do with the team database being created while the old 'as supplied fsae_2018.cdb' was installed, but quickly saw that shouldn't make a difference.
     
    What I'm not sure of is how to change the properties as descibed by Thomas above. In which folder/file would I need to change the 2013 to 2018?
     
    I am right in thinking that this issue isn't normal? If I move the hard point positions even by a little bit (30mm), the moodel loses the property files?

    Attached Files (1)
Children
No Data