dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorCODESYS Development Systemdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference, User Interfacedl-breadcrumb-item__separatorMenu Commandsdl-breadcrumb-item__separatorMenu 'Online'dl-breadcrumb-item__separatorCommand 'Simulation
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Command 'Simulationdl-permalink__symbolPermalink

Function: The command switches the development system to simulation mode.

Call: Menu bar: “Online”

In simulation mode, you can start and debug the active application an on a simulated target device. A physical target device is not necessary for testing the online behavior of an application. When logging in for the first time, you are prompted whether the application should be created or loaded. For a simulated device, you do not have to configure the communication settings. In CODESYS simulation mode, the entry of the controller in the device tree is displayed in italics.

NOTICE

NOTICE
NOTICE
NOTICE

NOTICE

NOTICE

No C code for simulation mode

In simulation mode, C code is not generated and loaded to the runtime system. To simulate the code contained in the C modules anyway, you can implement it for this purpose in the respective IEC objects of the C code module.

After successful login, the red triangle symbol (_cds_icon_simulation_mode_connected) in the device tree indicates simulation mode. You can use the corresponding online commands for testing the application.

To switch off simulation mode, log out of the controller and execute the “Simulation” command again.

The command affects the active application only.

Differences between simulation mode and operation with a physical controller

Simulation

Physical Controller

Real-time behavior / multicore

  • Runs in the CODESYS process with normal priority

  • Single-core

    --> Worse real-time behavior

  • Real-time operating system

  • Single-core or multicore

Architecture scope

  • Simulation 64-bit (depends on the CODESYS installation): --> Possible compile error in the IEC application if the application has been previously run only as 32-bit (for example, use of ‎DWORD‎ as POINTER)

  • Controller 32-bit

FPU (rounding error)

  • Uses FPU of the PC

  • Different configuration of the FPU exceptions

  • Uses FPU of the controller or FPU emulation

  • Different configuration of the FPU exceptions

Handling of exceptions

  • Exception handling of the Windows Runtime System

  • Exception handling of the controller

External libraries (Cmp/Sys/CAA/OEM/…)

  • Only a few external Cmp/SysLibs are physically available. As compared to embedded, more SysLibs could also be available.

  • Other implementation/behavior of the SysLibs (Windows in contrast to the OS of the controller)

  • "Unresolved Reference error“ on download is ignored. The application can still be downloaded to the controller and started. If the missing functions are actually called, they return nonsense values.

    Therefore, an IEC implementation can also be specified for external POUs. This substitute IEC code is then executed in the simulation.

  • "Unresolved Reference error" on download when external libraries do not exist in the controller

I/O drivers

  • I/O configuration is generated but not evaluated.

  • Fieldbus stacks are not evaluated.

  • I/O channels are not updated and no bus telegrams are sent.

  • Mostly no restriction, but depends on the capabilities of the controller

SoftMotion drivers

  • All SoftMotion axes are set to virtual and therefore simulated.

  • Mostly no restriction, but depends on the capabilities of the controller