Switch Pair

Fault Tolerant Ethernet

Redundant
Qualified or
Built-in
Unqualified
Modbus Control Firewall
Modbus Device
Device

C300

Peer Control Data Interface: Part 2

Global Automation College
November 6, 2007
SIM-C300 Honeywell Confidential and Proprietary SIM-C300
Describe SIM-C300 1 May 9, 2023
Topics Honeywell
• Purpose, Use, and Value
• Topology and principle parts
• Connections of Modbus device to C300 controller
• Number of Master and Request blocks
• Master block usage requirements
• Types and capacity of request blocks
• Master block configuration properties
• Configuration of Modbus simulator
• Configuration properties of different request
blocks
• Verify Master block statistics
• Device related alarms
• Detail display in Station
• Error codes

Honeywell Confidential and Proprietary

2 May 9, 2023
 Describe the Configuration Properties for
Different Request Blocks

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 3 May 9, 2023
Request Blocks Honeywell
• Request blocks retrieve data from Modbus devices
• Three types of Request blocks with the following templates are present in
the MBTCP library in Control Builder:
– MBTCPFLAGARRCH
– MBTCPNUMARRCH
– MBTCPTEXTARRCH

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 4 May 9, 2023
Request Blocks Honeywell

FTE Network

C300/SIM C300

Modbus Devices

PCDI Master Block

…..
Modbus Serial Devices (1-16)
Request Blocks (1-64)

Modbus Bridge

MODBUS Request
Blocks

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 5 May 9, 2023
Request Block Configuration Honeywell
• All Request Blocks have the same Main property page as shown below

Request Block Name

Master Block Selection. Select the

PCDI Master device block to which
this request block must be assigned

List of Assigned and Unassigned

channels for the selected Master
Block displays here

Assign and Unassign the channels to

the request Block

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 6 May 9, 2023
Request Block Configuration – Numeric Array Honeywell
• Numeric request blocks read/write numeric values from/to a Modbus
device

These parameters are common

for all the Request Blocks

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 7 May 9, 2023
Request Block Configuration – Numeric Array Honeywell

When selected, the Request Block

will execute as quickly as possible.
When deselected the Request Block
starts a single execution cycle on the
positive transition of the SENDFL
parameter when the DONEFL
parameter is true.

Used to specify which access level is

required to write to the array data
(Operator, Engineer or Other FB)

Device Address of the MODBUS

Device. The range supported is 1 to
247 and 255.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 8 May 9, 2023
Request Block Configuration – Numeric Array Honeywell
• Starting Element Index:
– Starting Address for the Numeric Block to Read/Write from/to the device
depending upon the Read/Write Option
– Defines the data type storage done in the Modbus end device
– The address range varies depending upon the Data type used in the End device.
For Numeric Block:
• 200001-265535: Read or Write from 1 to 60 contiguous Word Swapped
IEEE floating point numbers
• 300001-365535: Read from 1 to 120 contiguous Signed Integer numbers
This is read only addresses. Read/Write Option setting is ignored
• 400001-465535: Read from 1 to 120 or write a single Signed Integer
numbers
• 700001-765535: Read or Write from 1 to 60 contiguous IEEE floating point
numbers
• 800002-865535: Read or Write from 1 to 60 contiguous IEEE floating point
numbers Addr-1

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 9 May 9, 2023
Request Block Configuration – Numeric Array Honeywell
• 900001-965535: Read from 1 to 120 or write a single Unsigned Integer
numbers
– The number of values supported for Integer data type is 1 to 60 if the LONG
parameter (explained later in this presentation) is checked
– The full Modbus address is the last 5 decimal digits of the address
– The Modbus specification of the maximum amount of flags or registers that
can be written using one Modbus packet is used as the maximum limits for
each data type

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 10 May 9, 2023
Request Block Configuration – Numeric Array Honeywell
The number of numeric values to
read. This number may not exceed
60 or 120 depending on the starting
index

Explained in the next few slides

Used to specify what value to

substitute when an error occurs.
Either the Last Known Good value or
the value specified by the Value to
Substitute On Error parameter or
NaN

The value to substitute when error

