| |
 |
|
|
MLC 9000 PID Control System (UML)
OPC Server Data Sheet
| Devices Supported: |
MLC 9000 system
(tested with B220 BCM, C130 LCM, and C230 LCM) |
| Device Manufacturer: |
West Instruments (UK) |
| Profile Name: |
MLC9000.PRO |
| Profile Built For: |
UOS |
| Platform: |
Windows NT4.0 / 2000 / XP |
| Interface Type: |
RS-485RS-485 |
| Max Devices Supported: |
1 BCM (Bus
Communication Module), up to 8 LCMs (Loop Controller Module)1 BCM (Bus
Communication Module), up to 8 LCMs (Loop Controller Module) per BCM (256
controllers total) |
| Protocol: |
Modbus RTU |
| Comment: |
UML is comprised of the Universal OPC
Server (UOS) for Serial and TCP/IP Devices and the MLC9000.PRO device profile. The UML mnemonic is used to identify this unique combination. UOS will
also support many other serial or TCP/IP device profiles. Please refer to our web site for
the current list. |
|
UOS is a stand-alone OPC Server that can be used with any OPC
compliant Client such as Intellution’s FIX® or FIX Dynamics® or
OA’s Enterprise Automation software. UOS has many advanced features like: DataView,
DataScope, Serial and TCP/IP communications support, and multiple "different"
device support. Please refer to our web site for more information on UOS capabilities. |
| Contact: |
Dimension Software, Inc.
1536 St. Clair Road, Taylorsville, NC 28681, USA
Voice: (828) 635-7189, Fax: (828) 625-5319,
E-Mail:  ,
Web: http://dimension-software.com |
| References: |
UOS (Universal OPC Server) Electronic
Documentation |
|
"MLC 9000
Bus-Compatible Temperature Control System User Guide" p/n 702324-0001
Feb. 2000"MLC 9000 Bus-Compatible Temperature Control System User
Guide" p/n 702324-0001 Feb. 2000 |
| |
|
Introduction
|
| This document provides general information on the device commands supported by UOS and
the MLC9000.PRO profile. If you have installed UOS, you should also review the sections
titled About the I/O Driver, How Do I…, Setting up The I/O Driver, and
Using the PowerTool in the UOS electronic documentation. To get there, click on Help
and Help Topics on the PowerTool menu bar. The PowerTool is a client application
with a graphical user interface that accesses the UOS OPC Server and lets you view and
modify communications channel, device, and datablock properties. |
| |
| Features |
| UOS OPC Server supports the following
features: |
| Feature |
Description |
| 1 |
A user interface called the PowerTool for configuring
channels, devices, and datablocks. Statistical communications data is
provided for throughput analysis at each level. |
| 2 |
The PowerTool has a built-in datascope for checking Host-to-RTU
and RTU-to-Host communications messages. You can write messages to disk
for later analysis. The PowerTool also has context sensitive help. |
| 3 |
Direct, Radio, and Telephone communication modes. |
| 4 |
Automatic reads after a write to confirm a write. |
| 5 |
Automation Interface - You don't have to use the Power Tool
to configure the driver. You can make your own COM or OLE application
(using Microsoft's Visual Basic) to configure the driver and access data. |
| 6 |
Secondary Poll Rate - The OPC Server polls a datablock at
the secondary poll rate once the Access Time expires. Data is polled at
the secondary poll rate until there is another client request for data. If
the secondary poll rate is set for a longer period of time than the
Primary Rate, CPU resources are reduced while ensuring that the datablock
will always be polled. |
| 7 |
Phased Poll Rates. |
| 8 |
Enable/Disable individual communication channels, devices,
and datablocks from the automation interface or your HMI. |
| |
| Device Commands Supported: |
| The device READ/WRITE commands supported are shown in Table
1. They are described in reference to the profile command group that
contains them. A "profile command group" is a group of related
commands. Usually it consists of an I/O Device READ/WRITE command pair.
However, the command group can contain only a device READ command, only a
device WRITE command, or more than one device READ/WRITE pair. This
depends on the protocol of the I/O Device to which the command is
directed. |
| |
| Table 1 – Device Commands Supported by
the UML Profile |
|
If the Profile Command
Group is… |
Then the Device READ command is… |
And the Device WRITE command is… |
Description |
|
LCM00_0006 |
03 |
10 |
LCM Input Parameters 0-6 |
|
LCM00_24 |
03 |
06 |
LCM Input Parameter 24 (External Input Value) |
|
LCM00_2526 |
03 |
N/A |
LCM Input Parameters 25-26 |
|
LCM01_0105_Instance0 |
03 |
10 |
LCM Instance 0 Output 1 Parameters 1-5 |
|
LCM01_25_Instance0 |
03 |
06 |
LCM Instance 0 Output 1 Parameter 25 (Bus Power) |
|
LCM01_0105_Instance1 |
03 |
10 |
LCM Instance 1 Output 2 Parameters 1-5 |
|
LCM01_25_Instance1 |
03 |
06 |
LCM Instance 1 Output 2 Parameter 25 (Bus Power) |
|
LCM01_0105_Instance2 |
03 |
10 |
LCM Instance 2 Output 3 Parameters 1-5 |
|
LCM01_25_Instance2 |
03 |
06 |
LCM Instance 2 Output 3 Parameter 25 (Bus Power) |
|
LCM02_0004 |
03 |
10 |
LCM Setpoint Parameters 0-4 |
|
LCM02_25 |
03 |
N/A |
LCM Setpoint Parameter 25 (Actual Setpoint) |
|
LCM03_0006 |
03 |
10 |
LCM Control Parameters 0-6 |
|
LCM03_0713 |
03 |
10 |
LCM Control Parameters 7-13 |
|
LCM03_2425 |
03 |
N/A |
LCM Control Parameters 24-25 |
|
LCM03_26 |
03 |
10 |
LCM Control Parameter 26 |
|
LCM04_0003_Instance0 |
03 |
10 |
LCM Instance 0 Alarm 1 Parameters 0-3 |
|
LCM04_26_Instance0 |
03 |
N/A |
LCM Instance 0 Alarm 1 Parameter 26 (Alarm State) |
|
LCM04_0003_Instance1 |
03 |
10 |
LCM Instance 1 Alarm 2 Parameters 0-3 |
|
LCM04_26_Instance1 |
03 |
N/A |
LCM Instance 1 Alarm 2 Parameter 26 (Alarm State) |
|
LCM06_0004 |
03 |
10 |
LCM Heater Current Parameters 0-4 |
|
LCM06_24 |
03 |
10 |
LCM Heater Current Parameter 24 (Bus Input Value) |
|
LCM06_2526 |
03 |
N/A |
LCM Heater Current Parameters 25-26 |
|
LCM14_23 |
03 |
N/A |
LCM Calibration Parameter 23 (Calibration Value) |
|
LCM14_2425 |
03 |
10 |
LCM Calibration Parameters 24-25 |
|
LCM15_0106 |
03 |
N/A |
LCM Descriptor Parameters 1-6 |
|
LCM15_2125 |
03 |
N/A |
LCM Descriptor Parameters 21-25 |
|
BCM12_0105 |
03 |
10 |
BCM Communications Configuration Parameters 1-5 |
|
BCM12_0708 |
03 |
10 |
BCM Communications Configuration Parameters 7-8 |
|
BCM15_0106 |
03 |
N/A |
BCM Descriptor Parameters 1-6 |
|
BCM15_0815 |
03 |
10 |
BCM Descriptor Parameters 8-15 |
|
BCM15_1623 |
03 |
10 |
BCM Descriptor Parameters 16-23 |
| |
| OPC Addressing
Information: |
| |
| Item ID’s for the OPC server
follow the following format: |
| <Address>|<Signal
Conditioning>,<Low EGU>,<High EGU> |
| where: |
| <Address> |
is the I/O Address of the
data item requested. The <Address> field is required. The
<Address> field has the format: DataBlockName:VarName[:Bit]
where: |
|
DataBlockName |
The name of the hardware device that contains
the data you want to access. DEVICE name is user assigned in the UOS
PowerTool. |
|
VarName |
Point type. Refer to Table 2 above. |
|
Bit |
Bit number (Bit 0 = LSB and bit 15 = MSB).
This parameter is optional. It is used only if you are addressing a single
bit of a 16-bit value. |
| <Signal Conditioning> |
is the type of Signal
Conditioning desired for the specified address. The default is
"None". The "|" character must separate the
<Address> and <Signal Conditioning> fields. |
| <Low EGU> |
is the low EGU limit for
the specified address. The default is 0. |
| <High EGU> |
is the high EGU limit for
the specified address. The default is 65535. |
| |
| Note that only the <Address>
field is required. All other fields are optional, and are only used for
analog values. |
| |
| The Low and High EGU fields (and
the % deadband value specified for a client group) are used by the OPC
Server in deadband calculations. The deadband calculation specifies when
the OPC server will update a client with new data. If no Low and High EGU
fields are entered, the default is 0-65535. In this case, the Dataview %
Deadband value defaults to 0%. |
| Signal Conditioning
Name: |
Description: |
| NONE |
No Scaling |
| LIN (Unsigned) |
Scales 16-bit unsigned values to the database block's EGU
range. |
| LIN (Signed) |
Scales 16-bit signed values to the database block's EGU
range. |
| 3BCD |
Scales 3-digit Binary Coded Decimal values to the database
block's EGU range. |
| 4BCD |
Scales 4-digit Binary Coded Decimal values to the database
block's EGU range. |
| 8BN |
Scales 8-bit binary values to the database block's EGU
range. Ignores the most significant byte. No Alarming on Out of Range. |
| 8AL |
Scales 8-bit binary values to the database block's EGU
range. Ignores the most significant byte. Alarming on Out of Range. |
| 12BN |
Scales 12-bit binary values to the database block's EGU
range. Ignores the most significant nibble (4-bits). No Alarming on Out of
Range. |
| 12AL |
Scales 12-bit binary values to the database block's EGU
range. Ignores the most significant nibble (4-bits). Alarming on Out of
Range. |
| 13BN |
Scales 13-bit binary values to the database block's EGU
range. Ignores the most significant 3 bits. No Alarming on Out of Range. |
| 13AL |
Scales 13-bit binary values to the database block's EGU
range. Ignores the most significant 3 bits. Alarming on Out of Range. |
| 15BN |
Scales 15-bit binary values to the database block's EGU
range. Ignores the most significant bit. No Alarming on Out of Range. |
| 15AL |
Scales 15-bit binary values to the database block's EGU
range. Ignores the most significant bit. Alarming on Out of Range. |
|
|
|
© 2011 Dimension Software, Inc. All Rights Reserved.
|
|
|
| |
|