Manual ILC 151

Installing, starting up, and operat-
ing the ILC 151 GSM/GPRS Inline

controller
User manual
User manual
Installing, starting up, and operating the ILC 151 GSM/GPRS Inline con-
troller
2015-10-09
Designation: UM EN ILC 151 GSM/GPRS
Revision: 03
Order No.:
This user manual is valid for:
Designation As of version As of version Order No.

(HW) (FW)
ILC 151 GSM/GPRS 01 4.06 2700977
PHOENIX CONTACT 8510_en_03

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.
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
injury 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
result 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
information or refer to detailed sources of information.
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

Flachsmarktstrae 8
32825 Blomberg
GERMANY
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
PHOENIX CONTACT
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 standard 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 is 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
Table of contents
1 Foreword ....................................................................................................................................9
1.1 Purpose of this user manual ..................................................................................9
1.2 Intended use..........................................................................................................9
1.3 General safety notes..............................................................................................9
1.4 Disposal...............................................................................................................10
1.5 Hardware and software requirements..................................................................10
2 Description of the Inline controller ............................................................................................11

2.1 General description of the Inline controller...........................................................11
2.2 Possible fields of application of the ILC 151 GSM/GPRS ....................................14
2.3 Notes on using the Inline controller in potentially explosive areas .......................15
2.4 Unpacking the Inline controller.............................................................................16
2.5 Connection and operating elements ....................................................................17
2.6 Diagnostics and status indicators ........................................................................18
2.7 Reset button (concealed) ....................................................................................20
2.8 Parameterization memory....................................................................................20
2.8.1 Inserting/removing the parameterization memory ................................21
2.9 Mode selector switch ...........................................................................................22
2.10 Internal basic circuit diagram ...............................................................................23
2.11 Mounting and removing the Inline controller ........................................................24
2.12 Communication path............................................................................................28
2.13 SIM card ..............................................................................................................29
2.14 Antenna ...............................................................................................................30
2.15 INTERBUS ..........................................................................................................33
2.15.1 Local bus .............................................................................................33
2.15.2 Remote bus ..........................................................................................33
2.16 Power supply .......................................................................................................34
2.16.1 Sizing of the power supply ...................................................................34
2.16.2 Connecting the power supplies ............................................................35
2.16.3 24 V segment supply/24 V main supply ...............................................37
2.16.4 24 V segment supply ............................................................................37
2.16.5 24 V main voltage ................................................................................37
2.16.6 24 V ILC supply ....................................................................................37
2.16.7 Jumpers ...............................................................................................37
2.17 Digital inputs and outputs ....................................................................................38
3 The Inline controller under PC Worx general .........................................................................41

3.1 Software version..................................................................................................41
3.2 Assigning the IP address for the controller...........................................................42
3.2.1 Dynamic Configuration Protocol (DCP) ................................................42
8510_en_03 PHOENIX CONTACT 5

ILC 151 GSM/GPRS
3.2.2 BootP server ........................................................................................43

3.3 Setting the realtime clock under PC Worx............................................................46
3.4 Download changes ..............................................................................................46
3.5 Functions of the plug-in parameterization memory (SD card) ..............................47
3.5.1 Main memory .......................................................................................47
3.5.2 Additional memory ..............................................................................49
3.5.2.1 SD card as memory for log files ..................................................50
3.6 Parameterization memory and Internet Explorer..................................................52
3.6.1 Internet Explorer FTP functionality .......................................................53
3.6.2 Activating/deactivating the FTP server .................................................54
3.6.3 Restricting FTP access ........................................................................55
3.6.4 Activating/deactivating the HTTP server ..............................................58
3.6.5 Using the Hypertext Transfer Protocol Secure (HTTPS) ......................59
3.7 Sending e-mails securely.....................................................................................59
3.8 Activating/deactivating specific ports...................................................................60
3.9 Activating/deactivating the journaling function .....................................................61
3.10 Activating/deactivating the GPRS watchdog .......................................................62
3.11 Function blocks for handling files on the parameterization memory.....................64
3.12 Function blocks for
TCP/IP and UDP/IP communication ....................................................................65
GSM/GPRS mobile communication functions .....................................................66
3.13.1 MOBILE_CONNECT function block .....................................................67
3.13.2 SMS_SEND function block ..................................................................71
3.13.3 SMS_RECEIVE function block .............................................................76
3.13.4 GPRS_CONNECT function block ........................................................79
3.14 Function blocks for PCP communication .............................................................84
3.15 Alignment ............................................................................................................85
4 The Inline controller under PC Worx program creation and example projects .......................89
4.1 Creating a new project.........................................................................................89
4.2 GSM settings in PC Worx ....................................................................................92
4.3 GPRS settings in PC Worx ..................................................................................94
4.4 Example projects .................................................................................................96
4.4.1 Example: sending/receiving an SMS text message .............................96
4.4.2 Example: active IP communication ......................................................98
4.4.3 Example: passive IP communication ..................................................100
5 System variables and status information ................................................................................103

5.1 General notes ....................................................................................................103
5.2 Status register for local digital inputs and outputs..............................................103
6 PHOENIX CONTACT 8510_en_03

Table of contents
5.3 Diagnostic status register ..................................................................................104

5.4 Diagnostic parameter register............................................................................105
5.5 IEC 61131 runtime system.................................................................................106
5.6 Control processor ..............................................................................................107
5.7 Power storage, realtime clock............................................................................107
5.8 Power supplies ..................................................................................................107
5.9 Mode selector switch .........................................................................................108
5.10 System time.......................................................................................................108
5.11 Bit error rate (BER) ............................................................................................109
6 Technical data and ordering data ...........................................................................................111

6.1 Technical data ...................................................................................................111
6.2 Ordering data.....................................................................................................118
6.2.1 Products .............................................................................................118
6.2.2 Accessories .......................................................................................118
6.2.3 Software .............................................................................................118
6.2.4 Documentation ...................................................................................119
A Appendix: service, maintenance, and derating .......................................................................121

A1 Error causes and remedies................................................................................121
A2 Updating the Inline controller firmware...............................................................121
A3 Connecting unshielded cables...........................................................................122
A4 Derating .............................................................................................................123
B Appendix for document lists....................................................................................................125

B1 List of figures .....................................................................................................125
B2 List of tables ......................................................................................................129
B3 Index..................................................................................................................131

ILC 151 GSM/GPRS

Foreword
1 Foreword
1.1 Purpose of this user manual
This user manual helps you to start up and operate the ILC 151 GSM/GPRS Inline control-
ler.
In the following, the term Inline controller is used in general.
1.2 Intended use
The Inline controller is a modular small-scale controller that can be used for small and me-
dium-sized applications. The device conforms to IP20 protection and is intended for use in
a closed control cabinet or control box (terminal box) with IP54 protection or higher.
This device is designed for use in industrial environments.
The Inline controller is only to be used as specified in the latest user documentation. Phoe-
nix Contact accepts no liability if the controller is used for anything other than its designated
use.
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 a clean
and dry environment. Do not subject the device to mechanical and/or thermal loads that
exceed the specified limits.

ILC 151 GSM/GPRS
NOTE: Risk of unauthorized network access

