CAN Integration in an Existing RT-LAB I/O Model

Overview

A practical RT-LAB example showing how to integrate CAN into an existing model and avoid common OpComm and I/O setup issues.

This example is intentionally practical. It is based on a real integration workflow and helps users extend an existing RT-LAB I/O project with CAN support. For community seeding, this is valuable because not every useful post needs to be a hero demo model; practical setup content often drives stronger engagement.

Real users often search for setup guidance before they search for flagship demos. A CAN integration example gives the community practical value from day one and helps establish RT-LAB as not only powerful, but usable.

Key Features

  • Adding CAN communication into an existing RT-LAB project
  • Understanding how to structure subsystems and help blocks
  • Avoiding communication conflicts related to OpComm usage
  • Helping new users move faster on real lab integration tasks

Getting Started

  1. Create or open the base RT-LAB project.
  2. Add the appropriate I/O interface and board configuration.
  3. Import the CAN example subsystem structure.
  4. Connect the CAN subsystem through the main project communication architecture.

Model Specifications

Parameter Value
Product RT-LAB
Software version RT-LAB 2024.4+
Model file Coming soon

Detailed specifications (time step, hardware, dependencies, license, known limitations, compatible hardware) to be confirmed.

Downloads

The downloadable model package is coming soon.

CAN_IO.zip (403.8 KB)

Which communication setup gives you the most trouble in early HIL integration: CAN, Modbus, IEC 61850, or custom I/O mapping?