HSE-RIO bringing Remote I/O into the Foundation fieldbus technology

Size: px

Start display at page:

Download "HSE-RIO bringing Remote I/O into the Foundation fieldbus technology"

Arthur Silas Stone
6 years ago
Views:

1 HSE-RIO bringing Remote I/O into the Foundation fieldbus technology 1 Andre Fritsch R. STAHL GmbH Sn. Product Manager andre.fritsch@stahl.de Multaqa 2011, Abu Dhabi

2 HSE - the new kid on the block?

3 H1 and HSE - Scalable Environment One Technology At Two Speeds FF HSE H1 host FIELDBUS H1 Linking Device HSE/H1 FIELDBUS H1 3

4 4 as of November 2011

5 Wireless and Remote I/O- the new kids on the block!!! WIO = Wireless & remote IO

6 How it started ISA EXPO 2006 Press Conference Latest News: Initiative Bringing Remote I/O To FOUNDATION Technology (Cont d) 3 Worldwide end user demand for a single network infrastructure drives our specification development effort Specification will define structure for interfacing remote I/O over tightly integrated High Speed Ethernet (HSE) control backbone Addition of remote I/O will further tighten integration of process instrumentation within the FOUNDATION architecture ISA EXPO 2006 Press Conference Houston, TX Fieldbus Foundation 6

7 and how it is today! EUAC Advisor Herman Storey Herman Storey Consulting WIO Program Director ISA Backhaul/Backbone Co-Chair FIC HSE Wireless Backhaul Program Manager WCT Project Coordinator TSC Chairman Dave Glanzer Fieldbus Foundation WIO Fast Track Marketing Demo Larry O Brian Talon Petty Fieldbus Foundation WIO Program Manager Jon Malins Cooper- MTL TSC Liaison Libanio de Souza Smar WIO Chief Architect Naoyuki Fukao Yamatake WCT Liaison WCT Technical Team Leader Marcos Peluso Emerson Device Registration Process Darie Dreptate Stephen Mitschke Fieldbus Foundation HSE RIO Technical Team Leader Detlef Arndt P+F ISA Backhaul/Backbone Co-Chair FIC Technical Team Leader Penny Chen Yokogawa Wireless Sensor Interface Team Program Manager & Technical Team Leader Pat Brett Honeywell WIO Validation Team Leader Johannes Lang R. STAHL HSE RIO Development Team FIC HSE Backhaul Development Team WSIT Development Team WIO Validation Team 7

8 WIO Development Teams Host HSE RIO Team Fieldbus Foundation - ISA100 Cooperation HSE Backhaul Team Gateway Conventio nal I/O H1 Wired HART WirelessHART ISA100.11a Wireless Sensor Team 8

9 WIO Development Phases WIO Phase 1 WIO Phase 2 WIO Phase 3 WIO Phase 4 HSE Remote I/O HSE Backhaul & WirelessHART I/F Flexible Function Blocks & I/F to other Networks ISA100 I/F Wired FF HSE Wired FF HSE or Wireless FF HSE backhaul Wired FF HSE or Wireless FF HSE Backhaul Wired FF HSE or Wireless FF HSE Backhaul Gateway Gateway Gateway FFB Gateway Convent l I/O Wireless HART Convent l I/O Other networks ISA100.11a FF H1 HART I/O HART I/O 9

Managing Host FF HSE FIELDBUS H1 WIO Conventional

10 H1 and HSE- Scalable Environment One Technology At Two Speeds Control System Host May be Combined Asset Managing Host FF HSE FIELDBUS H1 WIO Conventional I/O FF HSE-RIO & Wireless Wireless I/O HART AO HART AI 10

11 11 From HSE-RIO to WIO to ROM

12 12 More than just RIO 2.1 Gateways to other buses 2.2 Remote Logic 2.3 Simple I/O 2.4 Hot Swappable I/O Cards - Transparent to Fault Tolerance 2.5 Change field device parameter while operating 2.6 Acyclic communication to access config, diagnostic & maintenance data 2.7 Device Power 2.8 Hazardous Location Installation 2.9 Offline Configuration 2.10 Motor Control Center Comms 2.11 Variable Speed Drives 2.12 Sequence of Events (High Resolution Timing) 2.13 Redundant I/O Cards - Transparent to Fault Tolerance 2.14 Configuration changes while in service 2.15 Change control strategy while in service 2.16 HSE-RIO used as an RTU 2.17 Data buffer with Burst communications (Loss of comm without losing history) 2.18 Process Interrupt driven control execution 2.19 Distinguish & prioritize between Control & Device Support and Config Comms 2.20 HSE Interoperability 2.21 Standard Connection Mechanism (Physical Layer - Cables, Connectors etc.) 2.22 Redundant Comm 2.23 Fault Tolerant Comm 2.24 Functional Safety - Support of FOUNDATION SIF 2.25 Historic data retrieval 2.26 Device status of self comms, physical layer & connected devices 2.27 RIO Pass through (routable) system (i.e. VPN, Internet, Tunneling) 2.28 Security 2.29 Configuration change status in HSE-RIO reported 2.30 High Frequency Update 2.31 HSE-RIO capacities from HSE-RIO Use Case document

