CM589-PNIO / CM589-PNIO-4 - PROFINET IO Device Communication Module

The configuration of the CM589-PNIO PROFINET IO device module has to be done in the following steps:

Note

Configuration procedure for CM589-PNIO and CM580-PNIO-4 are basically the same. Thus this description refers to CM589-PNIO only. Differences between CM589-PNIO and CM589-PNIO-4 will be highlighted explicitly if necessary!

Parameterization of the AC500 communication module interface

For connecting a PLC as PROFINET IO device, plug CM589-PNIO / CM589-PNIO-4 at the Extension_Bus node.

Double-click on CM589-PNIO to open the CM589-PNIO configuration in the editor window.

The following parameters are available:

Parameter

Default

value

 Value Meaning
Run on config fault No No In case of a configuration error, the user program is not started.
Yes The user program is started even in case of configuration error.
Min update time 10 0…20000 Update time of Inputs and Outputs in [ms].

Parameterization of the PROFINET IO device protocol stack

PROFINET IO device protocol does not need user configuration. All needed parameters are set automatically by Automation Builder. Double-click on PROFINET IO device in tree view will show the parameter set in tab PROFINET IO device parameters. The parameters are displayed just for information and in read-only mode.

../_images/dbba68e332e54ea10a317f3417e00605

Note

  • Station name: the default name is displayed. The real name used on acting at the field bus is combined out of this default name and the used setting of the rotary switches at the CM589 module (cm589-pnio-00, 00 will be replaced by rotary switch value) or the name set via PROFINET set name service.
  • Parameter IP address, Subnet Mask, Default Gateway: the default values are displayed here. These values are not used as communication settings. PROFINET IO controller supplies the IO devices with IP settings on communication establishing.

Configuring PROFINET IO device module structure

CM589-PNIO provides I/O data as modules with different data types and directions. Create an application specific I/O structure by compiling an appropriate combination of modules.

To assign I/O modules to PROFINET-IO-device node open Add Object dialog.

../_images/2d7da95e32eeafa00a317f3465963362

The maximum image size available for I/O data depends on CM589-PNIO modules FW revision (see Technical Data: CM589-PNIO(-4) CM589-PNIO / CM589-PNIO-4 - PROFINET IO Device Communication Module how to calculate number of I/O data occupied by certain configuration.

Parameterization of the PROFINET IO device modules

PROFINET-IO-device modules do not need user configuration. All needed parameters are set automatically by Automation Builder. Double-click on a module node shows the parameter set just for information. This parameter set is identical for all module types and is displayed in read-only mode.

../_images/11e57864330487760a317f3412f68fef

Note

  • API: shows the API which is used by the CM589-PNIO modules. As API 0 is supported only CM589-PNIO modules do not provide configuration capabilities for this parameter
  • Slot number, Sub-Slot-Number, Offset in DPM, inputs/outputs: will be set to default values on inserting a module. On creating configuration data Automation Builder calculates real values and overwrites the defaults
  • Offset IOPS provider/consumer: not used and set to 0 values

Calculating size of I/O data

PROFINET defines IO data and status information to be exchanged between IO controller and IO device. The status information is called Provider Status and Consumer Status. Both (IO data and status information) have to be considered on calculating allocated memory in input and output image.

  • The number of status bytes depends on the type of module used.
  • The different types of modules input, output and in/output have to be considered different.
  • Some status bytes are reserved for predefined submodules have to be considered additionally.

A configured IO module allocates memory space at the corresponding IO image for data and status bytes. And additionally memory is allocated at the opposite directions IO image to store further status bytes. E.g. an input module allocates memory at the input image but additionally it allocates one byte for status at the output image. Summarized size of input and output data and status has to fit to the corresponding image.

See following table for an overview of IO module types and corresponding status bytes:

Module Type Input Data Output data
Inputs Provider Status Inputs Consumer Status Outputs Outputs Provider Status Outputs Consumer Status Inputs
Reserved 0 Input Bytes 4 Bytes 0 Bytes 0 Bytes 0 Bytes 4 Bytes

Input Module

(e.g 4 Byte Input)

 n Input Bytes 1 Byte 0 Bytes 0 Bytes 0 Bytes 1 Byte
Output Module 0 Input Bytes 0 Bytes 1 Byte n Output Bytes 1 Byte 0 Bytes
Input/Output Module n Input Bytes 1 Byte 1 Byte n Output Bytes 1 Byte 1 Byte

Following expressions calculate allocated sizes of input and output data:

Size Input = Input + Status + 4 bytes (reserved status)
Size Output = Output + Status + 4 bytes (reserved status)
  • Input = summarized number input bytes all modules
  • Output = summarized number output bytes all modules
  • Status = count input modules + count output modules + 2 * count input/output modules

Mapping of the I/Os

Double-click on the desired PROFINET-IO-device module object in the device tree to show current I/O mappings connected to this module.

See chapter Symbolic Names for Variables, Inputs and Outputs Symbolic Names for Variables, Inputs and Outputs for further details on mapping inputs and outputs.

Configuration specific to CM589-PNIO-4

CM589-PNIO-4 adds PROFINETShared Device feature to already described CM589-PNIO device functionality. Thus CM589-PNIO-4 is able to communicate to 4 different PROFINET IO controllers in parallel.

Shared device usage of a CM589-PNIO-4 does not need to be considered on doing the configuration of the CM589-PNIO-4 coupler device itself. It has to be considered only on doing the configuration of CM589-PNIO-4 as child to the CM579-PNIO IO controller. See Configuration of PROFINET Shared Device Functionality for details.