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

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

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

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

Praful

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

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

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.

&nbsp; &nbsp; *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, <span style="color: #f1c40f;">frc_jack_vertical_actuator.l.id, frc_jack_vertical_actuator.r.id, frc_jack_vertical_actuator.l.id, frc_jack_vertical_actuator.r.id, </span>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

&nbsp; &nbsp; *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<strong><span style="color: #169179;">.i.</span></strong>id, frc_jack_vertical_actuator.r<strong><span style="color: #169179;">.i.</span></strong>id, frc_jack_vertical_actuator.l<span style="color: #169179;"><strong>.j.</strong></span>id, frc_jack_vertical_actuator.r<span style="color: #169179;"><strong>.j.</strong></span>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

Hi Sudip

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

&nbsp; &nbsp; *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, <span style="color: #f1c40f;">frc_jack_vertical_actuator.l.id, frc_jack_vertical_actuator.r.id, frc_jack_vertical_actuator.l.id, frc_jack_vertical_actuator.r.id, </span>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

&nbsp; &nbsp; *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<strong><span style="color: #169179;">.i.</span></strong>id, frc_jack_vertical_actuator.r<strong><span style="color: #169179;">.i.</span></strong>id, frc_jack_vertical_actuator.l<span style="color: #169179;"><strong>.j.</strong></span>id, frc_jack_vertical_actuator.r<span style="color: #169179;"><strong>.j.</strong></span>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.