The DCS revolution started in the mid-1970’s was fundamentally a moving of control system “intelligence” from a centralized location to distributed locations. Rather than have a single computer (or a panel full of single-loop controllers) located in a central control room implement PID control for a multitude of process loops, many (smaller) computers located closer to the process areas would execute the PID and other control functions, with network cables shuttling data between those distributed locations and the central control room.
Beginning in the late 1980’s, the next logical step in this evolution of control architecture saw the relocation of control “intelligence” to the ﬁeld instruments themselves. In other words, the new idea was to equip individual transmitters and control valve positioners with the necessary computational power to implement PID control all on their own, using digital networks to carry process data between the ﬁeld instruments and any location desired. This is the fundamental concept of ﬁeldbus.
“Fieldbus” as a technical term has multiple deﬁnitions. Many manufacturers use the word “ﬁeldbus” to describe any digital network used to transport data to and from ﬁeld instruments. In this subsection, I use the word “ﬁeldbus” to describe a design philosophy where ﬁeld instruments possess all the necessary “intelligence” to control the process, with no need for separate centralized (or even distributed) control hardware. FOUNDATION Fieldbus is the ﬁrst standard to embody this fully-distributed control concept, the technical details of this open standard maintained and promoted by the Fieldbus Foundation.
The aim of this Foundation is to establish an open, technical standard for any manufacturer to follow in the design of their ﬁeldbus instruments. This means a FOUNDATION Fieldbus (FF) transmitter manufactured by Smar will work seamlessly with a FF control valve positioner manufactured by Fisher, communicating eﬀortlessly with a FF-aware host system manufactured by ABB, and so on. This may be thought of in terms of being the digital equivalent of the 3-15 PSI pneumatic signal standard or the 4-20 mA analog electronic signal standard: so long as all instruments “talk” according to the same standard, brands and models may be freely interchanged to build any control system desired.
To illustrate the general ﬁeldbus concept, consider this ﬂow control system:
Here, a ﬁeldbus coupling device provides a convenient junction point for cables coming from the transmitter, valve positioner, and host system. FOUNDATION Fieldbus devices both receive DC power and communicate digitally over the same twisted-pair cables. In this case, the host system provides DC power for the transmitter and positioner to function, while communication of process data occurs primarily between the transmitter and positioner (with little necessary involvement of the host system (Note 1) ).
Note 1 : Although it is customary for the host system to be conﬁgured as the Link Active Scheduler (LAS) device to schedule and coordinate all ﬁeldbus device communications, this is not absolutely necessary. Any suitable ﬁeld instrument may also serve as the LAS, which means a host system is not even necessary except to provide DC power to the instruments, and serve as a point of interface for human operators, engineers, and technicians.
Also Read : 4-20mA JB Versus Fieldbus JB
As with distributed control systems, FOUNDATION Fieldbus instruments are programmed using a function block language. In this case, we must have an analog input (for the transmitter’s measurement), a PID function block, and an analog output (for the valve positioner) to make a complete ﬂow control system:
The analog input (AI) block must reside in the transmitter, and the analog output (AO) block must reside in the valve positioner, since those blocks necessarily relate to the measured and controlled variables, respectively. However, the PID block may reside in either ﬁeld device:
Practical reasons do exist for choosing one location of the PID function block over the other, most notably the diﬀerence in communication loading between the two options (Note 2) . However, there is no conceptual limitation to the location of the PID function block. In a ﬁeldbus control system where the control “intelligence” is distributed all the way to the ﬁeld instrument devices themselves, there are no limits to system ﬂexibility.
Note 2 : With the PID function block programmed in the ﬂow transmitter, there will be twice as many scheduled communication events per macrocycle than if the function block is programmed into the valve positioner. This is evident by the number of signal lines connecting circled block(s) to circled block(s) in the above illustration.
Also Read : Foundation Fieldbus Interview Questions
- Foundation Fieldbus Split Range Valves
- Foundation Fieldbus Logics
- Difference between Fieldbus, Profibus and HART Protocols
- Foundation Fieldbus Tutorials
- Difference between Fieldbus and Profibus
- Foundation Fieldbus Standard Function Blocks
- What is Foundation Fieldbus (FF) ?
- H1 FF Device Configuration and Commissioning
- Convert 4-20ma current output to foundation fieldbus
- Control Valve Sequence Methods