Applications

Due to its flexible architecture the GPFC can support a wide range of control applications. Although the primary design goal was a small but powerful fieldbus controller, the GPFC actually is a general purpose device not limited to specifically fieldbus applications. Below are presented some foreseen application classes and real examples.


Fieldbus controller

To use the GPFC as a fieldbus controller, one need to install an appropriate IP module to connect to the fieldbus. There are many such modules on the market, which support CAN, Profibus, MIL1553 and other fieldbuses (see GRoupIPC directories for more information). Connection to the higher level control system resources can be provided with another IP module, or the onboard serial communication channel:

Ethernet communications are supported too (via the IP interface), so the GPFC can be attached directly to the control network:

The basic, single board GPFC configuration has two IP "slots", thus providing a simple, single branch controller to be implemented. When more fieldbus branches are to be connected one can extend the GPFC with an additional board carrying two more IP-modules.

Example application: EPICS IOC node

A specific fieldbus controller application is now considering at DESY, an EPICS IOC (I/O controller) node to control the equipment via CAN fieldbus. For this application the GPFC will be equipped with CAN and Ethernet interfaces (IP modules) and will run EPICS IOC software:


Intelligent fieldbus node

The GPFC can also be used as a device controller, being an intelligent fieldbus node. Just install an appropriate IP module, for example, analog/digital I/O:

Example application: SEDAC crate controller

An example of an intelligent fieldbus node application is a GPFC based crate controller for SEDAC system at DESY:

In this application the GPFC board is mounted inside the standard SEDAC module, which is installed in the crate, replacing the former non-intelligent crate controller. Such solution brings two new features to aged but still widely used at DESY SEDAC system: local computing resources and CAN/Profibus communications. This allows to offload expensive VME resources, currently driving SEDAC via dedicated serial bus, from a lot of communication traffic and low level control routines. This also replaces home-made SEDAC serial bus with industry standard CAN or Profibus.


Networked device

The GPFC, equipped with an Ethernet IP module instead of a fieldbus interface, can convert a fieldbus node to a network device:

Due to powerful network facilities of VxWorks, a wide range of network devices can be implemented. These are not limited to control applications only: one can consider, for example, a simple and cheap network server, a dedicated gateway, etc.


Standalone device controller

At last, the GPFC can be used completely autonomously, to control a standalone device or subsystem:

A considerably sized application can be stored locally, in the onboard EPROM/FLASH memory pool. This basic resource can be further extended either with a FLASH IP module, or with an extension board carrying an additional FLASH pool.