Jump to content

Recommended Posts

I am using the full vehicle with driver.

and have gone through the help files available.

To perform various maneuvers I have edited the .adf file for event altairdriverfile, in the .txt format and then inserted it from the event editor tab.

For the .adf file I copied a existing .adf file from Altair library (Straight Line Braking)  and then added the following from 3D spline road data file available in the help section.

ROAD_TYPE 			= 'PotHole'
COORDINATE_SYSTEM	      = 'distance'
START 			    = 0.7
LENGTH 			   = 1.5
DEPTH			     = -0.007
ROAD_TYPE             = 'Curb'
HEIGHT                = 0.05
START                 = 0
ROUND_OFF             = 3.99805
TOP_WIDTH             = 1
EDGE_WIDTH            = 3

But it only performed the straight line braking.

How do I insert the code for it? ( I want to add a few bumps and drops) 

Share this post

Link to post
Share on other sites

Thank you 


1.) I tried simulating it, but it still continued to be a straight path only.

I have edited the file as the following 

Road Type = 2D FLAT


FILE_TYPE  =  'rdf'
! road data file for TNO_flat_road
LENGTH             = 'meter'
FORCE              = 'newton'
ANGLE              = 'radians'
MASS               = 'kg'
TIME               = 'sec'
FUNCTION_NAME = 'mssticsub::ROAD'
METHOD             = '2D'
ROAD_TYPE          = 'flat'
 OFFSET                      = 0
 MU                          = 1.0
 DEPTH                       = -0.05
 START                       = 10
 LENGTH                      =0.5


(I am editing it in notepad and then saving it)

Please point out to the mistake. 

I want to create a pothole of the following dimension on the road.  (dimension in meters)


2) I have used the Vehicle Tools to create graphic files for the road files I am using (CRG,RDF) so I get an idea about the road graphically.

Is it possible to create a graphic file for the above code or for instance any .RDF or .ADF file given in the directory. How do I do it? 



3) How do you add ramps and potholes in .CRG file?

Share this post

Link to post
Share on other sites

There are three possible sources of error here:



1. Your tire data needs to be able to support non-flat road surfaces.  You have not indicated which tire model you are using (MF-Tyre, Fiala, F-tire, etc).  Tip:  look through the .log file, it will tell you what road file is being referenced, and what type of road contact.


For example, there is a flag to set in MF-Tyre for the type of road contact you want to use.  This has to be set correctly before the road file will be properly utilized.  Research "USE_MODE" in the MF-Tyre docs, if that's the tire model you want to use.


