WorldFIP
WorldFIP is a fieldbus network protocol designed to provide links between level zero (sensors/actuators) and level one (PLCs, controllers, etc.) in automation systems.
Standards
IEC 61158 and IEC 61784
Introductions to WorldFIP
- FIP Network General Introduction (originally at http://www.fipware.fr/pdfs/50249_nt.pdf)
- The WorldFIP Protocol
These documents show that the WorldFIP protocol is part of European fieldbus standard EN50170. However, it turns out that the standards series EN 50170 has been replaced by the 61158 series ("Industrial communication networks. Fieldbus specifications"), in particular:
- 61158-1: overview and guidance to 61158 and 61784 series
- 61158-2: the physical layer (2007)
- 61158-3-7 and 4-7: the data-link layer (2007)
- 61158-5-7 and 6-7: the application layer (2007)
- IEC 61784-1 Ed 2.0 (2007-12): Industrial communication networks . Profiles. Part 1: Fieldbus profiles
- IEC 61918 Ed 1.0 (2007-12): Industrial communication networks. Installation of communication networks in industrial premises.
These 8 standards are included in a CD-ROM IEC FIELDB-CPF-5 Ed. 1.0 Industrial communication networks - Fieldbus - Communication Profile Family 5: WorldFIP.
The European fieldbus standard EN50170 is available from the CERN document server (CERN intranet only. Thanks to Tullio Basaglia of the CERN Scientific Information Service).
EN 50170
-
NF EN 50170 Système de communication de terrain pour application générale.
- Volume 3/3 (WorldFIP) (pdf page 994).
-
NF EN 50170/A2 Système de communication de terrain pour application générale.
MICROFIP HANDLER Software User Reference Manual
The detailed contents of the so-called MPS variables is not defined in any of the above standards. I have not been able to find any other description than in the MICROFIP HANDLER Software Version 4 User Reference Manual.
-
MICROFIP HANDLER Software Release 1 User Reference Manual,
ALS 50202(from
http://www.fipware.fr/pdfs/50202_nt.pdf).
- 1.3.4.1 A definition of Promptness, Refreshment and a bit that's not in the IEC specifications called Significance (meaning: the variable has been written at least once) is given.
- 1.3.4.2 Format of Variables produced on network (but this is for so-called dynamic variables, but the STATUS byte is the same (bit 0=refreshment, bit 2=significance, other bits may be anything).
- 1.5 Detailed description of the variables Report, List of equipment present, Presence, Identification, Time and others. However, the Identification variable described has not the same PDU type and format as described in the MicroFIP manual.
FIP DEVICE MANAGER Software User Reference Manual
Other information
-
ALSTOM FIPWARE site (Product leaflets and
User documentation only work with IE)
- January 2014: the fipware.com site does not exist anymore.
- Some documents are available at fipware documentation on this site.
- The WorldFIP organization with the website "www.worldfip.org" was dissolved in 2007.
Note: links to the Fieldbus standards only available on CERN's Intranet.
Finding your way in the IEC Standards
The comments below may be helpful to find your way in the IEC standards.
-
IEC-61784-1 Industrial communication networks: Profiles : Part 1:
Fieldbus
profiles
- 3.3 Conventions (pages 19-20)
- 9 Communication Profile Family 5 (WorldFIP), Profile 5/1 (pages 208-217). Table 257 in section 9.2.1 defines what to use from IEC 61158-2 (PH layer).
-
- 9 Medium dependent sublayer (MDS) (page 120-123, defines coding, preamble, start/end of frame delimiters). Strangely enough Table 257 of IEC-61784 specifically states that this clause is not included in the profile 5/1 WorldFIP, but it corresponds to "The WorldFIP protocol" brief).
- 11.6 Jabber inhibit - describes the MAU should self-inhibit in case of too long transmissions (and reset after 0.5 to 3 seconds). If implemented in FielDrive, it may mean that it can inhibit itself if this logic is sensitive to radiation.
-
- Explains variables and messages, adressing and flow control.
-
- 4.2 Block diagram of a producer/consumer entity
- 5 General structure and encoding of PhIDUs and DLPDUs and
related elements of procedure (pages 32-43)
- 5.2 defines values for ID_DAT, RP_DAT control field.
- 5.2.5 defines the Frame Checksum FCS (CRC).
- 5.6.3 defines timers (e.g. T0=max allowed silence on link, T4=monitors absence of RP_DAT after ID_DAT-a.k.a. Silence Time in the MicroFIP specification).
- 6.4 Buffer transfer (pages 44-46)
- 7.2 Produce/consumer entity
- Figure 45: Simplifified state machine for a producer/consumer entity
- 7.2.1 transition table for producer/consumer entity (state machine)
- 7.4 Management of basic transactions
- Annex A Exemplary FCS implementation (page 97-98)
-
- 6.2.1.3.3.3 Variable transmission validity specification (Promptness)
- 6.2.1.3.3.4 Variable production validity specification
-
IEC-61158-6-7 Industrial communication networks: Fieldbus
specifications : Part 6-7: Application layer protocol specification
– Type 7
elements
- 5 Transfer syntaxes (Identification byte, number of content
bytes, content, ...)
- 5.2.1.4.2 VariableCompactValue PDU (production status, refreshment, but no explanation about refreshment)
- 5 Transfer syntaxes (Identification byte, number of content
bytes, content, ...)
WorldFIP usage at CERN
- WorldFIP @ CERN
- WorldFIP Users Club (hosted at CERN)
At CERN over 450km of WorldFIP cables is installed, serving a total of
about 12000 nodes. All of this is required for the lifetime of the LHC
operation timescale of 15-20 years.
WorldFIP is used in eight principle systems of the CERN accelerator
complex:
- Power Converter Controls
- Quench Protection Systems
- Cryogenic Controls
- Beam Diagnosis and Instrumentation
- Radio Frequency
- Survey
- Experiments
- Radiation Monitoring
E.Van der Bij, December 2011, January 2014