I recently had an issue with the fsae database I was using that just wouldn't load, but that issue was fixed with Rishi's help ( simcompanion.hexagon.com/.../ive-been-following-the-adm743-fsae-tutorial-and-while-completing-workshop2part2-simulating-a-full-vehicle-assembly-i-get-an-error-in-the-message-window-stating-the-model-isnt-defined-so-where-and-when-do-i-need-to-define-the-model ). 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: Created a new subsystem, using the template _fsae_frontsusp. 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. Applied the changes and looked at the graphical representation (looked good). Saved the subsystem and got a huge list of property file warnings (attached)? Did the same for the ARB and steering and got similar issues. Created a new assembly with the front susp, arb and steering, got some more property wanings. 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 Links (1) https://mscsoftware.force.com/customers/s/question/0D50c00007Jrkd6CAB/ive-been-following-the-adm743-fsae-tutorial-and-while-completing-workshop2part2-simulating-a-full-vehicle-assembly-i-get-an-error-in-the-message-window-stating-the-model-isnt-defined-so-where-and-when-do-i-need-to-define-the-model Attached Files (1) subsystem_property_file_path_warning.txt

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

I recently had an issue with the fsae database I was using that just wouldn't load, but that issue was fixed with Rishi's help ( simcompanion.hexagon.com/.../ive-been-following-the-adm743-fsae-tutorial-and-while-completing-workshop2part2-simulating-a-full-vehicle-assembly-i-get-an-error-in-the-message-window-stating-the-model-isnt-defined-so-where-and-when-do-i-need-to-define-the-model ).

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:

Created a new subsystem, using the template _fsae_frontsusp.
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.
Applied the changes and looked at the graphical representation (looked good).
Saved the subsystem and got a huge list of property file warnings (attached)?
Did the same for the ARB and steering and got similar issues.
Created a new assembly with the front susp, arb and steering, got some more property wanings.
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

Links (1)

https://mscsoftware.force.com/customers/s/question/0D50c00007Jrkd6CAB/ive-been-following-the-adm743-fsae-tutorial-and-while-completing-workshop2part2-simulating-a-full-vehicle-assembly-i-get-an-error-in-the-message-window-stating-the-model-isnt-defined-so-where-and-when-do-i-need-to-define-the-model

Attached Files (1)

subsystem_property_file_path_warning.txt

0 Thomas Nygårds over 5 years ago

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Woz over 5 years ago

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jesper Slattengren over 5 years ago

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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Thomas Nygårds over 5 years ago

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)

list_prop_files.cmd.zip
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Woz over 5 years ago

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Woz over 5 years ago

Hi Thomas, I tried to run the script from the downloads folder that it downloaded to and nothing happened? Is there a set way to do this? Do I need to open it from Adams?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jesper Slattengren over 5 years ago

Yes, this is an ADAMS command file. Once you have opened your model, press F2 and point to this file.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Woz over 5 years ago

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)

fsae_2018_file_path.txt
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Woz over 5 years ago

OK, I've managed to workout how to change the property lookup files (they're in the subsystem.tbl folders) and I have now modified them so they load and run simulations without errors!!!

Thanks for all the help so far. Very much appreciated.

Woz
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel