You are on page 1of 186

Installing and operating the ILC 191 ME/AN

and ILC 191 ME/INC Inline controllers


User manual
User manual
Installing and operating the ILC 191 ME/AN and ILC 191 ME/INC
Inline controllers

UM EN ILC 191 ME/X, Revision 06 2023-02-03

This user manual is valid for:

Designation As of version (HW) As of version (FW) Order No.


ILC 191 ME/AN 01 4.0x 2700074
ILC 191 ME/INC 01 4.0x 2700075
8607_en_06

Phoenix Contact GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany


phoenixcontact.com
Please observe the following notes
User group of this manual
The use of products described in this manual is oriented exclusively to:
– Qualified electricians or persons instructed by them, who are familiar with applicable
standards and other regulations regarding electrical engineering and, in particular, the
relevant safety concepts.
– Qualified application programmers and software engineers, who are familiar with the
safety concepts of automation technology and applicable standards.
Explanation of symbols used and signal words

This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety measures that follow this symbol to avoid possible in-
jury or death.
There are three different categories of personal injury that are indicated with a
signal word.
DANGER This indicates a hazardous situation which, if not avoided, will re-
sult in death or serious injury.
WARNING This indicates a hazardous situation which, if not avoided, could
result in death or serious injury.
CAUTION This indicates a hazardous situation which, if not avoided, could
result in minor or moderate injury.
This symbol together with the signal word NOTE and the accompanying text
alert the reader to a situation which may cause damage or malfunction to the
device, hardware/software, or surrounding property.
This symbol and the accompanying text provide the reader with additional in-
formation or refer to detailed sources of information.

8607_en_06 Phoenix Contact 1 / 185


ILC 191 ME/X

Table of contents
1 Foreword ....................................................................................................................................9
1.1 Purpose of this user manual .................................................................................. 9
1.2 Hardware and software requirements ............................................................... 9
1.3 General safety notes............................................................................................ 10
1.4 Intended use........................................................................................................ 10
1.5 Disposal .............................................................................................................. 11

2 Description of the Inline controller.............................................................................................12


2.1 General description of the Inline controller........................................................... 12
2.2 Possible fields of application of the Inline controller............................................. 14
2.2.1 Controller as a distributed controller of an Inline station ...................... 14
2.2.2 The Inline controller for position control ............................................... 15
2.2.3 The Inline controller as a PROFINET device in a PROFINET network 16
2.2.4 Applicative system redundancy using the Inline controller .................. 17
2.3 Unpacking the Inline controller ............................................................................ 18
2.4 Connection and operating elements .................................................................... 19
2.5 Diagnostics and status indicators ........................................................................ 21
2.6 Mode selector switch........................................................................................... 25
2.7 Reset button (concealed) .................................................................................... 26
2.8 Parameterization memory.................................................................................... 26
2.8.1 Inserting/removing the parameterization memory ................................ 27
2.9 Internal basic circuit diagram ............................................................................... 28
2.10 Mounting and removing the Inline controller ....................................................... 30
2.11 Communication paths.......................................................................................... 34
2.11.1 Ethernet ............................................................................................... 35
2.11.2 Serial PRG interface (mini-DIN socket) ................................................ 36
2.12 INTERBUS ................................................................................................. 38
2.12.1 Local bus ............................................................................................. 38
2.12.2 Remote bus ......................................................................................... 38
2.13 Power supply....................................................................................................... 39
2.13.1 Sizing of the power supply ................................................................... 39
2.13.2 Connecting the power supplies ............................................................ 40
2.13.3 24 V segment supply/24 V main supply ............................................... 43
2.13.4 24 V segment supply ........................................................................... 43
2.13.5 24 V main voltage ............................................................................... 43
2.13.6 24 V ILC supply ................................................................................... 43
2.13.7 Jumpers .............................................................................................. 43
2.14 Digital outputs...................................................................................................... 44
2.15 Digital inputs........................................................................................................ 46

5 / 185 Phoenix Contact 8607_en_06


Table of contents

2.16 Pulse direction outputs and PWM function .......................................................... 47


2.17 RS-485/RS-422 communication interface ........................................................... 48
2.18 Analog inputs....................................................................................................... 51
2.19 Analog outputs .................................................................................................... 53
2.20 Counter inputs ..................................................................................................... 54
2.21 Incremental encoder inputs ................................................................................. 55

3 The Inline controller under PC Worx/PC Worx Express ............................................................57


3.1 Software version.................................................................................................. 57
3.2 Creating a new project......................................................................................... 58
3.3 Assigning the IP address for the controller .......................................................... 59
3.3.1 Discovery and basic Configuration Protocol (DCP) .............................. 59
3.3.2 BootP server ........................................................................................ 60
3.4 The Inline controller as a PROFINET device ....................................................... 63
3.5 Setting the realtime clock under PC Worx Express.............................................. 69
3.6 Download Changes ............................................................................................. 69
3.7 Functions of the plug-in parameterization memory (SD card).............................. 70
3.7.1 Main memory ....................................................................................... 70
3.7.2 Additional memory .............................................................................. 72
SD card as the memory for log files 74
3.8 Parameterization memory and Internet Explorer.................................................. 76
3.8.1 Internet Explorer FTP functionality ....................................................... 77
3.8.2 Activating/deactivating the FTP server ................................................. 78
3.8.3 Restricting FTP access ........................................................................ 79
3.8.4 Activating/deactivating the HTTP server .............................................. 82
3.8.5 Using the Hypertext Transfer Protocol Secure (HTTPS) ...................... 83
3.9 Sending e-mails securely .................................................................................... 83
3.10 Activating/deactivating specific ports................................................................... 84
3.11 Activating/deactivating the journaling function..................................................... 85
3.12 Activating/deactivating the MRP client function ................................................... 86
3.13 Function blocks for handling files on the parameterization memory..................... 87
3.14 Function blocks for Ethernet communication....................................................... 88
3.15 Function blocks for PCP communication ............................................................. 88
3.16 Function blocks for pulse width modulation ......................................................... 89
3.17 Function blocks for RS-232 communication ........................................................ 93
3.17.1 RS232_INIT function block .................................................................. 93
3.17.2 RS232_SEND function block ............................................................... 95
3.17.3 RS232_RECEIVE function block ......................................................... 97
3.18 Function blocks for RS-485/RS-422 communication ........................................... 99
3.18.1 RS485_422_INIT function block .......................................................... 99

8607_en_06 Phoenix Contact 6 / 185


ILC 191 ME/X

3.18.2 RS485_422_SEND function block ..................................................... 101


3.18.3 RS485_422_RECEIVE function block ............................................... 103
3.19 Function blocks for counter inputs ..................................................................... 105
3.19.1 Counter operating modes .................................................................. 109
3.20 Function blocks for incremental encoder inputs................................................. 112
3.20.1 Counter operating modes for incremental encoders .......................... 114
3.21 Alignment .......................................................................................................... 116

4 System variables and status information.................................................................................119


4.1 General notes .................................................................................................... 119
4.2 Status register for local digital inputs and outputs.............................................. 119
4.3 Status register for local analog inputs and outputs ............................................ 120
4.3.1 Representation of measured values for the local analog inputs ......... 121
4.3.2 Representation of output values for the local analog outputs ............. 122
4.4 Status register for counter inputs ....................................................................... 123
4.5 Status register for incremental encoder inputs................................................... 123
4.6 Diagnostic status register .................................................................................. 124
4.7 Diagnostic parameter register............................................................................ 125
4.8 PROFINET register............................................................................................ 126
4.9 IEC 61131 runtime system................................................................................. 127
4.10 Control processor .............................................................................................. 128
4.11 Power storage, realtime clock............................................................................ 128
4.12 Power supplies .................................................................................................. 128
4.13 Mode selector switch......................................................................................... 129
4.14 System time....................................................................................................... 129

5 Easy Motion function block library ..........................................................................................130


5.1 Characteristics of one-dimensional positioning axes......................................... 132
5.2 Homing (dynamic homing)................................................................................. 134
5.3 Starting up the Easy Motion function block library ............................................. 137
5.4 Function blocks of the Easy Motion function block library.................................. 138
5.4.1 M191_DRV1 and M191_DRV2 function blocks ................................. 139
5.4.2 M191_Power function block ............................................................... 143
5.4.3 M191_HomePARA function block ..................................................... 145
5.4.4 M191_Home function block ............................................................... 147
5.4.5 M191_MoveAbsolute function block .................................................. 149
5.4.6 M191_MoveRelative function block ................................................... 151
5.4.7 M191_MoveVelocity function block ................................................... 153
5.4.8 M191_Reset function block ............................................................... 154
5.4.9 M191_Stop function block ................................................................. 155

7 / 185 Phoenix Contact 8607_en_06


Table of contents

5.5 Simple application example............................................................................... 158

6 Technical data and ordering data ...........................................................................................159


6.1 Technical data ................................................................................................... 159
6.1.1 Tolerance values for the analog inputs ............................................... 167
6.1.2 Tolerance values for the analog outputs ............................................ 168
6.2 Ordering data .................................................................................................... 170
6.2.1 Modules ............................................................................................. 170
6.2.2 Accessories ....................................................................................... 170
6.2.3 Software ............................................................................................. 170
6.2.4 Documentation ................................................................................... 170

A Appendix: Service and maintenance ......................................................................................171


A1 Error causes and remedies............................................................................... 171
A2 Updating the Inline controller firmware ............................................................. 171
A3 Connecting unshielded cables ......................................................................... 172
A4 Connecting the shield....................................................................................... 173

B Appendixes.............................................................................................................................174
B1 List of figures .................................................................................................... 174
B2 List of tables ..................................................................................................... 178
B3 Index................................................................................................................. 181

8607_en_06 Phoenix Contact 8 / 185


ILC 191 ME/X

1 Foreword

1.1 Purpose of this user manual


This user manual is intended to help you start up and operate the ILC 191 ME/AN and
ILC 191 ME/INC Inline controllers.

1.2 Hardware and software requirements


HW/SW Description
Inline controller ILC 191 ME/AN ILC 191 ME/INC
Parameterization For ordering data, see Section For ordering data, see Section
memory, plug-in “Accessories” on page 170 “Accessories” on page 170
Ethernet cable Ethernet cable for connecting the Inline controller to a PC
Connecting cable Connecting cable for connecting the Inline controller to a PC (RS-
232, optional)
Automation software versions (Service Pack = SP)
PC Worx ≥ 6.30 *
PC Worx Express ≥ 6.30 *
* Part of the AUTOMATIONWORX Software Suite 2013 1.80

For the ordering data for hardware, software, and additional documentation, please refer
to Section “Technical data and ordering data” on page 159.

PROFINET device function


The PROFINET device function of the controllers is not supported by the
PC Worx Express software.

9 / 185 Phoenix Contact 8607_en_06


Foreword

1.3 General safety notes


Observe the country-specific installation, safety, and accident prevention regulations.
During startup and maintenance work, proceed in accordance with the five safety rules of
DIN EN 50110-1. In general, the rules should be observed in the specified order:
– Disconnect safely
– Ensure power cannot be switched on again
– Verify safe isolation from the supply
– Ground and short circuit
– Cover or safeguard adjacent live parts
Once the work is complete, perform the above steps again in reverse order.

NOTE:
The IP20 degree of protection (IEC 60529/EN 60529) of the device is intended for use in
a clean and dry environment. Do not subject the device to mechanical and/or thermal
loads that exceed the specified limits.

NOTE: Risk of unauthorized network access


Connecting devices to a network via Ethernet always entails the risk of unauthorized
access to the network.
Therefore, please check your application for any option of deactivating active
communication channels (for instance SNMP, FTP, BootP, DCP, etc.), or setting
passwords to prevent third parties from unauthorizedly accessing the controller and
modifying the system.
With regard to the controller's communication interfaces, we recommend not to use the
controller in safety-critical applications unless using additional security devices.
So, please take additional protective measures according to the IT security requirements
and the standards applicable to your application (for instance virtual networks (VPN) for
remote maintenance access, firewalls, etc.) for protection against unauthorized network
access.
You shall indemnify Phoenix Contact GmbH & Co. KG, Flachsmarktstraße 8, 32825
Blomberg, Germany, as well as any affiliated company (all generally termed
“Phoenix Contact” in the following) in accordance with §§ 15 ff. AktG (German Stock
Corporation Law) against all third-party claims upon our first demand, which may result
from use that does not comply with its intended purpose.
For the protection of networks for remote maintenance via VPN, Phoenix Contact offers
the mGuard product series security devices which you can find described in the latest
Phoenix Contact catalog (phoenixcontact.net/products).

1.4 Intended use


The Inline controller is a modular small-scale controller that can be used for smaller and
medium-sized applications. The device has IP20 protection and is designed for use in
closed control cabinets or control boxes (terminal boxes) with IP54 protection or higher.
The device is designed for use in industrial environments.

8607_en_06 Phoenix Contact 10 / 185


ILC 191 ME/X

1.5 Disposal

The symbol with the crossed-out trash can indicates that this item must be collected and
disposed of separately. Phoenix Contact or our service partners will take the item back for
free disposal. For information on the available disposal options, visit phoenixcontact.com.
Delete personal data before returning the item.

11 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2 Description of the Inline controller

2.1 General description of the Inline controller


The Inline controller is a modular small-scale controller with integrated Ethernet and
INTERBUS connections.

The ILC 191 ME/AN and ILC 191 ME/INC Inline controllers have the same appearance
and numerous identical functions.
The main differences between the Inline controllers are connectors 6 (ILC 191 ME/AN:
analog inputs, ILC 191 ME/INC: counter inputs) and 7 (ILC 191 ME/AN: analog outputs,
ILC 191 ME/INC: incremental encoder inputs), see from page 51 onwards.
In the following, the term Inline controller is used in general. Differences between the
controllers are mentioned explicitly where necessary.

IEC 61131 controller The Inline controller is consistently configured and programmed according to IEC 61131
performance using the PC Worx automation software. PC Worx can be operated via the network
(Ethernet). The powerful processor can be programmed in all five IEC 61131 programming
languages and ensures quick control task processing.

Integrated Ethernet The integrated Ethernet connection (via twisted pair cable) ensures Ethernet connectivity.
connection Throughout the Ethernet network, the Inline controller can be accessed via TCP/IP or
UDP/IP. The Inline controller has two fully implemented Ethernet connections, which are
switched inside the device.
Integrated communication functions enable direct and effective data exchange via
Ethernet. The Ethernet network provides universal options for communicating with the Inline
controller. Using the IP_USEND and IP_URCV communication blocks, information, e.g.,
necessary coupling variables, can be exchanged between Inline controllers via Ethernet.
This enables distributed, modular automation solutions to be configured.
The existing IEC 61131-5 blocks have therefore been extended to include a transparent
TCP/IP mode and a transparent UDP/IP mode.
When using the AX OPC server provided in the AUTOMATIONWORX Software Suite
Version 1.30 or later, Inline controller data is available in the Ethernet network in a
standardized format and can be used for the different visualization packages.

PROFINET device The PROFINET protocol can be used via the Ethernet interfaces of the Inline controller. In
functionality this case, the Inline controller can be used as a PROFINET device.

For information on how to configure the Inline controller as a PROFINET device in the
PC Worx software, please refer to Section “The Inline controller as a PROFINET device”
on page 63.

Modbus functionality The Modbus/TCP (UDP) communication protocol can be used via the Ethernet interfaces
of the Inline controller. The Inline controller can be used as a Modbus/TCP client and/or as
a Modbus/TCP server (from firmware version 4.42 or later and from
AUTOMATIONWORX Software Suite Version 1.82 AddOn V1).
For additional information, please refer to the AH EN MODBUS/TCP application note.

8607_en_06 Phoenix Contact 12 / 185


ILC 191 ME/X

MRP The Media Redundancy Protocol (MRP) can be used via the Ethernet interfaces of the Inline
controller. The controller supports the MRP client function, which can be enabled or
disabled via PC Worx as an option. This function is disabled by default. If the function is
enabled, it remains enabled after the supply voltage is switched off and on. If the controller
has been reset to the delivery state, the MRP client function will also be disabled again. In
a ring with Media Redundancy Protocol, maximum switch-over times of up to 200 ms can
be expected.

Integrated INTERBUS An Inline local bus as well as an INTERBUS remote bus can be connected via the
connection INTERBUS connection. In this way you can create a complete INTERBUS system
(maximum of 4 remote bus levels) using the Inline controller as a distributed controller.
The I/O level is connected to the Inline controller via INTERBUS.

RS-232 interface This interface can be used to either assign the IP address of the Inline controller and to
access the controller using the Diag+ diagnostic tool or to communicate with serial I/O
devices via function blocks.

The Inline controller cannot be programmed via the RS-232 interface.

RS-485/RS-422 interface An RS-485 network with several I/O devices can be created via the RS-485/RS-422
interface. The interface is operated in PC Worx via the RS485_422_INIT,
RS485_422_RECEIVE, and RS485_422_SEND function blocks, see Section “Function
blocks for RS-485/RS-422 communication” on page 99.

Parameterization The Inline controller can be operated using a plug-in parameterization memory in the form
memory/SD card of an SD card. This memory can be used to save programs and configurations which belong
to your project.
The plug-in parameterization memory is optional and is not required in order to operate the
Inline controller.

The parameterization memory is not supplied as standard with the Inline controller.
Only use a parameterization memory provided by Phoenix Contact (for ordering data, see
Section “Accessories” on page 170).

NOTE: Parameterization memory (SD card) – formatting note


The SD card is already formatted and is intended for use with Phoenix Contact devices.
Make sure that the SD card is not reformatted.

13 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.2 Possible fields of application of the Inline


controller

2.2.1 Controller as a distributed controller of an Inline station


The Inline controller can be used as a distributed controller of an Inline station which is
connected to an Ethernet system. A single Inline local bus (Figure 2-1) as well as a complete
INTERBUS system with a maximum of 4 remote bus levels (Figure 2-2) can be connected
to the Inline controller.

Inline local bus


D-32825 Blomberg
ILC 191 ME/AN RDY FAIL BSA PF
Order-No.: 2700074 FR E I1 I2 UA O1 O2
HW/FW: 00/100 UL FF I3 I4
MAC Addr. 8Block: US BF Q1 Q2 I5 I6 P1 P2
xx. xx. xx. xx
UM SF Q3 Q4 I7 I8 D1 D2 TxD RxD
AUTOMATIONWORX
DI
PWM

AI
PWR
DO

A0
RS485/422

X1
MRESET
RESET
STOP

PWR
Slot Voltage
RUN/PROG
PRG PWR 24 V

LNK DO 24 V

DI 24 V
X2.1

PWM 5V
ACT
RS485/422

LNK
AI 0 - 10 V

X2.2 A0 0 - 10 V

ACT

Ethernet
Figure 2-1 Connected Inline local bus

Remote bus levels


Inline local bus

D-32825 Blomberg
ILC 191 ME/AN RDY FAIL BSA PF
Order-No.: 2700074 FR E I1 I2 UA O1 O2
HW/FW: 00/100 UL FF I3 I4
MAC Addr. 8Block: US BF Q1 Q2 I5 I6 P1 P2
xx. xx. xx. xx
UM SF Q3 Q4 I7 I8 D1 D2 TxD RxD
AUTOMATIONWORX
PWM

AI
DI

A0
PWR
DO

RS485/422

1.
X1
MRESET
RESET
STOP

PWR
Slot Voltage
RUN/PROG
PRG PWR 24 V

LNK DO 24 V

DI 24 V
X2.1

PWM 5V
ACT
RS485/422

LNK
AI 0 - 10 V

X2.2 A0 0 - 10 V

ACT

2.

INTERBUS

Remote bus levels


3.

INTERBUS

4.

INTERBUS

Figure 2-2 Remote bus levels

8607_en_06 Phoenix Contact 14 / 185


ILC 191 ME/X

2.2.2 The Inline controller for position control


The Inline controller offers Ethernet, RS-485, and pulse direction interfaces. This means
that electric motors can be driven via frequency inverters or other power electronics. Axis
limit switches and home position switches are connected directly to the Inline controller.
Analog inputs (ILC 191 ME/AN) are available for the position detection of a tool using a laser
measuring system, for example. The ILC 191 ME/INC has digital inputs for incremental
encoders.

ILC 191 ME/AN ILC 191 ME/AN


Order-No.: 2700074 Order-No.: 2700074
RDY FAIL BSA PF RDY FAIL BSA PF
HW/FW: 00/100 HW/FW: 00/100
MAC Addr. 8Block: FR E I1 I2 S1 S5 O1 O2 MAC Addr. 8Block: FR E I1 I2 S1 S5 O1 O2

xx. xx. xx. xx UL FF I3 I4


xx. xx. xx. xx UL FF I3 I4

AUTOMATIONWORX US SF Q1 Q2 I5 I6 P1 P2
AUTOMATIONWORX US SF Q1 Q2 I5 I6 P1 P2

UM SF Q3 Q4 I7 I8 D1 D2 TxD RxD UM SF Q3 Q4 I7 I8 D1 D2 TxD RxD

X1 X1

MRESET MRESET
RESET RESET

STOP

STOP
RUN/PROG PWR RUN/PROG PWR
Nr. Function Voltage Nr. Function Voltage
PRG PRG

X1 Power In 24 V X1 Power In 24 V
ACT ACT
X2 dig. Out 24 V X2 dig. Out 24 V
X2.1 X2.1
X3 dig. In 24 V X3 dig. In 24 V

LNK LNK
X4 PWM / PTO 5V X4 PWM / PTO 5V

X5 RS485/422 X5 RS485/422
ACT ACT
X6 analog In 0 - 10 V X6 analog In 0 - 10 V
X2.2 X2.2
X7 analog Out 0 - 10 V X7 analog Out 0 - 10 V
LNK LNK

X20 IN X21 OUT


PHOENIX CONTACT
GmbH Co. KG
Flachsmarktstrasse 8
D-32825 Blomberg
info@phoenixcontact.com

D R1

TR

ESC Enter

X10 X11
24 V GND DI0 DI1 DI2 DI3 DI4 AO AI COM NC NO

0 10 20 30 40 50 60
Figure 2-3 The Inline controller for position control

15 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.2.3 The Inline controller as a PROFINET device in a PROFINET


network
The following figure shows the example of an ILC 191 ME/AN as a PROFINET device in a
PROFINET network.

A RUN/PROG

STP

MRESET
DISPLAY

LNK LNK I/O


RFC 470 PN 3TX
L AN1.1 LAN1. 2
Ord.No.2916600
ACT ACT

LNK

USB LAN2

24VDC
+

REMOTE
-

PROFINET

PROFINET
C D-32825 Blomberg
ILC 191 ME/AN
Order-No.: 2700074 FR E I1 I2
RDY FAIL BSA
UA
PF
O1 O2
HW/FW: 00/100 UL FF I3 I4
MAC Addr. 8Block: US BF Q1 Q2 I5 I6 P1 P2
xx. xx. xx. xx
UM SF Q3 Q4 I7 I8 D1 D2 TxD RxD
AUTOMATIONWORX
DI
PWM

AI
PWR
DO

A0
RS485/422

X1
MRESET
RESET
STOP

PWR
Slot Voltage
RUN/PROG
PRG PWR 24 V

LNK DO 24 V

DI 24 V
X2.1

PWM 5V
ACT
RS485/422

LNK
AI 0 - 10 V

X2.2 A0 0 - 10 V

ACT

Figure 2-4 PROFINET device using the ILC 191 ME/AN as an example

Key:
A PROFINET controller (in the example: RFC 470 PN 3TX Remote Field Controller)
B Managed Switch
C PROFINET device (in the example: ILC 191 ME/AN)

For additional information on how to integrate the Inline controller into a PROFINET
network as a PROFINET device, please refer to Section “The Inline controller as a
PROFINET device” on page 63.

8607_en_06 Phoenix Contact 16 / 185


ILC 191 ME/X

2.2.4 Applicative system redundancy using the Inline controller


The following figure shows an example of applicative system redundancy. The example
shows a PROFINET device with control function (ILC 191 ME/AN) that is connected to a
PROFINET network by means of a switch. Identical application programs run on both
higher-level PROFINET controllers. To achieve synchronization, both PROFINET
controllers are connected via an Ethernet connection by means of a switch. PROFINET
controller A operates as primary controller, PROFINET controller B operates as backup
controller.

Controllers with applicative


(programmed) redundancy A RUN/PROG

STP

MRESET
DISPLAY

B RUN/PROG

STP

MRESET
DISPLAY

LNK LNK I/O LNK LNK I/O


RFC 470 PN 3TX RFC 470 PN 3TX
L AN1.1 LAN1. 2 L AN1.1 LAN1. 2
Ord.No.2916600 Ord.No.2916600
ACT

USB
ACT

LNK

LAN2
ETHERNET ETHERNET ACT

USB
ACT

LNK

LAN2

24VDC 24VDC
+ +
REMOTE

REMOTE
- -

Network redundancy with


Media Redundancy Protocol
(MRP) C C
PROFINET

PROFINET devices with


Phoenix Redundancy Layer D D-32825 Blomberg
ILC 191 ME/AN RDY FAIL BSA PF
Order-No.: 2700074 FR E I1 I2 UA O1 O2
HW/FW: 00/100 UL FF I3 I4
MAC Addr. 8Block: US DF Q1 Q2 I5 I6 P1 P2
xx. xx. xx. xx
UM SF Q3 Q4 I7 I8 D1 D2 TxD RxD
AUTOMATIONWORX
DI
PWM

AI
PWR
DO

A0
RS485/422

X1
MRESET
RESET
STOP

PWR
Slot Voltage
RUN/PROG
PRG PWR 24 V

LNK DO 24 V

DI 24 V
X2.1

PWM 5V
ACT
RS485/422

LNK

ETHERNET ACT
X2.2
AI

A0
0 - 10 V

0 - 10 V

PROFINET

Figure 2-5 Applicative system redundancy – example

For additional information on applicative system redundancy, please refer to the


AH EN APPLICATIVE SYSTEM REDUNDANCY application note. This application note
can be downloaded at phoenixcontact.net/products.
A Primary controller (in the example: RFC 470 PN 3TX Remote Field Controller)
B Backup controller (in the example: RFC 470 PN 3TX Remote Field Controller)
C Managed Switches
D PROFINET device with control function (in the example: ILC 191 ME/AN with PROF-
INET device function and Phoenix Redundancy Layer)

17 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.3 Unpacking the Inline controller


The Inline controller is supplied in an ESD bag together with a package slip with installation
instructions. Read the complete package slip carefully before unpacking the Inline
controller.

NOTE: Electrostatic discharge


The Inline controller contains components that can be damaged or destroyed by
electrostatic discharge. When handling the Inline controller, observe the necessary safety
precautions against electrostatic discharge (ESD) according to EN 61340-5-1 and
IEC 61340-5-1.

NOTE:
To avoid possible damage to the Inline controller, unpack and pack the controller in
accordance with the ESD regulations.

8607_en_06 Phoenix Contact 18 / 185


ILC 191 ME/X

2.4 Connection and operating elements


ILC 191 ME/AN

15
PF
O2
O1
BSA
UA
FAIL

1 I2
RDY

P2 TxD
RxD

14
I1 P1
I4 D2
E I3 D1
I6
I5

2
I8
I7
FR Q2
Q1
FF Q4
UL Q3
BF
US
rg SF
mbe UM
Blo N
25 E/A 074

A0
AI
28 M 700

RS485/422
D-3 91

PWM
1 .: 2

DI
ILC r-No /100 ck:

DO
3

PWR
e 00
Ord W: 8Blo
/F r.
HW Add xx ORX
C . W R
MA x. xx ION PW
.x T
xx OMA
T T
AU SE
RE
ET ge
STOP

ES lta
1 MR Vo
X

4 PR
G
RU
N/P
RO
G
Slo

PW

DO
t

24
V
24

24
V

13
K
LN

5
DI

M
5V

12
11
PW
T 22 V
AC 5/4 10
48 0-
RS
V
10
K AI 0-

6
LN
A0
10
AC
T

9
8
7
Figure 2-6 Structure of the ILC 191 ME/AN Inline controller

The Inline controller consists of the following components:


1 Electronics base
2 Slot for the parameterization memory/card holder (SD card)

The SD card is not supplied as standard with the Inline controller.


Please refer to the ordering data in Section “Accessories” on page 170.
3 Reset button
4 Mode selector switch
5 RS-232 interface
6 Ethernet connection
7 Connector 1: power connector
8 Connector 2: connector for digital outputs
9 Connector 3: connector for digital inputs
10 Connector 4: connector for PWM outputs
11 Connector 5: connector for RS-485/RS-422 communication
12 Connector 6: connector for analog inputs
13 Connector 7: connector for analog outputs
14 Diagnostics and status indicators
15 End plate

19 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

ILC 191 ME/INC

15
PF
A2
A1
BSA
B2
1 B1
C2 Z2
1
C1 2 Z1
FAIL C2

1
2
C1 3
C2
3
C1 4
RDY 4
C2
C1

RxD
I2 P2 TxD

14
I1 P1
I4 D2
E I3 D1
I6
I5

2
I8
I7
FR Q2
Q1
FF Q4
UL Q3
BF
US
rg SF
mbe UM
Blo NC 5

Encoder
25 E/I 7
M 7000

CNT
28

RS485/422
D-3 91

PWM
1 .: 2

DI
ILC r-No /xxx ck:

DO
3

PWR
e xx
Ord W: 8Blo
/F r.
HW Add xx ORX
C . W R
MA x. xx ION PW
.x T
xx OMA
UT T
A SE
RE
ET ge

STOP
ES lta
MR Vo
X1

4 PR
G
RU
N/P
RO
G

PW
Slo

DO
t

R
24

24

24
V
V

13
K
LN

5
DI

M
5V

12
11
PW
T 22
5/4 4V
AC 48 -2
RS 5
V
24
K T 5-

10
LN CN
r
de

6
co
En

A CT

9
8
7
Figure 2-7 Structure of the ILC 191 ME/INC Inline controller

The Inline controller consists of the following components:


1 Electronics base
2 Slot for the parameterization memory/card holder (SD card).

The SD card is not supplied as standard with the Inline controller.


Please refer to the ordering data in Section “Accessories” on page 170.
3 Reset button
4 Mode selector switch
5 RS-232 interface
6 Ethernet interfaces
7 Connector 1: power connector
8 Connector 2: connector for digital outputs
9 Connector 3: connector for digital inputs
10 Connector 4: connector for PWM outputs
11 Connector 5: connector for RS-485/RS-422 communication
12 Connector 6: connector for counter inputs
13 Connector 7: connector for incremental encoder inputs (asymmetric; channels A, B,
and Z)
14 Diagnostics and status indicators
15 End plate

8607_en_06 Phoenix Contact 20 / 185


ILC 191 ME/X

2.5 Diagnostics and status indicators


The diagnostics and status indicators are used for quick local error diagnostics.