Connecting devices to a network via Ethernet always entails the risk of unauthorized ac-
cess to the network.
Please check your application for any option of deactivating active communication chan-
nels (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.
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 Disposal
Do not dispose of the device with household waste, it should instead be disposed of in
accordance with the currently applicable national regulations. The device can also be re-
turned to Phoenix Contact.
1.5 Hardware and software requirements
Hardware Inline controller

GSM antenna (e.g., PSI-GSM/UMTS-QB-ANT; Order No. 2313371)
Ethernet cable (for connecting the Inline controller to a PC)
SIM card
Software PC Worx/PC Worx Express automation software in the following versions:

PC Worx Version 6.20 or later
(part of the AUTOMATIONWORX Software Suite 2012 1.70)
PC Worx Express Version 6.20 or later
Both software tools can be used to operate the ILC 151 GSM/GPRS in general. However,
to utilize the full range of functions of the ILC 151 GSM/GPRS, we recommend that you
use the PC Worx software with the specified version or later.
For the ordering data for hardware, software, and additional documentation, please refer
to Section Technical data and ordering data on page 111.

Description of the Inline controller
2 Description of the Inline controller
2.1 General description of the Inline controller
The Inline controller is a class 100 modular small-scale controller with integrated Ethernet
and INTERBUS connections. In addition, the ILC 151 GSM/GPRS has a built-in quad-band
modem.
IEC 61131 control perfor- The Inline controller is consistently configured and programmed in accordance with
mance IEC 61131 using the PC Worx automation software. PC Worx can be operated via the net-
work (Ethernet). The powerful processor can be programmed in all five IEC 61131 program-
ming languages and ensures fast processing of control tasks.
Integrated Ethernet con- The integrated Ethernet connection (via twisted pair cable) ensures Ethernet connectivity.
nection Throughout the Ethernet network, the Inline controller can be accessed via TCP/IP or
UDP/IP.
Integrated communication functions enable direct and effective data exchange via Ether-
net. The Ethernet connection 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 TCP/IP mode
and a UDP/IP mode.
When using the AX OPC server provided in the AUTOMATIONWORX Software Suite, Inline
controller data is available in the Ethernet network in a standardized format and can be used
for the different visualization packages.
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 (as of firmware Version 4.40 and AUTOMATIONWORX Software
Suite Version 1.82 AddOn V1). For additional information, please refer to the
AH EN MODBUS/TCP application note.
Integrated INTERBUS con- An Inline local bus as well as an INTERBUS remote bus can be connected via the
nection INTERBUS connection. In this way, you can create a complete INTERBUS system (maxi-
mum 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.
Parameterization memo- The Inline controller can be operated using a plug-in parameterization memory in the form
ry/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 118).

ILC 151 GSM/GPRS
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.
Mobile communication Mobile communication networks can be used for wireless telephony and data transmission.
networks
GSM services such as GPRS and SMS are used for data transmission within the mobile
communication networks.
GSM GSM is the abbreviation for Global System for Mobile Communication.
GSM is a standard for fully digital mobile communication networks that is mainly used for
telephony, line-switched and packet-switched data transmission as well as for short text
messages (SMS).
The GSM modem integrated in the ILC 151 GSM/GPRS enables the following functions to
be performed:
Sending and receiving SMS text messages
Remote maintenance of the ILC 151 GSM/GPRS via CSD or GPRS
Permanent GPRS connection for GPRS operation without application program (see Ta-
ble GPRS parameters in PC Worx on page 94)
TCP/IP connection via the application program using the corresponding function blocks
(see Function blocks for TCP/IP and UDP/IP communication on page 65)
The PC Worx software provides the MOBILE_CONNECT, SMS_SEND, and
SMS_RECEIVE function blocks to enable communication by SMS via the GSM network
using the ILC 151 GSM/GPRS.
CSD CSD is the abbreviation for Circuit Switched Data.

CSD is a line-oriented standard for data transmission in mobile communication networks
and is characterized by a low bit error rate.
As long as a CSD connection is active, the transmission channel to the partner is perma-
nently occupied, even if no data is exchanged. The transmission speed is 9.6 kbps.
A good wireless connection is required to ensure error-free data transmission via CSD. In-
terference-prone wireless connections with poor transmitting and receiving conditions in-
crease the probability of failure and reduce the effective data rate, as data packets have to
be repeatedly transmitted.
The PC Worx software enables remote maintenance of the ILC 151 GSM/GPRS via CSD
(see Section 4.2 GSM settings in PC Worx).
GPRS GPRS is the abbreviation for General Packet Radio Service.

GPRS is a service of the GSM mobile communication standard and is used for packet-ori-
ented data transmission.
If a GPRS connection is activated, there is only a virtual connection to the partner initially.
The transmission channel is only occupied when data is actually being transmitted, other-
wise it is free for other users. Therefore, no transmission channel is reserved permanently
for one user. GPRS costs are primarily based on the volume of data transmitted. GPRS is
packet-oriented. This means that data is divided into packets at the sender end, transmit-
ted, and reassembled at the receiver end. The GPRS technology bundles up all eight GSM
time slots of a channel. In theory, this allows for a data transmission speed of 171.2 kbps.

In practice, the number of available time slots within a frame is limited by the technical ca-
pabilities of the mobile station and the mobile communication networks. The maximum data
transmission speed that can be reached is 53.6 kbps. It depends on the signal-to-noise ra-
tio, the current network load, and the allocated time slots. This is roughly equivalent to the
speed of a V.90 telephone modem.
GPRS is also particularly suitable for remote control tasks. The major advantages of GPRS
with regard to remote control tasks are good network coverage and availability of GSM, as
well as low investment costs compared to other transmission methods. GPRS, for example,
is also used for vehicle positioning.
A GSM/GPRS connection is not always available. Availability depends on the provider

and the local infrastructure of the mobile communication network. For more information,
contact your provider.
The PC Worx software provides the GPRS_CONNECT function block which can be used
to establish a GPRS connection via the ILC 151 GSM/GPRS. The TCP/IP blocks enable
communication via this GPRS connection using the TCP/IP protocol.

ILC 151 GSM/GPRS
2.2 Possible fields of application of the

ILC 151 GSM/GPRS
The ILC 151 GSM/GPRS 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.
ILC 151 GSM/GPRS

Order-No.: 2700977
HW/FW: xx/xxx GSM E
MAC Addr.: xx.xx.xx.xx.xx.xx AV TR Q1 Q2 I1 I2 I9 I10
UL Q3 Q4 I3 I4 I11 I12
US FR RDY FAIL I5 I6 I13 I14
UM FF BSA PF I7 I8 I15 I16
RESET MRESET
STOP
RUN / PROG
LNK ACT
Ethernet 8510A001
Figure 2-1 Connected Inline local bus
Inline local bus

ILC 151 GSM/GPRS
Order-No.: 2700977
HW/FW: xx/xxx GSM E
AV TR Q1 Q2 I1 I2 I9 I10
D D D
MAC Addr.: xx.xx.xx.xx.xx.xx
RC RC RC
UL Q3 Q4 I3 I4 I11 I12
RD RD RD
LD LD LD
UM FF BSA PF I7 I8 I15 I16 RB-T RB-T RB-T
RESET MRESET
1.
STOP
RUN / PROG
LNK ACT
BA RD UL US 1 D 1 1 1 1 D 1 1 1 1 D 1 D 1 D
2 2 2 2 2 2 2 2 2 2 2
RC LD UM
DO8 DI8 DI2 DI2 DI2
2.
INTERBUS
Remote bus levels BA
RC
RD
LD
UL US
UM
1
DO8
D
2
1
2
1
2
1
2
1
DO8
D
2
1
2
1
2
1
2
1
DI2
D
2
1
DI2
D
2
1
DI2
D
2
3.
INTERBUS
BA RD UL US 1 D 1 1 1 1 D 1 1 1 1 D 1 D 1 D
2 2 2 2 2 2 2 2 2 2 2
RC LD UM
DO8 DO8 DI2 DI2 DI2
4.
INTERBUS 8510B002
Figure 2-2 Remote bus levels

2.3 Notes on using the Inline controller in potentially

explosive areas
Approval in accordance with directive 94/9/EC

II 3G Ex nA IIC T4 Gc X
WARNING: Explosion hazard

Make sure that the following notes and instructions are observed.
Installation notes
1. The Inline controller conforms to the requirements of n protection and can be installed
in a Zone 2 potentially explosive area. The Inline controller is a category 3G item of
equipment.
The Inline controller meets the requirements of EN 60079-0:2009 and
EN 60079-15:2010.
2. The Inline controller must only be installed, started up, and maintained by qualified spe-
cialist personnel.
3. Please follow the installation instructions given in the user manual and the package slip.
4. When installing and operating the device, the applicable safety regulations (including
national safety regulations), accident prevention regulations, as well as general techni-
cal regulations must be observed.
5. For the safety data, please refer to the corresponding documentation (user manual,
package slip) and the certificates (declaration of conformity and other approvals, if ap-
plicable).
6. Access to the circuits inside the Inline controller is not permitted. Do not repair the Inline
controller yourself but replace it with an approved controller of the same type.
Repairs may only be performed by the manufacturer. The manufacturer is not liable for
damage resulting from noncompliance.
7. The IP20 (EN 60529) degree of protection of the device is intended for use in a clean
and dry environment.
8. Do not subject the Inline controller to mechanical strain and/or thermal loads that ex-
ceed the limits specified in the product documentation.
9. The Inline controller is not designed for use in atmospheres with a danger of dust ex-
plosions. If dust is present, install the device in suitable, approved housing. Please note
the surface temperature of the housing.
Installation in Zone 2
1. Observe the specified conditions for use in potentially explosive areas.
2. Install the device in a suitable, approved housing (with at least IP54 protection accord-
ing to EN 60529) that meets the requirements of EN 60079-15.
3. In potentially explosive areas, only snap the device onto the DIN rail and remove it from
the DIN rail and connect and disconnect the cables when the power is disconnected.
4. Connect the DIN rail to protective earth ground.
5. Only connect devices to the supply and signal circuits in Zone 2 that are suitable for op-
eration in potentially explosive areas of Zone 2 and for the conditions at the installation
location.
6. The RJ45 connector must have a fully functional snap-in hook for safe operation. Re-
pair any damaged connectors immediately.

ILC 151 GSM/GPRS
7. For safe operation with the plug-in parameterization memory (SD card), this must be
fully plugged and snapped in. In potentially explosive areas, use the SD card as main
memory only. Don't insert or remove the SD card during operation.
8. The HF cable to the antenna must be suitable for the ambient conditions. Install the ca-
ble so that it is protected against mechanical damage, corrosion, chemical stress, and
negative effects from heat or UV radiation. The same applies to the antenna which is
connected to the cable and which functions as a cable termination.
9. The antenna itself must satisfy the requirements of EN 60079-0 with regard to the hous-
ing and electrostatic charge.
Restrictions/limit values
1. Only Inline terminals that are approved for use in potentially explosive areas
may be snapped onto the Inline controller.
Before using the Inline terminal in a Zone 2 potentially explosive area, check whether
this Inline terminal has been approved for installation within this area.
For a list of terminals that are approved for Zone 2 potentially explosive areas, please
refer to the AH EN IL EX ZONE 2 application note.
2. Please make sure that the maximum permissible current of 4 A flowing through poten-
tial jumpers UM and US (total current) is not exceeded when using the Inline controller
in potentially explosive areas.
3. Also make sure that the maximum permissible current of 2 A flowing through potential
jumper UL is not exceeded.
4. The maximum permissible current for each spring-cage contact is 2 A.
2.4 Unpacking the Inline controller
The Inline controller is supplied in an ESD bag together with a package slip with installation
instructions. Please 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 electro-
static discharge. When handling the Inline controller, observe the necessary safety pre-
cautions against electrostatic discharge (ESD) according to EN 61340-5-1 and IEC
61340-5-1.
NOTE:
To avoid possible damage to the module, unpack and pack the Inline controller in accor-
dance with the ESD regulations.

2.5 Connection and operating elements
1 12
2 I10
I9
3 er
/F
/GP
151 2700
ILC -No.:
xx
RS
GSM 977
Ord : xx/x x.xx.x

W xx.x
HW ddr.:
x.xx
.xx
O1 E
QE2
1
I1
I3
I2
I4
I11 4
3
I1 6
I1 5
I12
I1
I1
I6
MA
CA QD1 4
GSM I5
4
Q I8
TR Q3 I7
AV F2AIL
R1DY 4F
UL P
FR B3SA
U S
FF
UM
ET
ES
MR OP
ST
5 11
T
SE
RE G
RO
N/P
RU T
AC
K
LN
7
10
9
8
Figure 2-3 Structure of the 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 118.
3 Mode selector switch

4 Reset button
5 Ethernet connection
6 SIM card slot
The SIM card is not supplied as standard with the Inline controller.
7 SMA antenna connection
The antenna is not supplied as standard with the Inline controller.

Please refer to the ordering data in Section Accessories on page 118.
8 Connector 1: terminal points for voltage supply

9 Connector 2: output terminal points
10 Connectors 3 and 4: input terminal points
11 Diagnostics and status indicators
12 End plate (as station end)

ILC 151 GSM/GPRS
2.6 Diagnostics and status indicators
The diagnostics and status indicators are used for quick local error diagnostics.
I2
I9 I10
GSM/PWR/PLC I11 I12
I13 I14
GSM
I15 I16
AV TR
UL
US FR
UM FF I1
I10
I9
/GPR
S I12
GSM 977 I2 I11 4
151 2700 I1
ILC r-No.: x 1
I1
Orde : xx/xx .xx.xx
.xx.xx
E I4 I13 6
/FW .xx O1 I3 I1
HW dr.: xx QE2 I15
MAC
Ad
GSM
QD1 4 I5
I6 I1 I2
Q I8
TR Q3 I7
AV FA2IL
R1DY 4 I3
UL
FR 3A
BS
PF I4
US
FF
ET UM
MR
ES
OP
I5 I6
ST
T
SE
RE
N/P
RO
G
I7 I8
RU
A CT
K
LN
E
Q1 Q2
Q3 Q4 O1/IL
RDY FAIL
BSA PF
Figure 2-4 Diagnostics and status indicators
Local diagnostics and status indicators
Designation 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
On
another network device
Off Data transmission not active
ACT Yellow Data transmission active (activity): the Ethernet interface is sending or receiving
On
data
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.


GSM: diagnostics of the GSM connection
GSM status
Off GSM module not switched on
GSM Green Flashing GSM module registered in the GSM network
Flashing Searching for cellular network. GSM module not registered in the GSM network.
fast
AV Yellow On Device logged into the GSM network (available)
TR Yellow On GSM/GPRS data transmission active (traffic)
PWR: supply voltage
(see also Section Remote bus on page 33)
24 V supply UILC for generating voltages UL and UANA
Off Supply voltage is 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 is not present.
On Supply voltage is present.
24 V supply for main circuit
UM Green Off Supply voltage is not present.
On Supply voltage is present.
IL: INTERBUS diagnostics
INTERBUS master ready to operate/data transmission active
(INTERBUS ready/running)
RDY Green Off The INTERBUS master is not ready to operate.
Flashing The INTERBUS master is in the READY or ACTIVE state.
On The INTERBUS master is in the RUN state.
Failure
Off No error
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 Peripheral fault on a device in the connected bus (local bus or remote bus)

ILC 151 GSM/GPRS

I/O: digital inputs and outputs
Inputs 1 to 16
I1 to I16 Yellow Off Corresponding input is not set.
On Corresponding input is set.
Error
E Red Off No short circuit/overload at one of the outputs 1 to 4.
On Short circuit/overload at one of the outputs 1 to 4.
Outputs 1 to 4
O1 to O4 Yellow Off Corresponding output is not set.
On Corresponding output is set.
2.7 Reset button (concealed)
The reset button on the Inline controller (see 4 in Figure 2-3 on page 17) can only be oper-
ated with a pointed object (e.g., a pen) and is therefore protected against accidental activa-
tion.
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 around 1 minute.
2.8 Parameterization memory
The parameterization memory can be used to save programs and configurations which be-
long to your project. In addition, application-specific data can also be stored on the param-
eterization memory. See Section Parameterization memory and Internet Explorer on
page 52.
The Inline controller has an integrated parameterization memory.
In addition, it is possible to use a plug-in parameterization memory in the form of an SD card.
The SD card can be used as main memory or additional memory for the Inline controller, see
Section 3.6.
The SD card is optional and is not required in order to operate 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
2.8.1 Inserting/removing the parameterization memory
A B
4
TH 97
1 E 00
>Click<
15 27
ILC -No. /xxx xx
er xx x.
Ord W xx.x
/F r.: RX
HW Add NWO
C O
MA MATI
TO
AU
Order No.
SD FLASH 88 120 256MB
29
256MB
Figure 2-5 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 (Figure 2-5, 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 until the snap-
on mechanism releases the parameterization memory and partially ejects it from the
slot (Figure 2-5, B). Remove the parameterization memory.
For additional information on the parameterization memory, please refer to Section Func-
tions of the plug-in parameterization memory (SD card) on page 47 and Section Param-
eterization memory and Internet Explorer on page 52.

ILC 151 GSM/GPRS
2.9 Mode selector switch
The mode selector switch is used to define the operating state of the application program.
The RUN/PROG and STOP positions have a toggle button function and the MRESET posi-
tion a pushbutton function. After releasing the button in the MRESET position, it returns to
the STOP position.
Table 2-1 Inline controller operating modes
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.
For safety reasons, set the mode selector switch in the following se-
quence to delete the retain 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.
I10
I9
/GPR
S I12
GSM 977 I2 I11 4
151 2700 I1
ILC -No.: .xx 1
I1
er xx
Ord : xx/x x.xx.x
x.xx E I4 I13 6
/FW .x O1 I3 I1
HW dr.: xx QE2 I6 I15
AC
Ad
QD1 4
M
GSM Q I5
I8
TR Q3 I7
AV FA2IL
R1DY 4F
UL P
FR B3SA
US
FF
UM
ET
ES
MR OP
ST
T
SE
RE G
RO
N/P
RU T
AC
K
LN
Figure 2-6 Mode selector switch

2.10 Internal basic circuit diagram
Antenna
GSM/GPRS- P IB
SMA Modem
UL+
Q1...4 DI1...16
B UANA
UL
16 x DI C
7,5V 24V
4x
24V 24V US DO
UM
UL US
A
UM
ETH
PWR
Figure 2-7 Internal basic circuit diagram
Key:
Microprocessor Converter
Protocol chip LED
GSM/GPRS modem and

Optocoupler
antenna with SMA connection
Transmitter NPN transistor
SIM card holder/SD card holder (the SIM

RJ45 socket card and SD card are not supplied 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.

ILC 151 GSM/GPRS
2.11 Mounting and removing the Inline controller
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 instal-
lation manual or the Inline system manual for your bus system.
NOTE:
Before mounting or removing the controller, make sure that the supply voltage is switched
off and cannot be switched on again by unauthorized persons.
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 in several places, 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 In-
line 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 pro-
tects 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 sep-
arately.
NOTE:
When mounting or removing the Inline controller it must be tilted. This means that no Inline
terminal should be installed directly to the right of the Inline controller during mounting and
removal. The terminal must be removed prior to mounting or removing the Inline control-
ler. Otherwise, the snap-in hooks and jumper contacts will be damaged.
Mounting position Mount the Inline controller horizontally (as shown in Figure 2-8 on page 25). The specified
temperature range (see Ambient conditions on page 115) is only guaranteed if the Inline
controller is mounted in this position.

Mounting When mounting the Inline controller, proceed as shown in Figure 2-8:
Disconnect the power to the station.
Place the Inline controller onto the DIN rail from above (Figure 2-8, A) and push down
(Figure 2-8, B).
Then attach all the electronics bases required to set up the station. Observe the infor-
mation provided in the aforementioned user manuals.
Make sure that all featherkeys and keyways on adjacent terminals are securely inter-
locked.
A B
Figure 2-8 Snapping on the Inline controller (1)
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-9, A).
Then press the top of the connector towards the base until it snaps into the back snap-
on mechanism (Figure 2-9, B).
A
Figure 2-9 Snapping on the Inline controller (2)

ILC 151 GSM/GPRS
Removal When removing the Inline controller from the DIN rail, proceed as shown in Figure 2-11 on
page 27 and Figure 2-12 on page 27:
Disconnect the power to the station.
Unlike other Inline terminals, the Inline controller is removed by tilting it away from the DIN
rail. This requires the Inline terminal to the right to be removed prior to removing the Inline
controller. The right connector of the Inline controller must also be removed.
Remove the third and fourth connectors to access the right base latch.
It is therefore recommended that all connectors be removed prior to removing the Inline
controller.
If the connectors cause trouble during removal:

Remove all the connectors of the Inline controller.
Lever up each connector by pressing on the back connector shaft latching
(Figure 2-11, A).
Remove the connectors (Figure 2-11, B).
If Inline terminals are installed next to the Inline controller (see Figure 2-10):
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 in the aforementioned user manuals.
A1...A4 B1
ILC 151 GSM/GPRS

Order-No.: 2700977
HW/FW: xx/xxx GSM E
MAC Addr.: xx.xx.xx.xx.xx.xx AV TR Q1 Q2 I1 I2 I9 I10
UL Q3 Q4 I3 I4 I11 I12
UM FF BSA PF I7 I8 I15 I16
RESET MRESET
STOP
RUN / PROG
LNK ACT
ILC 151 GSM/GPRS A B 8510A003
Figure 2-10 Connectors to be removed if terminals are installed next to the Inline con-
troller

Figure 2-11 Removing the Inline controller (1)
Insert a tool in the base latches of the Inline controller and pull gently upwards
(Figure 2-12, A). Pull out the Inline controller from the DIN rail (Figure 2-12, B and C).
B
A
Figure 2-12 Removing the Inline controller (2)
Replacing the Inline con- If you want to replace an Inline controller within an Inline station, proceed as described
troller 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 se-
curely interlocked.
Observe the following when replacing an Inline controller:

Enter the MAC address of the new Inline controller in the PC Worx software when using the
BootP server.

ILC 151 GSM/GPRS
2.12 Communication path
For communication with the Inline controller, the following communication path is available:
Ethernet 10/100Base-T(X), see Figure 2-14
A standardized Ethernet interface is available for connecting the Ethernet network. The
Ethernet network is connected via an RJ45 socket.
Use an Ethernet cable according to 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-13 Ethernet interface
I10
S I9
M/G 7
PR I12
GS 97
151 : 2700 I2 I11 4
ILC r-No. x .xx 1
I1 I1
Orde W: xx/xx.xx.xx
.xx.xx
E I4 I13 6
/F .: xx O1 I3 I1
HW Addr QE2 I6 I15
MAC QD1 4 I5
GSM Q I8
TR Q3 I7
AV FA2IL
1Y
RD
UL 4
PF
FR 3A
BS
US
FF
UM
T
SE
MRE OP
ST
T
SE
RE G
RO
N/P
RU T
AC
K
LN
Figure 2-14 Connecting the Ethernet cable to the Inline controller
The interface is able to switch over the transmitter and receiver automatically (auto cross-
over).

2.13 SIM card
NOTE:
Disconnect power to the Inline controller before inserting/removing the SIM card.
The controller only supports 3 V SIM cards. In the event of older SIM cards, please contact
your provider.
You will receive a SIM card from the provider on which all important data for your connec-
tion is stored.
If the SIM card has been supplied in credit card format, simply detach the small sec-
tion of the card and remove any protruding parts of plastic.
I10
S I9
PR
M/G 7 I12
GS 97 I11 4
151 : 2700 x I2
ILC -No. xx xx.x 1
I1 I1
er
Ord W: xx/x .xx.xx
.xx. I4 I13 6
/F xx O1 E 2 I3 I1
HW Addr.: QE I6 I15
MA
C QD1 I5
GSM Q4 I8
TR Q3 I7
AV FA2IL
R1DY 4
UL PF
FR 3A
BS
US
FF
ET UM
ES
MR OP
ST
T
SE
RE G
RO
N/P
RU T
AC
K
LN
Figure 2-15 Inserting the SIM card
NOTE: Damage to the SIM card/card holder

When inserting/removing the SIM card, do not force the SIM card into the card holder, as
this could damage the SIM card and/or card holder.
Inserting the SIM card Place a SIM card in the card holder as shown in Figure 2-15. The SIM card must be po-
sitioned with the diagonal edge at the top towards the controller.
Applying light pressure, use a screwdriver to push the SIM card into the card holder as
far as possible (A: push-push technology).
Removing the SIM card Using a screwdriver, push the SIM card into the card holder as far as possible. When
you remove the screwdriver, the SIM card will protrude slightly from the card holder (A:
push-push technology).
Remove the SIM card.
PIN code The SIM card can be protected by a PIN code with up to 8 digits.

ILC 151 GSM/GPRS
To specify the PIN code, either use a parameter of the MOBILE_CONNECT function
block (see Section 3.13.1, MOBILE_CONNECT function block) or enter it in the Device
Details in PC Worx under Extended Settings/GSM Settings (see Section 4.2, GSM
settings in PC Worx).
For additional information on the function blocks, please refer to the online help for
PC Worx.
PIN code error

If the PIN code has been entered incorrectly three times, the PUK code must be entered.
To enter the PUK code, proceed as follows:

Remove the SIM card from the ILC 151 GSM/GPRS (see Section SIM card on
page 29).
Insert the SIM card in a mobile phone.
Enter the PUK code using the mobile phone.
Card contracts The following card contracts are usually available:

Prepaid card for outgoing data links, SMS text messages, and voice.
Voice card for outgoing data links, SMS text messages, and voice.
Data card for incoming and outgoing data links and SMS text messages.
Most providers offer combined data and voice contracts, whereby various phone numbers
for data and voice are assigned to a SIM card. Prepaid cards for incoming data links are usu-
ally not available.
GPRS options are usually available for all cards.
2.14 Antenna
WARNING: Transmitting antenna/electromagnetic radiation risk of personal in-

jury
The antenna for this transmitter must be installed at least 20 cm away from people.
NOTE: Risk of damage to equipment

The antenna for this transmitter must not be installed or operated near/in conjunction with
other antennas or transmitters.

In most cases, the ILC 151 GSM/GPRS Inline controller is operated as a fixed installation
within a wireless network for mobile devices. It is therefore important to supply the device
with a stable and undisturbed antenna signal.
To ensure a stable and undisturbed antenna signal, observe the following notes:
Do not install the antenna inside buildings.
Reflections are more likely to occur within buildings, leading to destructive interfer-
ence. This may temporarily weaken the signal strength meaning that communication
will no longer be possible.
The antenna should be at least 2.5 m away from power lines. Otherwise the voltage
induced in the antenna cable may cause the input amplifiers of the GSM receiver to
be overdriven resulting in communication no longer being possible.
The necessary safety distance from high-voltage cables must be observed.
Install the antenna cable according to the relevant antenna installation instructions. In
particular, observe the maximum cable length (influenced by cable attenuation) and
the bending radius of the cable.
GSM antenna installation using the PSI-GSM/UMTS-QB-ANT antenna (Order No.

2313371) as an example
Select an antenna position providing good wireless network conditions (e.g., a control
cabinet outside buildings).
Drill a hole with a diameter of 16.5 mm in the surface on which the antenna is to be
mounted (e.g., the top of the control cabinet).
Feed the antenna cable through the hole.
Please observe the following during installation:

The antenna has a diameter of 76 mm and is 23 mm high.
The cable supplied has a length of 2 m.
Secure the antenna using the washer and nut provided.
7735A015
Figure 2-16 Installation of the PSI-GSM/UMTS-QB-ANT antenna

ILC 151 GSM/GPRS
Connect the antenna cable with an SMA connector to the antenna connection of the In-
line controller. Tighten the nut at the antenna connection by hand only.
I10
S I9
M/G 7
PR I12
GS 97 I11 4
151 : 2700 .xx
I2 I1
ILC r-No. x 1
I1
Orde W: xx/xx.xx.xx
.xx.xx E I4 I13 6
O1 I3 I1
HW
/F .: xx
QE2 I15
Addr QD1 4
I6
MAC GSM Q I5
I8
TR Q3 I7
AV FA2IL
1Y
RD
UL 4
PF
FR 3A
BS
US
FF
SE
T UM
MRE OP
ST
T
SE
RE G
RO
N/P
RU T
AC
K
LN
Figure 2-17 Antenna connection with SMA connector
Signal strength and bit error rate

Both a sufficient signal strength and a low bit error rate are required to ensure proper oper-
ation (see Section Bit error rate (BER) on page 109).
Troubleshooting if the signal strength is too low

Install the antenna in a different location with sufficient field strength.
Install an antenna with higher antenna gain.
Improve the alignment of the antenna, if required.
Troubleshooting if the bit error rate is too high

A high bit error rate is usually associated with disturbances in the useful signal at the GSM
receiver side.
This may be caused by:
Power lines installed too close to the antenna or antenna cable
Network cables installed too close to the antenna or antenna cable
Break sparks from devices without radio interference suppression
Strong transmitters in the vicinity of the antenna
Avoid these sources of interference to ensure proper operation of the ILC 151 GSM/GPRS.
Re-install the antenna, if required.

2.15 INTERBUS
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
FO 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.15.1 Local bus
The local bus is automatically created by directly connecting I/O modules to the Inline con-
troller.
2.15.2 Remote bus
Connect the remote bus to the Inline controller using the IBS IL 24 RB-T-PAC branch termi-
nal (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 in-
stalled 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 ter-
minal 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).

ILC 151 GSM/GPRS
2.16 Power supply
2.16.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 op-
eration of the Inline controller (see Figure 2-19).
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-18). 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 current catalog from Phoenix Contact at phoenixcon-
tact.net/products) 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-18 Overload range with fall-back characteristic Figure 2-19 Overload range without fall-back charac-
curve teristic curve

