FC 201 - Data Point Definition (INIPT01)

The INFI-NET data point definition function code permits an INFI-NET or Plant Loop to import data from an INFI-NET or Plant Loop via the INFI-NET to Plant Loop interface. Specification S1 defines the point data type. The following Specifications table lists all the point types on the originating INFI-NET or Plant Loop that can generate exception reports of the corresponding type on the receiving INFI-NET or Plant Loop. Specifications S2 through S5 define the INFI-NET or Plant Loop loop, node, module and block address of the data point that this function code will import.

 

 

 

 

Outputs:

Blk

Type

Description

N

B

Block status for all point types except trend (good quality):

0 = specifications and exception reports received

1 = specifications received, exception reports not received

 

Block status for all point types except trend (bad quality):

0 = specifications not received, exception reports received)

1 = specifications not received, exception reports not received

 

Block status for trend point (good or bad quality):

0 = trend data request received

1 = trend data request not received

 

Remote IPT module ID (good quality):

0 = link to remote IPT module is good

1 = link to remote IPT module is bad

 

Remote IPT module ID (bad quality):

0 and 1 = specifications not received

 

Remote module status (good quality):

0 = module status exception received, error summary is 0

1 = module status exception received, error summary is 1

 

Remote module status (bad quality):

0 = module status exception not received, error summary is 0

1 = module status exception not received, error summary is 1

 

 

 

Specifications:

Spec

Tune

Default

Type

Range

Description

S1

N

0

I

0 - 11

Import data type:

0 = digital (function code 45)

1 = analog (function code 30, 70 or 151)

2 = station (function code 21, 22, 23 or 80)

3 = remote control memory (function code 62)

4 = remote manual set constant (function code 68)

5 = device driver (function code 123, 129 or 136)

6 = trend point (function code 66)

10 = remote station ID

11 = remote module status

S2

N

1

I

1 - 250

Source loop for data

S3

N

1

I

1 - 250

Source node for data

S4

N

2

I

0 - 31

Source module for data

S5

N

1

I

0 - 9998

Source block for data

 

 

201.1   Explanation

 

The INFI-NET to Plant Loop interface may be operated as a bridge (bridge mode) or configured gateway (non-bridge mode). No function code 201 configuration is required when the INFI-NET to Plant Loop interface is operated as a bridge on an INFI-NET. When the INFI-NET to Plant Loop interface is on a Plant Loop or it is being operated as a configured gateway, function code 201 configuration is required.

 

The function block range for this function code is 30 to 9,998. When the INIPT02 module containing this function code is on an INFI-NET, the exception reports are made available at the interface node address, module address two, and function code 201 block number. Because Plant Loop exception reported blocks must fall in the range of zero to 1,023, a virtual addressing mechanism is used when the INIPT02 module containing this function code is configured on a Plant Loop. For blocks in the range of 30 to 1,023, exception reports are made available at the interface node address, module address two and function code 201 block number. For blocks greater than 1,023, the module address and block number are derived as shown in Table 201-1.

 

 

 

For example, a function code 201 is configured in the INFI-NET to Plant Loop interface at block address 2000. The specifications S1 through S5 define the INFI-NET loop, node, module address, and block number on the INFI-NET. A Plant Loop node may request the corresponding exception reports at the interface node address, module three, and block 976.  Consoles on the Plant Loop can request trend data from INFI-NET by directing the requests at each INFI-NET data point definition block specified as a trend point type (S1 equals six). For this case, a fixed module number of two and block numbers in the range 30 to 9,998 must be used for the trend block location specified by S2 through S5.

 

The output of this block reflects the status of the block import data, rather than the exception report data values themselves.

The output for a trend type block indicates whether or not a request for trend data has been received.

 

 

 

201.1.2  Specifications

 

S1

Specification S1 identifies what type of data the INFI-NET side is importing to the Plant Loop.

0 = digital (function code 45)

1 = analog (function code 30, 70 or 151)

2 = station (function code 21, 22, 23 or 80)

