FC 219 - Common Sequence

The common sequence (CSEQ) function block serves as the interface between the connected batch sequence (BSEQ) function block and other (remote) batch sequences.

 

 

 

 

Outputs:

Blk

Type

Description

N

R

CSEQ campaign number

N+1

R

CSEQ batch number

N+2

R

CSEQ lot number

N+3

R

CSEQ reservation status

N+4

R

CSEQ ownership status

N+5

R

Spare

N+6

R

Spare

N+7

R

Spare

N+8

R

Spare

N+9

R

Spare

 

 

 

Specifications:

Spec

Tune

Default

Type

Range

Description

S1

N

30

I

Note 1

Block address of batch sequence block

S2

N

1

I

Note 1

Block address of control mode select (boolean):

0 = operator (manual)

1 = remote (automatic)

S3

N

6

I

Note 1

Block address of reserve allow input:

0.0 = reserve not permitted

1.0 = reserve permitted

S4

N

6

I

Note 1

Block address of ownership allow input:

-1.0 = ownership not permitted, queue is off and flush

0.0 = ownership not permitted, queue is on

1.0 = ownership permitted, queue is on

2.0 = ownership permitted, queue is off

S5

N

2

I

Note 1

Spare real input

S6

N

2

I

Note 1

Spare real input

S7

N

2

I

Note 1

Spare real input

S8

N

2

I

Note 1

Spare boolean input

S9

N

2

I

Note 1

Spare boolean input

S10

N

2

I

Note 1

Spare boolean input

S11

Y

1

R

0 - 9.2E18

Status update minimum time (in secs)

S12

Y

120

R

0 - 9.2E18

Status update maximum time (in secs)

S13

N

1

I

Full

Maximum number of program connections

S14

Y

0

I

Full

Spare parameter

S15

Y

0

I

Full

Spare parameter

S16

Y

0

R

Full

Spare parameter

S17

Y

0

R

Full

Spare parameter

 

NOTES:

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

 

 

 

219.1   Explanation

 

The following explanations describe each specification and provide details of how the CSEQ block interfaces with the BSEQ and batch historian (BHIST) function blocks.

 

219.1.1  Specifications

 

S1

Links the CSEQ block to a BSEQ block. The CSEQ block must be connected to the first output (N) of the BSEQ block.

 

S2

Selects the control mode of the CSEQ block.

0 = operator mode (manual batch sequence control)

1 = remote mode (automatic batch sequence control)

 

In the operator mode, the batch sequence recipe, phase and run/hold inputs control execution of the batch program.  Remote mode disables the batch sequence recipe, phase and run/hold inputs and control of program execution is available to other programs connected to the CSEQ block. Remote mode disables the campaign, batch and lot number inputs to the BHIST block. The campaign, batch, and lot numbers are passed to the BHIST from the CSEQ block.

 

S3

Reserve allow input. The reserve allow input determines if the CSEQ block may be reserved. Programs connected to the CSEQ block may request to reserve the common sequence. The act of reservation restricts future access to ownership (remote program control) of the common sequence.

0.0 = reserve not permitted, delete current reservation

1.0 = reserve permitted

 

S4

Ownership allow block input. The CSEQ block may be owned by only one program at a time. Specification S4 determines if a CSEQ block may be owned. Program requests for ownership that cannot be granted may be deferred to the ownership queue for later execution. This input also determines the status of the ownership queue.

-1.0 = ownership not permitted, ownership queue closed and cleared

0.0 = ownership not permitted, ownership queue open

1.0 = ownership permitted, ownership queue open

2.0 = ownership permitted, ownership queue closed

 

S5 through S7

Spare real input.

 

S8 through S10

Spare boolean input.

 

S11

Minimum time (in seconds) between status updates. Thus, S11 determines the maximum rate the CSEQ block reports status data to connected programs. This specification can limit the bus and loop traffic generated by rapidly changing CSEQ status data.

 