A DO PWM B DO PWM
RDY AI RDY CNT
BSA E BSA
E
P1 P2 UA P1 P2 C11 C21
D1 D2 D1 D2 C12 C22
Q1 Q2 Q1 Q2
Q3 Q4 C13 C23
Q3 Q4
C14 C24

PLC/PWR/PN PLC/PWR/PN
BSA
PF

O1
O2
AO BSA
C2
1
A1

B1
PF
A2

B2

Z2
INC
UA 1
C1 2 Z1
FAIL FAIL 2
C2
C1 3
C2

FR RDY
PF FR RDY
C1
3

4
C2
4 PF
C1

UL FF RxD O1 O2 UL FF TxD
RxD A1 A2
I2 P2 TxD I2 P2
I1 I1 P1
P1 I4
I4 D2
US BF E I3
I6
D1
D2
US BF E I3
I6
D1 B1 B2
I5 I5
I8 I8
I7
UM SF FR
Q1
Q2
I7
UM SF FR
Q1
Q2 Z1 Z2
FF FF Q4
Q4 UL
UL Q3 Q3
BF BF
US US
SF rg SF
rg be UM
be UM om C
om N
5 Bl E/IN 075

Encoder
5 Bl /A 4
A0

CNT
E 07 82
AI

82 32 1 M 00

RS485/422
32 1 M 00
RS485/422

D-

PWM
D- 27
PWM

19 : 27 19 :

DI
ILC -No. /xxx ck:
DI

ILC -No. /100 ck:

DO
DO

PWR
er xx
PWR

er 00
Ord W: 8Blo Ord W: 8Blo
/F r. /F r.
HW Add xx ORX HW Add xx ORX
C . R

ETH
C . R W

ETH MA . xx ON PW
W
MA . xx ON PW
. xx ATI . xx ATI
xx M xx M
TO
AU
TO
RES
ET
FAIL AU
RES
ET
FAIL
ET
ET tage

STOP
tage
STOP

ES ES
MR Vol MR Vol
X1 X1

LNK R OG S lot 24
V LNK N/P
R OG Slo
t
24
V

RU
N/P
V
I1 I2 RU V
I1 I2
R 24 R 24
PW PW
PR
G
24
V I3 I4 PR
G
DO 24
V I3 I4
K DO K
LN LN
DI 5V I5 I6 TxD RxD DI 5V I5 I6 TxD RxD

PW
M
2
I7 I8 PW
M
2
I7 I8
T V T 5/42 V
AC 5/42 10 AC 24
48 0- RS
48 5-
RS
ACT ACT
RS-485
V

RS-485
V 24
10 K T 5-
K AI 0- LN CN
LN
r
de

AC
T
A0

DI AC
T
En
co

DI

Figure 2-8 Diagnostics and status indicators of the ILC 191 ME/AN (A) and the
ILC 191 ME/INC (B)

Table 2-1 Diagnostics and status indicators

Des. Color Status Meaning


ETH: state of the Ethernet interface
Off Connection not established successfully
LNK Green Connection established successfully (link): the Inline controller is able to contact an-
On
other network device.
Off Data transmission inactive
ACT Yellow
On Data transmission active (activity): the Ethernet interface is sending or receiving data
PROFINET
Status of PROFINET communication/communication error (BusFail)
The higher-level PROFINET controller has established an active communication con-
Off
nection to the PROFINET device.
BF Red The PROFINET device has not established an active communication connection to a
On
higher-level PROFINET controller.
The higher-level PROFINET controller establishes a communication connection to the
Flashing
PROFINET device.
Group error (PROFINET)
SF Red Off PROFINET diagnostics not present.
On PROFINET diagnostics present.

21 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

Des. Color Status Meaning


PLC: diagnostics of the Inline controller
Inline controller running
Off IEC 61131 runtime system not ready to operate.

FR Green IEC 61131 runtime system successfully initialized.


Flashing
Control function is in the READY/STOP state, program not processed.
IEC 61131 runtime system successfully initialized and a program is running.
On
Control function is in the RUN state.
Failure
FF Yellow On A runtime error has occurred in the IEC 61131 runtime system program.
Off No runtime error has occurred in the IEC 61131 runtime system program.
PWR: supply voltage
(see also Section “Remote bus” on page 38)
24 V supply UILC for generating voltages UL and UANA
Off Supply voltage not present
UL Green
Supply voltage is present
On
(indication if 24 V supply voltage UILC is present).
24 V supply for segment circuit
US Green Off Supply voltage not present
On Supply voltage present
24 V supply for main circuit
UM Green Off Supply voltage not present
On Supply voltage present
IL: INTERBUS diagnostics
INTERBUS master ready to operate/data transmission active
(INTERBUS ready/running)
RDY Green Off INTERBUS master not ready to operate
Flashing INTERBUS master in READY or ACTIVE state
On INTERBUS master in RUN state
Failure
Off No error occurred
FAIL Red One of the following errors has occurred:
On – Bus error in the connected bus (remote bus/local bus)
– Controller error
Bus segment aborted
BSA Yellow Off Bus segment(s) in the connected bus not switched off.
On One or more bus segments in the connected bus are switched off.
Peripheral fault
PF Yellow Off No peripheral fault on a device in the connected bus.
On Peripheral fault on a device in the connected bus (local bus or remote bus).

8607_en_06 Phoenix Contact 22 / 185


ILC 191 ME/X

Des. Color Status Meaning


I/O: digital inputs and outputs
Inputs 1 to 8
I1 to I8 Yellow Off Corresponding input not set
On Corresponding input set
Error
E Yellow Off No short circuit and no overload at the outputs
On Short circuit/overload at at least one output
Outputs 1 to 4
Q1 to Q4 Yellow Off Corresponding output not set
On Corresponding output set
PWM: outputs for pulse width modulation
Pulse signal outputs
P1, P2 Yellow Off Corresponding output not set
On Corresponding output set
Direction signal outputs
D1, D2 Yellow Off Corresponding output not set
On Corresponding output set
RS-485: RS-485/RS-422 interface
Communication via RS-485/RS-422 interface
TxD Yellow Off No data being sent
Flashing Sending data
Communication via RS-485/RS-422 interface
RxD Yellow Off No data being received
Flashing Receiving data
AI: analog inputs (ILC 191 ME/AN)
Sensor supply voltage
UA Green Off Sensor supply voltage not present/short circuited
On Sensor supply voltage present
AO: analog outputs (ILC 191 ME/AN)
Overload of analog outputs
O1, O2 Red Off No overload at corresponding analog output
On Overload at corresponding analog output
CNT: counter inputs (ILC 191 ME/INC)
Status of counter inputs
C11...C24 Yellow Off Corresponding input not set
On Corresponding input set
INC: incremental encoder inputs (ILC 191 ME/INC)

23 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

Des. Color Status Meaning


Level at channel A
A1, A2 Yellow Off 0 signal
On 1 signal
Level at channel B
B1, B2 Yellow Off 0 signal
On 1 signal
Level at channel Z
Z1, Z2 Yellow Off 0 signal
On 1 signal

8607_en_06 Phoenix Contact 24 / 185


ILC 191 ME/X

2.6 Mode selector switch


The mode selector switch is used to define the operating state of the controller.
The RUN/PROG and STOP positions have a toggle button function and the MRESET
position a pushbutton function. After releasing the button in the MRESET position, it returns
to STOP.

Operating Explanation
mode
RUN/PROG The controller is in the RUN state. The application program is pro-
cessed.
The PC Worx/PC Worx Express software can be used for program and
configuration modifications as well as for the online monitoring func-
tion.

The application program is not processed if a controller error


has occurred or if the application program has been stopped
by PC Worx/PC Worx Express.

STOP The controller is in the STOP state. Application program processing


has been stopped.
MRESET Retain data and the application program are deleted.
Set the mode selector switch in the following sequence to delete the re-
tain data and the application program:
• Set the switch to the MRESET position for three seconds.
• Release the switch for less than three seconds.
• Set the switch to the MRESET position for three seconds.

PF
O2
O1
BSA

MRESET
UA
FAIL

RDY
STOP

RxD
I2 P2 TxD
I1 P1
I4 D2
E I3 D1
I6
I5
I8
FR I7
Q2
Q1
FF Q4
UL Q3
BF
US
rg SF
be UM
om N
5 Bl E/A 074
A0
AI

RUN/PROG
82
32 1 M 00
RS485/422

D-
PWM

19 : 27
DI

ILC -No. /100 ck:


DO
PWR

er 00
Ord W: 8Blo
/F r.
HW Add xx ORX
C . W R
MA . xx ON PW
. xx TI
xx MA
TO T
AU SE
RE
ET
tage
STOP

ES
MR Vol
X1
G t V
RO Slo 24
N/P
RU V
R 24
PW
G V
PR 24
K DO
LN
DI 5V

M
PW 2
T 5/42 V
AC 48 0-
10
RS
V
10
K AI 0-
LN
A0

T
AC

Figure 2-9 Mode selector switch of the Inline controller, ILC 191 ME/AN illustrated

25 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.7 Reset button (concealed)


The reset button on the Inline controller (see item 3 in Figure 2-6 on page 19/item 3 in
Figure 2-7 on page 20) can only be operated with a pointed object (e.g., a pen) and is
therefore protected against accidental activation.
If you carry out a voltage reset simultaneously as you press the reset button, this resets the
Inline controller to its default settings.

How to proceed Hold down the reset button and switch the supply voltage of the Inline controller off and on
again. Release the reset button only after the FF (yellow) LED starts flashing.
The Inline controller has been initialized successfully and reset to its default settings only
after the FR (green) and RDY (green) LEDs are flashing. The control function is in the
READY/STOP state, a program is not processed. This process may take up to one minute,
approximately.

2.8 Parameterization memory


The parameterization memory can be used to save programs and configurations which
belong to your project. In addition, application-specific data can also be stored on the
parameterization memory. See Section “Parameterization memory and Internet Explorer”
on page 76.
The Inline controller has an integrated parameterization memory.
A plug-in parameterization memory in the form of an SD card can also be used. The SD card
can be used as the main or additional memory of the Inline controller; see Section 3.7.
The SD card is optional and not required for operating the Inline controller.

NOTE: Parameterization memory (SD card) – formatting note


The SD card is already formatted and is intended for use with Phoenix Contact devices.
• Make sure that the SD card is not reformatted.

NOTE: Using the parameterization memory (SD card)


Only use a parameterization memory provided by Phoenix Contact (for ordering data, see
Section “Accessories” on page 170).

8607_en_06 Phoenix Contact 26 / 185


ILC 191 ME/X

2.8.1 Inserting/removing the parameterization memory

A B

PF
PF
O2 O2
O1 O1
A
BS A
BS
UA
UA
FAIL
FAIL

RDY
RDY

RxD
TxD RxD
I2 P2 TxD
I1 I2 P2
P1 I1
I4 D2 P1
I3 I4 D2
E D1 I3
I6 E D1
I6
I5
I8 I5
I8
FR I7
Q2 FR I7
Q1 Q2
FF Q4 Q1
UL FF Q4
Q3 UL
BF Q3
US BF
SF US
rg SF
be UM rg
om N be UM
5 Bl E/A 074 om

A0
N
5 Bl E/A 074

A0
AI
82
32 1 M

AI
00 82

RS485/422
32 1 M 00

RS485/422
D-

PWM
19 : 27 D-

PWM
19 : 27
DI
ILC -No. /100 ck:

DI
DO ILC -No. /100 ck:

DO
PWR
er 00

PWR
Ord W: 8Blo

>Click<
er 00
/F dr. Ord W: 8Blo
HW Ad xx ORX /F r.
C . W R HW Add xx ORX
MA . xx ON PW C
MA . xx ON
. W PW
R
. xx TI
xx MA . xx ATI
xx M
TO T
AU SE TO
SE
T
RE AU
RE
ET ET
tage
STOP

ES
tage

STOP
MR Vol ES
X1 MR Vol
X1
G t V
RO Slo 24 G
Slo
t V
N/P RO 24
RU N/P
V RU V
R 24 R 24
PW PW
G V
PR 24 PR
G V
K DO DO 24
LN K
LN
DI 5V DI 5V

M M
PW 2 PW
T V 2
AC 5/42 10 T 5/42 V
48
RS 0- AC 48 0-
10
V RS
10 V
K AI 0- K 0-
10
LN LN AI

A0 A0

T T
AC AC

Figure 2-10 Inserting (A) and removing (B) the parameterization memory

Inserting the SD card The Inline controller has an SD card holder with push/push technology.
• Insert the parameterization memory (SD card) into the slot as shown in Figure 2-10 (A).
• Applying light pressure, push the parameterization memory into the slot until it engages
with a click in the card holder.

Removing the SD card • Applying light pressure, push the parameterization memory into the slot in the direction
shown in Figure 2-10 (B) until the snap-on mechanism releases the parameterization
memory and partially ejects it from the slot. Remove the parameterization memory.

For additional information on the parameterization memory, please refer to Section


“Functions of the plug-in parameterization memory (SD card)” on page 70 and Section
“Parameterization memory and Internet Explorer” on page 76.

27 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.9 Internal basic circuit diagram


Basic circuit diagram of
the ILC 191 ME/AN

μP IB

UL+
Q1...4
UANA
UL
24V
10V
C
7,5V 24V 8 x DI RS-485/ ADC DAC
RS-422
24V 24V PWM/

US
4 x DO PTO D
UM
A UL US

UA UM
AGND
ETH 2TX
PWR

Figure 2-11 Internal basic circuit diagram of the ILC 191 ME/AN

Key:

Microprocessor Inverter

Protocol chip LED

RS-232 interface Optocoupler

Transmitter NPN transistor

RJ45 socket Ethernet switch

ADC Analog/digital converter DAC Digital/analog converter

SD card holder (the SD card is not sup-


plied as standard)
The gray areas in the basic circuit diagram represent electrically isolated areas:
A: Ethernet interface
B: Logic
C: I/O

Other symbols used are explained in the IL SYS INST UM E user manual.

8607_en_06 Phoenix Contact 28 / 185


ILC 191 ME/X

Basic circuit diagram of


the ILC 191 ME/INC

μP IB

UL+
Q1...4
UANA
UL

C C
7,5V 24V 8 x DI RS-485/ CNT INC
RS-422
24V 24V PWM/
4 x DO PTO D
US
UM
A UL US
UM

ETH 2TX
PWR

Figure 2-12 Internal basic circuit diagram of the ILC 191 ME/INC

Key:

Microprocessor Inverter

Protocol chip LED

RS-232 interface Optocoupler

Transmitter NPN transistor

RJ45 socket Ethernet switch

CNT Counter inputs INC Incremental encoder inputs

SD card holder (the SD card is not sup-


plied as standard)
The gray areas in the basic circuit diagram represent electrically isolated areas:
A: Ethernet interface
B: Logic
C: I/O

Other symbols used are explained in the IL SYS INST UM E user manual.

29 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.10 Mounting and removing the Inline controller

NOTE: Dangerous contact voltage


During any work on the controller, switch off the power supply to the Inline station and
make sure the supply voltage is protected against unauthorized reactivation.

For notes and instructions on mounting and removing Inline terminals, please refer to the
IB IL SYS PRO UM E user manual (for INTERBUS), the IL SYS INST UM E Inline
installation manual or the Inline system manual for your bus system.

An Inline station is set up by mounting the individual components side by side. No tools are
required. Mounting the components side by side automatically creates potential and bus
signal connections between the individual station components.
The controller is mounted perpendicular to the DIN rail.

Mounting location Like all other terminals in the Inline product range, the Inline controller has IP20 protection
and is designed for use in a closed control cabinet or control box (terminal box) with IP54
protection or higher.

DIN rail The Inline controller is mounted on a 35 mm standard DIN rail.

Fix the DIN rail on which the Inline controller is mounted several times, especially in the
area around the Inline controller. This makes it easier to remove the Inline controller.

End brackets Mount end brackets on both sides of the Inline station. The end brackets ensure that the
Inline station is correctly mounted. End brackets secure the Inline station on both sides and
keep it from moving from side to side on the DIN rail. Phoenix Contact recommends using
CLIPFIX 35-5 end brackets (Order No. 3022276).

End plate The mechanical end of an Inline station is the end plate. It has no electrical function. It
protects the station against ESD pulses and the user against dangerous contact voltages.
The end plate is supplied together with the Inline controller and does not need to be ordered
separately.

NOTE: Risk of damage during mounting and removal if an Inline terminal is left in
position
When mounting or removing the Inline controller, it must be tilted. Tilting the Inline
controller when mounting or removing it can damage the locking hooks and jumper
contacts of the adjacent Inline terminal on the right.
• Before mounting or removing the Inline controller, detach the right-hand connector of
the Inline controller and the adjacent Inline terminal on the right.

Mounting position Mount the Inline controller horizontally (as shown in Figure 2-13 on page 31). The specified
temperature range (see “Ambient conditions” on page 166) is only guaranteed if the Inline
controller is mounted in this position.

The Inline controller must only be mounted or removed within a temperature range from -
5°C to +55°C.

8607_en_06 Phoenix Contact 30 / 185


ILC 191 ME/X

Mounting When mounting the Inline controller, proceed as shown in Figure 2-13 and Figure 2-14:
• Disconnect the power to the station.
• Place the Inline controller onto the DIN rail from above (Figure 2-13, A) and push down
(Figure 2-13, B).
• Then attach all the electronics bases required to set up the station. Observe the
information provided in the aforementioned user manuals.

Make sure that all featherkeys and keyways on adjacent terminals are securely
interlocked.

• Once all the bases have been snapped on, insert the connectors in the corresponding
bases.
First, place the front connector shaft latching in the front snap-on mechanism
(Figure 2-14, A).
Then press the top of the connector towards the base until it snaps into the back snap-
on mechanism (Figure 2-14, B).

A B

Figure 2-13 Snapping on the Inline controller (1)

A
Figure 2-14 Snapping on the Inline controller (2)

31 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

Removal When removing the Inline controller from the DIN rail, proceed as shown in Figure 2-16 on
page 33:
• Disconnect the power to the station.

NOTE: Risk of damage during mounting and removal if an Inline terminal is left in
position
When mounting or removing the Inline controller, it must be tilted. Tilting the Inline
controller when mounting or removing it can damage the locking hooks and jumper
contacts of the adjacent Inline terminal on the right.
• Before mounting or removing the Inline controller, detach the right-hand connector of
the Inline controller and the adjacent Inline terminal on the right.
• Remove all the connectors of the Inline controller.

• Lever up each connector by pressing on the back connector shaft latching


(Figure 2-16, A).
• Remove the connectors (Figure 2-16, B).
• If Inline terminals are mounted on the Inline controller (see Figure 2-15):

• Remove the following connectors:


– All connectors of the terminal that is directly connected (A1 to A4)
– The adjacent connector of the following terminal (B1)
• Remove the directly adjacent Inline terminal (A).

Observe the information provided on page 30 of the above user manuals.

A1...A4 B1

D-32825 Blomberg
ILC 191 ME/AN RDY FAIL BSA PF
Order-No.: 2700074 FR E I1 I2 UA O1 O2
HW/FW: 00/100 UL FF I3 I4
MAC Addr. 8Block: US BF Q1 Q2 I5 I6 P1 P2
xx. xx. xx. xx
UM SF Q3 Q4 I7 I8 D1 D2 TxD RxD
AUTOMATIONWORX
DI
PWM

AI
PWR
DO

A0
RS485/422

X1
MRESET
RESET
STOP

PWR
Slot Voltage
RUN/PROG
PRG PWR 24 V

LNK DO 24 V

DI 24 V
X2.1

PWM 5V
ACT
RS485/422

LNK
AI 0 - 10 V

X2.2 A0 0 - 10 V

ACT

ILC 191 ME/AN A B

Figure 2-15 Connectors to be removed if terminals are installed next to the Inline
controller, ILC 191 ME/AN illustrated

8607_en_06 Phoenix Contact 32 / 185


ILC 191 ME/X

• Insert a tool in the base latches of the Inline controller and pull gently upwards
(Figure 2-17, A). Pull out the Inline controller from the DIN rail (Figure 2-17, B, C).

Figure 2-16 Removing the Inline controller (1)

A B
Figure 2-17 Removing the Inline controller (2)

Replacing an Inline If you want to replace an Inline controller within an Inline station, proceed as described
controller above (removing and mounting). Make sure that the terminal to the right is not installed
when removing and mounting the Inline controller. Only reinstall this terminal once the Inline
controller is mounted.

In particular, make sure that all featherkeys and keyways on adjacent terminals are
securely interlocked.

Observe the following when replacing an Inline controller:


• Enter the new MAC address when using the BootP server.

33 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.11 Communication paths


The communication path to the Inline controller must be determined before communication
with the Inline controller can take place.
The following communication paths are available on the Inline controller:

(A) 2 x Ethernet 10/100Base-T(X) (switched internally)

(B) PRG The serial interface of your PC is directly connected to the Inline
controller (not to the programming).
For additional information on using the serial interface (e.g., IP ad-
dress assignment), please refer to Section “Function blocks for
RS-232 communication” on page 93.

(C) RS-485/422 This interface is used for serial communication with one device
(full duplex or half duplex mode) or with several devices (half du-
plex mode).
For additional information, please refer to Section “RS-485/RS-
422 communication interface” on page 48.

The Inline controller cannot be programmed via the RS-232 interface (PRG) or the RS-
485/RS-422 interface.

A B C
PF PF PF
O2 O2 O2
O1 O1 O1
A A A
BS BS BS
UA UA UA
FAIL FAIL FAIL

RDY RDY RDY

RxD RxD RxD


I2 P2 TxD I2 P2 TxD I2 P2 TxD
I1 P1 I1 P1 I1 P1
I4 D2 I4 D2 I4 D2
E I3 D1 E I3 D1 E I3 D1
I6 I6 I6
I5 I5 I5
I8 I8 I8
FR I7 FR I7 FR I7
Q2 Q2 Q2
Q1 Q1 Q1
FF Q4 FF Q4 FF Q4
UL Q3 UL Q3 UL Q3
BF BF BF
US US US
SF SF SF
erg UM erg UM erg UM
mb mb mb
5 BloE/AN 074 5 BloE/AN 074 5 BloE/AN 074
A0

A0

A0
AI

AI

AI

82 82 82
32 1 M 00 32 1 M 00 32 1 M 00
RS485/422

RS485/422

RS485/422

D- D- D-
PWM

PWM

PWM

19 : 27 19 : 27 19 : 27
DI

DI

DI

ILC -No. /100 ck: ILC -No. /100 ck: ILC -No. /100 ck:
DO

DO

DO
PWR

PWR

PWR

er 00 lo er 00 lo er 00 lo
Ord W: . 8B Ord W: . 8B Ord W: . 8B
/F dr /F dr /F dr
HW Ad xx ORX HW Ad xx ORX HW Ad xx ORX
. R . R . R
MAC . xx IONW PW MAC . xx IONW PW MAC . xx IONW PW
. xx . xx . xx
xx MAT xx MAT xx MAT
TO T TO T TO T
AU SE AU SE AU SE
RE RE RE
T T T
ge ge ge
STOP

STOP

STOP

SE SE SE
lta lta lta
MRE Vo MRE Vo MRE Vo
X1 X1 X1
V V V
PR
OG Slot 24 PR
OG Slot 24 PR
OG Slot 24
N/ N/ N/
RU V RU V RU V
R 24 R 24 R 24
PW PW PW
G V G V G V
PR 24 PR 24 PR 24
K DO K DO K DO
LN LN LN
DI 5V DI 5V DI 5V

M M M
PW 2 PW 2 PW 2
T 5/42 V T 5/42 V T 5/42 V
AC 48 0-
10 AC 48 0-
10 AC 48 0-
10
RS RS RS
V V V
10 10 10
K AI 0- K AI 0- K AI 0-
LN LN LN
A0 A0 A0

T T T
AC AC AC

RS-485

Figure 2-18 Communication paths, ILC 191 ME/AN illustrated

8607_en_06 Phoenix Contact 34 / 185


ILC 191 ME/X

2.11.1 Ethernet
Two standardized Ethernet interfaces are available for connecting the Ethernet network.
The Ethernet network is connected via RJ45 sockets.

Use an Ethernet cable according to at least CAT5 of IEEE 802.3.


Observe the bending radii of the Ethernet cables used.

The contact assignment of the interface is as follows:

Transmit data + T+ 1
RJ45 Pin 1
Transmit data - T- 2
Pin 2
Receive data + R+ 3
Pin 3
– 4
Pin 4
– 5
Pin 5
Receive data - R- 6 Pin 6
– 7 Pin 7
– 8 Pin 8
Figure 2-19 Ethernet interface

PF
O2
O1
A
BS
UA
FAIL

RDY

RxD
I2 P2 TxD
I1 P1
I4 D2
E I3 D1
I6
I5
I8
FR I7
Q2
Q1
FF Q4
UL Q3
BF
US
rg SF
be UM
om N
5 Bl E/A 074
A0
AI

82
32 1 M 00
RS485/422

D-
PWM

19 : 27
DI

ILC -No. /100 ck:


DO
PWR

er 00 lo
Ord W: 8B
/F r.
HW Add xx ORX
C . W R
MA . xx ON PW
. xx TI
xx MA
TO
AU ET
RES
ET ge
STOP

ES lta
MR Vo
X1
G V
RO Slot 24
N/P
RU V
R 24
PW
G V
PR 24
K DO
LN
DI 5V

M
PW
T /422 V
AC 85
0-
10
RS4
V
10
K AI 0-
LN
A0

T
AC

Figure 2-20 Connecting the Ethernet cable to the Inline controller, ILC 191 ME/AN
illustrated

The interface is able to switch over the transmitter and receiver automatically (auto
crossover).

35 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.11.2 Serial PRG interface (mini-DIN socket)


In addition to providing the Ethernet interface, this serial interface enables communication
with the Inline controller from a PC.
A connecting cable is required for direct connection of the Inline controller to a PC with
PC Worx via the serial PRG interface. Connect the connecting cable to the programming
interface of the Inline controller (PRG) and the serial interface of the PC.

This interface can be used to either assign the IP address of the Inline controller and to
access the Inline controller using the Diag+ diagnostic tool or to communicate with special
I/O devices via function blocks (see Section 3.17, “Function blocks for RS-232
communication”).
The Inline controller cannot be programmed via the RS-232 interface.

Assembly instruction

1 2
2 3
4 5
5 8
6 7

PF
O2
O1
A
BS
UA
FAIL

RDY

RxD
I2 P2 TxD
I1 P1
I4 D2
E I3 D1
I6
I5
I8
FR I7
Q2
Q1
FF Q4
UL Q3
BF
US
rg SF
be UM
om
Bl N
25 E/A 074
A0
AI

28 M 700
RS485/422

D-3 91
PWM

1 .: 2
DI

ILC -No /100 ck:


DO
PWR

er 00
Ord W: 8Blo
/F dr.
HW Ad xx ORX
A C . W R
M . xx N PW
. xx TIO
xx OMA
T T
AU SE
RE
ET
tage
STOP

ES
MR Vol
X1
G t V
RO Slo 24
N/P
RU V
R 24
PW
G V
PR 24
K DO
LN
DI 5V

M
PW 2
T 5/42 V
AC 48 0-
10
RS
V
10
K AI 0-
LN
A0

T
AC

Figure 2-21 Connecting cable between PC and Inline controller, ILC 191 ME/AN
illustrated

8607_en_06 Phoenix Contact 36 / 185


ILC 191 ME/X

The contact assignment of the interface is as follows:

1 TXD
2 RXD
3 N.C.
4 GND
5 RTS
6 CTS
This interface can be used to:
– Assign the IP address or work with Diag+
– Communicate with I/O devices (e.g., modem, printer, barcode reader) via function
blocks
For communication with I/O devices, the PC Worx/PC Worx Express software provides the
RS232_INIT, RS232_SEND, and RS232_RECEIVE function blocks; see Section 3.17 on
page 93.

37 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.12 INTERBUS

The descriptions for INTERBUS apply to all Inline controllers listed on the inner cover page
of this user manual.

Observe the information in the “Configuring and installing the INTERBUS Inline product
range” user manual IB IL SYS PRO UM E when creating an Inline system (local bus and/or
remote bus).

Please note that the Inline controller does not support the following functions:
– Switching of devices
– Single-channel diagnostics
– Fiber optic diagnostics/optical regulation
– Logical addressing
Only INTERBUS devices with SUPI 3 and SUPI 3 OPC protocol chip or later can be used
with INTERBUS as local bus/remote bus devices.

2.12.1 Local bus


The local bus is automatically created by directly connecting I/O modules to the Inline
controller.

2.12.2 Remote bus


Connect the remote bus to the Inline Controller using the IBS IL 24 RB-T-PAC branch
terminal (Order No. 2861441; including accessories).

The first branch terminal must be placed directly after the Inline controller. In terms of
topology, it opens a remote bus.
If additional branch terminals are used after the first branch terminal, they must be
installed directly one after the other (see also notes in the terminal-specific data sheet). In
terms of topology, the additional branches are remote bus branches with the branch
terminal being the first device in the corresponding remote bus branch.
A maximum of 3 branch terminals can be connected to the Inline controller, each of which
opens a remote bus (see Figure 2-2 on page 14).

8607_en_06 Phoenix Contact 38 / 185


ILC 191 ME/X

2.13 Power supply

2.13.1 Sizing of the power supply


Choose a power supply unit that is suitable for the currents in your application. The selection
depends on the bus configuration, the resulting maximum currents, and the type of supply
(separate supply of UILC, UM, and US, or supply from a power supply unit).

A power supply without a fall-back characteristic curve must be used for correct
operation of the Inline controller (see Figure 2-23).
When the Inline controller is switched on, an increased switch-on current is temporarily
triggered. The Inline controller behaves like a capacitive load when it is switched on.

Some electronically controlled power supplies have a fall-back characteristic curve (see
Figure 2-22). They are not suitable for operation with capacitive loads.
A primary-switched power supply (without fall-back characteristic curve) from the
QUINT POWER range (see latest catalog from Phoenix Contact) is recommended for Inline
controller operation.

Overload range Overload range


UOUT with fall-back UOUT without fall-back
characteristic curve characteristic curve
[V] [ V]

24 24

I OUT I OUT
IN [A] [ A]

 1.1 x I N  2.4 x I N IN  1.5 x I N


6219B070 6219B071

Figure 2-22 Overload range with fall-back characteristic Figure 2-23 Overload range without fall-back
curve characteristic curve

39 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.13.2 Connecting the power supplies


Supply the Inline controller using external 24 V DC voltage sources. The permissible voltage
ranges from 19.2 V DC to 30 V DC (ripple included).

Only use power supplies that are suitable for operation with capacitive loads (increased
switch-on current) (see Section “Sizing of the power supply” on page 39).

1. Connect the power supplies to the connector for power supply as shown in Figure 2-24.
2. Insert the connector in the Inline controller.
3. Switch on the power supplies.
4. The UL, UM, and US LEDs light up and, after around 10 seconds, the FR and RDY
LEDs start flashing.
The Inline controller is now fully initialized.
If the LEDs do not light up or start flashing, there is a serious fault on the Inline controller. In
this case, please contact Phoenix Contact.