13 More potential FF HSE Applications Emission Monitor Gas Analyzer Variable Gas Speed Drive Chromatograph Machinery Vibration Monitoring Flow Computer Coriolis Mass Flow Meter Linking Device Ultrasonic Flow Meter RIO & RTU Wireless Gateway 13

14 So why do we need something new? To integrate a modular system for large data quantities into classic Foundation architecture, some add-ons were required. From FF-061 System Architecture for WIO : 1. Introduction HSE Remote Input/Output devices and Wireless Gateways/RTUs are examples of high point-count HSE devices that are aggregates of various components that will vary from one user instance to another user instance. The traditional small H1 device model and small pointcount HSE device model may not be a sufficient model for such a device. With device size permitted to vary from a few dozen points to several thousand points, scalability of the architecture is a requirement. 14

15 And what s new now? Association Block special form of transducer block also required for offline configuration description of hirarchical and functional organization of modules (e.g. slot and functionality of installed IO-module) association of head module (gateway) with possible set of IO-modules association of module (I/O or gateway) with it s individual transducer blocks 15

16 And what s new now? Element redundancy optional (depends on supplier) not limited dual, triple etc. all kinds of redundancy supported (head module, IO-module, cable) internal handling (e.g. configuration of modules) by head module 16

17 And what s new now? Transducer block for HSE-RIO one HSE-RIO TB for each HSE-RIO module (slot) handles data transfer between physical IO and function block application redundancy handled by association block link between transducer and function block via channel tags TB TB TB 17

18 And what s new now? Function block for HSE-RIO (FF-633 part 6) minimize CPU power for processing large number of IO-points minimize amount of data for configuration of IO-blocks minimize number of links between RIO and control device (!!) 4 additional new function blocks with limited features compared to single function blocks (e.g. only block alarm): MBI-64, MBO-64, MAI-16, MAO-16 single function blocks to be used to access full features 18

19 For FF experts only Single FB AI Multi FB MAI WIO FB MAI-16 No. of Input 1 No. of Input 8 No. of Input 16 View View View View View 1 View 3 View 3 View 4 View 1 View 3 View 3 View ST_REV ST_REV ST_REV TAG_DESC TAG_DESC TAG_DESC 3 STRATEGY 2 STRATEGY 2 STRATEGY 2 4 ALART_KEY 1 ALERT_KEY 1 ALERT_KEY 1 5 MODE_BLK 4 4 MODE_BLK 4 4 MODE_BLK BLOCK_ERR 2 2 BLOCK_ERR 2 2 BLOCK_ERR PV 5 5 CHANNEL 2 FORCE_ENB_ OUT 5 5 OUT_1 5 5 CHANNEL_TAG_16 9 SIMULATE OUT_2 5 5 OUTM_ XD_SCALE 11 OUT_3 5 5 MAP_MM_ OUT_SCALE 11 OUT_4 5 5 UPDATE_EVT 12 GRANT_DENY 2 OUT_5 5 5 BLOCK_ALM 13 IO_OPTS 2 OUT_ STATUS_OPTS 2 OUT_ CHANNEL 2 OUT_ L_TYPE 1 UPDATE_EVT 17 LOW_CUT 4 BLOCK_ALM 18 PV_FTIME 4 19 FIELD_VAL UPDATE_EVT MAI function block 21 BLOCK_ALM 22 ALARM_SUM ACK_OPTION 2 24 ALARM_HYS 4 25 HI_HI_PRI 1 26 HI_HI_LIM 4 27 HI_PRI 1 28 HI_LIM 4 29 LO_PRI 1 30 LO_LIM 4 31 LO_ LO_PRI 1 AI function block 32 LO_ LO_LIM 4 33 HI_HI_ALM 34 HI_ALM 35 LO_ALM LO_ LO_ALM NEW: MAI-16 RIO function block

20 And what s new now? Control in the field RIO an HSE-RIO is based on function blocks like any H1 fieldbus device each IO-module has it s own function & transducer blocks therefor a link between function blocks inside a RIO system is possible as well 20

21 And what s new now? Transducer block for wired & wireless HART represents HART devices within HSE-RIO devices. Wired HART and WirelessHART devices may be represented in this block. Describes the expected method for HART configuration tools and asset-managing hosts to access HART devices using the native HART command protocol transported through the Foundation High Speed Ethernet (HSE) network. The specification also defines structures to identify and maintain HART device status in wired multi-drop networks as well as in WirelessHART mesh networks Alternative solution : mapping of HART variables into the standard AI transducer blocks -> standard HART devices become multi variable device. 21

22 Overview HSE-RIO concept from FF-633 Part 6 22

23 Does it work? Media Event 1 st of Dec

24 24 Example HSE-RIO configuration

25 Ethernet & HSE the perfect team Additional diagnostics via Webserver 25

26 Explosion protection for FF HSE? see Multaqa 2009 Control System Host May be Combined Asset Managing Host FF HSE Ex? FIELDBUS H1 Remote IO Convention al I/O HART AO HART AI 26

27 The next steps Foundation has started F-ROM: Foundation for Remote Operations Management First media event 1st December 2011 in USA Small end user demos Q1 Q Big Demo event at end user sites Q Ask your DCS supplier for support of this new HSE-RIO functionality! 27

Technical Information

Technical Information DAQSTATION Applications of FOUNDATION TM FIELDBUS Copyright July 2001 1st Edition July 2001 Blank Page Introduction This document explains detailed specifications of