AUTOMATIONWORX

Quick Start Guide

UM QS EN CONFIG+

Order No.: 2699697

Config+
AUTOMATIONWORX

Quick Start Guide

Config+

11/2006

Designation: UM QS EN CONFIG+

Revision: 01

Order No.: 2699697

This user manual is valid for:

Designation Revision Order No.

CONFIG+ 1.10 or later 2868059
CONFIG+ DEMO 1.10 or later 2868046
CONFIG+ CPY 1.10 or later 2868062

6957_en_01 PHOENIX CONTACT

Config+

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 20 21
E-mail [email protected]

PHOENIX CONTACT 6957_en_01

 Config+

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.
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.

6957_en_01 PHOENIX CONTACT

Config+

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 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 6957_en_01

 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

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

2.1 Before Installation ............................................................................................. 2-1
2.2 Starting the Installation Program ........................................................................ 2-1
2.3 Enabling the Config+ License ............................................................................ 2-1
2.4 Starting Config+ ................................................................................................. 2-2

3 Example Project .....................................................................................................................3-1

3.1 Creating a New Project ...................................................................................... 3-2
3.2 Creating the Bus Structure ................................................................................. 3-3
3.2.1 Automatically Reading the Bus Structure via the Controller Board .... 3-3
3.2.2 Creating the Bus Structure Manually ................................................3-10
3.3 Configuring and Describing Devices ................................................................3-12
3.3.1 Modifying the Controller Board Settings ...........................................3-14
3.3.2 Modifying the Device Settings ..........................................................3-15
3.4 Controller Board Extended Settings.................................................................3-16
3.5 Process Data Assignment ................................................................................3-18
3.5.1 Automatic Assignment of Inputs and Outputs ..................................3-18
3.5.2 Manual Assignment of Inputs and Outputs ....................................... 3-20
3.6 Parameterization ..............................................................................................3-23
3.6.1 Execute Parameterization (RAM) .....................................................3-24
3.6.2 Saving the Parameterization to the Parameterization Memory ........3-25

4 Diagnostics .............................................................................................................................4-1

6957_en_01 PHOENIX CONTACT i

Config+

ii PHOENIX CONTACT 6957_en_01

 General

1 General

1.1 Introduction

Config+ is a software tool used to configure and start up bus systems.

In Config+, all functions can be easily accessed via the menus and a bus configuration can
be created in just a few steps.

1.2 Information About This Manual

This manual helps you to parameterize a bus structure and to start up INTERBUS using
an example project.
It is assumed the user has knowledge and experience in the operation of PCs and
Microsoft Windows operating systems.

More detailed information about the individual functions 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 controller board can be
executed without a physical bus structure.
However, complete configuration without a physical bus structure is also possible.

1.3 System Requirements

Supported Operating Systems

– Windows 2000
– Windows XP (recommended)

Hardware Requirements

Hardware Requirements for Config+

CPU Pentium 800 MHz
Main memory 256 MB, minimum
Hard disk 400 MB (without browser)
CD-ROM drive Yes
Interfaces 1 x serial, Ethernet
Monitor SVGA, 800 x 600 pixel resolution,
1024 x 768 (recommended)
Operating devices Keyboard, mouse

6957_en_01 PHOENIX CONTACT 1-1

Config+

1-2 PHOENIX CONTACT 6957_en_01

 Installing and Enabling the Software

2 Installing and Enabling the Software

2.1 Before Installation

Before starting installation, close all open Windows applications.

2.2 Starting the Installation Program

• Insert the CD-ROM in the drive.

The installation program 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 in-
stallation process.
• Follow the instructions in the installation program.

The installation program generates all the directories required for operation and copies the
files to the directory specified during installation.
• Following successful installation, restart your PC to activate the changes to the con-
figuration files. To do this, click "Finish" at the end of the installation process.

2.3 Enabling the Config+ License

The License Manager provides an overview of all the Phoenix Contact programs the rele-
vant license applies to. The License Manager is automatically installed in the same direc-
tory when Config+ is installed.
• Start the License Manager via "Start... Programs... Phoenix Contact...
License Manager" in the taskbar, if Config+ has been installed with the default set-
tings.

