FC 131 - Plant Loop Gateway Point Definitions (NPPG01-02, INPPR01)

The Plant Loop gateway point definition function code defines the exception report data received or transmitted between a pair of gateway modules. The allowable block range is from eight to 5,000. For blocks configured in the range of eight to 1,023, exception reports are available at the GCM modules PCU address, module address two and the function code 131 block number. For blocks greater than 1,023, exception reports are generated at a virtual module address. The module address and the block numbers are derived according to the information in Table 131-1.

 

NOTE: The actual output of a function code 131 block does not indicate the exception report value. The actual exception reported data is contained within the internal data structures of the block

and reported directly to the PCU that requested it. The actual output of a function code 131 block is the status of the exception report data.

 

 

 

 

Outputs:

Blk

Type

Description

N

I

Status of incoming data with quality (local GCM module only):

00 = good status, good quality, specs and exception reports received

10 = bad status, good quality, specs received, no exception reports received

11 = bad status, bad quality, specs not received, exception reports not received

 

 

 

Specifications:

Spec

Tune

Default

Type

Range

Description

S1

N

0

B

Full

Exception report direction:

0 = from the remote gateway to the local gateway

1 = to the remote gateway from the local gateway

S2

N

0

I

0 - 31

Loop address exception from which report received

S3

N

0

I

0 - 5

Exception report data type:

0 = digital

1 = analog

2 = station

3 = remote control memory

4 = remote manual set constant

5 = device driver

S4

N

1

I

1 - 63

PCU address exception from which report received

S5

N

2

I

2 - 31

Module address exception from which report received

S6

N

0

I

0 - 1023

Block address exception from which report received

 

 

131.1   Explanation

 

A GCM module has a function code 131 block defined in it for every block exception reported through the gateway. For example, if there are 2,000 exception reported points in the system and 70 of them are passed between the local loop and loop four, the loop four GCM module must have these 70 points configured with function code 131 blocks. These blocks must be configured in both the local and remote GCM module regardless of direction of exception report.

 

The maximum number of points that may be configured in the GCM module depends on the point type and the number of devices that receive the exception reports generated by the GCM module. The total memory available is 450,560 bytes.

Use Table 131-2 to calculate memory usage.

 

 

 

 

131.1.1  Specifications

 

S1 - XDIR

Specification S1 is the exception report direction.

 

0 = from remote gateway to the local gateway

1 = to remote gateway from the local gateway

 

NOTES:

1. The remote gateway is the GCM module with the remote dipswitch set to remote.

2. In one way communication, S1 is meaningless.

 

This specification defines how information travels through the gateways. Direction is based on the local GCM module as a reference point. For example, if information transmits to the local GCM module from a remote loop, the direction parameter is zero. The observer sitting at the local GCM module receives information coming from another gateway. When the configuration is entered into the remote GCM module, S1 remains zero, because the perspective remains the same.

 

Set the communication type with S1. Since the local GCM module is the reference point, any block that has S1 equal to one transmits exception reports from the local loop to a remote loop. This action is permitted only in two way communication. With two way communication, only two loops can be linked, and both loops have the capabilities to control each other. If all exception reports have S1 equal to zero, then communication is one way, with remote loops transmitting data to the local loop, and the local loop transmitting data, tuning, and controlling the remote loop.

 

S2 - LADR

(Loop address) Specification S2 identifies the loop from which the exception report defined in this block comes.

S3 - XDATA

Specification S3 is the exception report data type.

0 = digital

1 = analog

2 = station

3 = remote control memory (RCM)

4 = remote manual set constant (RMSC)

5 = device driver

 

This specification defines the type of information carried in the exception report. The value of any type of data through logic can be changed with S3.

 

S4 - XPCU

Specification S4 is the PCU address. This specification identifies the PCU from which the exception report in this block comes.

 

S5 - XMOD

Specification S5 is the module address. This specification identifies the module from which the exception report in this block comes.

 

S6 - XBLK

Specification S6 is the block address. This specification identifies the block from which the exception report in this block comes.

 

 

 

131.1.2  Outputs

 

N

Output N is the exception report status.

0 = good

1 = bad

This output is not the value of the point, but a reflection of the status of the point. The value of the point is routed directly to the PCU that requested it.