Contents:
- Latest Information
Version 16.0.10
- The new version now supports MATLAB R2023a, R2023b, and R2024a.
- Version 8.1 of the MinGW compiler is now supported.
- The MinGW target can now also be used if a Unix shell (bash, MSYS, ...) is configured as the default Windows shell.
- A build error that occurred when using the Windows SDK7.1 compiler was fixed.
- The ASAP2 importer was extended to support axis point objects and descriptions of look-up tables.
- The XCP DAQ memory size was enhanced and allows the measurement of more internal signals.
- An error in the ml_CANapeStopScript API function was fixed.
- Some minor display issues of vector blocks in the model screenshots for the Model Explorer were solved.
- CANape MC3 Matlab Interface - Version 9.1.4
- CANape/vSignalyzer Target (DLL) - Version 16.0.10
- Converter API - Version 2.0.3
- Simulink XCP Server - Version 4.0.3
+ Version 16.0 Hotfix 1
+ Version 16.0
+ Version 15.0.10
+ Version 15.0.0
+ Version 14.0.20
+ Version 14.0.10
+ Version 14.0.0
+ Version 13.0.60
+ Version 13.0.50
+ Version 13.0.40
+ Version 13.0.30
+ Version 13.0.20
+ Version 13.0.10
+ Version 13.0.0
- Help:
2.1 Pre-installation Check
This explains what you need to confirm beforehand in order to install the "Vector MATLAB/Simulink MC Add-on" correctly:
Before installing a new version of the "Vector MATLAB/Simulink MC Add-on" please make sure that no older version of the software is currently installed for the corresponding Matlab software.
To remove the "Vector MATLAB/Simulink MC Add-on" in Windows 7 from your computer hard disk drive, follow these steps:
- Click ÿ Start and then click Control Panel.
- Under Programs, click Uninstall a program. ...
- Select the version of the "Vector MATLAB/Simulink MC Add-on" you want to remove.
- Click Uninstall or Uninstall/Change at the top of the program list.
2.2 Silent installation
The "Vector MATLAB/Simulink MC Add-on" can be called in "silent" mode.
Silent installations are installations that run without an end-user interface and can be used for easier deployment to multiple machines.
The following options are available and must be set for installing the setup to a corresponding Matlab version.
Toolbox/feature names for the silent installation selection via ADDLOCAL property command-line argument (default: all features):- RTTarget: installs the CANape/vSignalyzer Target (DLL)
- SimulinkXCPServer: installs the Simulink XCP Server toolbox
- MC3Interface: installs the CANape MC3 Matlab API Interface
Matlab configuration:- MATLAB_REG_SERVER: whether to register Matlab COM automation server or not (required for Simulink XCP Server; default is 0)
Show readme files?- LAUNCHREADME: shows "Vector MATLAB/Simulink MC Add-on" readme file (default is 0)
- LAUNCH_RT_TARGET_README: shows "CANape/vSignalyzer Target (DLL)" readme file (default is 0)
- LAUNCH_XCP_SERVER_README: shows "Simulink XCP Server" readme file (default is 0)
- LAUNCH_MC3_README: shows "CANape MC3 Matlab Interface" readme file (default is 0)
The following example command will install the "Vector MATLAB/Simulink MC Add-on" (all toolboxes) to the specified Matlab R2017b (64-bit) directory "D:\Matlab\R2017b\":
Vector_MATLAB_Simulink_MC_Add_on.exe /s /v"/qn INSTALLDIR=\"D:\Matlab\R2017b\" MATLAB_REG_SERVER=1"
The following example command will install only the "Simulink XCP Server" to the specified Matlab R2018b (64-bit) directory "D:\Matlab\R2018b\":
Vector_MATLAB_Simulink_MC_Add_on.exe /s /v"/qn INSTALLDIR=\"D:\Matlab\R2018b\" ADDLOCAL=\"SimulinkXCPServer\" MATLAB_REG_SERVER=1"
The following example command will install only the "CANape/vSignalyzer Target" and the "CANape MC3 Matlab Interface" to the specified Matlab R2020b (64-bit) directory "D:\Matlab\R2020b\":
Vector_MATLAB_Simulink_MC_Add_on.exe /s /v"/qn INSTALLDIR=\"D:\Matlab\R2020b\" ADDLOCAL=\"RTTarget,MC3Interface\" MATLAB_REG_SERVER=0"
In order to generate a log file for the "Vector MATLAB/Simulink MC Add-on" installation the following option must be used:
/debuglog
/debuglog"setup.log"
If multiple Matlab installations are installed on a system, it is required to specifiy a certain InstanceId for the installation.
The following example installs a second instance of the "Vector MATLAB/Simulink MC Add-on" with activated debug log file generation:
Vector_MATLAB_Simulink_MC_Add_on.exe /s /instance=2 /debuglog"setup.log" /v"/qn INSTALLDIR=\"D:\Matlab\R2017b\" MATLAB_REG_SERVER=1"
To uninstall a specific instance via command-line call:
Vector_MATLAB_Simulink_MC_Add_on.exe /x /instance=1
Furthermore the standard MsiExec.exe command-line parameters can be found here:
Flexera InstallShield Setup.exe and Update.exe Command-Line Parameters2.3 Toolbox help text
Help text for the Vector MC toolboxes can be displayed in Command Window by entering the following commands.
Vector CANape MC3 Matlab Interface:help MC3Interface
Converter API:help converter
Simulink XCP Server:help SimulinkXCPServer
CANape/vSignalyzer Target (DLL):help cnp
2.4 Vector Converter API
Vector Converter API is a collection of Matlab M-File conversion functions for conversion and export of Simulink Data Dictionary, ASAP2 database and common automotive parameter set files.
Currently the following converter API functions are available:
- VConvert_MFile_DCM: Converts an M-File to a DCM-File.
- VConvert_SLDD_A2L: Generates an ASAP2 database file from a Simulink Data Dictionary.
- VConvert_SLDD_MFile: Generates a parameter M-File from a Simulink Data Dictionary.
- VUpdate_SLDD: Updates a Simulink Data Dictionary with an M-File.
For more details please read the corresponding read-me file:
$matlabroot\toolbox\VectorMC\converter\doc\Vector Converter Readme.htm2.5 Compressing model description INI file and EMF model graphic files to a single ZIP file
To generate and compress model description file and EMF model graphic files to a single ZIP file call:VSaveModel(modelName, 'zip', true); or VSaveModel(modelName, 'path', 'model_cnp_files', 'zip', true);
where:
modelName:name of the corresponding model 'zip':use the trueflag to compress the generated files'path':optionally: directory of the output ZIP-file, e.g. for 'model_cnp_files'a new directory namedmodel_cnp_fileswill be created and the ZIP-file will be placed here
This command must be executed manually.
2.6 Support of CANape Model Explorer for the xPC target
There are two possibilities to support the CANape Model Explorer for the xPC target.
Either 'Adapting xPC Target's ASAP2 database file generation to export valid names' (recommended)
or 'Adapting model description file to support xPC Target names'.
Adapting xPC Target's ASAP2 database file generation to export valid names:
To export valid ASAP2 names during ASAP2 database file generation using xPC target please copy the following files:
The modified TLC filexpcgenlib.tlc1
from$matlabroot\toolbox\VectorMC\xpcto$matlabroot\toolbox\rtw\targets\xpc\target\build\tlc
The Matlab p-Code filesVGetASAP2Name.pandVGetASAP2ObjectSize.p
from$matlabroot\toolbox\VectorMC\xpcto$matlabroot\toolbox\rtw\targets\xpc\xpc
After this adaptation the xPC Target ASAP2 database file generation exports the names of referenced Base Workspace parameters instead of the mnemonic parameter namesPxxand the names of 'named' signal lines instead of the mnemonic signal namesSxx2.
The rest of objects are exported using mnemonic namesPxxfor parameters andSxxfor signals.
To make the new files visible for Matlab update the Toolbox Path Cache file by executing therehash toolboxcachefunction.
1This feature is based on the original xPC Targetxpcgenlib.tlcfile from 12.11.2007.
2The xPC Target ASAP2 database file generation does not export virtual signals even if signals are defined as Simulink/ASAP2.Signal objects.
Adapting model description file to support xPC Target names:
To generate a model description file and EMF model graphic files for xPC Target call:VSaveModel(modelName, 'mode', 'xpctarget', 'path', 'xpc_cnp_files');
where:
modelName:name of the corresponding model 'mode':use 'xpctarget'to generate mnemonic xPC Target names (Pxxfor parameters andSxxfor signals)'path':directory of the output files, e.g. for 'xpc_cnp_files'a new directory namedxpc_cnp_fileswill be created and all generated files will be placed there
This command must be executed manually and must be called after the xPC Target Code-Generation,
because it requires the xPC Target i/o file (modelNamebio.m) and parameter file (modelNamept.m).
The generated model description file can be later used in CANape in combination with the associated xPC Target ASAP2 database file.
- Contact
Please find the contacts of Vector Informatik GmbH and all subsidiaries worldwide via:
www.vector.com