nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Siemens Community Catalyst Program

The Siemens Community Catalyst program was co-created with our community to acknowledge technology leaders who consistently contribute to the Siemens Community. Nominations are accepted on a rolling basis.

Nominate Now

Tires are failing to detect road profiles, or are doing so with significant delay

Roque

Hello,

I'm trying to run a RoadCourse simulation on Altair MotioSolve, however, the front tires of the vehicle assembly are not detecting the road profile, or are doing so with significant delay. The vehicle model and the road profile is shown as follows:

The vehicle assembly is a official Altair-provided template for Baja SAE and FSAE. No modifications were made to the model before trying to run the simulation. The Baja/FSAE library was downloaded from the following Altair Community link: https://community.altair.com/discussion/36055/baja-and-fsae-library-overview-in-motionsolve

The road profile selected for the simulations is a 2D pot_hole template available on Altair software folders.

2D_Pothole.rdf

During the simulation, the front tires ignore the road bump and follow a straight trajectory until it reaches half the bump lenght, then, the simulation stops or the front of the vehicle jumps out of the ground. The rear tires are detecting the bump/pothole correctly. When running the simulation with a pothole instead of a bump, the front tires still ignores the pothole, while the rear tires correctly detect it.

The road graphic marker selected is the road reference marker from the tires.

The RoadCourse was configurated as following:

There are neither special characters nor spaces in the file names. I am currently using the Student Edition License.

Thanks in advance,
Roque

Find more posts tagged with

Automotive

Student Competitions

MotionView/MotionSolve

Student Edition License

Accepted answers

GTT Adam

Hi @Roque,

It's likely that the road is not in a fine enough resolution for the tires to 'see' the obstacle, so I would reduce the ROAD_INCR value from 500 to 50.

I used your RDF with the default UTV model and the tires experienced the obstacle without issue.

Hope this helps!

Adam Reid

GTT Adam

Hi @Roque,

I would look to reduce the size of this upside-down pothole, however, as it is quite substantial given a 'normal' automotive tire size.

Hope this helps!

Adam Reid

All comments

GTT Adam

Hi @Roque,

I'm sorry you are having trouble with your bump simulation.

Can you please provide the model as a zipped model archive?

(File >> Export >> Model >> Archive Model & Create Zip File)

Hope this helps!

Adam Reid

Roque

Hello @GTT Adam,

The zipped model is attached as requested:

BajaSAE_Vehicle_Assembly_archive.zip

Additional info:
I can run any of the Car_Truck events without a problem.

Roque

GTT Adam

Hi @Roque,

It's likely that the road is not in a fine enough resolution for the tires to 'see' the obstacle, so I would reduce the ROAD_INCR value from 500 to 50.

I used your RDF with the default UTV model and the tires experienced the obstacle without issue.

Hope this helps!

Adam Reid

GTT Adam

Hi @Roque,

I would look to reduce the size of this upside-down pothole, however, as it is quite substantial given a 'normal' automotive tire size.

Hope this helps!

Adam Reid

Roque

Hi @GTT Adam,

I reduced the ROAD_INCR parameter value from 500 to 50 as suggested, and even to 10, but the problem persists.

I attempted to run the simulation using the UTV model, as you did, to verify if the issue originated from the Baja library; however, I encountered a "Permission Error" when trying to run the simulation.

Returning to the Baja model, the results from reducing the size of the bump from 100 mm to 30 mm are as follow:

Now the simulation finishes without any errors. Thanks again @GTT Adam.

Roque