Function description and documentation of

Phoenix Contact examples of use Page 1 of 21

Example of use

EtherNet/IP TP 3105T EIP communication

for the VISU+ visualization system

Function description and documentation for

Phoenix Contact examples of use
Software created by:
Phoenix Contact GmbH & Co. KG
Flachsmarktstrae 8
32825 Blomberg, Germany
Phone: +49 5235 / 3-00
 TP 3105T EtherNet/IP communication
Page 2 of 21

Contents
1 Introduction .................................................................................................................. 3
1.1 Description .............................................................................................................. 3
1.2 Target group............................................................................................................ 3
1.3 Data ........................................................................................................................ 3

2 Setting up the EtherNet/IP driver in Visu+ .................................................................. 4

2.1 Creating the project and integrating the driver ......................................................... 4
2.2 Setting up a dynamic task ..................................................................................... 10

3 Example projects........................................................................................................ 14
3.1 RS Logix project.................................................................................................... 14
3.2 Visu+ project ......................................................................................................... 17

4 Tips and tricks............................................................................................................ 20

5 List of figures ............................................................................................................. 21

 TP 3105T EtherNet/IP communication
Page 3 of 21

1 Introduction
1.1 Description
This example of use illustrates how communication is established between the touch panel
from Phoenix Contact and an Allen Bradley Control Logix.
This document describes setup of the EtherNet/IP driver in the Visu+ development
environment. The example program for RS Logix and Visu+ is described in section 4. Useful
expansions such as the monitoring of communication are dealt with in the Tips and Tricks
section.

1.2 Target group

This document is intended for users with a basic knowledge of the VISU+ 2 (Order No.
2988544) and RS Logix 5000 logic tools. Refer to the VISU+ Programmers Guide (Order No.
7477) in the PHOENIX CONTACT download center or the VISU+ User Course (Order
No. 2884716) for further information on Visu+.

1.3 Data
Name: TP 3105T EtherNet/IP communication
Type: Example of use
Environment: Visu+ 2.04, RS Logix 5000 Ver. 16.00.00
Language: Ladder Logic
Version: V1.00
Author: PxCE / MPOT
Touch Panel: TP 3105T (Order No. 2700916) or optional
TP 3057M (Order No. 2700901)
TP 3057T (Order No. 2700906)
TP 3070T (Order No. 2700911)
TP 3121T (Order No. 2700921)
Controller types: Allen Bradley Control Logix 5555, 1756 L55 A
 TP 3105T EtherNet/IP communication
Page 4 of 21

2 Setting up the EtherNet/IP driver in Visu+

This example includes a previously prepared Visu+ project that you can put into operation
immediately. The following steps describe the required settings in order to integrate the
EtherNet/IP driver into a new project and are not necessary for starting the example.

2.1 Creating the project and integrating the driver

You can open the project creation wizard via File -> New. It is recommended to use the
wizard for a Project Template, since this automatically makes a number of useful screens
available.

Fig. 1: creating a new Visu+ project

 TP 3105T EtherNet/IP communication
Page 5 of 21

In the following window, please select the desired HMI product first, subsequently the desired
storage location for the new project und finally, a name. If the order is adhered to, Visu+
automatically generates a folder with the selected name in the selected path and creates a
new project with suitable settings for the selected product.

Fig. 2: step 2 of the project wizard

 TP 3105T EtherNet/IP communication
Page 6 of 21

In the next step, click on the communication objects with the right mouse button select the
Add a new Comm. I/O driver item.

Fig. 3: adding the EtherNet/IP driver

 TP 3105T EtherNet/IP communication
Page 7 of 21

The new dialog offers you all available drivers in Visu+. A driver is offered for EtherNet/IP
communication within the Rockwell Automation group.

Fig. 4: selecting the driver

The driver is now integrated into your Visu+ project and no longer appears in the selection
list.
 TP 3105T EtherNet/IP communication
Page 8 of 21

Further settings are made to the driver during the following procedure. Double-click on the
driver beneath the communication objects in the list.

Fig. 5: driver configuration dialog

 TP 3105T EtherNet/IP communication
Page 9 of 21

You can now add your ControlLogix station via the Station Properties tab. Assign a unique
name for your station under Station Name and enter the IP address of the EtherNet/IP
scanner Additional setting must be made according to the driver help file.

Fig 6: station settings

You can test the connection of the hardware connected via the Test Cable/Comm function.
The result of the test is reported immediately.

Fig. 7: success message

 TP 3105T EtherNet/IP communication
Page 10 of 21

2.2 Setting up a dynamic task

Automatic import of the controller tag from a ControlLogix, CompactLogix and FlexLogix is
currently not supported. The local Visu+ variables must therefore be linked to the driver via
the Dynamic setting. This connection is referred to as dynamic task. Please create a
variable in Visu+ and open the dialog for dynamic linking via the Properties window, which is
highlighted in the following figure in red.

Fig 8: variable properties

 TP 3105T EtherNet/IP communication
Page 11 of 21

Change to the communication driver tab and click new/edit.

Fig 9: variable explorer

 TP 3105T EtherNet/IP communication
