Your SlideShare is downloading. ×
Understanding about Foundationtm fieldbus
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Understanding about Foundationtm fieldbus

1,003
views

Published on

Published in: Technology, Business

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,003
On Slideshare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
122
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Introduction to FOUNDATIONTM FIELDBUS (FF) By Rajesh S March 16th 2012 Friday1 02:32:31
  • 2. FOUNDATION FIELDBUS  Two-way digital communications system designed for interconnecting smart field devices and control systems.  Control/Monitoring functions on field mounted devices.  High speed  H1 – 31.25 Kbit/s  HSE – 100 Mbit/s  By Fieldbus Foundation2 02:32:31
  • 3. HART Vs FieldbusHART  Uses 4-20mA signal. Speed - 1200 bps  Ability to provide diagnostics for the device only , has no knowledge of other devices  Poll - HART status periodically  Multidrop – 15 devices but slow.Field bus:  Advanced diagnostics - Eg: Process Monitoring and Machinery Health monitoring.  Push - with events latched and time stamped in the device and sent to device.  True multidrop – 32 devices3 02:32:31
  • 4. Advantages of Fieldbus Foundation  Interoperability with other Field bus device.  High speed  Advanced Diagnostics Types  H1 – 31.25 Kbit/s – interconnects “field” equipment such as sensors, actuators and I/O.  HSE – 100 Mbit/s – High speed Ethernet – provides integration of high speed controllers.4 02:32:31
  • 5. OSI Model Vs Fieldbus Model5 02:32:31
  • 6. Fieldbus Model User Layer: • Function Blocks • Network Management (NM) • System Management (SM)6 02:32:31
  • 7. Fieldbus Model  Application Layer:  Fieldbus Message Specification (FMS) – Message structure  Fieldbus Access Sub layer – provides virtual communication channel , Addresses.  Data Link Layer  Error coding, parity checking. • Physical Layer  Wiring.7 02:32:31
  • 8. HSE Device Types  Linking device – Links H1 networks to the HSE network.  Ethernet device – Execute function blocks and may have some conventional I/O.  Host device - an operator workstation or an OPC server.  Gateway device (GD) - interfaces other network protocols such as Modbus, Device Net or Profibus8 02:32:31
  • 9. HSE Device  FDA Agent  HSE System Management Kernel (SMK)  HSE Network Management Agent (NMA)  Virtual Field Device (VFD)9 02:32:31
  • 10. Field Device Access (FDA)  Convey SM services over UDP  FMS Services over UDP/TCP  Allows HSE and H1 field devices, conventional I/O devices, and non-FF I/O devices to be connected to the HSE through a linking or a gateway device.10 02:32:31
  • 11. HSE System Management  Integrates devices on an HSE network into a coherent communication system  Unique, permanent identity for device  Maintains version control  Function block schedules  Devices added/removed without affecting other devices11 02:32:31
  • 12. HSE Network Management  HSE host systems to conduct management operations over the HSE network with their associated devices with an HSE interface.  Configuring the H1 Bridge  Loading the HSE Session List  HSE Session Endpoint – Logical communication channel  Loading the HSE VCR List – communication relationship used to access VFDs.  Fault Detection Monitoring.12 02:32:31
  • 13. FDA Components  FDA Session  An application relationship used for request/response, publisher/subscriber.  Identified by their source and destination endpoint addresses (IP addresses plus UDP/TCP port numbers)  FDA Agent  Entity within an HSE Device - uses the services provide HSE access to VFDs and SMKs (Within HSE device or other H1 devices)13 02:32:31
  • 14. FDA Agent14 02:32:31
  • 15. Application Processes (AP)  Application Processes (AP)  Entities within devices that perform a related set of functions, such as function block processing, network management, and system management Function Block Application Processes (FBAP)  Automated manufacturing and process control systems perform a variety of functions  Range of functional models, each addressing a different need.15 02:32:31
  • 16. Virtual Field Devices (VFDs)  Network visible objects of an Application Process  Descriptions of network visible objects are contained within the Object Dictionary (OD) within the VFD.  OD :  composed of a series of entries, each describing an individual object and its attributes.  OD entries are assigned an index which is used to obtain the description of the object from the OD. The OD index is also used to access the object itself. For each VFD there is exactly one Object Dictionary.16 02:32:31
  • 17. Virtual Field Devices (VFDs)  Virtual Communication Relationships  Network visible objects are accessible through VCRs using FMS Services  Communication relationship to access VFDs17 02:32:31
  • 18. Few SM and FMS services  SM Device Annunciation and Assignment  SM Device Identification Header  SM Tag Query Service-Specific Parameters + User Data (optional)  FDA Open Session Trailer (optional)  FMS Initiate  FMS Abort  FMS GetOD  LAN Redundancy Get information  LAN Redundancy Put information18 02:32:31
  • 19. More on Next Session…19 02:32:31
  • 20. Thank You20 02:32:31