About
Vector MATLAB/Simulink MC Add-on
Version 16.0 Service Pack 1
Date: 2024-02-22

Contents:

  1. Latest Information
  2. Help
  3. Contact


  1. Latest Information
  2. Version 16.0.10
     
    + 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

  3. Help:
  4. 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:

    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):
    Matlab configuration:
    Show readme files?
    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 Parameters
    2.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:


    For more details please read the corresponding read-me file:
    $matlabroot\toolbox\VectorMC\converter\doc\Vector Converter Readme.htm
    2.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 true flag to compress the generated files
       'path': optionally: directory of the output ZIP-file, e.g. for 'model_cnp_files' a new directory named model_cnp_files will 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 file xpcgenlib.tlc1
    from $matlabroot\toolbox\VectorMC\xpc to $matlabroot\toolbox\rtw\targets\xpc\target\build\tlc
     
    The Matlab p-Code files VGetASAP2Name.p and VGetASAP2ObjectSize.p
    from $matlabroot\toolbox\VectorMC\xpc to $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 names Pxx and the names of 'named' signal lines instead of the mnemonic signal names Sxx2.
    The rest of objects are exported using mnemonic names Pxx for parameters and Sxx for signals.
     
    To make the new files visible for Matlab update the Toolbox Path Cache file by executing the rehash toolboxcache function.
     
    1This feature is based on the original xPC Target xpcgenlib.tlc file 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 (Pxx for parameters and Sxx for signals)
       'path': directory of the output files, e.g. for 'xpc_cnp_files' a new directory named xpc_cnp_files will 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.
     

  5. Contact
  6. Please find the contacts of Vector Informatik GmbH and all subsidiaries worldwide via:
    www.vector.com