occurs. When an error occurs, the
value in the edit box will be set, if the
substitution on error type is set to
SUBVAL Param

Converts the Data type of Numeric

Value to LONG when checked

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 11 May 9, 2023
Request Block Configuration – Read/Write Option Honeywell

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 12 May 9, 2023
Request Block Configuration – Read/Write Option Honeywell

WriteOnDiff A check is done to see if the value to write is different from

the value read from the device
A read occurs after the write has completed
WriteAlways A write is performed regardless of the current value or the
value being written
A read occurs after the write has completed
WriteOnChange A check is done to see if the value to write is different from
the last value written to the Device
A read occurs after the write has completed
ReadOnly Reads the value from the device. No write will be
performed
WriteAlwaysWriteOnly The same as WriteAlways
A read is not performed after the write
WriteOnChgWriteOnly Same as WriteOnChange
A read is not performed after the write

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 13 May 9, 2023
Read/Write Option – Write on Diff Honeywell

Input Request Block PCDI Device

PV = 8 Original PV = 7
PV written = 8
New PV = 8

• WriteOnDiff command compares the input value with the last PV read
– If they are different, the input value is written to the device
– If they are same, write operation is not performed
– Read operation is performed after write

• Case 1: If the Input to RB changes from 7 to 8, then

– WriteOnDiff compares input value (8) to last PV value read (7) and writes the new value
(8) to the device
– The value from the Device is read back (8) and gets updated in the PV of the Request
Block

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 14 May 9, 2023
Read/Write Option – Write on Diff Honeywell

Input Request Block PCDI Device

PV = 8 Original PV = 9

PV written = 8
PV = 8

• Case 2: If the PCDI Device PV changes from 8 to 9:

– The value from the Device is read and gets updated in the PV of
the Request Block (9)
– Since the Input value (8) is different from the PV value read (9),
a write occurs (8) to the device

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 15 May 9, 2023
 Read/Write Option – Write Always Honeywell

Input Request Block PCDI Device

PV = 8 Value to Write = 8
PV = 8
PV = 8

• WriteAlways performs a write regardless of the Current value or the

value being written.
– Read operation performed after the Write
• Case 1: If the Input to RB changes from 7 to 8, then
– WriteAlways mode unconditionally writes the new value (8) to the device
– Now the value from the Device (8) is read back and gets updated in the PV of the
Request Block
• Case 2: If the PCDI Device PV changes from 7 to 9, then
– Same as case 1. Value is always unconditionally written, followed by read of the PV
value

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 16 May 9, 2023
 Read/Write Option – Write on Change Honeywell
Input Request Block This is an internal PCDI Device
value and will not be
visible to the user

PV = 7 Last Value Written

to the Device = 7
PV = 7
PV = 7

• WriteOnChange command compares the Input value to write and the last value
successfully written.
– If Input Value is different from the Last Value Written, then the input value is
written to the Device
– If both are same then write operation is not performed
• Case 1: If the Input to RB changes from 7 to 8, then
– WriteOnChange command compares input (8) with the last value written (7). Since
the values are not same, the new value (8) is written to the device
– If the Write operation is successful then the Last Value Written gets updated with
the new value (8)
– Now the value from the Device is read back and updates the PV of the Request Block

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 17 May 9, 2023
Read/Write Option – Write on Change Honeywell
Input Request Block This is an internal PCDI Device
value and it will not
be visible to the user

PV = 7 Last Value Written

No Write
to the Device = 7

PV read = 9
PV = 9

• Case 2: If the PCDI Device PV changes from 7 to 9, then

– The Input value is compared to the Last Value Written. Since both are same
(7), the write operation will not be performed
– The value (9) from the Device is read and updates the PV of the Request Block
(9)

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 18 May 9, 2023
Read/Write Option – Read only Honeywell
Request Block (RB)
PCDI Device

PV = 8 PV = 8

• Read only Option is for reading the device value. Write

operation is not performed

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 19 May 9, 2023
WriteAlwaysWriteonly and WriteOnChgWriteonly Honeywell

• WriteAlwaysWriteonly and WriteOnChgWriteonly are

similar to WriteAlways and WriteOnChange, but they
don’t perform the read after the write

• These commands are used for Registers that cannot be

