PC WORX Quickstart IT

AUTOMATIONWORX
Quick Start
UM QS EN PC WORX
Order No.: 2699862
PC WorX
AUTOMATIONWORX
Quick Start
PC WorX
05/2007
Designation: UM QS EN PC WORX
Revision: 02
Order No.: 2699862
This user manual is valid for:
Designation Version
PC WorX 5.10 or later
Part of the AUTOMATIONWORX Software Suite 2007 1.30 SP1 or later
7127_en_02 PHOENIX CONTACT

PC WorX
Please Observe the Following Notes
In order to ensure the safe use of the product described, we recommend that you read this
manual carefully. The following notes provide information on how to use this manual.
User Group of This Manual

The use of products described in this manual is oriented exclusively to qualified application
programmers and software engineers, who are familiar with the safety concepts of auto-
mation technology and applicable standards.
Phoenix Contact accepts no liability for erroneous handling or damage to products from
Phoenix Contact or third-party products resulting from disregard of information contained
in this manual.
Explanation of Symbols Used

The attention symbol refers to an operating procedure which, if not carefully followed, could
result in damage to hardware and software or personal injury.
The note symbol informs you of conditions that must be strictly observed to achieve error-
free operation. It also gives you tips and advice on the efficient use of hardware and on
software optimization to save you extra work.
The text symbol refers to detailed sources of information (manuals, data sheets, literature,
etc.) on the subject matter, product, etc. This text also provides helpful information for the
orientation in the manual.
We Are Interested in Your Opinion

We are constantly striving to improve the quality of our manuals.
Should you have any suggestions or recommendations for improvement of the contents
and layout of our manuals, please send us your comments.
PHOENIX CONTACT GmbH & Co. KG

Documentation Services
32823 Blomberg
Germany
Phone + 49 - 52 35 - 30 0
Fax + 49 - 52 35 - 34 18 08
E-mail [email protected]
PHOENIX CONTACT 7127_en_02

PC WorX
General Terms and Conditions of Use for Technical Documentation

Phoenix Contact GmbH & Co. KG 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 data sheets, installation instructions,
manuals, etc.) does not constitute any further duty on the part of
Phoenix Contact GmbH & Co. KG to furnish information on alterations to products and/or
technical documentation. Any other agreement shall only apply if expressly confirmed in
writing by Phoenix Contact GmbH & Co. KG.
Please note that the supplied documentation is product-specific documentation only and
that you are responsible for checking the suitability and intended use of the products in
your specific application, in particular with regard to observing the applicable standards
and regulations.
Although Phoenix Contact GmbH & Co. KG makes every effort to ensure that the informa-
tion content is accurate, up-to-date, and state-of-the-art, technical inaccuracies and/or
printing errors in the information cannot be ruled out. Phoenix Contact GmbH & Co. KG
does not offer any guarantees as to the reliability, accuracy or completeness of the infor-
mation.
All information made available in the technical data is supplied without any accompanying
guarantee, whether expressly mentioned, implied or tacitly assumed. This information
does not include any guarantees regarding quality, does not describe any fair marketable
quality, and does not make any claims as to quality guarantees or guarantees regarding
the suitability for a special purpose.
Phoenix Contact GmbH & Co. KG accepts no liability or responsibility for errors or omis-
sions in the content of the technical documentation (in particular data sheets, installation
instructions, manuals, etc.).
The aforementioned limitations of liability and exemptions from liability do not apply, in so
far as liability must be assumed, e.g., according to product liability law, in cases of premed-
itation, gross negligence, on account of loss of life, physical injury or damage to health or
on account of the violation of important contractual obligations. Claims for damages for the
violation of important contractual obligations are, however, limited to contract-typical, pre-
dictable damages, provided there is no premeditation or gross negligence, or that liability
is assumed on account of loss of life, physical injury or damage to health. This ruling does
not imply a change in the burden of proof to the detriment of the user.
7127_en_02 PHOENIX CONTACT

PC WorX
Statement of Legal Authority

This manual, including all illustrations contained herein, is copyright protected. Use of this
manual by any third party is forbidden. Reproduction, translation, and public disclosure, as
well as electronic and photographic archiving or alteration requires the express written con-
sent of Phoenix Contact. Violators are liable for damages.
Phoenix Contact reserves all rights in the case of patent award or listing of a registered
design. Phoenix Contact reserves all rights in the event of a patent being granted, in as far
as this concerns software of Phoenix Contact that meets the criteria of technicity or has
technical relevance. Third-party products are always named without reference to patent
rights. The existence of such rights shall not be excluded.
Windows 3.x, Windows 95, Windows 98, Windows NT, Windows 2000, and Windows XP
are trademarks of the Microsoft Corporation.
All other product names used are trademarks of the respective organizations.
Internet
Up-to-date information on Phoenix Contact products can be found on the Internet at:
www.phoenixcontact.com
Make sure you always use the latest documentation.

It can be downloaded at:
www.download.phoenixcontact.com
A conversion table is available on the Internet at:

www.download.phoenixcontact.com/general/7000_en_00.pdf
PHOENIX CONTACT 7127_en_02

Table of Contents
1 General....................................................................................................................................1-1
1.1 Introduction ........................................................................................................ 1-1
1.2 Information About This Manual ..........................................................................1-1
1.3 System Requirements ........................................................................................1-1
1.3.1 Supported Operating Systems ........................................................... 1-1
1.3.2 Hardware Requirements .....................................................................1-2
1.4 Ordering Data..................................................................................................... 1-2
2 Installing and Enabling the Software .......................................................................................2-1

2.1 Prior to Installation ............................................................................................. 2-1
2.2 AUTOMATIONWORX Software Suite................................................................ 2-1
2.3 Starting the Installation Program ........................................................................ 2-2
2.4 Starting PC WorX............................................................................................... 2-2
2.5 Enabling the PC WorX License ..........................................................................2-2
3 Helpful Information on PC WorX .............................................................................................3-1

3.1 Online Help ........................................................................................................ 3-1
3.2 Changing the Language .....................................................................................3-1
3.3 PC WorX User Interface.....................................................................................3-2
3.4 Toolbars ............................................................................................................. 3-3
3.5 Workspaces ....................................................................................................... 3-4
3.5.1 Windows in the Workspaces .............................................................. 3-7
3.5.2 Toggling Windows On/Off and Docking/Undocking Windows ............3-8
3.6 "Bus Structure" Window .....................................................................................3-9
3.6.1 Icons in the "Bus Structure" Window .................................................. 3-9
3.6.2 Display in the "Bus Structure" Window ............................................. 3-12
3.7 "EXCEL Link" Window......................................................................................3-14
3.8 "Diag+" Window ...............................................................................................3-15
3.9 Visualization ..................................................................................................... 3-19
4 Sequence for Creating a Project .............................................................................................4-1

4.1 Sequence for Creating a Project ........................................................................ 4-2
4.2 Creating a New Project ...................................................................................... 4-3
4.3 Specifying Project Information ........................................................................... 4-5
4.4 Preparing the PC for Communication................................................................. 4-7
4.5 Checking/Modifying IP Settings for the Controller..............................................4-8
4.6 Decision: Working Online or Offline ................................................................... 4-8
4.7 Inserting PROFINET IO Devices........................................................................ 4-9
4.8 Checking/Modifying the PROFINET Settings for PROFINET IO Devices........4-10
7127_en_02 PHOENIX CONTACT i

PC WorX 5
4.9 Manually Inserting INTERBUS Devices ........................................................... 4-12

4.9.1 Manually Inserting INTERBUS Devices - General ...........................4-12
4.9.2 Inserting INTERBUS Devices Below an INTERBUS Proxy .............. 4-16
4.9.3 Inserting Inline Terminals Below a PROFINET IO Bus Coupler ....... 4-16
4.9.4 INTERBUS Devices Below the PROFINET IO Controller ................4-16
4.10 Compiling After Completing the Bus Topology................................................. 4-17
4.11 Creating the Program ....................................................................................... 4-18
4.12 Compiling After Creating the Program .............................................................4-19
4.13 Generating Variables and Assigning Process Data .........................................4-19
4.13.1 Generating Variables ........................................................................4-19
4.13.2 Assigning Process Data ...................................................................4-20
4.14 Setting the Communication Path: Simulation ................................................... 4-23
4.15 Switching to Working With the System (Online)...............................................4-24
4.16 Assigning the IP Address for the Controller .....................................................4-24
4.16.1 Address Assignment via the PC WorX BootP Server ....................... 4-24
4.16.2 Address Assignment With PC WorX via the Serial Interface ............ 4-26
4.17 Setting the Communication Path...................................................................... 4-27
4.17.1 Communication via the Serial Port ................................................... 4-28
4.17.2 Communication via Ethernet ............................................................ 4-29
4.18 Reading and Importing PROFINET IO Devices ...............................................4-30
4.18.1 Reading PROFINET IO Devices ...................................................... 4-30
4.18.2 Importing PROFINET IO Devices Into the Project ............................ 4-32
4.18.3 Naming PROFINET IO Devices Without a PROFINET Device Name ....
4-32
4.18.4 Bus Configuration With Read PROFINET IO Devices ..................... 4-33
4.18.5 Subsequent Naming of a PROFINET IO Device ..............................4-34
4.19 Checking/Modifying the PROFINET Settings for PROFINET IO Devices........4-36
4.20 Transmitting PROFINET Device Names and IP Settings to
PROFINET IO Devices .................................................................................... 4-37
4.21 Reading INTERBUS.........................................................................................4-38
4.22 Compiling After Reading the Bus Topology .....................................................4-41
4.25 Assigning Process Data ...................................................................................4-42
4.26 Compiling and Sending a Project, and Performing a Cold Restart .................. 4-42
4.26.1 Compiling a Project .......................................................................... 4-42
4.26.2 Sending a Project ............................................................................. 4-42
4.26.3 Performing a Cold Restart ................................................................4-45
4.27 Operation ......................................................................................................... 4-46
4.27.1 Setting the Task Properties .............................................................. 4-46
4.27.2 Debug Mode ..................................................................................... 4-48
4.27.3 Simulation and Debug Mode ............................................................ 4-50
4.27.4 PLC Stop/Run ...................................................................................4-50
4.28 Switching from Simulation to Real Hardware ................................................... 4-51
ii PHOENIX CONTACT 7127_en_02

Table of Contents
5 Example Project for an INTERBUS System ............................................................................5-1

5.1 Describing the Project ........................................................................................5-1
5.2 Sequence for Creating the INTERBUS Project .................................................. 5-2
5.6 Assigning the IP Address for the Controller .......................................................5-5
5.7 Setting the Communication Path........................................................................ 5-6
5.8 Reading INTERBUS...........................................................................................5-6
5.9 Compiling After Completing the Bus Topology................................................... 5-7
5.10 Creating the Program ......................................................................................... 5-7
5.11 Compiling After Completing the Program........................................................... 5-7
5.12 Assigning Process Data .....................................................................................5-8
5.13 Compiling and Sending a Project, and Performing a Cold Restart .................... 5-9
5.14 Operation ........................................................................................................... 5-9
6 Example Project for a System Consisting of PROFINET IO and INTERBUS .........................6-1

6.2 Sequence for Creating the PROFINET Project .................................................. 6-3
6.5 Preparing the PC for Communication................................................................. 6-5
6.6 Checking/Modifying IP Settings for the PROFINET IO Controller...................... 6-6
6.7 Assigning the IP Address for the PROFINET IO Controller ............................... 6-7
6.8 Setting the Communication Path .......................................................................6-7
6.9 Reading and Importing PROFINET IO Devices .................................................6-8
6.10 Checking/Modifying the PROFINET Settings for PROFINET IO Devices..........6-9
6.11 Transmitting PROFINET Device Names and IP Settings to
PROFINET IO Devices .................................................................................... 6-10
6.12 Reading INTERBUS.........................................................................................6-11
6.13 Compiling After Completing the Bus Topology................................................. 6-12
6.16 Assigning Process Data ...................................................................................6-13
6.17 Compiling and Sending a Project, and Performing a Cold Restart .................. 6-14
6.18 Operation ......................................................................................................... 6-14
6.19 Additional Information ......................................................................................6-15
6.19.1 Modifying the PROFINET Device Name .......................................... 6-15
6.19.2 Renumbering Devices ...................................................................... 6-18
6.19.3 Assigning IP Parameters for the PROFINET IO Device ...................6-19
7127_en_02 PHOENIX CONTACT iii

PC WorX 5
7 Example Project for a Simulation With Processor Type "IPC" Control Systems .....................7-1
7.2 Sequence for Creating the Simulation Project ................................................... 7-2
7.6 Manually Inserting INTERBUS Devices ............................................................. 7-5
7.7 Compiling After Completing the Bus Topology................................................... 7-5
7.8 Creating the Program......................................................................................... 7-6
7.9 Compiling After Creating the Program ...............................................................7-6
7.10 Assigning Process Data .....................................................................................7-6
7.11 Setting the Communication Path........................................................................ 7-8
7.12 Compiling and Sending a Project, and Performing a Cold Restart .................... 7-8
7.13 Operation ........................................................................................................... 7-9
7.13.1 Setting the Task Properties ................................................................ 7-9
7.13.2 Simulation and Debug Mode ............................................................ 7-11
7.14 Switching from Simulation to Real Hardware ................................................... 7-13
8 Example Program....................................................................................................................8-1
8.1 Program Description .......................................................................................... 8-1
8.2 Function Blocks Used ........................................................................................8-2
8.3 Programming......................................................................................................8-4
8.4 Setting the Initial Value .................................................................................... 8-10
8.5 Additional Options for PROFINET.................................................................... 8-10
9 PC WorX and SafetyProg........................................................................................................9-1
iv PHOENIX CONTACT 7127_en_02

Table of Contents
A Additional Software Functions ................................................................................................ A-1

A1 Setting the Realtime Clock ............................................................................... A-1
A2 Options for Modifying a Project ........................................................................ A-2
A 2.1 Download Changes (PC WorX Version 3.10 or Later,
ProConOs Version 4.0 or Later) ........................................................ A-2
A 2.2 Online Modifications .......................................................................... A-5
A3 Extended Retain Handling ............................................................................... A-8
A4 Simulation ........................................................................................................ A-9
A5 Replacing a Control System (Hardware Replacement).................................... A-9
A6 Device Description Files................................................................................. A-15
A 6.1 Phoenix Contact Device Description Files ....................................... A-15
A 6.2 Device Description Files for Inline Controllers ................................. A-16
A 6.3 Device Description Files From Other Manufacturers (GSD Files) ... A-16
A 6.4 Creating Device Description Files ................................................... A-17
A7 Visualization ................................................................................................... A-17
A8 Ethernet Topology.......................................................................................... A-18
A9 INTERBUS Topology ..................................................................................... A-23
A 10 Comparing Projects........................................................................................ A-24
B Status Information for a PROFINET IO System ..................................................................... B-1

B1 Status of the PROFINET IO Controller............................................................. B-1
B2 Status of a PROFINET IO Device .................................................................... B-2
B3 INTERBUS register .......................................................................................... B-3
B4 Setting All PROFINET IO Devices to a Defined State...................................... B-4
C AX OPC Server and WebVisit ................................................................................................ C-1

C1 AX OPC Server ................................................................................................ C-1
C 1.1 Preparatory Tasks in PC WorX ......................................................... C-1
C 1.2 OPC Configurator .............................................................................. C-2
C 1.3 OPC Test Client ................................................................................. C-4
C2 WebVisit ........................................................................................................... C-8
D Overview of Phoenix Contact Control Systems...................................................................... D-1
7127_en_02 PHOENIX CONTACT v

PC WorX 5
vi PHOENIX CONTACT 7127_en_02

General
1 General
1.1 Introduction
PC WorX is the automation software, which combines programming according to

IEC 61131, fieldbus configuration, and diagnostics.
The programming system is based on a modern 32-bit Windows technology and enables
easy handling for the user by means of zooming, drag & drop, and dockable windows. IEC
configuration elements can be processed and libraries can be integrated. In addition, the
programming system has a powerful debugging system. In PC WorX, all functions can be
easily accessed via the menu and you can create a project using only a few dialog boxes.
You can then immediately start developing your program.
1.2 Information About This Manual
This document helps you to parameterize a bus configuration and to program the
application program (according to IEC 61131-3) using example projects.
It is assumed the user has knowledge and experience in the operation of PCs and
Windows operating systems, and knowledge in IEC 61131 and Ethernet basics.
More detailed information about the individual functions of PC WorX can be found in the
online help for the program. The entire help function can be called via "Help" in the menu
bar. Help for specific functions can be called via F1.
No functions or commands that require communication with the control system can be
executed without a physical bus configuration.
However, complete parameterization is possible in the "offline" state. The application
program can also be created and compiled.
1.3 System Requirements
1.3.1 Supported Operating Systems
– Windows 2000 SP3

– Windows XP SP2 (recommended)
7127_en_02 PHOENIX CONTACT 1-1

PC WorX
1.3.2 Hardware Requirements
Hardware Requirements for PC WorX

CPU Pentium III 800 MHz, 1 GHz (recommended)
Main memory 128 MB (minimum), 256 MB (recommended)
Hard disk space 500 MB free
CD-ROM drive Yes
Interfaces 1 x serial, Ethernet
Monitor SVGA, resolution of 800 x 600 pixels (minimum),
1024 x 768 (recommended)
Operating devices Keyboard, mouse
1.4 Ordering Data
Designation Order Description

No.
PC WORX DEMO 2985738 DEMO version with MSFC compiler;
maximum of 8 bytes of input data, 8 bytes of output data
PC WORX BASIC LIC 2985275 BASIC version without MSFC compiler;
maximum of 32 bytes of input data, 32 bytes of output data, license key
PC WORX PRO LIC 2985385 PRO version without MSFC compiler;
maximum of 64 kbytes of input data, 64 kbytes of output data, license key
PC WORX PRO-MSFC LIC 2985495 PRO-MSFC version with MSFC compiler;
maximum of 64 kbytes of input data, 64 kbytes of output data, license key
PC WORX BASIC-PRO LIC 2985259 PRO version without MSFC compiler;
maximum of 64 kbytes of input data, 64 kbytes of output data,
license key for upgrade from BASIC to PRO
PC WORX BASIC-PRO MSFC LIC 2985369 PRO-MSFC version with MSFC compiler;
license key for upgrade from BASIC to PRO-MSFC
PC WORX PRO-PRO MSFC LIC 2985479 PRO-MSFC version with MSFC compiler;
license key for upgrade from PRO to PRO-MSFC
PC WORX BASIC UPD 2985262 Version update for BASIC (e.g., from 3.12 to 5.xx),
license key (delivery only on return of old license)
PC WORX PRO UPD 2985372 Version update for PRO (e.g., from 3.12 to 5.xx),
PC WORX PRO MSFC UPD 2985482 Version update for PRO-MSFC (e.g., from 3.12 to 5.xx),
All versions support all five IEC programming languages according to IEC 61131-3.
However, the license key is version-specific.
1-2 PHOENIX CONTACT 7127_en_02

Installing and Enabling the Software
2 Installing and Enabling the Software
2.1 Prior to Installation
Prior to installation, close all open Windows applications.

This PC WorX version can be installed parallel to an existing earlier version.
2.2 AUTOMATIONWORX Software Suite
PC WorX is part of the AUTOMATIONWORX software suite.

