dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference: User Interface dl-breadcrumb-item__separatorMenu Commands dl-breadcrumb-item__separatorOnline dl-breadcrumb-item__separatorCommand: Simulation dl-breadcrumb-item__separatorDifferences between simulation mode and operation with a physical controller
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Differences between simulation mode and operation with a physical controller dl-permalink__symbolPermalink

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

For more information, see: ⮫ “Testing in Simulation Mode ”