MATLAB Answers

0

Why do motion measurements depend on the location where the Environment block is connected relative to the Variable Ratio Gear block in SimDriveline 1.0.2 (R14SP2)?

In the attached model 'new_model.mdl', the motion measurement answer varies depending on which side of the Variable Ratio Gear block the Driveline Environment block is attached.
In this model with a Variable Ratio Gear in the driveline, compare the motion measurements obtained by attaching the Environment block to the left part of the driveline as opposed to attaching it to the right part. Attaching on the right (F) side yields unreasonable velocities for that driveline axis.

Products


Release

R14SP2

1 Answer

Answer by MathWorks Support Team on 27 Jun 2009
 Accepted Answer

This enhancement has been incorporated in Release 14 Service Pack 3 (R14SP3). For previous product releases, read below for any possible workarounds:
We have verified that there is a bug in SimDriveline 1.0.2 (R14SP2) in the way that motion measurements vary depending on which side of the Variable Ratio Gear block the Driveline Environment block is attached.
To work around this issue, download a revised version of the files mentioned below. Here are the required steps:
1. Quit MATLAB
2. Download the file 'drive_engine.mexglx' and place the file in the following directory:
$MATLABtoolbox\physmod\drive\drive\
(where $MATLAB is the MATLAB root directory on your machine, as returned by typing
matlabroot
at the MATLAB command prompt.)
3. Download the file 'drive_codegen_files.tar.gz', unzip it, and place the unzipped files in the following directory:
$MATLAB\toolbox\physmod\drive\c\
(where $MATLAB is the MATLAB root directory on your machine, as returned by typing
matlabroot
at the MATLAB command prompt.)
4. Download the file 'drive_precomplib_glnx86.tar.gz', unzip it, and place the unzipped files in the following directory:
$MATLAB\toolbox\physmod\drive\lib\glnx86\
(where $MATLAB is the MATLAB root directory on your machine, as returned by typing
matlabroot
at the MATLAB command prompt.)
4. Restart MATLAB
5. After restarting MATLAB, issue the following command at the MATLAB prompt:
rehash toolboxcache
Note: This solution is for Linux only

  0 Comments

Sign in to comment.