PF
O2
O1
A
BS
UA
FAIL
FR
RDY
UL FF
RxD
I2 P2 TxD US BF
I1 P1
I4 D2
E I3
I6
D1 UM SF
I5
I8
FR I7
Q2
Q1
FF Q4
UL Q3
BF
US
rg SF
be UM
om
Bl N
25 E/A 074
A0
AI

28 M 700
RS485/422

D-3 91
PWM

1 .: 2
DI

ILC -No /100 ck:


DO

1 2
PWR

er 00
Ord W: 8Blo
/F dr.
HW Ad xx ORX
C . W R
MA . xx ION PW
. xx T
xx OMA
T T
AU SE
RE
ET
tage
STOP

ES
MR Vol
X1

RO
G
Slo
t
24
V 1 1
N/P
RU
PW
R 24
V
1 2 +
PR
G

LN
K DO 24
V

US
DI 5V

2 2 –
AC
T
PW

RS
M

48
5/42
2
0-
10
V 1.1 1 1
2.1 +
LN
K AI 0-
10
V
+ UM
A0
U ILC 3 3 –
AC
T
1.2 2 2
2.2 –
4 4
1.3 3 3
2.3

1.4 4 4
2.4

Figure 2-24 Connecting the supply voltages, ILC 191 ME/AN illustrated

8607_en_06 Phoenix Contact 40 / 185


ILC 191 ME/X

Terminal Assignment Remark


point
Connec- Power connector
tor 1
1.1 24 V DC 24 V segment The supplied voltage is directly routed to the potential jumper.
(US) voltage sup-
ply NOTE: Device defect and danger of fire due to inappropriate
external fuse
An inappropriate external fuse for this supply voltage can result in
a device defect or even the device catching fire.
• Protect the supply voltage externally according to the
connected load (local bus devices) with 8 A, maximum.
• Make sure the external fuse blows in the event of an error.

1.2 24 V DC 24 V supply The 7.5 V communications power (UL) for the ILC and the connected local bus
(UILC) devices is generated from this voltage. The 24 V analog voltage (UANA) for the
local bus devices is also generated.

NOTE: Device defect and danger of fire due to inappropriate


external fuse
An inappropriate external fuse for this supply voltage can result in
a device defect or even the device catching fire.
• Protect the supply voltage externally according to the
connected load (local bus devices) with 2 A, maximum.
• Make sure the external fuse blows in the event of an error.

2.1, 2.2 24 V DC 24 V main The main voltage is routed to the local bus devices via the potential jumpers.
(UM) voltage sup-
ply NOTE: Device defect and danger of fire due to inappropriate
external fuse
An inappropriate external fuse for this supply voltage can result in
a device defect or even the device catching fire.
• Protect the supply voltage externally according to the
connected load (local bus devices) with 8 A, maximum.
• Make sure the external fuse blows in the event of an error.

1.3 LGND Logic ground The potential is reference ground for the communications power.
reference po-
tential
2.3 SGND Segment The reference potential is directly routed to the potential jumper and is, simul-
ground refer- taneously, reference ground for the main and segment supply.
ence poten-
tial
1.4, 2.4 FE Functional Functional earth ground must be connected through the power supply. The
earth ground contacts are directly connected to the potential jumper and FE springs on the
(FE) bottom of the housing. The Inline controller is grounded when it is snapped
onto a grounded DIN rail. Functional earth ground is only used to discharge in-
terference.

41 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

NOTE: Device defect and danger of fire due to high total current
The maximum total current flowing through the potential jumpers is 8 A.
Exceeding the maximum total current can result in a device defect or even the device
catching fire.
• Make sure that the total current flowing through the potential jumpers does not exceed
8 A.

8607_en_06 Phoenix Contact 42 / 185


ILC 191 ME/X

2.13.3 24 V segment supply/24 V main supply


The segment supply and main supply must have the same reference potential. An
electrically isolated voltage area is not possible.

2.13.4 24 V segment supply


There are several ways of providing the segment voltage at connector 1:
1. The segment voltage can be supplied separately at terminal points 1.1 and 2.3 (GND)
(see Figure 2-24 on page 40).
2. Connections 1.1 and 2.1 (or 2.2) can be jumpered to ensure that the segment circuit is
supplied from the main circuit.
3. A switched segment circuit can be created with a switch between terminal points 1.1
and 2.1 (or 2.2).

NOTE:
The 24 V segment supply has protection against polarity reversal and surge voltage.
It does not have short-circuit protection.
The user must provide short-circuit protection. The rating of the fuse connected upstream
must be such that the maximum permissible load current of 8 A is not exceeded (total
current at UM and US).

2.13.5 24 V main voltage

NOTE:
The 24 V main supply has protection against polarity reversal and surge voltage.
It does not have short-circuit protection.
The user must provide short-circuit protection. The rating of the fuse connected upstream
must be such that the maximum permissible load current of 8 A is not exceeded (total
current at UM and US).

2.13.6 24 V ILC supply

NOTE:
The 24 V ILC supply has protection against polarity reversal and surge voltage. These
protective elements are only used to protect the power supply unit.
The rating of the fuse connected upstream must be such that the maximum permissible
load current of 2 A is not exceeded.

2.13.7 Jumpers

Terminals 1.3 and 2.3 on connector 1 can be jumpered if the communications power and
the segment voltage are not to be electrically isolated.

43 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.14 Digital outputs


Four 24 V DC outputs are available.

PF
O2
O1
A
BS
UA
FAIL

RDY

RxD
I2 P2 TxD
I1 P1

DO
I4 D2
E I3 D1
I6
I5
I8
FR I7
Q2
Q1
FF Q4
UL Q3

rg
US
BF
SF
1 2
be UM
Blom/AN
74

A0
25
ME 7000

AI
28

RS485/422
D-3 91

PWM
1 .: 2

DI
ILC -No /100 ck:

DO
PWR
er 00
Ord W: 8Blo
/F dr.
HW Ad xx ORX
C .
MA . xx ION
. xx T
xx OMA
T
W

T
PW
R
1.1 1 1
2.1
AU SE
RE
ET
tage

STOP
ES
MR Vol
X1
G t V
RO Slo 24

PR
G
RU
N/P

PW
R 24
V
V
1.2 2 2
2.2
DO 24
K
LN
DI 5V

AC
T
PW

RS
48
5/42
2
0-
10
V

V
1.3 3 3
2.3
10
K AI 0-
LN
A0

AC
T
1.4 4 4
2.4

Figure 2-25 Assignment of the terminal points of connector 2, ILC 191 ME/AN illustrated

Terminal point Assignment Remark


Connector 2 Output terminal points
1.1 Q1 Output 1
2.1 Q2 Output 2
1.2, 2.2 GND Ground contact for 2- and 3-wire termination
1.3, 2.3 FE Functional earth ground
1.4 Q3 Output 3
2.4 Q4 Output 4

The outputs are supplied with 24 V DC from the segment supply (US).

The outputs have protection against ground connection interrupt and must be wired
accordingly.

ILC 191 ME/AN L ILC 191 ME/AN L

8607A001
Figure 2-26 Basic wiring of an output with a load (L)
(shown using the ILC 191 ME/AN as an example)

8607_en_06 Phoenix Contact 44 / 185


ILC 191 ME/X

Phoenix Contact recommends that connectors for digital 4-channel or 16-channel Inline
terminals are used to connect sensors or actuators in 3-wire technology (not supplied as
standard, see Section “Accessories” on page 170).

The states of the digital outputs are written in PC Worx/PC Worx Express using the
corresponding system variables, see Section “Status register for local digital inputs and
outputs” on page 119.

45 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.15 Digital inputs


Eight 24 V DC inputs are available.

PF
O2
O1
A
BS
UA
FAIL

RDY

E
I1
I3
I5
I2
I4
I6
I8
P1
D1
P2
D2
TxD
RxD

DI
FR
Q1
Q2
I7 1 2
FF Q4
UL Q3
BF
US
rg SF
be UM
om
Bl N
25 E/A 074

A0
AI
28 M 700

RS485/422
D-3 91

1.1 2.1

PWM
1 .: 2

DI
ILC -No 100 ck:

DO
PWR
er 00/
Ord W: 8Blo

C
/F dr.
HW Ad xx ORX
. W R
1 1
MA . xx ION PW
. xx AT
xx OM
T T
AU SE
RE
ET
tage

STOP
ES
MR Vol
X1

RU
N/P
RO
G
Slo
t
24
V 1.2 2 2
2.2
V
R 24
PW
G V
PR 24
K DO
LN
DI

PW
M
2
5V
1.3 3 3
2.3
T 5/42 V
AC 48 0-
10
RS
V
10
K AI 0-
LN

T
A0
1.4 4 4
2.4
AC

Figure 2-27 Assignment of the terminal points of connector 3, ILC 191 ME/AN illustrated

Terminal point Assignment Remark


Connector 3 Input terminal points
1.1 I1 Input 1
2.1 I2 Input 2
1.2 I3 Input 3
2.2 I4 Input 4
1.3 I5 Input 5
2.3 I6 Input 6
1.4 I7 Input 7
2.4 I8 Input 8

The inputs are supplied with 24 V DC from the main supply (UM).

8607_en_06 Phoenix Contact 46 / 185


ILC 191 ME/X

2.16 Pulse direction outputs and PWM function


Two PWM outputs with direction signals are available for pulse width modulation (PWM).
The PWM outputs are parameterized in PC Worx using the PULSE_CH1 and PULSE_CH2
function blocks, see Section 3.16 on page 89.

For operating one-dimensional axis applications with step or servo motors with pulse
direction interface, the Easy Motion function block library is available in PC Worx. For
additional information, please refer to Section 5.

PF
O2
O1
A
BS
UA
FAIL

I1
I2
RDY

P1
P2 TxD
RxD
PWM
E I3
I4
I6
D1
D2
1 2
I5
I8
FR I7
Q2
Q1
FF Q4
UL Q3
BF
US

1.1 2.1
rg SF
be UM
om
Bl N
25 E/A 074

A0
AI
28 M 700

RS485/422
D-3 91
1 1

PWM
1 .: 2

DI
ILC -No /100 ck:

DO
PWR
er 00
Ord W: 8Blo
/F dr.
HW Ad xx ORX
A C . W R
M . xx N PW
. xx TIO
xx OMA
T T
AU SE
ET
RE
tage 1.2 2.2
STOP

ES
X1
MR Vol 2 2
G t V
RO Slo 24
N/P
RU V
R 24
PW

1.3 2.3
G V
PR 24
K DO
LN
DI 5V 3 3
M
PW 2
T 5/42 V
AC 48 0-
10
RS
V

1.4 2.4
10
K AI 0-
LN
A0 4 4
T
AC

Figure 2-28 Assignment of the terminal points of connector 4, ILC 191 ME/AN illustrated

Terminal point Assignment Remark


Connector 4 Output terminal points
1.1 P1 Output of PWM channel 1 (signal: PWMO1)
2.1 P2 Output of PWM channel 2 (signal: PWMO2)
1.2, 2.2 GND Ground contact for 2- and 3-wire termination
1.3 D1 Direction signal, corresponding to PWM signal/frequency signal PWMO1
2.3 D2 Direction signal, corresponding to PWM signal/frequency signal PWMO2
1.4, 2.4 FE Functional earth ground

If a shielded cable is required for connection of the I/O device, use the IB
IL SCN 6-SHIELD-TWIN (Order No. 2740245) or IB IL SCN-6 SHIELD (Order No.
2726353) Inline shield plug.

47 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.17 RS-485/RS-422 communication interface

For communication via the Modbus/RTU protocol, the “ILCME_ModBus_V1_00.exe”


setup must be downloaded to the product under phoenixcontact.net/products and
installed first.

Connector 5 of the Inline controller provides an RS-485/RS-422 communication interface.


An RS-485 network with one or more fieldbus devices can be created via this
communication interface.

PF
O2
O1
A
BS

RS-485
UA
FAIL

RDY

I2 P2 TxD
RxD 1 2
I1 P1
I4 D2
E I3 D1
I6
I5
I8
FR I7
Q2
Q1
Q4

1.1 2.1
FF
UL Q3
BF
US
SF
be
Blom/AN
4
rg
UM 1 1

A0
E25 07

AI
28
1 M 700

RS485/422
D-3
19 .: 2

PWM
DI
ILC -No /100 ck:

DO
PWR
er 00
Ord W: 8Blo
/F dr.
HW Ad xx ORX
C . R

1.2 2.2
W
MA . xx ION PW
. xx AT
xx OM
AU
T
RE
SE
T
2 2
ET
tage
STOP

ES
MR Vol
X1
G t V
RO Slo 24
N/P

PR
G
RU
PW
R

DO 24
24
V
V
1.3 3 3
2.3
K
LN
DI 5V

M
PW 2
T
1.4 2.4
5/42 V
AC 48 0-
10
RS
V

LN
K AI 0-
10
4 4
A0

T
AC

Figure 2-29 Assignment of the terminal points of connector 5, ILC 191 ME/AN illustrated

Terminal Assignment Full duplex mode Half duplex mode


point
1.1 TX+ Transmit data positive –
2.1 TX- Transmit data negative –
1.2 RX+ Receive data positive Transmit/receive data
positive
2.2 RX- Receive data negative Transmit/receive data
negative
1.3 R+ Termination resistor Termination resistor
(positive) (positive)
2.3 R- Termination resistor Termination resistor
(negative) (negative)
1.4, 2.4 FE Functional earth ground Functional earth ground

Please note:
Use a twisted pair, common shielded data cable to connect the devices, see Section
“Connecting the shield” on page 173.

8607_en_06 Phoenix Contact 48 / 185


ILC 191 ME/X

Data can be transmitted via the RS-485/RS-422 communication interface in full or half
duplex mode. In half duplex mode, several devices can be operated simultaneously via the
serial bus.
The respective interface wiring for full and half duplex mode is illustrated in Figure 2-30 and
Figure 2-31.

FAIL

TxD RxD

1.1 2.1

1.2 2.2

1.3 2.3

1.4 2.4 Rx+

Tx+
Rx-

Tx-

Figure 2-30 RS-485/RS-422 interface wiring: full duplex mode

FAIL

TxD RxD

1.1 2.1

1.2 2.2

1.3 2.3

1.4 2.4

Rx+/ Rx-/
Tx+ Tx-

Figure 2-31 RS-485/RS-422 interface wiring: half duplex mode

49 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

If the Inline controller is at the end of the bus, the internal termination resistor can be
switched on by inserting two wire jumpers.
The interface wiring for switching on the termination resistor is illustrated in Figure 2-32.

FAIL

TxD RxD

1.1 2.1

1.2 2.2

1.3 2.3

1.4 2.4

Rx-/ Rx+/
Tx- Tx+

Figure 2-32 RS-485/RS-422 interface wiring: termination resistor

Please observe the following when wiring:


– Fit the receive data cable with a termination resistor at the two furthest points of the RS-
485 network.
– Use the built-in termination resistor when connecting to the Inline terminal (see
Figure 2-32).
– If you use the integrated termination resistor, the polarization of the data cable will also
be active.
The interface is operated in PC Worx via the RS485_422_INIT, RS485_422_RECEIVE,
and RS485_422_SEND function blocks, see Section “Function blocks for RS-485/RS-422
communication” on page 99.

8607_en_06 Phoenix Contact 50 / 185


ILC 191 ME/X

2.18 Analog inputs

The description of the analog inputs applies to the ILC 191 ME/AN.

The ILC 191 ME/AN has two differential analog inputs.

PF

AI
O2
O1
A
BS
UA
FAIL

RDY
1 2
RxD
I2 P2 TxD
I1 P1
I4 D2
E I3 D1
I6
I5

1.1 2.1
I8
FR I7
Q2
Q1
FF Q4
UL
US
BF
Q3
1 1
rg SF
be UM
Blom N

A0
25 E/A 074

AI
28 0
1 M 70

RS485/422
D-3
19 .: 2

PWM
DI
ILC -No /100 ck:

DO
PWR
er 00
Ord W: 8Blo

M A C
/F dr.
HW Ad xx ORX
. xx
. xx TIO
xx OMA
.
NW PW
R 1.2 2 2
2.2
T T
AU SE
RE
ET
tage
STOP

ES
MR Vol
X1

RU
N/P
RO
G

PW
R
Slo
t
24

24
V

V
1.3 3 3
2.3
G V
PR 24
K DO
LN
DI 5V

AC
T
PW

RS
M

48
5/42
2
0-
10
V 1.4 4 4
2.4
V
10
K AI 0-
LN
A0

T
AC

Figure 2-33 Assignment of the terminal points of connector 6 on the ILC 191 ME/AN

Please note:
In environments with high levels of interference, unshielded cables may cause values to
be outside the specified tolerance limits.
• Connect the analog sensors using shielded, twisted-pair cables. See Section
“Connecting the shield” on page 173.
• Insulate the shielding at the sensor
or
Connect the shielding with a high resistance and a capacitor to the PE potential.

Terminal point Assignment Remark


Connector 6 Input terminal points
1.1 +AI1 Analog input of channel 1 positive
2.1 -AI1 Analog input of channel 1 negative
1.2 +AI2 Analog input of channel 2 positive
2.2 -AI2 Analog input of channel 2 negative
1.3 ASCR Sensor supply voltage
2.3 AGND Reference potential for sensor supply voltage
1.4, 2.4 FE Functional earth ground

51 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

Connection examples

1.1 2.1

1.2 2.2
U U
1.3 2.3

1.4 2.4

Figure 2-34 Connection for voltage measurement

+24 V
1.1 2.1

1.2 2.2
U
1.3 2.3 P

1.4 2.4
GND

Figure 2-35 Differential voltage input with active 3-wire transmitter

The states of the local analog inputs can be read using the corresponding system variables
in PC Worx, see Section “Status register for local analog inputs and outputs” on page 120.

8607_en_06 Phoenix Contact 52 / 185


ILC 191 ME/X

2.19 Analog outputs

The description of the analog outputs applies to the ILC 191 ME/AN.

The ILC 191 ME/AN has two analog outputs.

FAIL
BS
A
UA
PF

O1
O2

AO
1 2
RDY

RxD
I2 P2 TxD
I1 P1
I4 D2
I3

1.1 2.1
E D1
I6
I5
I8
FR I7
Q2

UL
FF
Q1
Q4 1 1
Q3
BF
US
rg SF
be UM
Bl /AN om
4

A0
E 007
25

AI
28
1 M 70

RS485/422
D-3
19 .: 2

PWM
1.2 2.2

DI
ILC -No /100 ck:

DO
PWR
er 00
Ord W: 8Blo

C
/F dr.
HW Ad xx ORX
. W R
2 2
MA . xx ION PW
. xx AT
xx OM
T T
AU SE
RE
ET
tage
STOP

ES
MR Vol
X1

RU
N/P
RO
G
Slo
t
24
V 1.3 3 3
2.3
V
R 24
PW
G V
PR 24
K DO
LN
DI 5V

T
PW
M
2 V
1.4 4 4
2.4
AC 5/42 10
RS
48 0-
V
10
K AI 0-
LN
A0

T
AC

Figure 2-36 Assignment of the terminal points of connector 7 on the ILC 191 ME/AN

Terminal point Assignment Remark


Connector 7 Output terminal points
1.1 AO1 Analog output channel 1
2.1 AO2 Analog output channel 2
1.2, 2.2 AGND Reference potential for the analog outputs
1.3 N.C. Not used
2.3 N.C. Not used
1.4, 2.4 FE Functional earth ground

Connection notes:
– Always connect the analog actuators using shielded twisted pair cables. Unshielded
cables may cause values to be outside the specified tolerance limits in environments
subject to heavy noise.

Please note:
An Inline shield plug is required to connect the cables to connector 7, see Section
“Connecting the shield” on page 173.
The states of the local analog outputs can be read and written using the corresponding
system variables in PC Worx, see Section “Status register for local analog inputs and
outputs” on page 120.

53 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

2.20 Counter inputs

The description of the counter inputs applies to the ILC 191 ME/INC.

The ILC 191 ME/INC has two counter inputs for detecting fast pulse sequences from
sensors.

PF
A2
CNT
A1
A B2
BS B1
1
C2 Z2

FAIL
C1
1
C2
2 Z1 1 2
2
C1 3
C2
3
C1 4
RDY 4
C2
C1

I1
I2
I4
P1
P2 TxD
RxD
1.1 1 1
2.1
D2
E I3 D1
I6
I5
I8
FR I7
Q2

UL
US
FF
BF
Q1
Q3
Q4
1.2 2 2
2.2
rg SF
be UM
Bl om
NC 5
Encoder
25 E/I 07 CNT
28
1 M 00
RS485/422

D-3
PWM

19 .: 27
1.3 2.3
DI

ILC -No /xxx ck:


DO
PWR

er xx
Ord W: 8Blo 3 3
/F r.
HW Add xx ORX
C . W R
MA . xx ION PW
. xx AT
xx OM
T T
AU SE
ET
RE
tage
1.4 2.4
STOP

ES
MR Vol 4 4
X1
G t V
RO Slo 24
N/P
RU V
R 24
PW
G V
PR 24
K DO
LN
DI 5V

M
PW 2
A CT 5/42 24
V
RS
48 5-
V
24
K CN
T 5-
LN
er
od
Enc

T
AC

Figure 2-37 Assignment of the terminal points of connector 6 on the ILC 191 ME/INC

Terminal point Assignment Remark


Connector 6 Input terminal points
1.1 CI11 Clock input status of channel 1
2.1 CI21 Clock input status of channel 2
1.2 CI12 Direction input status of channel 1
2.2 CI22 Direction input status of channel 2
1.3 CI13 Reset input status of channel 1
2.3 CI23 Reset input status of channel 2
1.4 CI14 Enable input status of channel 1
2.4 CI24 Enable input status of channel 2

Up to two counters (counter 1: terminal points 1.1 to 1.4; counter 2: terminal points 2.1 to
2.4) can be used for the evaluation of fast counter pulses. For additional information on the
counters, please refer to Section “Function blocks for counter inputs” on page 105.

Use shielded cables to ensure interference-free counter operation where possible.


Phoenix Contact recommends using the SKS 8-SNS35 shield terminal (Order No.
3062786).

8607_en_06 Phoenix Contact 54 / 185


ILC 191 ME/X

2.21 Incremental encoder inputs

The description of the incremental encoder inputs applies to the ILC 191 ME/INC.

The ILC 191 ME/INC has two incremental encoder inputs.


The incremental encoder inputs are used to detect positions (lengths) and angular positions
with relatively operating encoder systems, i.e., they read in square-wave signals from
incremental encoders. The position values are recorded with a counter which counts up or
down depending on the phase relation of the A and B signals.
Up to two asymmetrical encoders can be connected. The evaluating logic of the controller
detects the direction of rotation of the encoder using the pulse sequence and counts the
pulses accordingly.

INC
PF
A2 1 2
A1
A B2
BS B1
1
C2 Z2
1
C1 2 Z1
FAIL 2
C2

1.1 2.1
C1 3
C2
3
C1 4
RDY C2
C1
4
1 1
RxD
I2 P2 TxD
I1 P1
I4 D2

FR
E I3
I5
I7
I6
I8
D1
1.2 2 2
2.2
Q2
Q1
FF Q4
UL Q3
BF
US
be
rg
Blom/INC 5
UM
SF
1.3 2.3
Encoder

25 E 07 3 3
CNT

28
1 M 00
RS485/422

D-3
PWM

19 .: 27
DI

ILC -No /xxx ck:


DO
PWR

er xx
Ord W: 8Blo
/F r.
HW Add xx ORX
C
MA . xx ION
. xx T
xx OMA
T
. W

T
PW
R
1.4 4 4
2.4
AU SE
RE
ET
tage
STOP

ES
MR Vol
X1
G t V
O Slo 24
N /PR
RU V
R 24
PW
G V
PR 24
K DO
LN
DI 5V

M
PW 2
T 5/42 V
AC 48 5-
24
RS
V
24
K CN
T 5-
LN
er
od
Enc

T
AC

Figure 2-38 Assignment of the terminal points of connector 7 on the ILC 191 ME/INC

Terminal point Assignment Remark


Connector 7 Input terminal points
1.1 A1 Channel A, incremental encoder 1
2.1 A2 Channel A, incremental encoder 2
1.2 B1 Channel B, incremental encoder 1
2.2 B2 Channel B, incremental encoder 2
1.3 Z1 Channel Z, incremental encoder 1
2.3 Z2 Channel Z, incremental encoder 2
1.4, 2.4 FE Functional earth ground

Please note:
An Inline shield plug is required to connect the cables to connector 7, see Section
“Connecting the shield” on page 173.

55 / 185 Phoenix Contact 8607_en_06


Description of the Inline controller

Up to two counters for incremental encoders (counter 1: terminal points 1.1 to 1.3; counter
2: terminal points 2.1 to 2.3) can be used for position detection. For additional information
on the counters, please refer to Section “Function blocks for incremental encoder inputs” on
page 112.

8607_en_06 Phoenix Contact 56 / 185


ILC 191 ME/X

3 The Inline controller under PC Worx/PC Worx Express

3.1 Software version


In order to work with the Inline controller, the following version of
PC Worx/PC Worx Express is required:
PC Worx Version 6.30 or later
Part of the AUTOMATIONWORX Software Suite 2013 1.80
PC Worx Express Version 6.30 or later
Part of the AUTOMATIONWORX Software Suite 2013 1.80

PROFINET device function

The PROFINET device function of the controller is not supported by the PC Worx Express
software.

For information on installing and using PC Worx/PC Worx Express, please refer to the
corresponding quick start guide. It can be downloaded at phoenixcontact.net/products
and is supplied with the software.

57 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.2 Creating a new project


Before making the settings described below, create a new project in the
PC Worx/PC Worx Express software.
• Select the “New Project...” command from the “File” menu to create a new project using
a template.
• In the “New Project” dialog, select the “ILC 191 ME/...” template according to the
version of the Inline controller you are using.
• Save the project using an appropriate name (in the following example in Figure 3-1
“UM_ILC_191_ME”).

Figure 3-1 Project information after creating a new project

8607_en_06 Phoenix Contact 58 / 185


ILC 191 ME/X

3.3 Assigning the IP address for the controller

The procedure for assigning the IP address is essentially the same in PC Worx and
PC Worx Express for all Inline controllers described in this user manual.

By default, the Inline controller has no preset IP address. Initial setting of the IP address can
be carried out with the PC Worx/PC Worx Express software manually via the serial
interface, using the DCP protocol or by means of a BootP server. The IP address can be
changed later with the PC Worx/PC Worx Express software via the serial connection,
Ethernet or the DCP protocol.

3.3.1 Discovery and basic Configuration Protocol (DCP)

The Inline controllers support the DCP protocol from firmware version 4.42 or later and
from AUTOMATIONWORX Software Suite 1.82 AddOn V1).

The IP address is assigned via the DCP protocol in the PC Worx/PC Worx Express software
via the “Device Details” window:
• Select the “IP Settings” tab.
• Enter the IP address of the Inline controller.

Figure 3-2 DCP: setting the IP address

The “IP Assignment” tab is used for actual IP address assignment with DCP.
• Select the “IP Assignment” tab.
After selecting the “IP Assignment” tab, the PROFINET network is searched for DCP
devices.
• Click on “Assign IP” to start IP address assignment with DCP.

59 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Figure 3-3 Starting IP address assignment via DCP

A green status indicator indicates successful IP address assignment.


The PROFINET device name is assigned in the same way.

3.3.2 BootP server


The following example describes IP address assignment using a BootP server in
PC Worx Express for the ILC 191 ME/INC.

Bootstrap protocol In an Ethernet network, BootP is used to assign an IP address to a BootP client using a
(BootP) BootP server. For this example (ILC 191 ME/INC in the default settings), the
ILC 191 ME/INC (BootP client) sends a Boot_Request as a broadcast in the network. The
MAC address of the transmitter is sent with the Boot_Request to provide unique
identification. If the BootP server has been activated in PC Worx Express,
PC Worx Express responds with a Boot_Reply. PC Worx Express uses this Boot_Reply to
inform the ILC 191 ME/INC of its IP address and subnet mask. Please ensure that:
– The BootP server knows the MAC address sent by the BootP client.
– A corresponding IP address and subnet mask have been assigned in PC Worx Express
for the MAC address.
Once the IP data has been transferred to the ILC 191 ME/INC successfully,
PC Worx Express sends a corresponding acknowledgment message.

8607_en_06 Phoenix Contact 60 / 185


ILC 191 ME/X

PC/network adapter To determine whether your network permits the IP settings used in the example project (see
Figure 3-4 on page 61), proceed as follows:
• In the Windows Control Panel, check the settings for your PC network adapter.
• If necessary, adjust these settings so that the ILC 191 ME/INC can be accessed in your
network via the IP address used in the example project.
If your network does not permit the use of the IP address used in the example project, adjust
the settings in the project information accordingly (see Figure 3-1 on page 58).

Changes to project information are not applied automatically


If any modifications are made to the project information (see Figure 3-1) that affect the IP
settings for the controller, a warning is displayed. However, the modification is not
implemented automatically. When a new project is created, the default settings are
specified under “IP Settings” (see on page 62).

Assigning IP settings To set the IP address in PC Worx/PC Worx Express, proceed as described below.

By default, the Inline controller has no preset BootP.

The IP address that is assigned here for the controller is also implemented as the IP
address for the communication path via TCP/IP.

After assigning the IP address, PC Worx Express automatically creates a link via TCP/IP
as a communication path to the Inline controller.

• Establish an Ethernet connection between your PC and the controller.


• Switch to the bus configuration workspace.
• Select the controller node (in the example: “ILC 191 ME/INC”).
• In the “Device Details” window, select the “IP Settings” tab.
• Enter the MAC address of the controller (see Figure 3-4). It is printed on the device
(“00.A0.45.xx.xx.xx”).

PF
O2
O1
A
BS
UA
FAIL

RDY

RxD
I2 P2 TxD
I1 P1
I4 D2
E I3 D1
I6
I5
I8
FR I7
Q2
Q1
FF Q4
UL Q3
BF
US
rg SF
be UM
om N
5 Bl E/A 074
A0
AI

82
32 1 M 00
RS485/422

D-
PWM

19 : 27
DI

ILC -No. /100 :


DO
PWR

er 00 ck
Ord W: 8Blo
/F r.
HW Add xx ORX
C . W R
MA . xx ON PW
. xx TI
xx MA
TO ET
AU
RES
ET
tage
STOP

ES
MR Vol
X1
G t V
RO Slo 24
N/P
RU V
R 24
PW
G V
PR 24
K DO
LN
DI 5V

M
PW 2
T 5/42 V
AC 48 - 10
RS 0
V
10
K AI 0-
LN
A0

T
AC

Figure 3-4 Entering the MAC address

• In the PC Worx Express menu bar, select the


“Extras, BootP/SNMP/TFTP-Configuration...” menu.

