Main Content

Real-Time Execution in Run in Kernel Mode

A higher-performance alternative toConnected IOmode isRun in Kernelmode. In this mode, you use金宝app®Coder™to link generated algorithm code with I/O driver code generated from the I/O blocks. The resulting executable runs in operating system kernel mode on the development computer and exchanges parameter data with Simulink via a shared memory interface.

  • Signal acquisition — You can capture and display signals from your real-time application while it is running. Signal data is retrieved from the real-time application and displayed in the same SimulinkScopeblocks you used for simulating your model.

  • Parameter tuning — You can change parameters in your Simulink block diagram and have the new parameters passed automatically to the real-time application. External mode changes parameters in your real-time application while it is running in real time.

TheRun in Kernelmode executable is fully synchronized with the real-time clock. The main role of Simulink is to read and display simulation results returned from the executable.

Procedures related to real-time execution in run in kernel mode include:

  1. Set Run in Kernel Mode Code Generation Parameters

  2. Prepare Run in Kernel Mode Application

  3. Set Run in Kernel Mode (External Mode) Scope Parameters

  4. Execute Real-Time Application in Run in Kernel Mode by Using Run in Real Time

  5. Execute Real-Time Application in Run in Kernel Mode by Using Step by Step Commands

  6. Execute Real-Time Application with S-Functions in Run in Kernel Mode

Note

Use a fixed-step solver inRun in Kernelmode.

Image of external mode simulation architecture

InRun in Kernelmode, the real-time application and the I/O drivers run in the kernel mode process. Using the I/O drivers to communicate with the hardware, the application stores contiguous response data in memory accessible to Simulink until a data buffer is filled. When the buffer is filled, the real-time application continues to run while Simulink transfers the data to the MATLAB®environment through Simulink external mode. Transfer of data is less critical than maintaining deterministic real-time updates at the required sample interval. After model computations are finished, data transfer runs at a lower priority while the process waits for another interrupt to trigger the next model update.

Data captured within one buffer is contiguous. When a buffer of data has been transferred, it is immediately plotted in a SimulinkScopeblock. The data can also be saved directly to a MAT-file using the data archiving feature of the Simulink external mode.

With data archiving, each buffer of data can be saved to its own MAT-file. The MAT-file names can be automatically incremented, allowing you to capture and automatically store many data buffers. Although points within a buffer are contiguous, the time required to transfer data back to Simulink pauses data collection until the entire buffer has been transferred. This pause can result in lost sample points between data buffers.

Related Topics

金宝app桌面实时仿真软件Documentation

金宝app

Try MATLAB, Simulink, and Other Products

Get trial now