2. non-flat road surfaces typically required additional licenses.  Do you have the necessary license to run non-flat roads?  (Important note:  Our built-in enhanced Fiala tire model allows users to use non-flat road surfaces, for free.  It doesn't have the same level of fidelity as tire model like MF-Swift, CD-Tire, FTire, that all require additional 3rd party licenses.)

3. in "road type" in the file above, you still list it as "flat".  So, it's going to ignore any parameters you set.  You should look at  some of the many examples provided in the installation.  There are also examples provided with documentation for the particular tire model you are using (F-tire, CD-Tire, MF-Tyre, etc).


We currently do not provide tools for editing/modifying CRG files.  However, there are some open source tools available on the OpenCRG website.


If you want to create graphics for an analytical road surface like you are trying to use, what I normally do is create the geometry in Hypermesh, and put a simple mesh on it, and the export it as a .h3d file, which can then be loaded directly into MotionView as a graphical entity.


Here is an example of a pot hole road, taken from our installation folder:

FILE_TYPE  =  'rdf'
'pot_hole style road description'
 MASS               = 'kg'
 LENGTH             = 'mm'
 TIME               = 'sec'
 ANGLE              = 'degree'
 FORCE              = 'newton'
 ROAD_INCR = 500
 METHOD             = '2D'
 ROAD_TYPE          = 'pot_hole'
 OFFSET                  =     0
 MU                      =   1.0
 DEPTH                   =    -50.0
 START                   =  1000
 LENGTH                  =   2000



Share this post

Link to post
Share on other sites

Thank You Chris


I am using the Auto-Tires 


FILE_TYPE                ='tir'
FILE_VERSION             =3.0
FILE_FORMAT              ='ASCII'
! FILE_NAME :         TNO_car205_60R15.tir
! TIRE_VERSION :      MF-Tyre/MF-Swift 6.2
! MF-TOOL TEMPLATE :  TNO_mfswift62          $Revision: 1.15 $


From the tire property file 


I tried using the TNO_Plank .RDF file but still the vehicle in the H3D model shows no simulation of going over the Plank it follows the straight path only.

(It is the original file in the library) 


Can you please provide your secure dropbox ID. 


Share this post

Link to post
Share on other sites

Did you check the USE_MODE flag in the .tir file?  What values is given there?


Another thing you may want to check is the orientation of the Road Reference Marker.  Sometimes this needs to be rotated about the Z axis 180 degrees, depending on the tire model and road file you are using.  Note there are probably two Markers, one for the front axle, and one for the rear axle.

Share this post

Link to post
Share on other sites

1. The USE_MODE value is 114.


I tried the values as 434 and 400 also, but encountered licencing error from --- TASS Licensing Service ---.


2. I have checked for the orientation of the Road Reference Marker it matches with my geometric axis, But they are at different heights. Is it alright to keep it unchanged. 


3. I am also using the TNO_plank_road RDF file as the Road Property File. Will this work? 


4.According to the USE_MODE code I want to evaluate the forces in Fz direction also, only Fx, Fy and Mx My Mz is specified. 


Thank You 


Share this post

Link to post
Share on other sites

1. "USE_MODE" 114 - This is part of the problem.   114 is for "smooth road contact"  You are not going to be able to use certain types of road surfaces.  Even then, this specifies a "point follower" road contact, which does not provide physically accurate results for short wavelength bumps.  In order to use mode 4XX, TASS requires an additional 3rd party license, as do all of the other tire model companies (CD Tire, FTire).  Per my previous post, you do not have the necessary licenses to use this tire model over a plank road surface.  You might try a polyline, but again the physics are not going to be reasonable.


Again, please talk a look at Altair's enhanced Fiala tire model.  We support many different types of road surfaces, and there is no additional license cost.  It utilizes elliptical cam contacts, which is better than point follower, but not quite as accurate as the brush contact used by tire models like FTire or CDTire.


To use this tire model, all you have to do is point to the tire data in the sample file directory (it will say something like "fiala with elliptical cams" in the filename).  It is also well documented in our help.  The tire data files also have a smaller dataset, so they require less data to populate.  This kind of tire model serves as a better starting point for users just starting out with bumpy roads.



Share this post

Link to post
Share on other sites

1. I have started using FIALA Tire model and given RDF files in the FIALA file, I have used different USE MODE code (0,1,2,434,534) for the Simulations but the pothole is still not being simulated it follows a straight line. 


2. While the vehicle moving forward the output shaft and the half shaft on the right side are not straight and tend to deform and form an angle like its buckling. 






Share this post

Link to post
Share on other sites

1. The FIALA tire model does not have a USE_MODE code.  Make sure you are starting with a Fiala tire dataset from the examples.  Also try rotating the road reference marker 180 degrees as explained previously.  Note, the .log file will tell you what road surface is being used.  That's always a good first double check.  If something is wrong with your road surface, it will default to a flat road.

2. It's likely that you have not defined the outer CV joint location correctly. It needs to be located along the rotational axis of the wheel. Otherwise you will see the behavior you seem to be describing.

Share this post

Link to post
Share on other sites

I am using the following as the tire property file from examples and also other examples of road property file from examples


! HWVERSION_2019.1.0.20_Jun 28 2019_20:45:2
LENGTH                    ='meter'
FORCE                     ='newton'
ANGLE                     ='radians'
MASS                      ='kg'
TIME                      ='second'
FUNCTION_NAME             = 'mbdtire::USER_FIALA'
USE_MODE                  =  1
UNLOADED_RADIUS           = 0.272        $Free tyre radius         
WIDTH                     = 0.177        $Nominal section width of the tyre                 
ASPECT_RATIO              = 0.6           $Nominal aspect ratio
VERTICAL_STIFFNESS        = 47651.8      $Vertical Stiffness [force/length]
VERTICAL_DAMPING          = 50            $Vertical Damping [force * time / length]
ROLLING_RESISTANCE        = 0.007         $Rolling Resistance Moment Coefficient [length]
CSLIP                     = 86748         $Logitudinal Slip Stiffness [force]; 
CALPHA                    = 61296         $Cornering Stiffness [force / angle]
CGAMMA                    = 3594          $Camber Stiffness [force / angle]
UMAX                      = 1.0           $Static Friction Coefficient
UMIN                      = 0.878         $Sliding Friction Coefficient
RLENX                     = 0.242         $Relaxation Length in x direction
RLENY                     = 0.597         $Relaxation Length in y direction
ROLLING_RADIUS_FACTOR     = 0.5           $Rolling radius  =  loaded radius + ROLLING_RADIUS_FACTOR *(unloaded radius - loaded radius)
PA1                     = 0.671           $Coefficient of square root term in contact length equation
PA2                     = 0.733           $Coefficient of linear term in contact length equation
PB1                     = 1.059           $Coefficient of cube root term in contact width equation
PB2                     = -1.1878         $Coefficient of linear term in contact width equation
PLS                     = 0.8335          $Scaling of distance between front and rear ellipsoid
PAE                     = 0.4382          $Half of ellipsoid length
PBE                     = 0.302           $Half of Ellipsoid height 
PCE                     = 1.5174          $Order of ellipsoid 
ROAD_INCREMENT          = 0.001           $distance between contact points
N_WIDTH                 = 4               $Number of cams along contact width 
N_LENGTH                = 4               $Number of cams along contact length 

and also used the road property file that you have mentioned as above and did the following rotations also. 

I have checked the .log file and it shows that it has taken the pot hole profile and FIALA tire too. 

but still I can't simulate it going through the pot hole or any cleat. 


2. The left side half shaft and output shaft remains straight but only the right side deforms. 

The axis of rotation of half shaft and wheel center is not the same.

Had changed the position according to our geometry.


Thank you 


halfshaft buckling.PNG

halfshaft buckling 2.PNG

Share this post

Link to post
Share on other sites

1. at this point, we'd need to take a look at the model, road and tire files you are using, if you are able to provide them.  If not, I would suggest starting with a default model, and tire, and step by step adding the Fiala tire and road.  It's really a simple workflow, with the only thing you typically have to pay attention to is the orientation of the Road Reference Marker

2. The output shafts are clearly not in line with the differential.  I suspect you may have broken some of the parmeterization in the model.  The axis of the half shaft doesn't have to be on the axis of wheel rotation.  However, the outer CV joint must be on on the axis of wheel rotation.  Similarly, the inner CV joint locations must lie on the same axis of rotation as the differential revolute joint.


Since you are not a university user, it may make more sense for you to reach out to your account manager at Altair, and have him connect you with our support team, where they can provide you with more hands-on assistance.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

You are posting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...