61 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Figure 3-5 “Extras, BootP/SNMP/TFTP-Configuration...” menu

• Click on the “Activate BootP” button.

Figure 3-6 “Activate BootP” button

• Perform a cold restart for the controller. To do this, switch the supply voltage off and
then on again after about 2 seconds.
The controller is assigned the IP address which is specified in the project for the controller.
The following message appears in the message window in the “Bus Configurator” tab.

Figure 3-7 Message window following BootP

The IP address is now permanently stored in the internal controller parameterization


memory.

For additional information on setting the IP address with PC Worx/PC Worx Express,
please refer to the quick start guides for the software used.

8607_en_06 Phoenix Contact 62 / 185


ILC 191 ME/X

3.4 The Inline controller as a PROFINET device

Please note that it is only possible to integrate the Inline controller in the PC Worx software
as a PROFINET device.
The PROFINET device function of Inline controllers can also be activated in the
PC Worx Express software.
This section uses an example to describe how to integrate the ILC 191 ME/INC as a
PROFINET device. This procedure also applies to the ILC 191 ME/AN.

The PROFINET-specific system variables can be found in Section 4.8 on page 126.

Activating the PROFINET You can activate the PROFINET device function once you have assigned an IP address for
device function of the the ILC 191 ME/INC as described in Section “Assigning the IP address for the controller” on
ILC 191 ME/INC page 59 (in the following example: 192.168.161.155).
• In the “Device Details” window, select the “PROFINET device activation” item under
“Extended Settings”.
• Under “Settings”, select “PROFINET device activated”.

Figure 3-8 Activating the PROFINET device function

• Click on the “Send” button (hidden by the drop-down list in Figure 3-8).
• In the “Settings Communication Path” dialog, confirm the suggested IP address or the
one you have set according to your application with “OK”.

Figure 3-9 “Settings Communication Path” dialog

63 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Successful execution of the service will be displayed in the status window.

Figure 3-10 Sending PROFINET device function/settings: service executed


successfully

To accept the settings, the controller must be restarted.


• In the “Device Details” window, select the “Ethernet” setting under “Extended Settings”
(see Figure 3-11).
• In the “Activate Network Settings” area, click on the “Restart Controller” button (see
Figure 3-11).

8607_en_06 Phoenix Contact 64 / 185


ILC 191 ME/X

Figure 3-11 Activate Network Settings: Restart Controller

• In the “Settings Communication Path” dialog, confirm the suggested IP address or the
one you have set according to your application with “OK”.

Figure 3-12 “Settings Communication Path” dialog

65 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Successful execution of the service will be displayed in the status window.

Figure 3-13 Activating the network settings: service executed successfully

Now you can read in the ILC 191 ME/INC as a PROFINET device in a PC Worx project.

Integrating the The following section describes how to read in the ILC 191 ME/INC as a PROFINET device
ILC 191 ME/INC as a in the PC Worx software.
PROFINET device

Alternatively, you can also create the PC Worx project by selecting devices from the
device catalog. For additional information on creating a PC Worx project, please refer to
the online help or the quick start guide for the software.

The following conditions apply to the example project:

– Higher-level controller: AXC 1050


– Controller settings:
– IP address: 192.168.161.162
– Subnet mask: 255.255.255.0
– PROFINET device name: axc-10501
– Settings of the ILC 191 ME/INC as a
PROFINET device:
– IP address: 192.168.161.155
– Subnet mask: 255.255.255.0
– PROFINET device name (“DNS Name”): ilc-191me-pnd-8b-0d-ed
You can read in the ILC 191 ME/INC as a PROFINET device after you have done the
following:
– Activated the PROFINET device function of the ILC 191 ME/INC
– Installed the PROFINET controller and the PROFINET devices (ILC 191 ME/INC and
other PROFINET devices according to your application),
– Created a project in PC Worx
– Configured the PROFINET controller according to your application
• In the “Bus Structure” window, select the “Read PROFINET” setting in the PROFINET
context menu.

8607_en_06 Phoenix Contact 66 / 185


ILC 191 ME/X

Figure 3-14 Bus Structure: PROFINET context menu “Read PROFINET...”

The “Read PROFINET” dialog that opens shows the PROFINET devices that have been
detected in the connected network.

Figure 3-15 “Read PROFINET” dialog

• Select the ILC 191 ME/INC and click on the “Insert” button to insert the controller as a
PROFINET device.
• Close the dialog by clicking on the “Close” button.

67 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

The PROFINET device inserted earlier will be displayed in the “Bus Structure” window.

Figure 3-16 ILC 191 ME/INC inserted as a PROFINET device

The process data of the PROFINET device will be displayed on the “Process Data” tab in
the “Device Details” window.

Figure 3-17 ILC 191 ME/INC as a PROFINET device: Process Data

The ILC 191 ME/INC is now available as a PROFINET device in the PC Worx project.

8607_en_06 Phoenix Contact 68 / 185


ILC 191 ME/X

3.5 Setting the realtime clock under PC Worx Express

The procedure for setting the realtime clock is essentially the same in PC Worx and
PC Worx Express. The following example describes the setting in PC Worx Express.

The time and date for the internal system clock of the Inline controller can be set under
“Extended Settings” in the “Device Details” window for the controller in PC Worx Express.

To set the realtime clock, proceed as described in the quick start guide for the
PC Worx Express version used.

3.6 Download Changes


The Inline controller supports the “Download Changes” function.

69 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.7 Functions of the plug-in parameterization memory


(SD card)

The function is available for Inline controllers with firmware versions ≥ 4.42 from
AUTOMATIONWORX Software Suite Version 1.82 AddOn V1.

The plug-in parameterization memory can be used as the main or additional memory.
Figure 3-18 shows how to proceed to use the SD card as the main or additional memory.

Setting in PC Worx:
Preferably, use the SD card inserted before PLC start-up
SD card is main memory
external SD card
SD card inserted after PLC start-up
as main memory

Setting in PC Worx:
Use external SD card SD card inserted before/after PLC start-up
SD card is additional memory
as additional memory
8385A019

Figure 3-18 Procedure for using the SD card as the main or additional memory

Information on using the SD card as the main or additional memory can be found in the
following sections.

3.7.1 Main memory

The function is available for Inline controllers with firmware versions ≥ 4.42 from
AUTOMATIONWORX Software Suite Version 1.82 AddOn V1.

If the SD card is used as the main memory, all application-specific data is stored on the SD
card.
The SD card is recognized during initialization of the Inline controller.
• Make sure that the SD card is inserted before switching on the controller to enable
the controller to use it as the main memory.

Removing the SD card The SD card must not be removed while the Inline controller is running.
during operation

NOTE: Potential data loss


If you remove the SD card during operation, this may result in a loss of data.
• Do not remove the SD card during operation.

8607_en_06 Phoenix Contact 70 / 185


ILC 191 ME/X

Should the SD card be accidentally removed during operation, the Inline controller signals
an error, stops processing the application program, and switches to the READY state. The
FAIL LED indicates an error. If an online connection to PC Worx is established, the message
window indicates that the SD card was unintentionally inserted or removed.

Changing operating For changing modes (operating the Inline controller with/without SD card), please note the
modes following:

Change: operation without To change the Inline controller mode from “operation without SD card” to “operation with SD
SD card  operation with card”, proceed as follows:
SD card • Switch off the supply voltage of the Inline controller.
• Insert the SD card; see Section 2.8.1 “Inserting/removing the parameterization
memory”.
• Switch on the supply voltage of the Inline controller.

NOTE: Deletion of all data in the internal parameterization memory


When the Inline controller is switched on, all application-specific data is deleted from the
internal parameterization memory. PC Worx projects and IP configurations stored on the
parameterization memory are no longer available.
The Inline controller accesses the data stored on the SD card.

Change: operation with SD To change the Inline controller mode from “operation with SD card” to “operation without SD
card  operation without card”, proceed as follows:
SD card • Switch off the supply voltage of the Inline controller.
• Remove the SD card; see Section 2.8.1 “Inserting/removing the parameterization
memory”.
• Switch on the supply voltage of the Inline controller.

NOTE: No data on the internal parameterization memory


Once the Inline controller has been operated with the SD card, there is no data available
on the internal parameterization memory. The Inline controller therefore does not have an
IP address.
• Assign an IP address to the Inline controller as described in Section 3.3.

Settings in PC Worx Figure 3-19 shows the settings in PC Worx for using the SD card as the main memory.

Figure 3-19 Setting the SD card as the main memory

• In the “Device Details” window, select the “Use of external SD card” setting under
“Extended Settings”.

71 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

• Under “Settings”, select the “Preferably, use the external SD card as main memory”
setting in the drop-down list.
• Click on the “Send” button (hidden by the drop-down list in Figure 3-19) to send the
setting to the Inline controller.
• Restart the Inline controller.

Default setting The “Preferably, use the external SD card as main memory” setting is activated by default
in PC Worx.
If you do not change this setting the following applies:
– If the SD card is already inserted before starting up the Inline controller (see also
Figure 3-18 on page 70), the SD card is used as the main memory. All application-
specific data is stored on the SD card.
– If the SD card is inserted after starting up the Inline controller (see also Figure 3-18 on
page 70), the SD card is used as the additional memory (see Section 3.7.2). All
application-specific data is stored on the internal parameterization memory of the Inline
controller.

3.7.2 Additional memory

The function is available for Inline controllers with firmware versions ≥ 4.42 from
AUTOMATIONWORX Software Suite Version 1.82 AddOn V1.

WARNING: Explosion hazard


In potentially explosive areas, the SD card must not be used as additional memory. Use
the SD card as main memory only. Don't insert or remove the SD card during operation.
If the SD card is used as the additional memory, all application-specific data is stored on the internal parameterization memory of the Inline controller. If you are using an SD card with license key, the license
is still used.

NOTE: Function blocks are no longer executed under certain circumstances


If an SD card with license keys for function block libraries (SD FLASH XXX APPLIC A) is
removed from the Inline controller for more than 60 minutes, function blocks that require a
license can no longer be executed under certain circumstances.
If the SD card is removed and reinserted into the Inline controller within 60 minutes, all
function blocks continue to be executed.
• Never remove an SD card with license keys for function block libraries from the Inline
controller for more than 60 minutes.

Use as additional memory The SD card is used as additional memory (see also Figure 3-18 on page 70) if
– the SD card is inserted after starting up the Inline controller
or
– you have selected the “Use external SD card as additional memory” setting (default
setting) in PC Worx.

Inserting/removing the SD The SD card may be inserted or removed before starting up or while operating the Inline
card controller.

NOTE: Potential data loss


If you remove the SD card while read and/or write access to the SD card is active, this may
result in a loss of data.
• Only remove the SD card when it is not being accessed.

Settings in PC Worx Figure 3-20 shows the settings in PC Worx for using the SD card as the additional memory.

8607_en_06 Phoenix Contact 72 / 185


ILC 191 ME/X

Figure 3-20 Setting the SD card as the additional memory

• In the “Device Details” window, select the “Use of external SD card” setting under
“Extended Settings”.
• Under “Settings”, select the “Use external SD card as additional memory” setting in the
drop-down list.
• Click on the “Send” button (hidden by the drop-down list in Figure 3-20) to send the
setting to the Inline controller.
The Inline controller must be restarted to apply the setting.

73 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.7.2.1 SD card as the memory for log files


You can use the SD card as the memory for log files.
The content of the “cfroot” directory is shown in the “sddisk” directory on the SD card. You
can view the directories on the SD card if you access the Inline controller via FTP (see
Section “Parameterization memory and Internet Explorer” on page 76).

Figure 3-21 “sddisk” directory on the SD card

We recommend that you create a new directory within the “sddisk” directory to store log
files.
• Access the Inline controller via FTP.
• Double-click to open the “sddisk” directory.
• In the “sddisk” directory, right-click to open the context menu and select “New, Folder”.
• Enter a name for the new directory (in the example in Figure 3-22 “Logfile”).

Figure 3-22 Newly created “Logfile” directory in the “sddisk” directory

8607_en_06 Phoenix Contact 74 / 185


ILC 191 ME/X

To access the directories on the SD card, use the FILE function blocks in PC Worx (see
Section 3.13 and online help for PC Worx).
When you program your application program, the log data in the “Logfile.txt” file will be
saved and stored in the “Logfile” directory. You can then access the file using the
FILE_OPEN function block.
Figure 3-23 shows a FILE_OPEN function block for opening the “Logfile.txt” file in the
“\sddisk\Logfile” directory.

Figure 3-23 Opening the “Logfile.txt” file using the FILE_OPEN function block

In the “Variable Properties” dialog (shown on the right in Figure 3-23) always enter the
complete path and the file name.

75 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.8 Parameterization memory and Internet Explorer


To delete files or store user-specific files on the internal parameterization memory, proceed
as follows:

The FTP functionality must be activated in Internet Explorer. See Section “Internet
Explorer FTP functionality” on page 77.

• Switch to the bus configuration workspace in PC Worx.


• Select the controller, e.g., “ILC 191 ME/AN”, in the “Bus Structure” window.
• Select the “Extended Settings” tab in the “Device Details” window.
• Open Internet Explorer from this window by clicking on the “Open FTP Folder on
Device” button.

Figure 3-24 Extended Settings: Open FTP Folder on Device

The file structure, which is stored on the parameterization memory, is displayed in the
Internet Explorer window.

Data may only be copied or deleted on the parameterization memory. Do not edit any files
as Internet Explorer does not store modified data.
For the current state to be displayed, refresh the display after every action by means of the
“View, Refresh” command.

8607_en_06 Phoenix Contact 76 / 185


ILC 191 ME/X

3.8.1 Internet Explorer FTP functionality


• Activate this setting in Internet Explorer under “Tools, Internet Options, Advanced”.

Figure 3-25 Internet Options: Enable FTP folder view

77 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.8.2 Activating/deactivating the FTP server


To protect the Inline controller against unauthorized access, it may be necessary to
deactivate the FTP server. The CPU_Set_Value_Request service with Var ID 0172hex is
used for this. The FTP server can be activated or deactivated with this service. The FTP
server is deactivated as soon as the applicable service has been executed.
When you activate the FTP server, the setting is only applied after restarting the controller.
Value range for the CPU_Set_Value_Request service:

Var Count 1
Var ID 0172hex
Value 0000hex Deactivate FTP server
0001hex Activate FTP server

Figure 3-26 Deactivating the FTP server

8607_en_06 Phoenix Contact 78 / 185


ILC 191 ME/X

3.8.3 Restricting FTP access

The function is available for Inline controllers with firmware versions ≥ 4.42 from
AUTOMATIONWORX Software Suite Version 1.82 AddOn V1.

To prevent unauthorized FTP access to the parameterization memory, you can define a
user name (max. twelve characters) and a password (max. twelve characters). By default
upon delivery, the user name for the Inline controller is set to “anonymous” and there is no
password (“”). This setting is also restored when you reset the Inline controller to the delivery
state.
The CPU_Set_Value_Request service with Var ID 019Ahex is used to define a user name
and password.

Defining a user name and To define a user name and password, proceed as follows:
password • Switch to the bus configuration workspace in PC Worx.
• In the “Bus Structure” window, select the controller, e.g., “ILC 191 ME/INC”.
• In the “Device Details” window, select the “CPU Service Editor” tab.
• Open the “ILC1xx_Service_Common.slb” library.
• Double-click to select the CPU_Set_Value_Request service.

Figure 3-27 Opening the library and selecting the service

• Under “CPU Request” enter the value “1” for (* Var Count *).
• Under “CPU Request” enter the value “019A” for (* Var ID ... *).
• Under “CPU Request” enter the desired user name and password for (* Value ... *) (in
Figure 3-28 changed to (* length username & username *) and (* length password &
password *)).
Here the length of the user name must be entered first, followed by the individual characters
of the user name in hexadecimal ASCII format. Then the length of the password must be
entered, followed by the individual characters of the password in hexadecimal ASCII format.

79 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Example (see Figure 3-28): user name “USER” (length “04”), password “PASS” (length
“04”)

Charac- ASCII Charac- ASCII


ter ter
U 55 P 50
S 53 A 41
E 45 S 53
R 52 S 53
For the example shown, the ASCII characters “0455 5345 52” (length of the user name
followed by the individual characters of the user name) must be entered for the user name
“USER” followed by the ASCII characters “04 5041 5353” (length of the password followed
by the individual characters of the password) for the password “PASS”.
Figure 3-28 shows the settings for defining the user name “USER” and the password
“PASS” under “CPU Request”.

Figure 3-28 Defining a user name and password for FTP access

• Click on the “Send” button to send the settings to the Inline controller.
The new user name and password are set.
The successful execution of the service is acknowledged under “CPU Confirmation” as
follows:
<Cnf: CPU_Set_Value_Request>
82CB (*W1 : Confirmation_Code*)
0001 (*W2 : Parameter_Count*)
0000 (*W3 : Result*)

• Reset the Inline controller voltage.

8607_en_06 Phoenix Contact 80 / 185


ILC 191 ME/X

When accessing the parameterization memory via FTP, a dialog now appears in which the
user name and password must be entered.
The content of the parameterization memory is only displayed if the user name and
password entered are correct.

Recommendation:
If you wish to access the parameterization memory via a web browser, deactivate the web
browser's cache.
Otherwise the content of the parameterization memory may be displayed even if access
protection has been activated, if, for example, data from the last time the memory was
accessed without access protection is still stored in the web browser's cache.

Removing the user name To remove the user name and password, proceed as described above but under “CPU
and password Request” enter the value “0000” for (* Value ... *); see Figure 3-29.

Figure 3-29 Removing the user name and password for FTP access

81 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.8.4 Activating/deactivating the HTTP server

This function is supported by Inline controllers from firmware version 4.42 or later and from
AUTOMATIONWORX Software Suite 1.82 AddOn V1.

Disable To protect the Inline controller against unauthorized access, it may be necessary to disable
the HTTP server. To do this, proceed as follows:
• Switch to the bus configuration workspace in PC Worx.
• In the “Bus Structure” window, select the controller, e.g., “ILC 191 ME/AN”.
• Select the “Extended Settings” tab in the “Device Details” window.
• Under “Extended Settings” select the “Web server” setting.
• Select the “Disabled” setting from the drop-down list.
• Click on the “Send” button (hidden by the drop-down list in Figure 3-30) to send the
setting to the Inline controller.
• Restart the Inline controller.

Figure 3-30 Disabling HTTP

Once you have selected the “Disabled” setting, the HTTP server (web server) will be
disabled. HTTPS (see Section 3.8.5) will also be disabled.

Enable Proceed as follows to enable the HTTP server:


• In the drop-down list select the setting “HTTP (Port 80)”.
• Click on the “Send” button (hidden by the drop-down list in Figure 3-30) to send the
setting to the Inline controller.
• Restart the Inline controller.

From the WebVisit software, access to the Inline controller's web server is possible via
HTML5.

8607_en_06 Phoenix Contact 82 / 185


ILC 191 ME/X

3.8.5 Using the Hypertext Transfer Protocol Secure (HTTPS)

The Hypertext Transfer Protocol Secure (HTTPS) is supported by Inline controllers from
firmware version 4.42 or later and AUTOMATIONWORX Software Suite 1.82 AddOn V1.

The Hypertext Transfer Protocol Secure (HTTPS) can be used for HTTP server
communication.
The settings to use HTTPS are made via the “Device Details” window.
• Switch to the bus configuration workspace in PC Worx.
• Select the controller, e.g., “ILC 191 ME/AN”, in the “Bus Structure” window.
• Select the “Extended Settings” tab in the “Device Details” window.
• Under “Extended Settings” select the “Web server” setting.
• In the drop-down list select the setting “HTTPS (Port 443)”.
• Click on the “Send” button (hidden by the drop-down list in Figure 3-31) to send the
setting to the Inline controller.
• Restart the Inline controller.

Figure 3-31 Setting HTTPS

3.9 Sending e-mails securely


You can use the SMTPS method (e-mailing via SMTP with SSL/TLS) for secure e-mailing.
In order to use the SMTPS method, you need to import the IT library (≥ version 1_35)
function block library. It can be downloaded via the product at phoenixcontact.net/products.
For more detailed information about the function block library, please refer to the online help
for PC Worx.

Security certificates from the mail server are always accepted unchecked by the Inline
controller.

83 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.10 Activating/deactivating specific ports

The function is available for Inline controllers with firmware versions ≥ 4.42 from
AUTOMATIONWORX Software Suite Version 1.82 AddOn V1.

Depending on your application, it may be necessary to deactivate specific ports. The


CPU_Set_Value_Request service is used for this, with different Var IDs for the individual
ports. A port can be activated or deactivated with this service. The port is deactivated as
soon as the applicable service has been executed.
When you activate a port, the setting is only applied after restarting the controller.

Port 7 Value range for the CPU_Set_Value_Request service for port 7 (port for echo server):

Var Count 1
Var ID 0214hex
Value 0000hex Deactivate port 7
0001hex Activate port 7

If you deactivate port 7, the Inline controller will not be found by the AX OPC Server.

Port 1962 Value range for the CPU_Set_Value_Request service for port 1962 (port for communication
with PC Worx):

Var Count 1
Var ID 0213hex
Value 0000hex Deactivate port 1962
0001hex Activate port 1962

Port 41100 Value range for the CPU_Set_Value_Request service for port 41100 (port for OPC and
debug mode in PC Worx):

Var Count 1
Var ID 0192hex
Value 0000hex Deactivate port 41100
0001hex Activate port 41100

NOTE: No access to the Inline controller


If you deactivate port 1962 and/or port 41100, you will no longer be able to access the
Inline controller from PC Worx.
• Only deactivate port 1962 and/or port 41100 if you no longer need to access the Inline
controller from PC Worx.
Once you have deactivated port 1962 and/or port 41100, these can only be reactivated by
resetting the Inline controller to the default settings.

8607_en_06 Phoenix Contact 84 / 185


ILC 191 ME/X

3.11 Activating/deactivating the journaling function


The file system of the Inline controller supports the journaling function. As a result, voltage
failures during write processes do not destroy the file system; however, the access speed
becomes slower.

The journaling function is deactivated by default.

It can be activated or deactivated via the CPU_Set_Value_Request service with


Var ID 0194hex.
Value range for the CPU_Set_Value_Request service:
Code 02CBhex
Var Count 0001hex
Var ID 0194hex
Value 0001hex Activate journaling function
0000hex Deactivate journaling function

Figure 3-32 Activating the journaling function

85 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.12 Activating/deactivating the MRP client function


The Media Redundancy Protocol (MRP) can be used via the Ethernet interfaces of the
ILC 191 ME/AN and ILC 191 ME/INC Inline controllers. The controllers support the MRP
client function, which can be enabled or disabled via PC Worx as an option. This function is
disabled by default. If the function is enabled, it remains enabled after the supply voltage is
switched off and on. If the controllers have been reset to the delivery state, the MRP client
function will also be disabled again. In a ring with Media Redundancy Protocol, maximum
switch-over times of up to 200 ms can be expected.
To activate/deactivate the MRP client function, proceed as follows:
• Switch to the bus configuration workspace.
• Select the controller node (in the example: “ILC 191 ME/AN” 192.168.0.2).
• Select the “Extended Settings” tab in the “Device Details” window.
• In the “Device Details” window, select the “MRP client” setting under “Extended
Settings”.
• Under “Settings”, select “activated” to activate the MRP client function.
or
• Under “Settings”, select “deactivated” to deactivate the MRP client function.
• Click on the “Send” button.

Figure 3-33 Activating the MRP client function

8607_en_06 Phoenix Contact 86 / 185


ILC 191 ME/X

3.13 Function blocks for handling files on the


parameterization memory
The function blocks are used to access files from within the application program. Some of
the blocks support multiple instantiation. This means that it is possible to work with a number
of different files within the same project. The blocks perform the standard functions that are
required for typical file access operations.
The FILE_NOTIFY block is available in addition to the blocks for typical file access
operations. This block can be used to detect files that have been modified in a directory
containing user files. These modifications may include:
– Deletion of one or more files
– Writing one or more new files
– Modification of one or more existing files
Both modifications made to this directory via FTP (remote) and modifications made locally
via function blocks or firmware services can be detected.

All file operations are subject to the following restrictions:


No directory hierarchies are supported. All file operations only affect the root directory of
the parameterization memory.

Table 3-1 Overview of the function blocks

Function block Short description


FILE_OPEN Opens a file with a specific name
FILE_CLOSE Closes a file with a specific handle
FILE_READ Reads from a file with a specific handle
FILE_WRITE Writes to a file with a specific handle
FILE_REMOVE Deletes a file with a specific name
FILE_TELL Determines the current position of the file pointer in a file
FILE_SEEK Moves the current file pointer to a new position
FILE_NOTIFY Displays files that have recently been created, deleted or mod-
ified

The function blocks for handling files on the parameterization memory are described in the
PC Worx online help.

87 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.14 Function blocks for Ethernet communication


The function blocks are used to establish Ethernet communication between two
communication partners.
The IP communication blocks listed below enable IEC 61131-5-compliant communication
between controllers via Ethernet or communication between controllers and Ethernet
devices via TCP/IP or UDP/IP.
Implement all time and connection monitoring in the application program.
The function blocks support a maximum of 8 TCP/IP or UDP/IP communication
connections:

Table 3-2 Overview of the function blocks

Function block Short description


IP_CONNECT Establishes a connection between two communication partners
IP_USEND Sends data to a communication partner
IP_URCV Receives data from a communication partner

The communication blocks are described in the PC Worx online help.


The extensions for the TCP/IP and UDP/IP function blocks are described in the “TCP/UDP
COMMUNICATION” application note.

3.15 Function blocks for PCP communication


The function blocks are used to establish PCP communication between the Inline controller
and PCP devices in INTERBUS.
The Inline controller supports connections to a maximum of 24 PCP devices.

Table 3-3 Overview of the function blocks

Function block Short description


PCP_CONNECT This block can be used to set up communication connections to
each PCP device in INTERBUS.
PCP_WRITE This block enables PCP objects to be written.
PCP_READ This block enables data to be read from PCP objects.
PCP_SERVER This block enables PCP service indications to be received and
responses to be sent.

The communication blocks are described in the PC Worx online help.

8607_en_06 Phoenix Contact 88 / 185


ILC 191 ME/X

3.16 Function blocks for pulse width modulation


The PULSE_CH1 and PULSE_CH2 function blocks are used to perform the PWM,
frequency generator or pulse/direction interface functions.

Figure 3-34 PULSE_CH1 function block

Table 3-4 Inputs of the PULSE_CH1 and PULSE_CH2 function blocks

Name Data type Description


REQUEST BOOL Enabling of output signal PWMO1 or PWMO2.
TRUE: Signal PWMO1 or PWMO2 is output according to the set parame-
ters.
FALSE: Signal PWMO1 or PWMO2 is not output. Instead a 0 signal is out-
put at output PWMO1 or PWMO2.

89 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Table 3-4 Inputs of the PULSE_CH1 and PULSE_CH2 function blocks

Name Data type Description


FREQUENCY UDINT Frequency of the PWM signal in Hz.
Value range: 0 ... 150000
If value 0 is selected for FREQUENCY, a static 1 signal is output. The DUTY_-
CYCLE parameter is ignored.
For all other combinations of FREQUENCY and DUTY_CYCLE the following
upper limit applies:
0,33 μs < DUTY_CYCLE
FREQUENCY  100
PULSE_CNT UDINT Number of pulses to be output.
A positive edge at the REQUEST input means that the number of pulses spec-
ified here will be output at output P1 or P2. If the specified number of pulses
is changed during runtime, the change does not take effect until the next pos-
itive edge at the REQUEST input.
If a FALSE signal is present at the REQUEST input, pulse output is stopped.
On a new positive edge at the REQUEST input, output of the set pulses starts
again.
Value range: 0...232 - 1
If value 0 is selected for PULSE_CNT, pulses are output continuously.
DUTY_CYCLE UINT Pulse/pause ratio (pulse duty factor) of output signal PWMO1 or PWMO2
Value range: 0 ... 100
If value 0 is selected for DUTY_CYCLE, a 0 signal is output at output P1 or P2.
If value 50 is selected for DUTY_CYCLE, a square-wave signal is output at
output P1 or P2.
If value 100 is selected for DUTY_CYCLE, a static 1 signal is output at output
P1 or P2.
The upper limit applies to the combination of FREQUENCY and DUTY_CY-
CLE
0,33 μs < DUTY_CYCLE
FREQUENCY  100

Table 3-5 Outputs of the PULSE_CH1 and PULSE_CH2 function blocks

Name Data type Description


DONE BOOL TRUE: The function block has been executed successfully, the number of
pulses set under PULSE_CNT has been output.
FALSE: The set number of pulses to be output has not been reached yet or
a FALSE signal is present at the REQUEST input.

8607_en_06 Phoenix Contact 90 / 185


ILC 191 ME/X

Table 3-5 Outputs of the PULSE_CH1 and PULSE_CH2 function blocks

Name Data type Description


ERROR BOOL TRUE: An error has occurred. Details are provided by the STATUS output.
FALSE: No error. STATUS contains the current value of the internal pro-
cessing.
STATUS WORD Error value of the function block (see Table 3-6).
CV UDINT Number of pulses currently output.
If CV=PULSE_CNT, an event task can be triggered. In order to use this func-
tion, an event task must be defined and the corresponding “Number of pulses
reached Px” event must be selected.

Figure 3-35 Selecting the “Number of pulses reached Px” event

For information on event tasks, please refer to the online help


for the PC Worx software.

STATUS output
(ERROR = TRUE)
Table 3-6 Error values of the STATUS output (ERROR = TRUE)

Value Status
0001hex Invalid value at the FREQUENCY input
0002hex Invalid value at the PULSE_CNT input
0004hex Invalid value at the DUTY_CYCLE input
0x08hex Invalid combination of values at the FREQUENCY and DUTY_CYCLE
inputs

Behavior of the pulse/direction interface on Download Changes


If the parameters at the PULSE_CH1 and PULSE_CH2 function blocks are modified by a
Download Changes process, these parameters are applied immediately during runtime.
The PULSE_CNT parameter is an exception, as this parameter requires a rising edge at the
REQUEST input in order to be applied.

Behavior of the pulse/direction interface when the controller operating mode is


changed
When changed to STOP mode, pulse output is immediately interrupted. When changed to
RUN mode, the parameters at the PULSE_CH1 and PULSE_CH2 function blocks are read
in and the function blocks are executed.

91 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Signal sequence diagrams

Signal
REQUEST

DONE

Figure 3-36 Signal curve when the REQUEST input is set to FALSE too early (the DONE
output is only TRUE for one cycle)

Key:
1 Signal curve at output P1/P2 (PULSE_CNT parameter = 0)
2 FREQUENCY parameter = 2
3 FREQUENCY parameter = 4
Signal

REQUEST

DONE

Figure 3-37 Signal curve when the output signal frequency is changed

Key:
1 Signal curve at output P1/P2 (PULSE_CNT parameter = 5)
2 FREQUENCY parameter = 2
3 FREQUENCY parameter = 4
4 Output status of the PWM signal (processing carried out)
Signal

