WorldFIP data flow is controlled by a Bus Arbiter which controls the data exchanges of periodic and aperiodic variables and messages.
Periodic exchange of variables is used for "on time" data exchanges between a producer and one or several consumer(s). It is mainly used for on-line real time exchanges between applications running in different devices (PLC and I/O nests for instance). Aperiodic exchanges and messages are primarily used for configuration, parameter settings, and diagnosis applications. They are also use for non time-critical exchanges, such as events transmission (time stamped data) between a supervisory console and a field device or a PLC.
A specific technology has been designed to achieve the cost and easiness goals. A product built using Device WorldFIP technology is fully compatible with other equipments built using one of the other available WorldFIP sets of components (FULLFIP2, FIPIU 2), with the restriction indicated above.
Profile 1.2 : which provides the user with the same as Profile 1.1, except the size of the two application variables, the sum of which has to be less than 120 bytes.
For further information, refer to the "Interoperability Guides - Profile 1 Devices" document included in this Device WorldFIP Development Kit
Top
2. Device WorldFIP Solution: Technology
2.1 Introduction
2.2 Device WorldFIP Basic Technology
2.3 MICROFIP Component Description
2.3.1 MICROFIP Stand-Alone -- Profile 1.1
2.3.2 MICROFIP Micro-controlled Mode -- Profile 1.2
2.4 MICROFIP HANDLER Software
2.5 Line Drivers and Isolation Components
2.6 Cabling Components
Device WorldFIP provides a subset of the standardized WorldFIP set of services. Peculiarly, it does not allow the Bus Arbiter function, and hence is dedicated to agents' equipment, in architectures as follows:
In such an architecture, all the data exchanges are controlled by the Manager (which implements the Bus Arbiter function), and are made between the Manager and the agents. Due to restrictions in the addressing scheme of the solution, no direct exchange between agents equipment is permitted.
Device WorldFIP is based on a set of hardware and software components designed or selected for achieving a LOW COST and EASY TO IMPLEMENT solution:
- a protocol component MICROFIP
- its associated handler (when needed) MICROFIP HANDLER
- a line driver and line transformer
- a specific connecting set (FIELDTAP and DCTAP)
MICROFIP is an ASIC solution implementing the WorldFIP protocol and is able to communicate at the three standards speeds, 31,5 kbit/s, 1Mbit/s and 2,5 Mbit/s. It implements the management of the medium redundancy, and can be associated without external glue with the FIELDRIVE and the CREOL line drivers for copper twisted pair cable.
The MICROFIP chip is in a MQFP100, and can be supplied either under 3,3 or 5 volts with a very low power consumption. Its operating temperature range is -40°C / + 85°C.
MICROFIP is able to operate with or without an associated microcontroller.
- "Stand Alone" mode when operated without a microcontroller
- "Microcontrolled" mode when operated with a microcontroller. In that case, the MICROFIP HANDLER software is a library which provide a set of simple commands to easily access the resources of the MICROFIP chip.
MICROFIP operating in a Stand Alone mode (Profile1.1) allows the product to interface directly on the process inputs and outputs through two 8-bit bi-directional ports. The ports states are directly mapped on the network using 1 produced variable (identifier: 06xy with xy as subscriber physical address) for inputs and 1 consumed variable (identifier: 05xy with xy as subscriber number) for outputs.
MICROFIP operating in a Stand Alone mode can be automatically started after the power on initialization or after having received a start command by the configuration variable (identifier: 03xy with xy as subscriber number). This configuration variable contains 2 bytes dedicated to the I/O ports configuration.
MICROFIP operating in a Stand Alone mode takes the xy subscriber physical address on a dedicated port and the promptness and refreshment statuses are managed by MPS variables and set by dedicated pins.
MICROFIP operating with a micro-controller does not require any external logic glue for most of them (8051,68HC11,...). The use of microprocessors (80186, 68000,...) is also simplified.
MICROFIP communication resources are accessed by the micro-controller through an embedded dual port memory shared with the protocol machine.
In this Profile 1.2, MICROFIP has to be configured with 1 configuration consumed variable (identifier: 03xy with xy as subscriber number), 1 application produced variable (identifier: 06xy with xy as subscriber physical address) and 1 application consumed variable (identifier: 05xy with xy as subscriber number), sharing a global resource capability of 15 blocks of 8 bytes. The variables identifiers are allocated in the physical field.
The promptness and refreshment statuses are managed for all the MPS variables and the period can be selected through possible values.
MICROFIP takes its subscriber number directly from the dedicated pins during the chip set-up and can be modified later by the micro-controller.
When MICROFIP is controlled by an external micro-controller, this one can access the input-output ports (through the "user" interface).
For further information, please refer to MICROFIP User Reference Manual document.
This software provides the user application program with easy access to the MICROFIP chip. It is designed as a library to be linked with the user application program and run in the host micro-controller. It is written in ANSI/C language and requires less than 2 kbytes of memory.
It is available in ANSI/C source code as freeware.
The MICROFIP HANDLER software offers the following services:
- Initialization of the component
- Variable writing
- Variable reading
- Event management
- Access to input/output ports
For further information , please refer to the MICROFIP HANDLER User Reference Manual document included in the Device WorldFIP Development Kit
The MICROFIP components can be used with the FIELDRIVE or the CREOL line drivers, and their associated transformers (according to the speed chosen), without any additional glue.
The medium redundancy is built in the MICROFIP chip, and provides a simple management compatible with either FIELDRIVE and CREOL capabilities.
For further information , please refer to:
- the «FIELDRIVE User Reference Manual» document
- the «CREOL User Reference Manual» document
included in this Device WorldFIP Development Kit
A specific set of cabling elements are proposed for achieving a LOW COST implementation of the Device WorldFIP solution:
- FIELDTAP connecting element, low cost tap for fieldbus
- DCTAP, daisy chain TAP, as subscriber connector and tap
They are to be used with the standard WorldFIP cable (principal and drop cables).
For further information, please refer to the «Device WorldFIP Development Kit - Cabling your WorldFIP network» document included in this Device WorldFIP Development Kit.
Top
3. How to Implement Device WorldFIP
3.1 Available Hardware Components & Sub-systems
3.2 Hardware Design
3.3 Software Design
3.4 Device Configurator: OLGA Communication Builder - Optional Tool
3.5 Test Manager: FIP DESIGNER - Optional Tool
3.6 Line Observer: FIP ANALYSER - Optional Tool
Device WorldFIP technology is designed to be EASY TO USE. Its integration in an equipment does not require any specific knowledge in fieldbus, except the basic knowledge needed to develop electronic hardware and application software when using the micro-controlled mode of the MICROFIP component.
The following items are made available for hardware implementation:
- set of specific components, namely MICROFIP, FIELDRIVE or CREOL and their associated transformer, (depending on the bit rate),
- CC165, ISA single format and PC 104 daughter board
- MICROFIP-CREOL daughter board
- CC 131 daughter board (MICROFIP-FIELDRIVE)
The hardware dedicated to the WorldFIP connection can be integrated in the main hardware of the device to be connected, or can be on a separate board.
According to the solution retained, different simple solutions are possible:
- design the hardware relative to the WorldFIP connection using the components listed above, plus general purposes commercially available components, (diodes, resistors, ...), according to the schematics given in «Device WorldFIP Development Kit - Designing your Hardware» document and in the user manual of the components above
- use an already existing board, CC165 , CC 131 or MICROFIP-CREOL daughter board, and integrate it in your design according to the board interface described in the user manual of the selected board.
The primary test of the hardware will be made according to the general rules for hardware testing and debugging. Then the verification of good operation of the WorldFIP communication part will be made using the Development Kit tools described in chapter 3.3 , hereunder.
For design using the microcontrolled mode of the MICROFIP chip, MICROFIP HANDLER has to be linked with the user application of the device. This software has to be configured. For that purpose, the use of the OLGA Communication Builder TOOL is of major interest and help.
Testing the software needs to build a small network, enabling exercise ofthe device and its WorldFIP communication. This can be done with the help of the other tools provided in the development kit, described hereunder, FIP DESIGNER, and FIPANALYSER, used in the following development and test bench.
OLGA Communication Builder is a software tool used to generate on a PC under Windows the description of a WorldFIP device. It is a general purpose tools which has to be used for the configuration of a MICROFIP based device (used in its microcontrolled mode).
OLGA Communication Builder allows you to:
- describe the WorldFIP communication stack characteristics of the device
- export all useful files for the MICROFIP HANDLER library
- re-use each created device in OLGA Network Starter Kit.
For further information, please refer to the «OLGA Communication Builder User Reference Manual» document included in the Device WorldFIP Development Kit.
FIPDESIGNER is a software tool to be used by a developer to build a Test Manager equipment.
With the user-friendly Man Machine Interface, it enables to create the Bus Arbitrator function and access the Device WorldFIP equipment.
The Bus Arbiter configuration can be described simply by declaring the exchanges and the associated time constraints.
Network access facilities enable the WorldFIP variables exchanged to be read/written.
FIPDESIGNER is used on a standard PC running under Microsoft Windows 3.1 or Microsoft Windows 95, and fitted with a CC121 board ( 1Mbps )
FIPANALYSER is a software tool for network (1 Mbit/s) observation during each system operating phase. It allows an analysis of the data which are exchanged on the network.
Recommended in the development phase of the Device WorldFIP interface, this tool provides the usual functions of a network observer:
- Display and recording of frames circulating on the network
- Filtering according to type of frame or variable
- Control of the scanning period of a variable
- Etc.
The FIPANALYSER software runs on a standard PC running under DOS and fitted with a FPC10 board (1Mbit/s).
Top
4. Device WorldFIP Development Kit
4.1 Introduction
4.2 Sets of Components
4.3 MICROFIP HANDLER
4.4 PC ISA / PC 104 Evaluation Board: CC 165
4.5 ;MICROFIP-CREOL Daughter Board
4.6 MICROFIP-FIELDRIVE Daughter Board: CC131
4.7 OLGA Communication Builder
4.8 FIP DESIGNER
4.9 FIP ANALYSER
4.10 Set of Documentation
The Device WorldFIP Development Kit contains all the elements needed to develop and test a Device WorldFIP equipment running at 1 Mbit/s (for other bit rates, please consult WorldFIP Organization), including a set of components for making a limited number of prototypes.
It is composed of the following items:
This chip set is composed of:
The board can be used in classical desktop, plugged in its ISA slot, for making an initial evaluation of the MICROFIP structure and to refine the application software before it is definitively integrated into the equipment, as well as in an embedded industrial equipment which can receive PC104 compliant boards.
The parallel ports managed by MICROFIP can be accessed on the board using a dedicated connector.
The board is equipped with MICROFIP, and a single medium Medium Attachment Unit based on the FIELDRIVE + FIELDTR solution.
Up a level