Tutorials 4 Tutorials 4.1 Einfьhrung 4.1.1 Profiles supported by the TwinCAT Simulation Manager Two different configuration profiles are supported by the TwinCAT Simulation Manager (see Table 1). Table 1: Profiles The original profile is handled implicitly as the TwinCAT Systems configuration imported to the TwinCAT Simulation Manager. The Simulation profile is stored as a delta of Simulation actions referring to the Original profile. The original simulation mode switchover affects various components of the TwinCAT configuration:
Replacement of IO by the simulation PLC (see Mappings of I/Os [ } 14] ) Replacement of physically present axes by simulation axes (see Simulation axes [ } 16] ) Deactivation of devices (see Deactivating devices [ } 16] ) Mappings of I/Os Mappings of I/Os The TwinCAT Simulation Manager follows the concept that non-available physical devices are substituted by one or more simulation PLCs. Device Signals that are transferred via IO-Hardware usually source or end up in PLC Symbols. In TwinCAT the binding between IO Hardware and PLC are realized by so called IO- Mappings.
Via its Simulation profile the TwinCAT Simulation Manager is capable to break up or probe the connections to this IO-Hardware and redirect them to a dedicated Simulation PLC. These simulation PLCs can run locally (Local-Simulation) or remotly (Remote-Simulation). The TwinCAT Simulation Manager internally chooses transparently from the user the appropriate data exchange protocol for symbol value mappings between the 'Original'- and 'Simulation-PLCs'. The data exchange occurs in realtime, so that the simulation is capable to emulate the machine characteristics (specifically the signal timing) to the highest degree possible. Table 2: Simulation types Various kinds of mappings are possible:
TS1110 14 Version: 1.0 Profile Description Original All Devices and Hardware enabled (original configuration) Remote System is set to simulation mode. Not used or existant hardware is disconnected from the system and optionally replaced by simulation functionality. Simulation Type Description Local The Data-Transfer protocol is realized as TwinCAT internal IO-Mappings because they have the least overhead. The data exchange in this scenario is realized as IO- Driver synchronized Process-Image memory copy operations. The Realtime characteristics are directly derived from the Realtime characteristics of the TwinCAT Realtime system.
Remote The data exchange is realized with EtherCAT Network variables (Master-Master communciation). Because the Ethernet-Network is involved, the overhead is higher. The Realtime characteristics are derived from the capabilites of the EtherCAT Master-Master communication. Type of mapping Description Observing Observation of an I/O in simulation mode.