6957_en_01 PHOENIX CONTACT 2-1

Config+

Figure 2-1 License Manager

• Enter the license key for the program you wish to use. The cursor automatically jumps
to the next field.
• If the license key is valid, the Phoenix Contact programs that are installed, their ver-
sion, and whether your license is valid for them are displayed in a table.
• Close the License Manager.
The full license is enabled when Config+ is started.

2.4 Starting Config+

• Start Config+ via "Start... Programs... Phoenix Contact... Config+ 1" in the taskbar, if
Config+ has been installed with the default settings.

Without a valid license key Config+ runs in DEMO mode, i.e., created projects and
project modifications cannot be saved on the PC.
We recommend the full version for the example project in this user manual.

2-2 PHOENIX CONTACT 6957_en_01

 Installing and Enabling the Software

Overview of Windows in Config+

The windows in Config+ are arranged in the following way (the "Bus Configuration" work-
space is set by default):
Menu bar
Toolbar

Bus Structure

Device Details

Device Catalog

Output Window

Status bar

Figure 2-2 "Bus Configuration" workspace

The workspace can be changed via the toolbar:

The left icon (default) opens the "Bus Configuration" workspace with the "Bus Structure",
"Device Catalog", "Device Details", and "Output Window" windows.

The second icon from the left opens the "Process Data Assignment" workspace with the
"Process Data Assignment" and "Output Window" windows.

The third icon from the left opens the "Read INTERBUS" workspace, which is pre-assigned
with the "Bus Structure", "Device Details", and "Output Window" windows.

The fourth icon from the left opens the "Diagnostic" workspace, which is pre-assigned with
the "Bus Structure", "Device Details", "Diag+", and "Output Window" windows.

The fifth icon from the left opens the "FDT" workspace, which is pre-assigned with the "Bus
Structure", "Device Details", and "Output Window" windows.

The right icon opens the "User defined" workspace, which is pre-assigned with the "Bus
Structure", "Device Details", and "Output Window" windows.

6957_en_01 PHOENIX CONTACT 2-3

Config+

If you wish to change the user-defined workspaces, proceed as follows:

• Open the required window via the "View" menu and move it to the desired location us-
ing drag & drop.

If a window is opened or closed, the workspace retains this setting, even following a pro-
gram restart.

While holding down the CTRL key, the non-docked windows can be shifted to any posi-
tion.

2-4 PHOENIX CONTACT 6957_en_01

 Example Project

3 Example Project
The following modules are selected for the example project:

Controller board IBS S7 400 ETH DSC/I-T

Remote bus modules IL IB BK
ILB IB 24 DI16 DO16
Local bus modules IB IL 24 DO 2-2A
IB IL 24 DI 16
IB IL 24 DI 4
IB IL AO 2/SF
IB IL AI 2/SF
According to the installation specifications, a bus configuration with these modules must
have the following structure:

IB S S 7 4 0 0 E T H D S C /I-T
2 -2 A

IB IL 2 4 D I 1 6

IB IL A O 2 /S F
IB IL A I 2 /S F
IB IL 2 4 D I 4
IB IL 2 4 D O
IL IB B K

B A R D U L U S 1 D 1 D 1 1 1 1 D D D
2 2 2 2 2 2 O -S
R C L D U M 3 3 3 3 3
4 4 4 4 4
IB B K D O 2 -2 A D I1 6 D I4 A O 2 A I2

1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2
IN 1 0
IN 1 3
IN 1 4
IN 1
IN 2
IN 5
IN 6
IN 9

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
IN 1 1
IN 1 2
IN 1 5
IN 1 6
IN 3
IN 4
IN 7
IN 8

4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

5 5 5 5 5 5 5 5 5 5

6 6 6 6 6 6 6 6 6 6

IL B IB 2 4 D I1 6 D O 1 6

U L B A U S E U A 1 1 E 1 1 E 1 1 E 1 1 1
U A 2 2 2 2 2 2 2 2 2
R C R D 3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4
B U S 1 B U S 2 O 1 O 2 O 3 O 4 I1 I2 I3 I4

