WP3 Write functional specification of MicroFIP replacement
Description
The work package 3 includes the
- collection of detailed information on how the current MicroFIP is used in CERN’s applications and which operation modes are not used.
The deliverables are
- A document
- describing the subset of modes that are used at CERN
- functional specification of the needed MicroFIP replacement
Note: The compatibility to the original MicroFIP should be kept so that existing documentation, experience and software can be used in CERN’s applications.
The estimated duration is
- Six manweeks
Timeline
Date | Description |
---|---|
06-03-2009 | Received requirements for a standalone MicroFIP for a potential FGClite (TE/EPC) |
09-03-2009 | Kickoff meeting of project held. The requirement of compatibility to the MicroFIP may be removed as the software stack is trivial (QK) |
31-03-2009 | Questionnaire being made |
09-04-2009 | 2nd Meeting held |
11-06-2009 | 3rd Meeting held. Presented first draft of functional specification. |
24-06-2009 | Meeting with G. Penacoba and Q. King |
26-06-2009 | nanoFIP functional specification v1.2 |
11-12-2009 | 4th Meeting held |
26-11-2010 | 5th Meeting held |
02-12-2010 | nanoFIP functional specification v1.3 |
09-05-2011 | 6th Meeting held |
10-05-2011 | nanoFIP functional specification v1.4 |
Outcome
Useful documentation
Notes
Where are the official specifications of the Protocol Data Unit (PDU) types as used in the MicroFIP?
- 40h: Compact value
- 50h: Presence
- 52h: Identification
It is likely that these PDU types and the contents of these data units are defined in the Manufacturing Periodical/Aperiodical Services (MPS) application layer specification (also described as Industrial Periodical/Aperiodical Services). However, I have not been able to find this specification describing these services in detail.
The only place where I could find some description is in MICROFIP HANDLER Software Release 1 User Reference Manual, ALS 50202
- 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 the 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.
E.Van Der Bij, E.Gousiou, June 2011