Micromod SLC Configuration Manual
Command Series Migration to MOD 30ML™
Tutorial and Reference Guide for
Command Series Migration to MOD 30ML
Training
MicroMod Automation, Inc.
The Company
MicroMod Automation is dedicated to improving customer efficiency by providing the most cost-effective, application-specific process solutions
available. We are a highly responsive, application-focused company with years of expertise in control systems design and implementation.
We are committed to teamwork, high quality manufacturing, advanced technology and unrivaled service and support.
The quality, accuracy and performance of the Company's products result from over 100 years experience, combined with a continuous
program of innovative design and development to incorporate the latest technology.
Use of Instructions
Ì Warning. An instruction that draws attention to the risk of
injury or death.
Note. Clarification of an instruction or additional
information.
q Caution. An instruction that draws attention to the risk of
the product, process or surroundings.
Although Warning hazards are related to personal injury, and Caution hazards are associated with equipment or property damage, it
must be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process
system performance leading to personal injury or death. Therefore, comply fully with all Warning and Caution notices.
Information in this manual is intended only to assist our customers in the efficient operation of our equipment. Use of this manual for
any other purpose is specifically prohibited and its contents are not to be reproduced in full or part without prior approval of MicroMod
Automation, Inc.
Licensing, Trademarks and Copyrights
MOD 30 and MOD 30ML are trademarks of MicroMod Automation, Inc.
MODBUS is a trademark of Modicon Inc.
Health and Safety
To ensure that our products are safe and without risk to health, the following points must be noted:
The relevant sections of these instructions must be read carefully before proceeding.
1. Warning Labels on containers and packages must be observed.
2. Installation, operation, maintenance and servicing must only be carried out by suitably trained personnel and in accordance with the
information given or injury or death could result.
3. Normal safety procedures must be taken to avoid the possibility of an accident occurring when operating in conditions of high
pressure and/or temperature.
4. Chemicals must be stored away from heat, protected from temperature extremes and powders kept dry. Normal safe handling
procedures must be used.
5. When disposing of chemicals, ensure that no two chemicals are mixed.
Safety advice concerning the use of the equipment described in this manual may be obtained from the Company address on the back
cover, together with servicing and spares information.
i Information. Further reference for more detailed
information or technical details.
All software, including design, appearance, algorithms and source
codes, is copyrighted by MicroMod Automation, Inc. and is owned by
MicroMod Automation or its suppliers.
Command Series Migration to MOD 30ML
CONTENTS
CONTENTS
Page
BOOK 1
SECTION 1 – FUNCTIONCODES - INTRODUCTION
HOW TO USE THIS BOOK .................................................................................................. 1-1
ENVIRONMENT BLOCKS.................................................................................................... 1-2
I/O AND COMMUNICATION BLOCKS................................................................................. 1-5
FUNCTION BLOCKS............................................................................................................ 1-5
FUNCTION BLOCK EXECUTION ORDER .......................................................................... 1-9
COMPOUNDS ...................................................................................................................... 1-11
LOOP COMPOUNDS ........................................................................................................... 1-15
THE CONFIGURATON PROCESS...................................................................................... 1-18
PROCEDURE FOR ADDING THE DISPLAY TAG TO DISPLAY INTERFACE BLOCK ..... 1-19
PID CONFIGURATION REFERENCE ................................................................................. 1-22
SECTION 2 – GALLERY TUTORIAL
FOREWARD ......................................................................................................................... 2-1
OBJECTIVES........................................................................................................................ 2-1
INSTRUCTIONS – CREATING A NEW WORKSPACE, PROJECT AND DOCUMENT ..... 2-2
CONFIGURING SCAN GROUPS AND LOOP COMPOUNDS............................................ 2-10
ADDING COMPOUNDS FROM THE GALLERY.................................................................. 2-17
ADDING I/O .......................................................................................................................... 2-20
MAKING CONNECTIONS .................................................................................................... 2-24
CHANGING ENGINEERING RANGES AND ALARM TRIP VALUES ................................. 2-30
CONFIGURING DISPLAY TAG FOR DISPLAY................................................................... 2-34
SETTING UP COMMUNICATIONS WITH MODBUS........................................................... 2-41
COMPILING DATABASE...................................................................................................... 2-43
i
Command Series Migration to MOD 30ML
CONTENTS
BOOK 2 – FUNCTION CODE GALLERY COMPOUNDS REFERENCE
SECTION 1 – PRE-CONFIGURED CONTROL STRATEGIES
1 PRE-CONFIGURED SIGLE LOOP PID CONTROL ............................................................. P1-1
2. PRE-CONFIGURED DUAL LOOP PID CONTROL .............................................................. P2-1
3 PRE-CONFIGURED SIGLE LOOP PID WITH REMOTE SP ............................................... P3-1
4 PRE-CONFIGURED DUAL LOOP PID WITH REMOTE SP ................................................ P4-1
5 PRE-CONFIGURED CASCADE CONTROL ........................................................................ P5-1
6 PRE-CONFIGURED PID RATIO WITH REMOTE SP .......................................................... P6-1
SECTION 2 – FUNCTION CODE COMPOUNDS
1 FUNCTION CODE 1 – FUNCTION GENERATOR............................................................... 1-1
2 FUNCTION CODE 2 – MANUAL SET CONSTANT ............................................................. 2-1
3 FUNCTION CODE 3 – LEAD / LAG...................................................................................... 3-1
4 FUNCTION CODE 6 – HIGH / LOW LIMITER...................................................................... 6-1
5 FUNCTION CODE 7 – SQUARE ROOT............................................................................... 7-1
6 FUNCTION CODE 8 – RATE LIMITER................................................................................. 8-1
7 FUNCTION CODE 9 – ANALOG TRANSFER...................................................................... 9-1
8 FUNCTION CODE 10 – HIGH SELECT ............................................................................... 10-1
9 FUNCTION CODE 11 – LOW SELECT ................................................................................ 11-1
10 FUNCTION CODE 12 – HIGH /LOW COMPARE................................................................. 12-1
11 FUNCTION CODE 14 – SUMMER ....................................................................................... 14-1
12 FUNCTION CODE 15 – SUMMER (2 INPUTS).................................................................... 15-1
13 FUNCTION CODE 16 – MULTIPLY...................................................................................... 16-1
14 FUNCTION CODE 17 – DIVIDE ........................................................................................... 17-1
15 FUNCTION CODE 20 – INDICATOR STATION................................................................... 20-1
16 FUNCTION CODES 25 AND 41 – ANALOG/DIGITAL INPUT ............................................. 25-1
17 FUNCTION CODE 28 – ANALOG/DIGITAL OUTPUT ......................................................... 28-1
18 FUNCTION CODE 33 – NOT................................................................................................ 33-1
19 FUNCTION CODE 34 – MEMORY (R/S FLIP FLOP)........................................................... 34-1
ii
Command Series Migration to MOD 30ML
CONTENTS
20 FUNCTION CODE 35 – TIMER............................................................................................ 35-1
21 FUNCTION CODE 36 – QUALIFIED OR ............................................................................. 36-1
22 FUNCTION CODE 37 – AND (2 INPUT) .............................................................................. 37-1
23 FUNCTION CODE 38 – AND (4 INPUT) .............................................................................. 38-1
24 FUNCTION CODE 39 – OR (2 INPUT) ................................................................................ 39-1
25 FUNCTION CODE 40 – OR (4 INPUT) ................................................................................ 40-1
26 FUNCTION CODE 51 – MANUAL SET CONSTANT........................................................... 51-1
27 FUNCTION CODE 59 – DIGITAL TRANSFER .................................................................... 59-1
28 FUNCTION CODE 156 – PID WITH LOCAL SP .................................................................. 156-1
29 FUNCTION CODE 156 – PID WITH CASCADE .................................................................. 156c-1
30 FUNCTION CODE 156 – PID WITH REMOTE SP .............................................................. 156r-1
31 FUNCTION CODE 156 – PID RATIO WITH REMOTE SP .................................................. 156rr-1
32 FUNCTION CODE 156 – AUTO BIAS STATION ................................................................. 156ab-1
33 FUNCTION CODE 165 – MOVING AVERAGE.................................................................... 165-1
SECTION 3 – FUNCTION CODE COMPOUNDS - EXTRAS
1 EXTRAS – REJECT TO MANUAL........................................................................................ R-1
iii
Command Series Migration to MOD 30ML
CONTENTS
iv
BOOK 1
SECTION 1
FUNCTION CODES –
INTRODUCTION
HOW TO USE THIS BOOK
This book is meant for users of Bailey SLC, CLC controllers who are migrating to the
new generation MicroMod MOD 30ML controllers. Though both Bailey controllers and
MicroMod controllers are microprocessor based programmable controllers, the
configuration and the programming approach to them is different. This book should help a
Bailey user to understand the MOD 30ML controller with minimum time spent in learning
the new technology.
How to use this book:
The ViZapp Software contains Compound Galleries. A compound is a grouping of
function blocks configured and connected together for a specific control application. A
compound gallery is a library of commonly used compounds. Most of the commonly used
Bailey function codes have been translated to MOD 30ML compounds and stored in the
default gallery. This is included in ViZapp software versions 3 and above. The default
gallery contains multiple sections (tabs) for compounds:
Function Codes – Introduction
• General Compounds
• Bailey Function Codes
• Bailey Templates that contain pre-configured Control strategies
• Bailey Extras
This library can also be downloaded from the MicroMod Support website at
http://www.micromodautomation.com
The best way to use this book is to understand the MOD 30ML instrument database by
reading this chapter and then by going through the tutorial in the next chapter. Complete
the hands-on lab on configuring the MOD 30ML controller in the next chapter using the
ViZapp Software. After you have completed the lab, you will understand the mechanics of
configuring the MOD 30ML controller using ViZapp and the subtle difference in the
configuration process between Bailey tools and the ViZapp Software. You will also get
used to the new terminology and how easier and more powerful the MOD 30ML/Modcell
function blocks can be.
The subsequent chapters are reference material for the compounds.
For a complete training on MOD 30ML, use the ViZapp training manual IB-VIZAPP-TUT
with the 3
rd
chapter (PID Loop Lab) replaced by the tutorial in the next chapter. This
tutorial is written in such a manner that you could jump to chapter 4 in the ViZapp
Training manual (IB-VIZAPP-TUT) after completing the tutorial.
Look for updates to the Bailey FC Gallery file at out support website. For technical
support and questions, contact 585 292 9200 or visit the website at
http://www.micromodautomation.com
1 - 1
Command Series Migration to MOD 30ML
Function Codes – Introduction
The user database is configurable and writable to make the instrument perform a variety of
executable functions. The basic logical element of the database is a function block.
Function blocks are grouped to form multiple process loops. Loops in turn are grouped
into sets that are scanned (executed) at the same rate. Up to five different scan rates can be
configured through the interface block. The instrument operates at a fixed base rate (50
milliseconds) and each of the five groups can be configured at any multiple of the base
rate up to the maximum time value (about 1193 hours). I/O module blocks define the
physical interface to the database and serve as data handling blocks between the process
and the function blocks.
The MOD 30ML has a wide variety of function blocks with which you can configure any
complex control strategy. There are 4 types of configuration blocks in the MOD 30ML /
Modcell database. They are:
1. Environment Blocks
2. I/O Module blocks
3. Function Blocks
4. System Blocks
Environment Blocks:
The environment blocks support general instrument operation and do not directly perform
the user defined control functions. These blocks always exist as part of any configuration.
Some of the functions that are executed by these blocks are similar to that of the Station
type blocks in the CLC/SLC world.
The default database contains the following 4 blocks. (In the case of Modcell, the default
database contains only 2 blocks namely the IF and SE).
Interface block (IF):
The interface block contains the overall instrument related information and functionality.
Up to five scan intervals can be specified in this block. The function blocks in the database
can be grouped in to loop compounds and each loop compound can be assigned a scan rate
from this group of five scan rates. The function blocks will be executed at the assigned
rate in the instrument RUN state.
This block also has configurable parameters for start-up options such as running on I/O
mismatch and start-up types such as warm and cold starts. This block also has parameters
that are used for enabling or disabling certain diagnostics.
System Event Block (SE): The system event block supports general instrument operation.
This block defines diagnostic and system event acknowledgement and reporting
capabilities. System events occur in the instrument, are reported by database blocks, and
can be stored into the system event queue. The different types of system events are:
Informational only, Process Alarms, Notification/Request Messages, Diagnostics and
Acknowledge Only Diagnostics.
1 - 2
The system event queue stores a configurable number of time stamped event codes for the
diagnostic points and events reported by the database blocks. These codes are translated
into messages for operator display or logging by the interface software.
Command Series Migration to MOD 30ML
Function Codes – Introduction
Display Interface Block(DIF):
This block is used in MOD 30ML only. This block has configurable parameters for the
following:
• Define an instrument device tag
• Faceplate access and entry constraints (tune and configure passwords, access and entry
timeouts)
• Customize alarm/diagnostic presentation (flash/beep on/off and rates)
• Power up display
• Order in which user displays are selected by the tag key and/or
• Input for remote selection of user display
State Table Block (ST):
This block is used in MOD 30ML only. The State Table block is used by the Display
(DISP) and Process Alarm Display (PAD) blocks. The block consists of a set of tables,
each identified by a unique name. Each table contains a list of values and associated
mnemonic strings which are displayed for the corresponding value on the instrument
faceplate.
The MOD 30ML/Modcell database architecture is shown in the next figure:
1 - 3
Command Series Migration to MOD 30ML
Function Codes – Introduction
Figure 1 .1.
Instrument
Database
Architecture
1 - 4
Command Series Migration to MOD 30ML
I/O AND COMMUNICATION MODULE BLOCKS:
These blocks specify the physical I/O complement of the instrument. The following I/O
module blocks are available:
Type Function Availability
AIN Built-in universal analog input MOD 30ML
AOUT Built-in analog output MOD 30ML
VCIM Voltage or current input MOD 30ML and Modcell
TIM Thermocouple input MOD 30ML and Modcell
RIM 2 wire RTD / Resistance Input MOD 30ML and Modcell
WRIM 3 wire RTD / Resistance input MOD 30ML and Modcell
DIM Discrete input MOD 30ML and Modcell
Function Codes – Introduction
DOM Discrete output MOD 30ML and Modcell
DDOM Double Relay output MOD 30ML and Modcell
WDOM Form-C relay output MOD 30ML and Modcell
AOM Analog Output MOD 30ML and Modcell
ICN Instrument Communication Network (Peer-to-
MSC Modcell Serial Communication (RS232, Rs485
RIO Remote digital interface module MOD 30ML and Modcell
RDIM Remote digital input (extended digital inputs) MOD 30ML and Modcell
RDOM Remote digital output (extended digital outputs) MOD 30ML and Modcell
FUNCTION BLOCKS
There are three types of function blocks.
Process input function blocks configure input signal conditioning, engineering unit
conversion and linearization for inputs.
MOD 30ML and Modcell
peer)
MOD 30ML and Modcell
Modbus)
Algorithm function blocks define the user configured control functions on the
instrument.
Communication function blocks handle transfer of data between groups, as well as
transfer of data to the communication interfaces.
These are shown in the next table:
1 - 5
Command Series Migration to MOD 30ML
Function Codes – Introduction
Type Description Availability
Input Function Blocks or signal conditioning blocks:
VCI Voltage or current MOD 30ML and Modcell
TI Thermocouple input MOD 30ML and Modcell
RTI RTD input MOD 30ML and Modcell
TTI Thermocouple transmitter input MOD 30ML and Modcell
RTTI RTD Transmitter input MOD 30ML and Modcell
RI Resistance input MOD 30ML and Modcell
DI Digital input MOD 30ML and Modcell
Communication function blocks
ML Modbus List block MOD 30ML and Modcell
CL Configured list block (for both ICN and Modbus) MOD 30ML and Modcell
System function blocks:
TL Tuning List Only MOD 30ML
DISP Display block (one required for each display) Only MOD 30ML
LP Loop Block (one required for each loop
MOD 30ML and Modcell
compound)
Algorithm blocks
PID PID Control with Setpoint, A/M switching and
MOD 30ML and Modcell
tracking etc.
EX Expression block (multi-purpose configurable
MOD 30ML and Modcell
block for arithmetic, continuous and discrete
logic)
IC Input Communication (for incoming peer-to-peer
MOD 30ML and Modcell
communication)
OC Output Communication (for outgoing peer-to-
MOD 30ML and Modcell
peer communication)
1 - 6
LN Linearization MOD 30ML and Modcell
PW Piecewise and inverse piecewise table MOD 30ML and Modcell
PA Process Alarm MOD 30ML and Modcell
PAD Process Alarm Display Only MOD 30ML
Command Series Migration to MOD 30ML
Function Codes – Introduction
NM Notification Message MOD 30ML and Modcell
SM Supervisory Message MOD 30ML and Modcell
RSK Ramp – Soak Profile block MOD 30ML and Modcell
TOT Totalizer MOD 30ML and Modcell
TM Timer block MOD 30ML and Modcell
SEQ Sequencer MOD 30ML and Modcell
1 - 7
Command Series Migration to MOD 30ML
Function Codes – Introduction
A typical instrument database as function block diagram configured in ViZapp is shown in
the next figure: A typical instrument database has the environment blocks, I/O blocks,
communication blocks, and loop compounds.
Figure 1 .2.
Instrument
database
Algorithm function blocks are configured inside a loop compound to implement control
strategies. Each loop compound has a loop block (LP) by default.
The next figure shows function blocks inside a loop compound:
1 - 8
Figure 1 .3.
Function blocks
inside a loop
compound
Command Series Migration to MOD 30ML
Function Codes – Introduction
1 - 9
Command Series Migration to MOD 30ML
Function Codes – Introduction
FUNCTION BLOCK EXECUTION ORDER:
The order in which the blocks in the database are executed is known as the Function Block
execution order. The execution order is set at the top level where the loop compounds are
added to the database. The default execution order for the loop compounds is the order in
which they are placed in the database. The default execution order for the blocks inside the
loop compound is the order in which they are placed inside the loop compound.
The execution order of the loop compounds and the function blocks can be changed by the
user during the configuration process.
To view and change the execution order of function blocks in a database, select Objects –
Set Execution Order – List Mode from the menu bar in ViZapp. See the following
figure:
Figure 1 .4.
Function blocks
Execution Order
1 - 10
COMPOUNDS:
Function blocks in a database can be compounded (grouped) into a single group. This may
be done to functionally or visually organize the blocks in a database. Compounds can be
created at the top level or inside loop compounds. To compound a set of function blocks,
first select them and then select Objects – Compound from the ViZapp menu bar. When a
compound is made it creates a sub-level in the function block diagram and places the
blocks inside that level.
Figure 1 .5.
Open Compound
Command Series Migration to MOD 30ML
Function Codes – Introduction
The compound looks like a function block. See the above figure. To view the blocks,
select the compound and then right-click on the mouse to show a context sensitive menu
as shown in the above figure and then select Open – Compound.
If there were connections existing between the blocks that were compounded and other
blocks in the database, these connections are translated into jump objects inside the
compound.
1 - 11
Command Series Migration to MOD 30ML
Function Codes – Introduction
Figure 1 .6.
Inside a Compound
• You can ungroup a compound by un-compounding it. Select the compound by clicking on
Figure 1 .7.
Bailey FC Gallery
it and then select Objects from the menu bar and then select UnCompound from the
drop-down menu as shown in the next figure.
1 - 12
Command Series Migration to MOD 30ML
Function Codes – Introduction
• This will un-group the function blocks and place them where the grouped compound was.
When you uncompound a compound, the function blocks come out selected. You can
move all of them to a desired location by dragging them with the left mouse button
pressed.
a The advantage of uncompounding is that you can place the function blocks at the same
level as other function blocks you might already have at that level thereby making the
connections easier.
To connect to a compound from outside of it:
• Select the connector and select the attribute to connect from the desired block.
• Drag the line to the compound and click on it. See the figure below:
Figure 1 .8.
Right Angle
connection
• The Choose Parameter menu will be displayed as shown in the next figure:
Figure 1 .9.
Choose Parameter
• Select the desired jump object (if it was already present, for example PID.S1 in the above
figure) from the list and then click on OK.
1 - 13
Command Series Migration to MOD 30ML
Function Codes – Introduction
• You can also double-click on the Compound Internals and then select from the displayed
list of function blocks inside and then select the block and then the attribute to connect to.
• This will complete the connection for the process variable input. The connection will look
like in the next figure:
Figure 1 .10.
If you made a mistake while connecting, or if you do not know where to connect, you can
always cancel it or get out of the connection mode by clicking on the right mouse button
to show a menu as shown below:
• Select Cancel from this menu to cancel the connection.
Figure 1 .11.
Cancel Connection
1 - 14
LOOP COMPOUNDS
Loop compound is a special compound that contains a loop block. Loop compounds are
placed at the top level of a function block diagram (where the IF, DIF, SE and ST blocks
are located). All the function blocks other than Input, Output, Modules, Communication
and System blocks have to be configured inside a loop compound.
The loop block that is present inside the loop compound specifies the scan group at which
the blocks inside the loop compound get executed. See the next figure:
Figure 1 .12.
Cancel Connection
Command Series Migration to MOD 30ML
Function Codes – Introduction
The scan groups are configured in the Interface Block at the top level. There could be as
many as 5 different scan groups. The scan time is in multiples of 50 ms and can be as low
as 50 ms.
The next figure shows the Interface (IF) block configuration:
1 - 15
Command Series Migration to MOD 30ML
Function Codes – Introduction
Figure 1 .13.
Cancel Connection
Figure 1 .14.
Algorithms menu
To add a loop compound: Select the Loop Cpd (Loop compound) block from the
Algorithms window add it to the document. Do this by first locating the block in the menu
by selecting the All submenu at the bottom and then by dragging the scroll bar on the right
up/down. See the next figure:
1 - 16
• Drag the Loop Cpd block (Loop Compound) from the Algorithms menu on the left frame
to the right frame. Click on the Loop Cpd block with your left mouse button and then
drag it to the instrument document. Click on the mouse button to place the Loop
compound block with the other existing blocks (IF, SE, DIF and ST) on the right frame.
• Opening and closing of loop compound is exactly same as that of the compound explained
in the previous section.
Command Series Migration to MOD 30ML
Function Codes – Introduction
• Loop compounds also have jump objects when connections are made from or to the
outside of the compound.
• Refer to the previous section (COMPOUNDS) for more information.
1 - 17
Command Series Migration to MOD 30ML
Function Codes – Introduction
THE CONFIGURATION PROCESS
The steps involved configuring a MOD 30ML or Modcell controller are listed below:
1. Create a Workspace document in ViZapp
2. Create a Project document in ViZapp
3. Add a new instrument database for each controller to the project document.
4. Configure the instrument database in ViZapp.
5. Save and compile the instrument database
6. Configure the OPC Server (XModbus or ICN depending on which communication
protocol is used for connecting the controllers to the computer running ViZapp and
the OPC Server).
7. Add a device in the OPC Server for each controller that needs to be configured.
Communication settings for the device and the comm. Port should match that of the
instrument.
8. Download the compiled database from ViZapp using the OPC Server to the desired
instrument.
These steps are further explained in the next chapter and in the ViZapp training manual.
1 - 18
Command Series Migration to MOD 30ML
Function Codes – Introduction
Procedure for adding the Display Tag to the Display Interface Block
Each display configured in the MOD 30ML has a unique display tag.
• Open the display block by double-clicking on it. See the next figure:
Figure 1 .15.
PID Display
• As an example, the default display tag name configured in this compound is FIC-100.
During runtime, you can scroll through the displays in this list by pressing the Tag button
on the instrument.
Close the compound and the loop compound and go to the top level of the function block
diagram where the IF, DIF, ST, SE blocks and the loop compounds are located. See figure
below.
Start by opening the DIF (Display Interface) block as shown in the figure below:
1 - 19
Command Series Migration to MOD 30ML
Function Codes – Introduction
Figure 1 .16.
DIF block
Figure 1 .17.
DIF block
Click on the New button on this block as shown in figure below:
1 - 20
Command Series Migration to MOD 30ML
Function Codes – Introduction
A text edit box will appear in the area below and you will see a text edit cursor blinking.
Type the name of your display tag (FIC-100 for example).
a If you had more than one display blocks in your configuration, you will need to add
their display tags in the DIF block as explained in the above step. The order in which
the display tags appear in this list is the order in which the displays will scroll when
you press the Tag button on the instrument. The display block gets executed by the
instrument when it is loaded on the face of the instrument. If you did not add the
display tag of a display block to this list, that display will not appear on the instrument
when you press the Tag button.
Figure 1 .18.
DIF block
The Instrument tag field displays a unique tag name for the instrument. An instrument can
have multiple displays each with its own tag name. The instrument tag is useful in
identifying the instrument.
• Click on the OK button when you are done.
1 - 21
Command Series Migration to MOD 30ML
Function Codes – Introduction
PID CONFIGURATION REFERENCE
The PID block in the MOD 30ML/Modcell is versatile and extremely powerful. We will
focus only on the parameters that we would typically use in a CLC or SLC controller.
• Open the PID block by double-clicking on it. The General tab will be displayed by
default as shown below:
Figure 1 .19.
Bailey FC Gallery
1 - 22
• Change the values as desired for the parameters as shown in the figure above.
• Click on the Control tab of the PID block. This tab contains configurable parameters that
are associated with the control algorithm used in the MOD 30ML/Modcell. See the
following figure:
Loading...