REQUEST

DONE

Figure 3-38 Signal curve when the value specified at the PULSE_CNT input is reached
(the DONE output is only TRUE for one cycle)

Key:
1 Signal curve at output P1/P2 (PULSE_CNT parameter = 4)
2 Output status of the PWM signal (processing carried out)

8607_en_06 Phoenix Contact 92 / 185


ILC 191 ME/X

Signal
REQUEST

DONE

Figure 3-39 Signal curve when the output signal frequency is changed and output is
continuous (PULSE_CNT = 0)

Key:
1 Signal curve at output P1/P2 (PULSE_CNT parameter = 4)

3.17 Function blocks for RS-232 communication

3.17.1 RS232_INIT function block

Figure 3-40 RS232_INIT function block

The RS232_INIT function block is used to parameterize the serial RS-232 interface.
Once the RS232_INIT function block has been parameterized correctly, data is sent and
received using the RS232_SEND (see Section 3.17.2) and RS232_RECEIVE (see
Section 3.17.3) function blocks.

If the RS232_INIT function block is activated, the RS-232 interface cannot be used to
assign the IP address of the Inline controller or to work with Diag+.
In this case, IP address assignment or work with Diag+ is only made possible again when:
– The RS232_INIT function block is deactivated
– Or a new cold restart or warm start is performed for the Inline controller

93 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Table 3-7 Inputs of the RS232_INIT function block

Name Data type Description


ENABLE BOOL The function block is activated on a positive edge at this input. The RS-232
interface is initialized with the values specified under PARAMETER.
PARAMETER T_RS232 Initialization parameter
This input can be used to specify the following parameters of the serial inter-
face:
– Protocol: transparent
– Baud rate: 1200, 2400, 4800, 9600, 19200, 38400, 57600 or 115200
– Data width: 8 data bits, parity: even (default setting), odd, none
– Number of stop bits: 1 (default setting), 2
– Hardware flow control: off (0 (default setting)), on (1)

The RTS and CTS signals are used for hardware flow control.

For the data structure of the T_RS232 input parameter, please


refer to the online help for the function block in the
PC Worx/PC Worx Express software.

Table 3-8 Outputs of the RS232_INIT function block

Name Data type Description


VALID BOOL Parameterization status of the function block
TRUE: The function block has been parameterized without errors. The
function block is executed.
FALSE: Error in the parameterization of the function block.
ERROR BOOL TRUE: An error has occurred. Details are provided by the STATUS output.
FALSE: No error. STATUS contains the current value of the internal pro-
cessing.
STATUS WORD Error value of the function block (see Table 3-9).

STATUS output
(ERROR = TRUE)
Table 3-9 Status values of the STATUS output (ERROR = TRUE)

Value Status
0x0101 Wrong data type applied to PARAMETER input
0x0102 Data type information not available
0x0103 The data type does not correspond to the specification of the T_RS232
data structure
0x0104 The T_RS232 data structure contains an error
0x0105 Multiple instantiation prohibited
0x0160 Unknown protocol

8607_en_06 Phoenix Contact 94 / 185


ILC 191 ME/X

Table 3-9 Status values of the STATUS output (ERROR = TRUE)


Value Status
0x0161 Unknown baud rate
0x0162 Unknown number of data bits
0x0163 Unknown number of stop bits
0x0164 Unknown flow control
0x020x Incorrect elements in the data type of the T_RS232 data structure.
x indicates the position of the incorrect element in the PARAMETER pa-
rameter.

3.17.2 RS232_SEND function block


The RS232_SEND function block is used to send data via the RS-232 interface.

Figure 3-41 RS232_SEND function block

Table 3-10 Input of the RS232_SEND function block

Name Data type Description


REQUEST BOOL The function block is executed on a positive edge at this input. The data
present at the DATA input is transmitted via the RS-232 interface.

Table 3-11 Outputs of the RS232_SEND function block

Name Data type Description


DONE BOOL A positive edge at this output indicates that the function block has been
executed and data has been sent via the RS-232 interface.
ERROR BOOL TRUE: An error has occurred. Details are provided by the STATUS
output.
FALSE: No error. STATUS contains the current value of the internal
processing.
STATUS WORD Status value of the function block (see Table 3-12)

95 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Table 3-11 Outputs of the RS232_SEND function block


Name Data type Description
BUFFER_EMPTY BOOL TRUE: The send buffer of the RS-232 interface is empty. There are no
more characters left to send.
FALSE: There is still at least one character left to send in the send buf-
fer of the RS-232 interface.
SEND_BUFFER_COUNT INT Number of characters (still) in the send buffer.
DATA_COUNT INT Number of characters to be written. The number must correspond to the
size of the DATA byte array.
DATA ARRAY OF Send buffer that contains the characters to be transmitted.
BYTE

STATUS output
(ERROR = TRUE)
Table 3-12 Status values of the STATUS output (ERROR = TRUE)

Value Status
0x0102 Data type information not available
0x0105 Multiple instantiation prohibited
0x0107 RS232_INIT not executed successfully
0x0121 No byte array connected to DATA
0x0123 The number of bytes to be sent specified with DATA_COUNT exceeds
the internal send buffer
0x0125 The DATA send buffer is full.

8607_en_06 Phoenix Contact 96 / 185


ILC 191 ME/X

3.17.3 RS232_RECEIVE function block


The RS232_RECEIVE function block is used to receive data via the RS-232 interface.

Figure 3-42 RS232_RECEIVE function block

Table 3-13 Input of the RS232_RECEIVE function block

Name Data type Description


REQUEST BOOL The function block is executed on a positive edge at this input. The data
is transmitted from the receive buffer of the RS-232 interface to the
DATA parameter.

Table 3-14 Outputs of the RS232_RECEIVE function block

Name Data type Description


DONE BOOL A positive edge at this output indicates that the function block has been
executed and data has been received via the RS-232 interface.
ERROR BOOL TRUE: An error has occurred. Details are provided by the STATUS
output.
FALSE: No error. STATUS contains the current value of the internal
processing.
STATUS WORD Status value of the function block (see Table 3-15)
BUFFER_NOT_EMPTY BOOL TRUE: There is at least one character left to read in the receive buffer
of the RS-232 interface.
FALSE: The receive buffer of the RS-232 interface is empty. There are
no more characters left to read.

97 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Table 3-14 Outputs of the RS232_RECEIVE function block


Name Data type Description
BUFFER_FULL BOOL TRUE: The receive buffer of the RS-232 interface is full. No more
characters can be received.
FALSE: The receive buffer of the RS-232 interface is not full yet. More
characters can be received.
RECEIVE_BUFFER_COUNT INT Amount of data in the receive buffer.
DATA_COUNT INT Amount of data that has been transmitted from the receive buffer to the
DATA parameter.
DATA ARRAY OF Receive buffer which contains the received characters.
BYTE

STATUS output
(ERROR = TRUE)
Table 3-15 Status values of the STATUS output (ERROR = TRUE)

Value Status
0x0102 Data type information not available
0x0105 Multiple instantiation prohibited
0x0107 RS232_INIT not executed successfully
0x0121 The DATA parameter is not linked
0x0124 Receive buffer does not contain any characters

8607_en_06 Phoenix Contact 98 / 185


ILC 191 ME/X

3.18 Function blocks for RS-485/RS-422


communication

3.18.1 RS485_422_INIT function block

Figure 3-43 RS485_422_INIT function block

The RS485_422_INIT function block is used to parameterize the serial RS-485 interface.
Once the RS485_422_INIT function block has been parameterized correctly, data is sent
and received using the RS485_422_SEND (see Section 3.18.2) and
RS485_422_RECEIVE (see Section 3.18.3) function blocks.

Table 3-16 Inputs of the RS485_422_INIT function block

Name Data type Description


ENABLE BOOL The function block is activated on a positive edge at this input. The RS-
485/RS-422 interface is initialized with the values specified under PARAME-
TER.
COM INT Specification of the COM port. Select the value 1 for the Inline controller.
PARAMETER T_RS485_422 Initialization parameter
This input can be used to specify the following parameters of the serial inter-
face:
– Protocol: transparent, data transmission: full duplex (default setting), half
duplex
– Baud rate: 1200, 2400, 4800, 9600, 19200, 38400, 57600 or 115200
– Data width: 8 data bits, parity: none, even (default setting), odd
– Number of stop bits: 1 (default setting), 2
– Hardware flow control: none

For the data structure of the T_RS485_422 input parameter,


please refer to the online help for the function block in the
PC Worx/PC Worx Express software.

99 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Table 3-17 Outputs of the RS485_422_INIT function block

Name Data type Description


VALID BOOL Parameterization status of the function block.
TRUE: The function block has been parameterized without errors. The
function block is executed.
FALSE: Error in the parameterization of the function block.
ERROR BOOL TRUE: An error has occurred. Details are provided by the STATUS output.
FALSE: No error. STATUS contains the current value of the internal pro-
cessing.
STATUS WORD Error value of the function block (see Table 3-18).

STATUS output
(ERROR = TRUE)
Table 3-18 Status values of the STATUS output (ERROR = TRUE)

Value Status
0x0101 Wrong data type applied to PARAMETER input
0x0102 Data type information not available
0x0103 The data type does not correspond to the specification of
T_RS485_422
0x0104 The T_RS485_422 data type contains an error
0x0105 Multiple instantiation prohibited
0x0160 Unknown protocol
0x0161 Unknown baud rate
0x0162 Unknown number of data bits
0x0163 Unknown number of stop bits
0x0164 Unknown flow control
0x020x Incorrect elements in the data type of the T_RS485_422 data structure.
x indicates the position of the incorrect element in the PARAMETER pa-
rameter.

8607_en_06 Phoenix Contact 100 / 185


ILC 191 ME/X

3.18.2 RS485_422_SEND function block


The RS485_422_SEND function block is used to send data via the RS-485/RS-422
interface.

Figure 3-44 RS485_422_SEND function block

Table 3-19 Inputs of the RS485_422_SEND function block

Name Data type Description


REQUEST BOOL The function block is executed on a positive edge at this input. The data
present at the DATA input is transmitted via the RS-485/RS-422 interface.
COM INT Specification of the COM port. Select the value 1 for the Inline controller.

Table 3-20 Outputs of the RS485_422_SEND function block

Name Data type Description


DONE BOOL A positive edge at this output indicates that the function block has been
executed and data has been sent via the RS-485/RS-422 interface.
ERROR BOOL TRUE: An error has occurred. Details are provided by the STATUS
output.
FALSE: No error. STATUS contains the current value of the internal
processing.
STATUS WORD Status value of the function block (see Table 3-21)
BUFFER_EMPTY BOOL TRUE: The send buffer of the RS-485-/RS-422 interface is empty.
There are no more characters left to send.
FALSE: There is still at least one character left to send in the send buf-
fer of the RS-485/RS-422 interface.
SEND_BUFFER_COUNT INT Number of characters (still) in the send buffer.
DATA_COUNT INT Number of characters to be written. The number must correspond to the
size of the DATA byte array.
DATA ARRAY OF Send buffer that contains the characters to be transmitted.
BYTE

101 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

STATUS output
(ERROR = TRUE)
Table 3-21 Status values of the STATUS output (ERROR = TRUE)

Value Status
0x0102 Data type information not available
0x0105 Multiple instantiation prohibited
0x0107 RS485_422_INIT not executed successfully
0x0121 No byte array connected to DATA
0x0123 The number of bytes to be sent specified with DATA_COUNT exceeds
the internal send buffer
0x0125 The DATA send buffer is full.

Signal sequence diagram


Signal

REQUEST

DONE

Figure 3-45 Signal sequence when REQUEST = TRUE

Key:
1 Data signal when DATA_COUNT parameter = 4
2 REQUEST = TRUE
3 Positive edge at the DONE output; the four characters to be sent have been sent via the
RS-485/RS-422 interface

8607_en_06 Phoenix Contact 102 / 185


ILC 191 ME/X

3.18.3 RS485_422_RECEIVE function block

Figure 3-46 RS485_422_RECEIVE function block

Table 3-22 Inputs of the RS485_422_RECEIVE function block

Name Data type Description


REQUEST BOOL The function block is executed on a positive edge at this input. The data
is transmitted from the receive buffer of the RS-485/RS-422 interface to
the DATA parameter.
COM INT Specification of the COM port. Select the value 1 for the Inline controller.

Table 3-23 Outputs of the RS485_422_RECEIVE function block

Name Data type Description


DONE BOOL A positive edge at this output indicates that the function block has been
executed and data has been received via the RS-485/RS-422 interface.
ERROR BOOL TRUE: An error has occurred. Details are provided by the STATUS
output.
FALSE: No error. STATUS contains the current value of the internal
processing.
STATUS WORD Status value of the function block (see Table 3-24)
BUFFER_NOT_EMPTY BOOL TRUE: There is at least one character left to read in the receive buffer
of the RS-485/RS-422 interface.
FALSE: The receive buffer of the RS-485/RS-422 interface is empty.
There are no more characters left to read.

103 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Table 3-23 Outputs of the RS485_422_RECEIVE function block


Name Data type Description
BUFFER_FULL BOOL TRUE: The receive buffer of the RS-485/RS-422 interface is full. No
more characters can be received.
FALSE: The receive buffer of the RS-485/RS-422 interface is not full
yet. More characters can be received.
RECEIVE_BUFFER_COUNT INT Amount of data in the receive buffer.
DATA_COUNT INT Amount of data that has been transmitted from the receive buffer to the
DATA parameter.
DATA ARRAY OF Receive buffer which contains the received characters.
BYTE

STATUS output
(ERROR = TRUE)
Table 3-24 Status values of the STATUS output (ERROR = TRUE)

Value Status
0x0102 Data type information not available
0x0105 Multiple instantiation prohibited
0x0107 RS485_422_INIT not executed successfully
0x0121 The DATA parameter is not linked
0x0124 Receive buffer does not contain any characters

Signal sequence diagram


Signal

REQUEST

BUFFER_NOT_EMPTY

DONE

Figure 3-47 Signal sequence when receiving a stream of data

Key:
1 Data signal
2 First two bytes received
3 Last two bytes received

8607_en_06 Phoenix Contact 104 / 185


ILC 191 ME/X

3.19 Function blocks for counter inputs

The description of the function block applies to the ILC 191 ME/INC.

Up to two counters (counter 1: terminal points 1.1 to 1.4; counter 2: terminal points 2.1 to
2.4) can be used for the evaluation of fast counter pulses.
In the PC Worx software, the counters are represented by the CNT1 and CNT2 function
blocks. The DIR, RESET, and ENABLE inputs of the function block can be used to define
presets for the counting direction, reset of the counter status, and start of the counting
process.
Alternatively presets can be defined by the level at the assigned local counter inputs of the
Inline controller. In this case, the appropriate counter mode must be specified at the MODE
input of the function block.

If presets are defined by the level at the assigned counter inputs of the Inline controller, the
corresponding input signal at the function block is inactive.

Figure 3-48 CNT_1 and CNT_2 function blocks: CNT_1 illustrated

105 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Table 3-25 Inputs of the CNT1 and CNT2 function blocks

Name Data type Description


ENABLE BOOL Enabling of parameterization
With a rising edge at ENABLE, the values parameterized at the MODE
and EDGE inputs are applied.
TRUE: The counter starts from the last counter status (CV output) if
RESET is set to FALSE.
FALSE: The counter is stopped with the current counter status. The
value at the CV output is retained.
MODE BYTE Operating mode of the counter, see Section 3.19.1
EDGE BYTE This value is used to specify which edges must be present at the counter
input in order to start the counting process:
0x00: The counting process is started when a positive edge is pres-
ent at the counter input.
0x01: The counting process is started when a negative edge is
present at the counter input.
0x02: The counting process is started when a positive or negative
edge is present at the counter input.
DIR BOOL Counting direction
TRUE: The counter counts up.
FALSE: The counter counts down.
PV UDINT Preset value for the counter status
A preset value can be specified to which the current counter status is al-
ways reset as soon as a positive edge is preset at the LOAD_PV input.
The value range is determined by the data type.

8607_en_06 Phoenix Contact 106 / 185


ILC 191 ME/X

Table 3-25 Inputs of the CNT1 and CNT2 function blocks

Name Data type Description


LOAD_PV BOOL Loads preset value for the counter status
On a positive edge at this input, the current counter status is reset to the
preset value that was defined with the PV parameter.
EVENT_VALUE UDINT Triggering of the event task
If the counter status reaches the value specified here, an event task can
be triggered. In order to use this function, an event task must be defined
and the corresponding “Event Value CNTx” event must be selected.

Figure 3-49 Selecting the “Event Value CNTx” event

For information on event tasks, please refer to the online help


for the PC Worx software.

Triggering the event task does not affect the counting process. The
counter continues counting.
RESET BOOL Reset of the counter status
TRUE: On a positive edge at this input, the counter status is reset to
0.
As long as the input level is set to TRUE, the counter status
equals 0.
FALSE: The counting process is active, the counter status does not
equal 0.

Table 3-26 Outputs of the CNT1 and CNT2 function blocks

Name Data type Description


Q BOOL TRUE: This output is set to TRUE if the value 0 is present at the CV
output, i.e., the counter status is 0.
FALSE: This output is set to FALSE if a value not equal to 0 is present
at the CV output, i.e., the counter status does not equal 0.
CV UDINT The current counter status value is output at this output.

107 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Table 3-26 Outputs of the CNT1 and CNT2 function blocks

Name Data type Description

ERROR BOOL TRUE: An error has occurred. Details are provided by the STATUS
output.
FALSE: No error. STATUS contains the current value of the internal
processing.
STATUS WORD Status value of the function block (see Table 3-27)

The function blocks are only processed as long as the Inline controller is in the RUN state.
When the Inline controller goes from the RUN state to the STOP state, the current counter
status is saved. As soon as the Inline controller returns to the RUN state, the counting
process is continued based on the saved counter status.

STATUS output
(ERROR = TRUE)
Table 3-27 Status values of the STATUS output (ERROR = TRUE)

Value Status
0x01 MODE > 0x08
The value at the MODE input is invalid.
0x02 MODE > 0x02
The value at the EDGE input is invalid.
0x10 Invalid instance. An attempt was made to use more than one instance
of the function block.

If several errors are present, combinations of the status values are output.

8607_en_06 Phoenix Contact 108 / 185


ILC 191 ME/X

3.19.1 Counter operating modes


Specify the counter mode at the MODE input of the function block. The operating mode
defines the presets for the counting direction, reset of the counter status, and start of the
counting process.

If you have specified an operating mode at the MODE input of the function block, the
presets for the counting direction and start of the counting process are defined by the level
at the local counter inputs of the Inline controller. In this case, the corresponding inputs at
the function block are inactive.

Eight different operating modes are available. The following table provides an overview:

Table 3-28 Counter operating modes

MODE System variables and terminal points Counter operating mode


[hex] CNT1_F1/ CNT1_F2/ CNT1_RESET/ CNT1_ENABLE/
CNT2_F1 CNT2_F2 CNT2_RESET CNT2_ENABLE
1.1/2.1 1.2/2.2 1.3/2.3 1.4/2.4
0x00 Clock – – – Counter with external clock
0x01 Clock – RESET – Counter with external clock and reset function
Counter with external clock, reset function, and
counting process enable

0x02 Clock – RESET ENABLE The ENABLE input of the function


block is inactive in this operating
mode.

Counter with external clock and counting direc-


tion preset
0x03 Clock DIR – –
The DIR input of the function block is
inactive in this operating mode.

Counter with external clock, counting direction


preset, and reset function
0x04 Clock DIR RESET –
The DIR input of the function block is
inactive in this operating mode.

Counter with external clock, counting direction


preset, reset function, and counting process en-
able
0x05 Clock DIR RESET ENABLE
The DIR and ENABLE inputs of the
function block are inactive in this
operating mode.

109 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Table 3-28 Counter operating modes

MODE System variables and terminal points Counter operating mode


[hex] CNT1_F1/ CNT1_F2/ CNT1_RESET/ CNT1_ENABLE/
CNT2_F1 CNT2_F2 CNT2_RESET CNT2_ENABLE
1.1/2.1 1.2/2.2 1.3/2.3 1.4/2.4
Up counter or down counter
Clock, Clock,
0x06 counting counting – – The DIR input of the function block is
up down inactive in this operating mode.

Up counter or down counter with reset function


Clock, Clock,
0x07 counting counting RESET – The DIR input of the function block is
up down inactive in this operating mode.

Up counter or down counter with reset function


and counting process enable
Clock, Clock,
0x08 counting counting RESET ENABLE The DIR and ENABLE inputs of the
up down function block are inactive in this
operating mode.

Key:

Clock The counter counts the signal edges at the counter input,
which were determined at the EDGE input of the function
block.
Clock, counting up The counter counts (up) the signal edges at the counter input,
which were determined at the EDGE input of the function
block.
Clock, counting down The counter counts (down) the signal edges at the counter in-
put, which were determined at the EDGE input of the function
block.

8607_en_06 Phoenix Contact 110 / 185


ILC 191 ME/X

DIR Specifies the counting direction


If a 1 signal is present at the terminal points (MODE 0x03,
0x04, 0x05) or at the input of the function block (MODE 0x00,
0x01, 0x02), the counter counts up.
If a 0 signal is present at the terminal points (MODE 0x03,
0x04, 0x05) or at the input of the function block (MODE 0x00,
0x01, 0x02), the counter counts down.
RESET Reset of the counter status
If a 1 signal is present at the terminal points or at the input of
the function block, the counter status is reset to 0. As long as
the 1 signal is present, the counter status equals 0.
If a 0 signal is present at the terminal points or at the input of
the function block, the counting process is active and the
counter status does not equal 0.
ENABLE Counting process enable
If a 1 signal is present at the terminal points (MODE 0x02,
0x05, 0x08) or at the input of the function block (MODE 0x00,
0x01, 0x03, 0x04, 0x06, 0x07), the values present at the
MODE and EDGE inputs of the function block are applied and
the counting process is started.
If a 0 signal is present at the terminal points (MODE 0x02,
0x05, 0x08) or at the input of the function block (MODE 0x00,
0x01, 0x03, 0x04, 0x06, 0x07), the counting process is contin-
ued from the last counter status.

111 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.20 Function blocks for incremental encoder inputs

The description of the function block applies to the ILC 191 ME/INC.

Figure 3-50 INC_CNT_1 and INC_CNT_2 function blocks: INC_CNT_1 function block
illustrated

The function blocks are only processed as long as the Inline controller is in the RUN state.
When the Inline controller goes from the RUN state to the STOP state, the current counter
status is saved. As soon as the Inline controller returns to the RUN state, the counting
process is continued based on the saved counter status.

Table 3-29 Inputs of the INC_CNT1 and INC_CNT2 function blocks

Name Data type Description


ENABLE BOOL Enabling of parameterization
TRUE: The value entered for the MODE input is applied and the
counting process is started. If the RESET input is set to
FALSE, the counting process is continued from the last
counter status.
FALSE: The counting process is stopped, the counter status is saved.
MODE BYTE Operating mode of the counter, see Section 3.20.1
PV UDINT Preset value for the counter status
A preset value can be specified to which the current counter status is al-
ways reset as soon as a positive edge is preset at the LOAD_PV input.
LOAD_PV BOOL On a positive edge at this input, the current counter status is reset to the
preset value that was defined with the PV parameter.

8607_en_06 Phoenix Contact 112 / 185


ILC 191 ME/X

Table 3-29 Inputs of the INC_CNT1 and INC_CNT2 function blocks

Name Data type Description


EVENT_VALUE UDINT Triggering of the event task
If the counter status reaches the value specified here, an event task can
be triggered. In order to use this function, an event task must be defined
and the corresponding “Event Value INC_CNTx” event must be se-
lected.

Figure 3-51 Selecting the “Event Value INC_CNTx” event

For information on event tasks, please refer to the online help


for the PC Worx software.

Triggering the event task does not affect the counting process. The
counter continues counting.
RESET BOOL Reset of the counter status
TRUE: On a positive edge at this input, the counter status is reset to
0.
As long as the input level is set to TRUE, the counter status
equals 0.
FALSE: The counting process is active, the counter status does not
equal 0.
CV UDINT The current counter status value is output at this output.
Q BOOL TRUE: This output is set to TRUE if the value 0 is present at the CV
output, i.e., the counter status is 0.
FALSE: This output is set to FALSE if a value not equal to 0 is present
at the CV output, i.e., the counter status does not equal 0.
ERROR BOOL TRUE: An error has occurred. Details are provided by the STATUS
output.
FALSE: No error. STATUS contains the current value of the internal
processing.
STATUS WORD Status value of the function block (see Table 3-31)

113 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Table 3-30 Outputs of the INC_CNT1 and INC_CNT2 function blocks

Name Data type Description


CV UDINT The current counter status value is output at this output.
Q BOOL TRUE: This output is set to TRUE if the value 0 is present at the CV
output, i.e., the counter status is 0.
FALSE: This output is set to FALSE if a value not equal to 0 is present
at the CV output, i.e., the counter status does not equal 0.
ERROR BOOL TRUE: An error has occurred. Details are provided by the STATUS
output.
FALSE: No error. STATUS contains the current value of the internal
processing.
STATUS WORD Status value of the function block (see Table 3-31)

STATUS output
(ERROR = TRUE)
Table 3-31 Status values of the STATUS output (ERROR = TRUE)

Value Status
0x01 MODE > 0x08
The value at the MODE input is invalid.
0x10 Invalid instance. An attempt was made to use more than one instance
of the function block.

If several errors are present, combinations of the status values are output.

3.20.1 Counter operating modes for incremental encoders


Specify the counter mode for incremental encoders at the MODE input of the function block.
Two different operating modes are available. The following table provides an overview:

Table 3-32 Counter operating modes

MODE Terminal points Counter operating mode


hex 1.1 and 2.1 1.2 and 2.2 1.3 and 2.3 1.4 and 2.4
0x00 Channel A Channel B – – Counter for incremental encoder
0x01 Channel A Channel B Channel Z – Counter for incremental encoder and reset function

The counting direction at the moment when a positive edge is present at channel A is
derived from the phase relation of channels A, B, and Z (MODE 0x01 only):

8607_en_06 Phoenix Contact 114 / 185


ILC 191 ME/X

Table 3-33 Derivation of the counting direction


Counting direc-
Channel A Channel B Channel Z Counter status reset to 0
tion
Positive edge Yes
1 signal Down
Negative edge –
Positive edge
Positive edge Yes
0 signal Up
Negative edge –

Figure 3-52 and Figure 3-53 show the phase relation of channels A, B, and Z (MODE 0x01
only) for counting directions up and down.

Channel A

Channel B

Channel Z

... N-3 N-2 N-1 N 0 1


8607A002

Figure 3-52 Phase relation of channels for counting direction up

Channel A

Channel B

Channel Z

... N+2 N+1 N 0 32


2 -1 232-2
8607A003

Figure 3-53 Phase relation of channels for counting direction down

115 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

3.21 Alignment
The alignment of the data elements in the Inline controller memory can result in “data gaps”
when storing data in the memory. The compiler automatically fills these gaps with padding
bytes during the compilation process in order to prevent incorrect processing.
The disadvantage of the “automatic” filling of data gaps becomes apparent when data is
transmitted from the Inline controller to another controller. If this controller does not know the
memory algorithm of the Inline controller, it will interpret the received data incorrectly.
It is therefore useful to program the filling of data gaps in your application program.
Alternatively, you can use the PACK and UNPACK function blocks (see online help in
PC Worx). Data transmissions to other controllers can therefore be taken into
consideration. For example, use byte arrays with an even number of bytes and/or word
arrays in order to avoid data gaps in your application program.
Please observe the following notes for program creation:
– Create data types in flat structures, i.e., do not nest user-defined data types.
– Insert padding bytes manually in order to ensure the uniform size and layout of the data
types.
– When inserting padding bytes, observe the memory alignment method of the
controllers used in the application (1-byte, 2-byte or 4-byte alignment).

Program example with The following program example shows how data gaps are filled.
data gaps

Figure 3-54 Example programming

8607_en_06 Phoenix Contact 116 / 185


ILC 191 ME/X

Struct1 Struct2 Struct3 Struct4 Array1


ByteElement ByteElement1
WordElement WordElement WordElement
Padding Byte ByteElement2
ByteElement ByteElement ByteElement
WordElement
Padding Byte Padding Byte Padding Byte
ByteElement1
WordElement
ByteElement2
ByteElement
Padding Byte

Size: 4 bytes Size: 4 bytes Size: 2 bytes Size: 6 bytes Size: 8 bytes
Align: 2 bytes Align: 2 bytes Align: 1 byte Align: 2 bytes Align: 2 bytes

Figure 3-55 Alignment - padding bytes in data gaps

Struct1 receives a padding byte after the ByteElement so that the WordElement is at a
WORD address (address that can be divided by 2 leaving no remainder). The alignment of
the overall structure is based on the data type used with maximum alignment. In this case,
the WordElement specifies the alignment.
The size of Struct2 is calculated based on the elements used and the resulting alignment.
The corresponding number of padding bytes is inserted so that the size of the data type with
the value of the alignment can be divided by 2 leaving no remainder (data type size modulo
alignment = 0).
Struct3 does not receive any padding bytes as the maximum alignment corresponds to one
byte.
Due to the padding byte that belongs to the Struct2 structure, the Struct3 structure starts at
an even address in Struct4.
Array1 receives 2 padding bytes corresponding to two consecutive Struct2 structures.

117 / 185 Phoenix Contact 8607_en_06


The Inline controller under PC Worx/PC Worx Express

Program example without The following program shows an example of how to fill data gaps in your application
data gaps program. Fill data gaps, which are to be expected due to the memory alignment, with
application data (padding bytes in Figure 3-56).

Figure 3-56 Example programming with padding bytes

8607_en_06 Phoenix Contact 118 / 185


ILC 191 ME/X

4 System variables and status information

4.1 General notes


This section describes the special program functions of the PC Worx/PC Worx Express
software that are available for the Inline controller.

The following descriptions of system variables and status information apply to PC Worx
and PC Worx Express.

The Inline controller has a register set, which is used for diagnostics and easy control of the
bus system. The diagnostic data is stored in the diagnostic status register and the
diagnostic parameter register. These registers are available to the application program as
system variables (system flags, global variables).
Operating states, error states, and additional information about the INTERBUS system can
be evaluated in the application program.

For additional information on diagnostics, please refer to the following user manual:
– INTERBUS diagnostics guide
IBS SYS DIAG DSC UM E Order No. 2747293

4.2 Status register for local digital inputs and outputs


The following system variables can be used to read the local digital input and output states
and to write the local digital output states.

Table 4-1 System variables of the status register for local digital inputs and outputs

System variable Type Meaning