read

• Safety Manager has some registers that you write at one

address and read at another
– Reading from the write address generates a MODBUS
exception. These commands are used in this case

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 20 May 9, 2023
Request Block Configuration – Flag Array Honeywell

• Flag request blocks are PCDI blocks that read/write flag

values from/to a PCDI device

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 21 May 9, 2023
Request Block Configuration – Flag Array Honeywell

• Starting Element Index:

– Starting index of flags to read or write depending on
the Read/Write Option:
• 000001-065535: read from 1 to 1968 contiguous
flags or write single flag
• 100001-165535: read from 1 to 1968 contiguous
flags. This is read only addresses. Read/Write
Option setting is ignored

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 22 May 9, 2023
Request Block Configuration – Flag Array Honeywell

The number of Flag values to be

read. This number may not exceed
1968

The value to substitute when error

occurs. For the Modbus Flag Block
this is a check box. When checked
the substitution value will be True,
otherwise False.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 23 May 9, 2023
Request Block Configuration – Text Array Honeywell
• Text request blocks are Modbus blocks that read/write text values to and
from a Modbus device

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 24 May 9, 2023
Request Block Configuration – Text Array Honeywell
• Starting Element Index:
– Starting index of strings to read or write depending on the Read/Write Option:
• 500001-565535: read/write up to 120 Unicode characters or 240 ASCII
characters
• 600000: write diagnostic message
• 600001-665535: Read Vendor info from device, and write to
VENDORINFO Parameter
• 699999: Write input strings to VENDORINFO parameter. No device
access performed
• NOTE: If the 2B/OE device info command is enabled and supported,
VENDORINFO will be automatically queried and populated at block
execution startup. If the device does not support this command, the Text
block capability provides an alternative way to populate the
VENDORINFO parameter

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 25 May 9, 2023
Request Block Configuration – Text Array Honeywell

The number of String values to be

read. This number may not exceed
16

Number of characters per string. The

number of characters per string may
not exceed 120 or 240

Used to convert the text to ASCII

format

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Configuration Properties for Different Request Blocks 26 May 9, 2023
 Verify the Master Block Statistics

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Verify the Master Block Statistics 27 May 9, 2023
Communication Statistics Honeywell

• In this lesson we learn about Modbus communication

status
– Device statistics
– Connection statistics

• The communication statistics use is to check the

communication between the Modbus Device and the
C300 Controller

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Verify the Master Block Statistics 28 May 9, 2023
Device statistics Honeywell
• Open the PCDI Master properties window in Monitoring side and open
the Module statistics Tab to verify the following items:
Module Status should be OK state
when communication between C300
and end device is successful

Device status
shows
OPERATIONAL

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Verify the Master Block Statistics 29 May 9, 2023
Connection Statistics Honeywell
• Open the Connection Statistics tab to verify the following parameters.

Connection Status should show as

Connected. Successful connection
and connection attempts show some
successful numbers

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Verify the Master Block Statistics 30 May 9, 2023
 Describe the Master Block Statistics Related
Items

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 31 May 9, 2023
Overview Honeywell

• In this lesson, we learn about PCDI Master Block

Statistic related items:
– Module Statistics
– Connection Statistics
– Channel Status

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 32 May 9, 2023
Module Statistics Honeywell

Communication
Status

Device statistics

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 33 May 9, 2023
Module Statistics Honeywell
When checked, alarms conditions are Number of requests
propagated to the alarm displays and journals. sent and received from
When not checked, alarm conditions are not the device.
propagated to alarm displays. The default value
is checked or on.

Maximum Number of the Average of the data and

data (bytes) and messages sent and
messages sent and received per second
received per second

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 34 May 9, 2023
Module Statistics Honeywell
Displays the current
status for the individual Type of Device:
Device. The 1. Primary Vendor information
following states are 2. secondary provided by the device
available: 3. Unused manufacturer
1. INVALID 4. Serial
2. INITIAL
3. DIAG OK
4. OPERATIONAL Total number of request
5. FAIL sent.
6. IDLE

Device Address of the

PCDI device

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 35 May 9, 2023
Module Statistics – Device Status Honeywell

• INITIAL: Attempting initial diagnostic request