2.16.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 34).
1. Connect the power supplies to the connector for power supply as shown in Figure 2-20.
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 may be a serious fault on the Inline control-
ler.
In this case, please contact Phoenix Contact.
GSM
1 2 AV TR
UL
1.1 2.1 US FR
UM FF
I15 I16
I10
1.2 /GP
GSM 977
151 2700
ILC -No.:
er xx
RS
x.xx
.xx
2.2 1
I1
I2
I9
I12
I11 4
I1
I13 6
Ord : xx/x x.xx.x O1 E I4 I1
/FW .x I3
HW ddr.: xx QE2 I15
MA
C
1.3
A
2.3 GSM
AV
TR
QD1 4
Q3
Q
F2AIL
R1DY 4F
I5
I7
I6
I8
UL P
FR B3SA
US
1.4 MR
ES
ET
ST
OP
2.4 UM
FF
US +
-
T
SE
RE G
/P RO
R UN
T
AC
LN
K
+ +
UILC -
- UM
Figure 2-20 Supply voltage connection

ILC 151 GSM/GPRS
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-
NOTE:
ply
Protect the supply voltage externally according to the connected
load (local bus devices) with 8 A, maximum. Make sure the exter-
nal 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:
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
NOTE:
(main power)
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 potential
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 interfer-
ence.
NOTE:
The maximum total current flowing through the potential jumpers is 8 A.

2.16.3 24 V segment supply/24 V main supply
The segment supply and main supply must have the same reference potential. An electri-
cally isolated voltage area is not possible.
2.16.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-20 on page 35).
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 transient surge volt-
age.
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 cur-
rent at UM and US).
2.16.5 24 V main voltage
NOTE:
The 24 V main supply has protection against polarity reversal and transient 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 cur-
rent at UM and US).
2.16.6 24 V ILC supply
NOTE:
The 24 V ILC supply has protection against polarity reversal and transient 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.16.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.

ILC 151 GSM/GPRS
2.17 Digital inputs and outputs
There are sixteen 24 V DC inputs and four 24 V DC outputs.
4
1 2
2-3 3.1 4.1

1 2
3.2 4.2
1.1 2.1 3.3 I9
I10
4.3
/GPR
S I12
GSM 977 I2 I11 4
151 2700 I1
ILC -No.: 1
3.4
I1
4.4
.xx
x.xx I13 6
1.2 2.2
er xx I4
Ord : xx/x x.xx.x
/FW .x O1 E 2 I3 I1
HW dr.: xx QE I6 I15
MAC
Ad
QD1
GSM Q4 I5
I8
TR Q3 I7
AV FA2IL
R1DY 4F
1.3 2.3 UL P
FR B3SA
US
FF
UM
ET
ES
MR OP
ST
1.4
T
2.4
SE
RE G
RO
N/P
RU T
AC
K
LN
Figure 2-21 Terminal point assignment of connectors 2 to 4
Table 2-2 Terminal point assignment
Terminal point Assignment Remark

Connector 2 Output terminal points
1.1 O1 Output 1
2.1 O2 Output 2
1.2, 2.2 GND Ground contact for 2 and 3-conductor connection
1.3, 2.3 FE Functional earth ground for 3-conductor connection
1.4 O3 Output 3
2.4 O4 Output 4
The outputs are supplied with 24 V DC from the segment supply (US).
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

Table 2-2 Terminal point assignment

Terminal point Assignment Remark
Connector 4 Input terminal points
3.1 I9 Input 9
4.1 I10 Input 10
3.2 I11 Input 11
4.2 I12 Input 12
3.3 I13 Input 13
4.3 I14 Input 14
3.4 I15 Input 15
4.4 I16 Input 16
The inputs are supplied with 24 V DC from the main supply (UM).
The outputs have protection against ground connection interrupt and must be wired ac-
cordingly.
ILC 151 GSM/GPRS L ILC 151 GSM/GPRS L
8510A004
Figure 2-22 Basic wiring of an output with a load (L)
To connect actuators in 3-wire technology, Phoenix Contact recommends using connec-

tors for digital 4-channel or 16-channel Inline terminals (not supplied as standard, see

ILC 151 GSM/GPRS

The Inline controller under PC Worx general
3 The Inline controller under PC Worx general
3.1 Software version
In order to work with the Inline controller, the following version of PC Worx is required:
PC Worx Version 6.20 or later
PC Worx Express Version 6.20 or later
Recommended:
To utilize the full range of functions of the ILC 151 GSM/GPRS, we recommend that you
use the PC Worx software with the specified version or later.
For information on installing and using PC Worx, please refer to the corresponding quick
start guide. It can be downloaded at phoenixcontact.net/products and is supplied with the
software.

ILC 151 GSM/GPRS
3.2 Assigning the IP address for the controller
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 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 proto-
col.
3.2.1 Dynamic Configuration Protocol (DCP)
The ILC 151 GSM/GPRS as of firmware Version 4.20 and as of PC Worx Version
6.30.767 (part of the AUTOMATIONWORX Software Suite 1.81 including AddOn V1)
supports the DCP protocol.
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-1 DCP: setting the IP address
The IP Assignment tab is used for IP address assignment with DCP.

Select the IP Assignment tab.
After selecting the IP Assignment tab, the PROFINET network is searched for DCP de-
vices.
Click on Assign IP to start IP address assignment with DCP.

Figure 3-2 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.2.2 BootP server
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 151 GSM/GPRS in the default settings), the Inline con-
troller (BootP client) sends a Boot_Request as a broadcast in the network. The MAC ad-
dress of the transmitter is sent with the Boot_Request to provide unique identification. If the
BootP server has been activated in PC Worx, PC Worx responds with a Boot_Reply.
PC Worx uses this Boot_Reply to inform the Inline controller of its IP address and subnet
mask. You must make sure 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 for the
MAC address.
Once the IP data has been transferred to the Inline controller successfully, PC Worx sends
a corresponding acknowledgment message.
PC/network adapter To determine whether your network permits the IP settings used in the example project (see
Figure 3-3 on page 44), proceed as follows:
In the Windows Control Panel, check the settings for your PC network adapter.
If necessary, adjust these settings so that the Inline controller can be accessed in your
network via the IP address used in the example project.

ILC 151 GSM/GPRS
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 4-2 on page 89).
Changes to project information are not applied automatically

If any changes are made to the project information (see Figure 4-2) that affect the IP set-
tings for the controller, a warning is displayed. However, the change is not implemented
automatically. When a new project is created, the default settings are specified under IP
Settings (see Figure 3-3 on page 44).
Assigning IP settings To set the IP address in PC Worx, proceed as described below:
BootP is activated by default for communication with the Inline controller via Ethernet. Ini-
tial setting of the IP address can be carried out with the PC Worx software manually by
means of a BootP server. The IP address can be changed later via Ethernet using the
PC Worx software.
Establish an Ethernet connection between your PC and the controller.

