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