• FAILED: Diagnostic or Operational request failure. Diagnostics

will be issued periodically until successful or device is disabled

• DIAG OK: Diagnostic request was successful. Diagnostics will

be issued periodically until operational request is issued or device
is disabled

• IDLE: Safety Manager has been placed in the IDLE state.

Diagnostic Register request has been successful

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 36 May 9, 2023
Module Statistics Honeywell
Number of responses for which there
is no outstanding request. Usually
Number of request in because the request has timed out or
queue the bridge reported a MODBUS
exception and the request has been
Number of Request reissued.
timeout

Number of diagnostic
request sent

Number of request retry

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 37 May 9, 2023
Module Statistics Honeywell

If error is present in the Device

this flag will be ON Description of last error

Number of Errors
occurred Time and date of last
error

Number of Diagnostic
responses from end
device

Reset button to
reset the statistic
to zero

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 38 May 9, 2023
Connection Statistics Honeywell

Different connection statistic of primary

device like IP address, TCP port,
number of successful connections
established, number of connection
attempts made and last connection time

Information about Number of disconnects,

last disconnect time, error counts, last error
and last error time. Additional Error Info gives
the socket error code received

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 39 May 9, 2023
Channel Status Honeywell
Channel cycle time in
Milliseconds. Cycle
time is the elapsed
Current channel Number of requests time from the write
status sent from Request block request to the read
response
Request Block Control
Modules Assigned to Responses
Master Block received from Device

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 40 May 9, 2023
Channel Status Honeywell

Describe the last error

Error counts shows occurred in channel
number of errors in this
channel
Time of the last error
Error flag is set ON
when there is an error
in channel

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 41 May 9, 2023
 Honeywell

This page intentionally left blank

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe the Master Block Statistics Related Items 42 May 9, 2023
 Describe PCDI Device Related Alarms

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Device Related Alarms 43 May 9, 2023
System Status Display Alarm Pane Honeywell
• PCDI Master block alarms display in the System Status Display
• Select a PCDI alarm and click on Show Details pane to see the Alarm Details

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Device Related Alarms 44 May 9, 2023
Device Related Alarms Honeywell

PCDI Event Condition Priority Description Event Description

Subtype

Connection FAIL DIAG H Connection(s) For a single Modbus device, an alarm is

FAIL generated when a single PCDI
connection has failed
For a redundant pair of Modbus devices,
an alarm is generated when both
connections of a redundant pair of
Modbus devices have failed
Connection Warning DIAG H Connection For a redundant pair of Modbus devices,
Warning an alarm is generated when a single
connection has failed and the alternate
connection is in use.

Single Device FAIL DIAG H Single Device For a Single PCDI or a Single Safety
FAIL Manager, an alarm is generated when
the single connection is OK, but the
single device has failed.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Device Related Alarms 45 May 9, 2023
Device Related Alarms Honeywell

PCDI Event Condition Priority Description Event Description

Subtype
Primary Device FAIL DIAG H Primary Device FAIL For a Redundant PCDI or a Redundant
Safety Manager, an alarm is generated
when the primary connection is OK, but
the primary device has failed.
Secondary Device FAIL DIAG H Secondary Device For a Redundant PCDI or a Redundant
FAIL Safety Manager, an alarm is generated
when the secondary connection is OK,
but the secondary device has failed.

Primary Connection is DIAG H Secondary Offline For a redundant pair of Modbus

forced devices, an alarm is generated when
CONTOUSE is set to Primary.
Secondary connection DIAG H Primary Offline For a redundant pair of Modbus
is forced in use devices, an alarm is generated when
CONTOUSE is set to Secondary.

Primary and secondary DIAG H Both Connection For a redundant pair of Modbus
connections are forced Offline devices, an alarm is generated when
Offline CONTOUSE is set to NONE.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Device Related Alarms 46 May 9, 2023
Device Related Alarms Honeywell

PCDI Event Condition Priority Description Event Description