Switch to the bus configuration workspace.
Select the controller node (ILC 151 GSM/GPRS in the example).
Select the IP Settings tab in the Device Details window.
Enter the MAC address of the controller (see Figure 3-3). It is printed on the device
(00.A0.45.xx.xx.xx).
I10
I9
GPRS I12
GSM/ 977 I2 I11 4
151 2700 I1
ILC r-No.: .xx.xx 1
I1 I13 6
Orde : xx/xxx .45.xx O1 E I4 I1
.A0 I3
QE2
/FW
HW dr.: 00 I6 I15
C Ad QD1 4
MA
GSM Q I5
I8
TR Q3 I7
AV FA2IL
1Y
RD
UL 4
PF
FR 3A
BS
US
FF
T
UM
SE
MRE OP
ST
ET
RES
OG
N/PR
RU T
AC
K
LN
Figure 3-3 Entering the MAC address
In the menu bar, select the

Extras, BootP/SNMP/TFTP Configuration ... menu.
Click on the Activate BootP button.

Figure 3-4 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-5 Message window following BootP
The IP address is now permanently stored in the internal parameterization memory of the
Inline controller.
For additional information on setting the IP address with PC Worx, please refer to the
quick start guides for the PC Worx version used.

ILC 151 GSM/GPRS
3.3 Setting the realtime clock under PC Worx
The time and date for the internal system clock of the Inline controller can be set under Ex-
tended Settings in the Device Details window for the controller in PC Worx.
To set the realtime clock, proceed as described in the quick start guide for the PC Worx
version used.
3.4 Download changes
The ILC 151 GSM/GPRS supports the Download Changes function.

3.5 Functions of the plug-in parameterization memory

(SD card)
This function is available for Inline controllers with firmware versions 4.40 as of AUTO-
MATIONWORX Software Suite Version 1.82 AddOn V1.
The plug-in parameterization memory can be used as main memory or additional memory.
Figure 3-6 shows how you should proceed in order to use the SD card as main memory 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-6 Procedure for using the SD card as main memory or additional memory
Information on using the SD card as main memory or additional memory is provided in the
sections below.
3.5.1 Main memory
If the SD card is used as main memory, all application-specific data is stored on the SD card.
The SD card is recognized during initialization of the Inline controller.
If the SD card is to be used as main memory by the controller, make sure that the SD
card has been inserted before switching on the controller.
Removing the SD card The SD card must not be removed during operation of the Inline controller.
during operation
NOTE: Potential data loss
If the SD card is removed during operation, data may be lost.
Do not remove the SD card during operation.
Should the SD card be accidentally removed during operation, the Inline controller indicates
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 operating modes (operating the Inline controller with/without SD card), please
modes note the following:

ILC 151 GSM/GPRS
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 memo-
ry.
Switch on the supply voltage of the Inline controller.
NOTE: Deletion of all data on 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.2.
Settings in PC Worx Figure 3-7 shows the settings in PC Worx for using the SD card as main memory.
Figure 3-7 Setting to use the SD card as main memory
In the Device Details window, select the Use of external SD card setting under Ex-
tended Settings.
In the Settings area, select the Preferably, use the external SD card as main memory
setting from the drop-down list.
Click on the Send button (hidden by the drop-down list in Figure 3-7) to send the set-
ting 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-6 on page 47), the SD card is used as 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-6 on
page 47), the SD card is used as additional memory (see Section 3.5.2). All applica-
tion-specific data is stored on the internal parameterization memory of the Inline con-
troller.
3.5.2 Additional memory
This function is available for Inline controllers with firmware versions 4.40 as of
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 additional memory, all application-specific data is stored on the in-
ternal parameterization memory of the Inline controller. If you use an SD card with license
key, the license is used nonetheless.
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 longer than 60 minutes, under certain circumstanc-
es it may no longer be possible to execute function blocks that require a license for exe-
cution.
If the SD card is removed and re-inserted in the Inline controller within 60 minutes, all func-
tion blocks will still 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-6 on page 47), if:
The SD card is inserted after starting up the Inline controller.
or
You have selected the Use the external SD card as additional memory setting in
PC Worx (default setting).
Inserting/removing the SD The SD card may be inserted or removed before starting up the Inline controller or during
card operation.
NOTE: Potential data loss

If the SD card is removed during active read and/or write access to the SD card, data may
be lost.
Only remove the SD card when the SD card is not being accessed.

ILC 151 GSM/GPRS
Settings in PC Worx Figure 3-8 shows the settings in PC Worx for using the SD card as additional memory.
Figure 3-8 Setting to use the SD card as additional memory
In the Device Details window, select the Use of external SD card setting under Ex-
tended Settings.
In the Settings area, select the Use external SD card as additional memory setting
from the drop-down list.
The Inline controller must be restarted in order to activate the setting.
3.5.2.1 SD card as memory for log files

You can use the SD card as memory for log files.
The contents of the cfroot directory are 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 Sec-
tion Parameterization memory and Internet Explorer on page 52).
Figure 3-9 sddisk directory on the SD card
It is useful to create a new directory in the sddisk directory where log files should be stored:
Access the Inline controller via FTP.
Double-click on the sddisk directory to open it.
In the sddisk directory, right-click to open the context menu and select New, Folder.
Enter a name for the directory to be created (Logfile in the example in Figure 3-10).

Figure 3-10 New Logfile directory in the sddisk directory
To access the directories on the SD card, use the FILE function blocks in PC Worx (see
Section 3.11 and online help for PC Worx).
If you program your application program accordingly, the log files are stored in the Log-
file.txt file and in the Logfile directory. You can then access the file using the FILE_OPEN
function block.
Figure 3-11 shows a FILE_OPEN function block for opening the Logfile.txt file in the \sd-
disk\Logfile directory.
Figure 3-11 Opening the Logfile.txt file using the FILE_OPEN function block
Always specify the complete path and file name in the Variable Properties dialog (right
in Figure 3-11).

ILC 151 GSM/GPRS
3.6 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 Explor-
er FTP functionality on page 53.
Switch to the bus configuration workspace in PC Worx.

Select the ILC 151 GSM/GPRS controller 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 De-
vice button.
Figure 3-12 Extended Settings: Open FTP Folder on Device
The file structure, which is stored on the parameterization memory, is displayed in the Inter-
net 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.

3.6.1 Internet Explorer FTP functionality
Activate this setting in Internet Explorer under Tools, Internet Options, Advanced.
Figure 3-13 Internet Options: Enable FTP folder view

ILC 151 GSM/GPRS
3.6.2 Activating/deactivating the FTP server
To protect the Inline controller against unauthorized access, it may be necessary to deacti-
vate 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 de-
activated as soon as the corresponding service has been executed.
When you activate the FTP server, the setting is not actually activated until the controller has
been restarted. The set FTP server state is stored retentively and mapped to the
ETH_SRV_FTP_ACTIVE system variable.
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-14 Deactivating the FTP server

3.6.3 Restricting FTP access
In order to prevent unauthorized FTP access to the parameterization memory, you can
specify a user name (maximum of twelve characters) and a password (maximum of twelve
characters) for access. By default, the user name for the Inline controller is anonymous
and no password is set (). This setting is also restored when the Inline controller is reset to
the delivery state.
The CPU_Set_Value_Request service with Var ID 019Ahex is used to specify the user name
and password.
Specifying a user name To specify a user name and password, proceed as follows:
and password Switch to the bus configuration workspace in PC Worx.
Select the ILC 151 GSM/GPRS controller in the Bus Structure window.
Select the CPU Service Editor tab in the Device Details window.
Open the ILC1xx_Service_Common.slb library.
Double-click to select the CPU_Set_Value_Request service.
Figure 3-15 Opening the library and selecting the service
In the CPU Request area for (* Var Count *), enter the value 1.
In the CPU Request area for (* Var ID ... *), enter the value 019A.
In the CPU Request area for (* Value ... *) (changed to (* length username & username
*) and (* length password & password *) in Figure 3-15), enter the desired user name
and password.
The length of the user name must be entered first followed by the individual characters of
the user name in hexadecimal ASCII format. The length of the password must then be en-
tered followed by the individual characters of the password in hexadecimal ASCII format.

ILC 151 GSM/GPRS
Example (see Figure 3-34): 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, the ASCII characters 0455 5345 52 must be entered for the user name
USER (length of the user name followed by the individual characters of the user name) and
then the ASCII characters 04 5041 5353 must be entered for the password PASS (length
of the password followed by the individual characters of the password).
Figure 3-16 shows the settings for specifying the user name USER and the password
PASS in the CPU Request area.
Figure 3-16 Specifying the 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 the new password are set.
Successful execution of the service is acknowledged in the CPU Confirmation area as fol-
lows:
<Cnf: CPU_Set_Value_Request>
82CB (*W1 : Confirmation_Code*)
0001 (*W2 : Parameter_Count*)
0000 (*W3 : Result*)
Perform a voltage reset of the Inline controller.

A dialog now appears for FTP access to the parameterization memory where you need to
enter the user name and password.
The contents of the parameterization memory are only displayed if the correct user name
and password have been entered.
Recommended:
If you want to access the parameterization memory using a web browser, disable the web
browser's cache.
Otherwise under certain circumstances, it is possible that the contents of the parameter-
ization memory will be displayed, despite access protection being activated, if data from
previous access without access protection is still located in the web browser's cache.
Removing the user name To remove the user name and password, proceed as described above but enter the value
and password 0000 in the CPU Request area for (* Value ... *), see Figure 3-17.
Figure 3-17 Removing the user name and password for FTP access

ILC 151 GSM/GPRS
3.6.4 Activating/deactivating the HTTP server
This function is supported as of AUTOMATIONWORX Software Suite 2009 1.50.
Deactivate To protect the Inline controller against unauthorized access, it may be necessary to deacti-
vate the HTTP server. To do this, proceed as follows:
Select the Inline controller in the Bus Structure window.
Select the Web server setting under Extended Settings.
Select the Disabled setting from the drop-down list.
Figure 3-18 Deactivating the HTTP server
If you have selected the Disabled setting, the HTTP server (web server) is deactivated.
HTTPS (see Section 3.6.5) is also deactivated.
Activate To activate the HTTP server, proceed as follows:

Select the HTTP (Port 80) setting from the drop-down list.

3.6.5 Using the Hypertext Transfer Protocol Secure (HTTPS)
The ILC 151 GSM/GPRS supports the Hypertext Transfer Protocol Secure (HTTPS) as of
firmware Version 4.20 and as of PC Worx Version 6.30.767 (part of the
AUTOMATIONWORX Software Suite 1.81 including AddOn V1).
The Hypertext Transfer Protocol Secure (HTTPS) can be used for HTTP server communi-
cation.
The settings to use HTTPS are made via the Device Details window.
Select the Inline controller in the Bus Structure window.
Select the Web server setting under Extended Settings.
Select the HTTPS (Port 443) setting from the drop-down list.
Figure 3-19 Setting HTTPS
3.7 Sending e-mails securely
You can use the SMTPS method (e-mail via SMTP with SSL/TLS) to send e-mails securely.
In order to use the SMTPS method, you must import the IT library ( version 1_34) function
block library. It can be downloaded via the product at phoenixcontact.net/products.
For additional information on the function block library, please refer to the online help for
PC Worx.
Security certificates from the mail server are always accepted by the Inline controller and
not checked.

ILC 151 GSM/GPRS
3.8 Activating/deactivating specific ports
Depending on your application, it may be necessary to deactivate certain ports. The

CPU_Set_Value_Request service with various Var ID for the individual ports is used for this.
A port can be activated or deactivated with this service. The port is deactivated as soon as
the corresponding service has been executed.
When you activate a port, the setting is not actually activated until the controller has been
restarted.
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
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
NOTE: The Inline controller cannot be accessed

If you deactivate port 1962 and/or port 41100, you can no longer access the Inline con-
troller from PC Worx.
Only deactivate port 1962 and/or port 41100 if you no longer need to access the Inline
controller from PC Worx.
If you have deactivated port 1962 and/or port 41100, these ports can only be re-activated
by resetting the Inline controller to the default settings.

3.9 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.
Code 02CBhex
Var Count 0001hex
Var ID 0194hex
Value 0001hex Activate journaling function
0000hex Deactivate journaling function
Figure 3-20 Activating the journaling function

ILC 151 GSM/GPRS
3.10 Activating/deactivating the GPRS watchdog
To ensure GPRS availability over a longer period of time, the GPRS watchdog of the
ILC 151 GSM/GPRS can be activated.
The GPRS watchdog is activated by default.
The GPRS watchdog is based on four levels (see Table 3-1).
If the GPRS watchdog is activated, all four levels will always be active.
Table 3-1 GPRS watchdog levels

Level Description
1 GPRS connection establishment is monitored. If a GPRS connec-
tion cannot be established, the GSM modem will be automatically
reset.
2 The number of bytes exchanged via GPRS is monitored. If there
are no bytes transmitted or received over a certain period of time,
the GPRS connection will be automatically terminated and then
established again.
When defining a period of time for the Level 1 watch-

dog, please note that each automatic termination and
subsequent re-establishment of the GPRS connection
may result in costs. These costs vary depending on the
provider.
3 The number of bytes exchanged via GPRS is monitored. If there

are no bytes transmitted or received over a certain period of time,
the GPRS modem will be automatically reset.
24 h reset After 24 hours an active GPRS connection will be automatically
terminated and then established again.

The GPRS watchdog can be activated or deactivated via the CPU_Set_Value_Request ser-
vice with Var ID 0190hex.
Code 02CBhex
Var Count 0001hex
Var ID 0190hex GSM settings
GSM index 0007hex GPRS watchdog
Value 0001hex Activate GPRS watchdog
0000hex Deactivate GPRS watchdog
000Ahex Period of time for the Level 2 watchdog
in min
(default value: 10 min)
001Ehex Period of time for the Level 3 watchdog
in min
(default value: 30 min)
Only values > 0000hex are valid for Level 2 and 3 watchdogs.
The value for the Level 2 watchdog must be lower than the value for the Level 3 watchdog.

ILC 151 GSM/GPRS
3.11 Function blocks for handling files on the parame-

terization 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 opera-
tions. 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-2 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.


TCP/IP and UDP/IP communication
The function blocks are used to establish Ethernet communication between two communi-
cation partners.
The IP communication blocks listed below enable IEC 61131-5-compliant communication
between controllers via Ethernet or communication between controllers and Ethernet de-
vices 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 connec-
tions.

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.
Data transmission using GPRS port address of the communication partner

When using the TCP/IP or UDP/IP function blocks, please note that the port addresses
that can be set depend on the port filter, which can be activated in PC Worx in the GPRS
settings (see Figure 3-27 on page 81).

ILC 151 GSM/GPRS