1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5

6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6

6 9 5 7 A 0 0 1

Figure 3-1 Bus structure for the example project

6957_en_01 PHOENIX CONTACT 3-1

Config+

3.1 Creating a New Project

To create a new project, proceed as follows:

• Select the "New" command from the "File" menu.
• Save the project using the "File... Save As" command (not available in DEMO mode)
and enter a name for the project in the dialog box that follows (e.g., System01).
This creates a new project.

Figure 3-2 Basic structure of a project

The "Untitled" and "Unconnected" elements are the basic elements of a project. They
cannot be deleted.

Describing the Project

The "Untitled" element is automatically renamed in the file name when the project is saved.

Figure 3-3 Device Details: Project name

3-2 PHOENIX CONTACT 6957_en_01

 Example Project

3.2 Creating the Bus Structure

3.2.1 Automatically Reading the Bus Structure via the Controller

Board

• Manually select the controller board as the first element. The connected bus devices
cannot be read via the controller board unless it is selected as the first element.
A physical bus structure must be available and the controller board must be connected
to the PC. The controller board must also be supplied with power.
• Open the "Phoenix Contact" entry in the Device Catalog.

Figure 3-4 Device Catalog

Figure 3-5 Phoenix Contact device catalog opened

6957_en_01 PHOENIX CONTACT 3-3

Config+

Controller board: • Select the "SIMATIC® S7" entry in the Phoenix Contact device catalog.
SIMATIC® S7

Figure 3-6 Phoenix Contact device catalog: SIMATIC® S7

PLC card: • Under "PLC card", select the controller board to be inserted with the appropriate hard-
IBS S7 400 ETH DSC/I-T ware and firmware version. In the example, the IBS S7 400 ETH DSC/I-T card with re-
vision 20/4.63 is used.

Figure 3-7 Selecting the controller board

The controller board hardware and firmware version is specified on a label on the device.
The version specified on the controller board label must be the same or later than the
hardware and firmware version of the controller board in Config+.

• Drag & drop the highlighted controller board to the "Bus Structure" window to the right
of the "System01" element.

3-4 PHOENIX CONTACT 6957_en_01

 Example Project

Figure 3-8 Moving the controller board to the bus structure

Prohibited position: Permitted position: Permitted position:

Cannot be inserted here Insert in the lower level Insert at the same level
The controller board is inserted below the "System01" element, which represents the entire
higher-level project. All modules that are controlled by the controller board are then in-
serted below the controller board. Modules that are on the same bus level (e.g., in the
same remote bus branch) are inserted on the same level.

The prohibited symbol appears when a device from the Device Catalog is moved to an
element in the Bus Structure but cannot be inserted. The mouse pointer changes into an
insertion symbol at positions where the element can be inserted.

Figure 3-9 shows the full screen with an inserted controller board ("Bus Configuration"
workspace).

6957_en_01 PHOENIX CONTACT 3-5

Config+

Figure 3-9 Project with inserted controller board

3-6 PHOENIX CONTACT 6957_en_01

 Example Project

Setting the Communication Path

Set the communication path between the programming PC with Config+ and the controller
board.
• Highlight the controller board in the "Bus Structure" window.
• Select the "Communication" tab in the "Device Details" window.
• Select the communication path to the control system.

Figure 3-10 Communication path

Specify the IP address of the controller board used when communicating via TCP/IP (see
IBS S7 400 ETH DSC QS UM E controller board user manual (Order No. 2743983)).

• Check the specified communication path and therefore the IP address by clicking
"Test".
If a green status indicator appears in the window, the communication path has been tested
successfully .
If a red status indicator appears, either no physical bus structure is available or the control-
ler board cannot be accessed via the set communication path or is disconnected. Check
the communication path and change, if necessary.

Import your settings to the project via "Apply".

6957_en_01 PHOENIX CONTACT 3-7

Config+