ONBOARD_INPUT WORD State of all local inputs
ONBOARD_INPUT_BIT0 BOOL State of local input IN1
ONBOARD_INPUT_BIT1 BOOL State of local input IN2
ONBOARD_INPUT_BIT2 BOOL State of local input IN3
ONBOARD_INPUT_BIT3 BOOL State of local input IN4
ONBOARD_INPUT_BIT4 BOOL State of local input IN5
ONBOARD_INPUT_BIT5 BOOL State of local input IN6
ONBOARD_INPUT_BIT6 BOOL State of local input IN7
ONBOARD_INPUT_BIT7 BOOL State of local input IN8
ONBOARD_OUTPUT_BIT0 BOOL State of local output OUT1
ONBOARD_OUTPUT_BIT1 BOOL State of local output OUT2
ONBOARD_OUTPUT_BIT2 BOOL State of local output OUT3
ONBOARD_OUTPUT_BIT3 BOOL State of local output OUT4
ONBOARD_OUTPUT_OVERLOAD_0_3 BOOL Overload at at least one of the local outputs

119 / 185 Phoenix Contact 8607_en_06


System variables and status information

Each digital input can trigger an event task if a positive edge is present at the respective
input.
In order to use this function, an event task must be defined and the corresponding “Input X
Terminal point DI/X.X” event (positive edge) must be selected (see Figure 4-1).

Figure 4-1 Event task: selecting the “Input X Terminal point DI/X.X” event

For information on event tasks, please refer to the online help for the PC Worx software.

4.3 Status register for local analog inputs and outputs


The following system variables can be used to read the local analog input and output states
and to write the local analog output states.

Table 4-2 System variables of the status register for local analog inputs and outputs

System variable Type Meaning


ANALOG_INPUT CH1 WORD State of local analog input, channel 1
ANALOG_INPUT CH2 WORD State of local analog input, channel 2
ANALOG_OUTPUT_CH1 WORD State of local analog output, channel 1
ANALOG_OUTPUT_CH2 WORD State of local analog output, channel 2
ANALOG_OUTPUT_SUBST_VALUE_CH1 WORD Substitute value1 at local analog output, channel 1
ANALOG_OUTPUT_SUBST_VALUE_CH2 WORD Substitute value1 at local analog output, channel 2
ANALOG_OUTPUT_OVERLOAD_CH1 BOOL Overload2 at local analog output, channel 1
ANALOG_OUTPUT_OVERLOAD_CH2 BOOL Overload2 at local analog output, channel 2
ANALOG_SOURCE_OK BOOL The 10 V sensor supply voltage is OK.
1
If the controller is in the STOP state, the set substitute value is output. Exception: the controller is in the STOP state when switched on. In this case
the value 0 is output.
2
The analog output is overloaded. The desired voltage cannot be output.

8607_en_06 Phoenix Contact 120 / 185


ILC 191 ME/X

4.3.1 Representation of measured values for the local analog


inputs

This section applies to the ILC 191 ME/AN.

The measured values are depicted in IB IL format.


The measured value is represented in bits 14 to 4.
An additional bit (bit 15) is available as an error bit.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Err Analog value X X X X

Err Error bit


Is set to TRUE in the event of an overrange.
X Is set to 0 or 1. The bit is always 0 when a measured value is transmitted. The bit
can have the value 1 only when a diagnostic code is transmitted.

Table 4-3 Significant measured values


Input data Input voltage
0 V ... 10 V
hex dec V
8001 Overrange > 10.837
7F00 32512 + 10.837
7530 30000 + 10.0
0010 16 + 0.00533
0000 0 0

Table 4-4 Error values of analog inputs


Value Meaning
0x8001 Overrange
0x8004 Measured value is invalid
0x8040 Checksum error

121 / 185 Phoenix Contact 8607_en_06


System variables and status information

4.3.2 Representation of output values for the local analog


outputs

This section applies to the ILC 191 ME/AN.

The output values are depicted in IB IL format.


The output value is represented in bits 14 to 0.
An additional bit (bit 15) is available as a sign bit.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
V Analog value X X X X

V Sign bit (continuously 0)


X Irrelevant bit

Table 4-5 Output values


Output data Output voltage
0 V ... 10 V
hex dec V
7FFF ... + 10.837
7F01
7F00 32512 + 10.837
7530 30000 + 10.0
0010 16 + 0.00533
0000 0 0

8607_en_06 Phoenix Contact 122 / 185


ILC 191 ME/X

4.4 Status register for counter inputs

This section applies to the ILC 191 ME/INC.

The states of the local counter inputs can be read using the following system variables.

Table 4-6 System variables of the status register for counter inputs

System variable Type Meaning


CNT1_F1 BOOL Functional input F1
CNT1_F2 BOOL Functional input F2
Function block CNT_1
CNT1_RESET BOOL RESET input
CNT1_ENABLE BOOL ENABLE input
CNT2_F1 BOOL Functional input F1
CNT2_F2 BOOL Functional input F2
Function block CNT_2
CNT2_RESET BOOL RESET input
CNT2_ENABLE BOOL ENABLE input

4.5 Status register for incremental encoder inputs

This section applies to the ILC 191 ME/INC.

The states of the local incremental encoder inputs can be read using the following system
variables.

Table 4-7 System variables of the status register for incremental encoder inputs

System variable Type Meaning


INC_CNT1_A BOOL Counter 1, channel A
INC_CNT1_B BOOL Counter 1, channel B
INC_CNT1_Z BOOL Counter 1, channel Z
INC_CNT2_A BOOL Counter 2, channel A
INC_CNT2_B BOOL Counter 2, channel B
INC_CNT2_Z BOOL Counter 2, channel Z

123 / 185 Phoenix Contact 8607_en_06


System variables and status information

4.6 Diagnostic status register


Information on the operating state of the Inline controller is stored in the diagnostic status
register. Every bit in the diagnostic status register is assigned a certain Inline controller
state.
The following system variables can be used to read the diagnostic status register
information.

Table 4-8 System variables of the diagnostic status register

System variable Type Meaning


MASTER_DIAG_STATUS_REG_USER BOOL User error/parameterization error
MASTER_DIAG_STATUS_REG_PF BOOL I/O error
MASTER_DIAG_STATUS_REG_BUS BOOL Bus error
MASTER_DIAG_STATUS_REG_CTRL BOOL Error on Inline controller/hardware fault
MASTER_DIAG_STATUS_REG_DTC BOOL Diagnostic routine is active
MASTER_DIAG_STATUS_REG_RUN BOOL Data transmission is active
MASTER_DIAG_STATUS_REG_ACT BOOL Selected configuration is ready to operate
MASTER_DIAG_STATUS_REG_RDY BOOL Inline controller is ready to operate
MASTER_DIAG_STATUS_REG_BSA BOOL Bus segment switched off
MASTER_DIAG_STATUS_REG_SYSFAIL BOOL System failure
MASTER_DIAG_STATUS_REG_RES BOOL Standard function processed negatively
MASTER_DIAG_STATUS_REG_SYNCRES BOOL Synchronization error occurred
MASTER_DIAG_STATUS_REG_DCR BOOL Faulty data cycles
MASTER_DIAG_STATUS_REG_WARN BOOL Defined warning time exceeded
MASTER_DIAG_STATUS_REG_QUAL BOOL Defined error density exceeded
MASTER_DIAG_STATUS_REG_SSINFO BOOL A message is present
MASTER_DIAG_STATUS_REG_HI BYTE Master diagnostic status register, high byte
MASTER_DIAG_STATUS_REG_LOW BYTE Master diagnostic status register, low byte

8607_en_06 Phoenix Contact 124 / 185


ILC 191 ME/X

4.7 Diagnostic parameter register


The diagnostic parameter register provides additional information on the error indicated in
the diagnostic status register. The following information is stored in the diagnostic
parameter register:
– Error location
– Error code

15 8 7 0
3 1
Segment number Position in the segment

Example: device number 3.1


6219B040
Figure 4-2 Error location in the diagnostic parameter register

Special case: if an interface error cannot be located, the value 128 is indicated in the
diagnostic parameter register, i.e., bit 7 is set.

The diagnostic parameter register is rewritten whenever an error occurs. The diagnostic
parameter register contains the value “0” if no errors are detected.

Table 4-9 System variables of the diagnostic parameter register

System variable Type Meaning


MASTER_DIAG_PARAM_REG_HI BYTE Diagnostic parameter register, high byte
MASTER_DIAG_PARAM_REG_LOW BYTE Diagnostic parameter register, low byte
MASTER_DIAG_PARAM_2_REG_HI BYTE Extended diagnostic parameter register, high byte
MASTER_DIAG_PARAM_2_REG_LOW BYTE Extended diagnostic parameter register, low byte

125 / 185 Phoenix Contact 8607_en_06


System variables and status information

4.8 PROFINET register

The PC Worx Express software does not support this function.

Table 4-10 PROFINET system variables (PROFINET device function)

System variable Type Meaning


PND_S1_PLC_RUN BOOL Status of the higher-level controller/PROFINET controller
Information indicating whether the higher-level controller
is active. The value is TRUE if the higher-level controller is
in the RUN state (program). The display only applies
when there is an existing PROFINET connection
(PND_S1_VALID_DATA_CYCLE).
PND_S1_VALID_DATA_CYCLE BOOL The higher-level controller/higher-level PROFINET con-
troller has established the connection.
Information indicating whether a connection exists and
cyclic data is being exchanged between the PROFINET
controller and PROFINET device and whether the last
frame received contained valid data.
PND_S1_OUTPUT_STATUS_GOOD BOOL IOP status of the higher-level controller/higher-level
PROFINET controller
Information indicating whether the IN process data of the
PROFINET device (PND_S1_INPUTS) was received by
the PROFINET device with “valid” status. The value is
TRUE if the output data of the higher-level controller is
valid (provider status).
PND_S1_DATA_LENGTH WORD Process data length that was configured for the
PROFINET device.
PND_S1_OUTPUTS PND_IO_256 OUT process data
Memory area for OUT process data that the PROFINET
device sends to the higher-level controller/higher-level
PROFINET controller.
PND_S1_INPUTS PND_IO_256 IN process data
Memory area for IN process data that the PROFINET de-
vice receives from the higher-level controller/higher-level
PROFINET controller.
PND_IO_DRIVEN_BY_PLC INT Applicative system redundancy:
Specifies from which higher-level PROFINET controller
the data in the PROFINET device originates (see
Figure 2-5 on page 17).
0: No PROFINET controller
1: Controller A
2: Controller B

8607_en_06 Phoenix Contact 126 / 185


ILC 191 ME/X

4.9 IEC 61131 runtime system


There is a separate group of system variables for the IEC 61131 runtime system.

Table 4-11 System variables of the IEC 61131 runtime system

System variable Type Meaning


PLCMODE_ON BOOL PLC status ON: the runtime system on the Inline controller is ready
to operate.
PLCMODE_RUN BOOL PLC status RUN: the application program is running.
PLCMODE_STOP BOOL PLC status STOP: the application program is currently not running.
PLCMODE_HALT BOOL PLC status HALT: the application program was stopped at an
unspecified point.
PLCDEBUG_BPSET BOOL Breakpoint set: at least one breakpoint has been set in the applica-
tion program.
PLCDEBUG_FORCE BOOL Variable(s) forced: at least one variable is being continuously
overwritten (forced).
PLCDEBUG_POWERFLOW BOOL Powerflow ON: in “Powerflow” mode, you can see which parts of
your application program are being processed. This bit indicates
whether “Powerflow” mode is active.
PLC_TICKS_PER_SEC INT System ticks per second: this variable shows how many pulses the
system clock of the Inline controller delivers per second.
PLC_SYS_TICK_CNT DINT Number of system ticks: this variable shows the total number of
pulses delivered by the system clock since the last startup.
PLC_TASK_AVAILABLE INT Number of available PLC tasks
PLC_SYSTASK_AVAILABLE INT Number of available system tasks
PLC_MAX_ERRORS DINT Maximum number of “errors, warnings, and logging events”.
If this maximum number is reached, the controller is stopped.
PLC_ERRORS DINT Number of “errors, warnings, and logging events” currently entered.
PLC_TASK_DEFINED INT Number of tasks used
PLC_TASK_1 Record, ele- Information regarding task 1
ments = 17
: : :
PLC_TASK_8 Record, ele- Information regarding task 8
ments = 9

127 / 185 Phoenix Contact 8607_en_06


System variables and status information

4.10 Control processor


The system variables listed below show the states of the diagnostic status register on the
control processor of the Inline controller.

Table 4-12 System variables of the control processor

System variable Type Meaning


COP_DIAG_STATUS_REG_RT_ERR BOOL A runtime error (out of realtime) has occurred on the control pro-
cessor.
COP_DIAG_STATUS_REG_FAT_ERR BOOL A fatal error has occurred on the control processor. Division by
zero, for example, leads to a fatal error.
COP_DIAG_STATUS_REG_WARN BOOL A warning has been issued on the control processor.
COP_DIAG_STATUS_REG_PON BOOL Power ON (COP): the control processor is ready to operate.
COP_DIAG_STATUS_REG_FC_RUN BOOL Runtime system RUN
COP_DIAG_STATUS_REG_FC_STOP BOOL Runtime system STOP
COP_DIAG_STATUS_REG_FC_HALT BOOL Runtime system HALT
COP_DIAG_STATUS_REG_FC_LDG BOOL Runtime system LOADING
COP_DIAG_STATUS_REG_FC_DBG BOOL Runtime system DEBUG
COP_DIAG_STATUS_REG_FC_RDO BOOL Runtime system READONLY
COP_DIAG_PARAM_REG WORD Diagnostic parameter register of the control processor
COP_DIAG_PARAM_2_REG WORD Extended diagnostic parameter register of the control proces-
sor

4.11 Power storage, realtime clock


Table 4-13 System variables of the power storage and realtime clock

System variable Type Meaning


RTC_BATTERY_LOW BOOL Low capacity of the power storage for the realtime clock.
TRUE: Power storage device is being charged.
FALSE: Power storage device is fully charged.
The charging process has been completed.
RTC_DATA_INVALID BOOL The realtime clock data is invalid.

4.12 Power supplies


Table 4-14 System variables of the power supplies

System variable Type Meaning


POWER_SUPPLY_MAIN_OK BOOL The 24 V main power supply is OK.
POWER_SUPPLY_INPUTS_OK BOOL The 24 V power supply for the local inputs is OK.
POWER_SUPPLY_OUTPUTS_0_3_OK BOOL The 24 V power supply for the local outputs is OK. (Bits 0 to 3)

8607_en_06 Phoenix Contact 128 / 185


ILC 191 ME/X

4.13 Mode selector switch


Table 4-15 System variables of the mode selector switch

System variable Type Meaning


KEY_SWITCH_RESET BOOL The mode selector switch is in the MRESET position.
KEY_SWITCH_STOP BOOL The mode selector switch is in the STOP position.
KEY_SWITCH_RUN_PROG BOOL The mode selector switch is in the RUN_PROG position.

4.14 System time


Table 4-16 System variables of the system time

System variable Type Meaning


RTC_HOURS INT System time (hours)
RTC_MINUTES INT System time (minutes)
RTC_SECONDS INT System time (seconds)
RTC_DAY INT System time (day)
RTC_MONTH INT System time (month)
RTC_YEAR INT System time (year)

129 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

5 Easy Motion function block library

The Easy Motion function block library is not included as standard in the PC Worx
software.
The setup for installing the Easy Motion function block library can be downloaded at
phoenixcontact.net/products as part of the ILC 191 ME/AN and ILC 191 ME/INC
products.

The procedure described here also applies to servo motors with pulse direction interface.
In the following, however, the term step motors is used only.

Driver for Driver for


step motor step motor

8607A008

Figure 5-1 Hardware structure of an Easy Motion application with the ILC 191 ME/AN
and ILC 191 ME/INC Inline controllers

The ILC 191 ME/AN and ILC 191 ME/INC Inline controllers can be used to control step
motor drivers. In PC Worx, the connected step motor drivers are controlled via the pulse
direction outputs of the Inline controller using the blocks of the Easy Motion function block
library (ILCME_MCE).

8607_en_06 Phoenix Contact 130 / 185


ILC 191 ME/X

The pulse direction interface is used to determine the direction of rotation of the drive. The
movement of the drive is determined via the pulse output. The frequency of the pulse output
is directly proportional to the speed of the drive.

U/V 5

0
t
8607A005
Figure 5-2 Direction output: direction of rotation right
U/V

0
t
8607A006
Figure 5-3 Direction output: direction of rotation left
U/V

0
t
U/V

0
t
8607A007

Figure 5-4 Pulse output: ratio of frequency to speed

131 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

Key:
1. Low speed (low frequency)
2. High speed (high frequency)

The pulses cause the step motor shaft to turn by a defined angle.
Example:
A step motor requires 100 pulses per revolution, i.e., with each pulse the shaft of the step
motor turns by 3.6°; at a frequency of 100 Hz, the shaft of the step motor turns by 360°.
The frequency determines the number of pulses that is output with each time unit. The
frequency is directly proportional to the speed of the step motor.

The Easy Motion function block library can be used to implement easy travel and homing
processes for one-dimensional positioning axes for step motor drivers with pulse direction
input. The following moves can be made:
– Absolute move (see Section 5.4.5)
– Relative move (see Section 5.4.6)
– Continuous move (see Section 5.4.7)
– Homing (see Section 5.4.3 and Section 5.4.4)
The function blocks are based on the PLC open standard.

5.1 Characteristics of one-dimensional positioning


axes
Every one-dimensional positioning axis has two hardware limit switches, two software limit
switches, and one home position switch:
The two hardware limit switches are used to specify the theoretically permissible positioning
range. Within the permissible positioning range, the working range of the drive is specified
using the software limit switches.
In the PC Worx software, the hardware limit switches, software limit switches, and the home
position switch are defined on the M191_DRV1 driver block. There are two pulse direction
outputs available (see Section 2.16). In PC Worx, one driver block
(M191_DRV1/M191_DRV2) is available for each pulse direction output. Two one-
dimensional positioning axes can be operated independently of each other.

Hardware limit switches: Physical switching elements to specify the limits of the per-
missible positioning range.
Software limit switches: Specify the working range of the drive within the theoreti-
cally permissible positioning range.
The software limit switches only become active after hom-
ing has been performed.
The software limit switches are not physical switching ele-
ments but are specified in the PC Worx software depend-
ing on the application.
Home position switch: Specifies a reference point for the limits of the positioning
and working ranges.

8607_en_06 Phoenix Contact 132 / 185


ILC 191 ME/X

5
2 3 3 2

1 4 1
8607A004

Figure 5-5 Diagram of an axis application

Key:
1. Wall
2. Hardware limit switches
3. Software limit switches
4. Home position switch
5. Working range
6. Permissible positioning range
Before a move can be made on the axis, homing must be performed. During homing the
current axis coordinate of the drive is adjusted to the actual position of the drive.

NOTE: Damage to the positioning object and system parts


If the axis coordinate of the positioning object does not match the actual position in the
application, the desired setpoint positions cannot be approached. This may damage the
positioning object and system parts.
• Perform homing prior to the initial move.

133 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

5.2 Homing (dynamic homing)


Dynamic homing includes four different procedures.

Procedure 1
Homing starts with fast travel in the negative direction. If the current position is negative in
relation to the home position switch, limit switch IN1 is approached. The direction is then
changed to the positive direction. When the falling edge is reached, the direction of travel is
switched to the negative direction again. When the rising edge is reached, travel is switched
to the positive direction and is continued slowly. The reference point is set when the falling
edge of the home position switch signal is detected.
If the current position is positive in relation to the home position switch at the beginning, the
direction of travel is changed to the positive direction and continued slowly when the rising
edge of the home position switch is reached. The reference point is set when the falling
edge of the home position switch signal is detected.

IN1 IN2

REF

IN1 IN2

REF
6977B017

Figure 5-6 Homing: procedure 1

8607_en_06 Phoenix Contact 134 / 185


ILC 191 ME/X

Procedure 2
Homing is started in the negative direction and is carried out in the negative direction.

IN1 IN2

REF

IN1 IN2

REF
6977C018

Figure 5-7 Homing: procedure 2

Procedure 3
Homing is started in the positive direction and is also carried out in the positive direction.
The homing sequence is the same as for procedure 1, however, travel is started in the
positive direction.

IN1 IN2

REF

IN1 IN2

REF
6977C019

Figure 5-8 Homing: procedure 3

135 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

Procedure 4
Homing is started in the positive direction and is carried out in the negative direction. The
homing sequence is the same as for procedure 2, however, travel is started in the positive
direction.

IN1 IN2

REF

IN1 IN2

REF
6977B020

Figure 5-9 Homing: procedure 4

8607_en_06 Phoenix Contact 136 / 185


ILC 191 ME/X

5.3 Starting up the Easy Motion function block library

For a description of the individual function blocks, please refer to Sections 5.4.1. to 5.4.9.

To start up the Easy Motion function block library, proceed as follows:


• Instantiate the M191_DRV1 driver block (see Section 5.4.1).
• Instantiate the M191_Power, M191_HomePARA, and M191_Home blocks (see
Sections 5.4.2, 5.4.3 and 5.4.4).
• Create a data type MCE_UDT_AXIS_REF_V1_00 variable.
• Connect the variable to the Axis inputs and outputs of all instantiated blocks.
• Create the required variables for all other inputs of the M191_DRV1 driver block.
• Connect all inputs of the M191_DRV1 driver block to the corresponding variables.
• Assign the properties of the connected motor (number of pulses per revolution and
length of the feed in mm per revolution) to the corresponding inputs.
• Create the required variables for all inputs of the M191_Power, M191_HomePARA,
and M191_Home driver blocks.
• Connect the Active output of block M191_Home to the xEnableREF1 input of the
M191_DRV1 driver block.
• Compile the project and send the project to the controller.
• Restart the controller via the project control dialog box.
• Activate the Execute inputs of blocks M191_Power, M191_HomePARA, and
M191_Home one after the other in order to activate the function blocks one after the
other and to start homing.

Please note:
When activating the function blocks, it is essential to follow the sequence specified here.

137 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

5.4 Function blocks of the Easy Motion function block


library
The function blocks of the Easy Motion function block library (ILCME_MCE) can be used to
implement easy travel and homing processes for one-dimensional positioning axes for step
motor drivers with pulse direction input.

Table 5-1 Overview of the Easy Motion function blocks

Function block Short description


M191_DRV1/ The M191_DRV1 and M191_DRV2 function blocks (driver blocks) connect the two pulse di-
M191_DRV2 rection outputs of the Inline controller to the blocks of the Easy Motion library.
The driver blocks are also used to define all the axis-related properties.
M191_HomePARA This function block is used to parameterize the M191_Home function block.
M191_Home This function block is used to perform homing.
M191_MoveRelative This function block is used to perform a relative move.
M191_MoveAbsolute This function block is used to perform an absolute move.
M191_MoveVelocity This function block is used to perform a continuous move.
M191_Power This function block activates or deactivates the other function blocks of the Easy Motion li-
brary and enables the pulse direction outputs of the Inline controller.
The function block must be activated to start a move.
M191_Reset This function block acknowledges an axis-related error. The axis is set from “ErrorStop” to
the “StandStill” state. All axis-related errors are reset. The outputs of the other function blocks
remain unaffected.
M191_Stop This function block is used to stop a move using a specified deceleration ramp.
This function block should also be used if a move was started but could not be carried out
due to an error on the driver block. In this case, the move should be stopped using the
M191_Stop block.

8607_en_06 Phoenix Contact 138 / 185


ILC 191 ME/X

5.4.1 M191_DRV1 and M191_DRV2 function blocks

This block must be instantiated, parameterized, connected, and activated in order to


perform a move.

The M191_DRV1 and M191_DRV2 function blocks (driver blocks) connect the two pulse
direction outputs of the Inline controller to the blocks of the Easy Motion library. The driver
blocks map all the axis-related properties.

Figure 5-10 M191_DRV1 driver block

Table 5-2 Inputs of the M191_DRV function block

Name Data type Description


lrMotorTurnMM1 LREAL Feed in mm/revolution of the drive
The feed defines which distance the system mechanics travels with each
motor revolution. If a transmission is present, the feed must be calculated.
iMotorTurnSteps1 INT Number of pulses (steps)/revolution of the drive
The number of pulses can be found in the data sheet for the step motor.
rLimitVEL1 REAL Maximum permissible speed in mm/s
rLimitACC1 REAL Maximum permissible acceleration in mm/s2
rLimitDCC1 REAL Maximum permissible deceleration in mm/s2
xEnableABS1 BOOL Input for connecting the M191_MoveAbsolute function block (function
block for performing an absolute move)
TRUE: An absolute move is started or already active
FALSE: No absolute move is started

139 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

Table 5-2 Inputs of the M191_DRV function block


Name Data type Description
xEnableREL1 BOOL Input for connecting the M191_MoveRelative function block (function
block for performing a relative move)
TRUE: A relative move is started or already active
FALSE: No relative move is started
xEnableTIP1 BOOL Input for connecting the M191_MoveVelocity function block (function
block for performing a continuous move)
TRUE: A continuous move is started or already active
FALSE: No continuous move is started
xEnableREF1 BOOL Input for connecting the M191_Home function block (function block for
performing homing)
TRUE: Homing is started or is already active
FALSE: Homing has not started
xStopActive1 BOOL Input for connecting the M191_Stop function block
(function block for stopping the drive using a specified deceleration ramp)
TRUE: The current move is stopped
FALSE: The current move is not stopped
lrSoftEndDCC1 LREAL Deceleration when exceeding the position of the positive or negative soft-
ware limit switch in mm/s2
lrNegativeSoftEnd1 LREAL Position of the negative software limit switch in mm
lrPositiveSoftEnd1 LREAL Position of the positive software limit switch in mm
xNegativeHard1 BOOL Input for connecting a digital input of the Inline controller which is con-
nected to the negative hardware limit switch of the axis
TRUE: Negative hardware limit switch has been reached
FALSE: Negative hardware limit switch has not yet been reached
xPositiveHard1 BOOL Input for connecting a digital input of the Inline controller which is con-
nected to the positive hardware limit switch of the axis
TRUE: Positive hardware limit switch has been reached
FALSE: Positive hardware limit switch has not yet been reached
xReferenceHard1 BOOL Input for connecting a digital input of the Inline controller which is con-
nected to the home position switch of the axis
TRUE: Home position switch has been reached
FALSE: Home position switch has not yet been reached

8607_en_06 Phoenix Contact 140 / 185


ILC 191 ME/X

Table 5-3 Outputs of the M191_DRV function block

Name Data type Description


xError BOOL TRUE: An error has occurred. Details are provided by the wDiag-
Code output.
FALSE: No error. wDiagCode contains the current value of the internal
processing.
wDiagCode WORD Diagnostic value of the error that occurred (see Table 5-5)
udiCounter UDINT Current counter state of the pulses/steps output
udiFrequency UDINT Current frequency of the pulses output
lrPositionRQ LREAL Setpoint position in mm which was specified by the Position input of func-
tion block M191_MoveAbsolute
lrPositionCR LREAL Actual position in mm
xPosSoftEnd BOOL TRUE: The positive software limit switch has been reached
FALSE: The positive software limit switch has not yet been reached
xNegSoftEnd BOOL TRUE: The negative software limit switch has been reached
FALSE: The negative software limit switch has not yet been reached

Table 5-4 Input/output of the M191_DRV function block

Name Data type Description


Axis1 MCE_UDT_AXIS_REF_V1_00 Data structure for data exchange between the function blocks of the
Easy Motion library

In the event that both pulse direction outputs of the Inline controller are used, two
M191_DRV driver blocks must also be used. A second variable must be created for the
MCE_UDT_AXIS_REF_V1_00 data structure which is used for all blocks that control the
second pulse direction output.

Table 5-5 Diagnostic value of the wDiagCode output (xError = TRUE)

Name Description
0000hex The function block/drive is not active.
8000hex The drive is active.

141 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

Table 5-5 Diagnostic value of the wDiagCode output (xError = TRUE)

Name Description
C100hex Missing values at at least one of the lrMotorTurnMM, iMotorTurn-
Steps, lrSoftEndDCC inputs
C200hex (r)Velocity > rLimitVEL and/or (r)Acceleration > rLimitACC and/or
Deceleration > rLimitDCC
The specified speed and/or acceleration at one of the M191_MoveX
blocks or at the M191_HomePARA block is higher than the
corresponding maximum value which was specified on the
M191_DRV driver block.
C300hex The two hardware limit switches (positive and negative) have been
mixed up on the driver block or one of the two hardware limit switches
has been reached.

8607_en_06 Phoenix Contact 142 / 185


ILC 191 ME/X

5.4.2 M191_Power function block

This block must be instantiated, parameterized, connected, and activated in order to


perform a move.

The M191_Power function block activates or deactivates the other function blocks of the
Easy Motion library and enables the pulse direction outputs of the Inline controller.

The step motor driver is not enabled by the M191_Power function block but must be
enabled separately.

Figure 5-11 M191_Power function block

Table 5-6 Inputs of the M191_Power function block

Name Data type Description


Enable BOOL TRUE: The instantiated function blocks of the Easy Motion library are
enabled and ready to use. The pulse direction interface of the
Inline controller is enabled.
FALSE: The instantiated function blocks of the Easy Motion library are
not enabled and not ready to use. The pulse direction interface
of the Inline controller is not enabled.
EnablePositive BOOL TRUE: The move in a positive direction is enabled.
FALSE: The move in a positive direction is not enabled.
EnableNegative BOOL TRUE: The move in a negative direction is enabled.
FALSE: The move in a negative direction is not enabled.

Table 5-7 Outputs of the M191_Power function block

Name Data type Description


Status BOOL TRUE: The axis is enabled.
FALSE: The axis is not enabled.

143 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

Table 5-7 Outputs of the M191_Power function block


Name Data type Description
Valid BOOL Parameterization state of the function blocks
TRUE: No error in the parameterization of the function blocks.
FALSE: Error in the parameterization of the function blocks.
Error BOOL TRUE: An error has occurred. Details are provided by the ErrorID out-
put.
FALSE: No error. ErrorID contains the current value of the internal pro-
cessing.
ErrorID WORD Error value of the error that occurred (see Table 5-9)

Table 5-8 Input/output of the M191_Power function block

Name Data type Description


Axis MCE_UDT_AXIS_REF_V1_00 Data structure for data exchange between the function blocks of the
Easy Motion library

Table 5-9 Error values of the ErrorID output (Error = TRUE)

Name Description
0000hex No error occurred.
0001hex The axis is in the “StandStill” state.

8607_en_06 Phoenix Contact 144 / 185


ILC 191 ME/X

5.4.3 M191_HomePARA function block


The M191_HomePARA function block is used to specify the approaching speed and
reference speed as well as the acceleration during homing using the M191_Home function
block.

Figure 5-12 M191_HomePARA function block

Table 5-10 Inputs of the M191_HomePARA function block

Name Data type Description


