Testing the Verification and Validation Capability of a DCP-Based Interface for Distributed Real-Time Applications

Abstract

Cyber–physical systems (CPS) integrate diverse elements developed by various vendors, often dispersed geographically, posing significant development challenges. This paper presents an improved version of our previously developed co-simulation interface based on the non-proprietary Distributed Co-Simulation Protocol (DCP) standard, now optimized for broader hardware platform compatibility. The core contributions include a demonstration of the interface’s hardware-agnostic capabilities and its straightforward adaptability across different platforms. Furthermore, we provide a comparative analysis of our interface against the original DCP. It is validated via various X-in-the-Loop simulations, reinforcing the interface’s versatility and applicability in diverse scenarios, such as distributed real-time executions, verification and validation processes, or Intellectual Property protection.

Enhancing the Coupling of Real-Virtual Prototypes: A Method for Latency Compensation

“…FOH amplifies the discontinuity by a factor of four for one time step, according to Equation (8). The usage of EROS results in a large extrapolation error for five consecutive time steps, as this is the duration it uses signal values for before and after the discontinuity for extrapolation, according to Equation (19).…”

“…Just as the FMI facilitates the setup of co-simulations, the DCP standardizes the configuration and operation of the network communication between coupled prototypes, which enables the efficient setup of RVPs, even when the coupled prototypes originate from different vendors [17,18]. Since its introduction, the DCP has been improved several times, for example, in [19], where the DCP was combined with an already existing co-simulation interface to increase its compatibility with certain hardware platforms. Amongst others, the DCP has been successfully adopted by the authors of [20] to couple an electric machine and a combustion engine test bench, in [21], for coupling a 3D environment simulation to a vehicle simulation, and in our previous contribution [22] to couple a real and a virtual prototype across a large distance.…”