FDI Common Host Components

FDI Common Host Components

Host ARCHITECTURE

The FDI host architecture is based on the information model used in the OPC Unified Architecture (OPC UA), which provides advantages such as platform independence. The FDI Server imports FDI Device Packages into its internal device catalog. As FDI Packages do not require registration in the sense of a software installation, there are no unpleasant side effects. The architecture supports hosts built around EDDL as well as FDT technology.

Common Host COmponents

The FDI Common Host Components - EDD Engine and UI Engine - ensure that an FDI Device Package or an existing EDD behaves in the same way in various FDI host system architectures. The EDD Engine supports the entire EDDL scope in a multiprotocol manner for FF, HART, PROFIBUS and PROFINET, and is backward compatible with existing EDDL binary formats for FF (ff4, ff5) and HART (fm8). The UI Engine is independent of communication protocols. It generates the device specific user interfaces from a device description. This means that, in future, system manufacturers no longer need to integrate three interpreter components, but only one. This saves time and effort, and aims to contribute to improving the quality and interoperability of host systems.

Order Now

 

 

The FDI host architecture is based on the information model used in the OPC Unified Architecture (OPC UA), which provides advantages such as platform independence. The FDI Server imports FDI Device Packages into its internal device catalog. As FDI Packages do not require registration in the sense of a software installation, there are no unpleasant side effects.

The representation of device instances in the FDI Server takes place in the information model. The information model maps the communication topology of the automation system by representing the entire communication infrastructure and the field devices as objects. This is also where the data, functions and user interfaces of the devices are stored. FDI Clients access the information model. By interpreting the EDD in its EDD Engine the FDI Server always ensures that the device data remain consistent.

The multiprotocol EDD Engine is backward compatible with existing EDD formats HART fm8 and FF ff4 and ff5. Existing EDDs can therefore be processed directly in an FDI host.  

FDI Host

In the FDT-based architecture, from the viewpoint of the FDI Package, the FDI DTM acts like an FDI host; for FDT framework applications, it acts as a DTM. For many FDT Frame manufacturers, this opens up an economically attractive migration route to FDI.

Also here the FDI Common Host Components are used to ensure interoperability. The backward compatibility of the EDD Engine enables execution of existing EDD formats HART fm8 and FF ff4 and ff5.

Related Content