S12

Defines the maximum time (in seconds) between updates. In the event that CSEQ status data is unchanging, S12 determines the rate the CSEQ block checks the connection status of connected programs.

 

S13

Defines the maximum number of program connections that may be supported by the CSEQ block at once.

 

S14 through S17

Spare parameters.

 

 

 

219.2   Function Block Outputs

 

N

(CSEQ campaign number) Shows the current campaign number of the BSEQ block.

 

N+1

(CSEQ batch number) Shows the current batch number of the BSEQ block.

 

N+2

(CSEQ lot number) Shows the current lot number of the BSEQ block.

 

N+3

(CSEQ reservation status) Shows if the CSEQ block is reserved and which production variables (campaign, batch or lot) of ownership requesting programs must match the reservation. The value of N+3 is a three-digit integer:

 

                                                    

Examples:

 

000 = CSEQ block not reserved

100 = campaign number must match

011 = batch and lot numbers must match

111 = campaign, batch and lot numbers must match

 

 

N+4

(CSEQ ownership status) Shows if a remote program owns the CSEQ block.

0.0 = CSEQ block not owned

1.0 = CSEQ block owned

 

N+5 through N+9

Spare outputs.

 

 

 

219.3   Application

 

The primary objective of the CSEQ block is to reduce the number of function codes required to implement batch management or unit management program structures. In a common sequence configuration, the CSEQ block provides the interface between two BSEQ blocks. This interface serves as a communication path established by one batch sequence (client) connecting to a second batch sequence (server).

 

In order for a client program to gain control of a CSEQ block (server program), the client program must acquire ownership of the server. The client program that has acquired ownership of the CSEQ block (server) may perform the following operations on the server via the CSEQ block:

 

 

 

In this manner, the client to server relationship between programs, with the client potentially controlling the server program execution, is possible with the use of CSEQ blocks. One program may be the owner (client) of a second program or CSEQ (server) block, and be a server or common sequence to a third program. Figure 219-1 shows an example of a production train that illustrates this point.

 

 

 

In Figure 219-1, the BSEQ block performs its usual role of executing the batch program. The CSEQ block provides the interface by which the program may be shared and controlled by other batch programs. In the operator mode, the BSEQ block controls execution of the batch program normally. Recipe, phase and run/hold inputs to the BSEQ block control program execution. In this mode the BHIST block buffers data for batch records by batch and lot numbers selected by the BHIST inputs.

 

The remote mode disables the BSEQ block recipe, phase and run/hold inputs and the BHIST block campaign, batch and lot number inputs. The CSEQ block gains control of these inputs in the remote mode. Once a connected program acquires ownership of the CSEQ block, the program that owns the CSEQ block controls these inputs to the BSEQ and BHIST blocks.

 

NOTE: The E-STOP (executed stop) and operator acknowledge inputs to the BSEQ remain enabled in both modes.  The operator can suspend batch sequence execution despite the CSEQ mode.

 

All connected programs receive status information from the CSEQ block. Specifications S11 and S12 control the rate of transmission. The CSEQ block can only have one owner at a time and only the owner can send commands to the CSEQ block. The CSEQ block can be reserved with production ID numbers (campaign, batch and lot). This restricts future ownership of the CSEQ block to programs belonging to related production runs.

 

Before a program can communicate with a CSEQ block it must establish a connection to the CSEQ block. The CSEQ block has a configurable limit (S13) on the number of connections it can support at once. When a program is no longer interested in a CSEQ block, it may unconnect from the CSEQ block. Thus, making the connection slot available to other programs.

 

While a CSEQ block is connected, the following data is available to all connected programs:

 

 

Table 219-1 provides a description of the specification settings for that CSEQ block in Figure 219-3. Figure 219-2 is an example of a common sequence. Once there is a connection between the BSEQ block and the S1 input of the CSEQ block, no other connection to function blocks is required.