• Select the "Read INTERBUS" workspace and select the IBS S7 400 ETH DSC/I-T
controller board in the "Selected Control System" field.
The connected bus structure is read and displayed in the "Connected Bus" window.
• Right-click on the controller board in the "Connected Bus" window.
• In the context menu, click "Import to Project... With Device Description". This displays
the ID code and process data length of the device.
• If necessary, select the "All" device catalog in the "Catalog Selection" window.
The controller board reads the devices with their ID code and process data length. As the
combination of ID code and process data length cannot always be assigned clearly, select
the corresponding device from the list (see Figure 3-11).
• Specify all the devices one after the other by double-clicking on them to select them
from the list. A new dialog box with a new list appears for each device.

Figure 3-11 Select Device

The complete bus structure for the example project is illustrated in Figure 3-12.

Figure 3-12 Bus structure for the example project

3-8 PHOENIX CONTACT 6957_en_01

 Example Project

• Switch to the "Bus Configuration" workspace.

When connected, each device receives a process data description for IN process data
and/or a process data description for OUT process data. For information on assignment to
control system addresses, please refer to section "Controller Board Extended Settings" on
page 3-16.
• Save the project on the PC via the "File... Save" menu or via the "Save" icon in the
toolbar (not available in DEMO mode).

6957_en_01 PHOENIX CONTACT 3-9

Config+

3.2.2 Creating the Bus Structure Manually

If the bus is not yet physically installed or the controller board cannot be accessed directly
from Config+, the bus structure can be created manually.

When inserting manually, please note that no local bus devices can be inserted in the
remote bus. Likewise, no remote bus devices can be inserted in the local bus.

The bus structure required for the example project is now created.
• Insert the controller board as the first element and set the communication path. Pro-
ceed as described in section "Automatically Reading the Bus Structure via the Con-
troller Board" on page 3-3.
Now insert the Inline terminals required for the project:
• Open the "IL" entry in the Device Catalog.

Figure 3-13 Phoenix Contact IL (Inline Modular) device catalog

• Select the IL IB BK terminal from the "Bus Coupler" entry.

Figure 3-14 Selecting the bus coupler

3-10 PHOENIX CONTACT 6957_en_01

 Example Project

• Move the bus coupler to the bus structure and insert it below the controller board (low-
er level, i.e., either drag & drop it next to the controller board or drag & drop it directly
onto the controller board with the shift key pressed).

Figure 3-15 Project with inserted bus coupler

• Insert the other required Inline terminals below the bus coupler (lower level) in the fol-
lowing order:
1. I/O digital IB IL 24 DO 2-2A
2. I/O digital IB IL 24 DI 16
3. I/O digital IB IL 24 DI 4
4. I/O analog IB IL AO 2/SF
5. I/O analog IB IL AI 2/SF

The order of the terminals can be changed at any time using drag & drop or via the con-
text menu (right mouse button).

If you wish to insert an element, even though the bus structure does not actually permit
this, but no prohibited symbol appears, the program does not execute the action and the
corresponding error message appears in the Output Window.

• Insert the ILB IB 24 DI16 DO16 Inline Block IO module in the same level as the bus
coupler.
The complete bus structure for the example project is illustrated in Figure 3-16.

Figure 3-16 Bus structure for the example project

• Save the project on the PC via the "File... Save" menu or via the "Save" icon in the
toolbar (not available in DEMO mode).

6957_en_01 PHOENIX CONTACT 3-11

Config+

3.3 Configuring and Describing Devices

Various tabs for configuring and describing the controller board and devices are available
in the "Device Details" window.
Some cells have preset data, others are empty. If you wish to modify the information in the
individual tabs, proceed as follows:
• Highlight the relevant device in the "Bus Structure" window.

The arrangement of the tabs varies depending on the device type (controller board, I/O
terminal, etc.).
All cells that can be edited have a white background. Cells that have a gray background
cannot be edited.

• Double-click in the "Value" column to activate the cell to be modified.

There are various ways of entering values in the cells:
– Enter the information as text (e.g., control system name)

Figure 3-17 Entering the information as text

– Select a value from the drop-down menu (e.g., baud rate)

Figure 3-18 Selecting a value from the drop-down menu

– Set the value using the slider or enter the value manually (e.g., bus warning time)

Figure 3-19 Setting the value using the slider

