User defined Output request causing error in "Static Ride Analysis event"

Sudip_Chavan · January 13

Hi

I am simulating a custom made double wishbone model with static ride analysis event, and trying to extract ride steer, caster and camber using following function:

`USER({MODEL.sys_misc.ds_report_ms.scale_index.value}, 180, 1, {sa_testing_parameter_array.id, %d}, 0, {sa_vehicle_parameter_array.id, %d})`

The simulation works perfectly if that output request is deactivated, when it is activated the log files shows solver failed and Error written as,

INFO: ALL: 10705150 11102020 20705150 21102020 30903100 3094100

ERROR: Marker [id=11101] not found in SYSFNC!

ERRMWS: USER [11101]

sdf_wcdata: Error calling sysfnc for left constraint force.

** EXECUTION STOPS DUE TO ENDFLG IN USER SUB **

Abnormal return from processing model!

ERROR: Simulation failed due to error encountered in analysis!

Marker with id 11101 are following markers which all are located & oriented correctly as per my template reference model

1.WC marker at ground, 2.Jack CP marker, 3.Upper steer axis, 4.Ground Patch Marker

And Left Verical Actuator force is also verified from reference model.

Any help would be greatly appreciated

Best regards

Sudip Chavan

Praful · January 19

Praful Prabhu_20784 said:
Hi Sudip - If the model is not confidential, you may attach the mdl & any other reference files when you reply.

Else, drop the files at this drop box > https://ftam1.altair.com/filedrop/ppraf@altair.com

Regards

Praful

Hi Sudip

Thank you for sharing the model. I did a quick review. I see you have edited Solver Array testrig_parameter_array.

    *SetSolverArray(sa_testrig_parameter_array, VALUE, 17, mrk_wc.l.id, mrk_wc.r.id, mrk_kp.l.id, mrk_kp.r.id, mrk_grnd.l.id, mrk_grnd.r.id, frc_jack_vertical_actuator.l.id, frc_jack_vertical_actuator.r.id, frc_jack_vertical_actuator.l.id, frc_jack_vertical_actuator.r.id, MODEL.sys_steering.j_1.i.id, -1, ds_steering_actuation_application.int_api_value.value, mrk_upr_mnt.l.id, mrk_upr_mnt.r.id, mrk_jack_cp.l.id, mrk_jack_cp.r.id)

I think the function expects markers in the 7th to 10th arguments. What you have referred are force ids !

frc_jack_vertical_actuator.l.id is the id of the left side of force frc_jack_vertical_actuator.

To rectify it, you need to add .i and .j

*SetSolverArray(sa_testrig_parameter_array, VALUE, 17, mrk_wc.l.id, mrk_wc.r.id, mrk_kp.l.id, mrk_kp.r.id, mrk_grnd.l.id, mrk_grnd.r.id, frc_jack_vertical_actuator.l.i.id, frc_jack_vertical_actuator.r.i.id, frc_jack_vertical_actuator.l.j.id, frc_jack_vertical_actuator.r.j.id, MODEL.sys_steering.j_1.i.id, -1, ds_steering_actuation_application.int_api_value.value, mrk_upr_mnt.l.id, mrk_upr_mnt.r.id, mrk_jack_cp.l.id, mrk_jack_cp.r.id)

After this change, I was able to run the model successfully.

Regards

Praful

GTT Adam · January 15

Hi Sudip,

If you are having trouble with the USER subroutine, you could always just measure the caster, camber, and tire steered angles through Expressions. Simply place a Marker attached to the knuckle which is located at the tire center and aligned with the Global Frame Marker. Measure the rotational displacement (AZ) of the new Marker with respect to the Global Frame Marker for steer angle. Measure AX for the camber angle. Lastly, align the Z axis of a second marker along the shock / AutoDamper entity and measure AY with respect to the Global Frame Marker as well to calculate the caster angle.

Hope this helps!

Adam Reid

Sudip_Chavan · January 17

Hi Adam,

Thank you for your reply! It works.

But as reference to all template models they have defined Suspension Design Factors (SDF) Requests with use of USER Subroutine, with ref to Local File : msautoutils

I was actually trying to do the same for easy and fast post processing of the model.

Can anyone help me out with above USER Subroutine error with reference to local file msautoutils

Praful · January 17

Hi Sudip - would you be able to share your model ?

Praful

Sudip_Chavan · January 18

Praful Prabhu_20784 said:
Hi Sudip - would you be able to share your model ?

Praful

Hi Praful,

Yes, I can share my model as it only includes default modelling parameters and not related to any other specific product.

Can you provide any info to share that model to you?

