FC 184 - Factory Instrumentation Protocol Handler

The factory instrumentation protocol (FIP) handler function code provides an interface between a primary and a redundant FIP module. Function code 184 is used with the IMFBM02 WorldFIP Server Module. The FIP handler function code manages the redundant operation by determining that a valid failure has occurred before switching to the secondary module. The input specifications contain the starting block address for all configured subscriber blocks. The status of both the primary and secondary FIP modules are outputs from the block.

 

NOTES:

  1. For more information on factory instrumentation protocol, refer to the FIP Application Description C46-602 which is written by the French Commission AFNOR, and the INFBA01 Programming Reference Manual.

  2. If configuring function code 184 for an Ethernet device interface slave (IMEDI01), refer to the IMEDI01 instruction for details and explanations of this function code.

 

 

 

 

Outputs:

Blk

Type

Description

N

B

Primary module status:

0 = good

1 = bad

N+1

B

Secondary module status:

0 = good

1 = bad

 

 

 

Specifications:

Spec

Tune

Default

Type

Range

Description

S1

N

0

I

0 - 63

Primary module address

S2

N

0

I

0 - 63

Secondary module address

S3

N

2

I

Note 1

Block address of analog input subscriber block

S4

N

2

I

Note 1

Block address of digital input subscriber block

S5

N

2

I

Note 1

Block address of analog output subscriber block

S6

N

2

I

Note 1

Block address of digital output subscriber block

S7

N

2

I

Note 1

Reserved

S8

N

0

I

Note 1

Reserved

S9

N

0

I

0 - 1

Continue on secondary module error:

0 = trip primary module

1 = continue to operate

S10

N

0

I

0 - 60000

Synchronization ID2

S11

N

0

I

0 - 60000

Reserved

S12

N

0

I

0 - 60000

Reserved

S13

N

0

I

0 - 100

Number of synchronization subsystem2

S14

Y

0.000

R

Full

Timer control3

S15

Y

1.000

R

0.0 - 255.0

Field bus segment number or WorldFIP field bus segment number. Refer to S15 explanation.

S16

Y

0.000

R

Full

Spare

 

NOTES:

  1. Maximum values are:9,998 for the BRC-100, IMMFP11/12 and 31,998 for the HAC

  2. For most applications, the default value shown will suffice for the specification.

  3. Refer to S14 explanation for field bus communications speeds.

 

 

184.1   Explanation

 

184.1.1  Specifications

 

S1

Address of the primary FIP module.

 

S2

Address of the secondary FIP module.

 

S3

Block address of the first analog input subscriber (function code 186).

 

S4

Block address of the first digital input subscriber (function code 185).

 

S5

Block address of the first analog output subscriber (function code 187).

 

S6

Block address of the first digital output subscriber (function code 188).

 

S7 and S8

Reserved.

 

S9

Sets the module operating status upon a module failure.

0 = trip primary module

1 = continue operation

 

S10

For most applications, the default specification value will suffice. Specification S10 is the synchronization ID. The synchronization ID is the FIP identifier of the synchronization variable that the FIP handler configures to synchronize the MFP module and the associated variables. At present, the MFP module does not synchronize its segment executions to this variable.

 

S11 and S12

Reserved.

 

S13

For most applications, the default specification value will suffice. Specification S13 is the number of the synchronization subsystem. This is the number of the subsystem that the current FIP handler manages. When S13 is zero, the current FIP handler manages the primary system and synchronizes the module. This refers to the synchronization clock on the dual port RAM register of the other I/O modules (I/O modules count the milliseconds and reset the clock on every synchronization). Any number above zero means the current FIP handler manages a subsystem and does no synchronization.

 

S14

Specifies several parameters dealing with the physical timing of the IMFBM02 module and bus arbitration capability. This

specification is set as follows:

 

 

S14 = TXCKL + RP + IEC + BA

 

where:

 

TXCKL

=

Bus speed

0 = 31.25 kbits/sec

1 = 1 Mbit/sec

2 = 22.5 Mbits/sec

 

RP

=

RTTime x 4

 

RTTime

=

Return time of the WorldFIP station in bit-time (time duration of one bit) in the range of zero to 63

 

 

Example:

 

At 1 Mbit/sec, the bit-time equals 1 μsec. Therefore, if RTTime = 8, the actual return time is 8 μsec. At 32 kbits/sec, the bit-time equals 31.25 μsec. In this example, RTTime = 8 means an actual return time of 250 μsec.

 

The return time (also known as turnaround time) is the length of time the WorldFIP station will wait before responding to transactions received on the WorldFIP field bus. In addition, it is also the amount of time the WorldFIP station will wait for other WorldFIP stations to respond to transactions it initiates.

 

The setting for this return time parameter is dependent on several physical link criteria such as the length and media type (twisted pair, coaxial, fiber optic, etc.) of the field bus segment. The setting for this parameter must correspond to the maximum return time setting for this field bus segment. The maximum return time setting for the field bus segment is determined by the maximum turnaround time of the slowest device on the field bus segment.

 

The IEC physical layer standard specifies a minimum return time of four bit-times and maximum return time of 32 bit-times.  Intermediate settings between these two ranges must be in four bit-time increments.

 

The physical layer parameter (IEC/FIP) specifies the choice between the IEC or FIP physical layer standard.  

 

where:

 

IE

=

Physical Layer

 

C/F

=

0 = IEC (WorldFIP)

 

IP

=

32768 = FIP

 

 

 

The bus arbiter occupation parameter specifies the number of kilobytes (within the range of one to 54) of RAM to reserve in the IMFBM02 module for the bus arbitration program. If BA (bus arbiter occupation x 256) is set to zero, then the bus arbitration function of the IMFBM02 is disabled.

 

S15

WorldFIP field bus segment number for the IMFBM02 WorldFIP Server Module. This number is used to uniquely identify a specific WorldFIP field bus segment among several that may be connected together via WorldFIP field bus bridge devices.

 

 

184.2   FIP Variable Input/Output Types

 

FIP variables may consist of one value or an array of values. The various types mentioned in S4 of function codes 185 and 186 and S12 of function codes 187 and 188 actually refer to the format of the values within a FIP variable.

 

The FIP input and output subscriber blocks are used to interface the Harmony controller with these FIP variables. Up to four FIP subscriber blocks of the same type may be associated with a single FIP variable. For FIP variables that contain an array of values, the maximum number of values for that array is 32. The individual elements of a FIP variable are associated to a particular subscriber block using the group number found in S3. The number of elements specified in S3 of the subscriber block is used to identify the number of values or elements within the FIP variable. The input/output type describes the format of the elements of the FIP variable. For most of the types, one block output is associated with each element of the FIP variable. The exception to this rule is for the digital types in which eight block outputs or inputs are associated with one element that has packed within it, eight values. FIP variables can also have a check byte associated with each element. The check byte is used to associate a quality flag with the data contained within the element.

 

Refer to Figure 184-1 for a list of the various input/output types and their formats.

 

 

 

 

184.3   Application

 

Figure 184-2 shows the FIP handler block linked to other FIP I/O blocks (function codes 185 through 188).