Page 12 of 21

The following window shows the properties of a dynamic task. The station is assigned as
device that was created in the previous Station Properties window. The other properties are
set according to the instructions in the help file. The A-B address in the 'Allen-Bradley Task
Settings" section must correspond to the name in the RS Logix controller tag list.

Fig. 10: settings task

 TP 3105T EtherNet/IP communication
Page 13 of 21

The successful setup of the driver can now be checked with a lamp for example. For this
purpose, take a lamp out of the tool box on your drawing area and link it to the
bPlcTaktMerker variable. Since the clock marker of the controller linked via the
bPlcTaktMerker variable is a byte and each bit symbolizes a specific frequency, you must
determine a matching bit manually. Supplement the variable name linked to the lamp with the
desired bit number (e.g., .5 corresponds to 1 Hz).

Fig. 11: checking successful integration

If implemented successfully, the lamp should flash at the the selected frequency.
 TP 3105T EtherNet/IP communication
Page 14 of 21

3 Example projects
3.1 RS Logix project
The project included for the RS Logix consists of 3 parts.

Fig. 12: RS Logix project tree

In these three parts, the following 'global variables' or controller tags can be accessed from Visu+. The
EtherNet/IP driver only supports access to controller tags.

Fig. 13: controller tag list

 TP 3105T EtherNet/IP communication
Page 15 of 21

The eXclusive OR condition for the analog value visualized in fig. 2 in a trend is located in
the Counter program section. If the result is True, counting up (up to max. 100) or down
(down to min. 0) takes place depending on the CountUp or CountDown button pressed. If the
result is False, no action is performed.

Fig. 14: program counter

 TP 3105T EtherNet/IP communication
Page 16 of 21

The LifeBit is generated in the Toggle program section. Visu+ reads the LifeBit from the
Control Logix via the ToggleBit variable.

Fig. 15: program toggle

The date and time are read in the the "Main Program" section via the Get System Value
block. Visu+ reads the date and time from the Control Logix via the user-defined TIME (
DINT[7] ) of the DateAndTime variable.

Fig 16: main program

 TP 3105T EtherNet/IP communication
Page 17 of 21

3.2 Visu+ project

The previously prepared Visu+ project can be transferred directly to a TP 3105T. During
creation, the Control Logix or the EtherNet/IP scanner is linked with the following
communication settings:

Fig 17: station settings

 TP 3105T EtherNet/IP communication
Page 18 of 21

Should your controller be accessible under another address, you must adjust this in the
station configuration of the EtherNet/IP driver. The project uses some elements of the image
1 and 2 process images that exchange data with the Control Logix CPU. The current data
and time of the CPU is shown in figure 1. Furthermore, the LifeBit indicating controller
accessibility is visualized

Fig. 18: process image 1 view

 TP 3105T EtherNet/IP communication
Page 19 of 21

A trend window is represented in figure 2 that displays the value of the counter from the RS
Logix project. CountUp and CountDwn are linked within the Control Logix CPU XOR and
enable the counter to count up to a maximum of 100 or count down to a minimum of 0.

Fig. 19: process image 2 view

All further process images or functions correspond to the standard Phoenix Contact Visu+
project example of use and are described in the Visu+_Template_V1_00_049.DOC
document. This document is available in the download center under
http://www.PhoenixContact.com.
 TP 3105T EtherNet/IP communication
Page 20 of 21

4 Tips and tricks

Evaluable monitoring of the communication is required in every application. In this example,
it is implemented by the controller with the help of a LifeBit. The LifeBit is read from the
ToggelBit of the Control Logix via the EtherNetIP driver.
This LifeBit is monitored for change and an internal variable set in the event of a downtime in
the global instruction logic in Visu+. The alarm bit is evaluated in a Visu+ alarm.

Fig. 20: LifeBit monitoring

 TP 3105T EtherNet/IP communication
Page 21 of 21

5 List of figures
Fig. 1: creating a new Visu+ project....................................................................................... 4
Fig. 2: step 2 of the project wizard......................................................................................... 5
Fig. 3: adding the EtherNet/IP driver...................................................................................... 6
Fig. 4: selecting the driver ..................................................................................................... 7
Fig. 5: driver configuration dialog........................................................................................... 8
Fig 6: station settings............................................................................................................. 9
Fig. 7: success message ....................................................................................................... 9
Fig 8: variable properties ..................................................................................................... 10
Fig 9: variable explorer........................................................................................................ 11
Fig. 10: settings task............................................................................................................ 12
Fig. 11: checking successful integration .............................................................................. 13
Fig. 12: RS Logix project tree .............................................................................................. 14
Fig. 13: controller tag list ..................................................................................................... 14
Fig. 14: program counter ..................................................................................................... 15
Fig. 15: program toggle ....................................................................................................... 16
Fig 16: main program .......................................................................................................... 16
Fig 17: station settings......................................................................................................... 17
Fig. 18: process image 1 view ............................................................................................. 18
Fig. 19: process image 2 view ............................................................................................. 19
Fig. 20: LifeBit monitoring.................................................................................................... 20