TORERO Presentation

1
TORERO Total Lifecycle Web-integrated Control
Marcus Tangermann Center Distributed Systems at
IAF Univ. of Magdeburg / Germany marcus.tangerman
n_at_mb.uni-magdeburg.de
2
Project details

• Project funded by the EU in the IST
• Duration 2002 2004
• Consortium consists of European Research
  Institutes
• and Companies of the Automation Industry

3
Partners
4
Distributed automation systems today
5
Trends I
Trends in Automation On the way torwards
Distributed Control
6
Trends II
Trends in Automation On the way torwards
Distributed Control
Source PNO, Germany, 2001
7
Trends III

• Seamless integration of all levels of the
  automation pyramid.
• Adoption of Internet related technologies

8
Common tools

• Current Control application for distributed
  systems - connection of function blocks in a
  system editor - programming of the FBs in vendor
  specific editorsThe overall system functionality
  can only be programmed as relationsship of
  already existing FBs.
• Device specific tools for engineering and
  maintenance
• device specific software code
• Web-technologies will not be used for e.g.
  self-configuration / self-maintenance

9
Distributed automation systems tomorrow
10
Primary Objective
... is to create a total life cycle web-integrated
control design architecture and methodology
for distributed systems.
11
Primary Goals

• Define an architecture for an distributed
  automation system
• Define and develop semi-automatic code
  distribution
• Develop a methodology for reuse of software
  components
• Integrate web-services
• Enable Plug and Play for devices

12
TORERO Environment
TORERO devices TORERO IDE Internet TORERO
environment
13
TORERO Device
A TD is the smallest part of an automation system
which itself interacts in a distributed and non
hierarchical environment.
Lenze drive Fraba sensor
14
TORERO Device
15
TORERO IDE

• Extendable Framework
• WorkbenchUI
• Integration of Plug-ins

16
TORERO Software Server

• SOAP based
• basic element of a
• supply chain
• source for updates,
• bugfixes of device
• functions

17
TORERO Communication

• Plug and Play system
• JINI too heavy for embedded devices
• Universal Plug and Play as an alternative
• Leightweight stack
• firewall friendly implementation
• Covers device description
• Equipped with SOAP RPC

18
TORERO Communication

• Device communication
• (RT)CORBA one possible solution
• IP based automation protocols prefered by vendors
• EtherNet/IP
• Modbus/TCP

19
Conclusion

• Application oriented control design, HW
  independent
• Distribution of central control functions
• integration of web technologies
• Plug and Participate technology in the field of
  automationself-configuration and
  self-maintenance capabilities
• Paradigm shift from central control to fully
  distributed control.
• Novel, application oriented control design
  architecture and methodology, independent from
  HW.