Beruflich Dokumente
Kultur Dokumente
MasterLogic-Experion PKS
Integration
User's Guide
Release 300
6/08
Release 300
Honeywell Confidential & Proprietary
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customers.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The
information and specifications in this document are subject to change without notice.
Experion PKS is a registered trademark of Honeywell International Inc.
Other brand or product names are trademarks of their respective owners.
ii
R300
6/08
Intended Audience
The intended audience for this guide includes:
Project Engineers.
Operators.
Service Engineers.
For details about Experion PKS, see Experion Knowledge Builder >
Experion PKS R300 > Purpose > Overview > Introduction > Experion
Process Knowledge System.
For details about Quick Builder features and operations, see Experion
Knowledge Builder > Experion PKS R300> Configuration > Quick Builder
Guide.
R300
6/08
iii
See page
Introduction
15
Installation
23
ML Server License
43
Configuration
57
121
159
175
Troubleshooting
195
Appendix
212
References
The following list identifies references for material discussed in this publication:
iv
R300
6/08
R300
6/08
TM
Description
Experion Process Knowledge System.
ML Server
MLPLC
PLC
PV
QDB
SM
MLDP
RTC
Real Time Clock data represents the current time in the PLC.
SP
OP
Contacts
World Wide Web
The following Honeywell websites may be of interest to Industry Solution customers:
Honeywell Organization
Corporate
http://www.honeywell.com
Process Solutions
http://www.honeywell.com/ps
Telephone
Contact us by telephone at the following numbers listed:
vi
Location
Organization
Phone
United States
and Canada
1-800-822-7673
Europe
Honeywell TAC-EMEA
+32-2-728-2704
Pacific
1300-300-4822
(toll free within Australia)
+61-8-9362-9559
(outside Australia)
India
+91-20-2682-2458 / 1600-44-5152
Korea
+82-2-799-6317
Peoples
Republic of
China
Singapore
+65-6580-3500
Taiwan
+886-7-323-5900
Japan
+81-3-5440-1303
Elsewhere
R300
6/08
Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions:
Symbol
Definition
ATTENTION: Identifies information that requires special
consideration.
R300
6/08
vii
viii
R300
6/08
Contents
1.
INTRODUCTION ..........................................................................15
1.1
Overview ........................................................................................................ 15
2.
INSTALLATION ...........................................................................23
2.1
Overview ........................................................................................................ 23
2.2
2.3
Verifying Installation..................................................................................... 32
2.4
Getting started............................................................................................... 37
2.5
2.6
3.
Overview ........................................................................................................ 43
Background ..........................................................................................................................43
Before you begin ..................................................................................................................43
Obtaining the license............................................................................................................43
Using the demo versions of ML Server ................................................................................43
ML Server license features...................................................................................................44
Experion point and PLC point...............................................................................................44
3.2
3.3
R300
6/08
Contents
Updating license certificate ................................................................................................. 49
3.4
4.
CONFIGURATION....................................................................... 57
4.1
Overview .........................................................................................................57
4.2
4.3
4.4
4.5
4.6
5.
Overview .......................................................................................................121
5.2
5.3
R300
6/08
Contents
Status Info ..........................................................................................................................132
Driver Info...........................................................................................................................142
5.4
5.5
Overview ............................................................................................................................150
5.6
Overview ............................................................................................................................152
Viewing bad quality item in Point Detail display .................................................................153
6.
6.2
6.3
Raising SOE.......................................................................................................................170
Viewing SOE alarms in Experion Station ...........................................................................171
Configuring SOEs using Quick Builder...............................................................................174
7.
7.2
Overview ............................................................................................................................178
7.3
7.4
SOEs............................................................................................................. 181
7.5
Overview ............................................................................................................................183
Configuring PLC Status information in MLMonitor.xml.......................................................183
Configuring Base-Slot Information in MLMonitor.xml .........................................................184
Configuring IO Module Information in MLMonitor.xml ........................................................184
Configuring AD Module Information in MLMonitor.xml .......................................................185
Configuring Special Module information in MLMonitor.xml ................................................186
R300
6/08
11
Contents
Configuring All Module Information in MLMonitor.xml ....................................................... 187
Time Synchronization between PLC and EPKS ................................................................ 189
7.6
7.7
8.
TROUBLESHOOTING............................................................... 195
8.1
8.2
R300
6/08
Contents
6030 ...................................................................................................................................204
6031 ...................................................................................................................................204
6032 ...................................................................................................................................205
6033 ...................................................................................................................................205
6034 ...................................................................................................................................205
6035 ...................................................................................................................................205
6036 ...................................................................................................................................206
6037 ...................................................................................................................................206
6038 ...................................................................................................................................206
6039 ...................................................................................................................................206
6040 ...................................................................................................................................206
6041 ...................................................................................................................................207
6042 ...................................................................................................................................207
6043 ...................................................................................................................................207
6044 ...................................................................................................................................207
6045 ...................................................................................................................................207
6046 ...................................................................................................................................208
6047 ...................................................................................................................................208
6048 ...................................................................................................................................208
6049 ...................................................................................................................................208
6050 ...................................................................................................................................208
6051 ...................................................................................................................................209
6052 ...................................................................................................................................209
6053 ...................................................................................................................................209
6054 ...................................................................................................................................209
6055 ...................................................................................................................................209
6056 ...................................................................................................................................210
6057 ...................................................................................................................................210
6058 ...................................................................................................................................210
9.
APPENDIX .................................................................................212
9.1
ChannelStatus....................................................................................................................212
InputRange.........................................................................................................................212
OutputType ........................................................................................................................213
FilterProcess ......................................................................................................................214
FilterValue ..........................................................................................................................214
AverageSetting...................................................................................................................215
AverageProcessing ............................................................................................................215
AverageValue.....................................................................................................................215
9.2
ChannelRun .......................................................................................................................217
ChannelConnection............................................................................................................217
9.3
Overview ............................................................................................................................218
Configuring ML Server parameters in MLConfig XML........................................................218
Monitoring ML Server parameters in MLMonitor XML........................................................222
R300
6/08
13
Contents
Configuring ML Server Application Settings ...................................................................... 236
Configuring PLC SOEs in MLSOEConfig XML.................................................................. 247
14
R300
6/08
1. Introduction
1.1
Overview
R300
6/08
15
1. Introduction
1.1 Overview
The underlying principle is that when the master module fails, the standby module
takes over the control without interrupting the operation of the process in control.
FTE Network Two Ethernet cables are connected between the Experion and the
PLC or other devices. When the master network connection fails, the standby
network connection is used for the communication between the Experion and the
PLC.
Redundant Experion PKS server The secondary Experion server takes over
when the primary Experion server fails. All the MasterLogic Channels, Controllers,
Points and Graphics are also available when the secondary Experion server is active.
ATTENTION
The MasterLogic PLC functions as a non-FTE node together with other FTE
nodes on the network.
Integration Scope
Experion integration gains special access to intricate areas of MasterLogic PLC through
proprietary MLDP:
CPU, I/O module, communication Status and Alarms Flags (CPU error, battery
error, I/O module)
16
R300
6/08
1. Introduction
1.1 Overview
The following figure depicts the Address Monitoring window (available only in
SoftMaster):
R300
6/08
17
1. Introduction
1.1 Overview
Quick Builder
Quick Builder is the tool used for the following:
View the point values obtained from Experion through custom graphics.
Operates by looking at its inputs and depending on their state, turning on/off its
outputs.
Current MasterLogic PLCs available are ML100R, ML200 (IEC and NonIEC) and
ML200R.
R300
6/08
1. Introduction
1.1 Overview
MasterLogic Server
The PLCs are integrated to Experion server, through the ML Server software. After
downloading the Points to Experion server, ML Server performs the following:
R300
6/08
19
1. Introduction
1.1 Overview
The following picture illustrates the software architecture of the MasterLogic PLCExperion integration solution:
20
ML200R
ML100R
R300
6/08
1. Introduction
1.1 Overview
ML200R
Honeywells next generation Programmable Logic Controllers which supports CPU level
redundancy. This provides real power, performance and versatility with compact size,
high speed scanning of I/O Channels and execution of program instructions, open
network through Ethernet, Profibus TM-DP, DeviceNet TM, remote I/O and engineerfriendly programming & diagnostic software tools.
ML200
Honeywells next generation Programmable Logic Controllers providing real power,
performance and versatility with compact size, high speed scanning of I/O Channels and
execution of program instructions, open network through Ethernet, Profibus TM-DP,
DeviceNet TM, remote I/O and engineer-friendly programming & diagnostic software
tools.
ML100R
ML100R is an earlier version of ML200 which supports CPU level redundancy. There
are some significant improvements in terms of speed, size, performance in ML200
compared to ML100R.
R300
6/08
21
1. Introduction
1.1 Overview
22
R300
6/08
2. Installation
2.1
Overview
This section describes the procedure for installing the ML Server.
Ensure that you have installed Experion server with OPC client license. (The ML
Server information provided in this guide is compatible with Experion R301.1.)
Ensure that you have logged into the Experion server machine with Administrative
privileges.
REFERENCE - EXTERNAL
For more details on Hardware and Software requirements, refer to Hardware
and Software requirements section in Experion PKS Knowledge Builder.
ATTENTION
You must have Experion OPC client license (Model#: EP-OPCCLI) to
configure MasterLogic Channel, Controller and Point.
Package Information
The ML Server CD contains the setup.exe file required to install ML Server.
R300
6/08
23
2. Installation
2.2 Installing ML Server
2.2
Installing ML Server
To install ML Server, perform the following steps:
Step
1
Action
Click setup.exe file from the ML Server installation CD.
ATTENTION
If an earlier version of ML Server is installed already, the wizard
displays an error message indicating that the previous ML Server
version must be installed before installing the new version.
The wizard displays the following screen:
24
R300
6/08
2. Installation
2.2 Installing ML Server
Step
Action
After performing the initial checks, the wizard displays the following screen:
Click Next.
The wizard displays the License Agreement screen.
R300
6/08
25
2. Installation
2.2 Installing ML Server
Step
Action
The License Agreement screen is displayed.
26
Click Next.
R300
6/08
2. Installation
2.2 Installing ML Server
Step
Action
The wizard displays the Destination Folder screen.
TIP
Honeywell recommends retaining the default destination folder for
installing ML Server.
6
R300
6/08
Click Next.
27
2. Installation
2.2 Installing ML Server
Step
Action
The wizard displays the Ready to Install the Program screen.
28
Click Install.
R300
6/08
2. Installation
2.2 Installing ML Server
Step
Action
The wizard displays the Installing Honeywell MasterLogic Server screen,
displaying the status messages and the progress bar during the installation
process.
R300
6/08
29
2. Installation
2.2 Installing ML Server
Step
Action
The wizard completes the installation and displays the following screen:
ATTENTION
If Experion server is not installed on the machine where the ML
Server is being installed, the following message is displayed after
step 2:
Click OK.
30
R300
6/08
2. Installation
2.2 Installing ML Server
Step
Action
The wizard displays the following message:
Click Finish. Install Experion server with OPC client license and
perform step 1.
R300
6/08
31
2. Installation
2.3 Verifying Installation
2.3
Verifying Installation
Verify graphics pages and xml files copied to the installation path (typically
C:\Program Files\Honeywell\Experion PKS\Client\Abstract) during installation,
as shown in the following figure:
Figure 2.3-1: Graphics pages and xml files copied during installation
32
R300
6/08
2. Installation
2.3 Verifying Installation
The following table lists the graphics pages and xml files copied during installation:
Type
Filename
xml files
Graphics pages
Schema files
R300
6/08
Description
MLConfig.xml
MLMonitor.xml
MLSOEConfig.xml
MLPLC_Config.htm
MLPLC_Status.htm
MLPLC_Driver.htm
MLConfig.xsd
MLMonitor.xsd
MLSOEConfig.xsd
Verify xml, exe, dll files and document copied to the installation path (typically
C:\Program Files\Honeywell\MasterLogicServer) during installation, as shown in
the following figure:
33
2. Installation
2.3 Verifying Installation
34
Filename
Description
xml file
MLAppSettings.xml
Schema files
MLAppSettings.xsd
Document
MLServer_Users_Guide.pdf
Template
StatusPointBuildTemplate.t
xt
Configuration
Tool
MLServerConfigTool.exe
R300
6/08
2. Installation
2.3 Verifying Installation
Type
Filename
Description
Point Build
Utility
PointBuildUtility.exe
License
Application
MLServerLicenseRegistrati
on.exe
Demo
certificate
MLPLC_Demo.cert
QDB file
ML_Sample.qdb
The ML Server configuration tool, point build utility, users guide and the license
application is accessed through Start > Programs > Honeywell MasterLogic Server.
The shortcuts for the configuration tool and the point build utility are available in the
desktop.
R300
6/08
35
2. Installation
2.3 Verifying Installation
36
R300
6/08
2. Installation
2.4 Getting started
2.4
Getting started
R300
6/08
Action
To view PLC information in the graphics display, build Point for each PLC
Using PointBuild Utility.
37
2. Installation
2.5 Removing ML Server
2.5
Removing ML Server
After removing the ML Server, the integration between the PLC and the
Experion does not work.
Action
38
R300
6/08
2. Installation
2.5 Removing ML Server
Step
3
Action
Select Honeywell MasterLogic Server and click Remove.
The following screen appears:
Click YES.
The wizard displays the Remove the Program screen.
Click OK.
The wizard displays the Uninstalling Honeywell MasterLogic Server
screen, displaying the status messages and the progress bar while the
remove operation is in progress.
R300
6/08
39
2. Installation
2.5 Removing ML Server
To remove ML Server using the setup.exe file in the installation CD, perform the
following steps:
Step
1
Action
Click setup.exe file in the installation CD.
The Program Maintenance screen appears.
40
R300
6/08
2. Installation
2.6 Repairing ML Server
2.6
Repairing ML Server
Action
Click setup.exe file in the installation CD.
The Program Maintenance screen appears.
R300
6/08
41
2. Installation
2.6 Repairing ML Server
42
R300
6/08
3. ML Server License
3.1
Overview
Background
After installing the ML Server, you must register it and obtain the license before using it.
Before you begin
Before obtaining the license, ensure that you have the following items:
Host ID Files These files are automatically created when you open the ML Server
License Registration Application or enable the ML Channel for the first time. Names
of the Host ID files are <Computer Name>.Zip and <Computer Name>.HID,
example: If the computer name is EPKSSRVRPC1 then the Host ID files created are
EPKSSRVRPC1.zip and EPKSSRVRPC1.HID. These files are available in the
installation path (typically C:\Program files\Honeywell\MasterLogicServer).
Separate email needs to be sent for getting license for each Experion
server attaching the Host ID files of the corresponding computer.
For a redundant Experion server two licenses must be obtained, one for
each server machine.
R300
6/08
43
3. ML Server License
3.1 Overview
Number of PLCs
Number of PLC points that can be used across all the PLCs
For example if the obtained license supports 10 PLCs and 1000 PLC points,
A maximum of 1000 PLC points can be used for data communication across all the
PLCs
44
R300
6/08
3. ML Server License
3.2 Obtaining a new license
3.2
Action
Name>.HID files.
ATTENTION
Other than the Subject line, do not type any information in the
e-mail.
After receiving the e-mail, Honeywell sends the new license certificate in a
zip file. This file must be unzipped using the password password.
R300
6/08
45
3. ML Server License
3.2 Obtaining a new license
Step
4
Action
Save the license certificate in the ML Server system. This license certificate
can be re-installed if the Experion server machine is reformatted.
Action
Click Start > Programs > Honeywell MasterLogic Server > License
Registration.
The ML Server License Registration dialog box appears.
46
R300
6/08
3. ML Server License
3.2 Obtaining a new license
Step
Action
R300
6/08
47
3. ML Server License
3.2 Obtaining a new license
Step
3
Action
Click OK.
The ML Server License dialog box appears displaying the licensed
ATTENTION
The license need not be terminated before uninstalling ML Server
software. The license is retained and active when the ML Server
software is re-installed in the same machine.
48
R300
6/08
3. ML Server License
3.3 Updating license certificate
3.3
Action
Name>.HID files.
ATTENTION
Other than the Subject line, do not type any information in the
e-mail.
After receiving the e-mail, Honeywell sends the new superseded license
certificate in a zip file. This file must be unzipped using the password
password.
R300
6/08
Save the license certificate in the ML Server system. This license certificate
can be re-installed if the Experion server machine is reformatted.
Click Start > Programs > Honeywell MasterLogic Server > License
Registration.
49
3. ML Server License
3.3 Updating license certificate
Step
Action
The ML Server License dialog box appears.
ATTENTION
If the ML Server version is R2xx, use mlplcr200 as password.
The following message box appears.
50
R300
6/08
3. ML Server License
3.3 Updating license certificate
Step
7
Action
Click Yes to continue.
The Re-license ML Server dialog box appears.
R300
6/08
51
3. ML Server License
3.3 Updating license certificate
Step
Action
The selected certificate appears in New certificate file path as shown in
10
Click OK.
The following message box appears.
11
52
Click OK.
R300
6/08
3. ML Server License
3.3 Updating license certificate
Step
Action
The ML Server License Registration dialog box appears displaying the
12
R300
6/08
53
3. ML Server License
3.4 Transferring license certificate
3.4
Action
Click Start > Programs > Honeywell MasterLogic Server > License
Registration.
The ML Server License dialog box appears.
54
R300
6/08
3. ML Server License
3.4 Transferring license certificate
Step
Action
The Enter Password dialog box appears.
ATTENTION
If the ML Server version is R2xx, use mlplcr200 as password.
The following message box appears.
ATTENTION
The *.term file generated after terminating the license can be used
for transferring the license to a different machine.
R300
6/08
55
3. ML Server License
3.4 Transferring license certificate
Action
files and create a zip file with password password. Attach this zip file to
the e-mail.
Note: Ensure not to select the option to save the folder information while
zipping the files.
ATTENTION
Other than the Subject line, do not type any information in the email.
After receiving the e-mail Honeywell sends the new license certificate in a
zip file. This file must be unzipped using the password password.
4
Save the license certificate in the ML Server system. This license certificate
can be re-installed if the Experion server machine is reformatted.
REFERENCE INTERNAL
For more details about installing the new license certificate, see
Installing license certificate.
56
R300
6/08
4. Configuration
4.1
Overview
b)
c)
R300
6/08
57
4. Configuration
4.2 Configuring ML Server using Configuration Tool
4.2
PLC
LOGS
SOE
ADVANCED
ATTENTION
The PLC information configured using the configuration tool must be saved.
The ML Server must be restarted for the changes to take effect. However, the
exception is that when the ML Server or Protocol Log file settings are
changed, there is no need to restart the ML Server.
Action
Click Start > Programs > Honeywell MasterLogic Server > Configuration
Tool.
The following window appears:
58
R300
6/08
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Step
Action
R300
6/08
59
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Step
7
Action
Repeat steps 1 through 6 for each PLC in the plant.
Note: The PLCs must be added using the procedure Adding a new PLC.
Tip
The ToolTip appears when the cursor is placed over the options
available in the ML Server Configuration tool.The ToolTip provides
additional information about the setting options.
Action
Select the PLC ID from the left pane.
The PLC information appears in the PLC tab as shown in the following
figure:
60
R300
6/08
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Step
3
Action
Enter PLC Name.
Note: The PLC Name is a unique name for each PLC. It is alphanumeric and
there is no limit on the number of characters. Example MLPLC1. Separate
logs are created for each PLC based on the PLC ID.
Select the PLC type from the PLC Type list box
Note: The supported PLCs are ML100R, ML200-IEC, ML200-NonIEC and
ML200R.
Enter the EPKS Asset Name for this PLC. All the Alarms/Events raised by
the ML Server is in this asset.
REFERENCE EXTERNAL
For more details on configuring and creating asset, refer Expperion
Knowledge Builder > Experion R300 > Configuration > Enterprise
Model Builder Users Guide > Accessing Enterprise Model Builder
> Creating and Configuring Assets.
6
R300
6/08
10
To view the updated RTC time in Experion graphics display select Enable
Read/Write in RTC and EPKS Write under Monitor.
MasterLogic-Experion PKS Integration - User's Guide
Honeywell Confidential & Proprietary
61
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Step
Action
Enable Read/Write
Synch Interval
Deadband
11
62
R300
6/08
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Configuring settings for transfer of the PLC Logs into the ML Server
Action
12
Select the PLC ID from the left pane and click LOGS tab.
13
Select the Initial History check box if the already existing events in the PLC
Log need to be transferred to Experion server or Log files during startup of
the ML Server.
Note: Honeywell recommends that this option need not be selected.
14
Select the Log To File check box if the events in the PLC Log need to be
transferred to corresponding ML Server log files.
Note: Honeywell recommends that this option need not be selected.
R300
6/08
63
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Step
Action
15
Select the Events check box if the events in PLC Log need to be transferred
to Experion server as Events/Alarms.
Note: Honeywell recommends that this option can be selected for the desired
PLC log.
16
17
Click
under ML Server Logs to browse and select the folder path to
save the ML Server log files.
18
under Protocol Logs to browse and select the folder path to save
Click
the Protocol log files.
64
19
20
R300
6/08
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Action
Select the PLC ID from the left pane and click SOE tab.
The PLC SOE information appears as shown in the following figure:
22
Click Add.
A new row is added as shown in the following figure:
R300
6/08
65
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Step
Action
23
Enter the PLC memory area address for which the SOE needs to be raised in
the Memory address column.
Enter the SOE Option which indicates the condition for raising the SOE. The
possible values are:
1 SOE is raised when value of the memory address changes from 0 to 1
0 SOE is raised when value of the memory address changes from 1 to 0
C SOE is raised when value of the memory address changes either from 0
to 1
F SOE is not raised for any value changes
Enter the Description to be used as the SOE message text.
In the example provided, the SOE would be raised with the message text
Boiler Unit turned ON when the value of M0010F memory location bit
becomes 1.
Note: The data type value cannot be modified.
66
24
25
R300
6/08
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Step
Action
ATTENTION
The Delete option is available after saving the SOE information.
26
R300
6/08
67
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Action
Select the PLC ID from the left pane and click ADVANCED tab.
The ML Server advanced information appears as shown in the following
figure:
68
R300
6/08
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Action
Click Start > Programs > Honeywell MasterLogic Server > Configuration
Tool.
R300
6/08
69
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Step
Action
ATTENTION
For each PLC added, a corresponding point must be built using the
Point build utility, for viewing the PLC status in Experion graphics
displays.
70
R300
6/08
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Deleting a PLC
To delete a PLC, perform the following steps:
Step
Action
Click Start > Programs > Honeywell MasterLogic Server > Configuration
Tool.
Right click the PLC ID from the left pane and select DeletePLC.
R300
6/08
71
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Action
Click Start > Programs > Honeywell MasterLogic Server > Configuration
Tool.
Enter the EPKS Asset Name for the general ML Server Alarms. All Alarms
raised by the ML Server is in this asset.
Enter the Log Retention Days for the ML Server and Protocol Logs. The ML
Server automatically deletes the log files that are older than these days.
Enter the PLC Info Update Rate which indicates how fast the changes in the
dynamic MLConfig XML parameters (Log files enabling / disabling, and so
on) are detected.
6
Click
under ML Server Logs to browse and select the folder path to
save the ML Server log files.
7
72
R300
6/08
4. Configuration
4.2 Configuring ML Server using Configuration Tool
Step
Action
8
under Protocol Logs to browse and select the folder path to save
Click
the Protocol Stack log files.
9
10
Enter the scan period for General Diagnostic, PLC Diagnostic, IO Read,
AD Module Read, Special Module Read and All Module Read under Scan
Period.
General Diagnostics Frequency at which the general diagnostics
parameters in the Driver Info Experion display are collected.
PLC Diagnostics Frequency at which the PLC specific diagnostics
parameters in the Driver Info Experion display are collected.
IO Read Frequency at which the IO Module information is read from all the
PLCs. This setting is not applicable for the ML100R PLCs.
AD Module Read Frequency at which the AD Module information is read
from the PLCs. This setting is not applicable for the ML100R PLCs.
Special Module Read Frequency at which the Special Module parameters
are read from the U memory area of the PLCs. The Bad PV is set for the
corresponding Experion parameters based on this parameter. This setting is
not applicable for the ML100R PLCs.
All Module Read Frequency at which the module level errors,
Max/Min/Current Scan periods are read from the F Area for the ML200 PLCs.
This setting is not applicable for the ML100R PLCs.
11
R300
6/08
73
4. Configuration
4.3 Configuring ML Server using Quick Builder
4.3
The ML Server must be configured using the Quick Builder. The configuration
involves the following tasks:
Configuring the Quick Builder component manager
TIP
For example on configuring ML Channel, Controller and Points, refer to the
sample QDB file (ML_Sample.qdb) in the installation folder.
To configure the Quick Builder component manager, perform the following steps:
Step
1
Action
Create a new project in Quick Builder.
The Enable Components dialog box is displayed.
74
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
R300
6/08
Action
Click OK.
75
4. Configuration
4.3 Configuring ML Server using Quick Builder
Action
Right-click the Channel icon from the right-pane of the Quick Builder window
and select Add Item.
76
Select Channel and MasterLogic Channel type in the Add Item(s) dialog
box.
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
Select Channels icon from the left-pane of the Quick Builder window. From
the right pane, select the channel that you want to configure.
ATTENTION
Ensure that the Item Number for the channel configured is unique.
R300
6/08
77
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
WARNING
REFERENCE EXTERNAL
For more details on adding and configuring a Channel, see Experion
Knowledge Builder > Experion PKS R300 > Configuration > Quick
Builder Guide > Configuring Controllers and Channels.
Action
REFERENCE INTERNAL
For more details on adding a MasterLogic Channel, see Configuring
a MasterLogic Channel.
78
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
3
Action
Right-click the Controller icon from the right-pane of the Quick Builder
window and select Add Item.
R300
6/08
Select the Controllers icon from the left-pane of the Quick Builder window.
From the right pane, select the controller that you want to configure.
79
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
REFERENCE - EXTERNAL
For more details on adding and configuring a Controller, see
Experion Knowledge Builder > Experion PKS R300 > Configuration
> Quick Builder Guide > Configuring Controllers and Channels.
80
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Action
Add a MasterLogic Channel and one (or more) MasterLogic Controller (s)
corresponding to each PLC configured in the Plant.
REFERENCE INTERNAL
For more details on adding MasterLogic Channel and Controller,
see Configuring a MasterLogic Channel and Configuring a
MasterLogic Controller.
R300
6/08
81
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
3
Action
Right-click the Point icon from the right-pane of the Quick Builder window
and select Add Item.
82
Select Point and Analog Point type in the Add Item(s) dialog box.
Select the Points icon from the left-pane of the Quick Builder window. From
the right pane, select the point that you want to configure.
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
Enter the Parent Asset for the point. All Alarms/Events raised by Experion
(value change Events, Range checking Alarms, and so on.) is in this Asset.
TIP
Honeywell recommends that the Parent Asset configured for the
points here must be the same as the EPKS Asset Name configured
in the ML Server Configuration Tool for the PLC referred in this
point.
8
Select ellipse
R300
6/08
83
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
REFERENCE INTERNAL
WARNING
If the user defined data format is not defined in Experion, then the
entire item is not recognized by the ML Server.
10
11
reads the associated parameter value that can be viewed in the Experion
Station.
Setpoint Dest Address: The value written to SP is transferred to this
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
TIP
Honeywell recommends you to configure the same PLC memory
address for both the source and destination addresses of the SP
parameter.
12
WARNING
The Scan Period,
13
the associated parameter value that can be viewed in the Experion Station.
Output Dest Address: The value written to OP is transferred to this
TIP
Honeywell recommends you to configure the same PLC memory
address for both the source and destination addresses of the OP
parameter.
14
WARNING
The Scan Period,
R300
6/08
85
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
TIP
The values for SetPoint and Output need not be defined for every
Experion point.
REFERENCE EXTERNAL
For more details on adding and configuring Points, see Experion
Knowledge Builder > Experion PKS R300 > Configuration > Quick
Builder Guide > Point Properties.
Action
REFERENCE INTERNAL
For more details on configuring a MasterLogic Channel and
Controller, see Configuring a MasterLogic Channel and Configuring
a MasterLogic Controller.
86
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
3
Action
Right-click the Point icon from the right-pane of the Quick Builder window
and select Add Item.
R300
6/08
Select Point and Status Point type in the Add Item(s) dialog box.
Select the Points icon from the left-pane of the Quick Builder window. From
the right pane, select the point that you want to configure.
87
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
Enter the Parent Asset for the point. All Alarms/Events raised by Experion is
in this Asset.
TIP
Honeywell recommends that the Parent Asset configured here
must be the same as the EPKS Asset Name configured in the ML
Server Configuration Tool for the PLC referred in this point.
8
Select ellipse
88
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
REFERENCE - INTERNAL
10
11
the associated parameter value that can be viewed in the Experion Station.
Output Dest Address: The value written to OP is transferred to this
WARNING
The Scan Period,
R300
6/08
89
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
TIP
The value for Output need not be defined for every Experion point.
REFERENCE EXTERNAL
For more details on adding and configuring Points, see Experion
Knowledge Builder > Experion PKS R300 > Configuration > Quick
Builder Guide > Point Properties.
The following are the list of PLC Point name formats supported in ML200 R, ML200
and ML100R:
Table 4.3-1: PLC Point name formats supported in ML200R, ML200-IEC,
ML200-NonIEC and ML100R
PLC Point Name Format
90
ML200R
ML200-IEC
ML200-NonIEC
ML100R
Direct Variable
Named Variable
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
PLC Point Name Format
ML200R
ML200-IEC
ML200-NonIEC
ML100R
Device Variable
The following table lists the different memory areas supported in ML200R and its
associated data type, range and read/write property:
BYTE
WORD
DWORD
LWORD
INT
DINT
LI NT
Range
BIT
Memory
Area
Readable/
Writable
Low
00.00.00
127.15.63
00.00.00
127.15.63
R/W
00000
8192F
R/W
00000
11263F
R/W
00000
2047F
00000
32767
R/W
00.00.00
0
31.15.511
R/W
00000
65535
R/W
High
Note: The R and W memory areas refer to the same storage locations for the first 32767
words. For example, %RW10 and %WW10 is referring to the same PLC memory
address and therefore always have the same value.
The following table lists the different memory areas supported in ML200-IEC and its
associated data type, range and read/write property:
R300
6/08
BYTE
WORD
DWORD
LWORD
INT
DINT
LI NT
Range
BIT
Memory
Area
Readable/
Writable
Low
00.00.00
127.15.63
00.00.00
127.15.63
R/W
High
91
4. Configuration
4.3 Configuring ML Server using Quick Builder
Range
M
00000
8192F
R/W
00000
11263F
R/W
00000
2047F
00000
32767
R/W
00.00.0
3F.31.F
R/W
00000
65535
R/W
Note: The R and W memory areas refer to the same storage locations for the first 32767
words. For example, %RW10 and %WW10 is referring to the same PLC memory
address and therefore always have the same value.
The following table lists the different memory areas supported in ML200-NonIEC and its
associated data type, range and read/write property:
92
DWORD
LWORD
INT
DINT
LI NT
00000
2047F
R/W
00000
2047F
R/W
00000
11263F
R/W
00000
2047F
R/W
00000
2047F
0000
2047
R/W
0000
2047
R/W
000.00
127.99
R/W
00000
32767
R/W
00000
32767
R/W
00.00.0
7F.31.F
R/W
00000
21503
R/W
BIT
WORD
Range
BYTE
Memory
Area
Readable/
Writable
Low
High
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Range
Z
000
127
R/W
00000
32767
R/W
The following table lists the different memory areas supported in ML100R and its
associated data type, range and read/write property:
DWORD
LWORD
I NT
DINT
LINT
I (Input
Memory)
00.00.00
15.07.63
Q (Output
Memory)
00.00.00
15.07.63
R/W
M (Internal
Memory)
00000
2047F*
R/W
BIT
WORD
Range
BYTE
Memory
Area
Readable/
Writable
Low
High
Note: The INT (9) data type is supported only for Named Variable.
* The higher range for M memory area must be same as configured in the Softmaster tool.
R300
6/08
93
4. Configuration
4.3 Configuring ML Server using Quick Builder
94
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Read
Write
Remarks
Advantages:
R300
6/08
95
4. Configuration
4.3 Configuring ML Server using Quick Builder
Commands
TB
(ML200/ML2
00R)
Read
Write
Remarks
Advantages:
96
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Commands
Read
Write
Remarks
COS
(ML200/ML2
00R)
Advantages:
R300
6/08
97
4. Configuration
4.3 Configuring ML Server using Quick Builder
Commands
DEV
(ML200/ML2
00R)
Read
Write
Remarks
Advantages:
SEP
(ML100R,
ML200/ML20
0R)
98
Separate Read
Separate Write
Advantages:
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Note:
A single Continuous Read/Write command is used for reading or writing data together for multiple addresses within the same
memory area.
In ML100R, the maximum number of bytes read /written is 1024.
In ML200/ML200R, the maximum number of bytes read/written is 1400.
For the Separate Read/Write command, even when the Device Variable format is used, the offset must be provided in the Direct
Variable format. For instance, ML01.%MX10A$SEP is not a valid item, ML01.%MX170 must be used. Configuring
ML01.%MX10A$SEP would generate an error log message.
The examples given in the previous table refer to ML200. For ML100R examples, see Table 4.3-7: Examples of Direct Variable.
ATTENTION
R300
6/08
The Separate Read/Write and Continuous Read/Write command are the only commands supported in ML100R.
If an incorrect command is specified in the PLC Point name, an error message is logged and the default command is
automatically used. For instance, if a ML200 PLC Point name is configured as ML01.%MW90$CEP, then it would be
internally converted to ML01.%MW90$DEV.
99
4. Configuration
4.3 Configuring ML Server using Quick Builder
TIP
Honeywell recommends to use the commands in the following order:
a) CON: First try to use the CON (Continuous Read/Write) command. This is particularly useful when there are a lot of
contiguous memory addresses that need to be read from / written to one or two PLC memory areas.
b) COS (Only for ML200/ML200R): This command can be used as it reduces the network traffic. This command can be
used for a maximum of 1024 points (512 points in ML200-NonIEC) per PLC. This is useful when data from different
memory areas needs to be read and the values do not change frequently. This command could be mainly used for
Status points
c) TB (Only for ML200/ML200R): This command must be used because it reduces Network traffic. However, this
command can be used for a maximum of 1024 points (512 points in ML200-NonIEC) per PLC. This is useful when data
from different memory areas needs to be read and the values change frequently. Therefore this command is
preferred for Analog points.
d) DEV (Only for ML200/ML200R): This command must be used when data from different memory areas needs to be
read and the TB/COS points limit have been exceeded.
e) There is no limit on the number of points that can be configured.
f) SEP: Honeywell discourages the use of this command for performance reasons. However, this command is the only
method available for reading named variables in ML100R.
100
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Direct Variable
The following figure depicts the Direct Variable format:
PLCID: This refers to the PLC. It is a two digit number ranging from 01 through 99
and always prefixed by ML. This must be configured in ML Server Configuration
Tool.
MemoryAddress: This refers to the address within the PLC memory area where
information is stored.
Format: %<MemoryArea><DataType><Offset>
In ML200-NonIEC, for all the memory areas, <Offset> represents the address
within the memory area.
REFERENCE - INTERNAL
For more details on memory areas supported in ML200R, see Table 4.3-2.
For more details on memory areas supported in ML200-IEC, see Table 4.3-3.
For more details on memory areas supported in ML200-NonIEC, see Table
4.3-4.
For more details on memory areas supported in ML100R, see Table 4.3-5.
101
Command Type: This refers to the different commands used for reading/writing
data from/to PLC by ML Server. For more details on command types, see Table
4.3-6.
MasterLogic-Experion PKS Integration - User's Guide
Honeywell Confidential & Proprietary
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
BIT
BYTE
The request is sent to PLC with the data types configured in the memory
address part (that is X, B, W, D and L) of the PLC point name. After receiving
the responses, the ML Server converts it to the data type configured after #.
If no data type is configured in the PLC point name (that is no # part), by
default the corresponding basic data type is used by the ML Server. For
example, if the PLC point is configured as ML01.%MW90$COS, then it would
be assumed as ML01.%MW90$COS#WORD.
st
rd
rd
102
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Direct Variable
Note: In the following examples, ML01 is a ML200-IEC PLC, ML02 is a ML200NonIEC PLC and ML03 is a ML100R PLC. The bit / word positions are 0-based.
th
st
nd
160th and 161st words) in R memory area of PLC ML01. The default
Device Area Read/Write command is used for communication with
the PLC. The data is converted by ML Server and available as a
decimal (or REAL) value on the Experion side.
th
st
nd
th
memory area in PLC ML02. The Timer Based command is used for
getting values from PLC and the Device Area Write command is
used for writing values into PLC.
th
th
st
th
th
139 word of P memory area in PLC ML02. The default Device Area
Read/Write command is used for communication with PLC.
st
th
st
R300
6/08
103
4. Configuration
4.3 Configuring ML Server using Quick Builder
Named Variable
The following figure depicts the Named Variable format:
The data type configured in the PLC Point name must match with the
data type configured for the variable in Softmaster. If the data type does
not match, the PLC returns an error. For instance, in the previous
example, if VAR23 is not defined as a BOOLEAN variable in Softmaster,
an error is returned by PLC.
The following table lists the format and examples of Named Variables supported in
ML100R:
Table 4.3-8: Named Variable supported in ML100R
Named Variable
Note: In the following examples, ML03 is a ML100R PLC. The bit / word positions are
0-based.
Examples
ML03.
104
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Device Variable
The following figure depicts the Device Variable format:
PLCID: This refers to the PLC. It is a two digit number ranging from 01 through 99
and always prefixed by ML. This must be configured in ML Server Configuration
Tool.
MemoryAddress: This refers to the address within a memory area where PLC
information is stored.
Note: <Offset> represents the word offset address of the memory location in
PLC.
CommandType: This refers to the command that must be used for reading/writing
data from/to PLC by ML Server. For more detail on command types, see Table 4.3-6
DataType: This refers to the PLC data type. The default data type is WORD. For
more details about available data types for ML100R and ML200, see Table 4.3-4.
The following table lists the format and examples of Device Variable supported in
ML200:
Table 4.3-9: Example of Device Variable format in ML200
Device Variable
Note: In the following examples, ML01 is a ML200-IEC PLC and ML02 is a ML200NonIEC PLC.
R300
6/08
105
4. Configuration
4.3 Configuring ML Server using Quick Builder
Device Variable
Examples
ML200-IEC Examples:
th
th
th
th
rd
st
Note: In the previous COS examples, to read this information from the
PLC, the Change of State command is used, but for writing information
into the PLC, the Device Area Write command is used.
nd
Word in C memory
th
106
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Device Variable
ML02.F94$TB#DINT This denotes the Double Integer formed
th
PLC ML02.
th
rd
th
th
ATTENTION
It is important to note that the offset configured for the SEP
command is used in the same way as the offset configured
for the Direct Variable format. That is the offset does not
indicate the word position, but it indicates the offset with
respect to the data type itself.
R300
6/08
107
4. Configuration
4.3 Configuring ML Server using Quick Builder
108
Action
R300
6/08
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
R300
6/08
Action
109
4. Configuration
4.3 Configuring ML Server using Quick Builder
Step
Action
Select data type from Data Type drop-down list. For Example INT2.
Enter the minimum and maximum field values in Minimum and Maximum.
For Example 0 and 16000 respectively.
Enter Field value and corresponding Converted value for Point 1 and Point
2 to define the conversion. For Example 0 and 1000 respectively.
Example: If the field value is 8000, the corresponding converted value must
be 500.
ATTENTION
While configuring the Points in Quick Builder,
1000
0 to 1000
100
0 to 100
The following table describes some sample field values and their corresponding
engineering values in Experion:
Data Format
Input
Range
PLC
110
Field
value
PLC
value
Engineering
value
(Converted
value)
2.5
volts
8000
500
2 volts
4000
250
Engineering
0 to 5
volts
Minimum: 0
Point 1: 0
Maximum: 16000
Point 2: 1000
1 to 5
volts
Minimum: 0
Point 1: 0
Maximum: 16000
Point 2: 1000
R300
6/08
4. Configuration
4.4 Downloading Quick Builder Points to Experion
4.4
Overview
After adding and configuring items, you must download all or part of your project to the
server database. The Channel, Controller or Point that have been imported or manually
created in Quick Builder must be downloaded to Experion server database before you can
use them.
The items are downloaded in the following sequence:
MasterLogic Channel.
MasterLogic Controller(s).
Analog/Status Point(s).
REFERENCE EXTERNAL
For more details on downloading items to Experion, see Experion Knowledge
Builder > Experion PKS R300 > Configuration > Quick Builder Guide >
Managing items > Downloading items.
After downloading, the MasterLogic Channel and MasterLogic Controller are enabled in
the Experion Station using View > System Status > Channels.
R300
6/08
111
4. Configuration
4.5 Verifying the Configuration
4.5
Overview
After downloading Points to the Experion, enable the Channel and Controller from the
Experion Station.
After enabling the Channel and Controller, the following events occur:
The MasterLogic server starts communicating with the PLCs using the configuration
information from the Experion server database. A connection is established with the
ML Server based on the Channel configuration.
ML Server establishes communication with the PLCs using the IP Address & other
PLC specific details configured using the configuration tool.
The ML Server reads data from the PLC and transfers the values to the
corresponding parameters in Experion Points. The data values written into these
parameters are written into the appropriate memory locations in the PLC.
Based on the status of the PLCs, the alarms/events are raised by the ML Server, in
the Experion.
The data, alarms raised by the PLCs and change of event in the PLCs can be
monitored from the Experion Station.
You must ensure that PLCs are configured with correct IP address and there is a
successful communication between the PLCs and the ML Server as represented by the
Channel status.
Verifying data exchange between PLC and Experion
The Point Detail display in the Experion Station helps in monitoring the online status of
each parameter for a particular Point and the data exchange between the PLC and the
Experion server.
112
The parameter values set in the Point Detail display reflects in the Address
monitoring window of the SoftMaster tool.
The parameter values set in the Address monitoring window reflects in the Experion
station.
R300
6/08
4. Configuration
4.5 Verifying the Configuration
The following procedure is an example to verify data exchange between the PLC and the
Experion:
Step
Action
Ensure that the ML16K user defined data format is configured in Experion.
The user-defined data format ML16K is used here to convert between the
field value (0 to 16000) and the engineering value (0 to 1000).
4
Enable the Channel from the Channel Summary page in the Station.
The MasterLogic Server starts communicating with the PLC using the
configuration information.
The MasterLogic Server reads data from the PLC and transfers the values
R300
6/08
113
4. Configuration
4.5 Verifying the Configuration
Step
Action
Assume that the data value stored in the 10th word of M memory area is
8000. The following image shows the value displayed in the Address
Monitoring window of the SoftMaster tool:
114
R300
6/08
4. Configuration
4.5 Verifying the Configuration
Step
Action
The raw value (8000) is converted to the engineering value (500) because of
the ML16K data format and updated in the PV parameter. This value is
displayed in the Station as shown in the following image:
R300
6/08
115
4. Configuration
4.5 Verifying the Configuration
116
Step
Action
Change the value of M0010 memory location through the Change Current
Value dialog box in Address Monitoring Window as shown in the following
image:
R300
6/08
4. Configuration
4.5 Verifying the Configuration
Step
Action
The raw value (12000) is converted to the engineering value (750) because
of the ML16K data format and updated in the PV parameter. This value is
displayed in the Station as shown in the following image:
R300
6/08
117
4. Configuration
4.5 Verifying the Configuration
Step
7
118
Action
Set a value 250 to SP parameter in the Station as shown in the following
image:
R300
6/08
4. Configuration
4.5 Verifying the Configuration
Step
Action
The engineering value (250) is converted to the raw value (4000) and
updated in the %MW80 memory location. This can be observed in the
Address Monitoring window of the SoftMaster tool as shown in the following
image:
R300
6/08
119
4. Configuration
4.6 Adding new PLC dynamically
4.6
Overview
The PLCs can be added dynamically in the ML Server Configuration tool when the ML
Server is running.
To add a new PLC dynamically when the ML Server is running, perform the following
steps:
Step
Action
Configure the PLC information for the new PLC as explained in Configuring
ML Server using Configuration Tool.
Build the points for the new PLC as explained in Using PointBuild Utility.
The status of data communication for the new PLC can be viewed in the
graphics pages.
To view the PLC status in the custom graphics pages, the Station must be
closed and re-opened.
120
R300
6/08
Overview
Experion displays
The Experion standard Station displays and the Custom displays are used for monitoring
the PLC status.
The following are the Experion standard Station displays:
R300
6/08
121
Action
Configure the PLC information using the ML Server Configuration Tool, for
each PLC with which the ML Server must communicate. Ensure that EPKS
Asset Name is configured in the tool.
REFERENCE INTERNAL
For more information about configuring the PLC information, see
Configuring PLC Information.
2
122
Click Start > Programs > Honeywell MasterLogic Server > PointBuild
Utility.
R300
6/08
Action
Click Browse to change the point build file path. The output file with
extension .out is created in the same path.
Note: The default path and filename appears in Point Build File Name.
The PLCID, PLCName, PLCType, Asset Name of each PLC configured is
Select each PLC or click Check All to select all the PLCs.
For example:
The MLPLC_StatusPoints.pnt file is created. This file contains the
7
R300
6/08
Click Search to check the existence of Points for the local Experion server.
MasterLogic-Experion PKS Integration - User's Guide
Honeywell Confidential & Proprietary
123
Action
If there is an error during point building the following message appears:
124
R300
6/08
5.3
File name
Description
Config Info
MLPLC_Config.htm
Status Info
MLPLC_Status.htm
Driver Info
MLPLC_Driver.htm
Config Info
The Config Info page is used for monitoring the base slot information of each PLC and
the status of communication between the PLC and the Experion server.
The following PLC information appears in the Config Info page:
R300
6/08
PLC Name
PLC ID
PLC Type
Base number
125
To view the general PLC and base/slot information in the Experion display, perform the
following steps:
Step
126
Action
Ensure the Points corresponding to the PLCs are built using the PointBuild
utility.
Click Start > Programs > Honeywell MasterLogic Server > Configuration
Tool and select the PLC.
Select EPKS Write and IO Read check boxes under Monitor using the ML
Server Configuration Tool.
R300
6/08
Action
Enter MLPLC_Info.htm in the Command zone. Press Enter.
The following page appears:
R300
6/08
127
Action
The following page appears for ML 200:
128
R300
6/08
Action
The following page appears for ML 100R:
displayed.
Note: All the fields in the page (except the PLC Name and Base Number)
are not editable. The IP Address indicated in green is the active IP Address.
8
R300
6/08
129
Action
ATTENTION
If some of the IO Modules are not displayed properly, then edit
MLMonitor.xml as explained in Adding a new IO Module.
The following information appears in 3 columns in the lower part of the
window:
The Name column indicates the slot position and module name.
The Assigns Information column indicates the module information.
The Description column indicates the module description.
ATTENTION
The base slot information is not available for ML100R and not
displayed in the Config Info page.
130
R300
6/08
To view the RTC time in the Config Info page, perform the following steps:
Step
Action
Click Start > Porgrams > Honeywell MasterLogic Server > Configuration
Tool and select the PLC.
Select EPKS Write under Monitor and Enable Read/Write under RTC using
the ML Server Configuration tool.
following figure:
R300
6/08
131
Status Info
The Status Info page is used for monitoring the online status of each PLC, the ML
Server and the data exchange between the PLC and the Experion server.
The parameter value for the PLC status set in the xml files is used for updating the
PLC status information in the Experion graphics pages.
To verify the PLC status information updates in the Experion graphics pages, perform the
following steps:
Step
132
Action
Ensure the Points corresponding to the PLCs are built using the PointBuild
utility.
Click Start > Programs > Honeywell MasterLogic Server > Configuration
Tool and select the PLC.
Select EPKS Write and Status Read check boxes under Monitor using the
ML Server Configuration tool.
R300
6/08
Action
The status of the CPU operation mode is updated in the Experion graphics
display.
4
Open MLPLC_Config.htm from the Experion Station and select the PLC for
which you want to view the status. See Config Info for more details.
R300
6/08
133
Action
CPU Operation Mode
RUN
STOP
ERROR
DEBUG
Local PADT
Remote PADT
Remote Comn.
Local / Remote
Local
Remote
Online Editing
Download
Internal Proc
Done
Error
Miscellaneous Flags
134
Forced Input
Forced Output
Skip I/O
Fault Mask
Monitor Mode
R300
6/08
Action
CPU MODBUS Port
Stop Instruction
ESTOP Instruction
Minimum
Current
R300
6/08
Configuration Error
External Equipment
135
Action
Comn. Module
Parameter Error
CPU Warnings
RTC Error
Task Collision
External Equipment
Battery Failure
136
HSL1
P2P1
R300
6/08
Action
The following page appears for ML 100R:
The CPU Type and OS Version (CPU firmware version) are displayed.
R300
6/08
Slot Info
PADT_CNF
CNF_ER
CNF_WAR
DOMAIN_ST
137
Action
ATTENTION
The option of selecting another PLC is not available in Status Info
page. To view another PLCs status, select a PLC name from
Config Info page and click Status Info tab.
The CPU operation in run mode is displayed in the Experion graphics
138
Click Stop button in the Softmaster tool or using the keys on the PLC,
change the CPU operation mode to stop.
R300
6/08
Action
R300
6/08
139
Action
Click Yes.
The CPU operation mode status is updated in the graphics display within
8
in the Softmaster tool or using the keys on the PLC, change the
Click
CPU operation mode to run.
The following message appears:
Click Yes.
The CPU operation mode status is updated in the graphics display within
140
R300
6/08
R300
6/08
Action
141
Driver Info
The ML Server diagnostic parameter information appears in the Driver Info page. This
page is used for viewing the status of communication between the ML Server, PLC and
the Experion.
To view the ML Server diagnostics information, perform the following steps:
142
Step
Action
Click Start > Programs > Honeywell MasterLogic Server > Configuration
Tool and select the PLC.
Select EPKS Write check box under Monitor using the ML Server
Configuration tool.
Select ML Server from the left pane. Enter the frequency for General
Diagnostic and PLC Diagnostic under ScanPeriod of the ML Server tab.
Open MLPLC_Config.htm from the Experion Station and select the PLC for
which you want to view the Driver Diagnostics information. See Config Info
for detailed procedure.
R300
6/08
Action
The following page appears:
ATTENTION
The option of selecting another PLC is not available in Driver Info
page. To view another PLCs driver diagnostics, select a PLC name
from Config Info page and click Driver Info tab.
R300
6/08
143
The following table lists the ML Server diagnostics parameters displayed in the graphics
page:
Parameter Name
Description
PSCommunication Status
Number of Requests
Number of Responses
144
R300
6/08
Description
Licensed Mode
R300
6/08
145
Description
146
R300
6/08
R300
6/08
Description
147
5.4
Action
148
R300
6/08
Action
In the Station Command Zone, enter the name of the Point. Press F12.
The Point Detail page appears.
REFERENCE - EXTERNAL
For more information on Experion displays, see Experion Knowledge
Builder.
R300
6/08
149
150
Action
The graphics pages and the xml files must be available in the client system
for viewing the PLC information in the client system. If the files are not
available, ensure to copy the graphics pages and xml files from the
installation path (typically C:\Program Files\Honeywell\Experion
PKS\Client\Abstract) to the client system in the same path.
The connection properties of the Experion Station must have the folder path
C:\Program Files\Honeywell\Experion PKS\Client\Abstract in the list. This
allows the viewing of PLC information in the client system.
R300
6/08
Action
ATTENTION
To view the PLC status from an Experion client system, the points
need not be built using the Point Build utility.
3
R300
6/08
To invoke the PLC display pages, follow the procedures explained in Using
Experion custom displays.
151
5.6
Overview
Experion Point parameters are configured in QuickBuilder with PLC Points for data
exchange between PLC and Experion. The quality of the Experion Point parameter
indicates the status of the data in PLC or the data communication with Experion.
MasterLogic-Experion integration enables the monitoring of analog input signal failures
such as transmitter failure or disconnection of input signal. All channels of all analog
input modules are constantly monitored for input signal failure. If the input signal fails,
all Experion points configured for this input channel is set to BADPV status for safer
control of the plant.
The BADPV setting is applicable for the following modules:
Module Type
Model#
Analog Input
module
2MLF-AV8A
Description
Voltage Input: 8 channel
DC 1 ~ 5V / 0 ~ 5V / 0 ~ 10V / 10 ~ +10V
2MLF-AC8A
2MLF-AD4S
Thermocouple
Input Module
2MLF-TC4S
RTD Input
Module
2MLF-RD4A
The following explains the two ways of setting quality for the Point parameter:
152
Setting quality for the item based on the PLC Read command responses.
R300
6/08
R300
6/08
Step
Action
Click Start > Programs > Honeywell MasterLogic Server > Configuration
Tool and select the PLC.
Select EPKS Write and IO Read check boxes under Monitor in the
configuration tool to view the IO module information in the Experion graphics
display. To view PLC status information in Experion graphics display, select
Status Read and Alarm Raising check boxes.
Configure the Input Range as 1~5V in the Softmaster tool. Ensure to write the
IO Module configuration to the PLC.
153
Action
Configure a PLC Point as ML01.U02.06$DEV#WORD in Quick Builder and
download to the Experion server.
Note: This PLC point must be configured with address U02.02 for channel 0
and with address U02.06 for channel 4. ( .06 is derived by adding the base
.02 and the channel number.)
154
R300
6/08
Action
View the status of the data communication in the Station display.
R300
6/08
155
Action
Disconnect the input signal from Channel 4.
View the status of the data communication in the Station display.
Note: The previous example is for Channel 4. If you want to test with a
different channel in the IO module, ensure that the data item configured in
Experion is also changed appropriately.
156
R300
6/08
Action
Alarm is raised corresponding to the disconnected channel.
R300
6/08
157
158
R300
6/08
Alarm integration
Types of Alarms
The following are the two types of Alarms raised by the ML Server:
PLC Status diagnostics Alarms These alarms are raised based on the current
PLC Status.
The Asset configured in the PLC tab of the configuration tool, for that particular PLC, is
used while generating the Alarms/Events.
PLC Status Diagnostics alarms
After downloading Points to the Experion server, the ML Server starts receiving the
status data from the PLC at every configured interval (default is 10 seconds).
Alarms are raised based on the present PLC status. Another PLC level alarm is raised
corresponding to the PLC Point if any of the alarming conditions is active at that point of
time for the PLC. These alarms can be viewed in the Alarm Summary display of the
Experion Station.
ATTENTION
If one or more alarms are raised at the status bit level of a Point, the OP
parameter value of the Point is set ON and the corresponding alarm is raised
at the PLC level.
R300
6/08
159
R300
6/08
To view the PLC alarms in the Experion Station, perform the following steps:
Step
Action
Ensure the Points corresponding to the PLCs are built using the PointBuild
utility.
Select the Status Read and the Alarm Raising check boxes under Monitor
in the ML Server Configuration tool.
The operation mode of the CPU is RUN and therefore the Stop by Stop
R300
6/08
161
162
Action
Add the Stop Instruction to the Ladder logic program using the Softmaster
and write the program to the PLC.
R300
6/08
Action
After executing this instruction, the PLC CPU operation mode changes to
STOP.
The status of the flag indicating that CPU has stopped by Stop instruction
R300
6/08
163
Action
Remove the Stop Instruction from the Ladder logic program using the
Softmaster and write the program to the PLC. Change the PLC CPU
operation mode to RUN.
The operation mode of the PLC CPU changes to RUN as indicated in the
status page.
164
R300
6/08
Action
R300
6/08
165
166
R300
6/08
6.2
PLC Events
Description
Buffer Size in
CPU
Error log
Shutdown log
1024 events
1024 events
2048 events
Mode log
System log
2048 events
Possible Values
Enabled/Disabled
Description
If it is Enabled, the already existing
R300
6/08
167
Possible Values
Description
Log To File
Enabled/Disabled
Events
Enabled/Disabled
ScanPeriod
After the ML Server starts communicating with the PLCs, depending on the values of
these parameters, the events are transferred to the Experion server or the Log files.
The backlog events are saved in the memory area of the respective PLCs. These events
can be viewed in the Softmaster, as shown in the following figure:
After restarting the ML server, these events are transferred to the Experion server or log
files based on the PLC log parameters settings. To get the backlog of the PLC logs into
Experion, the Initial history option could be enabled.
To view a summary of events, select View > Events > Event Summary from the
Experion Station Display. The following figure depicts the list of events viewed from the
Experion Station:
168
R300
6/08
The following figure depicts how the PLC events are transferred to Experion server and
are saved in the log files:
169
6.3
Sequence of Events
Raising SOE
The sequence of events (SOE) can be logged based on the value of some status indicating
bits in the PLC. These bits are referred using the memory address. Each status bit refers
to particular information about the PLC. A special command called SOE can be used for
configuring the memory addresses of these bits. The SOEs are timestamped by PLC. The
resolution of the SOE is 5 milliseconds.
After downloading Points to the Experion server, the ML Server starts receiving the
status data from these memory addresses within the PLC. The SOE Information
configured in SOE tab of the configuration tool, indicates if an SOE needs to be raised
depending on the bit value stored in the memory address. These SOEs can be viewed
from the SOE Summary display in the Experion Station.
Parameter
Description
Memory
Address
Option
Description
170
R300
6/08
Action
Configure the SOE information for a particular PLC, using the ML Server
Configuration tool.
R300
6/08
171
Action
Double-click Value.
The Change Current Value dialog box appears.
172
Click OK.
R300
6/08
Action
The memory address value is changed to 1 (On) as shown in the following
figure:
R300
6/08
173
174
R300
6/08
CAUTION
The XML files contain critical parameters used for fine-tuning of the ML
Server. Incorrect configuration of these parameters could adversely affect the
performance of the MasterLogic-Experion integration. Therefore, Honeywell
recommends that you retain the default values for the critical parameters.
However, if you want to reconfigure the critical parameters, understand the
purpose of each parameter and how it works before changing the
configuration.
R300
6/08
175
The following table lists the XML files available for configuring the PLC information:
MLConfig.xml
REFERENCE INTERNAL
For more information on parameters of MLConfig.xml
file, see Configuring ML Server parameters in
MLConfig XML.
MLMonitor.xml
This file acts as common settings file for the ML Server and
the Graphics.
The ML Server updates the PLC information into Experion
REFERENCE INTERNAL
For more information on parameters of
MLMonitor.xml file, see Monitoring ML Server
parameters in MLMonitor XML.
MLAppSettings.xml
settings.
This contains some important configurations such as
REFERENCE INTERNAL
For more information about parameters of
MLAppSettings.xml file, see Configuring ML Server
Application Settings.
MLSOEConfig.xml
This file is used for configuring the SOEs for the PLCs
176
R300
6/08
REFERENCE INTERNAL
For more information about parameters of
MLSOEConfig.xml file, see Configuring PLC SOEs in
MLSOEConfig XML.
R300
6/08
177
7.2
Overview
The XML files are used for configuring the following ML Server features:
7.3
Alarms
SOEs
Alarms
178
Priority denotes the severity of the alarm. The different values that can be set to
priority are:
3 Urgent
2 High
1 Normal
0 Low
Alarm, indicates when the alarm must be raised. The different values set to alarm
are:
F This denotes that no alarm is raised for this bit value. This is the default
value for alarm setting.
MasterLogic-Experion PKS Integration User's Guide
Honeywell Confidential & Proprietary
R300
6/08
Alarm = F indicates that by default, an alarm is not raised for the status bits.
Value0ShapeIndex represents the default color indication of the PLC status for the
bit value 0. (1 Black, 2 Red, 3 Green. These color LEDs are indicated in the
MLPLC_Status graphics page)
Value1ShapeIndex represents the default shape index for the bit value 1.
This indicates that if there are no specific settings for any of the status bits, then the
default settings are used for that status bit.
Configuring alarms at bit level
To configure alarms at bit level, the Priority and Alarm attributes of PLCInfo >
AlarmInfo > Bit tag is configured in MLMonitor.xml file.
The following code snippet depicts how an alarm is configured at the bit level:
Alarm = 1 shows that an alarm is raised when the value of 96th status bit is 1.
Desc = CPU configuration error indicates the description of the alarm displayed
in the alarm summary display.
The alarm raised because of this alarm setting is shown in Figure 6.1-1.
R300
6/08
179
ATTENTION
To configure alarms for ML100R in MLMonitor.xml file, configure the Alarm
and Priority parameters of PLCInfo100 > AlarmInfo100 tag.
180
R300
6/08
7.4
SOEs
SOEOption, indicates when SOE must be raised. The different values set to this
parameter are:
SOEOption = 1 indicates that by default an SOE is raised when the value of any
configured memory address is 1.
DataType = BIT indicates the data type of the value stored in the memory
address.
This indicates that if there are no specific settings for any of the memory addresses, then
these default settings apply for that memory address.
R300
6/08
181
182
SOEOption = 0, indicates that an SOE is raised when the value of the memory
address is 0.
Description = Boiler Unit turned ON., indicates the description of the SOE
displayed in the SOE Summary display.
R300
6/08
7.5
Overview
After configuring and downloading the Points, ML Server starts communicating with the
PLCs. During this communication ML Server periodically reads the PLC information
like status, base-slot, AD module and Special module. The information is updated in the
Experion UDP parameters configured using the MLMonitor.xml and MLConfig.xml
files.
REFERENCE - INTERNAL
For more information on Experion UDP parameters, see Monitoring ML
Server parameters in MLMonitor XML.
Base-Slot information
IO Module information
AD Module information
R300
6/08
183
From the previous snippet, the 96th bit value of the PLC status information is written to
CNF_ER_CPU_ER, the EPKS parameter. The description of the parameter is provided
in Desc. The alarm corresponding to the parameter is also raised using the setting
Alarm=1 and Priority=3.
Note: These settings are also used for viewing the PLC status in the graphics display.
Configuring Base-Slot Information in MLMonitor.xml
The Base Slot information read from the PLC are written to the EPKS parameters using
MLMonitor >PLCInfo > BaseSlotInfo tag settings defined in MLMonitor.xml.
The following xml snippet depicts how the bit value is mapped to EPKS UDP:
From the previous example, the number of slots in Base 0 is written to the EPKS
parameter B0NumSlots. The value corresponding to the module in Slot 0 is written to
the EPKS parameter B0S0. The total number of bases is written to the EPKS parameter
NumBases.
ATTENTION
These settings are also used for viewing base slot information in the Graphics
display. The base slot information is supported only in ML200.
Identifying the AD Module and updating the corresponding EPKS UDP parameters.
Identifying the Special Module and updating the corresponding EPKS UDP
parameters.
184
R300
6/08
Suppose the Module ID=5A40 is read from the EPKS UDP parameter B0S1
configured in base-slot information.
The Name and Description parameter indicate the module name and description.
The value configured in ShapeIndex indicates the index of the shape to be used for
representing the module in the Graphics display.
The FirstColumn=Module# represents the heading for the first column in the
Graphics display. The modules Name=2MLL-CH2A is displayed in this
column.
185
The Offset=08 in the AD Module command response indicates the status of the
Channels in that AD Module. (Note: The offset value is an hexadecimal)
The Offset=0C in the AD Module command response indicates the input range to
that AD Module.
186
R300
6/08
For example, consider the module in Slot 1of Base 0 is a SpecialModule. The following
table explains the mapping between the Special module information stored in the U
memory area and the EPKS UDP parameter:
Memory
location
U01.10
Remark
The value stored in this location
indicates whether the Channels of that
module are Connected or not
Connected.
REFERENCE - INTERNAL
For more details on Special Module information, see Special Module
information in Appendix.
R300
6/08
187
Five types of module errors at each slot level which are consolidated and placed in a
single ModuleError parameter corresponding to the Base Slot UDP.
The alarms for the module errors are raised in Experion containing the exact error details
i..e cause of the error, base/slot position of the I/O module.
The All Module information is always stored in F memory area. The address range in the
F memory area and the corresponding alarm description for the module errors are set
using the BaseModule parameter of AllModuleInfo tag, as shown in the following code
snippet:
The StartAddress and EndAddress refer to the start and end address within the F
memory area for all the Bases. The Base range starts from 0 and ends at 7. The value
stored in each range corresponds to the number of slots or the CPU scan period or
module errors as explained in the Description.
The following are inferred from the previous example:
188
R300
6/08
The 5 different module error values set using the AllModuleInfo tag is used for
displaying the module status in PLC custom graphic displays. The module status is
indicated using the LEDs in the graphic display. The module level LED glows Red if any
of the errors are active for the particular I/O module or it glows green.
The PLC scan periods are set using the MLMonitor > PLCInfo > MiscellaneousInfo >
PLCScanPeriodInfo tag in MLMonitor.xml. The parameter includes the minimum,
maximum and the current scan period for the PLC.
Parameter
Description
RTCReadWriteEnable
RTCSynchInterval
Indicates the time frequency for reading the RTC time from
the PLC.
Note: If this value is 0 then the RTC time is not read from
or written to the PLC.
RTCDeadband
R300
6/08
189
7.6
Overview
MasterLogic-Experion integration enables the monitoring of analog input signal failures
such as transmitter failure or disconnection of input signal. All channels of all analog
input modules are constantly monitored for input signal failure. If the input signal fails,
all Experion points configured for this input channel is set to BADPV status for safer
control of the plant.
The BADPV setting is applicable for the following modules:
Module Type
Model#
Analog Input
module
2MLF-AV8A
Description
Voltage Input: 8 channel
DC 1 ~ 5V / 0 ~ 5V / 0 ~ 10V / 10 ~ +10V
2MLF-AC8A
2MLF-AD4S
Thermocouple
Input Module
2MLF-TC4S
RTD Input
Module
2MLF-RD4A
The following explains the two ways of setting quality for the Point parameter:
Setting quality for the item based on the PLC Read command responses.
190
R300
6/08
The AD Module command response contains the InputRange for that module.
The Special Module command response indicates the values stored in the U memory
area for ChannelConnection.
An alarm is raised for the disconnected Channel in the Experion Station display, if
the AlarmRaisingEnable parameter is set to Yes.
If a PLC Point is configured in EPKS with one of the previous U memory data
addresses (such as UXY.02, UXY.03), then the quality of that particular Point
(ML01.U01.02$DEV#WORD) is set to good or bad based on the corresponding
ChannelConnection status address (UXY.10.0).
The following example explains how the quality of an item name is set to bad:
R300
6/08
191
The connection status of Channel 0 in this module is read from the memory location
U01.10.0.
If the value of U01.10.0 is 1, the Channel 0 is disconnected and the quality of the
previous item name in EPKS is set to bad. Also, a Channel disconnection alarm is
raised indicating Base 0, Slot 1.
If the value of U01.10.0 is 0, the Channel 0 is normal and the quality of the previous
item name in EPKS is set to good.
The Bad Quality for the PLC points configured with TB command is set based on the
NumberOfCycles parameter in the MLAppSettings XML file.
Consider the following example:
192
R300
6/08
7.7
Action
Enter Module ID, Name and Description. To get the Module ID, you need to
check the value of the IO Module for which the shape is not being shown
properly. Get the value of the Module in Hexadecimal and then fill in the
Module ID.
For example, if the proper shape is not being shown for Base0, Slot 4, then
configure a custom display and get the Hexadecimal value of say ML01.B0S4
and fill in the Module ID part.
Enter index value for the shape of the IO Module represented in the graphics
display. If the shape is not already there for the new IO Module, add a new
shape.
REFERENCE INTERNAL
For more information on adding new shapes for the IO Module, see
Adding new shape for IO Module.
7
R300
6/08
Save MLMonitor.xml
193
194
Step
Action
Open the SlotShape.sha file from the installation path (typically C:\Program
Files\Honeywell\Experion PKS\Client\Abstract\MLPLC_Info_files) using
the HMIWebDisplay builder.
Observe the index value of the newly added shape. Use this index value for
configuring the shape index for the IO Module in MLMonitor.xml.
R300
6/08
8. Troubleshooting
8.1
Overview
The ML Server has two modules, the ML Protocol and the ML Server. The modules
generate a series of logs, which are useful for various troubleshooting, analysis and
recording purposes.
The following is the list of logs generated by the ML Protocol and the ML Server:
Activity
Request
Response
Trace
Error
Hex
MLMonitor
ML Server logs
The Parameters under ML ServerLogs to enable/disable the generation of logs are
selected using the ML Server configuration tool. The path to store the log files are also
configured The LogFolderPath parameter value indicates the path, where the ML Server
logs are saved.
R300
6/08
Optional /
Mandatory
Description
Mandatory
195
8. Troubleshooting
8.1 MasterLogic Server logs
Log
Error
Optional /
Mandatory
Mandatory
Description
This log provides information about unsuccessful add
item, exceptions and general error messages.
The information in this log helps for troubleshooting.
Request
Optional
Response
Optional
Trace
Optional
MLMonitor
Optional
ML protocol logs
The parameters under MLProtocol Logs to enable/disable the generation of logs are
selected using the ML Server Configuration tool.. The path to store the log files is also
configured..
The LogFolderPath parameter value indicates the path, where the ML protocol logs are
stored.
196
Optional /
Mandatory
Mandatory
Description
This log provides information on initial xml settings,
socket connection/disconnection status.
R300
6/08
8. Troubleshooting
8.1 MasterLogic Server logs
Log
Optional /
Mandatory
Description
Error
Mandatory
Request
Optional
Response
Optional
Trace
Optional
Hex
Optional
ATTENTION
The Activity and Error logs are mandatory and generated by default. These
logs are not controlled by any parameter setting.
The optional log settings can be enabled/disabled at Runtime by changing
the appropriate XML parameters. Any change for these configurations are
updated every 30 seconds.
R300
6/08
197
8. Troubleshooting
8.2 MasterLogic PLC error messages
8.2
6000
Type
Critical
Description
Cause
Resolution
unwanted files.
6001
Type
Critical
Description
Cause
Resolution
6002
Type
Critical
Description
Cause
the range.
Resolution
range.
198
R300
6/08
8. Troubleshooting
8.2 MasterLogic PLC error messages
6003
Type
Critical
Description
Cause
Resolution
6004
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
6005
6006
R300
6/08
199
8. Troubleshooting
8.2 MasterLogic PLC error messages
6007
Type
Critical
Description
Cause
Resolution
6008
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
6009
Configuration tool.
Resolution
Configuration tool.
6010
Type
Non-Critical
Description
Cause
Resolution
format as following:
PLCID.%<MemoryArea><DataType><Offset>$Command
6011
Type
200
R300
6/08
8. Troubleshooting
8.2 MasterLogic PLC error messages
Description
Invalid Point
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
6012
6013
6014
6015
6016
R300
6/08
201
8. Troubleshooting
8.2 MasterLogic PLC error messages
Resolution
Type
Non-Critical
Description
Cause
Resolution
Type
Non-Critical
Description
Cause
Resolution
6017
6018
command.
6019
Type
Non-critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
6020
6021
202
R300
6/08
8. Troubleshooting
8.2 MasterLogic PLC error messages
6022
Type
Critical
Description
Cause
Resolution
Type
Non-Critical
Description
Cause
Resolution
Type
Non-Critical
Description
Cause
Resolution
6023
6024
6025
Type
Description
Cause
Resolution
Type
Critical
Description
Cause
6026
R300
6/08
203
8. Troubleshooting
8.2 MasterLogic PLC error messages
6027
Type
Non-Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Non-Critical
Description
Cause
6028
6029
Configuration tool.
Resolution
6030
Type
Non-Critical
Description
Cause
Resolution
6031
204
Type
Non-Critical
Description
R300
6/08
8. Troubleshooting
8.2 MasterLogic PLC error messages
by %s Memory Area
Cause
Resolution
Type
Non-Critical
Description
Cause
6032
6033
Type
Non-Critical
Description
Cause
6034
Type
Non-Critical
Description
Cause
Resolution
Type
Non-Critical
Description
6035
R300
6/08
205
8. Troubleshooting
8.2 MasterLogic PLC error messages
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Non-Critical
Description
Cause
Invalid IP address
Resolution
Type
Critical
Description
Cause
Resolution
Type
Non-Critical
Description
Cause
6036
6037
6038
6039
6040
206
R300
6/08
8. Troubleshooting
8.2 MasterLogic PLC error messages
Resolution
Type
Non-Critical
Description
6041
Cause
Resolution
6042
Type
Non-Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Non-Critical
Description
6043
6044
6045
R300
6/08
207
8. Troubleshooting
8.2 MasterLogic PLC error messages
Cause
Resolution
Type
Non-Critical
Description
Cause
Resolution
Type
Non-Critical
Description
Cause
Resolution
Type
Non-Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
6046
6047
6048
6049
6050
208
R300
6/08
8. Troubleshooting
8.2 MasterLogic PLC error messages
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Non-Critical
Description
Cause
Resolution
Type
Non-Critical
Description
Cause
Resolution
Type
Non-Critical
Description
6051
6052
6053
6054
6055
R300
6/08
209
8. Troubleshooting
8.2 MasterLogic PLC error messages
The memory area configured in item name does not
Cause
memory area.
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
Type
Critical
Description
Cause
Resolution
6056
6057
6058
210
R300
6/08
9. Appendix
9.1
AD Module Information
ChannelStatus
The value stored in each bit indicates the status of corresponding Channels available in
the module.
B31
B9
B8
B7
B6
B5
B4
B3
B2
B1
B0
CH
CH
CH
CH
CH
CH
CH
CH
Description
Disable
Enable
InputRange
XGF-AV8A module
The value stored in two consecutive bits indicates the input range to the module.
B
15
CH7
B
14
B
13
CH6
B
12
B
11
B
10
CH5
B
9
B
8
CH4
B
7
CH3
Honeywell International
Process Solutions
2500 West Union Hills
Phoenix, AZ 85027
BIT
Description
00
1V~5V
01
0V~5V
B
6
B
5
CH2
B
4
B
3
CH1
B
2
B
1
CH0
B
0
9. Appendix
9.1 AD Module Information
10
0 V ~ 10 V
11
-10 V ~ 10 V
XGF-AC8A module
B
15
B
14
CH7
B
13
B
12
CH6
B
11
B
10
CH5
B
9
B
8
CH4
B
7
B
6
CH3
B
5
B
4
CH2
B
3
B
2
CH1
B
1
B
0
CH0
Description
00
4 mA ~ 20 mA
01
0 mA ~ 20 mA
OutputType
B
15
B
14
CH7
B
13
B
12
CH6
B
11
B
10
CH5
B
9
CH4
B
8
B
7
CH3
B
6
B
5
B
4
CH2
B
3
CH1
B
2
B
1
B
0
CH0
Description
00
0 ~ 16000
01
-8000 ~ 8000
10
Precise Value
11
0 ~ 10000
Precise value has the following digital output ranges for the analog input range:
- XGF-AV8A
Analog input
-10 ~ 10V
0 ~ 10V
0 ~ 5V
1 ~ 5V
Digital output
R300
6/08
213
9. Appendix
9.1 AD Module Information
Precise Value
-10000 ~ 10000
0 ~ 10000
0 ~ 5000
1000 ~ 5000
- XGF-AC8A
Analog input
4 ~ 20
0 ~ 20
4000 ~ 20000
0 ~ 20000
Digital output
Precise Value
FilterProcess
B31
B9
B8
BIT
B7
B6
B5
B4
B3
B2
B1
B0
CH
CH
CH
CH
CH
CH
CH
CH
B1
B0
Description
Disable
Enable
FilterValue
B31
B9
B8
B7
Offset
214
B6
B5
B4
B3
B2
Details
0x18
0x1C
0x20
0x24
0x28
0x2C
0x30
R300
6/08
9. Appendix
9.1 AD Module Information
0x34
AverageSetting
B31
B9
B8
BIT
B7
B6
B5
B4
B3
B2
B1
B0
CH
CH
CH
CH
CH
CH
CH
CH
B7
B6
B5
B4
B3
B2
B1
B0
CH
CH
CH
CH
CH
CH
CH
CH
B1
B0
Description
Disable
Enable
AverageProcessing
B31
B9
B8
BIT
Description
Count average
Time average
AverageValue
B31
B9
B8
B7
B6
B5
B4
B3
B2
R300
6/08
Details
0x40
0x44
0x48
215
9. Appendix
9.1 AD Module Information
216
0x4C
0x50
0x54
0x58
0x5C
R300
6/08
9. Appendix
9.2 Special Module information
9.2
ChannelRun
B31
B9
B8
B7
B6
B5
B4
B3
B2
B1
B0
CH
CH
CH
CH
CH
CH
CH
CH
Description
Stopped
Running
ChannelConnection
B31
B9
B8
B7
B6
B5
B4
B3
B2
B1
B0
CH
CH
CH
CH
CH
CH
CH
CH
R300
6/08
Description
Normal
Disconnection
217
9. Appendix
9.3 Advanced settings
9.3
Advanced settings
Overview
The MLConfig.xml, MLMonitor.xml and MLAppSettings.xml contain critical
parameters used for fine-tuning of the ML Server. This section describes the list of
critical parameters available in each of the xml file.
Configuring ML Server parameters in MLConfig XML
The MLConfig.xml file is used for configuring the PLC information.
The following table lists the parameters of PLCInfo > MLPLC tag in the
MLConfig.xml file:
Parameter Name
Description
Default
Value
Possible
Values
Name
MLPLC1
1 40
Characters
ID
ML01
01 99,
prefixed with
ML.
Type
ML200R
ML200R,
ML200-IEC,
ML200NonIEC,
ML100R
IPAddress1
0.0.0.0
xxx.xxx.xxx.x
xx
IPAddress2
0.0.0.0
xxx.xxx.xxx.x
xx
IPAddress3
0.0.0.0
xxx.xxx.xxx.x
xx
IPAddress4
0.0.0.0
xxx.xxx.xxx.x
xx
218
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter Name
Description
Default
Value
Possible
Values
RTCSyncInterval
0 3600
RTCDeadband
10
1 60
HeartBeatTimeout
30
0 3600
InitialAddSubscription
No
Yes or No
EPKSAssetName
localhost
1 40
Characters
The following table lists the parameters of PLCInfo > MLPLC > MLMonitorInfo in
the MLConfig.xml file:
Parameter Name
Description
Default
Value
Possible
Values
IOReadEnable
(Only for ML200/
ML200R)
No
Yes or No
StatusReadEnable
No
Yes or No
EPKSWriteEnable
No
Yes or No
AlarmRaisingEnable
No
Yes or No
R300
6/08
219
9. Appendix
9.3 Advanced settings
Parameter Name
Description
RTCReadWriteEnable
(Only for ML200/
ML200R)
No
Yes or No
PointBuildEnable (Only
for ML100R)
No
Yes or No
Default
Value
Possible
Values
The following table lists the parameters of PLCInfo > MLPLC > MLServerLog in the
MLConfig.xml file:
Parameter
Name
Description
Default
Value
Possible
Values
RequestLog
Yes
Yes or No
ResponseLog
Yes
Yes or No
MLMonitorLog
Yes
Yes or No
TraceLog
No
Yes or No
LogFolderPath
0 255
characters
The following table lists the parameters of PLCInfo > MLPLC > MLProtocolInfo in
the MLConfig.xml file:
Parameter Name
RequestLog
220
Description
If yes, the information about each
Request received from the MLServer is
logged before sending to the PLC.
Default
Value
Yes
Possible
Values
Yes or No
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter Name
Description
Default
Value
Possible
Values
ResponseLog
Yes
Yes or No
HexLog
No
Yes or No
TraceLog
No
Yes or No
LogFolderPath
PLCCommandTime
out
2000
0 60000
NumOfConnectionA
ttempts
1 100
ConnectAttemptGa
p
2000
500 3600000
0 255
characters
The following table lists the parameters of PLCInfo > MLPLC > ErrorLogInfo in the
MLConfig.xml file:
Note: The parameters are applicable to SystemLogInfo, ModeLogInfo and
ShutdownLogInfo. (Only for ML200/ ML200R)
Parameter Name
Description
Default
Value
Possible
Values
InitialHistoryEnable
No
Yes or No
LogToFile
No
Yes or No
EventsInDCS
No
Yes or No
R300
6/08
221
9. Appendix
9.3 Advanced settings
Parameter Name
Description
EventCategoryInDCS
System
Alarm
System
Alarm /
System
Event /
SOE
ScanPeriod
10
0 3600
Default
Value
Possible
Values
ATTENTION
Parameters marked * are configured at subnode level to override the default
value.
For example: The data type defined at PLCGeneralParameters is the default
type for all parameters within the tag. The subnode MLServerStart can have
a different data type defined for that particular parameter.
The following table lists the parameters of PLCInfo > DiagnosticsInfo >
PLCGeneralParameters tag in the MLMonitor.xml file:
Parameter Name
222
Description
Default
Value
R300
6/08
Possible
Values
9. Appendix
9.3 Advanced settings
Parameter Name
Description
Default
Value
Possible
Values
EPKSPointName
MLServer
1 40
Characters
ScanPeriod
0 3600
DataType*
INT2
INT2, INT4,
CHAR,
REAL,
DBLE
MLServerI
nitStatusP
arameter
MLConfi
gXML
Parameter
ToUpdate
D_MLConf
igXMLStat
us
1 40
Characters
MLSOE
ConfigX
ML
Parameter
ToUpdate
D_MLSOE
ConfigXM
LStatus
1 40
Characters
MLMonit
orXML
Parameter
ToUpdate
D_MLMoni
torXMLSta
tus
1 40
Characters
MLAppS
ettingsX
ML
Parameter
ToUpdate
D_MLApp
SettingsX
MLStatus
1 40
Characters
MLServ
erStart
Parameter
ToUpdate
D_MLServ
erStartTim
e
1 40
Characters
Connectio
nStatus
PSCom
municati
on
Parameter
ToUpdate
D_PSCom
munication
Status
1 40
Characters
ThreadSta
tus
MainRe
sponseT
hread
Parameter
ToUpdate
D_MainRe
sponseThr
eadStatus
1 40
Characters
HCICall
BackThr
ead
Parameter
ToUpdate
D_HCICall
BackThrea
dStatus
1 40
Characters
R300
6/08
223
9. Appendix
9.3 Advanced settings
Parameter Name
Description
Default
Value
Possible
Values
EPKSC
ommuni
catorThr
ead
Parameter
ToUpdate
D_EPKSC
ommunicat
orThreadS
tatus
1 40
Characters
EngineT
hread
Parameter
ToUpdate
D_Engine
ThreadSta
tus
1 40
Characters
QueueSiz
e
MainRe
sponse
Queue
Parameter
ToUpdate
D_MainRe
sponseQu
eueSize
1 40
Characters
UpdatedTi
me
Diagnos
ticsUDP
Updatio
n
Parameter
ToUpdate
D_Diagno
sticsUDPU
pdatedTim
e
1 40
Characters
RequestID
StaticRe
quest
Parameter
ToUpdate
D_Current
StaticRequ
estID
1 40
Characters
DynamicRe
quest
Param
eterTo
Update
D_Current
DynamicR
equestID
1 40
Characters
Request
Param
eterTo
Update
D_Number
OfRequest
s
1 40
Characters
Response
Param
eterTo
Update
D_Number
OfRespon
ses
1 40
Characters
LicensedNu
mberOfPLC
s
Param
eterTo
Update
D_License
dNumberO
fPLCs
1 40
Characters
LicensedNu
mberOfPLC
Points
Param
eterTo
Update
D_License
dNumberO
fPLCPoint
s
1 40
Characters
LicensedMo
de
Param
eterTo
Update
D_License
dMode
1 40
Characters
Performan
ceParamet
ers
LicensePa
rameters
224
R300
6/08
9. Appendix
9.3 Advanced settings
The following table lists the parameters of PLCInfo > DiagnosticsInfo >
PLCSpecificParameters tag in the MLMonitor.xml file:
Parameter Name
Description
Default
Value
Possible
Values
ScanPeriod
0 3600
DataType*
INT2
INT2,
INT4,
CHAR,
REAL,
DBLE
Connection
Status
PLCConnecti
on
ParameterToU
pdate
D_PLCCon
nectionStat
us
1 40
Characters
ThreadStat
us
RequestThre
ad
ParameterToU
pdate
D_Request
ThreadStat
us
1 40
Characters
ResponseTh
read
ParameterToU
pdate
D_Respons
eThreadSta
tus
1 40
Characters
MonitorThre
ad
ParameterToU
pdate
D_MonitorT
hreadStatus
1 40
Characters
ResponseQu
eue
ParameterToU
pdate
D_Respons
eQueueSiz
e
1 40
Characters
EPKSWriteQ
ueue
ParameterToU
pdate
D_EPKSWr
iteQueueSi
ze
1 40
Characters
EPKSAlarm
Queue
ParameterToU
pdate
D_EPKSAla
rmQueueSi
ze
1 40
Characters
QueueSize
R300
6/08
225
9. Appendix
9.3 Advanced settings
Parameter Name
RequestID
Performanc
eParameter
s
UpdatedTi
me
226
Description
Default
Value
Possible
Values
StaticReque
st
ParameterToU
pdate
D_CurrentS
taticReques
tID
1 40
Characters
DynamicReq
uest
ParameterToU
pdate
D_CurrentD
ynamicReq
uestID
1 40
Characters
Response
ParameterToU
pdate
D_Number
OfRespons
esPerSec
1 40
Characters
Request
ParameterToU
pdate
D_Number
OfRequests
PerSec
1 40
Characters
EPKSWrite
ParameterToU
pdate
Represents number of
EPKS UDP writes per
second.
D_Number
OfEPKSWri
tesPerSec
1 40
Characters
EPKSAlarm
ParameterToU
pdate
Represents number of
EPKS Alarms raised per
second.
D_Nubmer
OfEPKSAla
rmsPerSec
1 40
Characters
StatusUDPUpdati
on
Parameter
ToUpdate
Represents EPKS
parameter with Status UDP
updated time.
D_StatusU
DPUpdated
Time
1 40
Characters
BaseSlotUDPUp
dation
Parameter
ToUpdate
Represents EPKS
parameter with BaseSlot
UDP updated time.
D_BaseSlot
UDPUpdate
dTime
1 40
Characters
ADModuleUDPU
pdation
Parameter
ToUpdate
Represents EPKS
parameter with ADModule
UDP updated time.
D_ADModul
eUDPUpdat
edTime
1 40
Characters
SpecialModuleU
DPUpdation
Parameter
ToUpdate
Represents EPKS
parameter with Special
Module UDP updated time.
D_SpecialM
oduleUDPU
pdatedTime
1 40
Characters
MiscellaneousUD
PUpdation
Parameter
ToUpdate
Represents EPKS
parameter with
Miscellaneous UDP
updated time.
D_Miscella
neousUDP
UpdatedTi
me
1 40
Characters
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter Name
ProtocolSta
ckParamete
rs
R300
6/08
Description
Default
Value
Possible
Values
RTCReadUDPUp
dation
Parameter
ToUpdate
Represents EPKS
parameter with RTC UDP
updated time.
D_RTCRea
dUDPUpdat
edTime
1 40
Characters
DiagnosticsUDP
Updation
Parameter
ToUpdate
Represents EPKS
parameter with Diagnostics
UDP updated time.
D_Diagnost
icsUDPUpd
atedTime
1 40
Characters
RTCWriteUDPUp
dation
Parameter
ToUpdate
Represents EPKS
parameter with RTC Write
UDP updated time.
D_RTCWrit
eUpdatedTi
me
1 40
Characters
RequestQueueSi
ze
Parameter
ToUpdate
D_Request
QueueSize
1 40
Characters
LargeBuffer
Parameter
ToUpdate
D_LargeBuf
fersAvailabl
e
1 40
Characters
SmallBuffer
Parameter
ToUpdate
D_SmallBuf
fersAvailabl
e
1 40
Characters
MediumBuffer
Parameter
ToUpdate
D_Medium
BuffersAvail
able
1 40
Characters
ThreadCount
Parameter
ToUpdate
D_PSThrea
dCount
1 40
Characters
RequestThreadSt
atus
Parameter
ToUpdate
D_PSRequ
estThreadS
tatus
1 40
Characters
ResponseThread
Status
Parameter
ToUpdate
D_PSResp
onseThread
Status
1 40
Characters
TBCOSThreadSt
atus
Parameter
ToUpdate
D_PSTBCO
SThreadSta
tus
1 40
Characters
227
9. Appendix
9.3 Advanced settings
Parameter Name
228
Description
Default
Value
Possible
Values
ResponseReceiv
ed
Parameter
ToUpdate
D_LastRes
ponseRecei
vedTime
1 40
Characters
RequestSent
Parameter
ToUpdate
D_LastReq
uestSentTi
me
1 40
Characters
TBResponseRec
eived
Parameter
ToUpdate
D_LastTBR
esponseRe
ceivedTime
1 40
Characters
COSResponseR
eceived
Parameter
ToUpdate
D_LastCOS
ResponseR
eceivedTim
e
1 40
Characters
MinRequest
Parameter
ToUpdate
D_MinRequ
estTime
1 40
Characters
MinResponse
Parameter
ToUpdate
D_MinResp
onseTime
1 40
Characters
MaxRequest
Parameter
ToUpdate
D_MaxReq
uestTime
1 40
Characters
MaxResponse
Parameter
ToUpdate
D_MaxRes
ponseTime
1 40
Characters
AvgRequest
Parameter
ToUpdate
D_AvgRequ
estTime
1 40
Characters
AvgResponse
Parameter
ToUpdate
D_AvgResp
onseTime
1 40
Characters
PLCConnected
Parameter
ToUpdate
D_LastPLC
Connected
Time
1 40
Characters
PLCDisconnecte
d
Parameter
ToUpdate
D_LastPLC
Diconnecte
dTime
1 40
Characters
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter Name
Description
Default
Value
Possible
Values
HBSentTime
Parameter
ToUpdate
D_LastHBS
entTime
1 40
Characters
StatusRecievedTi
me
Parameter
ToUpdate
D_LastStat
usReceived
Time
1 40
Characters
The following table lists the parameters of PLCInfo > ADModuleInfo tag in the
MLMonitor.xml file:
Note: These parameters are applicable only for ML200/ ML200R.
Parameter Name
Description
Default
Value
Possible
Values
ScanPeriod
10
0 3600
NumberOfParameter
1 255
DataType*
INT2
INT2,
INT4,
CHAR,
REAL,
DBLE
Offset
08
Parameter
ToUpdate
Channel
Status
ADRead
1 40
Charact
ers
The following table lists the parameters of PLCInfo > SpecialModuleInfo tag in the
MLMonitor.xml file:
Note: These parameters are applicable only for ML200/ ML200R.
Parameter Name
R300
6/08
Description
Default
Value
Possible
Values
229
9. Appendix
9.3 Advanced settings
Parameter Name
Description
Default
Value
Possible
Values
ScanPeriod
10
0 3600
DataType*
INT2
INT2,
INT4,
CHAR,
REAL,
DBLE
Address
01
Paramet
erToUpd
ate
Channel
Run
SpecialMod
ule
1 40
Charact
ers
The following table lists the parameters of PLCInfo > AllModuleInfo tag in the
MLMonitor.xml file:
Note: These parameters are applicable only for ML200/ML200R.
Parameter Name
Description
Default
Value
Possible
Values
ScanPeriod
10
0 3600
ParameterToUpdate
Module
Error
1 40
Charact
ers
DataType*
INT2
INT2,
INT4,
CHAR,
REAL,
DBLE
F0150
BaseMod
ule
230
StartAddr
ess
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter Name
Description
Default
Value
EndAddre
ss
F0157
Descriptio
n
Number
of slots
in base
Possible
Values
1 255
Charact
ers
The following table lists the parameters of PLCInfo > BaseSlotInfo tag in the
MLMonitor.xml file:
Note: These parameters are applicable only for ML200/ ML200R.
Parameter Name
Description
Default
Value
Possible
Values
DataType*
INT2
INT2,
INT4,
CHAR,
REAL,
DBLE
ScanPeriod
3600
0 3600
NumberOfBasesParameter
NumBas
es
1 40
Charact
ers
Base
ID
07
NumberOfSlotsPar
ameter
B0Num
Slots
1 40
Charact
ers
Slot
ID
0 11
Paramete
rToUpdat
e
B0S0
1 40
Charact
ers
R300
6/08
231
9. Appendix
9.3 Advanced settings
The following table lists the parameters of PLCInfo > AlarmInfo tag in the
MLMonitor.xml file:
Note: These parameters are applicable only for ML200/ ML200R.
Parameter
Description
Default
Value
Possible
Values
Value0ShapeIndex
0 10
Value1ShapeIndex
0 10
DataType*
INT2
INT2,
INT4,
CHAR,
REAL,
DBLE
Priority*
03
Alarm*
F, 1, 0,
C
ID
Desc
Slot 0
info on
remote
connecti
on from
local
port to
other
ports
1 255
Charact
ers
ParameterTo
Update
SLOT_I
NFO_R
EMOTE
_CON_L
OC_0
1 40
Charact
ers
Bit
The following table lists the parameters of PLCInfo > IOModuleInfo tag in the
MLMonitor.xml file:
232
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter
Description
Default
Value
Possible
Values
ShapeIndex*
0 10
ADModule
No
Yes or
No
SpecialModule
No
Yes or
No
NumberOfChannels
0 1024
FirstColumn
Module#
SecondColumn
Address
Informati
on
ThirdColumn
Module
Descripti
on
Module
ID
25A40
Name
2MLLCH2A
1 40
Charact
ers
Descripti
on
Cnet
Module,
RS232C/R
S-422
1 255
Charact
ers
R300
6/08
233
9. Appendix
9.3 Advanced settings
The following table lists the parameters of PLCInfo > MiscellaneousInfo tag in the
MLMonitor.xml file:
Parameter
Description
DataType*
Default
Value
Possible
Values
CHAR
INT2,
INT4,
CHAR,
REAL,
DBLE
RTCTim
eInfo
ParameterToUpdate
RTCTim
e
1 40
Charact
ers
IPAddre
ssInfo
ParameterToUpdate1
IPAddre
ss1
1 40
Charact
ers
ParameterToUpdate2
IPAddre
ss1
1 40
Charact
ers
ParameterToUpdate3
IPAddre
ss1
1 40
Charact
ers
ParameterToUpdate4
IPAddre
ss1
1 40
Charact
ers
ActiveDataType
INT2
INT2,
INT4,
CHAR,
REAL,
DBLE
ActiveIPAddress
ActiveIP
Address
1 40
Charact
ers
MinSca
nPerio
d
Parameter
ToUpdate
MinScan
Period
1 40
Charact
ers
MaxSc
anPeri
od
Parameter
ToUpdate
MaxSca
nPeriod
1 40
Charact
ers
PLCSca
nPeriod
234
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter
Current
ScanP
eriod
Description
Parameter
ToUpdate
Default
Value
Possible
Values
Current
ScanPer
iod
1 40
Charact
ers
The following table lists the parameters of PLCInfo100 > AlarmInfo100 tag in the
MLMonitor.xml file:
Note: These parameters are applicable only for ML100R.
Parameter
Description
Default
Value
Possible
Values
Value0ShapeIndex
0 10
Value1ShapeIndex
0 10
DataType*
INT2
INT2,
INT4,
CHAR,
REAL,
DBLE
Priority*
03
Alarm*
ID
32-39
Desc
Cpu
Type
1 255
ParameterToUp
date
CPU_T
YPE
1 40
Charact
ers
Bit
R300
6/08
235
9. Appendix
9.3 Advanced settings
The following table lists the parameters of MLServerSettings > MLServerInfo tag in
the MLAppSettings.xml file:
Parameter
Description
ModuleNam
e
MLServer
1 40
characters
PLCIDPrefix
ML
18
characters
ConfigXMLFi
le
MLConfig.xml
1 40
characters
MonitorXML
File
MLMonitor.xml
1 40
characters
SOEConfigX
MLFile
MLSOEConfig.
xml
1 40
characters
CommandSe
parator
# or $
DataTypeSe
parator
# or $
236
Default Value
Possible
Values
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter
Description
Default Value
Possible
Values
DirectVariabl
eSymbol
RequestLog
Yes
Yes or No
ResponseLo
g
Yes
Yes or No
MLMonitorLo
g
Yes
Yes or No
TraceLog
Yes
Yes or No
LogFolderPa
th
C:\\Temp\\Gen
eralLogs
PLCInfoUpd
ateRate
30
0 3600
DemoCertific
ateFilePath
MLPLC_Demo.
cert
1 255
characters
LogRetentio
nDays
30
1 365
days
R300
6/08
237
9. Appendix
9.3 Advanced settings
The following table lists the parameters of MLServerSettings > ProtocolInfo tag in the
MLAppSettings.xml file:
Parameter
Description
Default
Value
Possible
Values
ModuleName
MLProtocol
1 40
characters
RequestLog
Yes
Yes or No
ResponseLog
Yes
Yes or No
Yes
Yes or No
Yes or No
HexLog
TraceLog
Yes
LogFolderPath
C:\\Temp\\G
eneralLogs
Protocol
Settings
MaxNoofChan
nels
0 3600
MaxNoofDevi
ces
100
1 100
MaxNoofSmal
lBuffers
1000
1
100000
MaxNoofMedi
umBuffers
30000
1
100000
MaxNoofLarg
eBuffers
1000
1
100000
SizeofSmallB
uffers
256
256
1024
SizeofMedium
Buffers
512
512
10240
238
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter
QueueS
ettings
Description
Default
Value
Possible
Values
SizeofLargeB
uffers
2000
1024
1048576
SizeofEventQ
ueue
10000
1
100000
PLCHeartBea
tTimeout
5000
1 5000
ThreadMaxCo
unt
500
1 1000
StatusPollingFr
eq
10000
1000
3600000
HeartBeatUpd
ateTimeout
1000
1000
3600000
MainResponse
QueueSize
5000
1
100000
Description
Default
Value
Possible
Values
ServerName
Localhost
1 40
characters
Area
System
1 40
characters
AlarmPriority
03
AlarmSubPriority
0 15
PointBuildFileName
PointBuildFil
e
1 40
characters
R300
6/08
239
9. Appendix
9.3 Advanced settings
Parameter
Description
PointBuildTemplateN
ame
Default
Value
Possible
Values
StatusPointB
uildTemplate
.txt
1 40
characters
The following table lists the parameters of MLServerSettings >XMLPathInfo tag in the
MLAppSettings.xml file:
Parameter
Description
Default
Value
Possible
Values
RegKeyPath
SOFTWARE
\Honeywell\T
PS50\InstallI
nfo
1 255
characters
InstallDriveVal
ue
InstallDrive
0 40
characters
FolderPathVal
ue
InstallComm
onDir
0 40
characters
SubFolderPath
Client\Abstra
ct
0 40
characters
The following table lists the parameters of MLServerSettings >PLCLogInfo tag in the
MLAppSettings.xml file:
Parameter
ShutDownL
ogInfo
240
Description
Default
Value
Possible
Values
Name
PLCShutdow
n
1 40
characters
LogSize
1 10000
NumberOfLogR
equest
128
1 10000
MaxLogPosition
1024
1 10000
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter
Description
Default
Value
Possible
Values
Sou
rce
MAIN_BASE
_SHUT_DO
WN
0 40
characters
Cod
e
-1 10000
Des
c
Main base
shut down
1 255
characters
Name
PLCMode
1 40
characters
LogSize
16
1 10000
NumberOfLogR
equest
64
1 10000
MaxLogPosition
1024
1 10000
Mode
Sourc
e
STATE_MO
D_RUN
0 40
characters
Code
-1 10000
Desc
State Mode
Run
1 255
characters
Sourc
e
MODE_TYP
E_LOCAL_K
EY
0 40
characters
Code
-1 10000
Desc
Mode Type
Local Key
1 255
characters
Shutdow
n
ModeLogInf
o
Type
R300
6/08
241
9. Appendix
9.3 Advanced settings
Parameter
ErrorLogInf
o
Description
242
Possible
Values
Name
PLC Error
1 40
characters
LogSize
16
1 10000
NumberOfLogR
equest
128
1 10000
MaxLogPosition
2048
1 10000
Source
ROMPACK
0 40
characters
Code
22
-1 10000
Desc
Invalid User
program
(Memory
Module)
1 255
characters
Name
PLCSystem
1 40
characters
LogSize
16
1 10000
NumberOfLogR
equest
64
1 10000
MaxLogPosition
1024
1 10000
System
Sour
ce
SYS_HIS_P
ADT
0 40
characters
Code
-1 10000
Error
SystemLogI
nfo
Default
Value
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter
Description
Desc
Default
Value
PADT
Possible
Values
1 255
characters
The following table lists the parameters of MLServerSettings > IntervalInfo tag in the
MLAppSettings.xml file:
Parameter
Description
Default
Value
Possible
Values
MainResponseInterval
500
500 - 3600000
PLCConnectionInterval
500
500 - 3600000
WriteResponseInterval
500
500 - 3600000
MonitorRequestInterval
500
500 - 3600000
ReadRequestInterval
500
500 - 3600000
HCICallBackInterval
500
500 - 3600000
DisableDeviceInterval
500
100 10000
DeleteDeviceInterval
500
100 10000
DisableChannelInterval
500
100 10000
DeleteChannelInterval
500
100 10000
CreateChannelInterval
500
100 10000
EnableChannelInterval
500
100 10000
R300
6/08
243
9. Appendix
9.3 Advanced settings
Description
Default
Value
Possible Values
GeneralReqIDStart
1000
1 4294967295
GeneralReqIDEnd
5000
1 4294967295
DeviceReqIDStart
5000
1 4294967295
DeviceReqIDEnd
10000
1 4294967295
Description
Default
Value
Possible Values
GeneralRequestIDStart
15000
1 4294967295
GeneralRequestIDEnd
20000
1 4294967295
DeviceRequestIDStart
25000
1 4294967295
DeviceRequestIDEnd
30000
1 4294967295
244
R300
6/08
9. Appendix
9.3 Advanced settings
The following table lists the parameters of MLPLCSettings > PLCFamily tag in the
MLAppSettings.xml file:
Parameter
Description
Default
Value
Possible
Values
PLCType
ML100R
ML200R,
ML200-IEC,
ML200_NonIE
C, ML100R
DefaultCommand
CON
SEP, CON,
TB, COS,
DEV
DefaultDataType
WORD
BIT, BYTE,
WORD,
DWORD,
LWORD
ConnectPort
2004
1 65536
RequestHeader
LGISGLOFA
1 20
characters
ResponseHeader
LGISGLOFA
1 20
characters
CommandS
upported
MemoryInfo
R300
6/08
Name
SEP
SEP, CON,
TB, COS,
DEV
MaxPacket
Size
1024
100 1400
NumberOfV
ariables
1 1000
Area
1 40
characters
Readable
Yes
Yes or No
245
9. Appendix
9.3 Advanced settings
Parameter
Description
Default
Value
Possible
Values
Writable
No
Yes or No
ScanPeriod
10
0 3600
seconds
BitLow
00.00.00
1 20
characters
15.07.63
DataTypes
Supported
XBWDL
AddressFor
mat
ww.ww.b
b
CustomAre
aType
BASE_S
LOT_AR
EA
BASE_SLOT_
AREA,
COMMON_A
REA,
BIT_WORD_
AREA
QueueSetti
ngs
DeviceResp
onseQueue
Size
10000
1 100000
CPUType
Code
01
-1 10000
BitHigh
246
xx.xx.xx
1 20
characters
xx.xx.xx
X/B/D/W/L/d/
w/l/r/R
R300
6/08
9. Appendix
9.3 Advanced settings
Parameter
Description
CPUName
Default
Value
GM1
Possible
Values
1 20
characters
The following table lists the parameters of MLPLCSettings >BadPVInfo tag in the
MLAppSettings.xml file:
Parameter
Description
BadPVSup
ported
InputRange
SpecialMo
duleMap
Special
Channel
Default
Value
1v~5v
StatusA
ddress
UXY.10.0
DataAdd
ress
UXY.02
Description
Default
Value
Possible
Values
PLCID
ML01
01 99,
prefixed
with ML.
SOEOption
1, 0 ,C, F
DataType
BIT
M0010F
0 255
characters
SOE
R300
6/08
Device
Address
247
9. Appendix
9.3 Advanced settings
Parameter
Descript
ion
248
Description
Represents the description of the SOE
displayed in the SOE Summary display.
Default
Value
M00100
SOE
Alarm
Possible
Values
0 255
characters
R300
6/08
Honeywell International
Process Solutions
2500 West Union Hills
Phoenix, AZ 85027