Subtype
Primary all UID FAIL DIAG H Primary all UID For a Single PCDI Bridge, an alarm is
FAIL generated when all serial devices on the
primary connection have failed.
For a Redundant PCDI Bridge, an alarm is
generated when all serial devices on primary
connection have failed, CONINUSE is switched
to Secondary, the alarm will not return to
normal until CONINUSE is switched back to
Primary again and alarm condition has been
cleared.
Secondary all UID DIAG H Secondary all For a Redundant PCDI Bridge, an alarm is
FAIL UID FAIL generated when all serial devices on secondary
connection have failed, CONINUSE is switched
to Primary, the alarm will not return to normal
until CONINUSE is switched back to
Secondary again and alarm condition has been
cleared.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Device Related Alarms 47 May 9, 2023
Device Related for Modbus Bridge Alarms Honeywell

PCDI Event Condition Priority Description Event Description

Subtype
Serial Device [0…15] DIAG H UID xxx FAIL For a Single PCDI Bridge or a Redundant PCDI
Bridge with up to 16 serial devices, an alarm is
generated when a serial device has failed.
(xxx is Modbus TCP Bridge serial device Unit
ID, range 1..247)
Serial device[0…15] DIAG H UID xxx Disable For a Single PCDI Bridge or a Redundant PCDI
Bridge with up to 16 serial devices, an alarm is
generated when a serial device has been
disabled.
(xxx is PCDI Bridge serial device Unit ID, range
1..247)

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Device Related Alarms 48 May 9, 2023
Modbus Device or Redundant Modbus Device Alarms Honeywell

PCDI Event Condition Priority Description Event Description

Subtype
Channel Fail [0…63] DIAG H Channel xxx FAIL For a single Modbus device or a redundant pair
of Modbus devices, an alarm is generated
when an assigned channel has failed.

(xx is assigned channel number, range 0..63).

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Device Related Alarms 49 May 9, 2023
 Honeywell

This page intentionally left blank

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Device Related Alarms 50 May 9, 2023
 Describe PCDI Master Block Detail Display in
Station

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 51 May 9, 2023
Overview Honeywell

• In this lesson we learn about:

– PCDI Master Block Detail Display
– Monitor PCDI Master Block in Experion System Status Display

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 52 May 9, 2023
Detail Display for Non-redundant PCDI Master Device Honeywell

Faceplate gives information

about PCDI Master Device,
CnX OK= Connection OK,
DV OK=Device OK

Status of the Connection

Execution State of
Modbus Master Device

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 53 May 9, 2023
Detail Display for Non-redundant PCDI Master Device Honeywell

Shows the Execution state of CEE

TCP connection detail: Device

type, Device IP address, Device
Port and connected device are
primary/secondary

Connection statistics for primary

and secondary device

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 54 May 9, 2023
Device Status Summary Tab Honeywell
• This page contains the device status summary of the configured PCDI Master device

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 55 May 9, 2023
Device Status Detail Tab Honeywell
• This page lists out additional information on the selected device.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 56 May 9, 2023
Channel Status Detail Display Page Honeywell
• Channel status page lists out the assigned function blocks (maximum of
64)
– The assigned FBs are shown as hyperlinks
– Selecting the hyperlink will navigate to the point detail display of the CM
containing the assigned FB

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 57 May 9, 2023
Config Details Display Tab Honeywell
• The Config Details tab display contains the Control Builder
Monitoring form

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 58 May 9, 2023
System Status Display Honeywell
• PCDI Master Device shows under Controllers in System Components tree
of System Status Display

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 59 May 9, 2023
System Status Display Honeywell
• Selecting PCDI Master Block in the system tree shows PCDI related
alarms on System Alarm summary pane

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 60 May 9, 2023
System Status Display Honeywell
• The System Status Tree shows the polled status of the PCDI Master Block
as an icon in the System Status tree

OK –The single and redundant connections are OK

All devices are OK
OK
MARGINAL– The device is initializing or there is at
least one device that is OK. No devices could have
MARGINAL failed. For a redundant connections, one connection
may have failed

FAILED – For a single connection, the connection

has failed. For a redundant connection, both
FAILED
connections have failed. A serial device has failed
on a non-redundant connection. For a redundant
connection with one connection that has failed, a
single failed serial device will cause this state.
Complete device failure will cause this state.

DISABLED – The device is Disable

