Hi Adam, 

Thanks for responding.

You have correctly said CG summary and total mass in LOG file computed statically. But doubt lies in verifying total mass of the motorcycle in HyperGraph (Post Processing). 

Ideally, Total reaction force at front axle and rear axle shall equal to total weight in log file/CG Summary. Observed mismatch between sum of reaction force and total weight from log file. 

Is there is any other way to check total reaction force?

Hi Savan,

To verify what is shown in the CG/Inertial Summary toll with HyperGraph, you will need to correct your NPOST event as well as what you are plotting.

First, modify your event such that there is no soft or hard constraint on the vehicle body, which will allow it to settle under gravity. Since this is a motorcycle, you will need to add an in-plane constraint between the vehicle body and the ground which acts normal to the XZ plane. This will keep the motorcycle upright and allow you to see the mass of the vehicle only under gravity. By having a constraint on the body, you are adding a third reaction force, which must be removed.

Second, since your event is using the spindle coupling method and not the platform/jack coupling method, the Axle Load measurement will include all masses except the tires. The exclusion of AutoTires will account for a total mass reduction of 17.3 kg (front and rear tire). This is why you are seeing a difference in the LOG file compared to the CG/Inertia Summary Tool. To include the mass of the tires, you must change the event coupling method from spindle to tire.

Lastly, instead of plotting REQ/10000016 Front Axle Load - f2 and REQ/10000017 Rear Axle Load - f2, after making the above changes, please plot Front Tire - SinglePost - Actuator Force Z(70000126) and Rear Tire - SinglePost - Actuator Force Z(70000132). This will plot the force at the ground and thus include all bodies in the system.

As a result, this will give a front tire ground reaction of 897.218 N and a rear tire ground reaction of 1104.87 N. This totals 2002.088 N, or 204.086 N.

Hope this helps!

Adam Reid

Hello Mandy,

Please find below quick feedback regarding your questions.

Question 1: the main purpose of part config is to represent all the configurations in one hm database and activate only the interested one. For instance, different design of a same part.

Question 2: the main Model Subsystem is indeed mandatory. The first subsystem in your model will always be the "Model" subsystem. This is the subsystem connected to the "Main Include".

Question 3: subsystem set is just a group of subsystem, for organization/selection purpose. For this usecase, indeed, it is optional.

Question 4: it all depends of the organize settings (RMB in the subsystem browser > Organize settings). As you'll see, you can determine which dependent entities to move when managing subsystem content and behavior if entities are shared across subsystems. For instance, a prop assign to a comp will be move by default with the comp.

Question 5: All entities moved into a Subsystem will be moved to an Include. The Subsystem always has one linked include and contents of the include and subsystem will always be in sync. Therefore, you must organize your subsystem/entities based on the include type => bulk data, subcase section or I/O section. For instance, loadsteps should be defined in a "subcase section" include type.

Question 6: not sure to understand this question... since v2023, you can create and manage instance of subsystem. Please take a look at this video => https://youtu.be/KvZuZJ7C8lw?si=u2khQjAPLVfMcGED

Question 7: yes absolutely. You can still use the entity state browser, but the active state of parts/subsystems should do the job.

Question 8: Please take a look at this tutorial from the online help and this playlist from our Altair How To Youtube channel:
https://help.altair.com/hwdesktop/hwx/topics/tutorials/hwx/model_build_t.htm

Regards,
Fred.