Like so many other industrial data networks, FOUNDATION Fieldbus is an “unswitched” or “broadcast” type of network. This means all data transmissions by all devices on a network are sensed by all the other devices. In other words, there are no private messages between two devices on a shared network: every device “hears” every transmission from every other device. This means devices must take turns communicating, with no simultaneous transmissions. Layer 2 of the OSI Reference Model is where we define the “data link” elements of a digital data network, describing how individual devices negotiate for the right to transmit on the network. Here is a list of some layer-2 properties of H1 FF networks:
- Master/slave network behavior for cyclic communications (i.e. one device polls the others, and the others merely respond)
- Delegated token network behavior for acyclic communications (i.e. devices serially granted time to broadcast at will)
- Dedicated “scheduler” device for coordinating all segment communications
- 8-bit address field (0 through 255 possible)
- Maximum of 32 “live” devices on a segment
On an operating H1 segment, one device called the Link Active Scheduler (abbreviated LAS) functions as the “master” device for coordinating all network communications, analogous to a police officer directing traffic in a road intersection. The LAS device may be a regular field instrument (e.g. transmitter, valve positioner) or it may be the host system (i.e. the H1 segment interface card of a DCS). The FF standard allows for one operating LAS device, with multiple back-up LAS devices waiting to take over if the primary LAS happens to fail for any reason.
One of the tasks of the LAS is to “compel” the various field instruments to transmit their process control data (process variables, PID control output values, and other variables essential for loop monitoring and control), while the devices immediately respond in answer to the LAS’s “compel data” command. These critical communications occur on a regular schedule, and therefore are referred to as scheduled or cyclic communications. Cyclic communication operates in a “master-slave” fashion, with the LAS acting as the master (commanding slave devices to broadcast specific data), and all other devices responding only when called upon by the LAS. This form of communication is analogous to a traffic policeman specifically directing one vehicle at a time to drive through an intersection in a prescribed manner.
Periods of time in between these critical transmissions on an H1 network are used for device’s internal processing (e.g. PID algorithm execution, diagnostic checking) and also for less-critical data transmission. It is during these unscheduled or acyclic times that devices are sequentially given permission by the LAS to broadcast data of less importance such as operator setpoints, PID tuning constant updates, alarm acknowledgments, and diagnostic messages. Acyclic communication operates in a manner similar to “token-passing,” with the LAS issuing time-limited tokens to the other devices in sequence permitting them to freely broadcast whatever other data they have to share. This form of communication is analogous to a traffic policeman directing an entire lane of vehicles to enter the intersection at will.
The scheduled nature of cyclic communication guarantees a certain maximum response time to critical control functions, an important property of control networks called determinism. Without determinism, a control system cannot be relied upon to perform critical regulatory functions in a timely manner, and sequencing of control functions such as PID, summers, subtractors, ratio multipliers, and the like may be compromised. Thus, all the critical variables of a FF H1 loop are communicated between devices this way.
- Foundation Fieldbus Communication Management
- Fieldbus Device Capability
- HART Communication Tutorial Part 2
- Difference between Fieldbus, Profibus and HART Protocols
- What is HART, Foundation Fieldbus & Profibus ?
- H1 FF Physical layer
- HART Communication Tutorial Part 3
- Industrial Automation Communication Protocols
- Foundation Fieldbus (FF) Segment Topology
- WirelessHART Network Gateway Device