New integration with Siemens S7-1500Updates on integration with AB CIP

March 2016

THANK YOU!Together, we are stronger!

15+ years of innovation, collaboration, evolution, and success!

Agenda

InduSoft (Andre Bastos)What’s new: SITIA - new driver and Tag Integration for Siemens S7-1500 PLCsDriver and Tag Integration features and limitationsConfiguring the PLC for the communication to happenComparing with the existing SIETH driverLive Demo

Update: ABCIPIntroduction about the ABCIP driver and the Tag Integration for Family 5000 PLCsLatest improvements and bug fixesSymbolic vs Physical ModesLive Demo

Q & A

Siemens S7-1500

SITIA – Driver for S7-1500

S7-1500 is the new Family of PLCs from Siemens

Programming Software: TIA Portal

It uses Tag Names

Supports PLC Tags, UDTs, DBs

SITIA – Driver for S7-1500

The new SITIA driver allows communication with S7-1500 PLCs using the Tag Names configured on the PLC

It is as simple as it gets: type the PLC IP address on the “Station” field type the Tag Name on the “I/O Address” field

PLC ConfigurationSetting the PLC Security

Using the SIEMENS TIA Portal, you have change the Security Settings to allow the Driver to access the Tags

SITIA Driver

Considerations

The driver cannot communicate with the PLC if it is password protected

There is no need to configure optimizations for Data Blocks

This driver is available for Windows PC or Embedded Standard only – No WinCE or IoTView at this time. You can still use the SIETH driver for WinCE

projects

Demo

Tag Integration for S7-1500

The Tag Integration is a feature of InduSoft Web Studio that allows the user to configure the communication tags directly on the objects, skipping the Driver configuration

The Tag Integration for SIEMENS S7-1500 (SITIA Tag Integration) will be released on the upcoming version 8.0 + Patch 3

Tag Integration for S7-1500

Configuring the Tag Integration for S7-1500 is pretty simple: Add the Tag Provider

to the Project Configure the

PLC IP Address

Tag Integration for S7-1500

Next, using the “Object Finder” window, you will be able to import PLC tags into your project

Tag Integration and Driver S7-1500 - Notes

You can Read all the tags configured on the PLC even the ones with the “Visible to HMI” option unchecked

You can Write only to the Tags configured on the PLC with the “Accessible to HMI” checked

Read / Write Access Read only access

Tag Integration and DriverNotes:

Tags created using TIA Portal while On Line with the PLC are not accessible until you Compile and Download the new program with the new Tags

This icon represents that the Offline and Online versions of the PLC Tags do not match

Demo

Allen-Bradley ABCIP Driver

ABCIP

Driver used to communicate with newer Rockwell PLCs: ControlLogix CompactLogix FlexLogix MicroLogix 1100 MicroLogix 1400 Older families such as SLC500/PLC5 using 1756-DHRIO through DH+, or ProSoft bridges (AN-X2-AB-DHRIO)

Information

ABCIP – CL Family

Communicates using CIP over Ethernet IP Uses Tag Names Works with Atomic Types, UDTs, Aliases No 3rd-Party software or hardware needed (e.g. RSLinx)

Recent updates include: Improved Physical Mode connectivity Better support for Strings of any size Support for firmware 28 On the works: support for L5580 CPUs

ABCIP – CL Configuration

Station Field: <IP Address>[:<CPU Slot>]e.g.: 192.168.1.10 - If the CPU is on the Slot 0, you do not need to configure ite.g.: 192.168.1.10:1 - CPU on Slot 1

Driver Sheets

I/O Address: <Type>:<Name> or<Name>,<Type>

Demo

Tag Integration for L5K Files

The Tag Integration is a feature of InduSoft Web Studio that allows the user to configure the communication tags directly on the objects, skipping the Driver configuration

The Tag Integration for RSLogix 5000 Family imports tags from L5K files, exported using RSLogix5000 or Studio 5000

Tag Integration for L5K files

Configuring the Tag Integration for RSLogix 5000

Add the Tag Provider to the Project

Configure the PLC IP Address andCPU Slot number

Browse for the L5K file

Using the Object Finder, import the PLC Tags into your project

The “Connection Type” option has been validated only with the “Driver” option

Main Driver Sheet Pros:

Simple Configuration: usually uses the same PLC address syntax Automatic calculation of block sizes and group of messages Possibility of configuring Scan for Always, Screen, AutoNote: Keep in mind that the Readings happen in Groups! The closer the I/O addresses are to each other, the better the communication will be

Cons: Fixed scan Rate for all groups Every row requires a Station configuration Hard to identify a faulty communication group Writes Items Only. No Group Writing (it may be an issue for Recipes)

Main Driver SheetTroubleshooting hint: See the tags that are in each Read Group

Open the .App file using a Text Edit (e.g. Notepad) Find the [Options] section Create the following entry: DumpDriverSheets=1 Save, close the file and open the project As you call the runtime, you will find the files with the groups

created by the MDS in the project’s \Web\Dump folder. Use the development “Open File” command to visualize them.

Optimization hint: Changing the Reading Rate.

Open the .App file using a Text Edit (e.g. Notepad) Find the [Options] section Create the following entry: MainDrvAlwaysTrigger=<tagname> <tagname> is the name a project tag that you will use as Trigger

for the MDS, e.g. BlinkFast (200 ms rate) or create your own. Save, close the file and run the project

ABCIP

Symbolic: The driver sends the Tag

Names that it wants to read on every request

This is the way that the has been originally implemented

For better performance, use shorter Tag Names and Arrays on the PLC

Symbolic vs Physical modes

ABCIP

Physical: When the communication starts,

the driver asks the PLC for IDs for the tags, and then no longer sends the tag names

A Cache file is created, that you can manipulated

Here, the length of the Tag Names, or being an array no longer matters

Symbolic vs Physical modes

ABCIP

Note: Used only in Physical mode4 Options, where option 3 is a combination of 1 and 2

Blank – if you do not configure anything on this field, the CACHE file will be created when the driver first starts and it will not be recreated, unless the user manually deletes it.

1 – Cache is recreated when driver starts – this means that when the driver starts, it deletes the existing cache file, reads all the information from the PLC, recreates the cache and starts communicating

Cache Action

ABCIP

2;TAG – in this mode, configure a Tag in the PLC to force the CACHE to be recreated It is quite helpful when you have the driver communicating while you are still

changing the PLC program, since the Tag IDs change on each program version When the PLC goes from PROG to RUN mode, a system tag called S:FS is Set only

during the First Scan Use this tag to Latch another one, and that one can be used by the driver to signal

that the CACHE should be recreated

Examples2;S_FS_L

1;S_FS_L

Cache Action

Demo

Allen-Bradley ABCIP Driver

Routing through DH+

ABCIP – PLC5 / SLC500 Works with 1756-DHRIO Works also with other emulators such as:

ProSoft: AN-X2-AB-DHRIOEquustek: EQ7000-EDH+

ABCIP – PLC5 / SLC500 Station Field: path to the PLC

<Family>:<IP Address>:<Backplane>:<Slot>:<Channel>:<Remote Node>

I/O Address: PLC Native I/O Address format

Station to SLC5/04500:10.13.63.68:1:2:B:1

Station to PLC5/80E5:10.13.63.68:1:2:B:7

Q&A

THANK YOU!