GSM/GPRS mobile communication functions
The ILC 151 GSM/GPRS supports:

Sending and receiving SMS text messages via the GSM modem
GPRS data transmission via the GSM modem
The PC Worx software provides function blocks to enable the ILC 151 GSM/GPRS to com-
municate by SMS via the GSM network and to transmit data using GPRS. These function
blocks are described in the following sections.
GSM functionality The function blocks are used to send and receive SMS text messages via a mobile commu-
nication network.

MOBILE_CONNECT This function block is used to parameterize and diagnose the
GSM modem of the controller.
In addition, the block provides information on the current pro-
vider and the received field strength of the GSM modem.
SMS_SEND This block can be used to send an SMS text message via the
SMS_RECEIVE This block can be used to receive an SMS text message via the
The SMS_SEND and SMS_RECEIVE function blocks can be instantiated multiple

times, for example, to exchange specific SMS text messages with multiple devices of an
application.
The function blocks for GSM/GPRS mobile communication functions are described in the
PC Worx online help.
GPRS functionality The GPRS (General Packet Radio Service) mobile communication service can be used to
transmit data in GSM mobile communication networks. Data is transmitted using IP function
blocks (see Section Function blocks for TCP/IP and UDP/IP communication on page 65).

GPRS_CONNECT GPRS is activated/deactivated using the GPRS_CONNECT
function block.
The function block is described in the PC Worx online help.

3.13.1 MOBILE_CONNECT function block
General The MOBILE_CONNECT function block is used to parameterize and diagnose the mobile
communication modem integrated in the ILC 151 GSM/GPRS.
The mobile communication modem is always switched on as soon as it has been parame-
terized or the ILC 151 GSM/GPRS has been supplied with voltage.
The function block provides the following diagnostic information:
Registration status
Signal strength of the mobile communication connection
Current provider
The function block can be used to parameterize the following:
PIN
Roaming registration
Service Center number (phone number of the SMS Center)
Please note:
The MOBILE_CONNECT function block is used to parameterize the device for sending
and receiving SMS text messages. As of PC Worx 6.0, these settings can also be made
under Extended Settings, GSM Settings in the Device Details window. When you
make the settings in PC Worx, it is not absolutely necessary to use the
MOBILE_CONNECT function block. In this case, however, the diagnostic function of the
function block will not be available.
If you have made GSM settings in the extended settings, they will be overwritten as soon
as the MOBILE_CONNECT function block is called with the corresponding parameteriza-
tion. The current settings depend on whether the MOBILE_CONNECT function block was
called last or GSM settings were transmitted by PC Worx.
Function block
Figure 3-21 MOBILE_CONNECT function block
Function description If the ENABLE input is set to TRUE, an attempt is made to parameterize the mobile commu-
nication modem. The modem is configured with the parameters specified at the PARAME-
TER input.
Once the mobile communication modem has been registered successfully in the mobile
communication network, the VALID output is set to TRUE. If an error occurred during pa-
rameterization, the ERROR output is TRUE. The STATUS output shows the details of the
error as an error code. The PROVIDER output shows the name of the current provider as a

ILC 151 GSM/GPRS
STRING. The SIGNAL_STRENGTH output indicates the RSSI (Received Signal Strength
Indicator) value. Refer to the description of the SIGNAL_STRENGTH output for increments
of the RSSI value.
Input parameters
Table 3-6 Inputs of the MOBILE_CONNECT function block
Name Data type Description

The mobile communication modem can be parameterized with a positive edge at
this input. The function block establishes a connection to the mobile communica-
tion modem and, in turn, to the provider. The inputs of the block are read and the
mobile communication modem is parameterized with the values specified at the
MODE and PARAMETER inputs.
An additional positive edge change (FALSE TRUE) at ENABLE is required for
error acknowledgment (ERROR output = TRUE). If there is already a TRUE signal
at ENABLE, a TRUE FALSE TRUE edge change is required.
To reset the mobile communication modem (MODE = 255dec), an additional posi-
ENABLE BOOL tive edge change (FALSE TRUE) is required at ENABLE. Once the modem has
been reset successfully, the VALID output shows successful registration in the mo-
bile communication network.
The modem is always reparameterized if a positive edge is detected at

ENABLE.
The output states of the function block will only be updated cyclically if
ENABLE is TRUE. If ENABLE is set to FALSE and there is no error
present, the outputs will no longer be updated cyclically.
0...254: Reserved
255dec: Reset of mobile communication modem (see also description of EN-
MODE INT
ABLE input)
255: Reserved
This string is used to specify the following parameters for the mobile communica-
tion modem:
PIN (number up to eight digits)
Roaming registration allowed: Yes (TRUE) / No (FALSE)
Service Center number of the provider (phone number of the SMS Center) in
international format (e.g., +495235300)
Syntax: PIN;roaming registration,Service Center number;
PARAMETER STRING Example: 1111;true;+495235300;
If one of the parameters should not be transmitted, it can be left out.

However, you still have to insert the semicolon after the parameter.
Example: 1111;;+495235300;
If none of the parameters are to be transmitted, the string is as follows:
;;;. To allow roaming, it looks like this: ;true;;.

Output parameters
Table 3-7 Outputs of the MOBILE_CONNECT function block

TRUE: The mobile communication modem is registered in the mobile commu-
VALID BOOL nication network and has been parameterized successfully.
FALSE: The mobile communication modem has not been registered.
TRUE: An error has occurred. Details are provided by the STATUS output.
FALSE: No error. STATUS contains the current value of the internal processing.
ERROR BOOL The ERROR state is independent of the ENABLE input state.
ERROR indicates an error until it is acknowledged with a positive edge

at ENABLE.
STATUS WORD Error value of the function block (see Table 3-9 on page 69).
RSSI value:
0 -113 dBm or less
1 -111 dBm
2...30 -109 dBm ... -53 dBm (2 dBm per increment)
31 -51 dBm or more
SIGNAL_STRENGTH INT 99 Not known or not measurable
An RSSI value of at least 3 (-107 dBm) is required in order to send/re-

ceive SMS text messages.
Data connections (GSM/GPRS) require an RSSI value of at least 17 (-
79 dBm).
Input/output parameters
Table 3-8 Input/output of the MOBILE_CONNECT function block

PROVIDER STRING Name of the current provider
STATUS output (ERROR =

TRUE)
Table 3-9 Error values of the STATUS output (ERROR = TRUE)
Value Meaning
0x0A No SIM card inserted
0x0B SIM card faulty
0x0C SIM card is currently being written/read. Try accessing it again.
0x0D Wrong type of SIM card
Firmware of the mobile communication modem is not compatible with the
firmware of the ILC 151 GSM/GPRS.
Remedy:
0x0F
Update the modem firmware
Downgrade the ILC 151 GSM/GPRS firmware to a version that is com-
patible with the modem firmware

ILC 151 GSM/GPRS
Value Meaning
SIM card with activated PIN request inserted, however a PIN has not been
transferred to the controller yet.
0x10 Remedy:
Parameterization using PC Worx or the MOBILE_CONNECT function
block.
0x14 Modem could not be started up properly
0x15 Wrong PIN
PIN has been entered incorrectly three times. The PUK code must be entered
0x16 now. The PUK code cannot be entered via the ILC 151 GSM/GPRS. Use a
mobile phone, for example, to enter the PUK code.
Re-registration failed. Signal strength too weak at the current location or SIM
0x17
card is not activated.
0x18 Abort for unknown reasons
0x19 Roaming provider rejected
0x1A Performing firmware update for GSM modem, controller not ready to operate
0x1E Error when switching operating state (MODE)
0x1F Unknown operating state (MODE)
0x23 Modem information not up to date
Error transferring parameters (group error message, could not transfer all pa-
0x28
rameters)
0x29 Error transferring the Service Center number
0x2A Error transferring the roaming parameter
Incorrect PIN value in PARAMETER:
Letter or another invalid character entered
0x2B
More than eight digits entered
Semicolon is missing
Incorrect roaming value in PARAMETER:
0x2C Value not set to true or false
Incorrect value for the Service Center number in PARAMETER:
0x2D Phone number not entered in international format (e.g., +49...)

3.13.2 SMS_SEND function block
General The SMS_SEND function block is used to send SMS text messages.
Function block
Figure 3-22 SMS_SEND function block
Function description The SMS_SEND function block can be used to send SMS text messages via the mobile
communication modem of the ILC 151 GSM/GPRS. The function block can be instantiated
multiple times. Using the ID input, a maximum of 100 SMS_RECEIVE function blocks can
be addressed.
A password request has been implemented as a safety function. The password must be
specified at the SMS_RECEIVE function block.
In order to make sure that there is a mobile communication connection, we recommend

applying a positive edge (FALSE TRUE) at the ENABLE input of the
MOBILE_CONNECT function block and requesting the VALID output before sending an
SMS text message.

ILC 151 GSM/GPRS
Input parameters
Table 3-10 Inputs of the SMS_SEND function block

A positive edge causes the function block to send the SMS text pending at the
REQUEST BOOL
DATA input to the phone number specified at the NUMBER input by SMS.
Phone number to which the SMS text message should be sent, specified in inter-
NUMBER STRING
national format (e.g., +495235300) or starting with 00 (e.g., 005235300).
Optional identifier (ID) of a receive block enabling blocks with an identical ID to be
assigned to each other in the event of multiple instantiations of the
SMS_SEND/SMS_RECEIVE blocks. For example, if several receive blocks are
available in the application, you can send an SMS text message directly to a spe-
cific receive block using the ID. If no ID is specified, the SMS text message will be
sent to the receive block with the ID = 0.
We recommend that you always use the ID for unique identification of

the sender and receiver.
The ID is used to assign SMS text messages to a specific receiver, if several re-
ceive blocks are used within the application. The function block on the receive side
ID UINT
outputs the SMS text message only if the ID parameterized at the block matches
the ID of the SMS text message received.
The block places the specified ID in front of the SMS text to be sent (see SMS for-
mat on page 74).
If the SMS text message is sent from another device (not from an
ILC 151 GSM/GPRS, but from a mobile phone, for example), the re-
quired SMS format must be implemented by the user.
ID format: ID<YY>;
ID value range (YY =): 0...99dec

Table 3-10 Inputs of the SMS_SEND function block

Optional password that must match the password specified for the
SMS_RECEIVE block. If the passwords do not match, the SMS_RECEIVE func-
tion block will discard the SMS text message. This input must not be wired.
We recommend using password protection for security reasons.
The block places the specified password in front of the SMS text to be sent (see
SMS format on page 74).
PASSWORD STRING
If the SMS text message is sent from another device (not from an
ILC 151 GSM/GPRS, but from a mobile phone, for example), the re-
quired SMS format must be implemented by the user.
Password format: PTC<XX>;

Maximum number of characters in the password: 10
Permissible characters: see Section Permissible character set on page 75.
The actual text of the SMS text message is applied to this input.
The maximum permissible number of characters in the SMS text is calculated ac-
cording to the following formula when a password and an ID have been specified:
Cmax = 160 - (CPW + 6) - (CID + 5)
Cmax: Maximum number of characters in the SMS text

ARRAY
DATA [0...1] OF CPW: Number of characters in the password
STRING CID: Number of characters in the ID
All 160 characters can be used if neither a password nor an ID have been speci-
fied.
If the specified data is not IEC-compliant, the block outputs an error message (see
STATUS output).
Permissible characters (as of firmware Version 3.54): see Section Permissible
character set on page 75.

ILC 151 GSM/GPRS
Output parameters
Table 3-11 Outputs of the SMS_SEND function block

A positive edge at this output indicates that the function block has been executed
DONE BOOL and an SMS text message has been sent.
FALSE: The SMS text message has not been sent yet.
FALSE: Resending not permitted yet. The block is still being executed.
TRUE: The block is ready to send an SMS text message.
READY BOOL
AND this input with the REQUEST input.
ERROR BOOL After a timeout of at least 5 seconds, the block acknowledges itself and
then sets ERROR to FALSE and READY to TRUE.

TRUE)
Value Meaning
0x0A Wrong data type at DATA input
0x0B Password at PASSWORD input too long
0x0C Too many characters at DATA input
0x0D Too many characters at NUMBER input
0x0E Timeout during transmission
0x0F Too many characters at ID input
0x10 No phone number created at the NUMBER input of the block
0x11 The password string contains an invalid character (Figure 3-23 on page 75).
SMS format The SMS_RECEIVE block expects an SMS text message in a specific format that supports
additional parameters preceding the actual message text, as described below. The
SMS_SEND block must create and send the SMS text message in accordance with this for-
mat.
If the SMS text message is sent from another device (not from an ILC 151 GSM/GPRS,
but from a mobile phone, for example), the required SMS format must be implemented by
the user.
Syntax of an SMS text message: PTC<Password>;ID<ID>;SMS text

The individual parameters are separated by semicolons. The ID and password can be en-
tered in any order. However, they must both be placed in front of the actual SMS text.
For additional information on the password and ID, please refer to the descriptions of the
PASSWORD and ID inputs (see Table 3-10 on page 72).

The sent SMS text message has the following format, for example:
Without ID and without password: SMS text
With ID = 3 and without password: ID<3>;SMS text
Without ID and with password HELLO: PTC<HELLO>;SMS text
With ID = 3 and password HELLO: ID<3>;PTC<HELLO>;SMS text
Permissible character set The figure below shows the character set for SMS text messages that is supported as of
firmware Version 3.54.
Figure 3-23 Permissible character set
The complete character set of the SMS specification has not been implemented. The fol-
lowing characters are not available:
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
, , ,

ILC 151 GSM/GPRS
3.13.3 SMS_RECEIVE function block
General The SMS_RECEIVE function block is used to receive SMS text messages.
Function block
Figure 3-24 SMS_RECEIVE function block
Function description The SMS_RECEIVE function block is used to receive SMS text messages via the mobile
communication modem integrated in the ILC 151 GSM/GPRS. The function block can be in-
stantiated multiple times. Due to the maximum value range of the ID (0...99; see also ID
input at the SMS_SEND function block) we recommend generating no more than 100 in-
stances of the SMS_RECEIVE block.
A password request has been implemented as a safety function. The password must be
specified at the SMS_RECEIVE function block. The password must match the password for
the SMS_SEND block with the same ID.
If the incoming SMS text message is sent from another device (not from an
ILC 151 GSM/GPRS, but from a mobile phone, for example), the required SMS format
must be implemented by the user.

Input parameters
Table 3-13 Inputs of the SMS_RECEIVE function block

