Quick Start | Data Logger

The Data Logger's intended use is to capture signals and triggers and to record them to data files for post-simulation analysis. It records multiple signals' evolution during the simulation in order to give users the ability to validate their design in a post-processing phase.

The supported format for the log files is OPREC (.oprec). Additionally, the DataLogger captures transient phenomena and anomalies when they occur, which provides options to trigger the acquisition of data.

Here are some of its advantages over the standard acquisition with ScopeView:

• Usable with either triggered or non-triggered acquisition
• Less intrusive on real-time simulation performance
• Capable of capturing signals with trigger conditions that occur at any moment during the simulation, including the very first calculation steps
• Capable of logging multiple signals' acquisition within the same model and within a multi-model simulation scope
• Handles multiple signal groups and multiple acquisition rates based on ratios of the simulation step
• Parametrizable log file characteristics (Maximum Size, File Naming, etc.) and log duration (seconds, minutes, hours, etc.)
• Provides clear log files naming, including models’ tags, subsystems’ tags, date and time tags for ease of management.

• Step 1: Accessing the Data Logger Configuration
• Step 4: Controlling the Data Logger During Simulation
• Step 5: Analyzing Results with ScopeView
• Step 3: Assigning Signals to the DataLogger
• Step 2: Configuring the Data Logger