the somachine solution: fdt integration and use … property of schneider electric 3 agenda...

1

The SoMachine Solution:

FDT Integration and use-casesFDT Developer Forum 2015

05-05-2015

Marco Mendes

Industry Business | Device LifeCycle Platform | System Engineer

[email protected]

3Confidential Property of Schneider Electric

Agenda

Schneider Electric's SoMachine is an open Original Equipment

Manufacturers (OEM) software solution for developing,

configuring and commissioning of the entire machine in a single

environment (including logic, motor control, HMI and related

network automation functions). Such a solution requires the

integration of many device configurations and utilities that

provides the user with a powerful building-block approach to

construct his/hers application. FDT fulfills these requirements and

therefore it is supported by SoMachine to extend its capabilities

of device integration. This presentation explains the device

integration using FDT in SoMachine and highlights some of its

use-cases.


Agenda

> FDT at Schneider Electric

> Introduction to SoMachine

> Overview on FDT/DTM support in SoMachine

> Device integration with FDT/DTMs in SoMachine

> CANopen

> Modbus SL

> Modbus TCP

> 3rd Party

> Conclusions

55

FDT at Schneider Electric


Why FDT at Schneider Electric?

> Many different device providers inside Schneider Electric

> Several Engineering Tools for different markets with the requirement to

integrate devices from different device provider

A common device integration technology is required!

> FDT offers an open standard for the device integration in Schneider Electric

Engineering tools

> for Schneider Electric products

> for Schneider Electric partner products

> and for third party products

> FDT provides a powerful device integration mechanism with many supported

protocols and features


Some of Schneider Electric’s offer

supporting FDT/DTM

> Unity Pro

> SoMove

> RenConnect

> Foxboro Field Device Manager

> SoMachine

> Many dedicated Comm/Master/Gateway/Device DTMs

88

Introduction to SoMachine


What is SoMachine?

> SoMachine: open Original Equipment Manufacturers (OEM)

software solution for

> Developing, configuring and commissioning of the entire

machine in a single environment (including logic, motor control, HMI

and related network automation functions).

> CoDeSys based IEC 61131 Engineering tool for machine

builders

> Current version is v4.1 SP1


Software solution for OEMs

One Software

Flexible Control-Platforms

Configuration, Programming and

und Commissioning

Integrated inteligence


One Software environment

With SoMachine you can design a complete solution with

just:

> 1 software package

> For Controller, Motion-Controller, HMI und Drive

> 1 download

> Transfer of the entire machine program at once

> 1 connection & Transparency

> Single cable connection and download of the application

> Access to networked devices completely transparent

> 1 Project file


SoMachine features

> Entire range of IEC 61131-3 languages

> Integrated fieldbus configurators

> Expert diagnostics and debugging

> Visualization screen

> Upgrading software via the Schneider Electric Software Update (SESU)

> Integrated function block finder to simplify programming

> Integrated OPC server

> Optional installation of the HMI application development tool Vijeo-Designer

> Optional installation of SoMachine Basic to configure and program the M221

Logic controller

> Optional installation of the Controller Assistant to manage firmware and

application download

> Application and function templates

> Improved user interface


SoMachine in Flexible Machine Control

Packaging

Material handling

Hoisting technology

Common applications

Function blocks for

automation and

application

Flexible

Control-

Platforms

Motion-Controller

Logic-Controller

Drive-Controller

HMI-Controller

SoMachine

Architectures for

automation and

application

Packaging

Building

Material handling

HVAC

Hoisting

Ceramics, wood, metal,

textile

Common applications


Project Workflow

● Assistant for each

stage during the

lifetime of an

automation project

● Configuration

● Programming &

Troubleshooting

● Commissioning

of devices

● Maintenance of

devices


Network support

> Master:

> Serial Line

> AS-Interface (Master for M238)

> Ethernet (Modbus TCP for M241, M251, M258/LMC058)

> CANopen (Transparency via FDT/DTM)

> CANmotion (integrated in LMC058)

> Connectivity:

> Serial Line

> Ethernet (Modbus TCP, EtherNet/IP)

