Instruction Manual

ManualsBrandsMicromod ManualsEquipmentMOD: 1800P - MOD 30ML Identity Module (Version 2) System, I/O and Communications Functions

Logic Functions Data Base Reference

BOOK 1:

System, I/O and Communications Functions for

2001P - MODCELL™ Logic Control Identity Module (Version 6)

2004P - MODCELL™ Advanced Control Identity Module (Version 3)

1800P - MOD 30ML™ Identity Module (Version 2)

Summary of content (272 pages)

PAGE 1
Logic Functions Data Base Reference BOOK 1: System, I/O and Communications Functions for 2001P - MODCELL™ Logic Control Identity Module (Version 6) 2004P - MODCELL™ Advanced Control Identity Module (Version 3) 1800P - MOD 30ML™ Identity Module (Version 2)
PAGE 2
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.
PAGE 3
Logic Functions - Book 1 CONTENTS CONTENTS Page SECTION 1 - INTRODUCTION 1.1 GENERAL .......................................................................................................................................... 1-1 1.2 OVERVIEW OF INSTRUMENT SOFTWARE.................................................................................... 1-1 1.3 DATA BASE CONFIGURATION AND RUNTIME SUPPORT ........................................................... 1-1 1.4 RELATED DOCUMENTATION......................
PAGE 4
Logic Functions - Book 1 CONTENTS CONTENTS (Cont’d) Page 3.6 CONFIGURED LIST BLOCK (CL)................................................................................................... 3-49 3.6.1 Configured List Block Operation............................................................................................... 3-49 3.6.2 Configured List Block Parameters ............................................................................................ 3-50 3.6.
PAGE 5
Logic Functions - Book 1 CONTENTS CONTENTS (Cont’d) Page 5.5 ANALOG OUTPUT MODULE BLOCK (AOM) ................................................................................. 5-47 5.5.1 Analog Output Module Block Capabilities ................................................................................. 5-50 5.5.2 Analog Output Module Block Parameters ................................................................................. 5-51 5.5.3 Typical Block Connections for Analog Output Module Block ...
PAGE 6
Logic Functions - Book 1 CONTENTS CONTENTS (Cont’d) Page APPENDIX A - SUMMARY OF VERSION DIFFERENCES APPENDIX B - MODCELL MASTER CONFIGURATION B.1 OVERVIEW ....................................................................................................................................... B-1 B.2 MODCELL SERIAL COMMUNICATION (MSC) Block Modifications ................................................ B-2 B.3 Expression (EX) Block Modifications ...............................................................
PAGE 7
Logic Functions - Book 1 CONTENTS ILLUSTRATIONS Figure Page 2-1. Data Base Structure ................................................................................................................................. 2-2 3-1. Interface Block, Overview......................................................................................................................... 3-3 3-2. Interface Block (IF), Execution Menu ..............................................................................................
PAGE 8
Logic Functions - Book 1 CONTENTS ILLUSTRATIONS (Cont’d) Figure Page 5-23. Wide Resistance Input Module (WRIM), General Menu ...................................................................... 5-37 5-24. Wide Resistance Input Module (WRIM), Diagnostic Menu .................................................................. 5-37 5-25. Typical Block Connections for Analog Input Module Block .................................................................. 5-46 5-26.
PAGE 9
Logic Functions - Book 1 CONTENTS TABLES Table Page 2-. Data Types ................................................................................................................................................. 2-6 2-2. State Change Actions............................................................................................................................... 2-9 3-1. 3-2. 3-3. 3-4. 3-5. 3-6. Interface Block Attributes, Valid Values, Mnemonics, and Data Types ......................................
PAGE 10
Logic Functions - Book 1 CONTENTS viii
PAGE 11
Logic Functions - Book 1 INTRODUCTION 1 INTRODUCTION 1.1 GENERAL This document is the first of two books that includes database reference information for instruments with logic functionality. Also included is information on database organization and database memory block structure.
PAGE 12
Logic Functions - Book 1 INTRODUCTION Additional information about instrument installation can be found in: • IB-23C600 – Installation, MODCELL Multiloop Processor • IB-23C601 – Installation, Remote I/O Modules • IB-1800R-INS – Installation, MOD 30ML Multiloop Controller • IB-1800R-M30 – Installation, MOD 30ML Replacement for MOD 30 Additional MODBUS connection information can be found in the following: • IB-MODBUS-RTU – MODBUS™ RTU Communications Guide for use with MODCELL, MOD 30ML and Commander
PAGE 13
Logic Functions - Book 1 DATABASE DESCRIPTION 2 DATABASE DESCRIPTION 2.1 GENERAL This section describes the structures and global features that support the instrument database and it describes general instrument operation and how the database is protected. Understanding the basic elements that support database creation and operation is fundamental in knowing how the configuration will affect instrument performance.
PAGE 14
Logic Functions - Book 1 DATABASE DESCRIPTION * Loop Block #1 System Interface Block (IF1) Event Block (SE1) Function Block Execution Order Loop Block #n Main Block Execution Order Function Block Execution Order Loop Block #64 Function Block Execution Order * * * * * * * Configured List (CL) * * ICN MSC DIM DOM DDOM WDOM VCIM TIM I/O Module Block Selection (32 modules per MODCELL) CJIM RIM WRIM AOM RIO** = Any of the following function blocks: CL (Configured List) ML (Modbus List) DI (Dig
PAGE 15
Logic Functions - Book 1 DATABASE DESCRIPTION • Function blocks Process input function blocks configure an interface between the instrument’s process input module blocks and the control tasks. Algorithm function blocks define the user configured control functions on the instrument. These building blocks include expressions, linearization, notification messages, piecewise tables, process alarms, timers and sequencers.
PAGE 16
Logic Functions - Book 1 DATABASE DESCRIPTION The loop block specifies which of the scan rates, specified in the interface block, are used when executing the function blocks in the loop. All block groups having the same scan rate are implicitly grouped. Within a group, loop blocks, and the function blocks following each loop block, are executed in the order in which they are specified in the database. 2.2.3 Groups A group is a collection of one or more loops, which runs at a specified rate.
PAGE 17
Logic Functions - Book 1 DATABASE DESCRIPTION block is executed. However, if the input mode is configured to be manual, the initial data value will be retained until it is written over by an operator through the status display, or until input mode is changed to auto. If an input attribute is configured as NONE, then that attribute is not part of the database and cannot be read. 2.3.
PAGE 18
Logic Functions - Book 1 DATABASE DESCRIPTION 2.3.4 Data Types Function blocks in the instrument database consist of parameters that have data types as described in Table 2-1. Those data types with an asterisk are different in MOD 30 instruments. Table 2-1. Data Types Data Type Count (C) Bytes 2 Discrete (D) 1 Long State (L) Short State (S) 1 Date (DA) 3 Time 3 Millisecond Time * (M) 4 2-6 1 Range 0 to 65535 Remarks Count is an unsigned two-byte integer, with a value range of 0 to 65535.
PAGE 19
Logic Functions - Book 1 DATABASE DESCRIPTION Data Type Floating Point * (F) Logical Source Pointers * Bytes 4 Range ±1.18*E-35 to ±3.4*E38 4 (datab ase) 2 (ICN) ASCII * (A) n “any text” (for up to 126 bytes) Continuous 2 –204.8% to 204.8% Hex * (H) n MOD 30 Controller Modes 1 Remarks The floating-point data type is a four-byte data value in IEEE standard floating point format. A logical source pointer uniquely identifies an attribute in the database.
PAGE 20
Logic Functions - Book 1 DATABASE DESCRIPTION 2.4 GENERAL INSTRUMENT OPERATION 2.4.1 State Changes Instrument States The instrument may be in one of the following states: UPLOAD Instrument was powered up with memory module switch in the upload position and will do nothing beyond copying the main database (if it is ’complete’ and its checksums verify) into the memory module. POR Power up restart in process.
PAGE 21
Logic Functions - Book 1 DATABASE DESCRIPTION Table 2-2. State Change Actions Loop or Loop or Loop State Block State Block State (block trans.) Transition Transition or Block State From To (loop trans.) Action on Loop Transition or Block Transition Run Hold Run Hold Off Run Hold Debug Hold Run Debug Debug Debug Off Off Off Run or Hold Block Transitions: Change block state, report event. Loop Transitions: Change loop state, report event.
PAGE 22
Logic Functions - Book 1 DATABASE DESCRIPTION 2.4.2 Startup The instrument supports startup logic with configurable power-down/restart duration periods for warm and cold starts. The startup definitions are: WARM Instrument was down for less than a configurable amount of time. Timers, stack, PC, and so forth are reinitialized.
PAGE 23
Logic Functions - Book 1 DATABASE DESCRIPTION 2.4.4 LEDs The LEDs on the main board are handled as follows: 2.4.5 both off =No power. green off, red on =Initial Power-up condition, or Watchdog (not talking to I/O, default state, etc.). green on, red off =Normal; Running main database and talking to I/O. green on, red on =Any instrument state other than RUN (eg. HOLD, UPLOAD, etc.). If red LED stays on after power-up, fallback occurred and I/O goes into failsafe.
PAGE 24
Logic Functions - Book 1 DATABASE DESCRIPTION error is detected, a diagnostic event will be generated, and the instrument will go to a default state. Checksum boundaries are every 512 bytes (128 four-byte words). When a byte is written to memory, its address is shifted right 9 bits to produce the checksum boundary table index. A single database write typically involves more than one byte at a time. When multibyte writes cross checksum boundaries, the two checksum table entries are updated as required. 2.
PAGE 25
Logic Functions - Book 1 DATABASE DESCRIPTION If an instrument with a memory module shuts down (watchdogs for example) and cannot run again, the shut down information in the memory module can still be read. To do this, write protect the memory module, put the module on another instrument, and read the shutdown information using the STATUS display. Failure to write protect the memory module will cause the data to be written over by the instrument when it is powered up. 2.5.
PAGE 26
Logic Functions - Book 1 DATABASE DESCRIPTION 2.6 DATABASE REFERENCE CONVENTIONS Database reference information includes attribute definition, block capabilities, and examples of usage. The information is intended to aid the user in understanding and configuring the instrument database. Also included is information on database organization and memory block structures for users developing their own interface software. Explanations for each attribute are given in the order presented in the block data table.
PAGE 27
Logic Functions - Book 1 SYSTEM BLOCKS 3 SYSTEM DATABASE PARAMETERS 3.1 SYSTEM BLOCKS System blocks contain the overall instrument related information and functionality that does not logically fall within any loop or function block. These blocks exist through the System resource for instrument and loop Libraries. Only one interface and system event block is supported as part of the instrument configuration. These blocks are automatically made available with each instrument.
PAGE 28
Logic Functions - Book 1 SYSTEM BLOCKS The execution order of the system blocks may be indicated by a number that the block displays in its upper right corner. The system blocks in order are: the Interface block (IF1), the System Event block (SE1), the configured list blocks (CL10, CL11, etc.), the Modbus list blocks (ML1, ML2, etc.), and the loop blocks (LP1, LP2, etc.). Occurrence numbers are used in consecutive order (e.g., LP1, then LP2, then LP3 etc.).
PAGE 29
Logic Functions - Book 1 INTERFACE BLOCK 3.3 INTERFACE BLOCK (IF1) The interface block is an environment block that contains the overall instrument related information and functionality which does not logically fall within any loop or function block. This includes startup/shutdown conditions, current instrument state, group scan rates and measured execution times, clock and calendar, controlling source information for those blocks not run under a loop, instrument tag, power line frequency, and so forth.
PAGE 30
Logic Functions - Book 1 INTERFACE BLOCK Figure 3-2. Interface Block (IF), Execution Menu Figure 3-3.
PAGE 31
Logic Functions - Book 1 INTERFACE BLOCK Figure 3-4. Interface Block (IF), Diagnostic Menu 3.3.1 Interface Block Operation The execution rates for each group task are specified in the interface block, and are allowed to be some multiple of the base interval (50 ms). The interface block is along with the system event block at a 50 ms scan task rate. 3.3.
PAGE 32
Logic Functions - Book 1 INTERFACE BLOCK Table 3-1.
PAGE 33
Logic Functions - Book 1 INTERFACE BLOCK Table 3-1.
PAGE 34
Logic Functions - Book 1 INTERFACE BLOCK Table 3-1.
PAGE 35
Logic Functions - Book 1 INTERFACE BLOCK Table 3-1.
PAGE 36
Logic Functions - Book 1 INTERFACE BLOCK Table 3-1. Interface Block Attributes, Valid Values, Mnemonics, and Data Types (Cont’d) Field Name / Attribute Warm start duration Cold start duration Run on I/O mismatch Download on warm start Power Out Duration Startup Type Power Up Initialization Runtime Initialization Lock ICN comm.
PAGE 37
Logic Functions - Book 1 INTERFACE BLOCK Table 3-1. Interface Block Attributes, Valid Values, Mnemonics, and Data Types (Cont’d) Field Name / Attribute Scan1 Max. Execution Time Scan2 Max. Execution Time Scan3 Max. Execution Time Scan4 Max. Execution Time Scan5 Max. Execution Time Scan6 Max. Execution Time Scan7 Max. Execution Time Scan8 Max. Execution Time Scan9 Max.
PAGE 38
Logic Functions - Book 1 INTERFACE BLOCK 8 9 10 11 12 13 14 15 3-12 Instrument is Unconfigured Unacknowledged (MUCFGUAK) ......................................– WR The unacknowledged instrument is unconfigured error diagnostic indicates if the error is or is not acknowledged. The status can be read or acknowledged as follows: YES 1 Diagnostic error is unacknowledged. NO 0 Diagnostic error is acknowledged. Instrument is Unconfigured Active (MUCFGACT) ..........................................
PAGE 39
Logic Functions - Book 1 INTERFACE BLOCK 16 17 18 19 20 21 22 Memory Module Database Version Error Unacknowledged (MDVERUAK)................. – WR The unacknowledged “memory module database version error” diagnostic indicates if the error is or is not acknowledged. The status can be read or acknowledged as follows: YES 1 Diagnostic error is unacknowledged. NO 0 Diagnostic error is acknowledged. Memory Module Database Version Error Active (MDVERACT).....................................
PAGE 40
Logic Functions - Book 1 INTERFACE BLOCK 23 24 25 26 27 28 29 3-14 Memory module is soft write protected Active (MDSWPACT)...................................... – – R The write protect bit in the module RAM has been set by software. YES 1 “MEMORY MODULE IS SOFT WRITE PROTECTED” is active. NO 0 Diagnostic error is not active. Instrument is overconfigured (OVRUNSUP) ..................................................................
PAGE 41
Logic Functions - Book 1 INTERFACE BLOCK 30 31 32 33 34 35 36 Instrument powered down (PWRDNSUP) .......................................................................CWR The instrument powered down diagnostic checks if the instrument lost power. The diagnostic can be suppressed or enabled as follows: SUPPRESS 1 Diagnostic error is suppressed. ENABLE 0 Diagnostic error is enabled. Instrument powered down Unacknowledged (PWRDNUAK) .......................................
PAGE 42
Logic Functions - Book 1 INTERFACE BLOCK area in the battery backed up RAM and is examined through the configurator STATUS display activity. 37 38 39 40 41 42 3-16 YES 1 “INSTRUMENT SHUTDOWN FAULT” is active. NO 0 Diagnostic error is not active. Module Shutdown Fault Unacknowledged (MSHUTUAK) .............................................– WR The unacknowledged module shutdown fault diagnostic indicates if the condition is or is not acknowledged.
PAGE 43
Logic Functions - Book 1 INTERFACE BLOCK 43 44 45 46 47 48 49 EPROM Checksum Fault Unacknowledged (EPCHKUAK)............................................ – WR The unacknowledged EPROM checksum fault diagnostic indicates if the condition is or is not acknowledged. The status can be read or acknowledged as follows: YES 1 Diagnostic error is unacknowledged. NO 0 Diagnostic error is acknowledged. EPROM Checksum Fault Active (EPCHKACT)................................................................
PAGE 44
Logic Functions - Book 1 INTERFACE BLOCK 95 96 97 98 99 100 101 102 3-18 Bad Clock Chip Unacknowledged (BDCLKUAK) ............................................................– WR The unacknowledged bad clock chip diagnostic indicates if the condition is or is not acknowledged. The status can be read or acknowledged as follows: YES 1 Diagnostic error is unacknowledged. NO 0 Diagnostic error is acknowledged. Bad Clock Chip Active (BDCLKACT) .....................................................
PAGE 45
Logic Functions - Book 1 INTERFACE BLOCK 103 104 105 Communication Blocks are Locked Active (CMLOKACT) .............................................– – R The communications blocks locked active is set when Attribute 158, Lock ICN Communications Blocks? (COMMLOCK) is YES. YES 1 “COMMUNICATION BLOCKS ARE LOCKED” is active. NO 0 Diagnostic error is not active. DMA Unacknowledged (DMAUAK) ..................................................................................
PAGE 46
Logic Functions - Book 1 INTERFACE BLOCK 110 111 112 113 114 3-20 Communication Hardware Fault Active (CMHWFACT) ................................................. – – R When a communication module is inserted in slots 9 and 10 of a MOD 30ML (1800R) and the built-in communication jumpers are set, a conflict of resources occurs since both require use of communication port 1. The instrument will be placed in the DEFAULT state.
PAGE 47
Logic Functions - Book 1 INTERFACE BLOCK End of Diagnostic Attributes 126 Base Scan Time (SCANTIME) ...........................................................................................– – R Average milliseconds of processor time between base scan ticks (00:00:00.050, unless overconfigured). 127 Scan Idle Time (IDLETIME) ...............................................................................................– – R Average milliseconds of unused processor time between base scan ticks.
PAGE 48
Logic Functions - Book 1 INTERFACE BLOCK Basic Configuration Attributes 134 Power Line Frequency (FREQ) ........................................................................................C – R Power Line Frequency is used by certain I/O modules for proper noise rejection. The valid values are: 50 0 The frequency of the ac input power to the instrument is 50 hertz. 60 1 The frequency of the ac input power to the instrument is 60 hertz. 135 User Tag (USRTAG) ......................................
PAGE 49
Logic Functions - Book 1 INTERFACE BLOCK 140 Next Instrument State (NXTISTAT) ................................................................................ – W R Under steady state conditions, next instrument state will be equal to instrument state. Writing to it constitutes a command to go to a new state. Be aware that changing the instrument state from RUN to DEFAULT or BEING CONFIGURED causes the instrument to stop sending foreground data and communications will be lost to any runtime front end.
PAGE 50
Logic Functions - Book 1 INTERFACE BLOCK 144 Calendar Date (DATE) .......................................................................................................– WR A three byte value where the first byte is the calendar year (0 to 99), the second is the calendar month (1 to 12) where 1 = January and 12 = December, and the third is the calendar day (1 to 31). Note that years 90 to 99 are assumed to be 1990 to 1999. 145 Calendar Date Quality (DATEQ)...............................................
PAGE 51
Logic Functions - Book 1 INTERFACE BLOCK NO 153 0 The instrument does stop in HOLD when an i/o mismatch is detected in attempting to go to RUN. Download on warm start (DNLDWARM) ..........................................................................CWR YES 1 The instrument will download from the (present and otherwise valid) memory module on a warm, cold or frozen start. NO 0 The instrument will download only on a cold or frozen start.
PAGE 52
Logic Functions - Book 1 INTERFACE BLOCK 3-26 164 Scan 6 Interval (INT6)........................................................................................................ – – R The Interface and System Event Block scan group interval is set at 50 milliseconds. This task manages instrument states, services diagnostics and the event queue, services the I/O, and provides self checking (checksums). 165 166 167 Scan 7 Interval (INT7).....................................................................
PAGE 53
Logic Functions - Book 1 INTERFACE BLOCK 196 Run completion cycles (RCCYCLES) ..............................................................................CWR When leaving the RUN state, the instrument will wait up to ‘run completion cycles’ executions (1 to 125) of the slowest user task for the run complete input to go TRUE. At that time it will leave the run state regardless of the run complete input value. 197 Run complete input (RUNCMPLT) ............................................................
PAGE 54
Logic Functions - Book 1 INTERFACE BLOCK 13 INSTRUMENT IS OVERCONFIGURED (26) 14 INSTRUMENT POWERED UP (29) 15 INSTRUMENT POWERED DOWN (32) 16 COMMUNICATIONS PORT MISMATCH (34) 17 INSTRUMENT SHUTDOWN FAULT (36) 18 MODULE SHUTDOWN FAULT (38) 19 PROCESSOR WATCHDOG FAULT (40) 20 SPURIOUS EVENT FAULT (42) 21 EPROM CHECKSUM FAULT (44) 22 BAD RAM FAULT (46) 23 I/O BOARD 1 COMMUNICATIONS ERROR (49) 24 through 38 reserved 39 BAD CLOCK CHIP (96) 40 TIME AND DATE NOT VALID (99) 41 I/O IS LOCKED (101) 42 COMMUNICATIO
PAGE 55
Logic Functions - Book 1 SYSTEM EVENT BLOCK 3.4 SYSTEM EVENT BLOCK (SE1) The system event block is an environment block that supports general instrument operation. One system event block is supported as part of the instrument configuration to define diagnostic and system event acknowledgement and reporting capabilities. System events are events that occur in the instrument, are reported by database blocks, and can be stored into the system event queue.
PAGE 56
Logic Functions - Book 1 SYSTEM EVENT BLOCK Figure 3-7. System Event Block (SE), General Menu Figure 3-8.
PAGE 57
Logic Functions - Book 1 SYSTEM EVENT BLOCK Figure 3-9. System Event Block (SE), Alarms Menu 3.4.1 System Event Block Operation System events are handled in the following way: • When an event is generated, an entry corresponding to that event is stored in the circular buffer (the size of this system event queue is configurable), and the queue entry ID (QID) attribute in the system event block is incremented.
PAGE 58
Logic Functions - Book 1 SYSTEM EVENT BLOCK • Example of events displayed by a user’s display (PC-30 device tag and header shown for example only): HH:MM:SS.mmm TAGxxxxx DDOM125 Remaining message = 47 characters total TIME 10:05:44.055 10:05:53.150 11:23:04.755 11:23:12.410 11:24:49.237 11:24:50.345 15:03:25.673 15:03:25.725 15:03:25.763 15:04:02.086 15:04:02.130 15:05:02.185 15:05:02.238 15:08:15.758 15:08:15.809 15:08:15.
PAGE 59
Logic Functions - Book 1 SYSTEM EVENT BLOCK Table 3-2. System Event Block Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length State Bad Inputs All Groups Diag. Supp. Group 1 Diag. Suppression Group 2 Diag. Suppression Group 3 Diag. Suppression Group 4 Diag. Suppression Group 5 Diag. Suppression Group 6 Diag. Suppression Group 7 Diag.
PAGE 60
Logic Functions - Book 1 SYSTEM EVENT BLOCK Table 3-2. System Event Block Attributes, Valid Values, Mnemonics, and Data Types (Cont’d) Field Name / Attribute General Event Reporting Informational Events Block ‘State’ Chngs. Process Alarm Events Notification Mesg Events System Event Events Global Acknowledge Cmd Diagnostic Ack. Cmd Process Alarm Ack. Cmd Notif/Req Msg Ack. Cmd Clear Queue Command Any Active Diagnostics Any Unacked Diagnostics Number of Active Diags. Number of Unacked Diags.
PAGE 61
Logic Functions - Book 1 SYSTEM EVENT BLOCK 04 05 06 07 08 09 10 11 12 13 14 15 ALL Groups Diagnostic Suppression (SUPALL)......................................................CWR Group 1 Diagnostic Suppression (SUPGP1) ............................................................CWR Group 2 Diagnostic Suppression (SUPGP2) ............................................................CWR Group 3 Diagnostic Suppression (SUPGP3) ............................................................
PAGE 62
Logic Functions - Book 1 SYSTEM EVENT BLOCK 16 17 18 19 20 21 22 3-36 Report Diagnostic Event: Diag goes clear while unacked (RDGCWU)..................CWR Used to enable the reporting of the event. YES 1 Report when a diagnostic event goes clear while it is still unacknowledged to the system event queue. NO 0 No reports are made. Report Diagnostic Event: Goes clear while acked (RDGCWA) ..............................CWR Used to enable the reporting of the event.
PAGE 63
Logic Functions - Book 1 SYSTEM EVENT BLOCK 23 24 25 26 27 28 29 Report Diagnostic Event: Enabled (RDGENA) .........................................................CWR Used to enable the reporting of the event. YES 1 Report when a diagnostic event suppression attribute is set to NO to the system event queue. NO 0 No reports are made. Report Alarm Event: Goes active and unacked (RALAU) .......................................CWR Used to enable the reporting of the event.
PAGE 64
Logic Functions - Book 1 SYSTEM EVENT BLOCK 30 31 32 33 34 35 36 3-38 Report Alarm Event: Acknowledged (RALACK) .......................................................CWR Used to enable the reporting of the event. YES 1 Report when a PA or NM alarm is acknowledged by a single acknowledge message to the system event queue. NO 0 No reports are made. Report Alarm Event: Globally acknowledged (RALGLACK) ...................................CWR Used to enable the reporting of the event.
PAGE 65
Logic Functions - Book 1 SYSTEM EVENT BLOCK 37 38 39 Report Process Alarm Events (RPTPA) ....................................................................CWR Used to enable reporting of Process Alarm events. YES 1 Report process alarm events to the event queue. NO 0 No event reporting is made for ALL Process Alarms in the database. Report Notification Message Events (RPTNM) ........................................................
PAGE 66
Logic Functions - Book 1 SYSTEM EVENT BLOCK 47 Number of Active Diagnostics (NUMACT) ................................................................– – R A count output indicating the number of currently active diagnostic errors. This value is incremented for each new alarm/clear alarm type diagnostic which becomes active, and is decremented every time this type of diagnostic clears.
PAGE 67
Logic Functions - Book 1 SYSTEM EVENT BLOCK Global Acknowledge Input (GLBINP) ....................................................................... C – R Diagnostic Acknowledge Input (DGINP).................................................................. C – R Process Alarm Acknowledge Input (PAINP)............................................................ C – R Notification/Requests Message Acknowledge Input (NMINP)...............................
PAGE 68
Logic Functions - Book 1 SYSTEM EVENT BLOCK 19 20 21 22 23 24 GROUP 5 DIAGNOSTICS ENABLED GROUP 6 DIAGNOSTICS SUPPRESSED GROUP 6 DIAGNOSTICS ENABLED GROUP 7 DIAGNOSTICS SUPPRESSED GROUP 7 DIAGNOSTICS ENABLED SYSTEM EVENT QUEUE CLEARED 3.4.5 Event Transitions Events have transition codes (internal to communications) and text associated with them. Table 3-3 lists the event transition codes and descriptions. These transition codes apply to all events for all blocks. Table 3-3.
PAGE 69
Logic Functions - Book 1 LOOP BLOCK 3.5 LOOP BLOCK (LP) The loop block is an environment block that provides a ’master control’ function for those function blocks found between it and the next loop block in the user database. This includes ’controlling source’ write access for consoles and computers and group control of function block execution by either database logic or operator/computer command. See Section 2.2.2 for a further description of loops.
PAGE 70
Logic Functions - Book 1 LOOP BLOCK Figure 3-12. Loop Block (LP), General Menu Figure 3-13.
PAGE 71
Logic Functions - Book 1 LOOP BLOCK 3.5.1 Loop Block Operation The actual behavior of the loop block is indicated by composite state, which is a composite of state and remote state. The loop’s function blocks only get executed if composite state is RUN. When state is RUN, composite state is equal to the remote state input, if present and valid. When state is not RUN, composite state is equal to state and remote state is ignored.
PAGE 72
Logic Functions - Book 1 LOOP BLOCK Remote state error Active quality State value to use when remote state error occurs Scan Group Composite State RSTAQ REST RUN(0), HOLD(1), OFF(2), DEBUG(3) GROUP 1, 2, 3, 4, 5 CSTATE RUN(0), HOLD(1), OFF(2), DEBUG(3) CNSTATUS FREE (0), BUSY (1) CPSTATUS FREE, BUSY, INACTIVE(2) RSTATE NONE, RUN, HOLD, OFF, DEBUG, or LSP (discrete, short or long state) Console Status Computer Status Remote State Input 2 3 GOOD (0) ––R Discrete 09 CWR Short State 10 C–R ––R Sh
PAGE 73
Logic Functions - Book 1 LOOP BLOCK 7 Remote state error unack quality (RSTUQ) ....................................................................– – R The remote state error unacknowledged always has good quality. GOOD 8 9 Quality is always good. Remote state error Active (RSTA)...................................................................................
PAGE 74
Logic Functions - Book 1 LOOP BLOCK Remote State Input (RSTATE).......................................................................................... CWR This is an input signal used to remotely change the block state. When state is RUN and remote state is present, composite state (CSTATE) will take on the value of remote state. Writable only if local data is configured. 15 3.5.3 NONE No remote state changes allowed. Composite state is the state value.
PAGE 75
Logic Functions - Book 1 CONFIGURED LIST BLOCK 3.6 CONFIGURED LIST BLOCK (CL) The configured list block is used to specify and/or collect data (up to 99 attributes or other configured lists) that is of interest to an external system. The configured list data is included in: an ICN or MSC foreground message; or as a Modbus list (no nested lists) for a MSC module; or solely as a background list to be included in interface files (TIF or MIF).
PAGE 76
Logic Functions - Book 1 CONFIGURED LIST BLOCK this block. When the list data is demanded from this block, it will demand data from the other block in the appropriate sequence. Configured list data is defined as foreground in the ICN and MSC blocks (Foreground List attribute). All lists are made part of the Tagged Interface File (TIF) or a comma delimited text Modcell Interface File (MIF).
PAGE 77
Logic Functions - Book 1 CONFIGURED LIST BLOCK 00 Version (VERSION)............................................................................................................– – R Attributes 8, 9 and 10 were added for version 2 of this block. 01 Block Length (BLKLEN).....................................................................................................– – R Number of data base bytes taken by the block. 02 State (STATE).....................................................................
PAGE 78
Logic Functions - Book 1 CONFIGURED LIST BLOCK 3.6.3 Typical Block Connections for Configured List Block Typical softwiring block structures used to connect a Configured List block are shown in Figure 3-16. Connect foreground list data of a Configured List block to the FGLISTIN attribute of the ICN or MSC block to specify foreground data (data updated every 0.25 seconds in the link).
PAGE 79
Logic Functions - Book 1 MODBUS LIST BLOCK 3.7 MODBUS LIST BLOCK (ML) The Modbus list block is used to specify and collect data, which is of interest to an external system that, supports the Modbus message protocol. The list of attributes identifying data for inclusion in Modbus Slave Communication block (MSC) single register read/write or single register read only lists must be specified in Modbus List (ML) blocks.
PAGE 80
Logic Functions - Book 1 MODBUS LIST BLOCK Millisecond Time Modbus Register Value 0 0 100 10 10000 1000 100000 10000 600000 60000 655350 65535 >655350 65535 Remarks 10 minutes worth out of range indication out of range indication The display that is used to configure the Modbus list block is shown in Figure 3-17. Up to 99 attributes can be defined through the configurator for one Modbus list block. Figure 3-17. Modbus List Block (ML), Edit Display, page 2 3.7.
PAGE 81
Logic Functions - Book 1 MODBUS LIST BLOCK 3.7.2 Modbus List Block Parameters The mnemonics, valid values, and data types for all fields that may be selected for display and/or be used in making softwiring connections are listed in Table 3-6. The following further defines the Modbus list block configuration parameters. Block Type ML This is the Modbus list block type. Table 3-6.
PAGE 82
Logic Functions - Book 1 MODBUS LIST BLOCK 3.7.3 Typical Block Connections for Modbus List Block Typical softwiring block structures used to connect a Modbus List block are shown in Figure 318. ML1 DI1 Result LISTOUT R Input 1 Input 2 LN1 Result R ML2 LISTOUT Figure 3-18.
PAGE 83
Logic Functions - Book 1 COMMUNICATION MODULE BLOCKS 4 COMMUNICATION MODULE DATABASE PARAMETERS 4.1 COMMUNICATION BLOCKS Communication module blocks define a physical interface port and are not part of a loop scan group. The ICN and MSC communication module blocks are available outside of loop compounds only and are placed somewhere at the instrument level. One of these modules is required to talk to other devices on the network.
PAGE 84
Logic Functions - Book 1 COMMUNICATION MODULE BLOCKS The baud rate, data bits, parity, and stop bits that match the device with which you are communicating can be: Comm Link Baud Type ICN Modbus 1720N 19200, 9600, 4800, 2400, 1200 1731N 19200, 9600 1733N 19200, 9600, 4800, 2400, 1200, 600, 300 None 38400,19200, 9600, 4800, 2400, 1200, 600, 300,150 Data Stop Bits Bits 8 1, 2 8 8 1 1 8 1,2 Parity None, Even, Odd None None None, Even, Odd For the ICN module, these parameters are set at the
PAGE 85
Logic Functions - Book 1 ICN COMMUNICATION BLOCK 4.2 ICN COMMUNICATION BLOCK (ICN) The ICN communication block is used to receive messages from other instruments on the ICN, transmit responses to the processed messages and also transmit foreground data as specified by the list designated by the user. The received messages, which pass validity checks, are then either processed (eg. READ messages) or routed (eg. WRITE messages) to the appropriate group for processing when that group becomes available.
PAGE 86
Logic Functions - Book 1 LOOP BLOCK Figure 4-2. ICN Communication Block (ICN), General Menu Figure 4-3.
PAGE 87
Logic Functions - Book 1 ICN COMMUNICATION BLOCK Figure 4-4.
PAGE 88
Logic Functions - Book 1 LOOP BLOCK 4.2.1 ICN Communication Block Capabilities The ICN communication block is responsible for two main functions. The first is to handle all messages received since its last execution. The second is to handle the reporting and acknowledgment of diagnostics for the configured port. The ICN Block executes once every 50 msec. Messages received by the port driver are checked for proper reception and definition.
PAGE 89
Logic Functions - Book 1 ICN COMMUNICATION BLOCK Table 4-1.
PAGE 90
Logic Functions - Book 1 LOOP BLOCK Table 4-1. ICN Communication Block Attributes, Valid Values, Mnemonics, and Data Types (Cont’d) Field Name / Attribute Bus Restart Counter Restart Failure Counter Invalid Message Counter Check-Sum Error Counter Framing Error Counter Noise Error Counter Overrun Error Counter Invalid msg. Length Counter Receive Buffer Full Counter Xmit. Buffer Full Counter Unexp. Comm. Msg. Counter ICN Overload Counter Req.
PAGE 91
Logic Functions - Book 1 ICN COMMUNICATION BLOCK 05 06 07 08 09 10 Module missing or invalid (MODMMS) ............................................................................CWR This diagnostic compares each slot configured for an ICN communications module against the content of the slot during a power-up or database download. If the slot is empty or the installed module does not match the configuration, this diagnostic is generated. SUPPRESS 1 Diagnostic error is suppressed.
PAGE 92
Logic Functions - Book 1 LOOP BLOCK 11 12 13 14 15 16 4-10 Restart Failure Unacked (FAILU) .....................................................................................– WR If the restart failure diagnostic is enabled, this status indicates if the diagnostic is or is not unacknowledged. The status can be acknowledged or read as follows. NO 0 Diagnostic error is acknowledged. YES 1 Diagnostic error is unacknowledged. Invalid message (MSGS) ...............................................
PAGE 93
Logic Functions - Book 1 ICN COMMUNICATION BLOCK 17 18 19 20 21 22 Framing Error Unacked (FRAMEU) ................................................................................. – WR If the framing error diagnostic is enabled, this status indicates if the diagnostic is or is not unacknowledged. The status can be acknowledged or read as follows. NO 0 Diagnostic error is acknowledged. YES 1 Diagnostic error is unacknowledged. Noise error (NOISES) ................................................
PAGE 94
Logic Functions - Book 1 LOOP BLOCK 23 24 25 26 27 4-12 Invalid msg. Length Unacked (LENU) .............................................................................– WR If the invalid message size diagnostic is enabled, this status indicates if the diagnostic is or is not unacknowledged. The status can be acknowledged or read as follows. NO 0 Diagnostic error is acknowledged. YES 1 Diagnostic error is unacknowledged. Too many messages received for port (RFULLS) .............................
PAGE 95
Logic Functions - Book 1 ICN COMMUNICATION BLOCK 28 29 30 31 32 Message received for unconfigured IC block (UCOMMS) .............................................CWR This diagnostic checks if the occurrence for which an input communications message was received is in the current configuration. SUPPRESS 1 Diagnostic error is suppressed. clear. Acknowledgement status remains ENABLE 0 Diagnostic error is not suppressed and errors are reported to the System Event block.
PAGE 96
Logic Functions - Book 1 LOOP BLOCK 33 Req. Buffer Full Unacked (QFULLU)................................................................................– WR If the too many messages received for scan group diagnostic is enabled, this status indicates if the diagnostic is or is not unacknowledged. The status can be acknowledged or read as follows. NO 0 Diagnostic error is acknowledged. YES 1 Diagnostic error is unacknowledged. 34 35 36 37 38 39 40 41 42 43 44 45 46 Bus Restart Counter (RSTC)........
PAGE 97
Logic Functions - Book 1 ICN COMMUNICATION BLOCK 51 I/O Module Mismatch (MODMM).......................................................................................– – R If the module missing or invalid diagnostic is suppressed, this status indicates if the diagnostic is or is not active (unsuppressed form of I/O module mismatch active). The unsuppressed mismatch condition is used to determine if there is an active mismatch condition when switching the diagnostic from suppressed to enable.
PAGE 98
Logic Functions - Book 1 LOOP BLOCK 4.2.3 Typical Block Connections for ICN Communication Block Typical softwiring block structures used on softwiring diagrams are shown in Figure 4-5. Special configuration connection. CL10 INPUT1 INPUT99 ICN1 LISTOUT FGLISTIN ICN Load FG LOAD Operator indication of Condition selected list and ICN load Operator writeable attribute. Figure 4-5. ICN Communication Block, Typical Connections 4.2.
PAGE 99
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 4.3 MODCELL SERIAL COMMUNICATION BLOCK (MSC) The Modcell Serial communication (MSC) block supports Modbus Slave, Extended Modbus Slave or Modbus Master communications over either a point-to-point or point-to-multipoint network. This block supports the Modbus Remote Terminal Unit (RTU) mode of transmission. The ASCII mode is not supported. A functional block diagram of the block is shown in Figure 4-6.
PAGE 100
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK FG PORTFUNC WRACT WRTIMOUT RS232 or RS485 Modules 1 2 Receive Buffer and Message Checker Transmit Buffer I/O Selection Messages Router Group Processors Modbus Lists SRWLIST 1-5 SROLIST 1-5 (NONE, ML#) Configured Lists DRWLIST 1-5 DROLIST 1-5 MRWLIST 1-5 MROLIST 1-5 (NONE, CL#) USEDEF Board Number Slot Number ADDR TARADDR Error Checks BAUDRATE DATABITS MODE PARITY STOPBITS MODMM COMMTYPE Suppress Diagnostic Errors Diagnostic G
PAGE 101
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK Figure 4-7. Modcell Serial Communication (MSC), Edit Block Display, Page 1 Figure 4-8.
PAGE 102
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 4.3.1 Modcell Serial Communication Block Modbus Slave Capabilities The MSC block is responsible for reading and writing instrument attributes. The MSC block executes once every 50 milliseconds.
PAGE 103
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK Function Code 05 Description Write one discrete point Maximum Values to Read/Write 1 attribute 06 Write one register 1 attribute 08 Loopback diagnostic test (only "Return of query" supported). 15 Write multiple discretes 16 attributes 16 Write multiple registers 16 attributes Modbus data types are bit (discrete) and word (count, 16 bit positive value). One Count occupies one register.
PAGE 104
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 4.3.2 Modcell Serial Communication Block Parameters The mnemonics, valid values, and data types for all fields that may be selected for display and/or be used in making softwiring connections are listed in Table 4-2. The following further defines the MSC block configuration parameters. Block Type MSC This is the Modcell Serial Communication Block type.
PAGE 105
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK Table 4-2. Modcell Serial Communication Block Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length State Bad Inputs Accepted Diagnostic Group Module missing or invalid Module Missing Unacked Module Missing Active Message Check Error Msg.
PAGE 106
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK Table 4-2.
PAGE 107
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK Table 4-2. Modcell Serial Communication Block Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Mnemonic Valid Values CWR Data Type Attr COMMTYPE RS232 (0), C – R Short State 80 ModuleType RS485 1 slot 2 wire (1) RS232 with Address (5) RS485 with Address (6) – WR Long State 81 Command CMD Reset Diag.
PAGE 108
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 08 09 10 11 12 13 4-26 Message Check Error (MSGCHKS).................................................................................. CWR This diagnostic checks if a received message can be processed by doing a Cyclical Redundancy Check (CRC). ENABLE 0 Diagnostic error is not suppressed and errors are reported to the System Event block. The error message is reported as “MESSAGE CHECK ERROR.
PAGE 109
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 14 15 16 17 18 19 Framing error (FRAMES)...................................................................................................CWR This diagnostic checks if a stop bit is received for a byte as detected by the 68032. ENABLE 0 Diagnostic error is not suppressed and errors are reported to the System Event block. The error message is reported as “FRAMING ERROR.” This indicates no stop bit detected by the 68032 for a received byte.
PAGE 110
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 20 21 22 23 24 25 4-28 Invalid message error (INVMSGS) .................................................................................. CWR This diagnostic checks if the message length and size of a received message are valid or if a global message is used correctly. ENABLE 0 Diagnostic error is not suppressed and errors are reported to the System Event block. The error message is reported as “INVALID MESSAGE.
PAGE 111
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 26 27 28 30 Default comm switch set (DEFCOMMS)..........................................................................CWR This diagnostic checks if the default communication switch is set (yes) on the RS-232 or RS485 module. ENABLE 0 Diagnostic error is not suppressed and errors are reported to the System Event block. The error message is reported as “DEFAULT COMM SWITCH SET.
PAGE 112
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 41 Scan Buffer Full Counter (QFULLC) ..............................................................................– WR Each of the above diagnostics has a counter which is a free running count (0 to 65535) of the quantity of errors detected. The count is active even if the diagnostic is suppressed. 44 Mode (MODE).....................................................................................................................
PAGE 113
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 50-54 55-59 60-64 65-69 Discrete Read/Write List 1 - 5 (DRWLISTn) ................................................................... C – R These values represent configured lists which make up the discrete read/write lists (1 through 5) for this Modbus port.
PAGE 114
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 70-74 74-79 Multiple Register Read/Write List 1 - 5 (MRWLISTn).....................................................C – R These values represent configured lists which make up the multiple read/write register for the lists (1 through 5) for this Modbus port.
PAGE 115
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 82 Reset Counters (RESET).................................................................................................. – WR The reset counters command will always read as NO. When YES is written, all diagnostic counters will be set to zero (0). 83 Port Functionality (PORTFUNC) ......................................................................................CWR Value indicates if the port is functioning as a slave or a master.
PAGE 116
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 87 88 Write Message Action (WRACT) ...................................................................................... CWR This value indicates the action that will be taken if a message times out. NO 0 Discard message and return NAK code “TIME EXPIRED MSG DISCARDED” YES 1 Return NAK code “TIME EXPIRED MSG PROCESSED”. The message will be processed when it can but it may or may not be accepted. Foreground List (FG) ......................
PAGE 117
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 4.3.3 Typical Block Connections for Modcell Communication Block Typical softwiring block structures used to connect an MSC block are shown in Figure 4-9. MSC1 ML1 LISTOUT Operator indication of data. SROIN1 SRWIN1 ML2 Command LISTOUT INPUT1 CL10 MSC1 LISTOUT FGLISTIN Operator indication of data. BGLISTIN CL12 Command LISTOUT INPUT1 Figure 4-9. Modcell Serial Communication Block, Typical Block Connections 4.3.
PAGE 118
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK 4.3.5 Using the Modcell Serial Communication Block A Modbus Reference File, similar to the following file, is created for each MSC block that exists in the database. Notice that an entry of NONE within a list block uses one register location (point) and that some data types in the Multiple Register Read/Write and Read only lists use more than one register location.
PAGE 119
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK Occurrence number of the Modbus list specified in the MSC Edit Block Display (page 2) for Single Register Read/Write Memory, List 1. Occurrence number of the Modbus list specified in the MSC Edit Block Display (page 2) for Single Register Read Only Memory, List 1.
PAGE 120
Logic Functions - Book 1 MODCELL SERIAL COMMUNICATION BLOCK Occurrence number of the configured list specified in the MSC Edit Block Display (page 3) for Multiple Register Read/Write Memory, List 1. Some data types use more than one register location. ASCII and Hex data can use any number of registers depending on their field size. Occurrence number of the configured list specified in the MSC Edit Block Display (page 3) for Multiple Register Read Only Memory, List 1.
PAGE 121
Logic Functions - Book 1 INPUT/OUTPUT MODULE BLOCKS 5 INPUT/OUTPUT MODULE DATABASE PARAMETERS 5.1 INPUT/OUTPUT MODULE BLOCKS Input/Output module blocks define a physical input or output connection point and are not part of a loop scan group. The I/O module blocks are available inside or outside of loop compounds. One of these modules is required to get a field signal into the instrument. Local I/O modules are selected from the Input/Output Library at the instrument or loop level.
PAGE 122
Logic Functions - Book 1 INPUT/OUTPUT MODULE BLOCKS AOM Analog Output Module. Reference Section 5.5. This block has a floating pt. attribute INPUT link for the following module. 2003A Current Output In general, a digital or analog input or output module may be used in any location. However, wiring considerations and power considerations, as described in the appropriate installation book, may require separation of signal types into specific locations.
PAGE 123
Logic Functions - Book 1 DIGITAL INPUT MODULE BLOCK (DIM) 5.2 DIGITAL INPUT MODULE BLOCK (DIM) The digital input module block serves as the data handling block for the digital input module. A digital input module conditions a field signal and processes the signal through an on-board select circuit which passes all digital data between the modules and the module blocks at the base scan rate of 50 milliseconds. Input filtering and power-up conditions are determined by the digital input function block (DI).
PAGE 124
Logic Functions - Book 1 DIGITAL INPUT MODULE BLOCK (DIM) Figure 5-3. Digital Input Module (DIM), General Menu Figure 5-4.
PAGE 125
Logic Functions - Book 1 DIGITAL INPUT MODULE BLOCK (DIM) 5.2.1 Digital Input Module Block Operation The Digital Input Module block is a data repository for the instrument. One module block services one module and as many other digital input function blocks as required can be connected. All digital inputs are buffered in one of five possible task state tables.
PAGE 126
Logic Functions - Book 1 DIGITAL INPUT MODULE BLOCK (DIM) 5.2.2 Digital Input Module Block Parameters The mnemonics, valid values, and data types for all fields that may be selected for display and/or be used in making softwiring connections are listed in Table 5-1. The following further defines the Digital Input/Output Module Block configuration parameters. Block Type DIM This is the Digital Input Module Block type. Occurrence 1 to 32 There may be up to 32 ‘instances’ allowed of the DIM block type.
PAGE 127
Logic Functions - Book 1 DIGITAL INPUT MODULE BLOCK (DIM) 05 06 07 08 I/O Mismatch (MODMMS) ..................................................................................................CWR The I/O mismatch diagnostic compares each slot configured for a digital input module against the contents of the slot during a power-up or database download. If the slot contains an intelligent module (analog input, analog output, ICN, MSC or RIO), this diagnostic is generated.
PAGE 128
Logic Functions - Book 1 DIGITAL INPUT MODULE BLOCK (DIM) Mode (MODE)..................................................................................................................... CWR The mode of the block is determined by configuring and/or writing this attribute. Changing mode is an informational event. 11 AUTO 1 The block input is processed using the input module data. MAN 0 The block input is the manual data form of the result. 12 Field Result (FR) ......................................
PAGE 129
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) 5.3 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) Digital output module blocks serve as the data handling blocks for the digital output modules. The output module blocks have their data processed through an on-board select circuit that passes all digital data between the module blocks and the modules at the base scan rate of 50 milliseconds.
PAGE 130
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) Bad PART 1 Track Not Run Manual I/O Lock (from IF Block) FALSE Track Status OR Lock Instrument State (from IF Block) Mode GOOD Input TRUE Unlock LSP Auto BAD Normal Lock Bad Inputs Accepted (YES/NO) See PART 2 Manual Initialize Quality Check LSP Quality Auto I/O Selection Board Number Initialize Bad AND Slot Number RQ Module Error (SUPP/ENAB) RBQ Error Check MODMM Diagnostic Group (NONE, 1 - 7) (init
PAGE 131
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) Input Channel 1 (Same as Digital Output Module signal flow) MODMM I/O Selection Board Number MODMMA Slot Number MODMMU Error Check Module Error DDOM1 Module Error (SUPP/ENAB) Diagnostic Group (NONE, 1 - 7) RQ1 RBQ1 DDOERRA1 DDOERRU1 Dual Digital Output Module Module Error RQ2 DDOM2 Module Error (SUPP/ENAB) RBQ2 I/O Mismatch (SUPP/ENAB) DDOERRA2 DDOERRU2 Input Channel 2 (Same as Digital Output Module signal flow) Figur
PAGE 132
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) Table 5-2.
PAGE 133
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) 5.3.2 Dual Digital Output Module Block Description (DDOM) The channel 1 display used to configure the dual digital output module block is shown in Figure 5-8 and the diagnostic properties display in Figure 5-9. The mnemonics, valid values, and data types for all fields that may be selected for display and/or be used in making softwiring connections are listed in Table 5-3.
PAGE 134
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) Figure 5-9. Digital Output Module (DOM), Diagnostic Menu Table 5-3.
PAGE 135
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) Table 5-3.
PAGE 136
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) 5.3.3 Wide Digital Output Module Block Description (WDOM) The menus used to configure the wide digital output module block are shown in Figure 5-10. The mnemonics, valid values, and data types for all fields that may be selected for display and / or be used in making softwiring connections are listed in Table 5-4. Figure 5-10a. Wide Digital Output Module (WDOM), General Menu Figure 5-10b.
PAGE 137
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) Table 5-4.
PAGE 138
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) 5.3.4 Digital Output Module Block Parameters The following further defines the Digital Input/Output Module Block configuration parameters. Block Type DOM This is the Digital Output Module Block type. It connects one 2005A Solid State Relay Output or one 2007A Unconditioned Digital Output. DDOM This is the Dual Digital Output Module Block type. It connects one 2011A Mechanical Relay Output (Dual SPST relay).
PAGE 139
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) DOM 05 DDOM 05 WDOM 05 DOM 06 DDOM 06 WDOM 06 DOM 07 DDOM 07 WDOM 07 DOM 08 DDOM 08 DDOM 11 WDOM 08 I/O Mismatch (MODMMS) ..................................................................................................CWR I/O Mismatch (MODMMS) ..................................................................................................CWR I/O Mismatch (MODMMS) .................................................................
PAGE 140
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) DOM 09 DDOM 09 DDOM 12 WDOM 09 DOM 10 DDOM 10 DDOM 13 WDOM 10 DOM 11 DDOM 14 WDOM 11 Unacked DOM Module Error (DOMERRU) ......................................................................– WR Unacked DDOM1 Module Error (DDOERRU1) ................................................................– WR Unacked DDOM2 Module Error (DDOERRU2) ................................................................
PAGE 141
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) DOM 15 DDOM 18 DDOM 28 WDOM 15 Mode (MODE) .....................................................................................................................CWR Mode (MODE1) ...................................................................................................................CWR Mode (MODE2) ...................................................................................................................
PAGE 142
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) DOM 20 DDOM 23 DDOM 33 WDOM 20 Track Status Quality (TRKQ)............................................................................................– WR Track Status Quality (TRKQ1)..........................................................................................– WR Track Status Quality (TRKQ2)..........................................................................................– WR Track Status Quality (TRKQ)..........
PAGE 143
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) Result (R)............................................................................................................................– – R Result (R1)..........................................................................................................................– – R Result (R2)..........................................................................................................................– – R Result (R)...........
PAGE 144
Logic Functions - Book 1 DIGITAL OUTPUT MODULE BLOCKS (DOM, DDOM, WDOM) 5.3.6 Digital Output Module Block Events The event codes (and their suggested text messages) for the digital output module blocks are given below. See the referenced data base attributes (in brackets) for additional information. See the system event block for event transitions.
PAGE 145
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) 5.4 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) The analog input module blocks serve as the data handling blocks for the analog input modules. Analog input modules condition the field signals and convert these signals to digital data in 100 milliseconds.
PAGE 146
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) 5.4.1 General Operation These blocks are data repositories for the instrument. One module block services one module and as many other analog input function blocks as required can receive signals from these blocks. All input values are buffered in one of five possible state tables.
PAGE 147
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) 5.4.2 Voltage/Current Input Module Block Description (VCIM) This block is used to input a count value from a voltage or current input module. It also performs filtering for the connected voltage/current input or thermocouple transmitter input block. A functional block diagram of a VCIM block is shown in Figure 5-13. The menus used to configure the block are shown in Figures 5-14 and 5-15.
PAGE 148
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) Figure 5-14. Voltage/Current Input Module Block (VCIM), General Menu Figure 5-15.
PAGE 149
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) Table 5-5. Voltage/Current Input Module Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length Block State Bad Inputs Accepted Diagnostic Group I/O mismatch Unacked I/O Mismatch Active I/O Mismatch I/O communications error Unacked comm. error Active comm.
PAGE 150
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) 5.4.3 Thermocouple Input Module Block Description (TIM) This block is used to input a count value from a voltage or thermocouple input module. It also performs filtering for the connected thermocouple input block. A functional block diagram of a thermocouple input module block is shown in Figure 5-16. The menus used to configure the block are shown in Figures 5-17 and 5-18.
PAGE 151
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) Figure 5-17. Thermocouple Input Module (TIM), General Menu Figure 5-18.
PAGE 152
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) Table 5-6. Thermocouple Input Module Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length Block State Bad Inputs Accepted Diagnostic Group I/O mismatch Unacked I/O Mismatch Active I/O Mismatch I/O communications error Unacked comm. error Active comm.
PAGE 153
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) 5.4.4 Resistance Input Module Block Description (RIM) This block is used to input a count value from a resistance input module. It also performs filtering for the connected resistance input block. A functional block diagram of a resistance input module block is shown in Figure 5-19. The menus used to configure the block are shown in Figures 5-20 and 5-21.
PAGE 154
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) Figure 5-20. Resistance Input Module (RIM), General Menu Figure 5-21.
PAGE 155
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) Table 5-8. Resistance Input Module Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length Block State Bad Inputs Accepted Diagnostic Group I/O mismatch Unacked I/O Mismatch Active I/O Mismatch I/O communications error Unacked comm. error Active comm.
PAGE 156
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) 5.4.5 Wide Resistance Input Module Block Description (WRIM) This block is used to input a count value from a resistance input module. It also performs filtering for the connected resistance input block. A functional block diagram of a wide resistance input module block is shown in Figure 5-22. The menus used to configure the block are shown in Figures 5-23 and 5-24.
PAGE 157
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) Figure 5-23. Wide Resistance Input Module (WRIM), General Menu Figure 5-24.
PAGE 158
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) Table 5-9. Wide Resistance Input Module Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length Block State Bad Inputs Accepted Diagnostic Group I/O mismatch Unacked I/O Mismatch Active I/O Mismatch I/O communications error Unacked comm. error Active comm.
PAGE 159
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) 5.4.6 Analog Input Module Block Parameters The following further defines the configuration parameters and attributes for the VCIM, TIM, RIM, and WRIM blocks.
PAGE 160
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) 06 07 08 09 10 VCIM 11 TIM 11 RIM 11 WRIM 11 5-40 Unacked I/O Mismatch (MODMMU) .................................................................................– WR If the I/O mismatch diagnostic error is enabled, the unacknowledged I/O mismatch diagnostic status indicates if the diagnostic is or is not acknowledged. The status can be acknowledged or read as follows. YES 1 Diagnostic error is unacknowledged.
PAGE 161
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) VCIM 12 TIM 12 RIM 12 WRIM 12 VCIM 13 TIM 13 RIM 13 WRIM 13 14 Unacked Input Module Error (VCIMERRU)..................................................................... – WR Unacked Input Module Error (TIMERRU) ....................................................................... – WR Unacked Input Module Error (RIMERRU) .......................................................................
PAGE 162
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) 18 Extended Error Code (EXTERR) ......................................................................................– WR The extended error code is a bitmapped two byte (16 bit) error code from the module that is presented as a count value.
PAGE 163
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) TIM 20 Thermocouple Type (TCTYPE).........................................................................................CWR The linearization specified here is performed in the TTI or TI function blocks. B E J K N R S T VCIM 28 RIM 21 WRIM 21 1 2 3 4 5 6 7 8 Input linearization is for a B type thermocouple. Input linearization is for a E type thermocouple. Input linearization is for a J type thermocouple.
PAGE 164
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) TIM 21 Cold Junction Compensation (CJCLOC) ........................................................................ CWR For TIM block types only. The cold junction compensation parameter is either a module source (MODOUT) or local data. Connect the module (MODOUT) to be used as a cold junction source or enter the floating point equivalent for the junction temperature in the required degree units (C, F, K, or R).
PAGE 165
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) VCIM 24 TIM 22 RIM 26 WRIM 25 Initial result (Result) (R).....................................................................................................CWR Initial Result (Result) (R) ....................................................................................................CWR Initial result (Result) (R).....................................................................................................
PAGE 166
Logic Functions - Book 1 ANALOG INPUT MODULE BLOCKS (VCIM, TIM, RIM, WRIM) VCIM 26 TIM 24 RIM 28 WRIM 27 Field Result (FR) ............................................................................................................... – – R Field Result (FR) ............................................................................................................... – – R Field Result (FR) ...............................................................................................................
PAGE 167
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) 5.5 ANALOG OUTPUT MODULE BLOCK (AOM) The analog output module block serves as the data handling block for the current output module. This block is used to output an analog value to, and receive a readback value from the current output module. The current output module converts a digital count value to a 420mA field signal and converts it back to counts for readback in 100 milliseconds.
PAGE 168
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) PART 2 Scaled Result Input Range Bottom Input Range Top Output Range Bottom Normalization In Tolerance Output Range Top Result Action (DIR/REV) Scaling Out of Tolerance Analog Output Module - Current Output Normal Scaled Readback See PART 1 Initialize Initialize Out of Tolerance In Tolerance Readback PREVIOUS Initialize PRESET Output to use on Restart HOLD Restart Preset Value PRESET Failsafe Preset Value RBQ EXTERR Output to
PAGE 169
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) Figure 5-28. Analog Output Module (AOM), General Menu Figure 5-29.
PAGE 170
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) Figure 5-30. Analog Output Module (AOM), Diagnostic Menu 5.5.1 Analog Output Module Block Capabilities The Analog Output Module block is a data repository for the instrument. One module block services one module. All values are buffered in one of five possible task state tables.
PAGE 171
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) 5.5.2 Analog Output Module Block Parameters The mnemonics, valid values, and data types for all fields that may be selected for display and/or be used in making softwiring connections are listed in Table 5-10. The following further defines the analog output module block configuration parameters. Table 5-10.
PAGE 172
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) Block Type AOM This is the Analog Output Module Block type. Occurrence 1 to 32 There may be up to 32 ‘instances’ allowed of the AOM block type. 02 State (STATE) .................................................................................................................... – – R Not configurable in this block (always equal to RUN). See Section 2.4.1, State Changes for additional information.
PAGE 173
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) 08 09 10 11 12 13 AO module communications error (COMMERRS) .........................................................CWR The AO module communications error diagnostic checks the status of communications between the module and this block and looks for checksum errors. This diagnostic is also generated when the select circuit, which is used to communicate with the module, has a diagnostic error.
PAGE 174
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) 14 I/O Mismatch (MODMM) .................................................................................................... – – R Even though the I/O mismatch diagnostic may be suppressed and its value not stored with the active I/O mismatch attribute, the actual I/O mismatch condition can still be determined by this attribute (value is unsuppressed).
PAGE 175
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) 21 Input Range, Top (INHI) ....................................................................................................CWR User scaled high floating point engineering units value for input normalization. The default is 100.0. The input range top must match the actual input engineering units high value. The normalization calculation is: (RSC – INLO) / (INHI – INLO). The normalized result must always be a value between 0 and 1.
PAGE 176
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) 26 Output to use on failsafe (FSACT)................................................................................... CWR A failsafe condition results when this block looses communication with the select circuit. A write to the failsafe action attribute causes the failsafe configuration to be downloaded to the module. HOLD 0 Failsafe output value is last result value. PRESET 1 Failsafe output value is the failsafe preset value.
PAGE 177
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) 33 Input (INPUT)......................................................................................................................CWR The local engineering units value input can be written when the input source is local and the block is in auto; otherwise, this value is the input source value and can not be written. When the instrument state is not run, i/o lock is set or mode is manual, the scaled result (RSC) can be written.
PAGE 178
Logic Functions - Book 1 ANALOG OUTPUT MODULE BLOCK (AOM) 5.5.3 Typical Block Connections for Analog Output Module Block Typical softwiring block structures used on softwiring diagrams are shown in Figure 5-31. Slot 8 AOM1 LN1 HILIM Result R 1 INPUT 2 Result Input Mode Scaled Result MODE RSC Operator indication of input value, output value and mode. Operator write access to set mode and scaled result. Figure 5-31. Analog Output Module Block, Typical Connections 5.5.
PAGE 179
Logic Functions - Book 1 REMOTE INPUT/OUTPUT BLOCKS 6 REMOTE INPUT/OUTPUT MODULE DATA BASE PARAMETERS 6.1 REMOTE INPUT/OUTPUT LIBRARY BLOCKS Remote Input/Output module blocks define a physical input or output connection point and are not part of a loop scan group. The Remote I/O module blocks are available inside or outside of loop compounds. One of these modules is required to get a remote field signal into the instrument.
PAGE 180
Logic Functions - Book 1 REMOTE INPUT/OUTPUT BLOCKS 6-2
PAGE 181
Logic Functions - Book 1 REMOTE I/O INTERFACE MODULE BLOCK 6.2 REMOTE I/O INTERFACE MODULE BLOCK (RIO) The RIO block is the data handling block for a Remote I/O Interface Module installed in the instrument. The RIO module serves as the interface between the instrument and a CS-31 Remote I/O Network (CS-31 Bus). The instrument database must have one RIO block for each installed interface module. A functional block diagram of a RIO block is shown in Figure 6-1.
PAGE 182
Logic Functions - Book 1 REMOTE I/O INTERFACE MODULE BLOCK The remote I/O interface module block generates a diagnostic error based upon the following: • Unsuppressed I/O mismatch condition • CS-31 bus communications error • I/O communications error • CS-31 database checksum error • Remote module error. Events are reported for each of these diagnostic errors. Figure 6-2.
PAGE 183
Logic Functions - Book 1 REMOTE I/O INTERFACE MODULE BLOCK 6.2.2 Remote I/O Interface Module Block Parameters The mnemonics, valid values, and data types for all attributes that can be selected for display and/or be used in making softwiring connections are listed in Table 6-1. A description of each attribute is provided in the attribute list that follows the table. Table 6-1.
PAGE 184
Logic Functions - Book 1 REMOTE I/O INTERFACE MODULE BLOCK 00 Version (VERSION) ........................................................................................................... – – R Version number of RIO block. Presently 1. 01 Block Length (BLKLEN) .................................................................................................... – – R Number of database bytes used. 02 State (STATE) ..........................................................................................
PAGE 185
Logic Functions - Book 1 REMOTE I/O INTERFACE MODULE BLOCK 08 09 10 11 12 13 I/O Communication Error (BUSERRS) .............................................................................CWR This diagnostic indicates that an error occurred in communication between the RIO module and the instrument. This diagnostic can be suppressed or enabled as follows: ENABLE 0 Diagnostic error is not suppressed and errors are reported to the System Event block. SUPPRESS 1 Diagnostic error is suppressed.
PAGE 186
Logic Functions - Book 1 REMOTE I/O INTERFACE MODULE BLOCK 14 15 16 17 18 19 6-8 Database Checksum Error (DBASERRS) ........................................................................ CWR This diagnostic indicates that the remote I/O database stored in the interface module has been declared bad due to a checksum error. This diagnostic can be suppressed or enabled as follows: ENABLE 0 Diagnostic error is not suppressed and errors are reported to the System Event block.
PAGE 187
Logic Functions - Book 1 REMOTE I/O INTERFACE MODULE BLOCK 20 I/O Module Mismatch (MODMM).......................................................................................– – R Even though the I/O mismatch diagnostic may be suppressed and its value not stored with the active I/O mismatch attribute, the actual I/O mismatch condition can still be determined by this attribute (value is unsuppressed).
PAGE 188
Logic Functions - Book 1 REMOTE I/O INTERFACE MODULE BLOCK 6.2.3 Typical Block Connections for Remote I/O Interface Module Block Typical RIO block connections are shown in Figure 6-3. The application builder software provides special connections to simplify the database configuration procedure required to transfer data between the interface block and its associated remote I/O module blocks.
PAGE 189
Logic Functions - Book 1 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) 6.3 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) The remote digital input module block is used to input as many as 16 digital inputs from a remote digital input module connected to a CS-31 remote I/O network. The RDIM block is valid for use with the following remote modules: Module No.
PAGE 190
Logic Functions - Book 1 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) 6.3.1 Remote Digital Input Module Block Operation The RDIM block is a data repository for the input data from a remote digital input module. This data is received via a remote I/O interface module, and is updated during each 50ms base scan cycle. One RDIM block services one remote digital input module, and as many digital input function (DI) blocks as required can be connected using the MODOUT to MODIN connection.
PAGE 191
Logic Functions - Book 1 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) Figure 6-5. Remote Digital Input Module Block, General Menu Figure 6-6.
PAGE 192
Logic Functions - Book 1 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) 6.3.2 Remote Digital Input Module Block Parameters The mnemonics, valid values, and data types for all attributes that can be selected for display and/or be used in making softwiring connections are listed in Table 6-2. A description of each attribute is provided in the attribute list that follows the table. Table 6-2.
PAGE 193
Logic Functions - Book 1 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) Table 6-2.
PAGE 194
Logic Functions - Book 1 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) Table 6-2.
PAGE 195
Logic Functions - Book 1 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) 00 Version (VERSION) ––R Version number of RDIM block. Presently 1. 01 Block Length (BLKLEN).....................................................................................................– – R Number of database bytes used. 02 State (STATE).....................................................................................................................– – R Not configurable in this block (always equal to RUN). See Section 2.4.
PAGE 196
Logic Functions - Book 1 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) 08 09 10 Module Error (EXTERRS) ......CWR This remote module error diagnostic checks for remote I/O module errors. Reported error codes are stored in the block database as extended errors (EXTERR, attributes 15-30). The diagnostic can be suppressed or enabled as follows: ENABLE 0 Diagnostic error is not suppressed and errors are reported to the System Event block. SUPPRESS 1 Diagnostic error is suppressed. clear.
PAGE 197
Logic Functions - Book 1 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) 15 - 30 Extended Error, Channel 0 (EXTERR0) through Channel 15 (EXTERR15) – WR The last error code as read from the remote module (whether active or not). See packed extended errors PKDERRS attribute 126.
PAGE 198
Logic Functions - Book 1 REMOTE DIGITAL INPUT MODULE BLOCK (RDIM) 64, 68...124 Initial Result Channel 0 (R0) through Channel 15 (R15) CWR The initial result is the value used for each channel when the block is initially downloaded. This value is overwritten when the block first executes. Subsequent values are the result of block evaluation after action is applied. This value is writeable only when the block mode is manual, when I/O is locked, or the instrument state is not run. 65, 69...
PAGE 199
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) 6.4 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) The remote digital output module blocks serve as the data handling blocks for the remote digital output modules. Each block can output as many as 16 discrete values to a remote digital output module. The RDOM block is valid for use with the following remote modules: Module No.
PAGE 200
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) Bad Lock Track OR TRKSTA0 Manual I/O Lock (from IF Block) MODE0 DIRECT REVERSE FALSE ACTION0 GOOD TRUE Input (I0) Unlock LSP Auto BAD Normal Lock Manual Bad Inputs Accepted (NO) Initialize LSP Quality Quality Check Auto TRKQ0 BUSADDR R0Q Bad AND SLOT Initialize PKDRQ (init flag) (Remote) I/O Mismatch (SUPP/ENAB) EXTERRU Error Check EXTERRA (Remote) Module Error (SUPP/ENAB) MODMMU MODMMA Diagnostic Group (NO
PAGE 201
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) Figure 6-9. Remote Digital Output Module Block, General Menu Figure 6-10.
PAGE 202
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) Figure 6-11.
PAGE 203
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) 6.4.2 Remote Digital Output Module Block Parameters The mnemonics, valid values, and data types for all attributes that can be selected for display and/or be used in making softwiring connections are listed in Table 6-3. A description of each attribute is provided in the attribute list that follows the table. Table 6-3.
PAGE 204
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) Table 6-3.
PAGE 205
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) Table 6-3.
PAGE 206
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) 03 Bad Inputs Accepted (BADINP) ....................................................................................... – – R This attribute is present but is not used in this block. See attributes 15 through 30. 04 Diagnostic Group (SUPPGRP).........................................................................................
PAGE 207
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) 09 10 11 Unacknowledged Remote Module Error (EXTERRU).................................................... – WR If this extended diagnostic error is enabled, the unacknowledged status indicates if the diagnostic is or is not acknowledged. The status can be acknowledged or read as follows. NO 0 Diagnostic error is acknowledged. YES 1 Diagnostic error is unacknowledged. Active Remote Module Error (EXTERRA).............................
PAGE 208
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) 31-46 Extended Error, Channel 0 (EXTERR0) through Channel 15 (EXTERR15) .....................– WR The last error code as read from the remote module (whether active or not). See packed extended errors PKDERRS attribute 244.
PAGE 209
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) 111, 113.. 141 Track Status,Channel 0 (TRKSTA0) through Channel 15 (TRKSTA15)........................... – WR Track status is set to track whenever the path from the input to the result is broken. This occurs when the data quality is bad, the I/O lock is locked, or when the mode is manual. NO TRACK 0 Data quality is good, I/O lock is unlocked and mode is auto. TRACK 1 Data quality is bad, I/O lock is locked or mode is manual.
PAGE 210
Logic Functions - Book 1 REMOTE DIGITAL OUTPUT MODULE BLOCK (RDOM) 213,215...243 Result Quality,Channel 0 (R0Q) through Channel 15 (R15Q) ..........................................– WR The result quality is set BAD when the input status is bad and bad inputs are not accepted, or if the restart value cannot be read after a warm start. Any write to the result causes the result quality to be set GOOD. The result quality is writeable in manual, when the I/O is locked, or the instrument state is not run.
PAGE 211
Logic Functions - Book 1 INPUT FUNCTIONS BLOCKS 7 INPUT FUNCTIONS DATABASE PARAMETERS 7.1 INPUT FUNCTIONS LIBRARY BLOCKS Function blocks (algorithm blocks that execute the logic) cannot operate independently in the instrument database. Groups of related function blocks must be organized into loops. Input function blocks are selected from the Input Functions library and placed in a loop compound. The input function block types are: DI Digital Input Block. Reference IB-23G600 Section 7.3.
PAGE 212
Logic Functions - Book 1 INPUT FUNCTIONS BLOCKS 7-2
PAGE 213
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) 7.2 ANALOG INPUT BLOCKS (VCI, TTI, TI, RI, RTI RTTI) The analog input blocks (VCI, TTI, TI, RI, RTI and RTTI) provide an input link from a physical analog input module (VCIM, TIM, RIM, WRIM, RAIM) to a loop. The relationship between these blocks is discussed in Sections 5 and 6. Functions performed by these blocks include input filtering, action, normalization, linearization, and scaling.
PAGE 214
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) 7.2.1 Voltage/Current Input Block Description (VCI) This block is used to input a volt/current module’s value and translate it to a user specified scaled value. It receives its input from a VCIM or RAIM block. A functional block diagram of a voltage/current input block is shown in Figure 7-1. The menus used to configure the block are shown in Figures 7-2 and 7-3.
PAGE 215
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Figure 7-2. Voltage/Current Input Block (VCI), General Menu Figure 7-3.
PAGE 216
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Table 7-1. Voltage/Current Input Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length State Bad Inputs Accepted Diagnostic Group Supp. Calculation Error Calc. Error Unacked Calc. Error Unacked Quality Calc. Error Active Calc.
PAGE 217
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) 7.2.2 Thermocouple Transmitter Input Block Description (TTI) This block is used to input a thermocouple transmitter’s value and translate it to a scaled temperature. It receives its input from a voltage/current module block only. A functional block diagram of a thermocouple transmitter input block is shown in Figure 7-4. The menus used to configure the block are shown in Figure 7-5 and 7-6.
PAGE 218
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Figure 7-5. Thermocouple Transmitter Input Block (TTI), General Menu Figure 7-6.
PAGE 219
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Table 7-2. Thermocouple Transmitter Input Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length State Bad Inputs Accepted Diagnostic Group Supp. Calculation Error Calc. Error Unacked Calc. Error Unacked Quality Calc. Error Active Calc.
PAGE 220
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) 7.2.3 Thermocouple Input Block Description (TI) This block is used to input a thermocouple value, compensate it and translate it to a scaled temperature. It’s input is from a thermocouple module and it’s compensation input from a RIM, or WRIM block or a floating point value specified in the thermocouple module block or through the local CJC input. A functional block diagram of a thermocouple input block is shown in Figure 7-7.
PAGE 221
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Figure 7-8. Thermocouple Input (TI), General Menu Figure 7-9.
PAGE 222
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Table 7-3. Thermocouple Input Block Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length State Bad Inputs Accepted Diagnostic Group Supp. Calculation Error Calc. Error Unacked Calc. Error Unacked Quality Calc. Error Active Calc.
PAGE 223
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) 7.2.4 Resistance Input Block Description (RI) This block is used to input a resistance module’s value and translate it to a user specified scaled value. It receives its input from a RIM or WRIM block only. A functional block diagram of a resistance input block is shown in Figure 7-10. The menus used to configure the block are shown in Figures 7-11 and 7-12.
PAGE 224
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Figure 7-11. Resistance Input Block (RI), General Menu Figure 7-12.
PAGE 225
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Table 7-4. Resistance Input Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length State Bad Inputs Accepted Diagnostic Group Supp. Calculation Error Calc. Error Unacked Calc. Error Unacked Quality Calc. Error Active Calc.
PAGE 226
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) 7.2.5 RTD Input Block Description (RTI) This block is used to input a RTD value and translate it to a scaled temperature. It receives its input from a RIM or WRIM module block only. A functional block diagram of a RTD input block is shown in Figure 7-13. Menus used to configure the block re shown in Figure 7-14 and Figure 7-15.
PAGE 227
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Figure 7-14. RTD Input Block (RTI), General Menu Figure 7-15.
PAGE 228
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Table 7-5. RTD Input Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length State Bad Inputs Accepted Diagnostic Group Supp. Calculation Error Calc. Error Unacked Calc. Error Unacked Quality Calc. Error Active Calc.
PAGE 229
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) 7.2.6 RTD Transmitter Input Block Description (RTTI) This block is used to input a RTD transmitter value and translate it to a scaled temperature. It receives its input from a VCIM module block only. A functional block diagram of a RTD transmitter input block is shown in Figure 7-16. The menus used to configure the block are shown in Figure 7-17 and 7-18.
PAGE 230
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Figure 7-17. RTD Transmitter Input Block (RTTI), General Menu Figure 7-18.
PAGE 231
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) Table 7-6. RTD Transmitter Input Block Attributes, Valid Values, Mnemonics, and Data Types Field Name / Attribute Version Block Length State Bad Inputs Accepted Diagnostic Group Supp. Calculation Error Calc. Error Unacked Calc. Error Unacked Quality Calc. Error Active Calc.
PAGE 232
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) 7.2.7 Analog Input Type Block Parameters The mnemonics, valid values, and data types for all fields that may be selected for display and/or be used in making softwiring connections are listed in Sections 7.2.1 to 7.2.7. The following further defines the configuration parameters for the VCI, TTI, TI, RI, RTI, and RTTI blocks. Block Type The following are valid analog input block types.
PAGE 233
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) 04 05 Diagnostic Group Supp. (SUPPGRP) ..............................................................................CWR The diagnostic error reported by this block can be grouped for System Event block control of its reporting. The selections are: NONE No group assigned. 1 to 7 Defines the diagnostic group number for the diagnostic suppression group controlled by the System Event block. Diagnostic Error (CERRS) ..............
PAGE 234
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) VCI 11 TTI 11 RI 11 RTTI 11 VCI 12 TTI 12 TI 11 RTI 11 RTTI 12 VCI 13 TTI 13 TI 12 RI 12 RTI 12 RTTI 13 7-24 Action (ACTION) ................................................................................................................ CWR Action (ACTION) ................................................................................................................ CWR Action (ACTION) ........................................
PAGE 235
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) milliseconds, four samples would be filtered using the following first order filter calculation: USER VCI 14 TTI 14 TI 13 RI 13 RTI 13 RTTI 14 2 Value = Previous value + (0.15 / (0.15 + FILTIME)) * (sampled value - Previous value) where 150 milliseconds is the base sample rate for analog inputs and FILTIME is the filter time = 0.150 / 0.
PAGE 236
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) TTI 16 RTTI 16 Transmitter Range - Bottom (TRANSLO) ........................................................................ CWR Transmitter Range - Bottom (TRANSLO) ........................................................................ CWR Transmitter bottom of range for TTI and RTTI blocks. Specified in result units as described for Top of Range. TTI 17 TI 14 RTI 14 RTTI 17 Output Calibrate - Zero (ZERO) .....................
PAGE 237
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) VCI 20 TTI 22 TI 19 RI 19 RTI 9 RTTI 22 TI 20 7.2.8 Result Data Quality (RQ).................................................................................................. – WR Result Data Quality (RQ).................................................................................................. – WR Result Data Quality (RQ)..................................................................................................
PAGE 238
Logic Functions - Book 1 ANALOG INPUT BLOCKS (VCI, TII, TI, RI, RTI, RTTI) 7.2.9 Analog Input Type Block Events The event codes (and their suggested text messages) for the analog input type blocks are given below. See data base attribute descriptions for additional information. See the system event block for a description of event transitions.
PAGE 239
Logic Functions - Book 1 DIGITAL INPUT BLOCK 7.3 DIGITAL INPUT BLOCK (DI) The digital input block provides an input link from a physical digital input module (DIM or RDIM) to a loop. A digital input module conditions a field signal and processes the signal through an on-board select circuit which passes all digital data between the modules and the module blocks at the base scan rate of 50 milliseconds.
PAGE 240
Logic Functions - Book 1 DIGITAL INPUT BLOCK Figure 7-21. Digital Input Block (DI), General Menu 7.3.1 Digital Input Block Operation The digital input block is a loop function block that provides a logical input link to an input module (one physical input point). As many input blocks as required can be connected to a module block source. The input value is buffered in the group state table for the loop.
PAGE 241
Logic Functions - Book 1 DIGITAL INPUT BLOCK Input Module ......................................................................................................................C – – DIM1 A Digital Input Module (DIM) is the only valid input module type as connected through MODIN. Occurrence numbers may be from 1 to 32. Table 7-7.
PAGE 242
Logic Functions - Book 1 DIGITAL INPUT BLOCK FALSE 1 If a FALSE latch is specified, a transition to FALSE by the input is latched until the value is read by the task. TRUE 2 If a TRUE latch type is specified, a transition to TRUE by the input is latched until the value is read by the task. TRANS. 3 TRANSITION latch will latch either transition. The transition latch type applies to the input signal before the input action is applied. Action (ACTION) .................................................
PAGE 243
Logic Functions - Book 1 APPENDIX A - VERSION DIFFERENCES APPENDIX A SUMMARY OF VERSION DIFFERENCES A.1 GENERAL This document is written to reflect the latest model and version of the instrument. The summary provided below notes the differences between the current instrument and the previous versions. Current functionality is: Logic 6, Advanced 3, MOD 30ML 2. At present, upgrades are possible using the configurator.
PAGE 244
Logic Functions - Book 1 APPENDIX A - VERSION DIFFERENCES A.4 LOGIC 3, REGULATORY 2, BATCH 1 FUNCTIONALITY These instrument versions have a Version 1 MSC Block (renamed from Modbus Slave to Modcell Serial with version 2 of the block). The version 1 block does not include attributes 26 to 28 and 83 to 88 and does not include event code 14. This functionality is used to support communication modules with the address switch and support Extended Modbus, Modbus master (see Appendix B) and slave communications.
PAGE 245
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION APPENDIX B MODBUS MASTER CONFIGURATION B.1 OVERVIEW Modbus Master communication functionality was introduced on the MODCELL Multiloop Processor firmware (version 3.1 logic controller, version 2.1 regulatory controller) without adding any new function blocks.
PAGE 246
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION B.2 MODCELL SERIAL COMMUNICATION (MSC) BLOCK MODIFICATIONS Configure an MSC block to be used as a MASTER. If the MSC block is version 2, just configure the Port Functionality attribute to be Master using the Application Builder or ViZapp Port Functionality configuration entry. This can also be done by writing the value 251 to the MSC Command attribute from the status page after the database is downloaded into the instrument (MSCx,CMD 251).
PAGE 247
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION The Expression in the Expression block can still be used. The Modbus Master code will execute first and then the expression will be evaluated. When an Expression block is used for a Modbus Master interface it’s message handler routine will not allow writes to attributes that are configuration parameters for the Modbus Master function.
PAGE 248
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION Modcell datatype to register mapping table: The following table describes how many registers the Modcell data types use and how the data is expected to be organized. See MODCELL Logic Controller Data Base Reference Manual IB-23G600 Section 2.3.4 for further Data Type description. MODCELL Data Type Remarks B-4 Discrete Takes 1 register. Valid values are 0 and 1 Short State Takes 1 register.
PAGE 249
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION Message STATUS INFO values and descriptions: Value 0 Description Valid response message received. *1 Illegal MFC *2 Illegal Data Addr *3 Illegal Data Value *4 Failure in associated device *5 Acknowledge *6 Busy, rejected message *7 Nak-Negative Acknowledgment *8 Memory parity error 241 At least one of the attributes that was read was out of it’s data type range.
PAGE 250
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION B.3.1 Configuration Items There must be one of these expression blocks configured per modbus port. If there is not one configured, the other Modbus Master EX blocks for this port will not execute as a MASTER. The configuration of a Modbus Master EX block used to hold some configuration parameters is defined as: INPUT1 CFG,MM,PORTz Local ASCII Not writeable through message handler.
PAGE 251
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION INPUT5 NUM OF MM EX BLKS CFGD OK Local Count Not writeable through message handler. This value indicates the number of Modbus Master EX blocks that are configured with no errors and have ram space allocated. Value 65534 indicates there is more than one of these EX blocks configured for this modbus master port; therefore, this one is not used. Value 65535 indicates the port that this EX block is configured for is not a modbus master port.
PAGE 252
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION If no response is received from a slave all other messages that are currently queued up for that slave address will be marked as no response and removed from the queue. This will help wasting too much time on a slave device that is no longer functioning. If there are more than one of these EX blocks in the database the lowest occurrence number EX block will be used.
PAGE 253
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION B.3.2 Read Coil Status The configuration of a Modbus Master EX block used to read the Coil Status (Discrete Read/Write memory) area 00001 to 09999 is defined as: INPUT1 RCS,MM,PORTz Local ASCII Not writeable through message handler. CFG ONLY INPUT2 NUMBER READ ATTRIBUTES Local Count Not writeable through message handler.
PAGE 254
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION INPUT7 REFRESH STATE Local Long State Support for the value of 255 was added in the release of Logic Controller version 5 and Advanced Controller version 2. IF REFRESH STATE = 0 Value 0 indicates the SEND INPUT is used and INPUT8 (SEND INPUT) must be configured. The value 0 can only be written through the message handler if the SEND INPUT is present.
PAGE 255
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION B.3.3 Read Input Status The configuration of a Modbus Master EX block used to read the Input Status (Discrete Read Only memory) area 10001 to 19999 is defined as: INPUT1 RIS,MM,PORTz Local ASCII Not writeable through message handler. CFG ONLY INPUT2 NUMBER READ ATTRIBUTES Local Count Not writeable through message handler.
PAGE 256
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION INPUT7 REFRESH STATE Local Long State Support for the value of 255 was added in the release of Logic Controller version 5 and Advanced Controller version 2. IF REFRESH STATE = 0 Value 0 indicates the SEND INPUT is used and INPUT8 (SEND INPUT) must be configured. The value 0 can only be written through the message handler if the SEND INPUT is present.
PAGE 257
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION B.3.4 Read Input Register The configuration of a Modbus Master EX block used to read the Input Register (Read Only memory) area 30001 to 39999 is defined as: INPUT1 RIR,MM,PORTz Local ASCII Not writeable through message handler. CFG ONLY INPUT2 NUMBER READ ATTRIBUTES Local Count Not writeable through message handler.
PAGE 258
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION INPUT7 REFRESH STATE Local Long State Support for the value of 255 was added in the release of Logic Controller version 5 and Advanced Controller version 2. IF REFRESH STATE = 0 Value 0 indicates the SEND INPUT is used and INPUT8 (SEND INPUT) must be configured. The value 0 can only be written through the message handler if the SEND INPUT is present.
PAGE 259
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION B.3.5 Read Holding Register The configuration of a Modbus Master EX block used to read the Holding Register (Read/Write memory) area 40001 to 49999 is defined as: INPUT1 RHR,MM,PORTz Local ASCII Not writeable through message handler. CFG ONLY INPUT2 NUMBER READ ATTRIBUTES Local Count Not writeable through message handler.
PAGE 260
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION INPUT7 REFRESH STATE Local Long State Support for the value of 255 was added in the release of Logic Controller version 5 and Advanced Controller version 2. IF REFRESH STATE = 0 Value 0 indicates the SEND INPUT is used and INPUT8 (SEND INPUT) must be configured. The value 0 can only be written through the message handler if the SEND INPUT is present.
PAGE 261
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION B.3.6 Write One or More Coils The configuration of a Modbus Master EX block used to write one or more Coils (Discretes) in memory area 00001 to 09999 is defined as: INPUT1 WRC,MM,PORTz Local ASCII Not writeable through message handler. CFG ONLY INPUT2 NUMBER WRITE ATTRIBUTES Local Count Not writeable through message handler. CFG ONLY This value is the number of attribute values that should be written.
PAGE 262
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION INPUT7 REFRESH STATE Local Long State Support for the value of 255 was added in the release of Logic Controller version 5 and Advanced Controller version 2. IF REFRESH STATE = 0 Value 0 indicates the SEND INPUT is used and INPUT8 (SEND INPUT) must be configured. The value 0 can only be written through the message handler if the SEND INPUT is present.
PAGE 263
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION B.3.7 Write One or More Registers The configuration of a Modbus Master EX block used to write one or more attributes in memory area 40001 to 49999 is defined as: INPUT1 WRR,MM,PORTz Local ASCII Not writeable through message handler. CFG ONLY This value is the number of attribute values that should be written. The values to be written are stored at this block’s INPUT11 through INPUTn. The minimum value is 1.
PAGE 264
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION INPUT7 REFRESH STATE Local Long State Support for the value of 255 was added in the release of Logic Controller version 5 and Advanced Controller version 2. IF REFRESH STATE = 0 Value 0 indicates the SEND INPUT is used and INPUT8 (SEND INPUT) must be configured. The value 0 can only be written through the message handler if the SEND INPUT is present.
PAGE 265
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION B.4 B.4.1 EXAMPLES Example 1 NOTE: The entry for input 1 must be all UPPER CASE (ASCII is case sensetive).
PAGE 266
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION I11 I12 I13 I14 I15 I16 I17 I18 ( ( ( ( ( ( ( ( LSP LSP LSP LSP LSP LSP LSP LSP DIM1,R DIM2,R DIM3,R DIM4,R DIM5,R DIM6,R DIM7,R DIM8,R written written written written written written written written to to to to to to to to coil coil coil coil coil coil coil coil 00001) 00002) 00003) 00004) 00005) 00006) 00007) 00008) EX4 Read 10 Discrete (coils) from slave address 4 starting with coil 21 and store as discrete data in the MODCELL Mul
PAGE 267
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION B.4.2 Example 2 NOTE: The entry for input 1 must be all UPPER CASE (ASCII is case sensetive).
PAGE 268
Logic Functions - Book 1 APPENDIX B - MODBUS MASTER CONFIGURATION I14 I15 I16 I17 I18 I19 B-24 Count 2000 Date M,03/22/94 Floating Point 99230.0 Millisecond Time 11:23:45.
PAGE 269
Logic Functions - Book 1 APPENDIX C - BLOCK DATA APPENDIX C BLOCK DATA C.1 GENERAL This block data is provided to aid users needing to interpret the address of a database attribute. A full description of the LSP (Logical Source Pointer) four byte address is given in IB-23G001, Programmers Guide for ICN Communication Link. Table C-1.
PAGE 270
Logic Functions - Book 1 APPENDIX C - BLOCK DATA Table C-1.
PAGE 271
PAGE 272
The Company’s policy is one of continuous product improvement and the right is reserved to modify the information contained herein without notice, or to make engineering refinements that may not be reflected in this bulletin. Micromod Automation assumes no responsibility for errors that may appear in this manual. © 2004 MicroMod Automation, Inc. Printed in USA IB-23G600, Issue 10 3/2005 MicroMod Automation, Inc. 75 Town Center Drive Rochester, NY USA 14623 Tel. 585-321-9200 Fax 585-321-9291 www.