xEnable BOOL TRUE: The parameters of the M191_HomePARA function block are
transferred to the M191_Home function block in order to per-
form homing.
FALSE: The parameters of the M191_HomePARA function block are
not transferred to the M191_Home function block.
rVelocity REAL Approaching speed in mm/s which is used to approach the home position
switch
Permissible value range: 0 < rVelocity ≤ rLimitVEL of the driver block
rVelocityREF REAL Reference speed (maximum speed at the home position switch) in mm/s
Permissible value range: 0 < rVelocityREF < rVelocity
rAcceleration REAL Acceleration for reaching the approaching speed and reference speed in
mm/s2.
Deceleration for reducing the approaching speed and reference speed is
not entered separately. Deceleration therefore is always equal to acceler-
ation.
Permissible value range: 0 < rAcceleration ≤ rLimitACC of the driver
block
rPositionREF REAL Home position in mm
Absolute position after homing to the desired side of the home position
switch (default value: 0 mm (input not connected))
iModeREF INT Homing procedure, permissible value range: 1 ... 4,
see Section 5.2

145 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

Table 5-11 Outputs of the M191_HomePARA function block

Name Data type Description


xReady BOOL TRUE: The values at the rVelocity, rVelocityREF, and rAccelera-
tion inputs are permissible.
FALSE: The xEnable input was not set or xError has occurred.
xError BOOL TRUE: An error has occurred. Details are provided by the wDiag-
Code output.
FALSE: No error. wDiagCode contains the current value of the internal
processing.
wDiagCode WORD Diagnostic value of the error that occurred (see Table 5-13)

Table 5-12 Input/output of the M191_HomePARA function block

Name Data type Description


Axis MCE_UDT_AXIS_REF_V1_00 Data structure for data exchange between the function blocks of the
Easy Motion library

Table 5-13 Diagnostic value of the wDiagCode output (xError = TRUE)

Name Description
0000hex No error occurred.
0006hex The M191_Power function block is not active.
0071hex Invalid value for rVelocity or rLimitVEL
(rVelocity ≤ 0 or rVelocity > rLimitVEL or rLimitVEL ≤ 0)
0072hex Invalid value for rVelocityREF (rVelocityREF = 0)
0073hex Invalid value for rVelocityREF (rVelocityREF > rVelocity)
0081hex Invalid value for rAcceleration (rAcceleration ≤ 0 or
rAcceleration > rLimitACC or rLimitACC ≤ 0)
00A1hex No homing procedure specified (permissible value range: 1 ... 4)
C100hex Missing values at at least one of the lrMotorTurnMM, iMotorTurn-
Steps, lrSoftEndDCC inputs

8607_en_06 Phoenix Contact 146 / 185


ILC 191 ME/X

5.4.4 M191_Home function block


The M191_Home function block is used to perform homing. The speed and acceleration
values for homing are specified using the M191_HomePARA function block.

The M191_HomePARA function block must be activated before the M191_Home function
block can be executed.

Figure 5-13 M191_Home function block

Table 5-14 Inputs of the M191_Home function block

Name Data type Description


Execute BOOL TRUE: Homing is started.

Table 5-15 Outputs of the M191_Home function block

Name Data type Description


Done BOOL A positive edge at this output indicates that the function block has been
executed and homing has been performed.
Busy BOOL TRUE: The function block is executed.
FALSE: The function block is not executed or has already been execut-
ed successfully.
Active BOOL The Active output must be connected to the xEnableREF input of the
driver block.
CommandAborted BOOL TRUE: Execution of the function block was aborted.
FALSE: Execution of the function block was not aborted.
Error BOOL TRUE: An error has occurred. Details are provided by the ErrorID out-
put.
FALSE: No error. ErrorID contains the current value of the internal pro-
cessing.
ErrorID WORD Error value of the error that occurred (see Table 5-17)

147 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

Table 5-16 Input/output of the M191_Home function block

Name Data type Description


Axis MCE_UDT_AXIS_REF_V1_00 Data structure for data exchange between the function blocks of the
Easy Motion library

Table 5-17 Error values of the ErrorID output (Error = TRUE)

Name Description
0000hex No error occurred.
0001hex The axis is not in the “StandStill” state.
0006hex Enabling by M191_Power function block is missing.
0061hex At least one missing error at the rVelocity, rVelocityREF, and rAccel-
eration inputs

8607_en_06 Phoenix Contact 148 / 185


ILC 191 ME/X

5.4.5 M191_MoveAbsolute function block


The M191_MoveAbsolute function block is used to perform an absolute move.

The M191_DRV and M191_Power function blocks must also be instantiated in order to
perform an absolute move.
Before a move can be made on the axis, homing must be performed.

Figure 5-14 M191_MoveAbsolute function block

Table 5-18 Inputs of the M191_MoveAbsolute function block

Name Data type Description


Execute BOOL TRUE: The absolute move is started.
Position REAL Absolute target position in the negative and positive direction of the home
position in mm
Velocity REAL Speed in mm/s
Permissible value range: 0 < Velocity ≤ rLimitVEL
Acceleration REAL Acceleration in mm/s2
Permissible value range: 0 < Acceleration ≤ rLimitACC of the driver
block
Deceleration REAL Deceleration in mm/s2
Permissible value range: 0 < Deceleration ≤ rLimitDCC of the driver
block

Table 5-19 Outputs of the M191_MoveAbsolute function block

Name Data type Description


Done BOOL A positive edge at this output indicates that the function block has been
executed and an absolute move has been performed.
Busy BOOL TRUE: The function block is executed.
FALSE: The function block is not executed or has already been execut-
ed successfully.
Active BOOL The Active output must be connected to the xEnableABS input of the
driver block.

149 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

Table 5-19 Outputs of the M191_MoveAbsolute function block


Name Data type Description
CommandAborted BOOL TRUE: Execution of the function block was aborted.
FALSE: Execution of the function block was not aborted.
Error BOOL TRUE: An error has occurred. Details are provided by the ErrorID out-
put.
FALSE: No error. ErrorID contains the current value of the internal pro-
cessing.
ErrorID WORD Error value of the error that occurred (see Table 5-21)

Table 5-20 Input/output of the M191_MoveAbsolute function block

Name Data type Description


Axis MCE_UDT_AXIS_REF_V1_00 Data structure for data exchange between the function blocks of the
Easy Motion library

Table 5-21 Error values of the ErrorID output (Error = TRUE)

Name Description
0000hex No error occurred.
0006hex Enabling by M191_Power function block is missing.
0007hex Invalid value for Velocity or rLimitVEL
(Velocity ≤ 0 or Velocity > rLimitVEL or rLimitVEL ≤ 0)
0008hex Invalid value for Acceleration (Acceleration ≤ 0 or
Acceleration > rLimitACC or rLimitACC ≤ 0)
0009hex Invalid value for Deceleration (Deceleration ≤ 0 or
Deceleration > rLimitDCC or rLimitDCC ≤ 0)
C100hex Missing values at at least one of the lrMotorTurnMM, iMotorTurn-
Steps, lrSoftEndDCC inputs
C300hex The two hardware limit switches (positive and negative) have been
mixed up on the driver block or one of the two hardware limit switches
has been reached.

8607_en_06 Phoenix Contact 150 / 185


ILC 191 ME/X

5.4.6 M191_MoveRelative function block


The M191_MoveRelative function block is used to perform a relative move.

The M191_DRV and M191_Power function blocks must also be instantiated in order to
perform a relative move.
Before a move can be made on the axis, homing must be performed.

Figure 5-15 M191_MoveRelative function block

Table 5-22 Inputs of the M191_MoveRelative function block

Name Data type Description


Execute BOOL TRUE: The relative move is started.
Position REAL Relative target position in the negative and positive direction of the current
position in mm
Velocity REAL Speed in mm/s
Permissible value range: 0 < Velocity ≤ rLimitVEL
Acceleration REAL Acceleration in mm/s2
Permissible value range: 0 < Acceleration ≤ rLimitACC of the driver
block
Deceleration REAL Deceleration in mm/s2
Permissible value range: 0 < Deceleration ≤ rLimitDCC of the driver
block

Table 5-23 Outputs of the M191_MoveRelative function block

Name Data type Description


Done BOOL A positive edge at this output indicates that the function block has been
executed and a relative move has been performed.
Busy BOOL TRUE: The function block is executed.
FALSE: The function block is not executed or has already been execut-
ed successfully.
Active BOOL The Active output must be connected to the xEnableREL input of the
driver block.

151 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

Table 5-23 Outputs of the M191_MoveRelative function block


Name Data type Description
CommandAborted BOOL TRUE: Execution of the function block was aborted.
FALSE: Execution of the function block was not aborted.
Error BOOL TRUE: An error has occurred. Details are provided by the ErrorID out-
put.
FALSE: No error. ErrorID contains the current value of the internal pro-
cessing.
ErrorID WORD Error value of the error that occurred (see Table 5-25)

Table 5-24 Input/output of the M191_MoveRelative function block

Name Data type Description


Axis MCE_UDT_AXIS_REF_V1_00 Data structure for data exchange between the function blocks of the
Easy Motion library

Table 5-25 Error values of the ErrorID output (Error = TRUE)

Name Description
0000hex No error occurred.
0006hex Enabling by M191_Power function block is missing.
0007hex Invalid value for Velocity or rLimitVEL
(Velocity ≤ 0 or Velocity > rLimitVEL or rLimitVEL ≤ 0)
0008hex Invalid value for Acceleration (Acceleration ≤ 0 or
Acceleration > rLimitACC or rLimitACC ≤ 0)
0009hex Invalid value for Deceleration (Deceleration ≤ 0 or
Deceleration > rLimitDCC or rLimitDCC ≤ 0)
C100hex Missing values at at least one of the lrMotorTurnMM, iMotorTurn-
Steps, lrSoftEndDCC inputs
C300hex The two hardware limit switches (positive and negative) have been
mixed up on the driver block or one of the two hardware limit switches
has been reached.

8607_en_06 Phoenix Contact 152 / 185


ILC 191 ME/X

5.4.7 M191_MoveVelocity function block


The M191_MoveVelocity function block is used to perform a continuous move without
position specification.

The M191_DRV and M191_Power function blocks must also be instantiated in order to
perform a continuous move.
Before a move can be made on the axis, homing must be performed.

Figure 5-16 M191_MoveVelocity function block

Table 5-26 Inputs of the M191_MoveVelocity function block

Name Data type Description


Execute BOOL TRUE: The continuous move is started.
Velocity REAL Speed in mm/s
Permissible value range: 0 < Velocity ≤ rLimitVEL
Acceleration REAL Acceleration in mm/s2
Permissible value range: 0 < Acceleration ≤ rLimitACC of the driver
block
Deceleration REAL Deceleration in mm/s2
Permissible value range: 0 < Deceleration ≤ rLimitDCC of the driver
block
Direction INT Moving direction
0: Positive direction
1: Negative direction

Table 5-27 Outputs of the M191_MoveVelocity function block

Name Data type Description


Done BOOL A positive edge at this output indicates that the function block has been
executed and a continuous move has been performed.
Busy BOOL TRUE: The function block is executed.
FALSE: The function block is not executed or has already been execut-
ed successfully.
Active BOOL The Active output must be connected to the xEnableVEL input of the
driver block.

153 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

Table 5-27 Outputs of the M191_MoveVelocity function block


Name Data type Description
CommandAborted BOOL TRUE: Execution of the function block was aborted.
FALSE: Execution of the function block was not aborted.
Error BOOL TRUE: An error has occurred. Details are provided by the ErrorID out-
put.
FALSE: No error. ErrorID contains the current value of the internal pro-
cessing.
ErrorID WORD Error value of the error that occurred (see Table 5-29)

Table 5-28 Input/output of the M191_MoveVelocity function block

Name Data type Description


Axis MCE_UDT_AXIS_REF_V1_00 Data structure for data exchange between the function blocks of the
Easy Motion library

Table 5-29 Error values of the ErrorID output (Error = TRUE)

Name Description
0000hex No error occurred.
0006hex Enabling by M191_Power function block is missing.
0007hex Invalid value for Velocity or rLimitVEL
(Velocity ≤ 0 or Velocity > rLimitVEL or rLimitVEL ≤ 0)
0008hex Invalid value for Acceleration (Acceleration ≤ 0 or
Acceleration > rLimitACC or rLimitACC ≤ 0)
0009hex Invalid value for Deceleration (Deceleration ≤ 0 or
Deceleration > rLimitDCC or rLimitDCC ≤ 0)
C100hex Missing values at at least one of the lrMotorTurnMM, iMotorTurn-
Steps, lrSoftEndDCC inputs
C300hex The two hardware limit switches (positive and negative) have been
mixed up on the driver block or one of the two hardware limit switches
has been reached.

5.4.8 M191_Reset function block


This function block acknowledges an axis-related error. The axis is set from “ErrorStop” to
the “StandStill” state. All axis-related errors are reset. The outputs of the other function
blocks remain unaffected. The other instantiated function blocks can only be used after the
errors have been reset.

8607_en_06 Phoenix Contact 154 / 185


ILC 191 ME/X

Figure 5-17 M191_Reset function block

Table 5-30 Input of the M191_Reset function block

Name Data type Description


Execute BOOL On a positive edge at this input, all axis-related errors are reset.

Table 5-31 Outputs of the M191_Reset function block

Name Data type Description


Done BOOL A positive edge at this output indicates that the function block has been
executed and all axis-related errors have been reset successfully.
Busy BOOL TRUE: The function block is executed.
FALSE: The function block is not executed or has already been execut-
ed successfully.
Error BOOL TRUE: An error has occurred. Details are provided by the ErrorID out-
put.
FALSE: No error. ErrorID contains the current value of the internal pro-
cessing.
ErrorID WORD Error value of the error that occurred (see Table 5-33)

Table 5-32 Input/output of the M191_Reset function block

Name Data type Description


Axis MCE_UDT_AXIS_REF_V1_00 Data structure for data exchange between the function blocks of the
Easy Motion library

Table 5-33 Error values of the ErrorID output (Error = TRUE)

Name Description
0000hex No error occurred.
0001hex The drive is in the “ErrorStop” state.

5.4.9 M191_Stop function block


This function block is used to stop a move using a specified deceleration ramp.

155 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

This function block should also be used if a move was started but could not be carried out
due to an error on the driver block. In this case, the move should be stopped using the
M191_Stop block.

Figure 5-18 M191_Stop function block

Table 5-34 Inputs of the M191_Stop function block

Name Data type Description


Execute BOOL On a positive edge at this input, the drive is stopped.
Deceleration REAL Deceleration in mm/s2
Permissible value range: 0 < Deceleration ≤ rLimitDCC of the driver
block

Table 5-35 Outputs of the M191_Stop function block

Name Data type Description


Done BOOL A positive edge at this output indicates that the function block has been
executed and the drive has been stopped.
Busy BOOL TRUE: The function block is executed.
FALSE: The function block is not executed or has already been execut-
ed successfully.
Active BOOL The Active output must be connected to the xStopActive input of the
driver block.
CommandAborted BOOL TRUE: Execution of the function block was aborted.
FALSE: Execution of the function block was not aborted.
Error BOOL TRUE: An error has occurred. Details are provided by the ErrorID out-
put.
FALSE: No error. ErrorID contains the current value of the internal pro-
cessing.
ErrorID WORD Error value of the error that occurred (see Table 5-37)

Table 5-36 Input/output of the M191_Stop function block

Name Data type Description


Axis MCE_UDT_AXIS_REF_V1_00 Data structure for data exchange between the function blocks of the
Easy Motion library

8607_en_06 Phoenix Contact 156 / 185


ILC 191 ME/X

Table 5-37 Error values of the ErrorID output (Error = TRUE)

Name Description
0000hex No error occurred.
0001hex The axis is in the “ErrorStop” state.
0006hex Enabling by M191_Power function block is missing.
0009hex Invalid value for Deceleration (Deceleration ≤ 0 or
Deceleration > rLimitDCC or rLimitDCC ≤ 0)

157 / 185 Phoenix Contact 8607_en_06


Easy Motion function block library

5.5 Simple application example


Figure 5-19 shows a simple application example in order to perform an absolute move.
All function blocks used and the pulse direction interface of the Inline controller must be
enabled first by the M191_Power function block before the M191_MoveAbsolute function
block can be parameterized and activated. After successful enabling by M191_Power, the
M191_HomePARA function block must be activated. Then, the M191_Home function block
must be activated in order to start homing. After homing, absolute moves can be performed
using the M191_MoveAbsolute function block.

Figure 5-19 Application example for performing an absolute move.

8607_en_06 Phoenix Contact 158 / 185


ILC 191 ME/X

6 Technical data and ordering data

6.1 Technical data

General data
Dimensions 163.5 mm x 135 mm x 71.5 mm
Weight 503 g
Connection data for connectors
Connection method Spring-cage connection
Conductor cross section
Single-wire/terminal point, solid 0.08 mm2 to 1.5 mm2
Single-wire/terminal point, stranded 0.08 mm2 to 1.5 mm2
Single-wire/terminal point, AWG 28 to 16
We recommend using a conductor cross section of 0.2 mm2
to 1.5 mm2.

General supply

Use a power supply without fall-back characteristic curve (see Section “Sizing of the power supply” on
page 39).

24 V main supply UM ILC 191 ME/AN ILC 191 ME/INC


Connection technology Spring-cage terminal blocks
Nominal value 24 V DC
Tolerance -15%/+20% (according to EN 61131-2)
Ripple ±5%
Current consumption at nominal voltage 6 mA + 7 mA for each input set 60 mA + 7 mA for each input set
(typical)
Current consumption at nominal voltage 8 A DC
(maximum)
Continuation Through potential routing
Protective measures
Surge voltage Input protective diodes (can be destroyed by permanent overload)
Pulse loads up to 1500 W are short circuited by the input protective diode.
Polarity reversal Parallel diodes for protection against polarity reversal; in the event of an error
the high current flowing through the diodes causes the fuse connected up-
stream to blow.

NOTE:
Provide external protection for the 24 V area. The power supply unit must be able to supply 4 times (400%) the
nominal current of the external fuse, to ensure that the fuse blows safely in the event of an error.

159 / 185 Phoenix Contact 8607_en_06


Technical data and ordering data

24 V segment supply US
Connection technology Spring-cage terminal blocks
Nominal value 24 V DC
Tolerance -15%/+20% (according to EN 61131-2)
Ripple ±5%
Current consumption at nominal voltage (typical) 10 mA + 4 mA for each output set + load
Current consumption at nominal voltage (maximum) 8A
Continuation Through potential routing
Protective measures
Surge voltage Input protective diodes (can be destroyed by permanent
overload)
Pulse loads up to 1500 W are short circuited by the input
protective diode.
Polarity reversal Parallel diodes for protection against polarity reversal; in the
event of an error the high current flowing through the diodes
causes the fuse connected upstream to blow.

NOTE:
Provide external protection for the 24 V area. The power supply unit must be able to supply 4 times (400%) the
nominal current of the external fuse, to ensure that the fuse blows safely in the event of an error.

24 V supply UILC ILC 191 ME/AN ILC 191 ME/INC


Connection technology Spring-cage terminal blocks
Nominal value 24 V DC
Tolerance -15%/+20% (according to EN 61131-2)
Ripple ±5%
Permissible range 19.2 to 30 V DC
Current consumption at nominal voltage 130 mA
(minimum)
Current consumption at nominal voltage 310 mA 360 mA
(typical)
Current consumption at nominal voltage 960 mA (sum of 460 mA communica- 1050 mA (sum of 550 mA communi-
(maximum) tions power + 500 mA analog power cations power + 500 mA analog
supply) power supply)
Protective measures
Surge voltage Input protective diodes (can be destroyed by permanent overload)
Pulse loads up to 1500 W are short circuited by the input protective diode.
Polarity reversal Serial diode in the lead path of the power supply unit; in the event of an error
only a low current flows. In the event of an error, no fuse trips within the ex-
ternal power supply unit.

8607_en_06 Phoenix Contact 160 / 185


ILC 191 ME/X

24 V supply UILC ILC 191 ME/AN ILC 191 ME/INC

NOTE:
Observe the current consumption of the Inline terminals
Observe the logic current consumption of each device when configuring an Inline station. It is specified in every
terminal-specific data sheet. The current consumption can differ depending on the individual terminal. The
permissible number of devices that can be connected therefore depends on the specific station structure.
Protection by the external power supply unit
Ensure protection of 2 A through the external power supply unit.

7.5 V communications power UL (potential jumper)


Nominal value 7.5 V DC
Tolerance ±5%
Ripple ±1.5%
Maximum output current 0.8 A DC

24 V analog supply UANA (potential jumper)


Nominal value 24 V DC
Tolerance -15%/+20%
Ripple ±5%
Maximum output current 0.5 A DC
Protective measures Electric short-circuit protection

PROFINET
Type PROFINET device
Specification 2.2
Performance class RT
Update rate ≥ 1 ms
Number of slots 1
Vendor ID
ILC 191 ME/AN 00B0hex/176dec
ILC 191 ME/INC 00B0hex/176dec
Device ID
ILC 191 ME/AN 0096hex/150dec
ILC 191 ME/INC 0097hex/151dec

INTERBUS
Number of I/O points 4096, maximum
Number of data words 256, maximum
Transmission speed 500 kbps or 2 Mbps

161 / 185 Phoenix Contact 8607_en_06


Technical data and ordering data

INTERBUS

This speed is automatically set according to the connected Inline terminals. Only use terminals with a uniform
transmission speed in the overall connected Inline system (local bus and remote bus).

Transmission reliability CR check (Hamming distance: 4)


Protocol EN 50254

Number of devices in the INTERBUS system


Total number of bus devices 128, maximum
Number of remote bus devices 32, maximum
Number of devices with parameter channel (PCP) 24, see Section 3.15 on page 88
Number of remote bus levels 4, see Section 2.2 on page 14

Network interface
Type 2 x Ethernet; 10Base-T and 100Base-T(X)
Transmission speed 10 Mbps (10Base-T), 100 Mbps (100Base-T(X))
half duplex, full duplex, auto negotiation

This speed cannot be set manually. It is set automatically by means of auto negotiation.

Connection technology CAT5 twisted pair cable


Twisted pair cable with a conductor cross section of 0.14
mm2 to 0.22 mm2
8-pos. RJ45 socket

Inline local bus


Interface Inline local bus
Electrical isolation No
Number of devices 128, maximum

NOTE: Observe the current consumption of the Inline terminals


Observe the logic current consumption of each device when configuring an Inline station. It is specified in every
terminal-specific data sheet. The current consumption can differ depending on the individual terminal. The
permissible number of devices that can be connected therefore depends on the specific station structure.

Modbus/TCP
Number of I/O points 32,768, maximum (internal Modbus/TCP client)

Diagnostic interface
Connection technology 6-pos. MINI-DIN socket (PS/2)

8607_en_06 Phoenix Contact 162 / 185


ILC 191 ME/X

Diagnostic interface
Interface type RS-232
Transmission speed 115 kbaud, maximum
Electrical isolation No

Digital outputs
Number 4
Output design Protected outputs according to EN 61131-2
Nominal output voltage 24 V DC
Nominal output current 500 mA

Digital inputs
Number 8
Input design According to EN 61131-2 type 1
Definition of the switching thresholds
Maximum low-level voltage 5 V DC
Minimum high-level voltage 15 V DC
Nominal input voltage 24 V DC
Permissible range -0.5 V < UIN < +30 V DC
Nominal input current at 24 V 7 mA, typical; 15 mA, maximum
Hardware filter times (typical), inputs I1 to I8
Signal change 0  1 3 ms
Signal change 1  0 3 ms
Permissible cable length to the sensor 30 m (to ensure conformance with EMC Directive
2014/30/EU)
Use of AC sensors AC sensors in the voltage range < UIN are limited in applica-
tion (according to the input design)

PWM outputs
Number 2
Nominal output voltage 5 V DC ±5%
Nominal output current 10 mA +10%
Maximum frequency 150 kHz

RS-485/RS-422 interface
Transmission speed 115 kbaud, maximum
Operating modes Full duplex, half duplex
Electrical isolation Yes

163 / 185 Phoenix Contact 8607_en_06


Technical data and ordering data

Analog inputs (ILC 191 ME/AN only)


Number 2
A/D resolution 11 bit
Measured value representation 0 V ... 10 V
Data formats IB IL
Process data update 10 ms
Filtering None
Overload protection ±30 V DC, maximum
Voltage input signal 0 V ... 10 V
Input resistance of voltage input 324 kΩ, typical
Limit frequency (3 dB) 100 Hz
Common mode voltage range, signal - ground 50 V, maximum
Sensor supply voltage 10 V DC ±5%
Maximum output current 50 mA
Tolerance See Section 6.1.1 on page 167

Analog outputs (ILC 191 ME/AN only)


Number 2
Signals 0 V ... 10 V
DAC resolution 11 bit
Output load > 1 kΩ
Process data update including conversion time of the D/A 10 ms
converter
Short-circuit protection, overload protection Electronic
Transient protection Suppressor diode
Tolerance See Section 6.1.2 on page 168

Counter inputs (ILC 191 ME/INC only)


Input design EN 61131-2 type 3
Number 2
Nominal input current 2.5 mA (per channel)
Input voltage range, 0 signal -3 V DC ... 5 V DC
Input voltage range, 1 signal 11 V DC ... 30 V DC
Permissible voltage range 30 V, maximum
Maximum frequency 200 kHz

8607_en_06 Phoenix Contact 164 / 185


ILC 191 ME/X

Incremental encoder inputs (ILC 191 ME/INC only)


Number 2
Switching threshold Low ≤ 2.5 V, high > 3.5 V (up to 27 V, maximum)
Encoder signal Two pulse trains (A and B, electrically shifted by 90°) and
one reference signal (Z)

Diagnostics and status indicators


IEC 61131 runtime system (PLC) FR, FF
Ethernet (ETH) LINK, ACT
INTERBUS diagnostics (IL) RDY, BSA, FAIL, PF
Digital inputs and outputs I1 to I8, E, Q1 to Q4
Supply voltages US, UM, UL
PROFINET BF, SF
Analog inputs and outputs (ILC 191 ME/AN) UA, O1 to O2
Counter inputs (ILC 191 ME/INC) C11 to C24
Incremental encoder inputs (ILC 191 ME/INC) A1, A2, B1, B2, Z1, Z2

IEC 61131 runtime system


Programming system PC Worx
Processing speed
1 K mixed instructions 1.3 ms
1 K bit instructions 90 µs
Shortest cycle time (for cyclic task) 1 ms
Program memory 1 Mbyte,
86 K instructions (IL)
Mass storage 1 Mbyte
Retentive mass storage 48 kbytes, NVRAM
Number of data blocks Depends on mass storage
Number of control tasks 8
Parameterization memory
Integrated 4 Mbytes Flash memory (100,000 write access operations
Plug-in, SD card per sector, typical)
See Section “Accessories” on page 170.

Please note that the number of write access operations to the parameterization memory is limited.
We recommend that you limit the number of write access operations to the parameterization memory in your
application program by first storing data on the mass storage and/or the memory for retentive data (NVRAM).
Write access operations to the parameterization memory for small volumes of data (bits, bytes) should not be
possible in your application program. Data should only be transferred from the mass storage/memory for
retentive data to the parameterization memory if the mass storage/memory for retentive data is full, i.e., data
must be deleted first to enable further write access operations.

165 / 185 Phoenix Contact 8607_en_06


Technical data and ordering data

Realtime clock
Accuracy 1 min./week, maximum
Power reserve 10 days
Charging time of the power storage 24 hours

Ambient conditions
Degree of protection IP20 (EN 60529:1991)
Ambient temperature (operation) -25°C to +55°C
Permissible temperature (storage/transport) -25°C to +85°C
Temperature class –

This temperature range is only guaranteed if the Inline controller is mounted horizontally.

Permissible humidity (operation/storage/transport) 10% to 95%, according to DIN EN 61131-2


No condensation, no ice formation
Permissible air pressure (operation/storage/transport) 70 kPa to 106 kPa (up to 3000 m above sea level)
Gases that may endanger functions according to
DIN 40046-36, DIN 40046-37
Sulfur dioxide (SO2) Concentration 10 ±0.3 ppm
Ambient conditions
- Temperature: 25°C (±2°C)
- Humidity: 75% (±5%)
- Test duration: 10 days
Hydrogen sulfide (H2S) Concentration 1 ±0.3 ppm
Ambient conditions
- Temperature: 25°C (±2°C)
- Humidity: 75% (±5%)
- Test duration: 4 days
Resistance of housing material to termites Resistant
Resistance of housing material to fungal decay Resistant

Mechanical tests
Vibration resistance according to EN 60068-2-6, Operation: 5g
IEC 60068-2-6
Shock test according to EN 60068-2-27, IEC 60068-2-27 25g

Conformance with EMC Directive 2014/30/EU


Noise immunity test according to EN 61000-6-2
Electrostatic discharge (ESD) EN 61000-4-2/ Criterion B
IEC 61000-4-2 6 kV contact discharge
8 kV air discharge
Electromagnetic fields EN 61000-4-3 Criterion A
IEC 61000-4-3 Field strength: 10 V/m

8607_en_06 Phoenix Contact 166 / 185


ILC 191 ME/X

Conformance with EMC Directive 2014/30/EU


Fast transients (burst) EN 61000-4-4/ Criterion B
IEC 61000-4-4 Supply lines: 2 kV
Signal/data lines: 2 kV
Surge test EN 61000-4-5 Criterion B
IEC 61000-4-5 Signal/data lines: 1 kV
Supply lines: 0.5 kV
Conducted interference EN 61000-4-6 Criterion A
IEC 61000-4-6 Test voltage: 10 V
Noise emission test according to EN 61000-6-4 Class A

NOTE: Radio interference


This is a Class A item of equipment. When using the equipment in residential areas, it may cause radio
interference. In this case, the operator may be required to implement appropriate measures and to pay the
resulting costs.

Approvals
For the latest approvals, please visit phoenixcontact.com or phoenixcontact.net/products.

Items manufactured until the start of 2023 comply with directive 2014/34/EU (ATEX).
You may use these items in potentially explosive areas of category 3.
Items manufactured afterwards do not meet the requirements of directive 2014/34/EU.
Use in potentially explosive areas of category 3 is not permitted.
If you use an item with ATEX-relevant printing in a potentially explosive area, please observe the associated
documentation.
Please also observe the specifications in the AH DE IL EX ZONE 2 (German) or AH EN IL EX ZONE 2
(English) application note.
If the item used by you does not feature ATEX-relevant identification, use in potentially explosive
areas is not permitted.

6.1.1 Tolerance values for the analog inputs

Tolerances at TA = 25°C; 500 kbps, without mean value


Absolute Relative
Typical Maximum Typical Maximum
0 V ... 10 V ±30 mV ±60 mV ±0.3% ±0.6%

Tolerances and temperature response at TA = -25°C ... 55°C


Drift
Typical Maximum
0 V ... 10 V ±75 ppm/K ±100 ppm/K

167 / 185 Phoenix Contact 8607_en_06


Technical data and ordering data

The maximum tolerance values represent the worst-case measurement inaccuracy.


