Tag Integration with Schneider Electric PLCs and Modbus in InduSoft Web Studio
34
IWS and Drivers for Schneider- Electric By Andre Bastos November 18, 2015
-
Upload
schneider-electric -
Category
Technology
-
view
2.606 -
download
21
Transcript of Tag Integration with Schneider Electric PLCs and Modbus in InduSoft Web Studio
IWS and Drivers for Schneider-ElectricBy Andre Bastos
November 18, 2015
AgendaAndre Bastos (InduSoft)- Intro
- Families- Modbus Communications- Unity Pro (M340)- SoMachine (M241, M251)- Triconex (Trident)
Q & A
Awards – Customer Recognition
Mobile HMI/SCADA Mobile HMI/SCADA BI Dashboard HMI/SCADA HMI/SCADA HMI/SCADA
Vote for this year’s Award:
http://www.indusoft.com/blog/2015/10/15/voting-is-now-open-for-control-engineerings-engineers-choice-awards/
InduSoftWeb
StudioOver 250Drivers
TCP/IPOPC Server
Gateway
XMLODBC/ADO
DDE
OPC DA,UA, .NET,
XMLClient
Web(HTML &
XML)
Driver &Database
API
Open ArchitectureSystem Integration
Product Customization
EnterpriseAccess , Oracle ,SQL Server, Fox Pro,PI and many others...
Client StationsRedundancyData Exchange in Real-TimeThird-Party SystemsSecure Viewer Thin Client
Web SolutionAccess to the system fromanywhere using a single browser
Mobile AccessVisualize your Data and Graphics
on Smart Phones and Tablets using HTML5
Plant Floor IntegrationSchneider-Electric,
OMRON, GE FANUC, AllenBradley , Siemens,
Modbus, Profibus, DeviceNet, ControlNet,
Interbus, Beckhoffand many others...
Connectivity
Communication Drivers Module
InduSoft Web StudioCore Process
Tags Database
Comm.Driver
Process Controller
Communication Channel
Local Viewer
Remote SecureViewer
Web Thin Client
TCP/IP Communications
MODBUS
MODBUS
Developed by Modicon (US) in or around 1977 Developed targeting industrial application Managed by the Modbus Organization (www.modbus.com)
Main Advantages: Openly published and royalty-free Easy to deploy and maintain It is a de facto standard in the industry It is still probably the most used Industrial Protocol to the date Uses RAW Bytes: the only 4 type of addresses. The data can then
be formatted as needed (Word, FP, DW, Word Swap, etc…)
Modbus Protocol
MODBUS
RS-232/485 RTU: serial, compact, binary ASCII: serial, uses ASCII chars
Ethernet Modbus TCP – TCP, Port 502, no Checksum Modbus over TCP: Modbus RTU encapsulated in TCP/IP
(includes Modbus Checksum) Modbus over UDP: Modbus RTU:
encapsulated in UDP/IP
Proprietary (Schneider only) Modbus Plus: requires PC Adapter
PCI, USB (MBXAPI)
Modbus “Flavors” and IWS DriversDriver
MODBU: MasterMODSL: Slave
MOTCP: MasterMODSL: Slave
Driver MODBU
With TCP or UDP Encapsulation
Driver MODPL
MODBUS
Modbus AddressingDescription
Modbus addressing
InduSoft format
Coils 00001 0x:1
Inputs 10001 1x:1
Input Registers 30001 3x:1Holding Registers 40001 4x:1
TAG INTEGRATION
Tag Integration vs Driver
Tag integration allows you to directly integrate tags from a third-party control application or device into your IWS project.
Registers added in this way appear as tags in the Shared Database folder:• They are "live" — that is, they are continuously and bilaterally
updated during run time as long as the source is also running and properly connected, and…
• They can be used anywhere in your project that you would normally use project tags.
Tag Integration
Tag Integration vs Driver
Instead of manually configuring driver worksheets to associate project tags with device registers, you can use the Object Finder to browse the device registers and add them directly to your project.
Tag Integration
Tag Integration vs Driver
During the Runtime, the Tag Integration will create a virtual Main Driver Sheet
The virtual Main Driver Sheet will work as a real one, creating multiple Virtual Read Groups in memory
At the end of this presentation, we will highlight some differences between Main Driver Sheet and Standard Driver Sheet
Tag Integration – background work
SCHNEIDER UNITY
SCHNE Driver and Tag Integration
Driver used to communicate with Schneider-Electric PLCs that are programmable using Unity Pro softwareIt wraps the addresses into the Modbus Protocol:
M340, M580* Premium Quantum
Supports: %M – Accessed as Modbus Coils (0x) %MW – Accessed as Modbus Holding Registers (4x)
SCHNE Driver
Unity
An I/O Point can be addressed on Unity Pro in 3 Modes.Let’s use, as an example, an 8 channel Thermocouple:• Mounted on the Slot 5 (Local Rack)• Starting Input Address: 201 (%IW201)• Addressing the Channel 3
Addressing modes: FLAT: e.g. %IW203 – Quantum CPUs Topological: %I1.5.3 - M340 and Premium Concept: 30203 – Modbus addressing
Addressing Method
SCHNE
SCHNE driver Features: Supports FLAT addressing only (%M and %MW) Modbus protocol does not address Topological addresses,
which is the mode used on M340 and Premium PLCs for I/Os
Configuring using Unity Pro
M340/Premium – I/O addressing is Tolological, e.g IW1.2.3: <Rack>.<Slot>.<Word>
Unity
InduSoft Supports Tag Integration for projects created using Unity Pro
Export the Variables that have Flat Addresses to a .XSY file Import on IWS using Tag Integration
Tag Integration
SCHNE
%M EBOOL are directly addressed on the driver Bit from WORD are BOOL, addressed like this: %MW100.3 %MW is the 4x area Format is on the driver I/O Address field. E.g. %MF1, %MT2
Configuration
SOMACHINE
SoMachine
Driver used to communicate with Devices that run 3S Codesys runtimes, versions 2.x and 3.x, such as:
Schneider-Electric SoMachine Devices M241, M251 LMC600 PacDrive Others
PLCHandler: Communicates through the 3S PLCHandler Library
Information
IWS COSYS Driver
3S PLCHandler Codesys Runtime
API
SoMachine
ARTI3 Implementation Access to PLC Variable
Names directly on the PLC or offline using Symbol File
NOTE: it is mandatory that a SYMBOL CONFIGURATION to the PLC Logic Project for the driver to communicate
Tag Integration: Codesys
SoMachine
IWS Configuration Simply add a Tag
Integration Source for Codesys
Select runtime version CoDeSys 3.x
On the Runtime Address field, configure the PLC Node Name
Tag Integration: Codesys
TRICONEX
Triconex
Safety PLC with Triple Modular Redundant (TMR) technology
Former INVENSYS product, now Schneider-Electric
Can communicate using the IWS TSAA driver
It has a built-in OPC UA Server
Uses addressing method similar to Modbus
Information
Triconex
Supports Standard Driver Sheet only Communicate with the Alias numbers No Tag Integration available at this time
Information
MAIN VS STANDARDDRIVER SHEETS
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
Standard Driver Sheet Pros:
Total Control of your Communication: choose when you want to read or write
Read constantly or on-demand Write an entire Group of variables or one single item Individual Group Communication Feedback 1 Station configuration for the entire group
Cons: Configuration is less-friendly than MDS Manual configuration of Blocks obeying Block Sizes Only 1 Station per worksheet Only 1 Register type per worksheet You may end up using several worksheets – harder maintenance
Q&A
HOW TO CONTACT INDUSOFT
Email(US) [email protected](Brazil) [email protected](Germany) [email protected]
Support [email protected] site
(English) www.indusoft.com(Portuguese) www.indusoft.com.br(German) www.indusoft.com.de
Phone +1 (512) 349-0334 (US) +55 (11) 3293-9139 (Brazil) +49 (0) 6227-732510 (Germany)
Toll-Free 877-INDUSOFT (877-463-8763) Fax +1 (512) 349-0375
Contact InduSoft Today
Germany
USA
Brazil
THANK YOU!