3-12 PHOENIX CONTACT 6957_en_01

 Example Project

INTERBUS Settings The "INTERBUS Settings" tab is used to describe the basic settings of an INTERBUS de-
vice.

Extended Settings Settings specific to the controller board are specified in the "Extended Settings" tab
(e.g., the "I/Q Operation Mode" for S7 controller boards (direct or extended)). For more de-
tailed information on these settings, please refer to the online help.

Communication The "Communication" tab can be used to set the communication path for the controller
board (e.g., serial interface, TCP/IP, see section "Setting the Communication Path" on
page 3-7).

Parameterization Memory The parameterization memory of the controller board is formatted in the "Parameterization
Memory" tab and files are written, read or deleted here.

@X Settings Application programs for PCP devices are assigned in this tab. Nothing is set in this tab for
this example project. For more detailed information, please refer to the online help.

IB G4 Service Editor The "IB G4 Service Editor" tab can be used to execute INTERBUS G4 services on the con-
troller board.

Parameter Channel The "Parameter Channel" tab indicates the supported PCP services and PDU sizes.

Bus Interfaces The "Bus Interfaces" tab indicates the number and type of available bus interfaces.

Process Data The "Process Data" tab indicates the assignment of the terminal point and
bit/byte position of the device process data transmitted via the bus.

Terminal Points The "Terminal Points" tab indicates the device terminal points to which the sensors, actu-
ators, supply voltage, etc. are connected.

Data Sheet The "Data Sheet" tab displays the device data sheet.

6957_en_01 PHOENIX CONTACT 3-13

Config+

3.3.1 Modifying the Controller Board Settings

The description of tabs and the procedure for modifying values can be found in section
"Configuring and Describing Devices" on page 3-12.
In this example project, the following information is specified for the controller board:
• Enter "Door assembly" under "Station Name".
• Enter "Controller 24a" under "Device Name".

Figure 3-20 Describing the controller board

Detailed information on the controller board in this example project can be found in the
IBS S7 400 ETH DSC QS UM E controller board user manual (Order No. 2743983).

3-14 PHOENIX CONTACT 6957_en_01

 Example Project

3.3.2 Modifying the Device Settings

Devices have a different set of tabs than controller boards. The description of these tabs
and the procedure for modifying values can be found in section "Configuring and Describ-
ing Devices" on page 3-12.
In this example project, the following information is specified for the IB IL AO 2/SF:
• Enter "Door assembly" under "Station Name".
• Enter "Voltage display" under "Device Name".

Figure 3-21 Describing a device

6957_en_01 PHOENIX CONTACT 3-15

Config+

3.4 Controller Board Extended Settings

An example project can be found in the IBS S7 400 ETH DSC QS UM E controller board
user manual (Order No. 2743983).

This section only describes the settings for S7 controller boards.

For information on the settings for other controller boards, please refer to the online help.

• Select the "Bus Configuration" workspace.

• Highlight the controller board in the "Bus Structure" window.
• Select the "Extended Settings" tab in the "Device Details" window.

Basic Settings • Select "Direct I/Q Operation Mode" under "Basic Settings".

Data Blocks • Select the "Data Blocks" item (see Figure 3-22).

Figure 3-22 Controller board extended settings: Data blocks

In this window, specify the address area for the controller board in INTERBUS.

3-16 PHOENIX CONTACT 6957_en_01

 Example Project

In this example project, the entire S7 area is used for INTERBUS, thus no modifications
are required here.
The extended addresses are not used in this example project.
If you wish to modify the address areas, proceed as follows:
• Enter the first byte of the corresponding data block in the "S7 Address" column. The
data blocks must not overlap.
• Modify the data block size in the "Length" column. The maximum length of each entry
is 128.

Error messages, e.g., due to area overlaps, are displayed in the Output Window.

6957_en_01 PHOENIX CONTACT 3-17

Config+

3.5 Process Data Assignment

The inputs and outputs of bus devices are assigned to control system addresses in the
"Process Data Assignment" workspace. Here, the inputs and outputs are connected to the
controller board.

3.5.1 Automatic Assignment of Inputs and Outputs

