Fieldbus

Abstract: After more than ten years of experience with applications of fieldbus in automation technology, the industry has started to develop and adopt Real-Time Ethernet (RTE) solutions. There already exists now more than ten proposed solutions. International Electrotechnical Commission standards are trying to give a guideline and selection criteria based on recognized indicators for the user.

Abstract: The requirement for flexible operation is becoming increasingly important in modern industrial systems. This requirement has to be supported at all system levels, including the field level in process industry, as well as the cell and machine control levels in manufacturing industry, where fieldbus-based communication systems are commonly found. Furthermore, typical applications at these levels require both time- and event-triggered communication services, in most cases under stringent timing constraints, to convey state data in the former case and alarms and management data in the latter. However, neither the requirement for flexible operation under guaranteed timeliness nor for joint support of time and event-triggered traffic are efficiently fulfilled by most of existing fieldbus systems. This paper presents a new protocol, flexible time-triggered communication on controller area network, which fulfills both requirements: it supports time-triggered communication in a flexible way as well as being an efficient combination of both time- and event-triggered traffic with temporal isolation. These types of traffic are handled by two complementary subsystems, the synchronous and the asynchronous messaging systems, respectively. The paper includes a justification for the new protocol as well as its description and worst case temporal analysis for both subsystems. This analysis shows the capability of the protocol to convey real-time traffic of either type.

Abstract: A process controller implements an overall, user-developed control strategy in a process control network that includes distributed controller and field devices, such as Fieldbus and non-Fieldbus devices. A user defines the control strategy by building a plurality of function blocks and control modules and downloading or installing user-specified portions of the control strategy into the Fieldbus devices and the non-Fieldbus devices. Thereafter, the Fieldbus devices automatically perform the downloaded portions of the overall strategy independently of other portions of the control strategy. For example in a process control system that includes distributed field devices, controllers and workstations, portions of the control strategy downloaded or installed into the field devices operate independently of and in parallel with the control operations of the controllers and the workstations, while other control operations manage the Fieldbus devices and implement other portions of the control strategy.

Abstract: Fieldbus technology in industrial automation is not only relatively complex because of the number of solutions possible, but also, and above all, because of the variety of applications. Ironically, these in turn are responsible for the multitude of solutions available. If the analysis of the basic needs is relatively standard, as they will always involve connecting sensors, actuators, and field controllers with each other, the options in architecture are numerous and can impose the need for certain services. The required performances themselves and the QoS expected fundamentally depend on the applications. This paper traces this technology from its beginnings, which go back to the first industrial networks in the 1970s. The principal stages of development are recounted, from the initial requirement specifications to the current state of international standardization. The diverse technical solutions are then analyzed and classified. In particular, we study the temporal aspects, the medium access control protocols, and application relationships.