DISABLED

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 61 May 9, 2023
System Status Display Honeywell
• Extended status for a Modbus Block displays within a faceplate as an optional
pane in the System Status Display by clicking show status pane button

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Master Block Detail Display in Station 62 May 9, 2023
 Describe PCDI Error Codes

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 63 May 9, 2023
Overview Honeywell

• In this lesson, you will see Error codes related to PCDI

blocks:

Peer Control Data Interface Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 64 May 9, 2023
PCDI Error Codes Honeywell
10679

ID ERR_CL_MBTCPMASTER_MAXALLOW

Description Maximum number of MBTCP Master Blocks per controller exceeded

Cause Added more than eight Master Blocks to a controller.

Work Around Add to a different controller.

10680

ID ERR_CL_MBTCPFLAG_INVALID_STARTINDEX

Description Invalid Start Index. Must be 1..65535 or 100001..165535

Cause The Start index entered is invalid.

Work Around Use index in the range of 1..65535 or 100001..165535.

10681

ID ERR_CL_MBTCPNUMERIC_INVALID_STARTINDEX
Description Invalid Start Index. Must be 200001..265535 or 300001..365535 or 400001..465535 or 700001..765535 or
800002..865535 or 900001..965535
Cause The Start index entered is invalid.

Work Around Use index in the range of 200001..265535 or 300001..365535 or 400001..465535 or 700001..765535 or
800002..865535 or 900001..965535.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 65 May 9, 2023
PCDI Error Codes Honeywell

10682

ID ERR_CL_MBTCPTEXT_INVALID_STARTINDEX

Description Invalid Start Index. Must be 500001..565535 or 600000..665535 or 699999

Cause The Start index entered is invalid.

Work Around Use index in the range of 500001..565535 or 600000..665535 or 699999.

10683

ID ERR_CL_MBTCPNUMERIC_INVALID_NNUMERIC

Description Invalid number of numeric. May not exceed 120.

Cause The number of numeric entered is invalid.

Work Around Use number that is not greater than 120.

10684

ID ERR_CL_MBTCPNUMERIC_INVALID_NNUMERIC_FLOAT

Description Invalid number of numeric. May not exceed 60.

Cause The number of numeric entered is invalid.

Work Around Use number that is not greater than 60.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 66 May 9, 2023
PCDI Error Codes Honeywell

10685

ID ERR_CL_MBTCPTEXT_INVALID_STRLEN_NSTRING

Description Invalid total number of characters. May not exceed 120 for non ASCII, or 240 for ASCII.

Cause The number of strings entered is invalid.

Work Around Enter a valid value into STRLEN.

10686

ID ERR_CL_MBTCPTEXT_INVALID_ASCII

Description When Convert to ASCII is checked, the string length must be even.

Cause Convert to ASCII must be even.

Work Around Make STRLEN even.

10687

ID ERR_CL_MBTCPMASTER_DUPLICATE_UNIT_ID

Description Duplicate unit id is not allowed.

Cause A duplicate unit id is entered.

Work Around Enter a unique unit id.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 67 May 9, 2023
PCDI Error Codes Honeywell

10688

ID ERR_CL_MBTCPMASTER_NO_COMMAND_SUPPORTED

Description Supported command may not be zero.

Cause Supported command may not be zero.

Work Around Configure at least one supported command.

10689

ID ERR_CL_MBTCPMASTER_INVALID_IP_TCP

Description Invalid IP address or port number.

Cause The IP address or port number is invalid or duplicated between the primary and secondary.

Work Around Enter a correct IP address or port number combo.

10690

ID ERR_CL_MBTCPMASTER_INVALID_UNIT_ID

Description Invalid Unit Id. Valid IDs are 1..247. A value of 0 can be used to un-assign a device.

Cause The unit id is invalid. Valid id range is 1..247.

Work Around Enter a correct unit id.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 68 May 9, 2023
PCDI Error Codes Honeywell

10691

ID ERR_CL_MBTCPREQUESTOR_INVALID_DEV_ADDRESS

Description Invalid Device Address. Valid addresses are 1..247 and 255

Cause The unit id is invalid. Valid id range is 1..247 and 255

Work Around

10692