3 = remote control memory (function code 62)

4 = remote manual set constant (function code 68)

5 = device driver (function code 123, 129 or 136)

6 = trend point (function code 66)

10 = remote station ID

11 = remote module status

 

The specification value of 10 is only used in non-bridge mode IPR interfaces and it identifies the address (loop, node, module, and block number) of an INIPT02 module to which this INIPT02 module is to communicate. The specified module address and block number must always be set to two and zero respectively. At least one function code 201 (S1 = 10) must be configured in each INIPT02 module that is operating in non-bridge mode. A non-bridge mode INIPT02 module that is the central participant in a multiple remote configuration must contain a function code 201 (S1 = 10) for each INIPT02 to which it expects to communicate. A non-bridge mode INIPT02 module that is a remote participant in a multiple remote configuration must only contain a single function code 201 (S1 = 10). Function code 201 with S1 set to zero through six or

11 that follow a function code 201 with S1 set to 10 will be associated with the function code 201 (S1 set to 10) they follow.

 

Example One

A system has one local IPR interface and two remote IPR interfaces. The local IPR interface is connected to node 54 of loop five. One remote IPR interface is connected to node seven of loop 10 while the other is connected to node nine of loop 50. Ten analog points (function blocks 100 through 109) and the module status (function block zero) are to be imported from node 15 of loop 10 and node 43 of loop 50. The local IPT module configuration is shown in Figure 201-2.

 

 

The specification value of 11 is only used in non-bridge mode IPR interfaces and it identifies the address (loop, node, module, and block number) of a module on the other side of the link whose status is to be imported. This importing of status can occur from local to remote IPR interfaces and from remote to local IPR interfaces but not between remote IPR interfaces. The specified block number must always be set to zero. The presence of a function code 201 with S1 set to 11 causes a virtual module to appear at the local IPT node address. This virtual module is used as a proxy for the module whose status it is configured to present. The virtual module also monitors and downloads configurations and firmware, provides module status reports (either exception reported or on-demand), and provides problem reports. Virtual module numbers are assigned during IPT module startup while the function blocks with S1 set to 11 are initialized in block order.  The first function block with S1 set to 11 that is initialized is assigned the virtual module address of four. The second is assigned the virtual module address of five and so on. Up to 27 virtual modules can be used with the maximum virtual module address being 31.

 

Example Two

The configuration detailed in Example One would create virtual modules four and five in response to function code 201  (with S1 set to 11) residing at function blocks 110 and 210.

 

Requests directed to virtual module four are sent to the remote module whose address is loop 10, node 15, and module three. The block number specified in the request is sent on to the remote IPT module unchanged.

 

An operator assigned trend that requests data from loop five, node 54, module five, block 22 will display the value of the seconds counter in the extended executive block of the remote IPT module in loop 50, node 43, module 3, block 22.

 

S2

Specification S2 identifies the data source loop address.

 

S3

Specification S3 identifies the data source node address.

 

S4

Specification S4 identifies the data source module address.

 

S5

Specification S5 identifies the data source block number.

 

 

 

201.1.2  Outputs

 

N

Function code 201 has one output. It provides the status of all point types except trend, remote IPT module ID, and remote module status. Output N also provides confirmation of receipt for trend points.

 

Block status for all point types except trend when quality is good:

0 = specifications and exception reports received

1 = specifications received, exception reports not received

 

Block status for all point types except trend when quality is bad:

0 = exception reports received, specifications not received

1 = exception reports not received, specifications not received

 

Block status for trend point when quality is good or bad:

0 = trend data request received

1 = trend data request not received

 

Remote IPT module ID when quality is good:

0 = link to remote IPT module is good

1 = link to remote IPT module is bad

 

Remote IPT module ID when quality is bad:

0 and 1 = specifications not received

 

Remote module status when quality is good:

0 = module status exception received, error summary is 0

1 = module status exception received, error summary is 1

 

Remote module status when quality is bad:

0 = module status exception not received, error summary is 0

1 = module status exception not received, error summary is 1