FALSE: Block is not activated.
ENABLE BOOL
TRUE: Block is active and waiting for messages.
Optional identifier (ID) to differentiate multiple instantiations of the block.
Depending on the value present at this input, only SMS text messages with an
identical ID will be received. The function block with ID = 0 only handles SMS text
messages without ID, the function block with ID = 22 only handles SMS text mes-
sages with ID = 22. SMS text messages with other IDs will be deleted.
ID UINT
We recommend that you always use the ID for unique identification of
the sender and receiver.
ID format: ID<YY>;
ID value range (YY =): 0...99dec
Optional password
If a password is specified for this input, the block will only receive SMS text mes-
sages that have an identical password. If no password is specified, the function
block can only receive SMS text messages without a password.
If the passwords do not match (no password/incorrect password), the
SMS_RECEIVE function block will discard the SMS text message.
PASSWORD STRING
We recommend using password protection for security reasons.
Password format: PTC<XX>;

Maximum number of characters in the password: 10
Permissible characters: see Section Permissible character set on page 75.
Output parameters
Table 3-14 Outputs of the SMS_RECEIVE function block

New Data Received
Return value indicating whether an SMS text message has been received.
NDR BOOL FALSE: No SMS text message received.
Positive edge (FALSE TRUE):
An SMS text message has been received.
ERROR BOOL
The error is pending until it has been removed or it disappears automatically, this
will be the case for at least one cycle.

ILC 151 GSM/GPRS
Table 3-15 Inputs/outputs of the SMS_RECEIVE function block

Phone number of the sender.
RETURN_ADDRESS STRING This string can be copied directly and used as a phone number for the SMS_SEND
function block.
Date and time the SMS text message was received at the Service Center.
RECEIVE_TIME STRING
Format: dd/mm/yy,hh:mm+ss+GMTxx
The actual text of the SMS text message is output at this output.
Password (CPW + 6) and ID (CID + 5) are filtered out internally by the function
block.
ARRAY
DATA [0...1] OF Since a string may have a maximum of 80 characters, the first 80 characters of the
STRING SMS text message are located in ARRAY OF STRING [0], the other characters are
located in ARRAY OF STRING [1].
If the specified data is not IEC-compliant, the block outputs an error message (see
STATUS output).

TRUE)
Value Meaning
The data type at the DATA output does not have the expected format (field
0x01
consisting of two strings).
0x02 The value at the ID input is greater than 99.
The ID has been assigned twice, at least two SMS_RECEIVE blocks have an
0x03
identical ID.

3.13.4 GPRS_CONNECT function block
General This function block is used to activate/deactivate the GPRS (General Packet Radio Service)
mobile communication service in a GSM network.
Function block
Figure 3-25 GPRS_CONNECT function block
Function description Once you have successfully registered in the GSM network and activated GPRS using the
GPRS_CONNECT function block, data can be transmitted in the mobile communication
network using IP blocks via a TCP/IP connection.
The GPRS parameters can be set in PC Worx in the Device Details window (see
Figure 3-27 on page 81).
The use of GPRS is registered with the provider using the mobile communication modem
integrated in the ILC 151 GSM/GPRS. To do this, the mobile communication modem must
be registered in the mobile communication network. After configuring the Inline controller,
this can be done automatically via the MOBILE_CONNECT function block or the GSM Set-
tings in PC Worx.
Requirements To register the modem in the mobile communication network of the ILC 151 GSM/GPRS
(GSM Settings) and to use GPRS with the mobile communication modem integrated in the
ILC 151 GSM/GPRS (GPRS Settings), the following settings must be made in PC Worx.

ILC 151 GSM/GPRS
GSM Settings (see Section GSM settings in PC Worx on page 92)
Figure 3-26 GSM Settings in PC Worx (Extended Settings)

GPRS Settings (see Section GPRS settings in PC Worx on page 94)
Figure 3-27 GPRS Settings in PC Worx (Extended Settings)
Mobile communication network registration can be checked via the status of the VALID out-
put of the MOBILE_CONNECT function block. After successful registration, the function
block returns the name of the current provider as a string at the PROVIDER output.
GPRS activation can be checked via the status of the VALID output of the
GPRS_CONNECT function block. After successful activation, the function block returns the
IP address assigned by the provider as a string at the IP_ADD output.
Input parameters
Table 3-17 Input of the GPRS_CONNECT function block

TRUE: Activate GPRS
FALSE: Deactivate GPRS
ENABLE BOOL
As long as a TRUE signal is present at ENABLE, the function block tries to keep
GPRS active.

ILC 151 GSM/GPRS
Output parameters
Table 3-18 Outputs of the GPRS_CONNECT function block

TRUE: GPRS activated
VALID BOOL
FALSE: GPRS deactivated
ERROR BOOL
ERROR indicates the error (ERROR = TRUE) until ERROR is reset with a negative
edge at ENABLE (TRUE FALSE).
Number of bytes received in the current session.
RX_BYTES DWORD
This value is always reset when GPRS is activated.
Number of bytes sent in the current session.
TX_BYTES DWORD
This value is always reset when GPRS is activated.
Table 3-19 Input/output of the GPRS_CONNECT function block

Indicates the IP address at the GPRS interface.
Example: 192.16.1.2 (without leading zeros)
To establish an IP connection to the ILC 151 GSM/GPRS from a client

(e.g., another ILC 151 GSM/GPRS), the client must know this IP_ADD
IP_ADD STRING IP address.
For detailed information on how to establish IP connections in mobile
communication networks, please refer to the
AH EN REMOTE NETWORK ACCESS application note. It can be
downloaded at phoenixcontact.net/products.


TRUE)
Value Meaning
The PPP stack could not establish a connection to the partner within 60 sec-
onds.
Possible causes:
0xff01 Incorrect GPRS password or user name.
GPRS APN (Access Point Name) is not supported by the provider.
Poor network quality. In case of poor network quality, it may be necessary
to acknowledge the error automatically.
A data call has higher priority than the GPRS connection.
Possible reasons:
0xff02 The GPRS connection has been interrupted due to a data call on the mo-
bile communication modem.
A data call is active and an attempt was made to activate GPRS.
0xff03 Unknown error in the network.
0xff04 At present, the device is not registered with a provider.
0xff05 The APN could not be set.
Internal error code.
0xeexx
Please contact your nearest Phoenix Contact representative.
Internal error code.
0xefxx
Please contact your nearest Phoenix Contact representative.

ILC 151 GSM/GPRS
3.14 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 up to a maximum of sixteen PCP devices.

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.

3.15 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. 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 control-
lers 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-28 Example programming

ILC 151 GSM/GPRS
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-29 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.

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

ILC 151 GSM/GPRS

The Inline controller under PC Worx program creation and example projects
4 The Inline controller under PC Worx program creation

and example projects
This section describes how to create software for the ILC 151 GSM/GPRS in the PC Worx
software.
4.1 Creating a new project
Start PC Worx.
Select the New Project... command from the File menu to create a new project using
a template.
Figure 4-1 File, New Project... menu
In the New Project dialog, select the ILC 151 GSM/GPRS... template according to
the version of the Inline controller you are using.
Save the project using an appropriate name (UM_ILC_151_GSM_GPRS in the exam-
ple in Figure 4-2).
Figure 4-2 Project information after creating a new project

ILC 151 GSM/GPRS
Switch to the bus configuration workspace.
Figure 4-3 Bus Configuration button
Check the IP address settings of the ILC 151 GSM/GPRS controller and adapt them to
your network environment, if required (see Section Assigning the IP address for the
controller on page 42).
Figure 4-4 ILC 151 GSM/GPRS: Device Details IP Settings
Select the File, Save Project As / Zip Project As... command.
Figure 4-5 File, Save Project As / Zip Project As... menu
Enter a name for your project (here: UM_ILC_151_GSM_GPRS).

Click on the Save button.

Figure 4-6 Save/Zip project as dialog
For additional information, please refer to the quick start guide or the online help for
PC Worx.

ILC 151 GSM/GPRS
4.2 GSM settings in PC Worx
The parameters required to establish a GSM connection to the mobile communication net-
work can be specified in PC Worx using the MOBILE_CONNECT function block or under
GSM Settings on the Extended Settings tab in the Device Details window.
Figure 4-7 GSM Settings in PC Worx (Extended Settings)
Table 4-1 GSM parameters in PC Worx
Parameter Description
PIN The PIN is a number up to eight digits that is used to unlock the
SIM card.
Service Center The Service Center number is the phone number of the SMS
Phone Number Center to which the SMS text messages are sent. From there, the
SMS text messages are further distributed.

Table 4-1 GSM parameters in PC Worx
Roaming The Roaming parameter indicates whether the mobile communi-
cation modem of the ILC 151 GSM/GPRS is allowed to register in
the mobile communication network of a third-party provider via
roaming.
Roaming allowed: check box activated
Roaming not allowed: check box deactivated
Please note that the use of mobile communication net-

works from third-party providers may result in addi-
tional costs.
Allowed Phone Num- Up to ten allowed phone numbers can be used to establish a re-
bers mote maintenance connection to the ILC 151 GSM/GPRS via
CSD.
The strings specified here are compared with the string of the call-
ing number. If an allowed number completely matches the calling
number or an allowed number is part of the calling number, a dial-
up connection can be established to the ILC 151 GSM/GPRS.
By specifying parts of a number it is possible to activate several
phone numbers with one entry. For example, 175 permits all
numbers that include this combination.
CHAP CHAP is a protection mechanism requiring the input of both a
user name and a password. The user name and the password are
requested when establishing a remote maintenance connection.
They need to be entered before a dial-up connection is started.
For additional information, please refer to the

AH EN REMOTE NETWORK ACCESS application
note.
The GSM parameters are stored retentively and will still be available after the supply volt-
age has been switched off and then on again. If other GSM parameters (PARAMETER in-
put: PIN/Service Center number/roaming) are transmitted to the controller using the
MOBILE_CONNECT function block, the data stored previously will be overwritten and the
current data will be stored retentively on the ILC 151 GSM/GPRS.

ILC 151 GSM/GPRS
4.3 GPRS settings in PC Worx
GPRS can be used when you activate it via the GPRS_CONNECT function block. Registra-
tion in the GSM mobile communication network is done via the MOBILE_CONNECT func-
tion block or via the GSM settings (see Section GSM settings in PC Worx on page 92).
Data is transmitted in the mobile communication network using IP blocks via a TCP/IP con-
nection.
The GPRS parameters are set in PC Worx in the Device Details window (see Figure 4-8).
Figure 4-8 GPRS Settings in PC Worx (Extended Settings)
Table 4-2 GPRS parameters in PC Worx
APN Access Point Name
Access point to the network
This data
GPRS User Name User name for the selected access point
depends on
GPRS Password Password for the selected access point the provider.
Primary/Secondary IP address of the primary and secondary DNS
DNS Server servers of the provider

Table 4-2 GPRS parameters in PC Worx
GPRS On at Startup If this check box is enabled, GPRS is activated after startup of the
ILC 151 GSM/GPRS and a connection is established to the se-
lected mobile communication network. This means that GPRS is
activated independently of the application program and the
GPRS_CONNECT function block.
The ILC 151 GSM/GPRS tries to keep the GPRS connection ac-
tive, even if it is set to the STOP state.
If this check box is disabled and the ILC 151 GSM/GPRS is set to
STOP state, the GPRS connection will be interrupted.
Activate Port Filter If this check box is enabled, a port filter is activated blocking the
ports between 0...2000 as well as port 41100. This ensures there
is no unauthorized access to the ILC 151 GSM/GPRS using
PC Worx. Port 80 is an exception. This port will not be blocked,
thereby allowing access to the web server independently of the
port filter.

ILC 151 GSM/GPRS
4.4 Example projects
This section provides a few example projects which have been created with PC Worx (Ver-
sion 6.00 Service Pack 3). You can program these projects easily by yourself. You can also
use these examples as a basis for your own applications.
For additional information on PC Worx and in particular the function blocks used in these
examples, please refer to the quick start guide for the software and the online help.
The following applies to all examples given on the following pages:

Use PC Worx for programming according to the figure shown.
Assign the values specified in the tables to the inputs, outputs, and variables used.
4.4.1 Example: sending/receiving an SMS text message
Description/programming The MOBILE_CONNECT function block can be used to parameterize and diagnose the
GSM modem.
If you want to avoid parameterization, e.g., because it has been implemented with PC Worx,
the string ;;; or ;true;; must be specified as a parameterization string at the PARAME-
TER input.
Successful registration in the GSM mobile communication network is indicated with a TRUE
signal at the VALID output following a TRUE signal at the ENABLE input.
The GSM modem is now ready for operation. The SMS service can now be used.
Before sending an SMS text message, it is recommended to check whether the modem is
registered in the GSM mobile communication network. To do this, AND the VALID output of
the MOBILE_CONNECT function block with the READY output of the SMS_SEND function
block. The ANDing result is linked to the REQUEST input of the SMS_SEND function block.
In addition, the SEND_Request variable is linked to the ANDing.
To attempt to send an SMS text message, the SEND_Request variable is set to TRUE di-
rectly from the application. A successful transmission attempt is indicated with a pulse
(edge change: FALSE TRUE FALSE) at the DONE output of the SMS_SEND function
block.

To receive SMS text messages, the ENABLE input at the SMS_RECEIVE function block
must be set to TRUE. In this case, all SMS text messages received by the GSM modem
which contain the specified combination of ID and password will be read. A positive edge at
the NDR output (FALSE TRUE) indicates that an SMS text message has been received.
It is useful to immediately evaluate the received SMS text message within the same PLC
cycle as it is received or to copy it to another location. If this is not done, a new SMS text
message received in the next PLC cycle will possibly overwrite the SMS text message pre-
viously received.

ILC 151 GSM/GPRS
4.4.2 Example: active IP communication
GSM modem.
TER input.
The GSM modem is now ready for operation. The GPRS service can now be used.
Before activating GPRS, it is recommended to check whether the modem is registered in

the GSM mobile communication network. To do this, AND the VALID output of the
MOBILE_CONNECT function block with the GPRS_Enable variable. The GPRS_Enable
variable is used to activate GPRS in the application.
The ANDing result is linked to the ENABLE input of the GPRS_CONNECT function block.
If there is a TRUE signal at the VALID output of the MOBILE_CONNECT function block,
GPRS can be started via a TRUE signal (GPRS_Enable variable).

IP communication can be activated when GPRS availability is indicated at the VALID output
of the GPRS_CONNECT function block. The IP_Enable variable can be used to control IP
communication from the application.
The ILC 151 GSM/GPRS (client) actively accesses a server specified with the string at the
PARTNER input of the IP_CONNECT function block. Owing to the transmission times in the
network, each timeout time is set to 5000 milliseconds.

ILC 151 GSM/GPRS
4.4.3 Example: passive IP communication
GSM modem.
TER input.
The GSM modem is now ready for operation. The GPRS service can now be used.
Before activating GPRS, it is recommended to check whether the modem is registered in