If you wish to assign inputs and outputs automatically, proceed as follows:

• Select the "View... Process Data Assignment" menu or switch to the "Process Data As-
signment" workspace via the icon in the toolbar.
• Highlight the controller board.
• Right-click on an entry in the list under the bus structure and click
"Filter... Standard Process Data" in the context menu (see Figure 3-23 on page 3-18).

Standard Process Data describes the entire module. This means that an IB IL 24 DI 16
is addressed with a single IN process data word, for example.
Single Process Data describes each individual bit of a module. A unique address is thus
specified for each individual bit of a device. These addresses do not necessarily have to
be continuous.
Both Standard Process Data and Single Process Data are displayed below "All" in the
context menu. The assignment of addresses can be displayed more clearly by filtering.

Figure 3-23 Setting the filter

3-18 PHOENIX CONTACT 6957_en_01

 Example Project

• Highlight an entry in the list below the bus structure.

• Right-click and click "Select all" in the context menu.
All entries are now highlighted.
• Right-click and click "Connect autom." in the context menu (see Figure 3-24 on
page 3-19).
Config+ now automatically assigns the corresponding control system address to the
individual devices.

Figure 3-24 Establishing a connection to the controller board

• If necessary, check the assignment of the inputs and outputs by clicking on the corre-
sponding workspace in the tree structure (e.g., Address area 1,
WORD in Figure 3-25).

Figure 3-25 Checking the assignment

6957_en_01 PHOENIX CONTACT 3-19

Config+

3.5.2 Manual Assignment of Inputs and Outputs

If you wish to assign inputs and outputs manually, proceed as follows:

• Select the "View... Process Data Assignment" menu or switch to the "Process Data
Assignment" workspace via the icon in the toolbar.
• Highlight the controller board.
• Right-click on an entry in the list under the bus structure and click "Filter... Standard
Process Data" in the context menu.

Standard Process Data describes the entire module. This means that an IB IL 24 DI 16
is addressed with a single IN process data word, for example.
Single Process Data describes each individual bit of a module. A unique address is thus
specified for each individual bit of a device. These addresses do not necessarily have to
be continuous.
Both Standard Process Data and Single Process Data are displayed below "All" in the
context menu. The assignment of addresses can be displayed more clearly by filtering.

Figure 3-26 Setting the filter

3-20 PHOENIX CONTACT 6957_en_01

 Example Project

Example: Addressing a Word-Oriented Device

• Open the "Output... Address area 1" folder (or one of the other address areas) under
"Address Range" in the top left window.
• Click "WORD", as a word-oriented device is to be described here.
• Highlight the "QW10" address in the bottom left window.
• Drag & drop the address onto the output area for module #7 ILB IB 24 DI16 DO16
2 . 0.
It is clear from the mouse pointer whether or not the address can be inserted in the
relevant module:

Prohibited position: Permitted position:

Cannot be inserted here Can be inserted here

Figure 3-27 Example: Addressing a word-oriented device

6957_en_01 PHOENIX CONTACT 3-21

Config+

Example: Addressing a Double Word-Oriented Device

• Open the "Input... Address area 1" folder (or one of the other address areas) under
"Address Range" in the top left window.
• Click "DWORD", as a double word-oriented device is to be described here.
• Highlight the "ID4" address in the bottom left window.
• Drag & drop the address onto the input area for module #5 IB IL AO 2/SF 1 . 4.
It is clear from the mouse pointer whether or not the address can be inserted in the
relevant module:

Prohibited position: Permitted position:

Cannot be inserted here Can be inserted here

Figure 3-28 Example: Addressing a double word-oriented device

• Proceed as follows for the other devices:

