A flexible acquisition cycle for incompletely defined fieldbus protocols

Găitan, Vasile Gheorghiţă; Gaitan, Nicoleta Cristina; Ungurean, Ioan

doi:10.1016/j.isatra.2014.02.006

Cited by 21 publications

(16 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Depending on the type of network, an acquisition cycle can be defined by which data in the buffer are updated periodically and prioritized depending on the criticality of the monitored data and the user configuration. An example of such an acquisition cycle is presented in [ 48 ].…”

Section: Description Of the Proposed Iiot Architecturementioning

confidence: 99%

A Software Architecture for the Industrial Internet of Things—A Conceptual Model

Ungurean

Gaitan

2020

Sensors

Self Cite

View full text Add to dashboard Cite

The Internet of Things (IoT) is an emerging concept that has revolutionized the use of new technologies in everyday life. The economic impact of IoT becoming very important, and it began to be used in the industrial environment under the name of the Industrial Internet of Things (IIoT) concept, which is a sub-domain of IoT. The IIoT changes the way industrial processes are controlled and monitored, increasing operating efficiency. This article proposes a software architecture for IIoT that has a low degree of abstraction compared to the reference architectures presented in the literature. The architecture is organized on four-layer and it integrates the latest concepts related to fog and edge computing. These concepts are activated through the use of fog/edge/gateway nodes, where the processing of data acquired from things is performed and it is the place where things interact with each other in the virtual environment. The main contributions of this paper are the proposal and description of a complete IIoT software architecture, the use of a unified address space, and the use of the computing platform based on SoC (System on Chip) with specialized co-processors in order to be able to execute in real-time certain time-critical operations specific to the industrial environment.

show abstract

Section: Description Of the Proposed Iiot Architecturementioning

confidence: 99%

A Software Architecture for the Industrial Internet of Things—A Conceptual Model

Ungurean

Gaitan

2020

Sensors

Self Cite

View full text Add to dashboard Cite

show abstract

“…As a solution for the IIoT, we propose and present in this article an architecture including communication systems (fieldbuses [11]), used in the industrial environments, and that can provide real-time facilities and predictability using a middleware system allowing the setting of different Quality of Service parameters. Furthermore, at the level of things, intelligent embedded systems can be developed, that can implement hard real time requirements specific to certain industrial processes.…”

Section: Things Based On Existing and Evolving Interoperable Informatmentioning

confidence: 99%

“…This level, aimed to acquire data from fieldbuses and to transmit it to the middleware level, contains a software communication module (as a software library) for each fieldbus. The purpose of this module is the implementation of both a specific fieldbus communication protocol and of the acquisition cycle [11], or even of the master specific to the fieldbus. Each software module exposes the same interface (API-MC from Fig.…”

Section: The Data Provider Levelmentioning

confidence: 99%

A Middleware Based Architecture for the Industrial Internet of Things

Ungurean¹,

Gaitan²,

Găitan³

2016

KSII TIIS

View full text Add to dashboard Cite

Due to its potential, the Internet of Things (IoT) begins to be used in the industrial field. Nevertheless, although the concept called the Industrial Internet of Things does not know a widely accepted definition, it is based on the existing technology, and introduces the IoT in the industrial environment through the compliance with specific additional requirements and by integrating various fieldbuses with distinctive features, from the real-time point of view. The aim of this paper is to propose a practical architecture for the Industrial Internet of Things. The proposed architecture is designed around the Data Distribution Service for Real Time System (DDS) middleware protocol, and it is organized on four levels. Between these levels, it is defined standard interface, and they can be developed independently. For this reason, the architecture is scalable because at the middleware level, the DDS can be replaced by other middleware systems. At the final, it is performed a comparison between several middleware systems used in the proposed architecture.

show abstract

“…These solutions are conceived to exploit either ring network topologies or full-duplex links (e.g., Fast Ethernet). Approaches like [14] try to bring slotting on legacy fieldbuses running on a shared bus, like MODBUS, which have no notion of time, so as to achieve temporal coherence in acquisition cycles. In [15] a solution aimed at increasing communication efficiency is described, which dynamically gathers multiple process data units from the same sender in a single CAN FD frame.…”

Section: Introductionmentioning

confidence: 99%

CAN With eXtensible In-Frame Reply: Protocol Definition and Prototype Implementation

Cena

Bertolotti

et al. 2017

IEEE Trans. Ind. Inf.

View full text Add to dashboard Cite

Abstract-Controller Area Network (CAN) has been the de facto standard in the automotive industry for the past two decades. Recently, CAN with flexible data-rate (CAN FD) has been standardized, which achieves noticeably higher throughput. Further improvements are still possible for CAN, by exploiting its peculiar physical layer to carry out distributed operations among network nodes, implemented as atomic transactions mapped on quasi-conventional frame exchanges.In this paper, a proposal is made for an extension to the CAN protocol, termed CAN with eXtensible in-frame Reply (CAN XR), which enables upper protocol layers to define new custom services devoted to, e.g., network management, applicationspecific functions, and high-efficiency data transfer. The key point is that CAN XR retains full backward compatibility with CAN, therefore there is no need to change the protocol specification once again.

show abstract

A flexible acquisition cycle for incompletely defined fieldbus protocols

Cited by 21 publications

References 29 publications

A Software Architecture for the Industrial Internet of Things—A Conceptual Model

A Software Architecture for the Industrial Internet of Things—A Conceptual Model

A Middleware Based Architecture for the Industrial Internet of Things

CAN With eXtensible In-Frame Reply: Protocol Definition and Prototype Implementation

Contact Info

Product

Resources

About