the GSM mobile communication network. To do this, AND the VALID output of the
MOBILE_CONNECT function block with the GPRS_Enable variable. The GPRS_Enable
variable is used to activate GPRS in the application.
The ANDing result is linked to the ENABLE input of the GPRS_CONNECT function block.
If there is a TRUE signal at the VALID output of the MOBILE_CONNECT function block,
GPRS can be started via a TRUE signal (GPRS_Enable variable).

IP communication can be started when GPRS availability is indicated at the VALID output
of the GPRS_CONNECT function block.
The ILC 151 GSM/GPRS (server) is waiting to be addressed by a communication partner
via the port specified at the PARTNER input of the IP_CONNECT function block. Owing to
the transmission times in the network, each timeout time is set to 5000 milliseconds.

ILC 151 GSM/GPRS

System variables and status information
5 System variables and status information
5.1 General notes
This section describes the special program functions of the PC Worx software that are avail-
able for the Inline controller.
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 diagnos-
tic 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
5.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 5-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

ILC 151 GSM/GPRS
Table 5-1 System variables of the status register for local digital inputs and outputs
ONBOARD_OUTPUT_BIT0 BOOL State of local output OUT1
ONBOARD_OUTPUT_OVERLOAD_0_3 BOOL Overload of one of the local outputs
5.3 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 informa-
tion.
Table 5-2 System variables of the diagnostic status register

MASTER_DIAG_STATUS_REG_USER BOOL User error/parameterization error
MASTER_DIAG_STATUS_REG_PF BOOL Peripheral fault
MASTER_DIAG_STATUS_REG_BUS BOOL Bus error
MASTER_DIAG_STATUS_REG_CTRL BOOL Error on the 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 aborted
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

5.4 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 parame-
ter register:
Error location
Error code
15 8 7 0
3 1
Segment number Position in the segment
Example: device number 3.1

6219B040
Figure 5-1 Error location in the diagnostic parameter register
Special case: if an interface error cannot be located, the value 128 is indicated in the di-
agnostic parameter register, i.e., bit 7 is set.
The diagnostic parameter register is rewritten whenever an error occurs. The diagnostic pa-
rameter register contains the value 0 if no errors are detected.
Table 5-3 System variables of the diagnostic parameter register

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

ILC 151 GSM/GPRS
5.5 IEC 61131 runtime system
There is a separate group of system variables for the IEC 61131 runtime system.
Table 5-4 System variables of the IEC 61131 runtime system

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 un-
specified 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 over-
written (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

5.6 Control processor
The system variables listed below show the states of the diagnostic status register on the
control processor of the Inline controller.
Table 5-5 System variables of the control processor

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
5.7 Power storage, realtime clock
Table 5-6 System variables of the power storage and realtime clock

RTC_BATTERY_LOW BOOL Low capacity of the power storage for the realtime clock.
TRUE: Power storage is being charged.
FALSE: Power storage is fully charged.
The charging process has been completed.
RTC_DATA_INVALID BOOL The realtime clock data is invalid.
5.8 Power supplies
Table 5-7 System variables of the power supplies

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)

ILC 151 GSM/GPRS
5.9 Mode selector switch
Table 5-8 System variables of the mode selector switch

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.
5.10 System time
Table 5-9 System variables of the system time

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)

5.11 Bit error rate (BER)
Table 5-10 System variable of the bit error rate (BER)

BER REAL Mean value of the bit error rate for the data link during the last
hour
Table 5-11 Bit error rate of the data link
Value Bit error rate as a percentage

0 < 0.2%
1 0.2% - 0.4%
2 0.4% - 0.8%
3 0.8% - 1.6%
4 1.6% - 3.2%
5 3.2% - 6.4%
6 6.4% - 12.8%
7 > 12.8%
99 Not known or not measurable
The bit error rate is particularly relevant if communication takes place via GPRS connection
or a data link is established via CSD. To evaluate the bit error rate, it is recommended that
you determine the individual bit error rates within a certain period of time during communi-
cation and generate a mean value.
The mean value of the bit error rate for the data link during the last hour is calculated au-
tomatically and indicated via the BER system variable.
If the mean bit error rate is above the value 1 during communication, permanent GPRS com-
munication is only possible to a limited extent and is characterized by multiple aborts at IP
level.
In this case, check whether the antenna and the antenna cable have been installed correctly
(see Section 2.14 Antenna) and select an alternative installation location, if required.

ILC 151 GSM/GPRS

Technical data and ordering data
6 Technical data and ordering data
6.1 Technical data
General data
CE conformance According to R&TTE Directive 1999/5/EC
Dimensions 85 mm x 120 mm x 69 mm
Weight 285 g, approximately
Connection data for connectors
Connection method Spring-cage terminals
Conductor cross section 0.2 mm2 to 1.5 mm2 (solid or stranded), 24 - 16 AWG
General supply
Use a power supply without fall-back characteristic curve (see Section Sizing of the power supply on page 34).
24 V main supply UM
Connection technology Spring-cage terminals
Nominal value 24 V DC
Tolerance -15%/+20% (according to EN 61131-2)
Ripple 5%
Current consumption at nominal voltage (typical) 6 mA + 7 mA for each input set
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 polarity protection diodes; 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 four times (400%) the nominal current of the external
fuse, to ensure that the fuse blows safely in the event of an error.
24 V segment supply US
Ripple 5%
Current consumption at nominal voltage (typical) 10 mA + 10 mA for each output set + load
Current consumption at nominal voltage (maximum) 8A
Continuation Through potential routing

ILC 151 GSM/GPRS
24 V segment supply US
Protective measures
Polarity reversal Parallel polarity protection diodes; 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 four times (400%) the nominal current of the ex-
ternal fuse, to ensure that the fuse blows safely in the event of an error.
24 V supply UILC
Ripple 5%
Maximum permissible voltage range including all tolerances 19.2 V DC to 30.0 V DC (ripple included)
Current consumption at nominal voltage (minimum) 80 mA (no-load operation, i.e., no local bus devices connected,
bus inactive)
Current consumption at nominal voltage (typical) 215 mA
Current consumption at nominal voltage (maximum) 880 mA (380 mA communications power + 500 mA analog power supply)
Protective measures
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 in the external
power supply unit.
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 (potential jumper)

Nominal value 7.5 V DC
Tolerance 5%
Ripple 1.5%
Maximum output current 0.8 A DC (internally protected against short circuit)
Derating See Section A 4 on page 123
24 V analog supply (potential jumper)


24 V analog supply (potential jumper)

Ripple 5%
Maximum output current 0.5 A DC
Protective measures Electric short-circuit protection
INTERBUS
Number of I/O points 4096, maximum
Number of data words 256, maximum
Number of bus segments 32, maximum
Transmission speed 500 kbps or 2 Mbps
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 PCP devices 16
Number of remote bus levels 4, maximum (see Section 2.2 on page 14)
Network interface
Type Ethernet
10Base-T and 100Base-TX
Speed 10 Mbits (10Base-T), 100 Mbits (100Base-TX)
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
RJ45 socket
Inline local bus

Interface Inline local bus
Electrical isolation No
Number of devices 63, maximum, limited by the maximum current consumption from the commu-
nications power and analog supply
Modbus/TCP
Number of I/O points 16,384, maximum (internal Modbus/TCP client)

ILC 151 GSM/GPRS
Digital inputs
Number 16
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 I16
Signal change 0 -> 1 5 ms
Signal change 1 -> 0 5 ms
Permissible cable length to the sensor 30 m (to ensure conformance with EMC Directive 2004/108/EC)
Use of AC sensors AC sensors in the voltage range < UIN are limited in application (according to
the input design)
Digital outputs
Number 4
Output design Protected outputs according to EN 61131-2
Nominal output voltage 24 V DC
Nominal output current 500 mA
Nominal current Inom per channel 0.5 A
Total current 2A
Nominal load
Ohmic 12 W
Lamp 12 W
Inductive 12 VA (1.2 H)
Switching frequency with nominal inductive load 0.5 Hz (1.2 H), maximum
Behavior in the event of inductive overload Output may be damaged
Diagnostics and status indicators

IEC 61131 runtime system (PLC) FR, FF
GSM/GPRS mobile communication connection GSM, AV, TR
Ethernet (ETH) LINK, ACT
INTERBUS diagnostics (IL) RDY, BSA, FAIL, PF
Digital inputs and outputs I1 to I16, E, O1 to O4
Supply voltages US, UM, UL
IEC 61131 runtime system

Programming system PC Worx
Speed 1.5 ms for 1 K instructions, typical
Shortest cycle time (for cyclic task) 1 ms
Program memory 512 kbytes, 48 K instructions in IL, typical
Mass storage 512 kbytes
Memory for retentive data 48 kbytes NVRAM

IEC 61131 runtime system

Number of control tasks 8
Parameterization memory
Integrated 4-Mbyte Flash memory (100,000 write access operations per sector, typical)
Plug-in 256 Mbytes/2 Gbytes (1,000,000 write access operations per sector, typical),
see Accessories on page 118
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 stor-
ing data in 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/mem-
ory 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.
Realtime clock
Accuracy 1 min./week, maximum
Power reserve 10 days
Charging time for the power storage 24 hours
Ambient conditions
Degree of protection IP20 (EN 60529:1991)
Permissible temperature (operation) -25C to +55C
Permissible temperature (storage/transport) -25C to +85C
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

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: 25C (2C)
- Humidity: 75% (5%)
- Test duration: 10 days
Hydrogen sulfide (H2S) Concentration 1 0.3 ppm
Ambient conditions
- Temperature: 25C (2C)
- 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, IEC 60068-2-6 5g (operation)
Shock testing according to EN 60068-2-27, IEC 60068-2-27 25g

ILC 151 GSM/GPRS
GSM
This device complies with Part 15 of the following FCC standard: FCC ID: RI7GE864Q2.
Maximum antenna gain 3 dBi
WARNING: Transmitting antenna/electromagnetic radiation risk of personal injury

The antenna for this transmitter must be installed at least 20 cm away from people.
NOTE: Risk of damage to equipment

The antenna for this transmitter must not be installed or operated near/in conjunction with other antennas or transmitters.
Frequencies 850 MHz, 900 MHz, 1800 MHz, 1900 MHz (EGSM)
Transmission power 2 W at 850 MHz and 900 MHz
1 W at 1800 MHz and 1900 MHz
SIM interface 3 V SIM card
Transmission speed Automatic adjustment
DCE/DCE 300 baud ... 14.4 kBaud
Fax 2400 baud ... 14.4 kBaud
GPRS 300 bps ... 85.6 kbps
Compatibility V.34, V.32, V.22bis, V.110
GPRS compatibility GPRS class 10, class B
Coding scheme: CS1 ... CS4
4 time slots for receiving data
2 time slots for sending data
Command set compatibility AT standard command set and extended
V.250 basic command set
Antenna connection 50 impedance SMA antenna socket
Bandwidth 70 MHz (850 MHz), 80 MHz (900 MHz)
170 MHz in DCS and 140 MHz (PCS band)
VSWR values 2:1
Conformance with EMC Directive 2004/108/EC

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
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 disturbance variables EN 61000-4-6 Criterion A
IEC 61000-4-6 Test voltage: 10 V
Noise emission test according to EN 61000-6-4

Interference emission of housing EN 55011 Class A

Conformance with R&TTE Directive 1999/5/EC

EMC EN 61000-6-2 Generic standard for the industrial sector
Immunity to interference
(electromagnetic compatibility)
Safety EN 60950-1
Protection of personnel with regard to electrical
safety
Health EC Gazette 1999/519/EC EC Council recommendation of July 12, 1999
Limitation of exposure of the population to electro-
magnetic fields
Radio DIN EN 301511
Effective use of the frequency spectrum and pre-
vention of radio interference
Approvals
For the latest approvals, please visit phoenixcontact.com or phoenixcontact.net/products.

ILC 151 GSM/GPRS
6.2 Ordering data
6.2.1 Products
Description Type Order No. Pcs./Pkt.

Inline controller, ILC 151 GSM/GPRS 2700977 1
including accessories (connectors and marking fields)
6.2.2 Accessories

Connector set for Inline bus coupler with connected I/Os IL BKDIO-PLSET 2878599 1
GSM UMTS antenna with omnidirectional character- PSI-GSM/UMTS-QB-ANT 2313371 1
istics 2m
Antenna cable with SMA circular connector
Dimensions 76 mm
Diameter 20 mm
Height
Multiband mobile communication antenna with TC ANT MOBILE WALL 5M 2702273 1
mounting bracket for outdoor installation
Antenna cable with SMA circular connector 5m
Dimensions
Diameter 48 mm
Height 82 mm
Program and configuration memory, plug-in, 512 SD FLASH 512MB 2988146 1
Mbytes
Program and configuration memory, plug-in, 512 SD FLASH 512MB APPLIC A 2701799 1
Mbytes with license key for function block libraries,
e.g., for: SNMP, SQL, wireless, motion functions, etc.
Program and configuration memory, plug-in, 2 SD FLASH 2GB 2988162 1
Gbytes
Program and configuration memory, plug-in, 2 SD FLASH 2GB APPLIC A 2701190 1
Gbytes with license key for function block libraries,
e.g., for: SNMP, SQL, wireless, motion functions, etc.
QUINT POWER power supplies See current catalog from Phoenix Contact phoenixcontact.net/products
6.2.3 Software

PC Worx automation software See current catalog from Phoenix Contact phoenixcontact.net/products

6.2.4 Documentation

Modbus/TCP with Phoenix Contact controllers application note AH EN MODBUS/TCP 1
Configuring and installing the INTERBUS Inline product range user manual IB IL SYS PRO UM E 1
Automation terminals of the Inline product range user manual IL SYS INST UM E 1
PC Worx quick start guide UM QS EN PC WORX 1
Data sheet for the PSI-GSM/UMTS-QB-ANT GSM UMTS antenna DB EN PSI-GSM/UMTS-QB-ANT 1

ILC 151 GSM/GPRS

A Appendix: service, maintenance, and derating
A1 Error causes and remedies
The following tables provide error information concerning the mobile communication con-
nection or the mobile communication modem integrated in the ILC 151 GSM/GPRS:
Table 3-9 on page 69 (MOBILE_CONNECT function block)
Table 3-12 on page 74 (SMS_SEND function block)
Table 3-16 on page 78 (SMS_RECEIVE function block)
Table 3-20 on page 83 (GPRS_CONNECT function block)
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. (see diagnostics LED).
The IEC 61131 program is not run- Mode selector switch in STOP posi- Set mode selector switch to
ning. tion. RUN/PROG position.
The devices on the remote bus cannot The IBS IL 24 RB-T-PAC Inline termi- Insert the terminal as the first Inline ter-
be started up. nal is not installed directly after the In- minal directly next to the Inline control-
line controller. ler.
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).
For additional information on errors, their causes, and remedies, please refer to the online
help for the PC Worx function blocks described in Section 3, The Inline controller under
PC Worx general.
A2 Updating the Inline controller firmware
The firmware (integrated software on the Inline controller) can be updated using the Ether-
net 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, please proceed as described in the Firmware update ILC
1.../3..., RFC 4... application note. It can be downloaded at
phoenixcontact.net/products.