> ProfibusDP

Modbus-TCP


Controller for Solutions

Logic-Controller HMI-Controller Motion-

Controller

Drive-

Controller

• M238 • M258 • XBT Gx • LMC058 • ATV-IMC

• M241

• M251 • HMISCUx

• M221

• LMC078


Typical SoMachine system configuration

Workstation with SoMachine

Controller

Fieldbus 1 Fieldbus 2

Transparency

1818

Overview on FDT/DTM support in

SoMachine


FDT in SoMachine

> Possibility of advanced configuration, diagnosis and maintenance that is

not possible with “simple” device descriptions

> Same DTMs can also be integrated in other solutions

> Reuse of software components

> Works with every device that has a DTM for it (or generic DTM)

> Integration of partner and 3rd party devices providing their DTMs

> Common Look and Feel


SoMachine FDT integration specifics

> SoMachine includes a component which implements such interface,

the M&M fdtContainer V2 (support for FDT1.2.x), which is able to

host these DTM components.

> Frame completely .NET based

> Frame integrates a communication channel and Master

configuration (CANopen). Other communication capabilities are

available.

> Integration and re-use of several Device DTMs from e.g. Drives or I/O

business units


What can you do with DTMs in SoMachine?

> Advance Configuration / Settings

> I/O Channels (Process Channels)

> Supply description of the I/O process channels of device

> Parameter upload and download (complete device

configuration)

> Device physical structure management

> Control (if supported) - Custom Logic inside DTM to do specific

device tasks

> Monitoring/Diagnosis

> Maintenance


=S= Private Interfaces

> Cover some specific =S= requirements that are not part of the

FDT specification

> Hiding several UI elements depending in which solution the

DTM is integrated

> E.g. Lexium / Altivar integrated in SoMachine

> Get more information about the Composite Device DTM and

Module DTMs (e.g. TM5-7, Advantys OTB)


E.g. Advantys OTB


Example of devices that have DTM integration

> Advantys OTB

> TM5-TM7

> ATV (Altivar)

> Lexium

> TeSysT

> TeSysU

2525

Device integration with FDT/DTMs in

SoMachine


Device repository and device

descriptions

> Device repository – local repository of device profiles to be used in a

SoMachine topology/project

> Devices are described in a defined format (known as devdesc)

> Schema: http://www.3s-software.com/schemas/DeviceDescription-1.0.xsd

> A full list of these files loaded by SoMachine can be found in the SoMachine

ProgramData folder under „Devices“.

> Some of these device profiles have a reference to a DTM that is loaded for

e.g. Advanced settings and I/O mapping.

> If DTM is available, normally there are two device profiles for a single

device:

> Without advanced settings (No DTM)

> With advanced settings (with DTM)

http://www.3s-software.com/schemas/DeviceDescription-1.0.xsd


Device integration in SoMachine -

relationships

Physical DeviceDevice(based on 3S device description)

Device Type Manager (DTM)

(specifically a DTM device type is used)

represented by (advanced settings or 3r-party integration)

represented by

SoMachine Device Tree(includes also the FDT Container to host DTMs for advanced settings or 3rd party

integration)

0..+instances of

parent of / child of

Device repository1..+

includes

DTM repository1..+

includes

Install DTMs of the DTM repository

parent of / child of

0..1

advanced settings

0..1

3rd party integration


Adding Project Devices

> When starting a

new SoMachine

project, the first

step is normally to

select one or

more Project

Devices (normally

a kind of

controller).


Generation of device tree


Adding specific devices to project

> Specific devices can

then be added to the

network topology of the

project device (based

on type of connector,

manager, protocol,

etc).

> Drag&Drop feature

available


Device configuration (advanced

settings)


Adding new profiles and DTMs

> New device profiles can be installed as well as DTMs via the

DTM repository


Ways of integrating DTMs into a

project> Using the 3S device descriptions, the integration of DTMs is specific to which

protocol is used (normally having a corresponding master for that protocol).

> Other way of integrating DTMs (depending on the protocol) is to enable the

„Use DTM Connection“ checkbox at the bottom of the Logic Builder.