For a bit-oriented device (2 or 4 bits), specify "BOOL" in the address area
(e.g., address "Q0.0" for device #2 IB IL 24 DO 2 1 . 1.).
For a byte-oriented device, specify "BYTE" (however, no byte-oriented device is avail-
able in this example project).

3-22 PHOENIX CONTACT 6957_en_01

 Example Project

3.6 Parameterization

• Select the "Edit... Parameterize" menu or click the "Parameterize" button in the menu
bar.
A list of the following commands can be found under "Actions":
– Execute parameterization (RAM)
– Execute parameterization (RAM) and write Diag+ file (Flash)
– Execute (RAM) and save (Flash) parameterization
– Save parameterization (Flash)
– Save parameterization (Flash) and perform reset

As soon as an action is selected, the explanation for the relevant action appears in the
field below.

6957_en_01 PHOENIX CONTACT 3-23

Config+

3.6.1 Execute Parameterization (RAM)

Only the "Execute parameterization (RAM)" action is required in this example project. How-
ever, the project is only stored in the volatile buffer of the controller board.
• If you wish to save the project file on a pluggable parameterization memory (flash) or
the internal flash memory of the controller board, proceed as described in section
"Saving the Parameterization to the Parameterization Memory" on page 3-25.

Figure 3-29 "Execute parameterization (RAM)" action

• Select the "Execute parameterization (RAM)" command under "Actions".

• Click "Execute". The controller board switches to the "RDY" state.
A physical bus structure must be available and the controller board must be connected
to the PC and supplied with power.
Once parameterization is complete (controller board is in the "RUN" state), the controller
board is parameterized and the inputs and outputs can be accessed via your application
program (e.g., STEP® 7).

Detailed information can be found in the user manual and the driver manual for the rele-
vant controller board.

• Click "Close" in the "Parameterize" window.

3-24 PHOENIX CONTACT 6957_en_01

 Example Project

3.6.2 Saving the Parameterization to the Parameterization

Memory

The Config+ project data can be saved to a pluggable or internal (built-in) parameterization
memory..
The controller board with it's previously created configuration can be restarted e.g. after
voltage drop by saving the parameterization to the parameterization memory (Flash).
The "Execute parameterization (RAM)" function is not sufficient here.

The project or project modifications cannot be saved in DEMO mode.

• Connect a pluggable parameterization memory (flash) to the controller board if the in-
ternal memory in the controller board is not available.
• Switch to the "Bus Configuration" workspace and highlight the controller board.
• Select the "Parameterization Memory" tab in the "Device Details" window and click on
the "Format" field if you wish to delete any existing files.

Figure 3-30 Parameterization memory

• Select the "Edit... Parameterize" menu or click the "Parameterize" button in the menu
bar.
• Select one of the following commands under "Actions":
– Execute (RAM) and save (Flash) parameterization
– Save parameterization (Flash)
– Save parameterization (Flash) and perform reset

As soon as an action is selected, the explanation for the relevant action appears in the
field below.

• Click "Execute" to start the selected action.

6957_en_01 PHOENIX CONTACT 3-25

Config+

3-26 PHOENIX CONTACT 6957_en_01

 Diagnostics

4 Diagnostics
• If an error message is received during parameterization, the Diag+ diagnostics soft-
ware can be used to find and remove the error. Diag+ is automatically installed when
Config+ is installed.

• Select the "Diagnostics" workspace or the "View... Diag+" menu.

Figure 4-1 Diag+

• Under "Communication Path", select the device with which you would like to establish
a connection (here: Door assembly).

Figure 4-2 Selecting the communication path

The diagnostics represented depends on the communication path.

• Click on "Connect" to activate the communication path.

6957_en_01 PHOENIX CONTACT 4-1

Config+

View: Settings • At the top of the section under "View", select which general information is to be
represented.

Figure 4-3 Example for device representation view

View: INTERBUS INTERBUS module in an INTERBUS system can be diagnosed with Diag+ as usual.
Diagnostics Various information can be called via the different tabs.

Figure 4-4 INTERBUS diagnostics: bus topology (no error)

Errors are indicated. Under the "Solution" tab, information is provided on how to remove
the error. After error removal, the "Action" tab can be used, for example, to acknowledge
errors, reset the control system, and start the bus.
For further information, please refer to the online help.

HOTLINE
If you have any application problems which you cannot resolve with the aid of the online
help function or the documentation, please contact our hotline:

+49 - 52 35 - 34 18 88
[email protected]

4-2 PHOENIX CONTACT 6957_en_01