Skip to main content
Ctrl+K
Lattix  documentation - Home
  • Why Use Lattix Architect?
    • Architecture Discovery
    • Architecture based Re-engineering
    • Comprehensive Coverage of Technologies
    • Impact Analysis
    • Learning to Use Lattix (4 Hours)
    • Manage Large Scale Heterogeneous Systems
    • Specify and Enforce Architecture
    • Track, Measure and Report
  • Installation
    • Installing on Mac
    • Installing on Windows
    • Installing on Linux
    • License Management
    • Floating License Manager
    • Running Lattix Architect from the Command Line on Mac
    • Supported Platforms and Configurations
    • Upgrade Process
  • Lattix Architect User Guide
    • Lattix Architect User Interface
    • Create a New Project
    • Managing Lattix Architect Projects
    • Working with the Dependency Structure Matrix (DSM)
    • Working with the Conceptual Architecture Diagram (CAD)
    • Working with the Heatmap
    • Applying Algorithms
    • Monitoring and Enforcing Architecture
    • Member Level Analysis
    • Filtering and Configuring Dependencies and Subsystems
    • Data Export and Reporting
    • Tagging and Impact Analysis
    • Multi-Module Projects
    • Match Model
    • Metrics
    • Architectural Category Tags and Risk Metric
    • Importing MISRA/AUTOSAR violations into Lattix
    • Importing code coverage data into Lattix
    • Support for Android APK files/AAR
    • Find Issues
    • Visual Studio Integration
    • Rules Import/Export
  • Command Line Applications (LDC)
    • Getting your hostid
    • What is LDC?
    • Using ldcupdate
    • Using ldcreport
    • Using ldcscript
    • Using ldcdiff
    • Using ldcget
    • Using ldcpublish
    • Using ldclicense
    • LDC Command Line Exit Codes
    • Continuous Integration with Hudson and Jenkins
    • Continuous Integration with Hudson and Jenkins V11
    • GitLab Integration
    • Jira Integration
    • SonarQube Integration
    • Integration into Ant builds (build.xml)
  • Modeling Complex Systems
    • Common Questions
    • Configuring Display Defaults
    • Creating DSMs Manually
    • Lattix Architect Data Model
    • Partitioning Algorithms for Activity/Process DSMs
    • Using the LDI Module
    • Working with Excel Spreadsheets
  • Module Guide
    • ActionScript (deprecated)
    • Ada
    • AUTOSAR/ARXML
    • C/C++
      • C++ (with Clang)
        • C/C++ with Clang using Visual Studio
        • C/C++ with Clang using a Build Spec
        • C/C++ with Clang using the Project Configurer
      • C++ (with Axivion)
      • C++ (with Klocwork)
      • C++ (with Understand)
      • C++ (with Parasoft)
    • EJB (deprecated)
    • Excel
    • Python (Understand)
    • Python
    • Ruby
    • Fortran
    • Java
    • JavaScript
    • LDI
    • .NET
    • Oracle
    • SQL (SQL Server)
    • UML/SysML
  • Lattix Web and the Repository
    • Accessing the Repository
    • Repository Management (backup, migration)
    • Lattix Web Dashboard
    • Lattix Web Project Page
    • Administering Lattix Web
    • HTTPS support for Lattix Web
    • Lattix Web REST API
    • Troubleshooting Lattix Web
    • Clear Project Caches
  • Scripting
    • Installing and Running Scripts
    • Scripting with Groovy
    • Script Catalog
  • Additional Tools
    • LXBuild: Monitor build for C/C++ analysis
    • LXBuild Internal Options
    • SARIF and source Viewing in VS Code
    • JavaScript Analyzer
    • Python Analyzer
    • JSP Analyzer
    • Java Constant Analyzer
    • Oracle Pro*C Analyzer
    • iBatis Analyzer
    • Generating dependencies using Oracle Audit
    • Simulink Analyzer
  • Release Notes
    • Release 2024
    • Release 2023
    • Release 2022
    • Release 2021
    • Release 12
    • Release 11
    • Release 10
    • Release 9
    • Release 8
    • Release 7
    • Release 6
    • Release 5
    • Release 4
    • Release 3
    • Release 2
    • Release 1
  • Succeeding with your Lattix Architect and Lattix Web evaluation
  • Frequently Asked Questions
  • .rst

Simulink Analyzer

Contents

  • Generate the Simulink XML file
  • Generate the LDI file
  • Create a Lattix project
  • Acknowledgement

Simulink Analyzer#

The Matlab/Simulink Analyzer takes as input a Simulink XML file and generates LDI from it. It works only for Standard Simulink models, not with the extended models such as those that are based on state.

This analyzer does a XSL transformation on the Simulink XML file to generate the LDI file. Contact Lattix (support@lattix.com) if you would like to try it out. Please note that this analyzer is provided for demonstration purposes only. If there is sufficient interest we will consider it developing and supporting it.

Generate the Simulink XML file#

Export xml model data from Simulink by running the following command:

save_system('sys', 'sim_filename.xml','ExportToXML', true)

Generate the LDI file#

Run the following command (note that this command assumes that you java installed and it is in your path):

java -jar saxon9he.jar -s:sim_filename.xml -xsl:mdlxml2ldi.xsl -o:output_filename.ldi.xml

-s:sim_filename.xml: Specify the xml file that you exported from Simulink.

-o:output_filename.ldi.xml: Specify the name of the ldi file for the output.

Create a Lattix project#

The generated ldi file can be loaded in using the LDI module.

Acknowledgement#

This analyzer was developed by TechMatrix, a Lattix partner in Japan.

previous

Generating dependencies using Oracle Audit

next

Release Notes

Contents
  • Generate the Simulink XML file
  • Generate the LDI file
  • Create a Lattix project
  • Acknowledgement

By CodeClinic LLC

© Copyright 2024, CodeClinic LLC.