Thanks and Regards,

Sudip Chavan

Praful · January 18

Sudip Chavan_20509 said:
Hi Praful,

Yes, I can share my model as it only includes default modelling parameters and not related to any other specific product.

Can you provide any info to share that model to you?

Thanks and Regards,

Sudip Chavan

Hi Sudip - If the model is not confidential, you may attach the mdl & any other reference files when you reply.

Else, drop the files at this drop box > https://ftam1.altair.com/filedrop/ppraf@altair.com

Regards

Praful

Praful · January 19

Praful Prabhu_20784 said:
Hi Sudip - If the model is not confidential, you may attach the mdl & any other reference files when you reply.

Else, drop the files at this drop box > https://ftam1.altair.com/filedrop/ppraf@altair.com

Regards

Praful

Hi Sudip

Thank you for sharing the model. I did a quick review. I see you have edited Solver Array testrig_parameter_array.

    *SetSolverArray(sa_testrig_parameter_array, VALUE, 17, mrk_wc.l.id, mrk_wc.r.id, mrk_kp.l.id, mrk_kp.r.id, mrk_grnd.l.id, mrk_grnd.r.id, frc_jack_vertical_actuator.l.id, frc_jack_vertical_actuator.r.id, frc_jack_vertical_actuator.l.id, frc_jack_vertical_actuator.r.id, MODEL.sys_steering.j_1.i.id, -1, ds_steering_actuation_application.int_api_value.value, mrk_upr_mnt.l.id, mrk_upr_mnt.r.id, mrk_jack_cp.l.id, mrk_jack_cp.r.id)

I think the function expects markers in the 7th to 10th arguments. What you have referred are force ids !

frc_jack_vertical_actuator.l.id is the id of the left side of force frc_jack_vertical_actuator.

To rectify it, you need to add .i and .j

*SetSolverArray(sa_testrig_parameter_array, VALUE, 17, mrk_wc.l.id, mrk_wc.r.id, mrk_kp.l.id, mrk_kp.r.id, mrk_grnd.l.id, mrk_grnd.r.id, frc_jack_vertical_actuator.l.i.id, frc_jack_vertical_actuator.r.i.id, frc_jack_vertical_actuator.l.j.id, frc_jack_vertical_actuator.r.j.id, MODEL.sys_steering.j_1.i.id, -1, ds_steering_actuation_application.int_api_value.value, mrk_upr_mnt.l.id, mrk_upr_mnt.r.id, mrk_jack_cp.l.id, mrk_jack_cp.r.id)

After this change, I was able to run the model successfully.

Regards

Praful

Sudip_Chavan · January 19

Praful Prabhu_20784 said:
Hi Sudip

Thank you for sharing the model. I did a quick review. I see you have edited Solver Array testrig_parameter_array.

    *SetSolverArray(sa_testrig_parameter_array, VALUE, 17, mrk_wc.l.id, mrk_wc.r.id, mrk_kp.l.id, mrk_kp.r.id, mrk_grnd.l.id, mrk_grnd.r.id, frc_jack_vertical_actuator.l.id, frc_jack_vertical_actuator.r.id, frc_jack_vertical_actuator.l.id, frc_jack_vertical_actuator.r.id, MODEL.sys_steering.j_1.i.id, -1, ds_steering_actuation_application.int_api_value.value, mrk_upr_mnt.l.id, mrk_upr_mnt.r.id, mrk_jack_cp.l.id, mrk_jack_cp.r.id)

I think the function expects markers in the 7th to 10th arguments. What you have referred are force ids !

frc_jack_vertical_actuator.l.id is the id of the left side of force frc_jack_vertical_actuator.

To rectify it, you need to add .i and .j

    *SetSolverArray(sa_testrig_parameter_array, VALUE, 17, mrk_wc.l.id, mrk_wc.r.id, mrk_kp.l.id, mrk_kp.r.id, mrk_grnd.l.id, mrk_grnd.r.id, frc_jack_vertical_actuator.l.i.id, frc_jack_vertical_actuator.r.i.id, frc_jack_vertical_actuator.l.j.id, frc_jack_vertical_actuator.r.j.id, MODEL.sys_steering.j_1.i.id, -1, ds_steering_actuation_application.int_api_value.value, mrk_upr_mnt.l.id, mrk_upr_mnt.r.id, mrk_jack_cp.l.id, mrk_jack_cp.r.id)

After this change, I was able to run the model successfully.

Regards

Praful

Thanks for the info!

It worked.

Thank You.

User defined Output request causing error in "Static Ride Analysis event"

Best Answer

Answers

Categories