User documentation

The Maestro2 approach is to create a specification in the domain specific language MaBL, verify the specification and finally, execute the specification. There is a particular focus on making the FMI-commands explicit in the specification, but it is possible to define runtime behaviour that is not limited to MaBL.

The Maestro2 approach to co-simulation is presented and described in Overview.

The ideal place to get a first impression of co-simulation with Maestro2 is Getting Started.

Table of Contents:

• 1. Overview
  • 1.1. Creating a specification
  • 1.2. Expansion of a Specification
  • 1.3. Executing a specification
  • 1.4. Outline of the Co-simulation Process with Maestro2
• 2. Getting Started
  • 2.1. DEVELOPMENT BRANCH
  • 2.2. Setup
  • 2.3. Example
  • 2.4. Part 1: First MaBL Specification
  • 2.5. Part 2: Specification Generation and Expansion
    • 2.5.1. Configuration file
    • 2.5.2. Specification Generation
    • 2.5.3. Final specification and Execution
    • 2.5.4. Execution
    • 2.5.5. Extra: Expansion
• 3. Command Line Interface
  • 3.1. Sub command: import
  • 3.2. Sub command: interpret
  • 3.3. Sub command: export
• 4. Web Interface (API)
• 5. Specification Components
  • 5.1. Expansion
  • 5.2. Specification Generator
• 6. Runtime Components
  • 6.1. Console Printer Component
  • 6.2. Variable Step Component
  • 6.3. Runtime Plugins
• 7. Configuration File Formats
  • 7.1. Legacy Configuration / INTO-CPS Multi-model and coe config File Format