ILC 151 GSM/GPRS
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 us-
ing 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.

Derating
A4 Derating
105
P [%]
100
95
90
85
80
75
70
65
60
0 10 20 30 40 50 60
T [C]
Figure A-2 Derating curve for the ILC 151 GSM/GPRS
Key:
P [%] Power dissipation as a percentage

T [C] Ambient temperature in C
The data is based on a supply voltage of 24 V.
When working in the upper voltage range (e.g., 30 V), the percentage values increase. In
this case, multiply the percentage values by 1.25 (30 V/24 V = 1.25).
The various functions of the Inline controller have different percentage shares of the power
dissipation.
For the percentage shares, please refer to the following table:
Function Percentage share of the power dissipa-

tion (%)
Inputs 31
Outputs 18
UM 21
UANA 2
UL 28

ILC 151 GSM/GPRS

B Appendix for document lists
B1 List of figures
Section 2
Figure 2-1: Connected Inline local bus ..................................................................14
Figure 2-2: Remote bus levels ..............................................................................14
Figure 2-3: Structure of the Inline controller ..........................................................17
Figure 2-4: Diagnostics and status indicators .......................................................18
Figure 2-5: Inserting (A) and removing (B) the parameterization memory .............21
Figure 2-6: Mode selector switch ..........................................................................22
Figure 2-7: Internal basic circuit diagram ..............................................................23
Figure 2-8: Snapping on the Inline controller (1) ...................................................25
Figure 2-9: Snapping on the Inline controller (2) ...................................................25
Figure 2-10: Connectors to be removed if terminals are installed next to the
Inline controller ....................................................................................26
Figure 2-11: Removing the Inline controller (1) .......................................................27
Figure 2-12: Removing the Inline controller (2) .......................................................27
Figure 2-13: Ethernet interface ................................................................................28
Figure 2-14: Connecting the Ethernet cable to the Inline controller .........................28
Figure 2-15: Inserting the SIM card .........................................................................29
Figure 2-16: Installation of the PSI-GSM/UMTS-QB-ANT antenna .........................31
Figure 2-17: Antenna connection with SMA connector ...........................................32
Figure 2-18: Overload range with fall-back characteristic curve .............................34
Figure 2-19: Overload range without fall-back characteristic curve .......................34
Figure 2-20: Supply voltage connection ..................................................................35
Figure 2-21: Terminal point assignment of connectors 2 to 4 ..................................38
Figure 2-22: Basic wiring of an output with a load (L) ..............................................39
Section 3
Figure 3-1: DCP: setting the IP address ................................................................42
Figure 3-2: Starting IP address assignment via DCP ............................................43
Figure 3-3: Entering the MAC address ..................................................................44
Figure 3-4: Activate BootP button .......................................................................45
Figure 3-5: Message window following BootP .......................................................45

ILC 151 GSM/GPRS
Figure 3-6: Procedure for using the SD card as main memory or

additional memory ..............................................................................47
Figure 3-7: Setting to use the SD card as main memory .......................................48
Figure 3-8: Setting to use the SD card as additional memory ................................50
Figure 3-9: sddisk directory on the SD card ........................................................50
Figure 3-10: New Logfile directory in the sddisk directory ..................................51
Figure 3-11: Opening the Logfile.txt file using the FILE_OPEN function block ......51
Figure 3-12: Extended Settings: Open FTP Folder on Device .................................52
Figure 3-13: Internet Options: Enable FTP folder view ............................................53
Figure 3-14: Deactivating the FTP server ................................................................54
Figure 3-15: Opening the library and selecting the service ......................................55
Figure 3-16: Specifying the user name and password for FTP access ....................56
Figure 3-17: Removing the user name and password for FTP access ....................57
Figure 3-18: Deactivating the HTTP server .............................................................58
Figure 3-19: Setting HTTPS ....................................................................................59
Figure 3-20: Activating the journaling function ........................................................61
Figure 3-21: MOBILE_CONNECT function block ....................................................67
Figure 3-22: SMS_SEND function block .................................................................71
Figure 3-23: Permissible character set ....................................................................75
Figure 3-24: SMS_RECEIVE function block ............................................................76
Figure 3-25: GPRS_CONNECT function block .......................................................79
Figure 3-26: GSM Settings in PC Worx (Extended Settings) ...................................80
Figure 3-27: GPRS Settings in PC Worx (Extended Settings) .................................81
Figure 3-28: Example programming ........................................................................85
Figure 3-29: Alignment padding bytes in data gaps ..............................................86
Figure 3-30: Example programming with padding bytes .........................................87
Section 4
Figure 4-1: File, New Project... menu ..................................................................89
Figure 4-2: Project information after creating a new project ..................................89
Figure 4-3: Bus Configuration button ..................................................................90
Figure 4-4: ILC 151 GSM/GPRS: Device Details IP Settings ..............................90
Figure 4-5: File, Save Project As / Zip Project As... menu ...................................90
Figure 4-6: Save/Zip project as dialog ................................................................91
Figure 4-7: GSM Settings in PC Worx (Extended Settings) ...................................92
Figure 4-8: GPRS Settings in PC Worx (Extended Settings) .................................94

List of figures
Section 5
Figure 5-1: Error location in the diagnostic parameter register ...........................105
Appendix A
Figure A-1: Connecting unshielded cables ..........................................................122
Figure A-2: Derating curve for the ILC 151 GSM/GPRS ......................................123

ILC 151 GSM/GPRS

B2 List of tables
Section 2
Table 2-1: Inline controller operating modes.........................................................22
Table 2-2: Terminal point assignment...................................................................38
Section 3
Table 3-1: GPRS watchdog levels ........................................................................62
Table 3-2: Overview of the function blocks ...........................................................64
Table 3-6: Inputs of the MOBILE_CONNECT function block ................................68
Table 3-7: Outputs of the MOBILE_CONNECT function block .............................69
Table 3-8: Input/output of the MOBILE_CONNECT function block .......................69
Table 3-9: Error values of the STATUS output (ERROR = TRUE) ........................69
Table 3-10: Inputs of the SMS_SEND function block..............................................72
Table 3-11: Outputs of the SMS_SEND function block...........................................74
Table 3-13: Inputs of the SMS_RECEIVE function block ........................................77
Table 3-14: Outputs of the SMS_RECEIVE function block .....................................77
Table 3-15: Inputs/outputs of the SMS_RECEIVE function block ...........................78
Table 3-17: Input of the GPRS_CONNECT function block .....................................81
Table 3-18: Outputs of the GPRS_CONNECT function block.................................82
Table 3-19: Input/output of the GPRS_CONNECT function block ..........................82
Section 4
Table 4-1: GSM parameters in PC Worx...............................................................92
Table 4-2: GPRS parameters in PC Worx.............................................................94
Section 5
Table 5-1: System variables of the status register for local digital inputs
and outputs ........................................................................................103

ILC 151 GSM/GPRS
Table 5-2: System variables of the diagnostic status register .............................104

Table 5-3: System variables of the diagnostic parameter register.......................105
Table 5-4: System variables of the IEC 61131 runtime system ...........................106
Table 5-5: System variables of the control processor .........................................107
Table 5-6: System variables of the power storage and realtime clock.................107
Table 5-7: System variables of the power supplies .............................................107
Table 5-8: System variables of the mode selector switch ...................................108
Table 5-9: System variables of the system time..................................................108
Table 5-10: System variable of the bit error rate (BER).........................................109
Table 5-11: Bit error rate of the data link ...............................................................109
Appendix A
Table A-1: Installation error causes and remedies ..............................................121

B3 Index
A Ethernet connection .................................................... 17

Ethernet interface........................................................ 28
Alignment
Memory alignment................................................. 85
Antenna....................................................................... 30 F
Antenna socket ........................................................... 17 Fall-back characteristic curve...................................... 34
Fields of application .................................................... 14
B Firmware update ....................................................... 121
FTP access
Basic wiring of an output ............................................. 39
User name and password...................................... 55
BootP .................................................................... 43, 44
FTP functionality ......................................................... 52
BootP server ............................................................... 27
Function block
GPRS_CONNECT ................................................ 79
C
MOBILE_CONNECT ............................................. 67
Character set .............................................................. 75
SMS_RECEIVE ..................................................... 76
Communication path ................................................... 28
SMS_SEND .......................................................... 71
Connecting cables .................................................... 122
Function blocks
Connecting the supply voltage .................................... 35
GSM/GPRS mobile communication functions ....... 66
Connecting unshielded cables .................................. 122
PCP communication .............................................. 84
Connection elements .................................................. 17
TCP/IP and UDP/IP communication ...................... 65
Connector ............................................................. 17, 25
Control box.................................................................. 24
G
See also Terminal box
GPRS watchdog ......................................................... 62
Control cabinet............................................................ 24
D H
Hardware requirements............................................... 10
Delivery state ........................................................ 20, 44
HTTP server
Derating .................................................................... 123
Activating/deactivating the HTTP server................ 58
Diagnostic parameter register ................................... 105
Using HTTPS ........................................................ 59
Diagnostic status register.......................................... 104
Diagnostics and status indicators................................ 17
Diagnostics indicators ................................................. 18 I
Digital inputs ............................................................... 38 Inline local bus ............................................................ 14
Digital outputs ............................................................. 38 Input/output parameters
DIN rail ........................................................................ 24 GPRS_CONNECT .......................................... 81, 82
Download changes ..................................................... 46 MOBILE_CONNECT ............................................. 68
SMS_RECEIVE ............................................... 77, 78
E SMS_SEND .................................................... 72, 74
INTERBUS.................................................................. 33
Electronics base.................................................... 17, 25
IP20............................................................................. 24
End bracket................................................................. 24
End plate............................................................... 17, 24
Error causes.............................................................. 121 L
Error diagnostics ......................................................... 18 Local bus..................................................................... 33
Ethernet ...................................................................... 28

ILC 151 GSM/GPRS
M Software requirements ................................................ 10

Status indicators ......................................................... 18
MAC address .............................................................. 27
Status register
Memory alignment
Local digital inputs and outputs ........................... 103
Alignment .............................................................. 85
System variables....................................................... 103
Modbus ....................................................................... 11
Control processor ................................................ 107
Mode selector switch ............................................ 17, 22
IEC 61131 runtime system .................................. 106
Mounting ............................................................... 24, 25
Mode selector switch........................................... 108
Mounting location........................................................ 24
Power storage, realtime clock.............................. 107
Mounting position........................................................ 24
Power supplies .................................................... 107
System time......................................................... 108
N
Network adapter.......................................................... 43
T
Terminal box ............................................................... 24
O
Operating elements..................................................... 17
P
Parameterization memory ........................................... 20
PIN code ..................................................................... 29
Ports............................................................................ 60
Power supply .............................................................. 34
Connection ............................................................ 35
Power supply sizing .................................................... 34
Power supply without fall-back characteristic curve ... 34,
111
R
Realtime clock............................................................. 46
Remote bus................................................................. 33
Removal................................................................ 24, 26
Replacement............................................................... 27
Reset button.......................................................... 17, 20
S
SD card
Additional memory................................................. 49
Functions............................................................... 47
Memory for log files ............................................... 50
Setting the IP address
BootP .................................................................... 43
DCP....................................................................... 42
SIM card...................................................................... 29
SIM card slot ............................................................... 17
Sizing of the power supply .......................................... 34
SMS format ................................................................. 74

Manual ILC 151

Uploaded by

Copyright:

Available Formats

Manual ILC 151

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual ILC 151

Uploaded by

Copyright:

Available Formats

Installing, starting up, and operat-

ing the ILC 151 GSM/GPRS Inline

Designation: UM EN ILC 151 GSM/GPRS

This user manual is valid for:

Designation As of version As of version Order No.

PHOENIX CONTACT 8510_en_03

Published by PHOENIX CONTACT GmbH & Co. KG

General terms and conditions of use for technical documentation

2 Description of the Inline controller ............................................................................................11

3 The Inline controller under PC Worx general .........................................................................41

8510_en_03 PHOENIX CONTACT 5

3.2.2 BootP server ........................................................................................43

5 System variables and status information ................................................................................103

6 PHOENIX CONTACT 8510_en_03

5.3 Diagnostic status register ..................................................................................104

6 Technical data and ordering data ...........................................................................................111

A Appendix: service, maintenance, and derating .......................................................................121

B Appendix for document lists....................................................................................................125

8510_en_03 PHOENIX CONTACT 7

8 PHOENIX CONTACT 8510_en_03

1.1 Purpose of this user manual

1.2 Intended use

1.3 General safety notes

Observe the country-specific installation, safety, and accident prevention regulations.

8510_en_03 PHOENIX CONTACT 9

NOTE: Risk of unauthorized network access

1.5 Hardware and software requirements

Hardware Inline controller

Software PC Worx/PC Worx Express automation software in the following versions:

10 PHOENIX CONTACT 8510_en_03

2 Description of the Inline controller

2.1 General description of the Inline controller

8510_en_03 PHOENIX CONTACT 11

NOTE: Parameterization memory (SD card) formatting note

CSD CSD is the abbreviation for Circuit Switched Data.

GPRS GPRS is the abbreviation for General Packet Radio Service.

12 PHOENIX CONTACT 8510_en_03

A GSM/GPRS connection is not always available. Availability depends on the provider

8510_en_03 PHOENIX CONTACT 13

2.2 Possible fields of application of the

ILC 151 GSM/GPRS

Inline local bus

Figure 2-2 Remote bus levels

14 PHOENIX CONTACT 8510_en_03

2.3 Notes on using the Inline controller in potentially

Approval in accordance with directive 94/9/EC

WARNING: Explosion hazard

8510_en_03 PHOENIX CONTACT 15

2.4 Unpacking the Inline controller

NOTE: Electrostatic discharge

16 PHOENIX CONTACT 8510_en_03

2.5 Connection and operating elements

Ord : xx/x x.xx.x

The Inline controller consists of the following components:

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

3 Mode selector switch

7 SMA antenna connection

The antenna is not supplied as standard with the Inline controller.

8 Connector 1: terminal points for voltage supply

8510_en_03 PHOENIX CONTACT 17