> This would enable to configure MB Serial devices via a corresponding DTM in which

the device is directly connected to the computer.

> The 3rd party integration allows the access to devices using the „normal“ FDT

way. In this case, no 3S profile is required for a device.

3434


SoMachineCANopen


CANopen: System View


CANopen: Integration

PLC

CoDeSys Device Tree

Master

Slave 1

Slave 2(advanced settings)

CoDeSys

CoDeSys Command Manager

CANopen Master Configurator

(CANopen plugin)

IFdtCommunication

IDtm

TCP / USB

Slave 1 Configurator(Dev Desc XML, EDS)


DTM for Slave 2(advanced settings)

IDtm

CoDeSys internal

CoDeSys Internal

CoDeSys Internal FDT XML

Fdt Integratio

n P

lug

in

FDT

Container

FDT XML

FDT XML

PLCTCP / USB

CoDeSys Service

Fieldbus interface

Slave 1 Device

Slave 2 Device

Hardware / Fieldbus

CA

Nop

en

Will use DTM configuration and features instead (if available)

Transparency!


CANopen: Example

3838


SoMachineModbus SL


Modbus SL: System View

(in this case Modbus)

Modbus Switch

FDT Advanced

configuration

(device view)

CoDeSys

Transparency

protocol

(solution view)


Modbus SL: Integration

PLC

CoDeSys Device Tree

Master

Slave 1

Slave 2

CoDeSys


MB SL I/O Scanner

TCP / USB




IDtm

CoDeSys internal

CoDeSys Internal

CoDeSys Internal

FDT XML

Fdt In

tegratio

n

Plu

gin

FDT

Container

FDT XML

PLCTCP / USB

CoDeSys Service

Fieldbus interface

Slave 1 Device

Slave 2 Device

Hardware / Fieldbus

MB

SL

FDT Connection

MB SL Manager


Communication DTM(specific protocol)

IFdtCommunication

IDtm

MB Driver

FDT XML

MB SL

Slave 2 must e either

connected to FDT or

CoDeSys configuration


Modbus SL: Example

4242


SoMachineModbus TCP


Modbus TCP: System View

SoMachine

Ethernet

Machine

Switch

SoMachine

Ethernet

Machine

! Same network !

Switch,

Daisy chain,…..

M251


Modbus TCP: Integration

MB TCP Configurator

MB TCP Ghost

PLC

CoDeSys Device Tree

Master

Slave 1


CoDeSys


IFdtCommunication

IDtm

TCP




IDtm

CoDeSys internal

CoDeSys Internal

CoDeSys Internal FDT XML

Fdt Integratio

n P

lug

in

FDT

Container

FDT XML

FDT XML

PLCTCPEthernet / MB TCP

Fieldbus interface

Slave 1 Device

Slave 2 Device

Hardware / Fieldbus

Ethe

rnet

/ M

B T

CP

Will use DTM configuration and features instead (if available)

Is this possible without DTM, since communication is done

via Ghost?

Transparency routing is used to make the communication

between the two networks possible


Modbus TCP: Example

4646


SoMachine3rd Party


3rd party: integration

FDT Connection

CoDeSys Device Tree

Comm Manager

Slave 1

Slave 2

CoDeSys

Communication DTM(specific protocol)

IFdtCommunication

IDtm

Protocol Driver

DTM for Slave 1

DTM for Slave 2

IDtm

FDT XML

Fdt In

tegration

Plugin

FDT

Co

ntain

er

FDT XML

FDT XML

Slave 1 Device

Slave 2 Device

Hardware / Fieldbus

Pro

toco

l sp

ecifi

cIDtmFDT XML

FDT XML


3rd party: Example

4949

Conclusions


Conclusions

> FDT/DTMs is used in many Schneider Electric’s products to

promote device integration and reusability in a consistent way

> SoMachine integrates FDT support to use many of its features

> The support FDT is flexible enough to cover different

requirements and use-cases in SoMachine

51

Questions?

Thank you!

[email protected]

the somachine solution: fdt integration and use … property of schneider electric 3 agenda...

Documents