ID ERR_CL_MBTCPMASTER_INVALID_NATIVE_UNIT_ID

Description Invalid Unit Id. Valid IDs are 1..247 and 255

Cause The native unit id is invalid. Valid id range is 1..247. In addition, 255 is also valid for native device.

Work Around Enter a valid unit id.

10693

ID ERR_CL_MBTCPMASTER_DUPLICATE_IP_TCP

Description Duplicate IP and PORTS

Cause Enter a correct secondary IP.

Work Around Enter a correct secondary IP.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 69 May 9, 2023
PCDI Error Codes Honeywell

10694

ID ERR_CL_MBTCPNUMERIC_INVALID_PVRANGE

Description Invalid PV Range. High limit should be greater than low limit.

Cause PV range is invalid

Work Around Enter a correct PV Range

10695

ID ERR_CL_MBTCPREQUESTOR_NOTASSIGNED

Description Request block not assigned to a master block.

Cause Request block not assigned to a master block.

Work Around Assign the request block to a master block.

• NOTE:- Error Codes will be available in the Knowledge Builder

documentation

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 70 May 9, 2023
Additional PCDI Error Codes Honeywell
– MBTCP_E_GENERIC = 256, // generic internal error - abnormal behavior, reload
controller
– MBTCP_E_NOT_INITIALIZED = 257, // request block connection to Master block
is invalid
– MBTCP_E_INVALID_PARAMETER = 258, // usually an illegal or unexpected
configuration value was specified
– MBTCP_E_NOT_SUPPORTED = 259, // PCDI command required is not enabled
– MBTCP_E_OUT_OF_RESOURCES = 260, // failed to allocate a buffer for issuing a
request - abnormal behavior, reload controller
– MBTCP_E_INVALID_UID = 261, // request block tried to access an unconfigured
UNIT ID
– MBTCP_E_SEND_FAILED = 264, // request send failure
– MBTCP_E_NOCONNECTION = 266, // no connection was available
– MBTCP_E_SOCKETERR = 267, // socket error occurred on the connection - see
Additional Error Info for socket error code
– MBTCP_E_INVALIDBUFINDEX = 268, // invalid buffer was addressed - abnormal
behavior, reload controller
– MBTCP_E_POINTER = 269, // abnormal behavior, reload controller
– MBTCP_E_TIMEDOUT = 270, // No response from device within timeout period.
Connection will be reset.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 71 May 9, 2023
Additional PCDI Error Codes Honeywell
– MBTCP_E_NOT_FOUND = 271, // internal error
– MBTCP_E_WAIT_FAILED = 272, // internal error
– MBTCP_E_DEVICEDISABLED = 273, // request could not be sent, device is
not enabled.
– MBTCP_E_INVALIDLEN = 274, // invalid message length received
– MBTCP_E_BADRESPONSE = 275, // receive message could not be validated
– MBTCP_E_BADXACTID = 276, // transaction id received not as expected
– MBTCP_E_UNEXPECTEDDIAGVALUE = 277, // the diagnostic test failed -
expected value was not received
– MBTCP_E_MASTERINACTIVE= 278, // request could not be sent,
associated master block is inactive
– MBTCP_E_DEVICEINIT= 279, // request could not be sent, associated device is
still in INITIAL state
– MBTCP_E_DEVICEFAIL= 280, // request could not be sent, associated device is
in FAILED state
– MBTCP_E_DEVICEIDLE = 281, // request could not be sent, Safety Manager is
in IDLE state

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 72 May 9, 2023
Additional PCDI error codes Honeywell
• The following codes are returned by the target device:
– MBTCP_E_ILLEGAL_FUNCTION = 512, // The function code received in the
query is not an allowable action for the server (or slave). This may be because the
function code is only applicable to newer devices, and was not implemented in the
unit selected. It could also indicate that the server (or slave) is in the wrong state to
process a request of this type, for example because it is unconfigured and is being
asked to return register values.
– MBTCP_E_ILLEGAL_ADDRESS = 513, // The address received in the query is
not an allowable address for the server (or slave). More specifically, the
combination of reference number and transfer length is invalid. For a controller
with 100 registers, a request with offset 96 and length 4 would succeed; a request
with offset 96 and length 5 will generate exception 02.
– MBTCP_E_ILLEGAL_DATA_VALUE = 514, // A value contained in the query
data field is not an allowable value for server (or slave). This indicates a fault in the
structure of the remainder of a complex request, such as that the implied length is
incorrect. It specifically does NOT mean that a data item submitted for storage in a
register has a value outside the expectation of the application program, since the
MODBUS protocol is unaware of the significance of any particular value of any
particular register.

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 73 May 9, 2023
Additional PCDI error codes Honeywell
– MBTCP_E_SLAVE_DEVICE_FAILURE = 515, // An unrecoverable error
occurred while the server (or slave) was attempting to perform the requested action.
– MBTCP_E_ACKNOWLEDGE = 516, // Specialized use in conjunction with
programming commands. The server (or slave) has accepted the request and is
processing it, but a long duration of time will be required to do so. This response is
returned to prevent a timeout error from occurring in the client (or master). The
client (or master) can next issue a Poll Program Complete message to determine if
processing is completed.
– MBTCP_E_SLAVE_DEVICE_BUSY = 517, // Specialized use in conjunction
with programming commands. The server (or slave) is engaged in processing a
long-duration program command. The client (or master) should retransmit the
message later when the server (or slave) is free.
– MBTCP_E_MEMORY_PARITY_ERROR = 518, // Specialized use in
conjunction with function codes 20 and 21 and reference type 6, to indicate that the
extended file area failed to pass a consistency check. The server (or slave) attempted
to read record file, but detected a parity error in the memory. The client (or master)
can retry the request, but service may be required on the server (or slave) device

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 74 May 9, 2023
Additional PCDI error codes Honeywell
– MBTCP_E_GATEWAY_PATH_UNAVAILABLE = 519, // Specialized use in
conjunction with gateways, indicates that the gateway was unable to allocate an
internal communication path from the input port to the output port for processing
the request. Usually means that the gateway is mis-configured or overloaded.
– MBTCP_E_GATEWAY_TARGET_DEVICE_FAILED_TO_RESPOND = 520
// Specialized use in conjunction with gateways, indicates that no response was
obtained from the target device. Usually means that the device is not present on the
network

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 75 May 9, 2023
Socket error codes Honeywell
• #define IP_ERRNO_EINPROGRESS 36 /* Operation now in progress */
• #define IP_ERRNO_EALREADY 37 /* Operation already in progress */
• #define IP_ERRNO_ENOTSOCK 38 /* Socket operation on non-socket */
• #define IP_ERRNO_EDESTADDRREQ 39 /* Destination address required */
• #define IP_ERRNO_EADDRINUSE 48 /* Address already in use */
• #define IP_ERRNO_EADDRNOTAVAIL 49 /* Can't assign requested address */
• #define IP_ERRNO_ENETDOWN 50 /* Network is down */
• #define IP_ERRNO_ENETUNREACH 51 /* Network is unreachable */
• #define IP_ERRNO_ENETRESET 52 /* Network dropped conn. on reset */
• #define IP_ERRNO_ECONNABORTED 53 /* Software caused connection abort */
• #define IP_ERRNO_ECONNRESET 54 /* Connection reset by peer */
• #define IP_ERRNO_ENOTCONN 57 /* Socket is not connected */
• #define IP_ERRNO_ESHUTDOWN 58 /* Can't send after socket shutdown */
• #define IP_ERRNO_ETIMEDOUT 60 /* Operation timed out */
• #define IP_ERRNO_ECONNREFUSED 61 /* Connection refused */
• #define IP_ERRNO_EHOSTDOWN 64 /* Host is down */
• #define IP_ERRNO_EHOSTUNREACH 65 /* No route to host */

Click forward button to resume

Peer Control Data Interface .
Honeywell Confidential and Proprietary Peer Control Data Interface
Describe PCDI Error Codes 76 May 9, 2023
The End
Honeywell

Please click HERE to record your attendance of Part 1 and

Part 2, to evaluate the training, and to offer any
comments.

This presentation is provided for study

by Honeywell Employees only. It may not
be used for customer presentations without
express authorization by Automation College.

Honeywell Confidential and Proprietary

77 May 9, 2023