The AUTOMATIONWORX software suite includes the following programs:
– Config+
Easy configuration and startup for INTERBUS networks
– Diag+
User-friendly network diagnostics during startup and operation
– Diag+ NetScan
User-friendly monitoring of several INTERBUS networks
– PC WorX
Uniform IEC 61131 programming environment for all Phoenix Contact control systems
– AX OPC Server
Software used for data exchange between distributed INTERBUS networks and
visualization systems
– WebVisit
Tool for creating web pages for Phoenix Contact control systems
The desired programs can be selected individually or simultaneously for installation.
Diag+ should only be selected if you wish to use it independently of PC WorX. When
installing PC WorX, Diag+ is installed as part of PC WorX.
When one of the software suite programs is started for the first time, it runs in demo mode
with limited resources. A registration code is required to enable the full version. You will
receive the registration code when a full version of the relevant program is purchased.

PC WorX
2.3 Starting the Installation Program
• Insert the "AUTOMATIONWORX Software Suite" CD in your CD-ROM drive. The

installation program usually starts automatically after a few seconds.
• If this is not the case, start the "SETUP.EXE" file from the "[Drive]:\Setup\" directory on
the CD-ROM. This file calls the installation wizard, which guides you through the
installation process.
• Follow the instructions in the installation program.
The installation program generates all the directories required for operation and copies the
files for the selected programs.
• Following successful installation, restart your PC to activate the changes to the
configuration files. To do this, click "Finish" at the end of the installation process.
2.4 Starting PC WorX
• For installation using the default settings, start PC WorX via

"Start/All Programs/Phoenix Contact/AUTOMATIONWORX
Software Suite 2007 1.30/PC WorX".
When PC WorX is started for the first time, it runs in demo mode with limited resources.
If the upper limits for demo mode are exceeded, the following error messages are
generated when compiling:
– Too many inputs in I/O configuration (8 maximum, 65535 specified)! PC WorX running
with limited resources.
– Too many outputs in I/O configuration (8 maximum, 65535 specified)! PC WorX
running with limited resources.
– Resource file cannot be compiled!
Regardless of the bus configuration, these error messages always appear when compiling
for various control systems (e.g., ILC 370 ...) in demo mode as all system variables are
entered in the I/O configuration.
If you wish to switch from demo mode to the full version, enable your PC WorX license.
2.5 Enabling the PC WorX License
After starting PC WorX, proceed as follows to enable your license:

• Select the "Register..." command from the "?" menu.
• Enter your registration code.
• Confirm your entry with "OK".
Registration will come into effect when PC WorX is started again.

Helpful Information on PC WorX
3 Helpful Information on PC WorX

3.1 Online Help
More detailed information about the individual functions of PC WorX can be found in the
online help for the program. The entire help function can be called via "Help" in the menu
bar. Help for specific functions can be called via F1.
3.2 Changing the Language
When installing the software, the language in which PC WorX should be started can be
selected. The program language can be changed at any time.
• Select the "Tools/Options..." menu.
• Select the "General" tab.
• Select the language.
• Confirm your selection with "Apply" and "OK".
Figure 3-1 Changing the language setting
The selected language is activated the next time PC WorX is started.
• Close and restart the program.

PC WorX
In addition, texts previously created in one language can be exported, translated, and
imported into PC WorX in the new language.
• Open the "File/Export..." menu.
• Select the data you wish to export.
• Confirm your selection with "OK".
Figure 3-2 Exporting files from the project
Once the files have been translated:

• Open the "File/Import..." menu.
• Select the data you wish to import.
• Specify the path for the data to be imported.
• Confirm your selection with "Import".
3.3 PC WorX User Interface
The user interface consists of the following main components: menu bar, toolbars, main
window, and status bar. The contents of the main window depend on the workspace.
Menu bar
Toolbars
Main window
Status bar
Figure 3-3 User interface

3.4 Toolbars
The program contains several toolbars with different icons, which enables frequently used
operations to be executed quickly. Alternatively, these operating steps can be called via
menu items or predefined shortcuts.
By default, all the toolbars are shown. To display or hide a specific toolbar, use the
"Tools/Options" dialog box.
When the mouse pointer is placed over an icon (without clicking on it), a tool tip appears.
The tool tip displays the name of the current icon. In addition, a short function description
appears in the status bar. If tool tips are not displayed, this feature can be activated in the
"Tools/Options/Toolbars" dialog box.
Icons for Selecting the Workspace

The workspace can be changed via the icons in the toolbar:
Activate IEC programming workspace.
Activate bus configuration workspace.
Activate process data assignment workspace.
Activate project comparison workspace.
Which windows will actually be displayed depends on which windows have been toggled
on (see also "Windows in the Workspaces" on page 3-7). The last setting for each
workspace is saved when the program is closed and restored when it is started again.
Frequently Used Icons for Compiling and Debugging

Online modifications.
Make (compile project; corresponds to "Build/Make" in the menu bar).
Switch debug mode on/off.
Display project control dialog box.

PC WorX
3.5 Workspaces
PC WorX is divided into three workspaces:

– IEC programming
– Bus configuration
– Process data assignment
– Project comparison
The "View" menu or the corresponding icon in the toolbar can be used to switch between
the workspaces. Following initial installation the IEC programming workspace is the default
setting.
Figure 3-4 to Figure 3-6 show the default workspaces. Table 3-1 provides an overview of
the windows that can be usefully added to the default setting.
IEC Programming Workspace
Figure 3-4 IEC programming workspace

Bus Configuration Workspace
Figure 3-5 Bus configuration workspace
Process Data Assignment Workspace
Figure 3-6 Process data assignment workspace

PC WorX
Project Comparison Workspace
Figure 3-7 Project comparison workspace

3.5.1 Windows in the Workspaces
The windows that you wish to display can be defined at any time for each workspace.
Table 3-1 lists which windows are set by default when PC WorX is started for the first time
and which windows can be usefully added.
Table 3-1 Windows in the workspaces

Window IEC Programming Bus Configuration Process Data Project
Assignment Comparison
D A D A D A D A
Project Tree Window Yes Yes
Message Window Yes Yes Yes Yes Yes Yes Yes Yes
Edit Wizard Yes Yes
Cross References Window Yes
Watch Window Yes
Logic Analyzer Yes
Project Comparison Result Yes Yes
Window
Status Bar Yes Yes Yes Yes Yes Yes Yes Yes
Bus Structure Yes Yes
Device Details Yes Yes
Device Catalog Yes Yes1
Module Catalog Yes2
Process Data Assignment Yes Yes
3
Diag+ Yes
Connected Bus Yes
EXCEL Link Yes Yes4
LCD Yes Yes Yes
Ethernet Yes
Topology
INTERBUS Yes
Topology
Key:
1
When inserted manually
2
For PROFINET
3
For troubleshooting
4
When using Excel
D Default
A Useful addition

PC WorX
3.5.2 Toggling Windows On/Off and Docking/Undocking

Windows
Toggling on/off Each window can be toggled on/off via the "View" menu by selecting the corresponding
menu item.
For the windows recommended for the relevant workspace, please refer to "Workspaces"
on page 3-4.
Docking/undocking For each window, you can specify whether it is to be docked in the other windows or not.
There are various options for docking/undocking windows:
1. Permanent docking/undocking:
In title bar or the gray frame of the relevant window right-click with the mouse and
activate/deactivate the "Allow Docking" menu item.
Move an undocked window to the position where it is to be inserted in the desktop.
2. Temporary undocking:
Double-click on the gray window frame or the title bar of the window. The window is
then displayed as a "normal" window. Its size can be modified and it can be moved to
any position on the screen. In order to re-dock the window, i.e., to reinsert it in the
desktop, double-click on the title bar.

3.6 "Bus Structure" Window
The "Bus Structure" window is used to display and edit the bus topology.
3.6.1 Icons in the "Bus Structure" Window
3.6.1.1 Logical Device Functions