Besides maximum offset and gain drift, they also include longtime drift as well as the
maximum tolerances of the test and calibration equipment.

Tolerances influenced by electromagnetic interference


Electromagnetic fields EN 61000-4-3/ < 1%
IEC 61000-4-3
Conducted interference EN 61000-4-6/ < 1%
IEC 61000-4-6
Fast transients (burst) EN 61000-4-4/ < 3.5%
IEC 61000-4-4
Additional tolerances may occur due to the influence of high-frequency electromagnetic
interference caused by wireless transmission systems in the immediate vicinity. The
specified values refer to nominal operation. The components are directly exposed to
interference without the use of additional shielding measures such as a steel cabinet, etc.
The tolerances specified above can be reduced through additional shielding measures for
the I/O module (e.g., use of a shielded control box/control cabinet, etc.).

6.1.2 Tolerance values for the analog outputs

Tolerances at TA = 25°C; 500 kbps, without mean value


Absolute Relative
Typical Maximum Typical Maximum
0 V ... 10 V ±30 mV ±60 mV ±0.3% ±0.6%

Tolerances and temperature response at TA = -25°C ... 55°C


Drift
Typical Maximum
0 V ... 10 V ±50 ppm/K ±75 ppm/K
The maximum tolerance values represent the worst-case measurement inaccuracy.
Besides maximum offset and gain drift, they also include longtime drift as well as the
maximum tolerances of the test and calibration equipment.

Tolerances influenced by electromagnetic interference


Electromagnetic fields EN 61000-4-3/ < 1%
IEC 61000-4-3
Conducted interference EN 61000-4-6/ < 1%
IEC 61000-4-6
Fast transients (burst) EN 61000-4-4/ < 1%
IEC 61000-4-4
Additional tolerances may occur due to the influence of high-frequency electromagnetic
interference caused by wireless transmission systems in the immediate vicinity. The
specified values refer to nominal operation. The components are directly exposed to

8607_en_06 Phoenix Contact 168 / 185


ILC 191 ME/X

interference without the use of additional shielding measures such as a steel cabinet, etc.
The tolerances specified above can be reduced through additional shielding measures for
the I/O module (e.g., use of a shielded control box/control cabinet, etc.).

169 / 185 Phoenix Contact 8607_en_06


Technical data and ordering data

6.2 Ordering data

6.2.1 Modules

Description Type Order No. Pcs./Pkt.


Inline controller with integrated pulse direction interface, ILC 191 ME/AN 2700074 1
RS-485/422, analog inputs (0 ... 10 V) and analog outputs
(0 ... 10 V), can be programmed according to IEC 61131-3
Inline controller with integrated pulse direction interface, ILC 191 ME/INC 2700075 1
RS-485/RS-422, fast counters, and incremental encoder in-
puts, can be programmed according to IEC 61131-3

6.2.2 Accessories

Description Type Order No. Pcs./Pkt.


For the latest accessories, visit phoenixcontact.net/products.

6.2.3 Software

Description Type Order No. Pcs./Pkt.


PC Worx Express automation software PC WORX EXPRESS 2988670 1
PC Worx automation software See current catalog from Phoenix Contact phoenixcon-
tact.net/products

6.2.4 Documentation

Description Type Order No. Pcs./Pkt.


“Modbus TCP with Phoenix Contact controllers” application AH EN MODBUS/TCP – 1
note
“Configuring and installing the INTERBUS Inline product IB IL SYS PRO UM E – 1
range” user manual
“Automation terminals of the Inline product range” user man- IL SYS INST UM E – 1
ual
“PC Worx Express Version 5.20 or later” quick start guide UM QS EN PC WORX – 1
EXPRESS
“PC Worx Version 6.10 or later” quick start guide UM QS EN PC WORX – 1
“PROFINET basics” user manual UM EN PROFINET SYS – 1
“PROFINET controller/device functions” user manual UM EN PROFINET CTRL – 1
DEV
“Applicative system redundancy” application note AH EN APPLICATIVE SYS- – 1
TEM REDUNDANCY

8607_en_06 Phoenix Contact 170 / 185


ILC 191 ME/X

A Appendix: Service and maintenance

A1 Error causes and remedies


Table A-1 Installation error causes and remedies

Error Cause Remedy


No outputs can be set. The power supply US is not present Connect the power supply.
(see diagnostics LED).
The devices connected to the Inline The power supply US is not present Connect the power supply.
controller cannot be read in. (see diagnostics LED).
The IEC 61131 program is not run- Mode selector switch in STOP posi- Set mode selector switch to RUN/PROG
ning. tion. position.
The serial interface is not operating. The connector pin assignment of the Use the COM CAB MINI DIN connecting
connecting cable or of the connector cable, Order No. 2400127, for the Inline
adapter used is incorrect. controller.
The devices on the remote bus can- The IBS IL 24 RB-T-PAC Inline ter- Insert the terminal as the first Inline termi-
not be started up. minal is not installed directly after the nal directly next to the Inline controller.
Inline controller.
The diagnostics LED on a device is The device has not been assembled Check the connection to the previous
flashing quickly. correctly. module (bus contacts).
The Inline controller cannot be ad- The IP address on the Inline control- Check the IP settings and adapt them to
dressed via the IP address. ler has been changed or does not your application, if necessary (see also
match the IP settings of the network Section “Assigning the IP address for the
devices involved. controller” on page 59).

A2 Updating the Inline controller firmware


The firmware (integrated software on the Inline controller) can be updated using the
Ethernet interface. Such firmware updates are exclusively used for adding new functions
that are implemented within the scope of continuous product improvement. No firmware
update is required for normal system operation.

To update the firmware via the Ethernet interface, proceed as described in the “Firmware
Update ILC 1.../3..., RFC 4...” application note. It can be downloaded at
phoenixcontact.net/products.

171 / 185 Phoenix Contact 8607_en_06


Connecting unshielded cables

A3 Connecting unshielded cables


Unshielded cables are used to connect the I/O devices and the supply voltage to the Inline
controller.
Connect these cables to the relevant Inline connectors using the spring-cage connection
method. You may connect cables with a connection cross section of 0.2 mm2 to 1.5 mm2
(24 - 16 AWG).

Figure A-1 Connecting unshielded cables

Wire the connectors according to your application.


When wiring, proceed as follows:
• Strip 8 mm off the cable.

Inline wiring is normally done without ferrules. However, it is possible to use ferrules. If
using ferrules, make sure they are properly crimped.

• Push a screwdriver into the actuation shaft of the appropriate terminal point (Figure A-1,
A) so that you can insert the wire into the spring opening.
Phoenix Contact recommends the SFZ 1-0,6x3,5 screwdriver (Order No. 1204517).
• Insert the wire (Figure A-1, B). Remove the screwdriver from the opening. This clamps
the wire.
After installation, the wires and the terminal points should be marked.

8607_en_06 Phoenix Contact 172 / 185


ILC 191 ME/X

A4 Connecting the shield


For some Inline controller connectors, it is necessary to connect a shield.

A 15
a
8
B

E
C D

Figure A-2 Connecting the shield

• Strip the outer cable sheath to the desired length (a) (A in Figure A-2).
Shorten the braided shield to 15 mm and wrap it around the outer sheath.
Remove the protective foil.
Strip 8 mm off the wires.
Connect the cables according to the terminal point assignment.
• Open the shield connection (B in Figure A-2).
• Insert the shield connection clamp according to the conductor cross section.
Insert the cable (C in Figure A-2).
• Close the shield connection (D in Figure A-2).
• Fasten the screws of the shield connection tightly using a screwdriver (E in Figure A-2).

173 / 185 Phoenix Contact 8607_en_06


Appendixes

B Appendixes

B1 List of figures

Section 2
Figure 2-1: Connected Inline local bus .................................................................. 14
Figure 2-2: Remote bus levels .............................................................................. 14
Figure 2-3: The Inline controller for position control .............................................. 15
Figure 2-4: PROFINET device using the ILC 191 ME/AN as an example ............. 16
Figure 2-5: Applicative system redundancy – example ......................................... 17
Figure 2-6: Structure of the ILC 191 ME/AN Inline controller ................................. 19
Figure 2-7: Structure of the ILC 191 ME/INC Inline controller ................................ 20
Figure 2-8: Diagnostics and status indicators of the ILC 191 ME/AN (A)
and the ILC 191 ME/INC (B) ............................................................... 21
Figure 2-9: Mode selector switch of the Inline controller,
ILC 191 ME/AN illustrated ................................................................... 25
Figure 2-10: Inserting (A) and removing (B) the parameterization memory ............. 27
Figure 2-11: Internal basic circuit diagram of the ILC 191 ME/AN ........................... 28
Figure 2-12: Internal basic circuit diagram of the ILC 191 ME/INC .......................... 29
Figure 2-13: Snapping on the Inline controller (1) ................................................... 31
Figure 2-14: Snapping on the Inline controller (2) ................................................... 31
Figure 2-15: Connectors to be removed if terminals are installed next to
the Inline controller, ILC 191 ME/AN illustrated ................................... 32
Figure 2-16: Removing the Inline controller (1) ....................................................... 33
Figure 2-17: Removing the Inline controller (2) ....................................................... 33
Figure 2-18: Communication paths, ILC 191 ME/AN illustrated .............................. 34
Figure 2-19: Ethernet interface ............................................................................... 35
Figure 2-20: Connecting the Ethernet cable to the Inline controller,
ILC 191 ME/AN illustrated ................................................................... 35
Figure 2-21: Connecting cable between PC and Inline controller,
ILC 191 ME/AN illustrated ................................................................... 36
Figure 2-22: Overload range with fall-back characteristic curve ............................. 39
Figure 2-23: Overload range without fall-back characteristic curve ....................... 39
Figure 2-24: Connecting the supply voltages, ILC 191 ME/AN illustrated ............... 40
Figure 2-25: Assignment of the terminal points of connector 2,
ILC 191 ME/AN illustrated ................................................................... 44
Figure 2-26: Basic wiring of an output with a load (L)
(shown using the ILC 191 ME/AN as an example) .............................. 44

8607_en_06 Phoenix Contact 174 / 185


ILC 191 ME/X

Figure 2-27: Assignment of the terminal points of connector 3, ILC 191 ME/AN
illustrated ............................................................................................ 46
Figure 2-28: Assignment of the terminal points of connector 4, ILC 191 ME/AN
illustrated ............................................................................................ 47
Figure 2-29: Assignment of the terminal points of connector 5, ILC 191 ME/AN
illustrated ............................................................................................ 48
Figure 2-30: RS-485/RS-422 interface wiring: full duplex mode ............................. 49
Figure 2-31: RS-485/RS-422 interface wiring: half duplex mode ............................ 49
Figure 2-32: RS-485/RS-422 interface wiring: termination resistor ......................... 50
Figure 2-33: Assignment of the terminal points of connector 6 on
the ILC 191 ME/AN ............................................................................. 51
Figure 2-34: Connection for voltage measurement ................................................. 52
Figure 2-35: Differential voltage input with active 3-wire transmitter ....................... 52
Figure 2-36: Assignment of the terminal points of connector 7 on
the ILC 191 ME/AN ............................................................................. 53
Figure 2-37: Assignment of the terminal points of connector 6 on
the ILC 191 ME/INC ............................................................................ 54
Figure 2-38: Assignment of the terminal points of connector 7 on
the ILC 191 ME/INC ............................................................................ 55

Section 3
Figure 3-1: Project information after creating a new project .................................. 58
Figure 3-2: DCP: setting the IP address ................................................................ 59
Figure 3-3: Starting IP address assignment via DCP ............................................ 60
Figure 3-4: Entering the MAC address .................................................................. 61
Figure 3-5: “Extras, BootP/SNMP/TFTP-Configuration...” menu ........................... 62
Figure 3-6: “Activate BootP” button ....................................................................... 62
Figure 3-7: Message window following BootP ...................................................... 62
Figure 3-8: Activating the PROFINET device function .......................................... 63
Figure 3-9: “Settings Communication Path” dialog ................................................ 63
Figure 3-10: Sending PROFINET device function/settings: service executed
successfully ........................................................................................ 64
Figure 3-11: Activate Network Settings: Restart Controller ..................................... 65
Figure 3-12: “Settings Communication Path” dialog ................................................ 65
Figure 3-13: Activating the network settings: service executed successfully .......... 66
Figure 3-14: Bus Structure: PROFINET context menu “Read PROFINET...” .......... 67
Figure 3-15: “Read PROFINET” dialog ................................................................... 67
Figure 3-16: ILC 191 ME/INC inserted as a PROFINET device .............................. 68
Figure 3-17: ILC 191 ME/INC as a PROFINET device: Process Data ..................... 68
Figure 3-18: Procedure for using the SD card as the main or additional memory .... 70

175 / 185 Phoenix Contact 8607_en_06


List of figures

Figure 3-19: Setting the SD card as the main memory ............................................ 71


Figure 3-20: Setting the SD card as the additional memory .................................... 73
Figure 3-21: “sddisk” directory on the SD card ........................................................ 74
Figure 3-22: Newly created “Logfile” directory in the “sddisk” directory .................. 74
Figure 3-23: Opening the “Logfile.txt” file using the FILE_OPEN function block ..... 75
Figure 3-24: Extended Settings: Open FTP Folder on Device ................................ 76
Figure 3-25: Internet Options: Enable FTP folder view ............................................ 77
Figure 3-26: Deactivating the FTP server ................................................................ 78
Figure 3-27: Opening the library and selecting the service ..................................... 79
Figure 3-28: Defining a user name and password for FTP access .......................... 80
Figure 3-29: Removing the user name and password for FTP access .................... 81
Figure 3-30: Disabling HTTP ................................................................................... 82
Figure 3-31: Setting HTTPS .................................................................................... 83
Figure 3-32: Activating the journaling function ........................................................ 85
Figure 3-33: Activating the MRP client function ....................................................... 86
Figure 3-34: PULSE_CH1 function block ................................................................ 89
Figure 3-35: Selecting the “Number of pulses reached Px” event ........................... 91
Figure 3-36: Signal curve when the REQUEST input is set to FALSE too
early (the DONE output is only TRUE for one cycle) ........................... 92
Figure 3-37: Signal curve when the output signal frequency is changed ................. 92
Figure 3-38: Signal curve when the value specified at the PULSE_CNT input is
reached (the DONE output is only TRUE for one cycle) ...................... 92
Figure 3-39: Signal curve when the output signal frequency is changed and
output is continuous (PULSE_CNT = 0) .............................................. 93
Figure 3-40: RS232_INIT function block ................................................................. 93
Figure 3-41: RS232_SEND function block .............................................................. 95
Figure 3-42: RS232_RECEIVE function block ........................................................ 97
Figure 3-43: RS485_422_INIT function block ......................................................... 99
Figure 3-44: RS485_422_SEND function block .................................................... 101
Figure 3-45: Signal sequence when REQUEST = TRUE ...................................... 102
Figure 3-46: RS485_422_RECEIVE function block .............................................. 103
Figure 3-47: Signal sequence when receiving a stream of data ............................ 104
Figure 3-48: CNT_1 and CNT_2 function blocks: CNT_1 illustrated ..................... 105
Figure 3-49: Selecting the “Event Value CNTx” event ........................................... 107
Figure 3-50: INC_CNT_1 and INC_CNT_2 function blocks: INC_CNT_1
function block illustrated ................................................................... 112
Figure 3-51: Selecting the “Event Value INC_CNTx” event ................................... 113
Figure 3-52: Phase relation of channels for counting direction up ......................... 115
Figure 3-53: Phase relation of channels for counting direction down .................... 115

8607_en_06 Phoenix Contact 176 / 185


ILC 191 ME/X

Figure 3-54: Example programming ...................................................................... 116


Figure 3-55: Alignment - padding bytes in data gaps ............................................ 117
Figure 3-56: Example programming with padding bytes ....................................... 118

Section 4
Figure 4-1: Event task: selecting the “Input X Terminal point DI/X.X” event ........ 120
Figure 4-2: Error location in the diagnostic parameter register ........................... 125

Section 5
Figure 5-1: Hardware structure of an Easy Motion application with the
ILC 191 ME/AN and ILC 191 ME/INC Inline controllers .................... 130
Figure 5-2: Direction output: direction of rotation right ........................................ 131
Figure 5-3: Direction output: direction of rotation left ........................................... 131
Figure 5-4: Pulse output: ratio of frequency to speed .......................................... 131
Figure 5-5: Diagram of an axis application .......................................................... 133
Figure 5-6: Homing: procedure 1 ........................................................................ 134
Figure 5-7: Homing: procedure 2 ........................................................................ 135
Figure 5-8: Homing: procedure 3 ........................................................................ 135
Figure 5-9: Homing: procedure 4 ........................................................................ 136
Figure 5-10: M191_DRV1 driver block .................................................................. 139
Figure 5-11: M191_Power function block .............................................................. 143
Figure 5-12: M191_HomePARA function block .................................................... 145
Figure 5-13: M191_Home function block .............................................................. 147
Figure 5-14: M191_MoveAbsolute function block ................................................. 149
Figure 5-15: M191_MoveRelative function block .................................................. 151
Figure 5-16: M191_MoveVelocity function block .................................................. 153
Figure 5-17: M191_Reset function block .............................................................. 155
Figure 5-18: M191_Stop function block ................................................................ 156
Figure 5-19: Application example for performing an absolute move. .................... 158

Appendix A
Figure A-1: Connecting unshielded cables .......................................................... 172
Figure A-2: Connecting the shield ....................................................................... 173

177 / 185 Phoenix Contact 8607_en_06


List of tables

B2 List of tables

Section 2
Table 2-1: Diagnostics and status indicators ........................................................ 21

Section 3
Table 3-1: Overview of the function blocks ........................................................... 87
Table 3-2: Overview of the function blocks ........................................................... 88
Table 3-3: Overview of the function blocks ........................................................... 88
Table 3-4: Inputs of the PULSE_CH1 and PULSE_CH2 function blocks .............. 89
Table 3-5: Outputs of the PULSE_CH1 and PULSE_CH2 function blocks ........... 90
Table 3-6: Error values of the STATUS output (ERROR = TRUE) ........................ 91
Table 3-7: Inputs of the RS232_INIT function block.............................................. 94
Table 3-8: Outputs of the RS232_INIT function block........................................... 94
Table 3-9: Status values of the STATUS output (ERROR = TRUE) ...................... 94
Table 3-10: Input of the RS232_SEND function block ............................................ 95
Table 3-11: Outputs of the RS232_SEND function block........................................ 95
Table 3-12: Status values of the STATUS output (ERROR = TRUE) ...................... 96
Table 3-13: Input of the RS232_RECEIVE function block....................................... 97
Table 3-14: Outputs of the RS232_RECEIVE function block .................................. 97
Table 3-15: Status values of the STATUS output (ERROR = TRUE) ...................... 98
Table 3-16: Inputs of the RS485_422_INIT function block...................................... 99
Table 3-17: Outputs of the RS485_422_INIT function block................................. 100
Table 3-18: Status values of the STATUS output (ERROR = TRUE) .................... 100
Table 3-19: Inputs of the RS485_422_SEND function block ................................ 101
Table 3-20: Outputs of the RS485_422_SEND function block.............................. 101
Table 3-21: Status values of the STATUS output (ERROR = TRUE) .................... 102
Table 3-22: Inputs of the RS485_422_RECEIVE function block ........................... 103
Table 3-23: Outputs of the RS485_422_RECEIVE function block ........................ 103
Table 3-24: Status values of the STATUS output (ERROR = TRUE) .................... 104
Table 3-25: Inputs of the CNT1 and CNT2 function blocks................................... 106
Table 3-26: Outputs of the CNT1 and CNT2 function blocks ................................ 107
Table 3-27: Status values of the STATUS output (ERROR = TRUE) .................... 108
Table 3-28: Counter operating modes .................................................................. 109
Table 3-29: Inputs of the INC_CNT1 and INC_CNT2 function blocks................... 112
Table 3-30: Outputs of the INC_CNT1 and INC_CNT2 function blocks................ 114

8607_en_06 Phoenix Contact 178 / 185


ILC 191 ME/X

Table 3-31: Status values of the STATUS output (ERROR = TRUE) .................... 114
Table 3-32: Counter operating modes .................................................................. 114
Table 3-33: Derivation of the counting direction.................................................... 115

Section 4
Table 4-1: System variables of the status register for local digital inputs
and outputs........................................................................................ 119
Table 4-2: System variables of the status register for local analog inputs
and outputs........................................................................................ 120
Table 4-3: Significant measured values.............................................................. 121
Table 4-4: Error values of analog inputs ............................................................. 121
Table 4-5: Output values .................................................................................... 122
Table 4-6: System variables of the status register for counter inputs .................. 123
Table 4-7: System variables of the status register for incremental
encoder inputs ................................................................................... 123
Table 4-8: System variables of the diagnostic status register ............................. 124
Table 4-9: System variables of the diagnostic parameter register ...................... 125
Table 4-10: PROFINET system variables (PROFINET device function) ............... 126
Table 4-11: System variables of the IEC 61131 runtime system ........................... 127
Table 4-12: System variables of the control processor ......................................... 128
Table 4-13: System variables of the power storage and realtime clock ................ 128
Table 4-14: System variables of the power supplies............................................. 128
Table 4-15: System variables of the mode selector switch ................................... 129
Table 4-16: System variables of the system time.................................................. 129

Section 5
Table 5-1: Overview of the Easy Motion function blocks..................................... 138
Table 5-2: Inputs of the M191_DRV function block............................................. 139
Table 5-3: Outputs of the M191_DRV function block .......................................... 141
Table 5-4: Input/output of the M191_DRV function block ................................... 141
Table 5-5: Diagnostic value of the wDiagCode output (xError = TRUE) ........... 141
Table 5-6: Inputs of the M191_Power function block .......................................... 143
Table 5-7: Outputs of the M191_Power function block ....................................... 143
Table 5-8: Input/output of the M191_Power function block ................................. 144
Table 5-9: Error values of the ErrorID output (Error = TRUE)............................ 144
Table 5-10: Inputs of the M191_HomePARA function block ................................. 145
Table 5-11: Outputs of the M191_HomePARA function block .............................. 146
Table 5-12: Input/output of the M191_HomePARA function block........................ 146

179 / 185 Phoenix Contact 8607_en_06


List of tables

Table 5-13: Diagnostic value of the wDiagCode output (xError = TRUE) ........... 146
Table 5-14: Inputs of the M191_Home function block........................................... 147
Table 5-15: Outputs of the M191_Home function block........................................ 147
Table 5-16: Input/output of the M191_Home function block ................................. 148
Table 5-17: Error values of the ErrorID output (Error = TRUE)............................ 148
Table 5-18: Inputs of the M191_MoveAbsolute function block ............................. 149
Table 5-19: Outputs of the M191_MoveAbsolute function block .......................... 149
Table 5-20: Input/output of the M191_MoveAbsolute function block .................... 150
Table 5-21: Error values of the ErrorID output (Error = TRUE)............................ 150
Table 5-22: Inputs of the M191_MoveRelative function block .............................. 151
Table 5-23: Outputs of the M191_MoveRelative function block............................ 151
Table 5-24: Input/output of the M191_MoveRelative function block ..................... 152
Table 5-25: Error values of the ErrorID output (Error = TRUE)............................ 152
Table 5-26: Inputs of the M191_MoveVelocity function block............................... 153
Table 5-27: Outputs of the M191_MoveVelocity function block ............................ 153
Table 5-28: Input/output of the M191_MoveVelocity function block...................... 154
Table 5-29: Error values of the ErrorID output (Error = TRUE).............................. 154
Table 5-30: Input of the M191_Reset function block............................................. 155
Table 5-31: Outputs of the M191_Reset function block ........................................ 155
Table 5-32: Input/output of the M191_Reset function block.................................. 155
Table 5-33: Error values of the ErrorID output (Error = TRUE)............................ 155
Table 5-34: Inputs of the M191_Stop function block............................................. 156
Table 5-35: Outputs of the M191_Stop function block .......................................... 156
Table 5-36: Input/output of the M191_Stop function block.................................... 156
Table 5-37: Error values of the ErrorID output (Error = TRUE)............................ 157

Appendix A
Table A-1: Installation error causes and remedies .............................................. 171

8607_en_06 Phoenix Contact 180 / 185


ILC 191 ME/X

B3 Index

A F
Analog inputs .............................................................. 51 Fall-back characteristic curve ..................................... 39
Analog outputs ............................................................ 53 Firmware update ....................................................... 171
Applicative system redundancy .................................. 17 FTP access
Deactivate FTP server........................................... 78
B User name and password ..................................... 79
Basic circuit diagram FTP functionality ......................................................... 76
ILC 191 ME/AN ..................................................... 28 Function blocks
ILC 191 ME/INC .................................................... 29 For counter inputs ............................................... 105
Basic wiring of an output ............................................. 44 For Ethernet communication ................................. 88
BootP .......................................................................... 60 For handling files on the parameterization memory 87
BootP server ............................................................... 33 For incremental encoder inputs ........................... 112
For PCP communication........................................ 88
C For pulse width modulation ................................... 89
For RS-232 communication................................... 93
Communication path ................................................... 34
For RS-485/RS-422 communication ..................... 99
Connecting cables .................................................... 172
of the Easy Motion function block library ............. 138
Connecting the shield ............................................... 173
Connecting the supply voltage .................................... 40
Connecting unshielded cables .................................. 172
H
Connection elements .................................................. 19 Hardware requirements ................................................ 9
Connector ................................................................... 31 HTTP server
Control box.................................................................. 30 Activating/deactivating the HTTP server ............... 82
See also Terminal box
Control cabinet............................................................ 30 I
Counter inputs............................................................. 54 ILC 191 ME/AN
Connector ............................................................. 19
D Diagnostics and status indicators.......................... 19
Delivery state .............................................................. 26 Electronics base.................................................... 19
Diagnostics indicators ................................................. 21 End plate ............................................................... 19
Digital inputs ............................................................... 44 Ethernet connection .............................................. 19
Digital outputs ............................................................. 46 Mode selector switch....................................... 19, 20
DIN rail ........................................................................ 30 Reset button.......................................................... 19
RS-232 interface ................................................... 19
E ILC 191 ME/INC
Card holder ........................................................... 20
Electronics base.......................................................... 31
Connector ............................................................. 20
End bracket................................................................. 30
Diagnostics and status indicators.......................... 20
End plate..................................................................... 30
Electronics base.................................................... 20
Error causes.............................................................. 171
End plate ............................................................... 20
Error diagnostics ......................................................... 21
Ethernet connection .............................................. 20
Ethernet ...................................................................... 35
Reset button.......................................................... 20
Ethernet interface........................................................ 35
RS-232 interface ................................................... 20
Slot for the parameterization memory.................... 20

181 / 185 Phoenix Contact 8607_en_06


Index

Incremental encoder inputs......................................... 55 Reset button ............................................................... 26


Inline local bus ............................................................ 14 Resetting the Inline controller ................................ 26
INTERBUS.................................................................. 38 Resetting the controller ............................................... 65
IP address RS-232 cables ............................................................ 36
Setting ............................................................. 59, 62
IP20............................................................................. 30 S
SD card
L Additional memory ................................................ 72
Local bus..................................................................... 38 Functions .............................................................. 70
Main memory ........................................................ 70
M Memory for log files ............................................... 74
MAC address .............................................................. 33 Serial interface
Mode selector switch .................................................. 25 PRG ...................................................................... 36
Mounting ............................................................... 30, 31 RS-485/RS-422..................................................... 48
Mounting location........................................................ 30 Sizing of the power supply .......................................... 39
Mounting position........................................................ 30 Software requirements.................................................. 9
Status indicators ......................................................... 21
O System variables....................................................... 119

Operating elements..................................................... 19
T
P Terminal box ............................................................... 30

Parameterization memory ........................................... 26


Parameterization memory, integrated ......................... 26
Parameterization memory, plug-in .............................. 26
Ports............................................................................ 84
Power supply .............................................................. 39
Connection ............................................................ 40
Power supply sizing .................................................... 39
Power supply without fall-back characteristic curve ... 39,
159
PROFINET
“Read PROFINET” dialog...................................... 67
Activating the device function ................................ 63
Device inserted ..................................................... 68
Device process data.............................................. 68
Integrating the device (example) ........................... 66
PROFINET device ................................................. 63
Read PROFINET................................................... 67
PWM outputs .............................................................. 47

R
Realtime clock............................................................. 69
Removal................................................................ 30, 32
Replacement............................................................... 33

8607_en_06 Phoenix Contact 182 / 185


ILC 191 ME/X

183 / 185 Phoenix Contact 8607_en_06


Please observe the following notes
General Terms and Conditions of use for technical documentation
Phoenix Contact reserves the right to alter, correct, and/or improve the technical
documentation and the products described in the technical documentation at its own
discretion and without giving prior notice, insofar as this is reasonable for the user. The
same applies to any technical changes that serve the purpose of technical progress.
The receipt of technical documentation (in particular user documentation) does not
constitute any further duty on the part of Phoenix Contact to furnish information on
modifications to products and/or technical documentation. You are responsible to verify the
suitability and intended use of the products in your specific application, in particular with
regard to observing the applicable standards and regulations. All information made
available in the technical data is supplied without any accompanying guarantee, whether
expressly mentioned, implied or tacitly assumed.
In general, the provisions of the current general Terms and Conditions of Phoenix Contact
apply exclusively, in particular as concerns any warranty liability.
This manual, including all illustrations contained herein, is copyright protected. Any
changes to the contents or the publication of extracts of this document are prohibited.
Phoenix Contact reserves the right to register its own intellectual property rights for the
product identifications of Phoenix Contact products that are used here. Registration of such
intellectual property rights by third parties is prohibited.
Other product identifications may be afforded legal protection, even where they may not be
indicated as such.

Phoenix Contact 184 / 185


185

How to contact us
Internet Up-to-date information on Phoenix Contact products and our Terms and Conditions can be
found on the Internet at:
phoenixcontact.com
Make sure you always use the latest documentation.
It can be downloaded at:
phoenixcontact.net/products

Subsidiaries If there are any problems that cannot be solved using the documentation, please contact
your Phoenix Contact subsidiary.
Subsidiary contact information is available at phoenixcontact.com.

Published by PHOENIX CONTACT GmbH & Co. KG


Flachsmarktstraße 8
32825 Blomberg
GERMANY
PHOENIX CONTACT Development and Manufacturing, Inc.
586 Fulling Mill Road
Middletown, PA 17057
USA
Should you have any suggestions or recommendations for improvement of the contents and
layout of our manuals, please send your comments to:
tecdoc@phoenixcontact.com

185 / 185 Phoenix Contact GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany
phoenixcontact.com
© Phoenix Contact 2023-02-03

Phoenix Contact GmbH & Co. KG


Flachsmarktstraße 8
32825 Blomberg, Germany
Phone: +49 5235 3-00
Fax: +49 5235 3-41200
8607_en_06

Email: info@phoenixcontact.com
phoenixcontact.com

You might also like