Description
PROFINET (Process Field Network) is an open standard for realtime industrial Ethernet systems in automation technology. It is promoted by the user organization PI (PROFIBUS The ethernet adapter is not used exclusively, it’s still available for all other applications using TCP/IP on this adapter (e.g. CODESYS Visualisation, Web Browser). CODESYS PROFINET Configurator configurator for settings of PROFINET Controller configuration of as slaves (single AR to PROFINET field device) with communications settings configuration of device/module specific parameters, in- and output-mapping status page with detailed view of currently pendig diagnostics and previously received alarms scan dialog with device-import function, online/offline compare, I This ethernet adapter is still be used for other services like CODESYS Communication (with IDE), Web-Server, or other CODESYS Fieldbuses (except EtherCAT). The CODESYS Runtime and the operating system (e.g. firewall) have to be configured correctly. For details, see CODESYS Online Help / Fieldbus Support (https://help.codesys.com/) Feature CODESYS PROFINET Controller (IEC) PROFINET Specification V2.45 Conformance Class B Max. Number of connections 64 (default) – 1024 Max. IO-Data (total) no limit Max. IO-Data (per slave) 1440 input and 1440 byte output Max. acyclic data 16 KB Plattforms / OS (see restrictions) Windows, Linux, VxWorks, WinCE CPU 32/64 Bit Little-/Big-Endian Provider-/Consumer-Status yes Automatic Name Assignment (Device Exchange) yes Topology-Config yes Fast Startup yes MRP-Configuration yes MRP-Role Client, see Dual Port Dual Port yes, see below Shared Device yes Device Access AR yes System Redundancy S2 Dynamic Reconfiguration yes Performance depends on Plattform ( ** see below) tested with 64 frames / ms CODESYS PROFINET Controller (IEC) and Dual-Port Interface: With standard Ethernet Adapter hardware only single port devices are possible, i.e. each PROFINET Controller can handle just one port. (The system itself may have more than one Ethernet adapter, maybe running a PROFINET Device on it). A Dual-Port Controller (e.g. for MRP support or a ‘daisy-chain’) may be implemented with special dual-port (bridge) Ethernet chipsets, but this requires some runtime adaptions by the OEM. Performance CODESYS PROFINET Controller (IEC): The IO performance, i.e. the possible transmitted ethernet frames / ms differs between outstanding (CODESYS Control RTE) and weak (out of the box Win CE). This depends nearly solely on the CODESYS Runtime’s SysEthernet implementation. Of course a system that manages only 8 frames / ms can handle for example 32 slaves – but ‘only’ with an update interval of 4 ms. Examples with 1 ms update rate: Plattform Frames / ms CODESYS Control RTE 64 CODESYS Raspberry Pi SL 8 Programming Interface (API for IEC application) The PROFINET Controller provides a rich API for Profinet related functions and utilities that can be used by the application at runtime. Function Description DCP-Identify (Bus-Scan) Function block ProfinetCommon.DCP_Identify DCP-Set/Get Function block ProfinetCommon.DCP_Set / DCP_Get set / get IP-Address or Stationname Factory Reset Function block ProfinetCommon.DCP_Reset IO-Link – Read / Write IO-Link Parameters with Function block ProfinetCommon.IOL_CALL – Smart Sensor Profile Support with Function Blocks in ProfinetCommon library Status Outputs Implicit Profinet slave function block: xRunning: Connection established xError: Connection aborted / failed xDiagnosis: diagnosis available xModuleDiff: module configuration not matching (wrong or missing). Status Outputs Controller Implicit Profinet Controller function block: xOnline: Profinet Controller is online xBusy: Controller is in startup phase xError: Profinet Controller is in error state xDataValid: All IO-Data of the configured Profinet devices is valid. Dynamic connect/abort Implicit Profinet Controller or slave function block, method SetCommunicationState() Generic access on device- and module-configuration Function block ProfinetCommon.DeviceIterator and SubmoduleIterator Generic API for iterating Slave- or Module Configuration and Status Diagnosis Shadowing Function block ProfinetCommon.DiagnosisBuffer All Diagnosis Data is locally buffered Receive Alarms Function block CommFB.RALARM Acyclic Read/Write Function block CommFB.RDREC / WRREC Direct IO-Data access Function block CommFB.SETIO_PART / GETIO_PART Device-Access AR Function block CommFB.CNCT Reconfigure Function block DED.Reconfigure Enable/Disable modules, slaves or the complete Profinet stack Function block IoDrvProfinetBase.ControllerConfigUtil: Change configured Stationname, Slot / Subslot oder device-settings in application.