The individual device functions are identified in the "Bus Structure" window with logical
icons. The logical icons in the example bus topology have the following meaning:
Table 3-2 Icons for logical device functions (examples)
Icon Meaning
Control system resource
When creating the project using a template, the control system resource
is inserted below this icon.
When creating the project using the wizard, the control system resource
is inserted below this icon.
PROFINET IO controller
Insert all PROFINET IO devices below this icon in the lower level.
INTERBUS master
Below this icon, insert the INTERBUS devices that are directly
connected to the device that this icon refers to (local bus and remote
bus).
Inline
Below this icon, insert the Inline terminals that are connected to the Inline
bus coupler (local bus).
PROFINET IO devices: device proxy and modules
For PROFINET IO devices, the display is divided into the device proxy
(bus interface) and its modules.
The device proxy is indicated with "@".
The slot number is specified after the graphical representation of the
device proxy or modules (setting in context menu under "Edit Device
Representation").
The icons for the device proxy and modules are stored in the device
description file (e.g., FDCML, GSD). They may vary from manufacturer
to manufacturer.
PROFINET IO devices from Phoenix Contact
(example: ILB PN 24 DI16 DIO16-2TX)
Default icons, if none are stored in the device description file.
Figure 3-8 Device proxy and modules of a PROFINET IO device

PC WorX
For the example in Figure 3-8:

– Slot 0 is the device proxy for the PROFINET IO device
– Slot 1 is the DIO module for the PROFINET IO device
– Slot 2 is the DI module for the PROFINET IO device
Since the modules are fixed components of the PROFINET IO device, each one is marked
with a pin. These elements cannot be deleted or replaced.
PROFINET IO controller Overall structure with PROFINET IO

devices and INTERBUS devices
Figure 3-9 Example for the representation of devices in the bus configuration
3.6.1.2 Validity of Actions

When editing the bus configuration with the mouse, the mouse pointer indicates the validity
of your actions.
Table 3-3 Icons when editing the bus configuration

Icon Meaning
Insert at the same level
The device can only be inserted in/moved to the same level as existing
devices.
Insert in the lower level
The device can only be inserted in/moved to a lower level than existing
devices.
Replace
The device under the mouse pointer can be replaced by holding down the
<Ctrl> key and placing the mouse pointer on the existing device.
Not permitted
This icon indicates a mouse pointer position for which actions are not
permitted.

3.6.1.3 Display of Status Information

In the "Bus Structure" window some icons, which superimpose other graphics, are used to
display important status information.
Table 3-4 Icons for displaying status information
Icon Meaning
The device is hidden or the bus is deactivated.
Errors have occurred for the device.
Warnings have occurred for the device.
The pin indicates a module that is a fixed component of a device. This element
cannot be deleted or replaced.

PC WorX
3.6.2 Display in the "Bus Structure" Window
The display in the "Bus Structure" window can be adapted to your requirements.
• Switch to the bus configuration workspace.
• In the context menu, open a device via the "Edit Device Representation..." menu item.
Figure 3-10 "Edit Device Representation..." menu item
• Select the criteria that you would like to see in the display.
Figure 3-11 Device representations

Examples for different device representations:
Product designation DNS/PROFINET device name, separator,

and IP address
Figure 3-12 Examples for different device representations
The selected representation only affects the representation of a specific device group.
Groups include, for example:
– Control systems
– PROFINET IO devices
– INTERBUS devices
For example, the setting for PROFINET IO devices does not have any influence on the
representation of the ILC 370 PN (see Figure 3-12).

PC WorX
3.7 "EXCEL Link" Window
The Excel link enables:

– Data to be exported to an Excel file
– Data to be imported from an Excel file
Data that can be exported/imported includes:
– IEC variables
– IEC variable connections to signals
– Associated data and text
The data for all IEC variables can thus be edited in an Excel worksheet rather than in
various dialog boxes in the PC WorX user interface.
Since IEC variables are edited in this window, it is useful to toggle the window on in the
process data assignment workspace.
The following functions can be executed with the Excel link:
– Export existing IEC variables.
– Adjust and import the IEC variables available in an Excel file with a specified format
with the IEC variables available in a PC WorX project.
– Settings that specify how you wish to identify devices.
For more detailed information on the Excel link, please refer to the online help for
PC WorX.
To toggle the "EXCEL Link" window on, select the "View/EXCEL Link" menu item.
The Excel link help can be called by pressing F1 in the active window.

3.8 "Diag+" Window
Diag+ is a diagnostics tool for the seamless diagnostics of INTERBUS and PROFINET.
When installing PC WorX, Diag+ is installed automatically and is integrated in PC WorX. It
can be called from PC WorX via the "Diag+" window.
Diag+ can be started separately via "Start... All Programs... Phoenix Contact...
AUTOMATIONWORX Software Suite... Diag+ 2.xx".
An online connection to the control system is required in order to use Diag+.

For the following description, the example bus configuration for the PROFINET and
INTERBUS system has been selected. The IB IL 24 DI 4-ME Inline terminal has been
removed from the bus configuration to prompt an error.
• Start Diag+ via "View... Diag+".
Figure 3-13 Diag+ start screen
• Under "Communication Path", select the device with which you would like to establish
a connection.
The diagnostics represented depends on the communication path:
– PROFINET IO controller: INTERBUS Diagnostic and Diagnostic Archive
– PROFINET IO devices: INTERBUS Diagnostic

PC WorX
• Select, e.g., the ILC 370 PN 2TX-IB PROFINET IO controller as the communication
path.
Figure 3-14 Selecting the communication path
• Click on "Connect" to activate the communication path.

• At the top of the section under "View", select which general information is to be
represented.
View: Settings • At the bottom of the section under "View", select which information is to be
represented.
Figure 3-15 Example for Device Representation view
View: Diagnostic Archive All events that have occurred are displayed in list format. The display can be adapted to
your individual requirements via the filter options at the top of the section.
Figure 3-16 Diagnostic Archive

View: INTERBUS INTERBUS modules in an INTERBUS system can be diagnosed with Diag+ as usual.
Diagnostic Various information can be called via the different tabs.
To indicate the functions, the ILC 370 PN 2TX-IB communication path changes to
FL IL 24 BK-PN-PAC here.
• Disconnect the existing communication path by clicking on "Disconnect".
• Select FL IL 24 BK-PN-PAC as the new communication path and activate it.
• Under "View/Device Representation", select "INTERBUS Devices" as the device type.
• At the top of the section, select "INTERBUS Diagnostic" as the view.
Figure 3-17 INTERBUS Diagnostic: Bus Architecture (no error)
An error is simulated, the IB IL 24 DI 4-ME Inline terminal is disconnected.
Figure 3-18 INTERBUS Diagnostic: Bus Architecture (error)

PC WorX
• Switch to the "Solution" tab.

Here, information is provided about how to remove the error.
Figure 3-19 INTERBUS Diagnostic: Solution
• Remove the error (here: insert Inline terminal again).

For PROFINET, the entire system is automatically restarted by the PROFINET IO
controller.
If the bus is not restarted automatically, the "Action" tab can be used, for example, to
acknowledge errors, reset the controller board, and start the bus.
Figure 3-20 Diag+: Action

View: The Ethernet topology can also be displayed in Diag+.

Ethernet Topology
Please note that the Ethernet topology can only be displayed if it has been previously
generated in PC WorX under "View/Ethernet Topology".
3.9 Visualization
The data generated in PC WorX can be used in other programs, e.g., to visualize
processes (e.g., Visu+, WebVisit).
The AX OPC Server is provided in order to enable the use of data in OPC clients.
See also "AX OPC Server and WebVisit" on page C-1.

PC WorX

Sequence for Creating a Project
4 Sequence for Creating a Project

This section describes the general procedure for creating a project.
The aim of this section is to provide an overview of the various options available for
achieving a particular objective and to explain some points in detail that are only referred
to briefly in later sections.
The aim is not to create a comprehensive project or to have an operational project at the
end of the section. If you create a project using the description in this section, please note
that you must enter the relevant versions for your project.
If you have little or no experience in creating projects, please proceed as described in
Sections 5, 6 or 7. These sections provide a brief description of a special project creation.
The various sections focus on the following topics:
– Section 5, "Example Project for an INTERBUS System"
– Section 6, "Example Project for a System Consisting of PROFINET IO and
INTERBUS"
– Section 7, "Example Project for a Simulation With Processor Type "IPC" Control
Systems"
The sections are labeled. The symbol next to the heading indicates the applicable
versions:
IB INTERBUS project
PN PROFINET project
SIM Simulation project

PC WorX
IB PN SIM 4.1 Sequence for Creating a Project
General
OFFLINE ONLINE
Start
IB PN SIM
IB PN SIM IB PN
Create new project No Yes

INTERBUS devices
Simulation? inserted?
IB PN SIM
Yes No
Specify project information SIM IB PN
Set communication path Read

IB PN SIM
INTERBUS
Check/modify IP settings
for controller A
IB PN SIM IB PN
Yes IB PN Yes
System Program created?
installed? Assign IP address Process data
for controller assigned?
No No
PN IB PN IB PN
Insert IO devices Set communication path Create program
PN IB PN
PN
Check/modify PROFINET
Yes Assign process data
settings for IO devices IO devices
inserted?
IB PN SIM
No A
Manually insert PN IB PN SIM
INTERBUS devices
Read IO devices Compile and send project,
IB PN SIM and perform cold restart
Create program PN
IB PN SIM
settings Operation (end)
IB PN SIM
Assign process data
PN
7127B018
Assign PROFINET device
name / IP settings
Figure 4-1 Sequence for creating a project

IB PN SIM 4.2 Creating a New Project
• Select the "New Project..." command from the "File" menu to create a new project
using a template.
The tree structure and the selection of the control system are now prepared.
• Select the control system.
For some control systems, there are several templates depending on the hardware
and firmware version of the control system used.
Figure 4-2 Project templates (here: "ILC 350 PN Rev. > 01/4.6F/1.41")
"List" view has been selected in Figure 4-2. The view can be switched via the
icons.
The ">" character in the selection stands for "later than" and not "greater than" in a
mathematical sense. The specified version is the first supported version.
If a control system is inserted in a project without a template, depending on the hardware

and firmware version, the processor type of the control system used must be specified.
A detailed table that lists the processor type and scope of functions according to the
control system used can be found in "Overview of Phoenix Contact Control Systems" on
page D-1.

PC WorX
• Select the "File... Save Project As/Zip Project As..." command.

• Enter a project name and save the project.
Figure 4-3 "Save/Zip project as" window

IB PN SIM 4.3 Specifying Project Information

After creating a new project, the project information is displayed in the bus configuration
workspace.
• Adapt the project information to your project.
Figure 4-4 Project information after creating a new project
During project creation, PC WorX automatically assigns an IP address area for a local
network (area from 192.168.0.2 to 192.168.0.254). If you would like to use another
address area (e.g., a global network), adapt the start and end address on the project
node (here: Quickstart_PN) to your application.
Make sure that all the components are in the same subnetwork.
For information on the IP parameters to be used within your system, please contact your
system administrator.
If the start address of the new address area to be entered is higher than the previous end
address, please modify the end address first.
When inserting PROFINET IO controllers and PROFINET IO devices, PC WorX

automatically assigns IP parameters that are within the specified area. If later on you
manually assign IP parameters that are outside the defined area, they will not be accepted.
If you are using a default gateway:
• Assign the address for the default gateway under "Default Gateway" in the "Device
Details" window.
This address must be within the specified IP address area. If the default gateway is entered
at the start of the project, it will be used automatically for all subsequent PROFINET IO
devices that are inserted (see also "Default Gateway" on page 4-11).

PC WorX
PN • Assign the name suffix for the PROFINET device name (here: quickstart.de) in the
"Device Details" window under "Domain Postfix".
The following characters are permitted for the "Domain Postfix":
Lowercase letters without umlauts a to z

As separators: Period .
Uppercase letters without umlauts are permitted, however, they will be converted to
lowercase letters internally. The entry is therefore not case sensitive.
If the "Domain Postfix" is entered at the start of the project, it will be used automatically for
all subsequent PROFINET IO devices that are inserted in the PROFINET device name
(see also "DNS/PROFINET Device Name" on page 4-11).
If the PROFINET IO devices are read, the PROFINET device name for the devices is
also read. In this case, the Domain Postfix may differ. Adapt it accordingly.
Figure 4-5 Assigning the Domain Postfix

PN 4.4 Preparing the PC for Communication
• In the "Tools/PROFINET Configuration..." menu in PC WorX select the network board

for your computer that is to be used for communication.
Figure 4-6 Selecting the network board
• Make sure that your PC has been assigned IP parameters that can be used to
communicate with the connected network.
If, e.g., when using PROFINET, you are working with a local network that is set by
default (192.168.0.2 to 192.168.0.254), the IP parameters for the PC must be
192.168.0.1, with subnet mask 255.255.255.0.

PC WorX
IB PN SIM 4.5 Checking/Modifying IP Settings for the Controller
The IP settings for the controller are made when the project is created.
If any modifications are made to the project information that affect the IP settings for the
controller, a warning is displayed. However, the modification is not implemented
automatically. When a new project is created, the default settings are specified as the IP
settings.
Adapt these settings, if necessary.

• Select the controller node.
• In the "Device Details" window, switch to the "IP Settings" tab.
• Check the IP settings and modify, if necessary.
Figure 4-7 IP settings
• If an IP address has still not been assigned, assign one according to "Assigning the IP
Address for the Controller" on page 4-24.
The IP parameters that are assigned here for the controller are also implemented as the
IP parameters for the communication path via TCP/IP.
IB PN SIM 4.6 Decision: Working Online or Offline
If your system is installed, you can work online. In this case, skip this section and proceed
to Section 4.17, "Setting the Communication Path".
If your system is not installed or you wish to work offline, proceed as follows:
– For PROFINET, see Section 4.7, "Inserting PROFINET IO Devices".
– For INTERBUS or Simulation, see Section 4.9, "Manually Inserting INTERBUS
Devices".

PN 4.7 Inserting PROFINET IO Devices
• Make sure you are in the bus configuration workspace.

Insert the PROFINET IO devices below the PROFINET IO controller node.
• If the device catalog is hidden, show it by selecting the "View/Device Catalog" menu.
• Open the " Phoenix Contact" device catalog.
For example, the specified folders contain the following PROFINET IO devices:
PROFINET IO Device Folder
FL IL 24 BK-PN-PAC FL - Gateway
ILB PN 24 DI16 DIO16-2TX ILB - I/O digital
FL PN/IBS PROFINET IO Proxy - INTERBUS Proxy
• Select the first PROFINET IO device (here: FL IL 24 BK-PN-PAC).
Figure 4-8 Selecting the PROFINET IO device
• Hold down the left mouse button and move the first PROFINET IO device in the "Bus
Structure" window to the right of the PROFINET IO controller icon until the "Insert in
the lower level" icon appears (see page 3-10).
• Move all other PROFINET IO devices to below the preceding PROFINET IO device
until the "Insert at the same level" icon appears (see page 3-10).
Figure 4-9 illustrates the bus configuration with inserted PROFINET IO devices.

PC WorX
Figure 4-9 PROFINET IO devices inserted
PN 4.8 Checking/Modifying the PROFINET Settings for

PROFINET IO Devices
When inserting each PROFINET IO device, the PROFINET settings are assigned
automatically according to the entries defined in the project information.
The PROFINET settings can be checked and modified via the "PROFINET Settings" tab.

• In the "Bus Structure" window select the PROFINET IO device.
• Under "Device Details" select the "PROFINET Settings" tab.
• Check the PROFINET settings and modify, if necessary.
Figure 4-10 PROFINETsettings for the device ILB PN 24 DI16 DIO16-2TX

The PROFINET settings comprise:
DNS/PROFINET This name is the unique identification for the PROFINET IO device in the network. It must
Device Name be known to the PROFINET IO device before it can be used in the network.
PC WorX automatically ensures that each device is assigned a PROFINET device name
that is unique throughout the entire project. The "Domain Postfix" that was set on the
project node is attached to this name (here: quickstart.de).
The PROFINET device name can be freely modified.
The following characters are permitted for the PROFINET device name:
Lowercase letters without umlauts a to z

Numbers 0 through 9
Hyphen -
If the naming conventions have not been observed, an error message is output in the
message window and the name is rejected.
Uppercase letters without umlauts are permitted, however, they will be converted to
lowercase letters internally. The entry is therefore not case sensitive.
The procedure that makes the device name known to the PROFINET IO device is either
called "assigning device names" or "device naming". This procedure is described under
"Transmitting PROFINET Device Names and IP Settings to PROFINET IO Devices" on
page 4-37.
IP Address During operation, the device can be accessed via the IP address. PC WorX selects the
address from the area that is set on the project node.
If the area for the IP addresses is later modified in the project node, you will also have to
adapt the addresses of the PROFINET IO devices accordingly.
Specify the IP address according to "Transmitting PROFINET Device Names and

IP Settings to PROFINET IO Devices" on page 4-37.
Subnetmask The subnet mask that was specified on the project node is assigned to each PROFINET IO
device as the default subnet mask. It can be modified specifically for each individual
device.
Default Gateway If a default gateway is used, enter its IP address here. The default gateway specified on
the project node is automatically assigned to each PROFINET IO device.
IP Address, Subnet Mask, and Default Gateway represent the IP parameters for a
device.

PC WorX
Reduction ratio input/ The time in which the inputs/outputs of the PROFINET IO device are updated. It can be set
Reduction ratio output individually for each PROFINET IO device for both data directions.
The update time directly affects the number of PROFINET IO devices that can be operated
on a PROFINET IO controller. The default setting displayed in PC WorX is the value that
was stored in the FDCML file for the corresponding PROFINET IO device. If this setting
exceeds the performance level of the PROFINET IO controller, a corresponding error
message appears when translating the project. In this case, select a longer update time for
certain devices.
Watchdog Sensitivity (ms) The watchdog sensitivity (monitoring time) can be set automatically by PC WorX according
to the update times. The monitoring time specifies how long PROFINET IO devices may
receive no valid PROFINET telegrams before substitute values are enabled at the outputs.
This setting can affect the "noise immunity" of the network.
Please note that excessively high settings can result in errors in the process as the
PROFINET IO device "freezes" the last output value until the error is detected.
IB PN SIM 4.9 Manually Inserting INTERBUS Devices
IB PN SIM 4.9.1 Manually Inserting INTERBUS Devices - General
If the bus configuration is not actually available yet or you wish to create the configuration
offline, the bus configuration can be created manually.
• Select a point in the "Bus Structure" window where a device is to be inserted
(e.g., INTERBUS node for the control system).
• In the device catalog, open the product range for the inserted device (e.g., IL for Inline)
under " Phoenix Contact".
• Under the product range, open the product group (e.g., I/O analog).
• Select the device to be inserted (e.g., IB IL AO 1/SF).

Figure 4-11 Selecting the device
• Hold down the mouse button and drag the selected device to the insertion point.
Please refer to the information about the mouse pointer in "Icons in the "Bus Structure"
Window" on page 3-9.
Figure 4-12 Device inserted (here: IB IL AO 1/SF)
• Insert all the other devices.

PC WorX
Example Configurations
Example 1: Simple bus configuration
RFC 430
ETH-IB
IBS IL 24 IB IL 24 IB IL 24
BK-T/U DO 8 DI 8
IBS IL 24 IB IL 24 IB IL
BK-T/U DI 16 AI 2/SF
7127A010
Figure 4-13 Simple bus configuration
Folders in the device catalog where the listed devices can be found:
RFC 430 ETH-IB RFC4xx - PLC

IBS IL 24 BK-T/U IL - Bus coupler
IB IL 24 D.... IL - I/O digital
IB IL A.... IL - I/O analog
Example 2: Bus configuration with branch terminals
0.0 1.0 2.0 2.1 2.2
ILC 350 IBS IL 24 IBS IL 24 IB IL 24 IB IL 24

ETH RB-T RB-T DO 8 DI 8
3.0
FLS IB M12
DIO 8/8
4.0 4.1 4.2
IBS IL 24 IB IL 24 IB IL
BK-T/U DO 2 AO 1/SF
5.0
ILB IB 24
DI 32
7127A011
Figure 4-14 Bus configuration with branch terminals

Example 3: Bus configuration with bus coupler for connecting a remote bus branch
0.0 1.0 1.2 1.3
ILC 350 IBS IL 24 IB IL 24 IB IL 24

ETH RB-LK DO 8 DI 8
2.0
(1) 3.0 3.1 3.2
IBS IL 24 BK RB-LK IB IL 24 IB IL 24
(2) DI 4 DI 2
4.0
FLS IB M12
DIO 8/8
5.0 5.1 5.2
IBS ST 24 IBS ST 24 IBS ST 24

BK-LK DO 16/3 DI 16/4
7127A012
Figure 4-15 Bus configuration with branch terminals
Folders in the device catalog where the devices listed in Figure 4-14 and Figure 4-15 can
be found:
ILC 350 ETH ILC3xx - PLC

IBS IL 24 RB-T; IBS IL 24 RB-LK IL - Bus coupler
IBS IL 24 BK RB-LK IL - Bus coupler
IB IL 24 D.... IL - I/O digital
IB IL A.... IL - I/O analog
FLS IB M12 DIO 8/8 FLS - I/O digital
ILB IB 24 DI 32 ILB - I/O digital
IBS ST 24 BK-LK ST - Bus coupler
IBS ST 24 D... ST - I/O digital

PC WorX
PN 4.9.2 Inserting INTERBUS Devices Below an INTERBUS Proxy
• Insert the required INTERBUS devices from the device catalog at the "INTERBUS"
node of the INTERBUS proxy (e.g., FL PN/IBS).
Figure 4-16 FLM modules inserted below an INTERBUS proxy
PN 4.9.3 Inserting Inline Terminals Below a PROFINET IO Bus

Coupler
• Insert the required Inline terminals from the device catalog at the "Inline" node of the
PROFINET IO bus coupler (e.g., FL IL 24 BK-PN-PAC).
Figure 4-17 Inline terminals inserted below a PROFINET IO bus coupler
PN 4.9.4 INTERBUS Devices Below the PROFINET IO Controller
Manually insert the INTERBUS modules connected to the PROFINET IO controller in the
same way as described above.
• Insert the required INTERBUS modules from the device catalog at the INTERBUS
node of the PROFINET IO controller (e.g., ILC 370 PN 2TX-IB).

IB PN SIM 4.10 Compiling After Completing the Bus Topology
At this point you can compile your project in order to detect any errors that may have
occurred.
Compiling a project • When compiling a project for the first time, select the "Rebuild Project" command from
the "Build" menu. For subsequent compiling processes, the "Make" command in the
"Build" menu can also be used (see also "Compiling (Additional Information)" on
page 4-18).
Figure 4-18 Compiling a project
• If errors occur when compiling, remove the errors and repeat the compiling process
until it is completed successfully. Error messages must be removed. Warning
messages do not have to be removed.
If you are compiling the project but have not yet programmed anything, you will receive
the "Empty worksheet" warning message. This does not affect the next step. You can
ignore it.
The results of the compiling process are displayed in the message window together with
details of the number of errors and warnings.
Compiling and Sending a Project: Special Notes for PROFINET

When translating the control project, the PROFINET IO configuration is generated
automatically. This is also displayed in the message window.

PC WorX
Compiling (Additional Information)

There are two options for compiling:
1 Build/Make
2 Build/Rebuild Project
Rebuild Project Use this command to compile an entire project for the first time or after modifying a user
library.
"Rebuild Project" compiles and links all worksheets. Errors and warnings that are
discovered by the compiler are logged in the message window. After the syntax has been
checked successfully, the system automatically generates the IEC code and the special
PLC code. Finally, the project can be sent to the PLC.
The "Rebuild Project" command should only be used if errors occurred when compiling
with "Make" or your project was unpacked without frontend.
Make The "Make" command is the standard mode for compiling. Use this command after editing
and completing your project.
When the "Make" menu item is executed, all modified worksheets are compiled/linked and
the modified PLC code is generated.
This command can be executed from the menu bar via "Build/Make", with the "Make" icon
in the toolbar or using the shortcut <F9>.
Modified worksheets in the project tree are identified by an asterisk that appears after the
worksheet name.
Both After the compiler has been started, the message window appears automatically if it was
closed before. This window indicates the steps the compiler is currently executing. In
addition, errors, warnings, and additional information about the process are logged here.
Once the compiling process has been completed successfully, i.e., no errors have been
reported, the modified project can be sent to the PLC.
IB PN SIM 4.11 Creating the Program
• Create the program.

To program the example program, proceed as described in "Example Program" on
page 8-1.
It is now assumed that you have created the program. If you skip this point, this may
result in deviations.

IB PN SIM 4.12 Compiling After Creating the Program
occurred.
• Select the "Build/Make" command.
IB PN SIM 4.13 Generating Variables and Assigning Process Data
This section provides a general description for generating variables and assigning process
data. Process data assignment for the example bus configuration is explained in later
sections.
IB PN SIM 4.13.1 Generating Variables
Usually, variables are either generated during program creation or they are created
individually. When all the previous steps for creating a project including programming have
been performed, variables have already been created.
Variables can also be generated automatically for the process data of all devices
(PROFINET IO and INTERBUS). The variable names are assigned automatically
according to the following pattern:
<I or Q>_<PROFINET device name>_<IBS segment>_<IBS position>_<PD name>
Key:
I or Q I = Input; Q = Output
IBS INTERBUS
PD name Name of the process data item
For direct inputs/outputs or PROFINET IO status data, no INTERBUS data is required.
To generate variables, proceed as follows:
• Switch to the process data assignment workspace.

• Select the control system in the top right window. The standard configuration is
displayed in the top left window, "Symbols/Variables".
• In the top left window, select the resource or program (in Figure 4-21: resource
"STD_RES: ILC370PN").
Please observe the following:

– If the resource has been selected, global variables are generated/displayed that can
be used in all POUs of the project (VAR_GLOBAL).
– If the program (POU) has been selected, global variables are generated/displayed
that can be used in all POUs of the project (VAR_GLOBAL_PG).
(POU = Program Organization Unit; see online help for PC WorX or IEC 61131-3)
• In the top right window, select the device for which you would like to link the process
data to variables (e.g., IB IL AO 1/SF in Figure 4-19).

PC WorX
• Select the process data item for which you would like to generate a variable (~AO 16
in Figure 4-19).
• In the context menu for the process data item, select the "Create Variable" menu item.
Figure 4-19 Variable generated for process data item "~AO1"
Figure 4-19 shows examples of automatically generated variables.
Figure 4-20 Examples of generated variables
IB PN SIM 4.13.2 Assigning Process Data
Process data and control variables are assigned in the process data assignment
workspace.
The assignment is seamless for INTERBUS and PROFINET IO.
Please observe the following:

– If the resource has been selected, global variables are generated/displayed that can
be used in all POUs of the project (VAR_GLOBAL).
– If the program (POU) has been selected, global variables are generated/displayed
that can be used in all POUs of the project (VAR_GLOBAL_PG).
(POU = Program Organization Unit; see online help for PC WorX or IEC 61131-3)

• Switch to the process data assignment workspace to assign the variables to the
process data.
• Select the control system in the top right window. The standard configuration is then
• In the top left window, "Symbols/Variables", select the standard resource (STD_RES
RFC450ET in Figure 4-21).
data to variables (e.g., IB IL 24 DO 8 in Figure 4-21).
• Select the process data item to be linked (1.1.1 in Figure 4-21).
• Using drag & drop, link the selected variable with one of the variables (OUT1 in
Figure 4-21) on the left-hand side.
In the bottom left window, the assignment between variables and process data is
displayed.
Figure 4-21 Process data item 1.1.1 assigned to variable OUT1
• Repeat this procedure for all inputs to be evaluated and for all outputs to be controlled.
PN Please note for a PROFINET IO device with inputs and outputs that this is represented with
its modules.
Figure 4-22 Representation of a PROFINET IO device with its modules

PC WorX
• In this case, select the module where the required inputs or outputs are located.
Figure 4-23 Assigning process data for a PROFINET IO device
The result of the process data assignment is displayed in the following figure.
Figure 4-24 All used process data assigned to variables
System variables (e.g., ONBOARD_INPUT_BIT10) are not displayed in this process

data view.

SIM
4.14 Setting the Communication Path: Simulation
This function is only available for processor type "IPC" controllers. For a list of controllers
that support this function, please refer to Appendix D "Overview of Phoenix Contact
Control Systems".
This item can be used to select a simulation environment and thus create a bus and
develop and check a program without the hardware having to be available.
• Switch to the bus configuration workspace to set the communication path between the
programming PC with PC WorX and the control system.
• In the "Bus Structure" window select the node for the control system.
• Select the "Communication" tab in the "Device Details" window.
• Select the "Simulation" interface type.
• Activate the simulation environment by clicking "Apply".
Figure 4-25 "Simulation" communication path

PC WorX
IB PN 4.15 Switching to Working With the System (Online)
Apart from during simulation, the following work can only be carried out if a system has
been installed and a connection has been established between your PC with PC WorX and
the controller.
IB PN 4.16 Assigning the IP Address for the Controller
An IP address must first be assigned to a controller that communicates via Ethernet in

order to enable communication.
For some controllers (e.g., RFC 430 ETH-IB), the IP address can only be set via the
diagnostic display or a special firmware service (see user manual for the controller).
For a number of controllers (e.g., ILC 350 ..., ILC 370 ...) BootP is activated by default upon
delivery for assigning the IP address via Ethernet. In this case, when setting the IP address
for the first time a BootP server can be used.
However, the first IP address can also be set manually using the PC WorX software via the
serial interface. The IP address can be changed later via the serial connection or Ethernet
using the PC WorX software. In the following, address assignment via PC WorX is
described.
After assigning the IP parameters, PC WorX automatically creates a link via TCP/IP as
a communication path to the controller.
4.16.1 Address Assignment via the PC WorX BootP Server
• Establish an Ethernet connection between your PC and the controller.

• In the menu bar, select the
"Extras... BootP/SNMP/TFTP Configuration..." menu.
Figure 4-26 Extras... BootP/SNMP/TFTP Configuration...
• Activate the "BootP server active" checkbox.

• Select the controller node (e.g., "ILC 370 PN 2TX-IB").
• Select the "IP Settings" tab in the "Device Details" window.
• Enter the controller MAC address, which can be found on a label on the device and
starts with 00.A0.45.

Figure 4-27 Entering the MAC address
• Reset the controller.

The controller is temporarily assigned the IP address, which is specified in the project for
the controller.
• Select the "Extended Settings" tab in the "Device Details" window.
The specified IP parameters are displayed under "Manual definition of the
TCP/IP settings".
Figure 4-28 IP address of the PROFINET IO controller
• Confirm the displayed IP parameters or your modifications via "Send".

The IP address is now permanently stored on the controller memory card.

PC WorX
4.16.2 Address Assignment With PC WorX via the Serial Interface
If the IP parameters were assigned using the BootP server, this section can be skipped.
• Establish a serial connection between your PC and the controller.

• Set the communication path (here: serial interface COM1).
• Check the specified communication path by clicking on "Test".
The communication path has been tested successfully if a green status indicator
appears in the window. If a red status indicator appears, check the communication
path and change it, if necessary.
• If the PROFINET IO controller had an IP address, the IP address of the PROFINET IO
controller read via the serial connection is displayed under "Extended Settings".
Figure 4-29 The read IP address of the PROFINET IO controller
• If you would like to change the network settings, specify the new settings.
• Confirm the display or your entry via "Send".
• Reset the control system in the "Activate Network Settings" area via "Reset Control
System".
The controller needs some time before it is ready to operate again. It indicates that it is
ready via the RUN LED that is either permanently ON or flashing cyclically.

IB PN
4.17 Setting the Communication Path
For a control system that supports Ethernet (e.g., ILC 3xx ETH, ILC 350 PN,
ILC 370 PN 2TX-IB), the communication path is automatically set to "Ethernet" by
default with the IP parameters of the controller specified under IP Settings. If you would
like to send your project to the control system via this Ethernet connection, the
communication path does not have to be set.
Since both the INTERBUS and PROFINET project have been created using the example
of an ILC 370 PN 2TX-IB, the communication path setting displayed applies to this
controller.
• Switch to the bus configuration workspace to set the communication path between the
programming PC with PC WorX and the control system.
• In the "Bus Structure" window select the node for the control system.
• Select the communication path to the control system.
Figure 4-30 Setting the communication path
• Depending on the communication path, proceed as described in

Section 4.17.1, "Communication via the Serial Port" or
Section 4.17.2, "Communication via Ethernet".
BootP is activated by default upon delivery for assigning IP parameters with an Inline
Controller via Ethernet.
If you would like to change this setting, select the serial port as the communication path
and specify the IP parameters in the "Extended Settings" dialog box. This setting is
activated following a control system reset.

PC WorX
4.17.1 Communication via the Serial Port

IB PN
The controller must be connected to the programming PC using the connecting cable.
Ordering data:
Connecting cable for connecting the controller to a PC (V.24 (RS-232)) for PC WorX,
length 3 m (Order Designation PRG CAB MINI DIN, Order No. 2730611).
• In the in the "Device Details" window, select the "Serial Port" interface type in the
"Communication" tab.
• Select the interface (e.g., COM1).
• Check the specified communication path by clicking on "Test".
path and change it, if necessary.
• Save your settings in the project via "Apply".
Figure 4-31 "Serial Port" communication path

IB PN 4.17.2 Communication via Ethernet
An Ethernet connection to the controller is required for communication via Ethernet.

Furthermore, the IP address must also be set in the controller.
• In the in the "Device Details" window, select the "Ethernet" interface type in the
"Communication" tab.
• Enter the IP address set in the Inline Controller in the "IP Address" field or select it from
the menu.
Figure 4-32 "Ethernet" communication path
• Check the specified communication path and therefore the IP address by clicking "Test".
path and the settings and change, if necessary.
If a red status indicator appears, an IP address may not have been assigned or the IP
address needs to be changed. To assign and change the TCP/IP settings, please
proceed as described in "Assigning the IP Address for the Controller" on page 4-24
(general), "Assigning the IP Address for the Controller" on page 5-5 (for INTERBUS)
or "Assigning the IP Address for the PROFINET IO Controller" on page 6-7 (for
PROFINET).
• Save your settings in the project via "Apply".
The Inline Controller can be accessed via a network using the Ethernet interface and the
TCP/IP protocol. Please note that with all networked devices/computers, there is a risk
that third parties may access the Inline Controller or the PC WorX computer and make
changes, either intentionally or unintentionally. Prevent unauthorized access to the Inline
Controller and your PC.

PC WorX
PN 4.18 Reading and Importing PROFINET IO Devices
If you have inserted the PROFINET IO devices manually, skip this section.
4.18.1 Reading PROFINET IO Devices

• In the "Bus Structure" window select the PROFINET node for the control system.
• Open the context menu and select the "Read PROFINET..." menu item.
Figure 4-33 Reading PROFINET
All the connected PROFINET IO devices are displayed. When reading, the device name
and the IP parameters are read for each device - provided it is present.
• Select the devices that are to be included in your project.
If your PROFINET IO controller already contains a project, another name can be

specified for the controller in the "Read PROFINET" window than the one assigned in the
current project. If you are sure you are communicating with the right controller this will
not have any adverse effects. The PROFINET IO devices displayed are connected to the
controller - regardless of its name. The current name is also transmitted when the current
project is sent to the controller.

Figure 4-34 Connected PROFINET IO devices selected for the project,

PROFINET device names and IP addresses are already present
Figure 4-35 Connected PROFINET IO devices selected for the project,

without PROFINET device names and IP addresses

PC WorX
4.18.2 Importing PROFINET IO Devices Into the Project
• Include the selected PROFINET IO devices in your project by clicking on "Insert".
4.18.3 Naming PROFINET IO Devices Without a PROFINET Device

Name
If a PROFINET device name does not yet exist for a device, a name should be assigned
at this point.
Figure 4-36 Naming a device
• Activate the "Name Device" checkbox.

• Check the displayed PROFINET device name (see also "DNS/PROFINET Device
Name" on page 4-11).
• Assign the name to the relevant device.
• Confirm the display or your entry with OK.
If you do not wish to assign a name at this point, deactivate the "Name Device" checkbox.
A name will have to be assigned later to the relevant device (here FL IL 24 BK-PN-PAC).

Figure 4-37 Devices named
• Close the "Read PROFINET" window by clicking on "Close".
4.18.4 Bus Configuration With Read PROFINET IO Devices
The PROFINET structure is displayed in the "Bus Structure" window.
Figure 4-38 Bus configuration with read PROFINET IO devices

PC WorX
The settings can also be checked in the "Read PROFINET" window. All PROFINET IO
devices should now have a PROFINET device name. The IP parameters are assigned
later.
4.18.5 Subsequent Naming of a PROFINET IO Device
If a device is displayed in the list without a device name, assign the PROFINET device
name to this device.
• Select the device in the bus configuration.
• In the "Device Details" window, switch to the "PROFINET Stationnames" tab.
• Select the device with no name.
Figure 4-39 Assigning the PROFINET device name
• Click on "Assign Name".

The updated list contains the PROFINET IO devices together with their PROFINET device
names.

Figure 4-40 Example: All devices with PROFINET device names

PC WorX
PN 4.19 Checking/Modifying the PROFINET Settings for

PROFINET IO Devices
If you have made the PROFINET settings for the PROFINET IO devices offline after
inserting the PROFINET IO devices, skip this section.
When reading, the PROFINET settings of the relevant PROFINET IO devices are included
with default values. Check these settings and modify, if necessary.

Figure 4-41 PROFINET settings for ILB PN 24 DI16 DIO16-2TX
The individual setting options are described in "Checking/Modifying the PROFINET

Settings for PROFINET IO Devices" on page 4-10.

PN 4.20 Transmitting PROFINET Device Names and

IP Settings to PROFINET IO Devices
Before a PROFINET IO device is operated in a PROFINET IO network, the PROFINET

device name and IP address configured in PC WorX must also be made known to the
device itself.
• Make sure that the PROFINET IO controller can establish communication with the
PROFINET IO devices.
• Compile the project, send it to the control system, and perform a cold restart. Proceed
as described in "Compiling and Sending a Project, and Performing a Cold Restart" on
page 4-42.
During startup, the PROFINET controller automatically assigns the IP settings and device
parameterizations specified in the project to the PROFINET IO devices.
• To check the assignment of device names and IP settings, select the "PROFINET
Stationnames" tab in the "Device Details" window.
names and the IP parameters.
Figure 4-42 All devices with PROFINET device names and IP addresses
When the tab is selected, the list is updated. If you would like to update the list again later,
click on "Refresh".
In order to limit the search results, different options are available:
No constraints All devices that are available in the network are listed.
Unnamed All those devices that do not yet have a PROFINET device
name are listed.
Not in project All those devices that are not included in the project are
listed.
The BF LED is now OFF on all PROFINET IO devices.

The PROFINET network is running.
For additional information about assigning PROFINET device names and IP addresses,
please also refer to "Additional Information" on page 6-15.

PC WorX
IB PN 4.21 Reading INTERBUS
If you have inserted the INTERBUS devices manually, skip this section.
The bus configuration must actually be available and power must be supplied to the
modules.
• Select the "Connected Bus" command from the "View" menu to read the connected
INTERBUS system.
Figure 4-43 "View... Connected Bus" command
• Select the control system in the "Connected Bus" window.
For PROFINET, the PROFINET IO devices can also be selected as the control system
(FL IL 24 BK-PN-PAC in Figure 4-44).
Figure 4-44 Selecting the control system

This activates the "online" operating state and the control system reads the connected
INTERBUS configuration.
Once the control system has read the connected INTERBUS system, the INTERBUS
devices must be accepted in the project.
• Select the control system in the "Connected Bus" window.
• Open the context menu and select the "Import to Project... With Device Description"
command.
Figure 4-45 "Connected Bus" window
The "Select Device" window lists the modules, whose device description corresponds to
that of the connected devices.
Figure 4-46 "Select Device" window
• Select the device that is actually connected in the INTERBUS system, and repeat this
step until all the devices are linked to their device description.

PC WorX
• Disconnect the link to the control system by selecting "Offline" under "Selected Control
System" in the "Connected Bus" window.
Figure 4-47 "Connected Bus" window
PN Please Note for PROFINET

The process for reading INTERBUS modules that are connected to a PROFINET IO
controller or a PROFINET IO device is essentially the same.
PROFINET IO controller After the communication path to the PROFINET IO controller has been set, the INTERBUS
devices connected to the controller can be read.
PROFINET IO device After device names and IP parameters for the PROFINET IO devices have been assigned,
the INTERBUS devices connected to the PROFINET IO devices can be read.
• Select all the "control systems" that are connected to the INTERBUS devices. These
include the Inline Controller as well as all the PROFINET IO devices displayed in the
"Connected Bus" window.
• Read the INTERBUS devices as described above.
The product designation or the station name is displayed under "Selected Control
System". If several devices of the same type are used in a project, first assign the
devices a station name. This enables the unique identification of the devices.

IB PN 4.22 Compiling After Reading the Bus Topology
occurred.
IB PN 4.23 Creating the Program
If the program has been created offline, skip this section.

page 8-1.
IB PN 4.24 Compiling After Creating the Program
occurred.

PC WorX
IB PN 4.25 Assigning Process Data
If the process data has been assigned offline, skip this section.
To assign the process data, proceed as described in "Generating Variables and Assigning
Process Data" on page 4-19.
IB PN SIM 4.26 Compiling and Sending a Project, and Performing

a Cold Restart
IB PN SIM 4.26.1 Compiling a Project
• To compile a project, proceed as described in "Compiling After Completing the Bus

Topology" on page 4-17.
IB PN SIM 4.26.2 Sending a Project
When working online, the project is written to the main memory of the control system.
When working in simulation mode, the project is written to the simulated main memory of
the control system.
• Open the project control dialog box.
If only the "Close" button is enabled in the project control dialog box that opens, there is
no valid connection to the control system. In this case, check the communication path.
Figure 4-48 Project control dialog box
• Click on "Download".

Another dialog box opens. There are various options for sending the project to the control
system or the simulated control system.
1. Click on "Download" in the "Project" area.
2. Click on "Download" in the "Bootproject" area.
3. Activate the "Include Bootproject" checkbox in the "Project" area and click on
"Download" in this area.
In the first option, the project is sent. However, it is not loaded automatically when booting
the control system.
For option 2 and 3, the project is written as a boot project to the parameterization memory
of the control system and is loaded automatically after the control system has been booted.
Option 3 is shown in Figure 4-49.
• Activate the "Include Bootproject" checkbox in the "Project" area and click on
"Download" in this area.
Figure 4-49 "Download" dialog box
For control systems that support the "Download Changes" function, the "Download" dialog
box appears as shown in Figure 4-50. If the "Download Changes" function is used, activate
the "Ensure realtime for Download Changes" and "Include Bootproject" checkboxes.
Figure 4-50 "Download" dialog box
The project is now in the real or simulated main memory of the control system.

PC WorX
4.26.2.1 Sending a Project: Special Notes for PROFINET

PN
When sending the project to the control system, the desired PROFINET IO configuration
is transmitted and activated. If activation was successful, the system variable
PNIO_CONFIG_STATUS_ACTIVE is set.
The PROFINET IO controller attempts to start up all the devices in the desired
configuration.
SIM 4.26.2.2 Sending a Project: Special Notes for Simulation

When sending, the project is written to the simulated main memory of the control system.
When the project is sent to the simulated main memory of the control system, two new
tasks are opened automatically that appear in the taskbar.
Figure 4-51 Tasks for simulation
The "PCSim32" task contains information about ProConOS.

The "DEMOIO-DRIVER" task is used for the simulation visualization.
• Open the "DEMOIO-DRIVER" task.
For all devices to which variables are linked, the status of all inputs and outputs is
indicated.
Figure 4-52 Status of inputs and outputs

IB PN SIM 4.26.3 Performing a Cold Restart
In order to activate the project, it is necessary to perform a cold restart.

• To do so, click on "Cold" in the project control dialog box.
Figure 4-53 Project control dialog box
If the system cannot be started up, a corresponding error message appears on the
diagnostic display (for control systems with diagnostic display) and in the message window
in PC WorX and Diag+.
For an explanation of the error message, please refer to the Diagnostics Guide
(IBS SYS DIAG DSC UM E, Order No. 2747293).
For example, the ILC 350 ETH controller has been started up successfully if the green
PLC RUN LED is ON.
Communication to the PROFINET IO devices has been established successfully if the
BF LED does not flash on any of the PROFINET IO devices.

PC WorX
IB PN SIM 4.27 Operation
IB PN SIM 4.27.1 Setting the Task Properties
If no settings have been made for the task, a default task is used. If necessary, change the
properties of the task (in the example below a default task is changed to a cyclic task).
• Switch to the IEC programming workspace.

• Select "STD_TSK : Default".
• In the context menu select the "Properties..." menu item.
Figure 4-54 Default task: Properties
• Under type, select "Cyclic". This selects a cyclic task.
Figure 4-55 Default task: Type
• Apply your settings with "Apply".

• Change the setting, e.g., to 1000 ms.

Figure 4-56 Changing the setting
• Confirm your settings with "OK".

• Compile the project, send it to the control system, and perform a cold restart.
If the process is now running too slowly, change the settings.
• In the default task context menu select the "Settings..." menu item.

PC WorX
IB PN SIM 4.27.2 Debug Mode
In order to use debug mode, a program must have been created in your project. The
method of operation of the program can be monitored in debug mode.
• Activate debug mode.

The status of all global variables in the program is displayed under "MainV" in the "Project
Tree Window".
Figure 4-57 Variables in debug mode: Global variables
For PROFINET IO devices, the system variable PNIO_DATA_VALID can be assigned, for
example. The status can be read here. Only if this bit is set does the PROFINET IO device
supply valid data and all other process values are valid. In this way, you can check in this
window whether all PROFINET IO devices supply valid data. For information on system
variables, please refer to Appendix B "Status Information for a PROFINET IO System".
Figure 4-58 Variables in debug mode: System variables of the PROFINET IO devices

The program status of a POU is displayed by opening the program worksheet (in
Figure 4-59 under "Main" in the "Project Tree Window" or under "Main:Main" on the tab in
the worksheet).
Figure 4-59 Variables in debug mode: Program variables
The status of all global variables is displayed under "Global Variables" in the "Project Tree
Window".
Figure 4-60 Variables in debug mode: Global variables
• Switch to the window that provides the best display of the required information.

PC WorX
SIM 4.27.3 Simulation and Debug Mode
Following a cold restart, the green RUN LED lights up in "DEMOIO-DRIVER".

Program simulation can now be started. To monitor all variables, switch to debug mode.
The status of variables can be monitored online in debug mode.

The windows that provide information in debug mode are described in "Debug Mode" on
page 4-48.
• Switch to the window that provides the best display of the required information. The
"MainV" window has been selected for the description below.
• Arrange the screen display so that the "MainV" and "DEMOIO-DRIVER" windows can
be seen.
Figure 4-61 Program output state
• Perform the simulation. For an example, please refer to "Simulation and Debug Mode"
on page 7-11.
IB PN SIM 4.27.4 PLC Stop/Run
If the PLC is set to STOP, all outputs are set to their safe state. On control system startup,
process values are output again.

SIM 4.28 Switching from Simulation to Real Hardware
Once you have successfully completed the simulation for your program, you can switch to
your hardware. To do this, the actual bus configuration must correspond to the simulated
bus configuration.
• Stop the simulation. To do so, click on "Stop" in the project control dialog box.
• Stop debug mode. To do this, click on "Debug on/off".
• In the "Device Details" window, switch to the "Communication" tab.
• Select the communication path (see "Setting the Communication Path" on page 4-27).
• Send the project to the control system and perform a cold restart (see "Compiling and
Sending a Project, and Performing a Cold Restart" on page 4-42).

PC WorX

Example Project for an INTERBUS System
5 Example Project for an INTERBUS System

The creation of a project is described in detail in Section 4, "Sequence for Creating a
Project".
This section covers:
– All steps to be taken in reference to the corresponding section in Section 4, "Sequence
for Creating a Project"
– Project-specific settings
– Information and special notes for an INTERBUS project
5.1 Describing the Project
In the following, an example project is developed using function block diagram (FBD)
programming language.
In order to obtain the best possible results, please use the same identifiers and names
as used in this user manual.
Project name Quickstart
Project hardware – Control system: Inline Controller ILC 370 PN 2TX-IB

– I/O modules: IB IL 24 DO 16, IB IL 24 DO 8, and IB IL 24 DI 8
PC with
PC WorX
ILC 370 PN 2TX-IB

ETH 1 PLC
MRESET
LNK RUN
ACT
STP FAIL I1 I5 I9 Q1 E US 1 D 1 1 1 1 D 1 1 1 1 D 1 1 1
I2 I6 I10 Q2 UM 2 2 2 2 2 2 2 2 2 2 2 2
100 RUN / PROG I3 I7 I11 Q3 UL 3 3 3 3
I4 I8 I12 Q4 4 4 4 4
10/100
LNK
ACT INLINE CONTROL
ILC 370 PN 2TX-IB 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22
100
Ord. No.: 2876915
RESET 1 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 1
IB RB IN RB OUT
2 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22 2
xxxxxxx (Seriennr.)
RC IL
PRG 3 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 3
BA RDY / RUN
RD BSA
4 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 4
TR FAIL
PF
5 55 55 55 5 5 55 55 55 5
6 66 66 66 6 6 66 66 66 6
IB IL 24 DO 16
IB IL 24 DO 8
IB IL 24 DI 8 7127A002
Figure 5-1 Example bus configuration

PC WorX
Inputs and
outputs/process data
Table 5-1 Inputs and outputs used in the example including process data and assigned variables
Device Input/Output Signal at Variable Process Data
According to the Item
Device Data Sheet
ILC 370 PN 2TX-IB Input IN11 Co 3 TP 1.4 ONBOARD_INPUT_BIT10 3.1.4
IB IL 24 DI 8 Input IN2 Co 1 TP 2.1 IN2 1.2.1
Input IN5 Co 3 TP 1.1 IN3 3.1.1
IB IL 24 DO 8 Output OUT1 Co 1 TP 1.1 OUT1 1.1.1
Output OUT6 Co 3 TP 2.1 OUT2 3.2.1
IB IL 24 DO 16 Outputs OUT1 to Co 1 to 4 V0 ~DO16
OUT16 TP x.1 and x.4
No assignment required T1
T2
Co Connector
TP Terminal point
x Row on the Inline connector
5.2 Sequence for Creating the INTERBUS Project
The sequence for creating an INTERBUS project is shown in Figure 5-2.

When implementing the project some of the tasks can be performed offline (without a
connection to the INTERBUS system).
All tasks related to communication must be performed online (with a connection to the
INTERBUS system).
In Figure 5-2 and in the description in this section, it is assumed that the system has been
fully installed and all tasks are performed online. This is the quickest way to start up an
INTERBUS system.
If the INTERBUS system has not yet been fully installed or if you would like to perform as
many preparatory tasks as possible offline, follow the sequence described in Section 4,
"Sequence for Creating a Project".

INTERBUS
OFFLINE ONLINE
Start
IB PN SIM
IB PN SIM IB PN

INTERBUS devices
IB PN SIM
Yes No

INTERBUS
IB PN SIM
for controller A
IB PN SIM IB PN
Yes IB PN Yes
No No
PN IB PN IB PN
PN IB PN
PN
inserted?
IB PN SIM
No A
INTERBUS devices
Create program PN
IB PN SIM
IB PN SIM
Assign process data
PN
7127B020
name / IP settings
Figure 5-2 Sequence for creating the INTERBUS project

PC WorX
5.3 Creating a New Project
See also "Creating a New Project" on page 4-3.
• Select the "New Project..." command from the "File" menu.

• Select the control system (here: "ILC 370 PN Rev. >01/4.6F/1.41") and confirm your
selection with "OK".
• Specify the project name "Quickstart" and save the project.
5.4 Specifying Project Information
See also "Specifying Project Information" on page 4-5.

5.5 Checking/Modifying IP Settings for the Controller
See also "Checking/Modifying IP Settings for the Controller" on page 4-8.
automatically. When a new project is created, the default settings are specified as the
IP settings.

Address for the Controller" on page 5-5.
The IP address that is assigned here for the controller is also implemented as the
IP address for the communication path via TCP/IP.

5.6 Assigning the IP Address for the Controller
See also "Assigning the IP Address for the Controller" on page 4-24.
An IP address must first be assigned to the controller in order to enable communication.

For the ILC 370 PN 2TX-IB controller BootP is activated by default upon delivery for
assigning the IP address via Ethernet. In this case, when setting the IP address for the first
time a BootP server can be used. The corresponding procedure is described below. For all
other options, please refer to "Assigning the IP Address for the Controller" on page 4-24.
• Establish an Ethernet connection between your PC and the controller.
• In the menu bar, select the
"Extras... BootP/SNMP/TFTP Configuration..." menu.
the controller.
The specified IP parameters are displayed under "Manual definition of the TCP/IP settings".

PC WorX
See also "Setting the Communication Path" on page 4-27.
For a control system that supports Ethernet (e.g., ILC xxx ETH, ILC 370 PN 2TX-IB), the
communication path is automatically set to "Ethernet" by default with the IP address of
the controller specified under IP Settings. If you would like to send your project to the
control system via this Ethernet connection, the communication path does not have to
be set.
If not using this path, please proceed as described in "Setting the Communication Path"
on page 4-27.
5.8 Reading INTERBUS
See also "Reading INTERBUS" on page 4-38.
INTERBUS system.
• Select the control system (here: "ILC 370 PN") in the "Connected Bus" window.
command.
• Select the device that is actually connected to the INTERBUS system, and repeat this
step until all the devices are linked to their device description. According to the
example, the following I/O modules are connected: IB IL 24 DO 16, IB IL 24 DO 8,
and IB IL 24 DI 8.
Figure 5-3 Complete bus configuration for the example project

5.9 Compiling After Completing the Bus Topology
See also "Compiling After Completing the Bus Topology" on page 4-17.
5.10 Creating the Program

page 8-1.
• Set variable V0 to initial value 1. This set bit is then rotated to the left during program
processing.
5.11 Compiling After Completing the Program
See also "Compiling After Creating the Program" on page 4-19.

PC WorX
5.12 Assigning Process Data
See also "Generating Variables and Assigning Process Data" on page 4-19.
process data.
• In the top left window, "Symbols/Variables", select the standard resource (in the
example: STD_RES ILC370PN).
data to variables (IB IL 24 DI 8 in Figure 5-4).
• Select the process data item to be linked (3.1.1 in Figure 5-4).
• Variables are created when the program is created. Using drag & drop, link the
selected variable with one of the variables (IN3 in Figure 5-4) on the left-hand side.
If you would like to link further process data but no corresponding variables have been
created yet, select "Create Variable" in the context menu.
The generated variable is displayed in the bottom left window.
Since variable ONBOARD_INPUT_BIT10 is a system variable, it is not shown in

Figure 5-4.

5.13 Compiling and Sending a Project, and Performing

a Cold Restart
See also "Compiling and Sending a Project, and Performing a Cold Restart" on
page 4-42.
Compiling a project
Sending a project

• Activate the "Include Bootproject" checkbox in the "Project" area.
• Click on "Download" in the area on the left.
5.14 Operation
See "Operation" on page 4-46.

PC WorX

Example Project for a System Consisting of PROFINET IO and INTERBUS
6 Example Project for a System Consisting of

PROFINET IO and INTERBUS
The creation of a project is described in detail in Section 4, "Sequence for Creating a
Project".
This section covers:
– All steps to be taken in reference to the corresponding section in Section 4, "Sequence
for Creating a Project"
– Project-specific settings
– Information and special notes for a project with PROFINET IO and INTERBUS.
In the following, an example project is developed using function block diagram (FBD)
programming language.
Project name Quickstart_PN
Project hardware Specify the system structure during configuration. A system consisting of PROFINET IO
and INTERBUS comprises the PROFINET IO controller (control system), PROFINET IO
devices, and INTERBUS devices. The example system is shown in Figure 6-1.

PC WorX
PC
PC WorX
ILC 370 PN 2TX-IB FL SWITCH MCS 16TX
ETH 1 PLC
MRESET 1 3 5 7 9 11 13 15
LNK RUN FL SWITCH MCS 16TX
Ord. No. 28 32 70 0
ACT
STP FAIL I1 I5 I9 Q1 E US
I2 I6 I10 Q2 UM
100 RUN / PROG I3 I7 I11 Q3 UL
I4 I8 I12 Q4
10/100
MODE
LNK
ACT INLINE CONTROL 2 4 6 8 10 12 14 16
ILC 370 PN 2TX-IB 11 22 11 22 11 22 11 22 11 22 11 22
100
Ord. No.: 2876915 MAC US1 US2 FAIL
Address 00.A0.45.1B.D2.1D
RESET 1 11 11 11 11 11 1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
IB X17 X18 X19
RB IN RB OUT US1 GND US2 GND R1 R2 V.24 ACT 100 FD
2 22 22 22 22 22 2
xxxxxxx (Seriennr.)
RC IL
PRG 3 33 33 33 33 33 3
BA RDY / RUN
RD BSA
4 44 44 44 44 44 4
TR FAIL
PF
5 55 55 55 5
6 66 66 66 6
IB IL AO 1/SF
ILB PN 24 DI16
FL IL 24 BK-PN-PAC DIO16-2TX
FL PN/IBS
US D D
1 1
UM 2 2 UL RDY/RUN
3 3 BSA
RESET UL 4 4
DO4 DI4
FAIL
PF
100
1 2 1 2 1 2
100
INTERBUS
FD
FD Reset REMOTE
COL 1 1 1 1 COL
XMT
XMT RCV
2 2 2 2
RCV
LNK 3 3 3 3 3 3
10/100 10/100
00A0451B8D
4 4 4 4 4 4
INTERBUS LB D LB LB D LB
IB IL 24 DI 4-ME IN OUT IN OUT
IB IL 24 DO 4-ME U LS
US E
U LS U LS
US E
U LS
I1 I2 I1 I2
I3 I4 I3 I4
01 02 01 02
03 04 03 04
UA UA11 UA UA UA11 UA
IN UA12 OUT IN UA12 OUT
DIO 4/4 DIO 4/4
FLS IB M12 FLS IB M12

DI 8 M12 DO 8 M12-2A
7127F001
Figure 6-1 Example system
Table 6-1 Example system devices
Switch FL SWITCH MCS 16TX

PROFINET IO controller ILC 370 PN 2TX-IB
PROFINET IO device FL IL 24 BK-PN-PAC
ILB PN 24 DI16 DIO16-2TX
PROFINET IO device: INTERBUS proxy FL PN/IBS
INTERBUS devices At ILC 370 PN 2TX-IB: IB IL AO 1/SF
At FL IL 24 BK-PN-PAC: IB IL 24 DO 4-ME
IB IL 24 DI 4-ME
At FL PN/IBS: FLS IB M12 DI 8 M12
FLS IB M12 DO 8 M12-2A
Several PROFINET IO controllers can be used within one project. In this example, only
one PROFINET IO controller is used.

Inputs and
Table 6-2 Inputs and outputs used in the example including process data and assigned variables
Device Connected at Input/Output Signal at Variable Process
According to Data
the Device Item
Data Sheet
FL SWITCH MCS 16TX
ILC 370 PN 2TX-IB Input IN11 Co 3 TP 1.4 ONBOARD_ 3.1.4
INPUT_BIT10
ILB PN 24 DI16 DIO16-2TX Outputs OUT1 Co 1 to 4 V0 ~DO16
to OUT16 TP x.1 and x.4
IB IL AO 1/SF ILC 370 PN 2TX-IB
IB IL 24 DO 4-ME FL IL 24 BK-PN-PAC Output OUT3 TP 1.4 OUT1 1.4
IB IL 24 DI 4-ME FL IL 24 BK-PN-PAC Input IN1 TP 1.1 IN2 1.1
FLS IB M12 DI 8 M12 FL PN/IBS Input IN3 FC 3 pin 4 IN3 IN3
FLS IB M12 DO 8 M12-2A FL PN/IBS Output OUT3 FC 3 pin 4 OUT2 OUT3
T2
Co Connector
TP Terminal point
FC Female connector
6.2 Sequence for Creating the PROFINET Project
The sequence for creating a PROFINET project is shown in Figure 6-2.

When implementing the project some of the tasks can be performed offline (without a
connection to the PROFINET IO system).
All tasks related to communication must be performed online (with a connection to the
PROFINET IO system).
In Figure 6-2 and in the description in this section, it is assumed that the system has been
fully installed and all tasks are performed online. This is the quickest way to start up a
PROFINET system. This path is shown in a dark color in Figure 6-2. Other possible paths
are grayed out.
If the PROFINET system has not yet been fully installed or if you would like to perform as
many preparatory tasks as possible offline, follow the grayed out sequence. This is
described in detail in Section 4, "Sequence for Creating a Project".

PC WorX
PROFINET
OFFLINE ONLINE
Start
IB PN SIM
IB PN SIM IB PN

INTERBUS devices
IB PN SIM
Yes No

INTERBUS
IB PN SIM
for controller A
IB PN SIM IB PN
IB PN
System Yes Program created? Yes
No No
PN IB PN IB PN
PN IB PN
PN
inserted?
IB PN SIM
No A
INTERBUS devices
Create program PN IB PN SIM

IB PN SIM
Assign process data
PN
7127B021
name / IP settings
Figure 6-2 Sequence for creating the PROFINET project


• Select the control system (here: "ILC 370 PN Rev. >01/4.6F/1.41") and confirm your
selection with "OK".
• Specify the project name "Quickstart_PN" and save the project.

• Assign the name suffix for the PROFINET device name (here: quickstart.de) in the
"Device Details" window under "Domain Postfix".
6.5 Preparing the PC for Communication
See also "Preparing the PC for Communication" on page 4-7.
• In the "Tools/PROFINET Configuration..." menu in PC WorX select the network card

for your computer that is to be used for communication.

PC WorX
6.6 Checking/Modifying IP Settings for the

PROFINET IO Controller
If any modifications are made under "Project Information" that affect the IP settings for
the controller, a warning is displayed. However, the modification is not implemented
automatically. When a new project is created, the default settings are specified as the
IP settings.

Address for the PROFINET IO Controller" on page 6-7.
The IP address that is assigned here for the controller is also implemented as the
IP address for the communication path via TCP/IP.

6.7 Assigning the IP Address for the PROFINET IO

Controller
See also "Assigning the IP Address for the Controller" on page 4-24.
An IP address must first be assigned to the PROFINET IO controller in order to enable

communication.
For the ILC 370 PN 2TX-IB PROFINET IO controller BootP is activated by default upon
delivery for assigning the IP address via Ethernet. In this case, when setting the IP address
for the first time a BootP server can be used. The corresponding procedure is described
below. For all other options, please refer to "Assigning the IP Address for the Controller"
on page 4-24.
• Establish an Ethernet connection between your PC and the PROFINET IO controller.
• In the menu bar, select the "Extras... BootP/SNMP/TFTP Configuration..." menu.
the controller.
The specified IP parameters are displayed under "Manual definition of the TCP/IP
settings".
For a control system that supports Ethernet (e.g., ILC 350 PN, ILC 370 PN 2TX-IB), the
communication path is automatically set to "Ethernet" by default with the IP address of
the PROFINET IO controller specified under IP Settings. If you would like to send your
project to the control system via this Ethernet connection, the communication path does
not have to be set.
If not using this path, please proceed as described in "Setting the Communication Path"
on page 4-27.

PC WorX
6.9 Reading and Importing PROFINET IO Devices
See also "Reading and Importing PROFINET IO Devices" on page 4-30.

• In the "Bus Structure" window select the PROFINET node for the control system.
• Open the context menu and select the "Read PROFINET..." menu item.
All the connected PROFINET IO devices are displayed. When reading, the device name
and the IP parameters are read for each device - provided it is present.
• Select the devices that are to be included in your project.
• Include the selected PROFINET IO devices in your project by clicking "Insert".
If a PROFINET device name does not yet exist for a device, a name should be assigned
at this point.
• Activate the "Name Device" checkbox.
• Check the displayed PROFINET device name (see also "DNS/PROFINET Device
Name" on page 4-11).
• Assign the name to the relevant device.
• Confirm the display or your entry with OK.
• Close the "Read PROFINET" window by clicking on "Close".
The PROFINET structure is displayed in the "Bus Structure" window.
Figure 6-3 Bus configuration with read PROFINET IO devices

6.10 Checking/Modifying the PROFINET Settings for

PROFINET IO Devices
See also "Checking/Modifying the PROFINET Settings for PROFINET IO Devices" on

page 4-36.
When reading, the PROFINET settings of the relevant PROFINET IO devices are included
with default values. Check these settings and modify, if necessary.


PC WorX
6.11 Transmitting PROFINET Device Names and

IP Settings to PROFINET IO Devices
See also "Transmitting PROFINET Device Names and IP Settings to PROFINET IO

Devices" on page 4-37.
Before a PROFINET IO device is operated in a PROFINET IO network, the PROFINET

device name and IP address configured in PC WorX must also be made known to the
device itself.
• Make sure that the PROFINET IO controller can establish communication with the
PROFINET IO devices.
page 4-42.
During startup, the PROFINET controller automatically assigns the IP settings and device
parameterizations specified in the project to the PROFINET IO devices.
• To check the assignment of device names and IP settings, select the "PROFINET
Stationnames" tab in the "Device Details" window.
click on "Refresh".
name are listed.
listed.
The BF LED is now OFF on all PROFINET IO devices.

The PROFINET network is running.
For additional information about assigning PROFINET device names and IP addresses,
please also refer to "Additional Information" on page 6-15.

6.12 Reading INTERBUS
See also "Reading INTERBUS" on page 4-38.
The process for reading INTERBUS modules that are connected to a PROFINET IO
controller or a PROFINET IO device is the same.
PROFINET IO controller After the communication path to the PROFINET IO controller has been set, the INTERBUS
devices connected to the controller can be read.
PROFINET IO device After device names and IP parameters for the PROFINET IO devices have been assigned,
the INTERBUS devices connected to the PROFINET IO devices can be read.
INTERBUS system.
• Select one of the control systems displayed in the "Connected Bus" window.
command.
• Select the device that is actually connected to the INTERBUS system, and repeat this
step until all the devices are linked to their device description.
• Select all the "control systems" that are connected to the INTERBUS devices. These
include the Inline Controller as well as all the PROFINET IO devices displayed in the
"Connected Bus" window.

PC WorX

page 8-1.
processing.
6.15 Compiling After Creating the Program

process data.
example: STD_RES ILC370PN).
data to variables.
Please note for a PROFINET IO device with inputs and outputs that this is represented with
its modules.
Figure 6-5 Representation of a PROFINET IO device with its modules
• In this case, select the module where the required inputs or outputs are located
(DIO16: ILB PN 24 DI16 DIO16-2TX in Figure 6-6).
• Select the process data item to be linked (~DO16 in Figure 6-6).
selected variable with one of the variables (V0 in Figure 6-6) on the left-hand side.
Figure 6-6 Assigning process data for a PROFINET IO device
• For the specified example, assign the inputs and outputs to the created variables
according to Table 6-2 on page 6-3.

PC WorX
Since the variable ONBOARD_INPUT_BIT10 is a system variable, it is not shown in

Figure 6-7.

a Cold Restart
page 4-42.
Compiling a project
Sending a project

• Activate the "Include Bootproject" checkbox in the "Project" area.
6.18 Operation
See "Operation" on page 4-46.

6.19 Additional Information
6.19.1 Modifying the PROFINET Device Name
If, following device naming, you wish to modify device names, proceed as follows:
If a project is located on the PROFINET IO controller, the controller attempts to start up the
PROFINET IO devices with the information stored in the project. In this case, a PROFINET
device name cannot be assigned. Therefore if there are Ethernet connections between the
PROFINET IO devices and the PROFINET IO controller with the project, these
connections must be aborted first. To do this, proceed as follows:

• Activate the "Stop" button.
• Activate the "Reset" button.
All Ethernet connections are aborted and the PROFINET device names can now be
assigned.
• In the bus configuration, select the PROFINET IO device which is to be assigned the
name.
• Select the "PROFINET Settings" tab in the "Device Details" window.
• Modify the device name under "DNS/PROFINET Device Name".
• In the "Device Details" window, select the "PROFINET Device Names" tab.
click on "Refresh".
name are listed.
Same type Only those devices that are the same type as the device
selected in the bus configuration are listed.
listed.

PC WorX
Figure 6-8 List of all PROFINET IO devices that can be accessed in the network
In the "Selected Device" area, the PROFINET IO device name specified under
"IP Settings" is displayed.
• From the list, select the corresponding PROFINET IO device (e.g., using the indicated
MAC address).
Figure 6-9 Selecting the device

A flashing display can be triggered on the device via "Flashing On". This display can be
used to find the selected device in the field.
When the button is activated, the devices in the example system flash as follows:
ILB PN 24 DI16 DIO16-2TX RDY LED flashing

FL IL 24 BK-PN-PAC Double-zero flashing on the 7-segment display
FL PN/IBS Double-zero flashing on the 7-segment display
The flashing process is also indicated in the list.
• Send the name to the device via "Assign Name".
If you receive an error message, first delete the name via "Delete Name" and then assign
the name again.
The PROFINET device name is transferred from the PC to the PROFINET IO device. The
previous parameters are still displayed as the IP parameters. The IP parameters are only
assigned in the next step.
• Assign the appropriate PROFINET device name to each PROFINET IO device.
• Compile the project, send it to the control system, and perform a cold restart (see
"Compiling and Sending a Project, and Performing a Cold Restart" on page 4-42).

PC WorX
6.19.2 Renumbering Devices
There is also the option of automatically regenerating the IP parameters

(e.g., IP addresses, Domain Postfix) for all devices. The settings from the project
information are used for this.
• Select the project node.
• Select "Renumber devices/Whole project" and then the menu item for renumbering the
devices (e.g., "All DNS/PROFINET Device Names").
Figure 6-10 Renumbering devices
In this example, the newly specified names (e.g., ilb-di16-dio16) are extended to include
the Domain Postfix quickstart.de specified in the project node. This is the complete
PROFINET device name.
• To view the IP addresses in the bus configuration in ascending order, renumber the
IP addresses as well.
Figure 6-11 Renumbering devices (PROFINET device names and IP addresses)
All the devices in the project now have the correct IP parameters. In the following section,
these parameters must actually be assigned to the devices.

• Compile the project, send it to the control system, and perform a cold restart
(see "Compiling and Sending a Project, and Performing a Cold Restart" on page 4-42).
6.19.3 Assigning IP Parameters for the PROFINET IO Device
In order to enable the connected INTERBUS modules to be read in the bus configuration,
the IP parameters must be assigned to the PROFINET IO devices.
There are two options for assigning IP parameters. Select an option based on the specified
requirements.
6.19.3.1 Option 1: IP Parameter Assignment During PROFINET IO Controller

Startup
This option always works provided the PROFINET IO controller is able to establish
communication with the PROFINET IO devices.
• In the "Device Details" window, select the "PROFINET Device Names" tab. You can
later check whether the IP parameters have been assigned.
page 4-42.
During startup, the PROFINET IO controller assigns the IP parameters specified in the
project to the PROFINET IO devices.
• Click on "Refresh".
Figure 6-12 All devices with PROFINET device names and IP parameters

PC WorX
6.19.3.2 Option 2: IP Parameter Assignment Without Project on the

PROFINET IO Controller
This option is specifically designed to read INTERBUS modules that are connected to a
PROFINET IO device without first sending a project to the PROFINET IO controller.
This option only works under the following conditions:
1. There is no project on the PROFINET IO controller, i.e., the PROFINET IO controller
did not yet establish a connection to the PROFINET IO devices.
Or
2. There is no connection between the PROFINET IO controller and the PROFINET IO
devices (Ethernet cable not plugged in or no supply voltage at the PROFINET IO
controller).
In each case, the BF LED must flash on each of the PROFINET IO devices. If the BF LED
of a PROFINET IO device does not flash, no IP parameters can be assigned to this device
as it is currently communicating.
• Select the device to which you would like to assign the IP parameters. Proceed as
described in "Transmitting PROFINET Device Names and IP Settings to
PROFINET IO Devices" on page 6-10.
• Send the IP parameters to the device via "Assign IP".
• Assign the IP parameters to each PROFINET IO device.
Figure 6-13 All devices with PROFINET device names and IP parameters
Now the INTERBUS modules connected to the devices can be read.

If there was already a project on the PROFINET IO controller and the connection was
aborted in order to send the IP parameters, please note the following:
On startup, the PROFINET IO controller starts up the PROFINET IO devices with the
IP parameters stored in this project (which may be old). Only after compiling, sending, and
performing a cold restart for the new project can the IP parameters be transferred from this
project to the PROFINET IO devices.
If error messages are displayed and if the IP parameters are not accepted:
• Check whether the BF LED is flashing.
If so: Check all Ethernet connections as well as your previous actions.
If not: You cannot assign any IP parameters. Either interrupt communication or
proceed according to "Option 1: IP Parameter Assignment During PROFINET IO
Controller Startup" on page 6-19.

Example Project for a Simulation With Processor Type "IPC" Control Systems
7 Example Project for a Simulation With Processor Type

"IPC" Control Systems
For processor type "IPC" control systems PC WorX can be used to simulate a project
completely without hardware. A program can be created and tested without having to
actually connect hardware.
For an overview of the processors used with the various control systems, please refer to
Table D-1 "Phoenix Contact control systems".
In the following, an example project is developed for the simulation using function block
diagram (FBD) programming language.
Project name: SIM

Project hardware:
– Control system: RFC 430 ETH-IB
– Bus coupler: IBS IL 24 BK T/U
PC with
PC WorX
RFC 450 ETH-IB
FCR
/PR UN
OG
FCR
UN
STO
P
FCR
ES
10/
100
Bas
LIN e-T
K
TRA
FFI
C
RU
N
SYS
FAIL
CO
FCR M1
UN
FCD
BG
I/O
IBS IL 24 BK T/U
Ord.No.: 27 30 20 0
RE
RFC 450 ETH-IB
SE
T
PR
G
RE
MO
TE
INT
ER +
BUS
–
+
–
24V
DC
BA RD UL US 1 D 1 1 1 1 D 1 1 1 1 D 1 1 1
2 2 2 2 2 2 2 2 2 2 2 2
RC LD UM 3 3 3 3
4 4 4 4
BK-T/U
1 2 1 2 1 2 1 2 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22 11 22
1 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 1
2 22 22 22 22 22 22 22 22 22 22 22 22 22 22 22 2
3 33 33 33 33 33 33 33 33 33 33 33 33 33 33 33 3
4 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 4
5 55 55 55 5
6 66 66 66 6
IB IL 24 DO 16
IB IL 24 DO 8
IB IL 24 DI 8 7127A013
Figure 7-1 Example bus configuration

PC WorX
Inputs and
Table 7-1 Inputs and outputs used including process data and assigned variables
Device Input/Output Signal at Variable Process Data Item

According to the
Device Data Sheet
IB IL 24 DI 8 Input IN1 Co 1 TP 1.1 S1 1.1.1
IB IL 24 DO 8 Output OUT1 Co 1 TP 1.1 OUT1 1.1.1
Output OUT6 Co 3 TP 2.1 OUT2 3.2.1
IB IL 24 DO 16 Outputs OUT1 to Co 1 to 4 V0 ~DO16
OUT16 TP x.1 and x.4
T2
Co Connector
TP Terminal point
x Row on the Inline connector
7.2 Sequence for Creating the Simulation Project
The sequence for creating the simulation project is shown in Figure 7-2.
When implementing the project all of the tasks are performed offline (without a connection
to the system).

Simulation
OFFLINE ONLINE
Start
IB PN SIM
IB PN SIM IB PN

INTERBUS devices
IB PN SIM
Yes No

INTERBUS
IB PN SIM
for controller A
IB PN SIM IB PN
Yes IB PN Yes
No No
PN IB PN IB PN
PN IB PN
PN
inserted?
IB PN SIM
No A
INTERBUS devices
Create program PN
IB PN SIM
IB PN SIM settings Operation (end)
Assign process data
PN
7127B019
name / IP settings
Figure 7-2 Sequence for creating the simulation project

PC WorX

• Select the RFC 430 ETH-IB IPC_40 control system and confirm your selection with "OK".
• Specify the project name "SIM" and save the project.
If you want to use a different control system for the example project then select a different
project template. Please note that the following descriptions may differ.
Always select only one processor type "IPC" control system.

7.5 Checking/Modifying IP Settings for the Controller
automatically. When a new project is created, the default settings are specified as the IP
settings.

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

7.6 Manually Inserting INTERBUS Devices
See also "Manually Inserting INTERBUS Devices" on page 4-12.
The following devices are used for the example project:

– Control system: RFC 430 ETH-IB
– Bus coupler: IBS IL 24 BK T/U
• Select a point in the "Bus Structure" window where a device is to be inserted. To insert
the bus coupler, select the INTERBUS node for the control system, as the first
INTERBUS device can only be inserted here.
• In the device catalog, open the product range for the inserted device (e.g., IL for Inline)
under " Phoenix Contact".
• Under the product range, open the product group (e.g., bus coupler, I/O analog).
• Select the device to be inserted (e.g., IBS IL 24 BK/T-U).
• Hold down the mouse button and drag the selected device to the insertion point.
• Insert all the other devices.
In the example: Insert the Inline modules (I/O digital) below the bus coupler.
The bus configuration with the INTERBUS modules used in the example is shown in
Figure 7-3.
• Select the "Rebuild Project" command from the "Build" menu.

PC WorX

page 8-1.
processing.
7.9 Compiling After Creating the Program
process data.
example: STD_RES: RFC450ET).
data to variables (IB IL 24 DO 16 in Figure 7-4).
• Select the process data item to be linked (~DO16 in Figure 7-4).
selected variable with one of the variables (V0 in Figure 7-4) on the left-hand side.

Figure 7-4 Variable V0


PC WorX
• Switch to the bus configuration workspace to set the communication path.

• In the "Bus Structure" window select the INTERBUS node for the control system.
• Select the "Simulation" interface type.
• Activate the simulation environment by clicking "Apply".

a Cold Restart
page 4-42.
Compiling a project
Sending a project

• Click on "Download".
• Activate the "Ensure realtime for Download Changes" and "Include Bootproject"
checkboxes in the "Project" area.
When sending, the project is written to the simulated main memory of the control system.
• Open the "DEMOIO-DRIVER" task.
For all devices to which variables are linked, the status of all inputs and outputs is
indicated.
Figure 7-6 Status of inputs and outputs

Cold restart Perform a cold restart as described in "Compiling and Sending a Project, and Performing
a Cold Restart" on page 4-42.
The cold restart activates the project. The simulation can now be started.
7.13 Operation
7.13.1 Setting the Task Properties
If no settings have been made for the task, a default task is used. If necessary, change the
properties of the task (in the example below a default task is changed to a cyclic task).

• Select "STD_TSK : Default".
• In the context menu select the "Properties..." menu item.
Figure 7-7 Default task: Properties
• Under type, select "Cyclic". This selects a cyclic task.

PC WorX
Figure 7-8 Default task: Type
• Apply your settings with "Apply".

Figure 7-9 Changing the setting
• Confirm your settings with "OK".

If the process is now running too slowly, change the settings.
• In the default task context menu select the "Settings..." menu item.

7.13.2 Simulation and Debug Mode
Following a cold restart, the green RUN LED lights up in "DEMOIO-DRIVER".

Program simulation can now be started. To monitor all variables, switch to debug mode.
The status of variables can be monitored online in debug mode.

• Switch to the window that provides the best display of the required information. The
"MainV" window has been selected for the description below.
• Arrange the screen display so that the "MainV" and "DEMOIO-DRIVER" windows can
be seen.
Figure 7-10 Program output state
In the program output state, Start = FALSE, only the status LED of the set output
(V0 = 16#0001) is ON.
In "DEMOIO-DRIVER" activate the IN0 LED, so that Start = TRUE and the program is
started. The following actions are performed:
– Pulse output S1 = TRUE (see S1 in the "MainV" window)
– The counter for the elapsed time T2 is started (see T2 in the "MainV" window).
– Output 0 of IB IL 24 DO 8 (variable OUT1) is set. This module is displayed in slot 2
(OUT/8) of the rack in "DEMOIO-DRIVER". The OUT0 status LED lights up.
– The chasing light is started (see V0 in the "MainV" window). This module is displayed
in slot 0 (OUT/8) and slot 1 (OUT/8). The status LEDs for these two slots light up in
succession.

PC WorX
Figure 7-11 Start has been activated
After 15 seconds the Pulse_Output is set to FALSE, output OUT0 of the IB IL 24 DO 8 is

switched off, and the chasing light is switched off.
Figure 7-12 Program execution complete
If input IN0 is set to TRUE when the maximum time is reached, T2 remains set to 15000.
As soon as IN0 switches to the FALSE state, T2 is set to 0.
• Activate and deactivate IN0 to check the validity of this program part.
The program part with the AND block operates independently of the program part with the
pulse timer.
• Activate and deactivate the LEDs that are assigned to inputs IN2 and IN5.
Output OUT5 of module IB IL 24 DO 8 responds according to the result of ANDing.

Figure 7-13 ANDing in "Main"
7.14 Switching from Simulation to Real Hardware
Once you have successfully completed the simulation for your program, you can switch to
your hardware. To do this, the actual bus configuration must correspond to the simulated
bus configuration.
• Stop the simulation. To do so, click on "Stop" in the project control dialog box.
• Stop debug mode. To do this, click on "Debug on/off".
• In the "Device Details" window, switch to the "Communication" tab.
• Select the communication path (see "Setting the Communication Path" on page 4-27).
• Send the project to the control system and perform a cold restart (see "Compiling and
Sending a Project, and Performing a Cold Restart" on page 4-42).

PC WorX

Example Program
8 Example Program
A different example project is described in each of the previous sections. The various
sections focus on the following topics:
– Section 5, "Example Project for an INTERBUS System"
– Section 6, "Example Project for a System Consisting of PROFINET IO and
INTERBUS"
– Section 7, "Example Project for a Simulation With Processor Type "IPC" Control
Systems"
The procedure for creating the program in the software is the same. This is described in
this section.
8.1 Program Description
The program is created in "function block diagram (FBD)" programming language.

The program controls the following sequence:
On an edge change at input IN from FALSE to TRUE, a timer (function block TP)
generates a pulse, which is output at output Q for the duration PT. The associated output
is set for this time. The state of the output is indicated at the corresponding status LED.
The elapsed time is output at output ET.
If IN switches from FALSE to TRUE for a second time while the pulse is still active (within
PT), this does not affect the duration of the pulse generated at output Q. This signal is
ignored.
If a TRUE signal is present at output Q, function block ROL is activated, which rotates
the operands associated with input parameter IN bit-by-bit to the left. I.e., for an initial value
equal to 1, the associated outputs (e.g., OUT1 to OUT16 of a 16-bit module) switch in
succession from FALSE to TRUE and back again. This state change is indicated by a
"chasing light" at the corresponding status LEDs.
Once the pulse time has elapsed, the output that indicates the presence of the pulse and
the chasing light are switched off.
Independent of this, inputs IN1 and IN2 are logically ANDed. IN1 and IN2 map the status
of the inputs to which the toggle switches are connected. The result of ANDing is output at
output OUT.

PC WorX
8.2 Function Blocks Used
Timer Format conversion Rotate to left ANDing
Timer Function Block TP
Table 8-1 Timer TP_1
Parameter Variable Data Type Application Initial Value Description

Name
IN ONBOARD_ BOOL VAR_EXTERNAL Start: If a rising edge is detected, a
INPUT_BIT10 pulse is generated.
/ S1
PT T1 TIME VAR T#15000ms Pulse time
Default: 15 seconds = 15,000 ms
Q OUT1 BOOL VAR Pulse output
(VAR_EXTERNAL) TRUE, when IN = TRUE and ET < PT;
FALSE, when IN = FALSE or ET > PT
ET T2 TIME VAR Time passed
(VAR_EXTERNAL)
ONBOARD_INPUT_BIT10) In the example, when using an Inline Controller a system variable is used for the onboard
/ S1 inputs and outputs (here: ONBOARD_INPUT_BIT10).
Otherwise a user variable is used (S1).
VAR (VAR_EXTERNAL) If a variable will only be used internally and will not be assigned to a process data item, it
can be declared as VAR. However, if this variable is to be monitored in debug mode or in
the simulation, declare it as VAR_EXTERNAL. This is why in the example program the
variables are declared as VAR_EXTERNAL.
Format Conversion Function Block BOOL_TO_DINT

To use the output signal of block TP_1 as the input signal for block ROL, the format must
be converted from BOOL to DINT.
Variables are not declared for this block.

Example Program
Rotation Function Block ROL
Table 8-2 Rotate to left ROL

Name
IN V0 WORD VAR_EXTERNAL Input value
N DINT Number of characters to be rotated
(in the example 0 or 1,
defined by OUT1)
(Output) V0 WORD VAR_EXTERNAL Output value ROL
ANDing Function Block AND
Table 8-3 ANDing function block AND

Name
IN1 IN2 BOOL VAR_EXTERNAL Input value 1
IN2 IN3 BOOL VAR_EXTERNAL Input value 2
OUT OUT2 BOOL VAR_EXTERNAL Output value AND

PC WorX
8.3 Programming
For programming, proceed as follows:

• Double-click on "Main" in the "Project Tree Window" to activate the IEC programming
interface.
• In the "Main" worksheet, click on the empty position where you would like to insert the
function block.
Figure 8-1 IEC programming workspace
• Select function block "TP" by double-clicking on it in the "Edit Wizard" window.

Example Program
• Enter the name "TP_1" for this function block in the "Variable Properties" window and
confirm your entry with "OK".
Figure 8-2 "Variable Properties" window
The function block is inserted in the worksheet.
Figure 8-3 Function block in the IEC programming workspace
• Double-click on the "IN" input parameter of the function block to define the variable
properties.

PC WorX
Select the relevant next step depending on whether you would like to assign the "IN" input
parameter for a user variable or a system variable:
Action User variable S1 System variable
ONBOARD_INPUT_BIT10
(Used for the simulation example) (Used for the example with the
ILC 370 ETH 2TX-IB)
• To set the scope of validity, open all folders
under "Global Variable Groups" and select
the following in the "STD_RES" folder: "Default" "System Variables"
• At the top of the section, select the scope of
validity as: "Local" "Global"
• In the "Variable Properties" window, enter or • Enter the name S1. • Select the corresponding
select the name for the "IN" input parameter variable.
under "Name". For input 11 of the
ILC 370 ETH 2TX-IB this is
ONBOARD_INPUT_BIT10.
Setting the scope of validity is only necessary when creating a variable for the first time
in the corresponding scope of validity. All other variables are also assigned to the
selected group.
User variable S1 System variable ONBOARD_INPUT_BIT10

Figure 8-4 "Variable Properties" window for user variables and system variables

Example Program
• Specify the data type. The variable is a bit variable and thus a "BOOL" data type.
• Select "VAR_EXTERNAL" (for "Local" scope of validity) or "VAR_GLOBAL" (for
"Global" scope of validity) in the "Usage" selection box because the variable will later
be assigned to a process data item.
If you have created a variable as VAR, which you later would like to use as
VAR_EXTERNAL, proceed as follows to change it:
• Select "VAR_EXTERNAL" in the "Usage" selection box.
• Create the variable in the "Project Tree Window" as a global variable under
"Global_Variables".
• Confirm your entries with "OK".

• Double-click on the "PT" input parameter of the function block to define the variable
properties.
• If "System Variables" was set in the scope of validity for "Local Variable Groups", set
"Default" in the "STD_RES" folder.
• In the "Variable Properties" window, assign the name "T1".
• "TIME" is specified in the "Data Type" selection box.
• Select "VAR" in the "Usage" selection box because the variable will only be used
internally and will not be assigned to a process data item.
• Enter a pulse width of 15 seconds (T#15000ms) as the "Initial value".
Figure 8-5 "Variable Properties" window
• Confirm your entries with "OK".

• Proceed in the same way for the output parameters of this block. Use the values in
Table 8-1 "Timer TP_1" on page 8-2.
Figure 8-6 Function block TP_1 with all parameters

(S1: user variable; ONBOARD_INPUT_BIT10: system variable)

PC WorX
• Insert function block BOOL_TO_DINT. A parameter declaration is not required for this
block.
• Insert block ROL.
• Declare the required parameters according to Table 8-2 "Rotate to left ROL" on
page 8-3.
• Insert block AND.
• Declare the required parameters according to Table 8-3 "ANDing function block AND"
on page 8-3.
All function blocks are shown in Figure 8-7 with the required parameters.
Figure 8-7 All function blocks inserted with the required parameters
Link the required inputs and outputs. To do this, proceed as follows:

• Select variable OUT1 and drag it to the same level as block BOOL_TO_DINT.
• Activate the "Linking objects" icon.

• Click in the part of the line for output OUT1 and link this item to the input of
BOOL_TO_DINT by holding down the mouse button.
• Link the output of BOOL_TO_DINT with input N of block ROL.
The finished program is shown in Figure 8-8.
User variable S1 System variable ONBOARD_INPUT_BIT10

Figure 8-8 Complete program

Example Program
Deleting Variables
If variables are created during program creation, they are created in different worksheets.
When variables are deleted or renamed in the program, they are not automatically deleted
or renamed in the other worksheets.
An error message is therefore displayed when compiling.
• In this case, delete the variables that are not used from the areas marked in the tabs
in Figure 8-9 ("Global_Variables" and "MainV:Main").
Figure 8-9 Deleting variables

PC WorX
8.4 Setting the Initial Value
If you would like to set an initial value, proceed as follows:

• Double-click on the "Global_Variables" item.
• Set the initial value for the variables (here: V0 to initial value 1).
Figure 8-10 Setting the initial value (here: V0 = 1)
8.5 Additional Options for PROFINET
The following additional data can be evaluated in a PROFINET IO system:

– For all PROFINET IO controllers: System variables that indicate the configuration
status
– All PROFINET IO devices: Pre-defined process data that indicates the status
See also "Status Information for a PROFINET IO System" on page B-1.

PC WorX and SafetyProg
9 PC WorX and SafetyProg

SafetyProg is an integrated part of PC WorX and is used to operate a safe INTERBUS
Safety system.
For a project using INTERBUS Safety, proceed in the same way as for a project using a
PROFINET IO or INTERBUS system.
All special Safety-specific features and settings are described in detail in the user manual
for the PROFINET proxy with integrated safe controller that is used. This section only
provides basic information about an INTERBUS Safety project in PC WorX.
Inserting a PROFINET If creating the bus configuration manually:

proxy from the device The PROFINET proxy with integrated safe controller is located in the device catalog under
catalog "Phoenix Contact/Safety/INTERBUS Proxy".
Specify the project name • In the bus configuration, select the "Safe Control" node on the PROFINET proxy with
for the INTERBUS Safety integrated safe controller.
project • Assign the project name in the "Device Details" window.
Figure 9-1 Project name for the INTERBUS Safety project
Preparing a project Make all the settings for the project according to the user manual for the PROFINET proxy
with safe controller that is used. This includes, for example:
– PROFINET settings
– Process data exchange with the standard control system
(exchange, acknowledgment, and standard variables)
Compiling a project Before switching to SafetyProg:

• Compile the project.
The project is saved automatically following compilation.

PC WorX
Starting SafetyProg Once the project has been completed in PC WorX, SafetyProg can be started.
• Make sure you are in the bus configuration or process data assignment workspace.
• Select the "Safe Control" node on the PROFINET proxy with integrated safe controller.
• In the context menu select the "SafetyProg" menu item.
Figure 9-2 Starting SafetyProg
For detailed information about operating the SafetyProg software, please refer to the
online help or the Quick Start Guide for the software.

Additional Software Functions
A Additional Software Functions
A1 Setting the Realtime Clock
Some control systems have an internal system clock (e.g., ILC 350..., ILC 370...). In the
"Extended Settings" tab, the time and date can be set for the internal system clock of the
control system.
The current control system time is read and displayed every time the "Extended Settings"
tab is opened. The display then indicates this value until the "Extended Settings" tab is
opened again.
If you want to apply the system time and date from your PC:
Requirement: A connection between the PC and control system.
• Select the control system node (e.g., "ILC 370 PN").
• Click on "System Time".
• Then immediately click on "Send" to transmit the data in the "Realtime Clock Settings"
tab to the control system.
If you want to set different values:
• Enter the values for the time and date.
• Then click on "Send" to transmit the data in the "Realtime Clock Settings" tab to the
ILC 350 PN.
Figure A-1 Realtime clock settings
7127_en_02 PHOENIX CONTACT A-1

PC WorX
A2 Options for Modifying a Project
PC WorX provides two functions that can be used to send project modifications to the
control system(s) and activate them there without having to stop the active PLC.
Table A-1 Options for modifying a project
Options: Download Changes Online Modifications

Features: Send the entire project (also Only send modifications that
known as Download Changes) have been made, e.g., individual
function blocks
Sequence: Debug mode ON: An error is detected
Debug mode OFF
Modify
Compile
Send via project control dialog Send via the
box "Build/Online Modifications"
menu
Application: Extensive modifications Minor modifications
Advantage: Fewer restrictions Fast
A 2.1 Download Changes (PC WorX Version 3.10 or Later,

ProConOs Version 4.0 or Later)
The "Download Changes" function is only available for controllers with an "IPC_40" or
"ARM_L_40" processor (see also Table D-1 on page D-2).
Download
Figure A-2 Download changes
A-2 PHOENIX CONTACT 7127_en_02

Options for Modifying a Project
When downloading changes to one or more control systems, it is possible to specify

whether the system should ensure the realtime behavior of the PLC before starting the
transmit process.
If the "Ensure realtime for Download Changes" option is activated, the system attempts to
execute the "Download Changes" function without violating the realtime conditions of the
tasks executed on the control system.
If the modifications cannot be sent, for example, because the amount of data to be copied
is too large, an error message is output. In this case, disable the "Ensure realtime..." option
(i.e., permit realtime violations) so that all modifications can be executed.
If realtime violations are permitted, first ensure that your PLC application is running within
safe limits. Please note that each realtime violation may result in unexpected
consequences in the automation system, as under certain circumstances user tasks are
not processed for a short time. Therefore, check the level of risk before disabling this
option.
For more detailed information on the "Download Changes" function and on ensuring
realtime with detailed background information, please refer to the online help for
PC WorX.
To determine when the "Download Changes" function can or cannot be used, please refer
to the table below.
Table A-2 Application options and restrictions for "Download Changes"
Area Can Be Used After Cannot Be Used After

POU – Modifying the code in existing POUs – Using an MSFC POU in the project
– Using new POU types in a resource
In principle, modifications in SFC POUs are permitted. However, they can result in critical
PLC states if the "Download Changes" function is executed when the PLC is running. For
example, the execution of an SFC step chain could be blocked if an active step is deleted.
These SFC modifications include:
– Modifying a previous/subsequent relationship.
– Modifying step properties (type).
– Modifying step/action relationships.
– Modifying qualifiers (action qualifiers).
In these cases, a warning is generated. Check the existing level of risk before continuing the
process by confirming the warning.
Variables – Adding/deleting local and global variables

– Modifying local and global variables (including
initial value)

PC WorX
Table A-2 Application options and restrictions for "Download Changes" (Continued)
Data types – Modifying the data type of variables, whereby
the variables are reinitialized
– Adding/deleting data types
– Modifying data type declarations. Modified data
variables are initialized.
– Modifying the data area
Function – Declaring new function block instances (user/
blocks firmware)
Program – Modifying comments in the program code
– Adding/deleting program instances
Tasks – Modifying task cycle times – Adding or deleting tasks
– Modifying watchdog times for tasks – Modifying task properties other than the cycle
time and the watchdog time (i.e., task type,
priority, event number, SPG assignment, stack
size)
I/O – Modifying driver parameters in the I/O – Modifying VAR_CONF groups in the I/O
configuration configuration configuration
– Adding/deleting an I/O group in the – Modifying I/O group properties other than the
I/O configuration driver parameters (e.g., addresses, the driver
itself, task assignment, etc.)
Other – Adding new configurations and resources
If a restriction is not observed, the system displays an error message in the message
window. Call the help information for the error message by right-clicking on the entry in the
message window and selecting the "Message Help" context menu item. Undo the relevant
modification, rebuild the project, and execute "Download Changes" again.
For additional information, please refer to the online help for PC WorX.

A 2.2 Online Modifications
"Online modification" of a POU means that in a single step the modifications in the project
are compiled and the code is generated and automatically sent to the active PLC. During
the entire process the PLC continues running, i.e., the program executed on the PLC is not
interrupted during compilation and transmission.
The "Online Modifications" menu item is only available in offline mode. The affected
worksheet can be set to online and offline mode via the "Debug ON/OFF" icon in the
toolbar.
"Online Modifications" can be called via the "Build/Online Modifications" menu item or via
the corresponding icon (see "Frequently Used Icons for Compiling and Debugging" on
page 3-3).
The "Online Modifications" command can be used in two ways:
1. Correcting errors in the code.
If a programming error is discovered in online mode and you have switched to offline
mode to correct the error, the modifications made can be compiled with "Online
Modifications".
2. Further development of a basic project.
In some cases it is easier and more convenient to develop a project using online
modifications rather than via the "Make" command. Once a basic project has been
compiled for the first time with "Make", this "skeleton project" can be completed by
editing the individual POU code worksheets and using "Online Modifications" to add
these extensions to the PLC program, which is already running on the target system.
In both cases, the modifications are sent automatically to the PLC without interrupting PLC
operation, i.e., the modifications can then be seen in online mode.
To determine when the "Online Modifications" function can be used, please refer to the
table below.

PC WorX
Table A-3 Application options and restrictions for "Online Modifications"

Variables – Adding new local and global variables – Modifying variable properties
– Deleting variables, which are not used in the – Modifying variable initial values (initialized
CSV file (*.csv) variables cannot be modified online)
– Adding global variables, which are not on direct
inputs and outputs
– Removing variables from the program
worksheet
– Adding a user-defined function block*
* Requirement: An instance of this function block
has already been declared in a variable worksheet
of any POU of the same resource
Functions – Adding new IEC-defined functions – Modifying the formal parameters of functions
– Adding a user-defined function* – Adding new formal parameters
– Adding a function from a firmware or user
library*
* Requirement: This function has already been
called in any POU of the same resource.
Function – Adding new IEC-defined function blocks – Modifying the formal parameters of function
blocks – Adding a user-defined function block* blocks (VAR_INPUT, VAR_OUTPUT, and
– Adding a function block from a firmware library VAR_IN_OUT)
or a user library* – Adding new formal parameters
* Requirement: An instance of this function block
has already been declared in a variable worksheet
of any POU of the same resource
Other See Table A-4 "Rules for the specific programming – Modifying character strings/constants or user-
languages" on page A-7 defined character strings
– Deleting POUs or libraries
– Modifying the hardware structure
Please observe the following when modifying functions and function blocks:
For online modifications to be possible in the above cases, the project must have been
compiled with "Make" and sent to the target system. In addition, online mode must
already be active.

Table A-4 Rules for the specific programming languages
Language Online Modification Possible After

All – Adding line breaks and blank lines
– Adding or modifying comments
IL – Adding or modifying IL operators
– Modifying the nesting depth
ST – Modifying instructions or expressions
FBD – Modifying existing networks
– Modifying graphics, e.g., moving lines or function blocks
– Networks have been modified or added
LD – Modifying existing networks
– Modifying graphics, e.g., moving lines or function blocks
– Networks have been modified or added
SFC – Modifying variables, FBD or LD networks, which are directly connected
– Modifying time intervals for time qualifiers
– Modifying variable names in action blocks
Use "Make" if online modifications cannot be implemented.

If some of the restrictions are not observed, the online modification process is aborted
and a corresponding error message appears in the message window.
Once the "Online Modifications" command has been aborted, compile the project with
"Make", and send it manually to the PLC. Modifications can now be implemented online
again.

PC WorX
A3 Extended Retain Handling
Extended retain handling is supported in ProConOs Version 4.0 or later.
Retentive variables are declared with the keyword "RETAIN". The value of a retentive
variable is retained even if the PLC is switched off. The last value of the variable is used
for a warm start.
Application: Your application program is already executed on the PLC. Modifications to

the retentive variables are now required or new RETAIN variables must be added.
Without the retain handling function, a cold restart would have to be carried out after the
modifications. In this case, all the variables are reinitialized.
With the retain handling function of the programming system, a PLC cold restart is no
longer required after the retentive variables have been modified. Instead, a warm start is
possible.
The retain handling function receives the value of all retentive symbolic variables, by
uploading them before the modified and newly compiled project is sent to the control
system. Once the modified program has been sent to the PLC, the system sends the
previously saved variable values back to the relevant memory addresses.
Please note:
– When adding new retentive variables:
Each newly added variable is initialized with the assigned initial value on a warm start.
If an initial value was not assigned when the new variable was declared, it is initialized
with the default value for the relevant data type.
– When modifying existing retentive variables:
The retain handling function identifies each retentive variable using its instance path,
variable name (not case-sensitive), and data type. If any one of these three items has
been modified, the retentive variable is considered a newly declared variable and
initialized (either with the declared initial value or with the default value, as described
above).
Please note that modifications within a user-defined data type result in the initialization
of all variables of this data type. Example: Following the modification of the data type
of a structure, all elements in this structure are initialized (see above).
– When deleting retentive variables:
Deleted retentive variables are not relevant for the retain handling function. However,
it may be that the remaining retentive variables are moved to the memory image of the
PLC.
– When moving retentive variables:
Please note that variables can be moved in the memory image of the PLC if variables
are added, deleted, and moved in the variables table.
With the "Download Changes" function, the retain data is only retained if the current
project has been saved to the parameterization memory.
Therefore when sending activate "Include Bootproject" (see Figure A-2 on page A-2) to
avoid inconsistencies.
For a list of control systems that support the function, please refer to Table D-1
"Phoenix Contact control systems" on page D-2.

Simulation
A4 Simulation
For processor type "IPC" control systems PC WorX can be used to develop a project
completely without hardware and to simulate operation. If you then install the hardware
according to the simulated configuration, you can start up your project on the hardware by
changing the communication path.
For an example of the simulation, please refer to Section 7, "Example Project for a
Simulation With Processor Type "IPC" Control Systems".
A5 Replacing a Control System (Hardware

Replacement)
To simply replace one control system with another, a wizard is provided for replacing
complex devices. It may be necessary to replace the control system, e.g., if you have
carried out the simulation of a project with an RFC 450 ETH-IB, but would like to use an
ILC 370 PN 2TX-IB for the actual project.
• In the "Bus Structure" window select the control system to be replaced
(RFC 450 ETH-IB in Figure A-3 on page A-9).
• Open the context menu for the control system.
• Select the "Replace..." menu item.
Figure A-3 Replacing a device
The wizard opens.

• Confirm the window that opens with "Next".
The window displays a selection of all the control systems, which can replace the control
system that is currently used in the project.
If the window is empty, the control system that is currently used cannot be replaced with
another one.

PC WorX
• Select the new control system to be used (e.g., ILC 370 PN).
Figure A-4 Selecting the new control system
• Confirm your selection with "Next".

The wizard replaces the device.
Depending on which control systems are replaced with one another, the bus topology may
have to be adapted. In addition, it may be necessary to insert additional devices.
In this example a bus coupler (IBS IL 24 BK-T/U) is connected to the RFC 450 ETH-IB.
This cannot be simply connected to the ILC 370 PN 2TX-IB. In order to continue using the
bus coupler, a terminal with remote bus branch (e.g., IBS IL 24 RB-T) must be connected
to the ILC 370 PN 2TX-IB.
If this type of adaptation is required, a window opens with a list of devices recommended
for the adaptation.
• Select the device that you would like to use for the adaptation.
Figure A-5 Selecting the device to adapt the structure

Replacing a Control System (Hardware Replacement)
The wizard indicates whether the control system was replaced successfully and also
displays special information.
Figure A-6 Completing replacement
• Confirm replacement with "Finish".

The bus configuration with the new control system is displayed.
Figure A-7 Bus configuration with new control system
In the example, an INTERBUS control system was replaced with a PROFINET IO

controller. When comparing the bus topology in Figure A-3 on page A-9 and Figure A-7 on
page A-11, you can see that the structure has been adapted accordingly as a result of
replacing the control system. The dedicated INTERBUS structure has been replaced by a
PROFINET structure.

PC WorX
In this example, it would be better to connect the Inline terminals directly to the Inline
Controller instead of using a branch terminal and a bus coupler.
• In this case, adapt the bus configuration.
• Move the Inline I/O terminals directly to the INTERBUS node of the control system.
• First delete the bus coupler (IBS IL 24 BK-T/U) and then the branch terminal
(IBS IL 24 RB-T).
Figure A-8 Manually adapted bus configuration with new control system
If a control system has been replaced with a different type of control system, as shown in
the example, the following error message is displayed in the message window: "Resource:
Invalid configuration type for resource "STD_CNF.STD_RES". The current type is
"IPC_40". However, type "ARM_L_40" is expected."
• In this case, first adapt the configuration then the resource.
• Open the context menu for the configuration and select the "Properties..." menu item.
Figure A-9 Configuration context menu: Properties

Replacing a Control System (Hardware Replacement)
• Switch to the "PLC/Processor" tab.

• Select the corresponding processor type for the control system. In the example this is
ARM_L_40.
Figure A-10 Selecting the processor type
• Confirm your selection with "Apply".

A message then informs you that under certain circumstances other parts of your project
may have to be adapted.
Figure A-11 Warning
• Confirm the warning with "OK".

• Confirm the processor type selection with "OK".

PC WorX
• Open the context menu for the resource and select the "Properties..." menu item.
Figure A-12 Resource context menu: Properties
• Switch to the "PLC/Processor" tab.

• Select the corresponding processor type for the control system. In the example this is
ILC370PN.
Figure A-13 Selecting the processor type
• Confirm your selection with "Apply".

A message then informs you that under certain circumstances other parts of your project
may have to be adapted.
• Confirm the warning with "OK".
• Confirm the processor type selection with "OK".
• Compile the project to detect any errors.
• If special POUs have been used, they must also be adapted.
• Compile the project.

Device Description Files
A6 Device Description Files
Device description files are FDCML or GSD files, which provide a complete description of
a device. If the device catalog does not contain a corresponding device description file, it
must be imported.
A 6.1 Phoenix Contact Device Description Files
When PC WorX is reinstalled, the device description files for the devices available at the
time are also installed. These descriptions are also found in the device catalog. When
installing PC WorX service packs, new device description files are installed in folder
...\FDCML10\...\Phoenix Contact. These new descriptions are not included in the device
catalog yet. They must be imported where necessary.
• Select "Phoenix Contact" in the "Device Catalog" window in PC WorX.
• Open the context menu and select "Import Device...".
Figure A-14 Device Catalog: Import Device
• Select the device description file. If you have used the suggested standard installation,
the files are located in directory
C:\Program Files\Common Files\FDCML10\xxx\Phoenix Contact.
xxx = system (e.g., ETHERNET, INTERBUS, PROFINET)
Figure A-15 Directory for the device description files
• Confirm your selection.

The message window indicates whether the device has been imported successfully.

PC WorX
A 6.2 Device Description Files for Inline Controllers
If you have used the suggested standard installation, the device description files together
with all configuration options for Inline Controllers are located in directory
C:\Program Files\Common Files\FDCML10\INTERBUS\
Phoenix Contact\modification
Figure A-16 Directory for the device description files
• Copy the required device description file to directory

...\FDCML10\INTERBUS\Phoenix Contact.
• Proceed as described above.
A 6.3 Device Description Files From Other Manufacturers

(GSD Files)
GSD files can be used to integrate devices from manufacturers other than Phoenix Contact
in PC WorX.
• Copy the GSD file for your device, e.g., from the Internet to your PC hard disk.
• Select "Phoenix Contact" in the "Device Catalog" window in PC WorX.
• Open the context menu and select "Import GSD File...".
Figure A-17 Device Catalog: Import GSD File
• Select the device description file and confirm with "Open".

Visualization
PC WorX creates an entry for the device in the device catalog. The entry is located in
directory "C:\Program Files\Common Files\FDCML10\...." (for standard installation).
The message window indicates whether the device has been imported successfully.
When reading a modular device, only the device, and not its modules, is displayed in the
bus configuration.
Manually insert the modules for these devices. To do this, proceed as follows:
• Open the module catalog via "View... Module Catalog...".
• Select the device modules one at a time from the module catalog and drag and drop
them in the lower level below the device entry.
A 6.4 Creating Device Description Files
If a device description file is not available, one can be created. For this, a device description
editor is included on the AUTOMATIONWORX Software Suite CD.
A7 Visualization
The data generated in PC WorX can be used in other programs, e.g., to visualize
processes.
In order to use the data, INTERBUS OPC Server and/or a visualization software program
are required.

PC WorX
A8 Ethernet Topology
PC WorX can be used to automatically detect Ethernet topologies. All the Ethernet devices
in the project can be displayed with connections in the "Ethernet Topology" window. For all
devices with LLDP functions, the connections are displayed automatically with the port
number.
The other functions are explained in the example. A complete bus configuration is required.
• Open the window via "View... Ethernet Topology".
• In the "Ethernet Topology" window, select "Topology... Refresh" in the context menu.
Figure A-18 Refreshing the topology for the first time
A device must now be selected as the starting point for the representation. Since
connections are only automatically created between devices with LLDP functions, it is
useful to select this type of device.
• Double-click on the switch.
• Activate the "Use device as root element of representation" option in the window that
opens.

Ethernet Topology
Figure A-19 Specifying the starting point for the representation
• Refresh the representation via the "Topology... Refresh" context menu.
Figure A-20 Topology with all automatically detected connections
If not all connections are displayed, proceed as follows to include the connections that are
not displayed:
• In the context menu of the "Ethernet Topology" window select "Edit... Link Mode".
• Press and hold down the mouse button over a device and draw a line to the device it
is connected to.
• Repeat this step for all connections.
• Set the link mode ("Edit... Link Mode" in the context menu).
The data that you wish to be displayed in the topology can be specified in the context menu
of the "Ethernet Topology" window via "Topology... Settings".

PC WorX
To create a visual assignment between the icons and the actual system, an image can be
placed in the background.
• Create an image and place it in the relevant directory on your PC.
• In the context menu of the "Ethernet Topology" window select "Topology... Settings".
• Open the "Background Image" tab.
• Import the image.
• Activate the "Display" checkbox.
• Select the image under "Settings".
• Adjust the transparency and zoom.
Figure A-21 Settings for the background image
• Confirm your settings with "Apply" and "OK".

• Position the icons on the image.
Figure A-22 Ethernet devices in the system

Ethernet Topology
Further options:
– The device context menu can be used to open the web interface of the device
(if present; e.g., for the switch).
– The context menu of the "Ethernet Topology" window and the device context menu
can be used to make various settings.
– The connection information is displayed by double-clicking on an automatically
created connection or a port number.
– The window context menu ("Topology... Print...") can be used to print the topology.
– If the "Online View... Show Accessibility" menu item is selected via the context menu
of the "Ethernet Topology" window, the accessibility of all devices is displayed.
Devices that can be accessed are indicated with a green dot, devices that cannot be
accessed are indicated with a red dot with a white cross. Changes to the connection
status are displayed when the view is refreshed.
Figure A-23 Topology with connection error
Options for Refreshing the Topology:

– Refresh the topology using the shortcut Ctrl + Shift + F5.
– Manual refresh via the context menu of the "Ethernet Topology" window
"Topology... Refresh".
– Automatic refresh according to the predefined refresh time.
Specify the time for automatic refresh as follows:
• Open the context menu of the "Ethernet Topology" window.
• Select "Topology... Settings...".
• Select the "Refresh" tab.
• Activate the "Cyclic Refresh" checkbox and set a "Spacing".

PC WorX
Figure A-24 Specifying the time for refreshing the topology

INTERBUS Topology
A9 INTERBUS Topology
PC WorX can be used to automatically detect INTERBUS topologies. The INTERBUS

structure can be viewed in the "INTERBUS Topology" window.
Figure A-25 INTERBUS topology for an INTERBUS system
If this function is used with PROFINET, only the INTERBUS topology is displayed that is
connected to the INTERBUS node for the control system.
To print the entire bus topology, another function can be used in PC WorX:
• In the bus configuration, activate the context menu via any element.
• Select the "Print Bus Configuration" menu item.

PC WorX
A 10 Comparing Projects
The "Project... Compare Projects" menu can be used to compare two compiled projects.
• Open the first of the projects to be compared.
• In the "Project" menu select the "Compare Projects" menu item.
• In the dialog box that opens, open the second of the projects to be compared.
• Open the project comparison workspace.
All the differences are displayed in table format in the "Project Comparison Result
Window".

Status Information for a PROFINET IO System
B Status Information for a PROFINET IO System
B1 Status of the PROFINET IO Controller
The PROFINET IO controller has status information that indicates its configuration status.
This can be requested via the system variable PNIO_CONFIG_STATUS. The system
variable is available as a word and as individual bits under "Global_Variables".
Figure B-1 System variable PNIO_CONFIG_STATUS
PNIO_CONFIG_ The variable is set if the PROFINET IO controller has been initialized correctly. No desired
STATUS_READY configuration has been loaded by PC WorX yet.
PNIO_CONFIG_ The variable is set if the desired configuration for the PROFINET IO controller has been
STATUS_ACTIVE loaded. In this state the PROFINET IO controller attempts to establish a connection
cyclically to all devices in the desired configuration (under the PROFINET icon). In this
way, it attempts to find each device with the corresponding "PROFINET device name" in
the current subnetwork.
If the connection to a PROFINET IO device has been established successfully, the
corresponding "PNIO_DATA_VALID" process data item is set.
For inaccessible devices, the PROFINET IO controller cyclically attempts to establish a
connection approximately every 5 seconds.
A connection cannot be established, e.g., if the corresponding device is ready, but a
correct PROFINET device name has not yet been assigned to it.
PNIO_CONFIG_ This system variable is set if an error occurred when configuring the PROFINET IO
STATUS_FAULT controller.
7127_en_02 PHOENIX CONTACT B-1

PC WorX
B2 Status of a PROFINET IO Device
The status of a PROFINET IO device can be requested using predefined process data.
The "~PNIO_DATA_STATE" byte that contains corresponding status bits is available. A
PROFINET IO device only provides valid data if this bit is set.
PNIO_DATA_VALID For PROFINET IO, it may be normal during operation that a PROFINET IO device within
the network cannot be accessed (e.g., undocking devices).
Use this variable to specify for your application whether or not the operation of all other
PROFINET IO devices is to be continued despite a device failure.
In both cases the application program must receive information on whether a
PROFINET IO device is supplying valid data or not. This is why each PROFINET IO device
has a PNIO_DATA_VALID process data item.
Only if this bit is set does the PROFINET IO device supply valid data and all other process
values are valid.
PNIO_IS_PRIMARY This process data item is reserved for future redundancy functions.
PNIO_APPL_RUN This bit indicates that the application is running on the PROFINET IO device.
PNIO_NO_DIAG If this bit is set, no device diagnostics are present.
Not all bits of the "~PNIO_DATA_STATE" byte are used. To prevent unused bits being
used by mistake, hide them in the control program by linking to a corresponding bit mask.
To request the status, assign the process data to variables.

• Switch to the process data assignment workspace.
• In the top left window, "Symbols/Variables", select the "STD_RES : ILC350PN"
resource.
data to variables (e.g., ILB PN 24 DI16 DIO16-2TX).
• Select the variable in order to link it (e.g., PNIO_NO_DIAG).
• If variables have already been created, use drag & drop to link the selected variable
with one of the variables on the left-hand side.
If a corresponding variable has not yet been created, select "Create Variable" in the
context menu.
B-2 PHOENIX CONTACT 7127_en_02

INTERBUS register
Figure B-2 Status of a PROFINET IO device
B3 INTERBUS Register
The registers for an INTERBUS master are directly available as process data. If necessary,
assign the corresponding process data to the variables for the control system.
Figure B-3 INTERBUS register
7127_en_02 PHOENIX CONTACT B-3

PC WorX
B4 Setting All PROFINET IO Devices to a Defined State
In many cases, a machine/system can no longer be operated in the event of a

PROFINET IO device failure. This is a standard situation in modern INTERBUS systems
where neither bus couplers nor isolated disconnection are used.
In the example system, a PROFINET IO device failure does not affect the operation of all
the other PROFINET IO devices. If you would like to set all the outputs to a defined state
in the event of an error, system variable PNIO_FORCE_FAILSAFE can be used. This can
be found in the IEC programming workspace under "Global_Variables".
Figure B-4 System variable PNIO_FORCE_FAILSAFE
If the variable is set, all the PROFINET IO devices output zero points or defined substitute
values (the substitute values are currently set to "0" by default). The corresponding inputs
are set to zero.
B-4 PHOENIX CONTACT 7127_en_02

AX OPC Server and WebVisit
C AX OPC Server and WebVisit
C1 AX OPC Server
For information on using AX OPC Server, please refer to the corresponding

documentation.
AX OPC Server includes:
– The "OPC Configurator" for establishing a connection between PC WorX and an OPC
client (e.g., Visu+).
– An "OPC Test Client" for testing the connection.
AX OPC Server is also installed as a demo version. To register your license, proceed as
follows:
• Start the "OPC Test Client".
• In the taskbar, activate the context menu for the "OPC Test Client" icon.
Figure C-1 Registering the "OPC Test Client"
• Select the "Register" menu item and enter the registration code.
C 1.1 Preparatory Tasks in PC WorX
• In order to use a variable in AX OPC Server, activate the "OPC" checkbox:

– When creating variables in the "Variable Properties" window (Figure C-2)
– In the variables worksheet (Figure C-3)
Figure C-2 Creating variables for AX OPC Server
7127_en_02 PHOENIX CONTACT C-1

PC WorX
Figure C-3 Activating "OPC" in the variables worksheet
• When sending the project, activate the "Include OPC data" checkbox.
Figure C-4 Download: Include OPC data
C 1.2 OPC Configurator
• Start the "OPC Configurator" program.

The configurator commands can be accessed via context menus.
• Select the resource type.
Figure C-5 Selecting the resource type
C-2 PHOENIX CONTACT 7127_en_02

AX OPC Server
• Open the context menu for the "TestResource" entry.

• Select the "Settings" menu item.
Figure C-6 Settings
• Under "IP Address" enter the IP address for the control system for which you would
like to use the OPC data.
Figure C-7 Specifying the IP address for the control system
This completes the configuration for using OPC data through an OPC client.
Figure C-8 OPC configuration completed

PC WorX
C 1.3 OPC Test Client
Test Client can be used to test the OPC configuration.

• Open the "OPC Test Client" program.
• Set the connection data in the window that opens.
Figure C-9 Setting connection data
• Click on "Browse" and select the OPC server.
Figure C-10 Selecting the OPC server

The OPC server and the PC where the OPC server is located are entered.
Figure C-11 Connection to OPC server selected
• Confirm your selection with "Connect".

AX OPC Server
• Activate the context menu for "Private Groups".
Figure C-12 Private Groups
• In the window that opens, enter the name of the group (e.g., "Quickstart_PN") and
confirm your entry with "OK".
Figure C-13 Entering the name of the group

PC WorX
• Activate the context menu for the created group.

• Select the "Add all Items" menu item.
Figure C-14 Add all Items
All variables defined as OPC variables are displayed.
Figure C-15 OPC variables

AX OPC Server
The connection between PC WorX, OPC, and Test Client can now be tested via the
context menu for the individual variables.
Figure C-16 OPC variables
The result is displayed at the bottom of the window.

PC WorX
C2 WebVisit
The WebVisit software is used to visualize the global variables of the Inline Controllers
used under PC WorX. WebVisit is a software tool used to generate web pages. The
software runtime component is a web server, which is stored in PC WorX. The variable
values are actually visualized via a Java-compatible standard browser.
To visualize variables from your PC WorX project in WebVisit, activate the "PDD"
checkbox:
– In the "Variable Properties" window (Figure C-17)
– In the variables worksheet (Figure C-18)
Figure C-17 Creating variables for WebVisit
Figure C-18 Activating "PDD" in the variables worksheet
When compiling the project, a file called "pdd.csv" is generated, which is used by WebVisit
for the visualization.
In WebVisit, enter the PC WorX project used (recommended) or the corresponding
pdd.csv file. For standard installation:
– The project is located in directory
C:\Program Files\Phoenix Contact\Software Suite ...\Projects
– The corresponding pdd.csv file is located in directory C:\Program Files\Phoenix
Contact\Software Suite ...\Projects\xxx\C\STD_CNF\R\STD_RES
(xxx = project name)
For information on using WebVisit, please refer to the corresponding documentation.

Overview of Phoenix Contact Control Systems
D Overview of Phoenix Contact Control Systems

Table D-1 provides an overview of Phoenix Contact control systems together with the
processor types and hardware and firmware versions used, and the resulting functions.
When creating a new project, several versions are provided for different control systems.
The versions differ with regard to the hardware and firmware version used.
If a control system is inserted in a project without a template, depending on the hardware
and firmware version, the processor type of the control system used must be specified.
Select the processor type according to Table D-1.
Some of the functions depend on the type of processor used. For example, the "Download
Changes" function is only available for control systems with an "IPC_40" or "ARM_L_40"
processor.
If a project is created in PC WorX and a processor type is selected, which does not
correspond to the processor used on your control system, this may result in the following:
– Fewer functions can be used even though your processor supports more
– Functions are displayed under PC WorX, which your processor does not support
Key for Table D-1:

HW: Hardware version
FW: Firmware version
Example:
You have an ILC 350 ETH Inline Controller.
Marked version 01/46F/120
This corresponds to:
Hardware version 01
Firmware version 4.6F/1.2
Select the ILC 350 ETH with ARM_L_40 according to the table.
If a controller is used with a firmware version, which is not listed in the table, select the older
firmware version. For an ILC 350 ETH controller with firmware 1.15, select ARM_L_32
(firmware Version 1.13 or later).
7127_en_02 PHOENIX CONTACT D-1

D-2
PC WorX
PHOENIX CONTACT
Table D-1 Phoenix Contact control systems
Control System Processor From From Master/Slave Supported by Function Supported

HW FW Function AX OPC Server Download Extended Simulation
Changes Retain
Handling
CP 306 ETH ARM_L_40 00 4.6F/1.2 No No Yes Yes No
FC 200 PCI M68_32 10 4.6C No No No No No
FC 350 PCI ETH ARM_L_32 01 4.6F/1.13 No No No No No
ARM_L_40 01 4.6F/1.2 No Yes Yes Yes No
ARM_L_40 01 4.6F/1.41 Yes Yes Yes Yes No
ILC 150 ETH eCLR 01 1.00/0.10 No Yes No Yes No
ILC 200 IB M68_32 12 4.6C Yes No No No No
ILC 200 UNI M68_32 01 4.6C Yes No No No No
ILC 350 ETH ARM_L_32 01 4.6F/1.13 No No No No No
ARM_L_40 01 4.6F/1.2 No Yes Yes Yes No
ILC 350 ETH/M ARM_L_40 02 4.6F/1.2 No Yes Yes Yes No
ILC 350 PN ARM_L_32 01 4.6F/1.3 No No No No No
ILC 370 ETH 2TX-IB ARM_L_40 01 4.6F/1.2 Yes Yes Yes Yes No
ILC 370 ETH 2TX-IB/M ARM_L_40 01 4.6F/1.2 Yes Yes Yes Yes No
ILC 370 PN 2TX-IB ARM_L_40 01 4.6F/1.40 Yes Yes Yes Yes No
ILC 370 PN 2TX-IB/M ARM_L_40 01 4.6F/1.42 Yes Yes Yes Yes No
ILC 390 ETH 2TX-IB ARM_L_40 01 4.6F/1.43 Yes Yes Yes Yes No
RFC 430 ETH-IB IPC_32 31 4.6D/4.20 No No No No Yes
IPC_40 31 4.6D/5.00 No No Yes Yes Yes
RFC 450 ETH-IB IPC_32 31 4.6D/4.20 No No No No Yes
IPC_40 34 4.6D/5.00 No No Yes Yes Yes
S-MAX 406 CE IPC_32 00 4.6F/1.10 No Yes No No Yes
7127_en_02
S-MAX 406 CE PN IPC_40 00 4.6F/1.41 No Yes Yes Yes Yes

PC WORX Quickstart IT

Uploaded by

Copyright:

Available Formats

PC WORX Quickstart IT

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

PC WORX Quickstart IT

Uploaded by

Copyright:

Available Formats

AUTOMATIONWORX

Order No.: 2699862

This user manual is valid for:

7127_en_02 PHOENIX CONTACT

Please Observe the Following Notes

User Group of This Manual

Explanation of Symbols Used

We Are Interested in Your Opinion

PHOENIX CONTACT GmbH & Co. KG

PHOENIX CONTACT 7127_en_02

General Terms and Conditions of Use for Technical Documentation

7127_en_02 PHOENIX CONTACT

Statement of Legal Authority

Make sure you always use the latest documentation.

A conversion table is available on the Internet at:

PHOENIX CONTACT 7127_en_02

2 Installing and Enabling the Software .......................................................................................2-1

3 Helpful Information on PC WorX .............................................................................................3-1

4 Sequence for Creating a Project .............................................................................................4-1

7127_en_02 PHOENIX CONTACT i

4.9 Manually Inserting INTERBUS Devices ........................................................... 4-12

ii PHOENIX CONTACT 7127_en_02

5 Example Project for an INTERBUS System ............................................................................5-1

6 Example Project for a System Consisting of PROFINET IO and INTERBUS .........................6-1

7127_en_02 PHOENIX CONTACT iii

9 PC WorX and SafetyProg........................................................................................................9-1

iv PHOENIX CONTACT 7127_en_02

A Additional Software Functions ................................................................................................ A-1

B Status Information for a PROFINET IO System ..................................................................... B-1

C AX OPC Server and WebVisit ................................................................................................ C-1

D Overview of Phoenix Contact Control Systems...................................................................... D-1

7127_en_02 PHOENIX CONTACT v

vi PHOENIX CONTACT 7127_en_02

PC WorX is the automation software, which combines programming according to

1.2 Information About This Manual

1.3 System Requirements

1.3.1 Supported Operating Systems

– Windows 2000 SP3

7127_en_02 PHOENIX CONTACT 1-1

1.3.2 Hardware Requirements

Hardware Requirements for PC WorX

1.4 Ordering Data

Designation Order Description

1-2 PHOENIX CONTACT 7127_en_02

2 Installing and Enabling the Software

2.1 Prior to Installation

Prior to installation, close all open Windows applications.

2.2 AUTOMATIONWORX Software Suite

PC WorX is part of the AUTOMATIONWORX software suite.

7127_en_02 PHOENIX CONTACT 2-1

2.3 Starting the Installation Program

• Insert the "AUTOMATIONWORX Software Suite" CD in your CD-ROM drive. The

2.4 Starting PC WorX

• For installation using the default settings, start PC WorX via

2.5 Enabling the PC WorX License

After starting PC WorX, proceed as follows to enable your license:

2-2 PHOENIX CONTACT 7127_en_02

3 Helpful Information on PC WorX

3.2 Changing the Language

Figure 3-1 Changing the language setting