G2-2 Series Foundation Fieldbus (H1) Technical Manual Asset Library/TDG22FFTM1-0EN.pdf · G2-2...

TDG22FFTM1-0EN 08/08

Subject to change without notice

www.numatics.com/fieldbus

G2-2 Series Foundation Fieldbus (H1)

Technical Manual

G2-2 Series Foundation Fieldbus Technical Manual

Page 1

TDG22FFTM1-0EN 8/08



Table of Contents PAGE

About Foundation Fieldbus (FF H1).................................................................................................................................. 3 Overview ........................................................................................................................................................................ 3

G2-2 Introduction ............................................................................................................................................................... 4 Discrete I/O .............................................................................................................................................................. 5

Sub-base Connectors...................................................................................................................................................... 7 Z-Board™ and Solenoid Coil Connections to Output Drivers .................................................................................. 7 Z-Board™ Connectors .............................................................................................................................................. 8

Communication Module Configurations and Pin-Outs ..................................................................................................... 9 Foundation Fieldbus Communication Module (Node) ................................................................................................. 9 Communication Module Parts List .............................................................................................................................. 10

Communication Connector Pin-Out ........................................................................................................................11 Power Connector Pin-Out ........................................................................................................................................11 Ground Wiring......................................................................................................................................................... 12

Power Consumption..................................................................................................................................................... 13 External Fuse Sizing Guide Chart ........................................................................................................................... 14

Diagnostics – Communication Module ....................................................................................................................... 15 LED Functions........................................................................................................................................................ 15 Internal Fuses.......................................................................................................................................................... 16

MCM – Manual Configuration Module (Optional) .......................................................................................................... 17 Self-Test Mode ............................................................................................................................................................. 18

Digital I/O Modules......................................................................................................................................................... 19 Digital I/O Module Rules............................................................................................................................................ 19

One Input per Connector - 12mm Female Modules................................................................................................ 20 Two Inputs per Connector - 12mm Female Modules .............................................................................................. 21 Eight Inputs per Connector – Sub-D 15 Pin Female Modules ................................................................................ 22 Sixteen Inputs per Connector – Sub-D 25 Pin Female Modules ............................................................................. 23 Sixteen Inputs per Connector – Terminal Strip Modules ........................................................................................ 24 Sixteen Inputs per Connector – M23 19 Pin Female Module .................................................................................. 25 One Output per Connector - 12mm Female Modules ............................................................................................. 26 Two Outputs per Connector - 12mm Female Modules ........................................................................................... 27 Sixteen Outputs per Connector – Sub-D 25 Pin Female Module ............................................................................ 28 Sixteen Outputs per Connector – Terminal Strip Module....................................................................................... 29 Twenty-Two Outputs per Connector – Sub-D 25 Pin Female Module ................................................................... 30

Digital Input/Output Modules.................................................................................................................................... 31 One Input/One Output per Connector - 12mm Female Modules .......................................................................... 31 Eight Inputs/Eight Outputs per Connector - M23 19 Pin Female Module ............................................................ 32

I/O Module(s) Wiring Diagrams ..................................................................................................................................... 34 Device Descriptions and Methods ............................................................................................................................... 36 Create a Device Placeholder ........................................................................................................................................ 36 Commissioning a Device ............................................................................................................................................. 37

General Block Information ............................................................................................................................................... 42 MODES........................................................................................................................................................................ 42 LINK ACTIVE SCHEDULER.................................................................................................................................... 43

Link Master ...................................................................................................................................................................... 43 Block Instantiation ........................................................................................................................................................... 43 Capabilities ....................................................................................................................................................................... 44 Resource Block................................................................................................................................................................. 44

FEATURES and FEATURES_SEL ............................................................................................................................ 44 PlantWeb™ Alarms...................................................................................................................................................... 45

VMS Transducer Block..................................................................................................................................................... 49 Logic Transducer Block ................................................................................................................................................... 50

Logic Equations........................................................................................................................................................... 50 Channel Functions ....................................................................................................................................................... 50


Page 2

TDG22FFTM1-0EN 8/08



Logic Functions ........................................................................................................................................................... 51 Logic Operator Functions............................................................................................................................................ 52 Limits on Functions ..................................................................................................................................................... 52 Edge Detection Functions ........................................................................................................................................... 52 Clock Function............................................................................................................................................................. 53 Latching Functions ...................................................................................................................................................... 54 Status Propagation ....................................................................................................................................................... 55 Logic Execution Timing.............................................................................................................................................. 56 Error Handling............................................................................................................................................................. 56

Channels For Input And Output Blocks........................................................................................................................... 57 Latching ....................................................................................................................................................................... 58

Discrete Input Blocks (DI)............................................................................................................................................... 59 Discrete Output Blocks (DO)........................................................................................................................................... 59 Multiple Discrete Input Block (MDI) .............................................................................................................................. 59 Multiple Discrete Output Block (MDO) .......................................................................................................................... 59 Packed I/O Channels Using Regular DI/DO ................................................................................................................. 60 Multiple I/O – MDI/MDO Blocks.................................................................................................................................. 61 Introduction To Valve Control.......................................................................................................................................... 62

Alarms .......................................................................................................................................................................... 62 Variations On Valve Control ........................................................................................................................................ 63 Boolean Expressions.................................................................................................................................................... 64 Basic Valve Control ...................................................................................................................................................... 64 Open-Auto-Close ......................................................................................................................................................... 64 Alarm Variations .......................................................................................................................................................... 64 Output With Interlock.................................................................................................................................................. 65 Simple Valve Variations ............................................................................................................................................... 65 Permissive .................................................................................................................................................................... 65 Double Block And Bleed.............................................................................................................................................. 66 Motorized Valve ........................................................................................................................................................... 67 Heat Exchange Medium Selection .............................................................................................................................. 67

Foundation Fieldbus Configuration and Mapping........................................................................................................... 68 Example:.................................................................................................................................................................. 70

Appendix........................................................................................................................................................................... 73 Auto Initialization.................................................................................................................................................... 73

System Specifications ................................................................................................................................................... 74 Factory Defaults Settings ............................................................................................................................................. 75 Troubleshooting........................................................................................................................................................... 76 Device Manufacturer and Type Identifier.................................................................................................................... 77 Glossary of Terms ........................................................................................................................................................ 78

Technical Support............................................................................................................................................................. 79


Page 3

TDG22FFTM1-0EN 8/08



About Foundation Fieldbus (FF H1)

Overview

Foundation Fieldbus (FF H1) is an all-digital, serial, two-way, multidrop communication protocol that interconnects devices such as transmitters and valve controllers. It is a local area network (LAN) for instruments that enables basic control and I/O to be moved to the field devices. The Numatics G2-2 Foundation Fieldbus module uses Foundation Fieldbus technology developed and supported by Emerson Process Management and the other members of the independent Fieldbus Foundation.


Page 4

TDG22FFTM1-0EN 8/08



G2-2 Introduction

The G2-2 Series is a product line featuring a variety of valve configurations and electronic interface options. This fieldbus manifold series is capable of addressing a total of 48 I/O. The manifold can be viewed as having two sections to it, the Valve Side and the Discrete I/O Side. The Valve Side supports a maximum of 16 solenoid coils and the Discrete I/O Side supports a maximum of 6 modules totaling 16 Outputs, 32 Inputs, or various combinations. The Foundation Fieldbus (FF H1) communication module has two connectors: a 5-pin power connector and a 4-pin communication connector. Pin-outs for these, along with I/O connectors, are labeled on the side of the respective modules and in the Discrete I/O module section of this document. This manual addresses the specifics of configuring and commissioning the Numatics G2-2 Series product line configured with the Foundation Fieldbus communication interface. For more information relating to pneumatic valving and valve manifold assemblies, please refer to the Numatics Inc. Control Catalog.

Valve Side(Maximum of 16 Solenoids)

Communications Module

Discrete I/O Side(Maximum of 6 Modules)

Manual Configuration Module (MCM)

I/O PointLED StatusIndicator(s)

Discrete I/O Connectors

8 Connector I/O Module

Module/Network

Status LED's

FUSE 2+24V VLV/OUT

COMM. STATUS

+24V NODE/IN

FUSE 1Foundation Fieldbus


Page 5

TDG22FFTM1-0EN 8/08



G2-2 Electronics Modularity

Discrete I/O

The G2-2 Series product line is a completely modular system. As shown below, all of the G2-2 electronic modules plug together, allowing easy assembly and field changes. Additionally, all the PC boards containing active electronics (i.e. communication, I/O and MCM) are also modular allowing changes to be made without the need to dismantle the manifold.


Page 6

TDG22FFTM1-0EN 8/08



Pneumatic Valve Manifold

The pneumatic valve manifold is also modular. The valve solenoid coil connections are made automatically using Z-Board™ technology (plug together PC boards which allow internal connection from solenoid coils to output drivers without the use of wires), this allows easy assembly and field changes.


Page 7

TDG22FFTM1-0EN 8/08



Sub-base Connectors

Z-Board™ and Solenoid Coil Connections to Output Drivers

Z-Board™ plug together technology connects all valve solenoids to the valve coil output drivers, located in the communication node. The valve solenoid coil output drivers are comprised of one output word, bits 0-15. Outputs connect directly to the Z-Boards™. The first output connects to the “14” (A) solenoid on the valve closest to the communication node.

DOUBLE

"Z-BOARD"SINGLE

"Z-BOARD"

DOUBLE

"Z-BOARD"SINGLE

"Z-BOARD"

14(A) Solenoid Pin No. 1Earth Ground Pin No. 3

12(B) Solenoid Pin No. 2Common Pin No. 4

Plug-in Manifold withIntergral "Z-Board"Eliminates Wiring

Output Solenoid CoilConnector

A single solenoid valve’s coil is always on the “14” end.


Page 8

TDG22FFTM1-0EN 8/08



Z-Board™ Connectors The 2005/2012/2035 valve series utilizes 2 different Z-Board™ designs to achieve the single and double solenoid output functions that yield the possible 16 single, 8 double, or any combination of valve solenoid coil output capabilities.

Single Z-Board™ Double Z-Board™

The G2-2 Foundation Fieldbus node is capable of driving up to 16 valve solenoid coils.


Page 9

TDG22FFTM1-0EN 8/08



Communication Module Configurations and Pin-Outs

Foundation Fieldbus Communication Module (Node)

This module is the communication interface to the manifold. It contains communication electronics and short circuit protected solenoid coil output drivers. This communication module can be configured via software.

+24V NODE/IN

COMM STATUS

+24V VLV/OUTFUSE 1

FUSE 2

Foundation Fieldbus


Page 10

TDG22FFTM1-0EN 8/08



Communication Module Parts List

Below is a 3D diagram of the G2-2 communication module. Also listed are the part numbers to the individual components.

Communication Module Kit

Foundation Fieldbus 240-217

Foundation Fieldbus with Logic Transducer Enabled

240-243

Communication Module Parts List

Detail No. No. Required Part Name Part No.

1 1 Ground Cup Washer 128-162

2 2 Screw 127-318

3 1 Backplane Board Assembly 256-1036

4 1 Housing (Not Sold Separately) N/A

5 1 Gasket 113-531

6 4 Screw 127-1047

7 1 LED Label Cover Lens 122-1252

8 1 Cover Gasket 113-533

9 1 Cover 105-416

Foundation Fieldbus Communication Board 256-1035 10 1

Foundation Fieldbus Communication Board with Logic Transducer Enabled 256-1043

11 1 Screw 127-794

12 1 4 Pin MINI Communication Connector 140-810

13 1 5 Pin MINI Power Connector 140-809

14 1 Ground Screw 127-176

16 1 Converter Board 256-1058

17 1 Valve and Output 10 Amp Fuse 140-934

18 1 Node and Input 4 Amp Fuse 140-933


Page 11

TDG22FFTM1-0EN 8/08



Communication Connector Pin-Out

Pin No. Function Description

1 FB-B Non-Polarized Network Signal

2 FB-A Non-Polarized Network Signal

3 SHIELD Cable Shield

4 NOT USED Not Used

Power Connector Pin-Out

Pin No. Function Description

1 NO CONNECTION Not Used

2 0VDC Common 0VDC Common, for Valves, I/O, and Node Power

3 Earth Ground Protective Earth (Case Ground)

4 +24VDC

(Node and Inputs) Voltage Used to Power Discrete Inputs and Node Electronics

5 +24VDC

(Valves and Outputs) Voltage Used to Power Outputs (Valve Coils and Discrete Outputs)

!

• Maximum current capacity on the 0VDC common pin of power connector is 8 Amps. The combined draw of the +24VDC Valves & Outputs and +24VDC Node & Inputs pins cannot exceed 8 Amps, at any given moment in time.

• The Node & Inputs pin supplies power to the node electronics. This pin must be powered at all times for communication node to be functional.

Foundation Fieldbus


Page 12

TDG22FFTM1-0EN 8/08



Ground Wiring

All Numatics Inc. communication nodes should be grounded during the installation process. These grounding guidelines can be found in National Electrical code IEC 60204-1 or EN 60204-1. There also is an, “ATTENTION: CONNECT TO EARTH GROUND FOR PROPER GROUNDING OF UNIT”, label attached to the chassis ground connection point on the G2-2 series communication node housing. This label also points out where the grounding guidelines can be found.

• Proper grounding will alleviate and prevent many intermittent problems with network communication.

• When grounding to a machine frame, please ensure that the machine frame itself is already properly grounded.

• Better grounding can be achieved when larger diameter (lower gauge) wire is used.

!

Foundation Fieldbus


Page 13

TDG22FFTM1-0EN 8/08



Power Consumption

Power Connection

Power Connector Pin No.

Description

5 24 VDC Power for Valves and Discrete Outputs

4 24 VDC Power for Inputs and Node Electronics

Discrete I/O Module(s) Power Jumper

All of Numatics, Inc., G2-2 I/O modules have a selectable power source jumper. This jumper determines which Power connector pin will power these modules.

This option allows the user to select how each specific module will be powered during different conditions (i.e. E-Stop). Each I/O module can be set-up independently allowing individual Output and/or Input modules to remain active if needed.

Power Rating

• Maximum system current capability is 8 Amps. Care should be taken not to exceed 8 Amp draw through the 0VDC common pin (Current through all +24 VDC Pins combined).

• Discrete I/O current draw is dependent on the device(s) connected. It is critical to know what these values are in order to remain safely within the 8 Amp limitation.

• Loads should not draw more than 0.5 Amps of current from any one individual discrete output point. (Contact factory for higher current capabilities)

+24VDC (Valves and Outputs)

Power Connector Voltage Tolerance Current Power Solenoid Valve Coil 2002 (Each) 24VDC +10%/-15% 0.021 A 0.5 Watts

Solenoid Valve Coil 2005 (Each) 24VDC +10%/-15% 0.056 A 1.35 Watts



Solenoid Valve Coil ISO - SPA (Each) 24VDC +10%/-15% 0.167 A 4.0 Watts

Discrete Output 24VDC - 0.5 A max. * 12 Watts max. *

+24VDC (Node and Inputs)

Power Connector Voltage Tolerance Current Power Node 24VDC +/- 10% 0.040 A 0.96 Watts

Discrete I/O Module (Each) 24VDC - 0.006 A 0.14 Watts

Discrete I/O Status LEDs (Each) 24VDC - 0.015 A 0.36 Watts

* Please consult the factory for output current requirements greater than 0.5 Amps.

Recommended External Fuses

External fuses should be chosen based upon the physical manifold configuration. Please refer to page 14 for the fuse sizing chart.

• Power consumption for each Discrete I/O point is dependent on the specific current draw of input sensor devices and output loads. Please consult the factory for output current requirements greater than 0.5 Amps.


Page 14

TDG22FFTM1-0EN 8/08



External Fuse Sizing Guide Chart

Power Consumption - Power Connector Pin for Valves and Outputs

Description Current

Number of Solenoid Valve Coils Energized Simultaneously

___ X 0.105 A (2012 and 2035 Series) = __________Amps

___ X 0.042 A (2005 Series) = __________Amps

___ X 0.031 A (2002 Series) = __________Amps

+ Total load current drawn by simultaneously energized Discrete Outputs

with Discrete Outputs Power Jumper in “SP” Position (Factory Default). =

__________Amps +

Total load current drawn by Sensor Devices from Discrete Inputs source with Discrete Input Power Jumper in “SP” Position.

= __________Amps

Total: __________Amps

Surge Compensation: X 1.25

Suggested External +24 VDC (Valves and Outputs) Fuse Value: __________Amps

Power Consumption - Power Connector Pin for Node and Inputs

Description Current

Communication Node Power Consumption = .040 Amps

+

Total load current drawn by simultaneously energized Discrete Outputs with Discrete Outputs Power Jumper in “UP” Position.

= __________Amps

+

Total load current drawn by Sensor Devices from Discrete Inputs source with Discrete Inputs Power Jumper in “UP” Position (Factory Default).

= __________Amps

+

Number of I/O modules installed ___ X 0.006 A = __________Amps

+

Number of Discrete I/O Status LEDs simultaneously on ___ X 0.015 A = __________Amps

Total: __________Amps

Surge Compensation: X 1.25

Suggested External Pin +24 VDC (Node and Inputs) Fuse Value: __________Amps

• The standard power jumper configuration for all Output Modules is “SP”.

• The standard power jumper configuration for all Input Modules is “UP”.

• At any given moment in time, the combined current draw through +24VDC (Valves and Outputs) pin and +24VDC (Node and Inputs) pin cannot exceed 8 Amps. Therefore, the combined value of the external fuses on the two +24VDC pins should not exceed 8 Amps.

• The internal fuses are installed to protect against fire damage due to catastrophic failure of internal components. External fuses are recommended for protection against power supply failure, over-current conditions, etc…


Page 15

TDG22FFTM1-0EN 8/08



Diagnostics – Communication Module

LED Functions

Upon power up, the LEDs indicate the status of the unit. There are five LEDs on the G2-2 Foundation Fieldbus node; one for Comm Status, two for internal fuse integrity and two for Aux. Power status.

LED Name Color Status Description

OFF The module has encountered a serious hardware error. Fieldbus board is not able to communicate with I/O board.

ON Normal operation; the device GPIO transducer block actual mode is in Auto.

COMM STATUS Green

Flashing

Device GPIO transducer block is in Out of Service (OOS) mode or Fieldbus board is not able to communicate with I/O board anymore. Also upon DC power up, there are burst of 5 quick flashes indicating device in Self Test Mode.

OFF Internal fuse F1 is OK (valid only when power is applied to +24V VLV / OUT pin on Aux. Power connector).

FUSE 1

Red ON

Internal fuse F1 is open; No power is internally provided to valves or outputs. Communication NOT affected.

OFF No DC Power present at +24V VLV / OUT pin on Power connector. +24V VLV/OUT

Green ON DC Power applied to +24V VLV / OUT pin on Power Connector.

OFF Internal fuse F2 is OK (valid only when power is applied to +24V NODE / IN pin on Power connector.

FUSE 2

Red ON

Internal fuse F2 is open; No power is internally provided to node electronics or inputs. Communication Node will not function.

OFF No DC Power present at +24V NODE / IN pin on Power connector. +24V NODE/IN Green

ON DC Power applied to+24V NODE / IN pin on Power connector.

+24V NODE/IN

COMM STATUS

+24V VLV/OUTFUSE 1

FUSE 2

FUSE 1+24V VLV/OUT

+24V NODE/INFUSE 2

COMM STATUS

Foundation Fieldbus


Page 16

TDG22FFTM1-0EN 8/08



Internal Fuses

Fuse Function and Description

Fuse No.

Description Size Part No. Type

F1 Fuse for Power connector pin for Valves and Outputs. 10 A max. fast acting

140-934 MINI ATO

F2 Fuse for Power connector pin for Node and Inputs. 4 A max.

fast acting 140-933 MINI ATO

Fuse(F1)

Fuse(F2)


Page 17

TDG22FFTM1-0EN 8/08



MCM – Manual Configuration Module (Optional)

The MCM is an optional module that allows the user to manually set self test mode. The MCM consists of two DIP switch sets (SW1 and SW2) and two rotary switches (SW3 and SW4).

MCM Module Part Numbers

Description Part Number Complete Module 239-1384

Replacement Board 256-684

(SW2)(SW3)

DIP Switch (SW1)

DIP Switch

(SW4)

All DIP switches shown in the "OFF" position

Rotary Switch

Rotary Switch

1 432 5 6 7 8

ON1 432 5 6 7 8

ON


Page 18

TDG22FFTM1-0EN 8/08



Self-Test Mode

An internal diagnostic tool can also be enabled using the optional MCM module. This tool allows the user to confirm that all of the Inputs and Outputs on the manifold are fully functional without needing a network connection or controller. There are two test modes that the user can choose using SW2-8. The “Output” test mode tests all the outputs by sequentially turning them ON one at a time. The “Input/Output” test mode tests the inputs by causing all of the outputs to toggle between even and odd values when any input is made.

To use the Self-Test Mode, the user must first set some initial conditions using the MCM module. Follow these steps to obtain the needed initial condition settings. Remember to remove power from the manifold before making changes to the MCM when setting these initial conditions.

1) Disconnect power and air from the manifold! 2) Record current MCM settings. 3) Set the rotary switches to 99 (SW3 and SW4). 4) Make sure that SW1-5, SW2-1, and SW2-7 are in the “ON” position. 5) Select the desired test mode with SW2-8 (see table below)

Switch Testing Mode

Setting Description

Output Off Sequentially turns all the outputs ON and OFF.

SW2-8 Input/ Output

On Causes all of the odd outputs to come on and stay on until an input is made. When an input is made, the outputs will toggle to the even outputs.

6) Make sure that all of the other switches are in the “OFF” position.

The initial conditions are now set. To enable the Self-Test Mode, apply power to the manifold and make the following changes while the module status LED is blinking (within 2 to 5 seconds of power up):

1) Set SW2-6 to the “ON” position. 2) Set SW2-7 to the “OFF” position.

Once Self-Test Mode is enabled, the comm. status LED will flash green until Self-Test Mode is terminated by removing power to the unit. Remember to return the MCM settings to their original settings to return the communication node to normal operation.

!• Air should be disconnected to the manifold when attempting to run the

Self-Test Mode to prevent unwanted motion.

• Communication lines should be disconnected before attempting to run the Self-Test Mode.


Page 19

TDG22FFTM1-0EN 8/08



Digital I/O Modules

Digital I/O Module Rules

The maximum number of I/O modules that can be used on the Discrete I/O side of the manifold is six. If the optional Manual Configuration Module (MCM) is used, a maximum of five I/O modules may be installed. Modules can be connected in any combination and sequence of inputs and outputs up to the logical limitations totaling 16 Outputs or 32 Inputs.

Damage will occur if Discrete I/O and MCM Modules are inserted or removed with power applied.

Input Module Types

Output Module Types

Input/Output Module Types


Page 20

TDG22FFTM1-0EN 8/08



Digital Input Modules

One Input per Connector - 12mm Female Modules

Module Part No.

Replacement I/O Board Part No.

I/O Type Short Circuit Protection

Internal Status Bits

Input Points Module Size

239-1304 240-100 NPN (Sinking) N/A N/A

239-1305 240-101 PNP (Sourcing) N/A N/A 4 Narrow

239-1312* 240-109 NPN (Sinking) N/A N/A

239-1313* 240-110 PNP (Sourcing) N/A N/A

240-130 240-134 NPN (Sinking) Yes N/A

240-131 240-135 PNP (Sourcing) Yes N/A

8 Wide

Power Jumper Settings

U P S

U P S U P S

Jumper Settings

Jumpered Pins

Description

“U” and “P”

Factory Default - Input power is supplied by the +24 VDC (Node and Inputs) pin of the Auxiliary Power Connector. This allows input power to be supplied by the same connection which powers the communication node (Unswitched Power).

“S” and “P”

Input power is supplied by the +24 VDC (Valves and Outputs) pin of the Auxiliary Power connector. This allows input power to be supplied by the same connection that powers the valve coils and discrete outputs (Switched Power).

LED Status

LED Name Color Status Description OFF Input module currently not sensing an input signal.

ON Input module currently sensing an input signal. Input Status Green

FLASHING Sensor device source voltage sensing (Pin No. 1) is externally short circuited.

*Wide I/O Modules may contain two jumpers; one for each group of four connectors


Page 21

TDG22FFTM1-0EN 8/08



Two Inputs per Connector - 12mm Female Modules

Module Part No.





239-1308 240-104 NPN (Sinking) N/A N/A


239-1316* 240-113 NPN (Sinking) N/A N/A

239-1317* 240-114 PNP (Sourcing) N/A N/A

239-2500 240-125 PNP (Sourcing) Yes N/A

239-2564 240-129 PNP (Sourcing) Yes 8

240-132 240-136 NPN (Sinking) Yes N/A

16 Wide


U P S

U P S U P S

Jumper Settings

Jumpered Pins

Description

“U” and “P”


“S” and “P”


LED Status






Page 22

TDG22FFTM1-0EN 8/08



Eight Inputs per Connector – Sub-D 15 Pin Female Modules

Module Part No.





239-1868 240-189 NPN (Sinking) N/A N/A


Byte X

Byte X + 1

PIN 15

PIN 1

Jumper Settings

U P SU P SU P S 0VDC

15

EG N/U0VDC11

0VDC

15

EG 0VDC

11

N/U

Jumper Settings

Jumpered Pins

Description

“U” and “P”


“S” and “P”


“EG” and “15” Factory Default – Use this jumper setting when replacing boards with part numbers 256-796 (239-1868) or 256-798 (239-1870). This setting connects Pin 15 to Earth Ground, i.e. Protective Earth or chassis ground.

“0VDC” and “15” Use this jumper setting when replacing boards with part numbers 256-147 (239-1466) or 256-149 (239-1480). This setting connects Pin 15 to 0VDC.

“0VDC” and “11” Factory Default – Use this jumper setting when replacing boards with part numbers 256-796 (239-1868) or 256-798 (239-1870). This setting connects Pin 11 to 0VDC.

“N/U” and “11” Use this jumper setting when replacing boards with part numbers 256-147 (239-1466) or 256-149 (239-1480). This setting makes Pin 11 Not Used (N/U).


Page 23

TDG22FFTM1-0EN 8/08



Sixteen Inputs per Connector – Sub-D 25 Pin Female Modules

Module Part No.





239-1869 240-190 NPN (Sinking) N/A N/A


PIN 1

PIN 25

Jumper Settings

U P SU P SU P S

0VDC25

EG 0VDC

21

N/U

0VDC25

N/UEG 0VDC21

Jumper Settings

Jumpered Pins

Description

“U” and “P”


“S” and “P”


“EG” and “25” Factory Default – Use this jumper setting when replacing boards with part numbers 256-797 (239-1869) or 256-799 (239-1871). This setting connects Pin 25 of the Sub-D connector to Earth Ground (EG).

“0VDC” and “25” Use this jumper setting when replacing boards with part numbers 256-148 (239-1467) or 256-150 (239-1481). This setting connects Pin 25 of the Sub-D connector to 0VDC.

“0VDC” and “21” Factory Default – Use this jumper setting when replacing boards with part numbers 256-797 (239-1869) or 256-799 (239-1871). This setting connects Pin 21 of the Sub-D connector to 0VDC.

“N/U” and “21” Use this jumper setting when replacing boards with part numbers 256-148 (239-1467) or 256-150 (239-1481). This setting makes Pin 21 of Sub-D connector Not Used (N/U).


Page 24

TDG22FFTM1-0EN 8/08



Sixteen Inputs per Connector – Terminal Strip Modules

Specifications - Wire Range: 14 to 30 AWG - Strip Length: 5mm

Module Part No.





239-2304 256-894 NPN (Sinking) N/A N/A


16 INPUT TERMINAL STRIP

Input Mapping

Byte X Discrete Inputs

Byte X+1 Discrete Inputs


UP

S

UP

S

UP

S

Jumper Settings

Jumpered Pins

Description

“U” and “P”


“S” and “P”


LED Status


Input Status Green ON Input module currently sensing an input signal.


Page 25

TDG22FFTM1-0EN 8/08



Sixteen Inputs per Connector – M23 19 Pin Female Module

Module Part No.





239-2382 240-193 PNP (Sourcing) N/A N/A 16 Wide

16 INPUT PNP19 PIN FEMALE

Input Mapping

Byte X Discrete Inputs

Byte X+1 Discrete Inputs


UP

S

UP

S

UP

S

Jumper Settings

Jumpered Pins

Description

“U” and “P”


“S” and “P”


LED Status



Connector Pin-Out


Page 26

TDG22FFTM1-0EN 8/08



Digital Output Modules

One Output per Connector - 12mm Female Modules

Module Part No.




Output Points Module Size

239-1307 240-103 PNP (Sourcing) Yes 1 4 Narrow

239-1315* 240-112 PNP (Sourcing) Yes 2 8 Wide


U P S

U P S U P S

Jumper Settings

Jumpered Pins

Description

“S” and “P”

Factory Default - Output power is supplied by the +24 VDC (Valves and Outputs) pin of the Auxiliary Power Connector. This allows discrete outputs to be disabled without disabling power to communication node (Switched Power).

“U” and “P”

Output power is supplied by the +24 VDC (Node and Inputs) pin of the Auxiliary Power Connector. This allows discrete outputs to be supplied by the same connection that powers the communication node (Unswitched Power). Outputs will not be disabled separately from the communication node.

LED Status

LED Name Color Status Description OFF Output module currently not supplying an output signal.

Output Status Green ON Output module currently supplying an output signal.



Page 27

TDG22FFTM1-0EN 8/08



Two Outputs per Connector - 12mm Female Modules

Module Part No.






239-1319* 240-116 PNP (Sourcing) Yes 4 16 Wide


U P S

U P S U P S

Jumper Settings

Jumpered Pins

Description

“S” and “P”


“U” and “P”


LED Status





Page 28

TDG22FFTM1-0EN 8/08



Sixteen Outputs per Connector – Sub-D 25 Pin Female Module

Module Part No.





239-1994 240-187 PNP (Sourcing) Yes 8 32 Wide


Jumper 1 - Selects source of output power for

outputs 17-32.

Jumper 2 - Selects source of output power for

outputs 1-16.

Fuse(s)(4.0 A)

Part No.140-933

Local 12mm Aux.Power Connector

Side View

End View

U P S

E

U P S

E

Jumper Settings

Jumpered Pins

Description

“E” and “P”

Factory Default - Output power is supplied by pin No. 1 and pin No. 4 of the local 12mm Auxiliary Power Connector. Outputs can be enabled/disabled via the Local 12mm Auxiliary Power Connector (External Power).

“S” and “P”

Output power is supplied by the +24 VDC (Valves and Outputs) pin of the Auxiliary Power Connector. This allows discrete outputs to be disabled without disabling power to communication node (Switched Power).

“U” and “P”


LED Status



OFF Internal fuse is OK (only when using the 4-pin 12mm power connector). Fuse Status Red

ON Internal fuse is open (only when using the 4-pin 12mm power connector).

OFF Output module is currently not being supplied power through the 12mm connector. PWR Green

ON Output module is currently being supplied power through the 12mm connector.


Page 29

TDG22FFTM1-0EN 8/08



Sixteen Outputs per Connector – Terminal Strip Module

Specifications - Wire Range: 14 to 30 AWG - Strip Length: 5mm

Module Part No.






16 OUTPUT TERMINAL STRIPPNP (SOURCING)

Jumper Settings

U P SJ1

J2J3U P S

J1

J3 J2

Jumper Settings

Jumpered Pins

Description

“S” and “P”


“U” and “P”


“BOTH” Factory Default – Output power is determined by jumper J1.

“NEITHER”

Outputs receive their power from an external source. User must connect +24VDC power to the “+” terminal on the black terminal strip to supply output power. If more than one power supply is used, both 0 VDC terminals should be connected together.

LED Status


Output Status Amber ON Output module currently supplying an output signal.


Page 30

TDG22FFTM1-0EN 8/08



Twenty-Two Outputs per Connector – Sub-D 25 Pin Female Module

Module Part No.





239-1460 240-188 PNP (Sourcing) Yes 6 22 Wide

25 PIN SUB-D CONNECTOR

4 PIN POWER CONNECTOR


Local 12mm Aux.Power Connector

Fuse(4.0 A)

Part No. 140-933 U

P

S

UP

S

X

X

Jumper Settings

Jumpered Pins

Description

“X” and “P”

Factory Default - Output power is supplied by pin No. 1 of the local 12mm Auxiliary Power Connector. Outputs can be enabled/disabled via the Local 12mm Auxiliary Power Connector (External Power).

“S” and “P”

Output power is supplied by the +24 VDC (Valves and Outputs) pin of the Auxiliary Power Connector. This allows discrete outputs to be disabled without disabling power to communication node (Switched Power).

“U” and “P”



Page 31

TDG22FFTM1-0EN 8/08



Digital Input/Output Modules

One Input/One Output per Connector - 12mm Female Modules

Internal Status Bits Module

Part No. Replacement I/O Board

Part No. I/O Type

Short Circuit Protection

Inputs Outputs

Input Points

Output Points

Module Size

239-2517 240-126 PNP (Sourcing) Yes 0 0 8 8 Wide




U P S

U P S U P S

Jumper Settings

Jumpered Pins

Description

“S” and “P”

Factory Default - Power is supplied by the +24 VDC (Valves and Outputs) pin of the Auxiliary Power Connector. This allows discrete outputs/inputs to be disabled without disabling power to communication node (Switched Power).

“U” and “P”

Power is supplied by the +24 VDC (Node and Inputs) pin of the Auxiliary Power Connector. This allows discrete outputs/inputs to be supplied by the same connection that powers the communication node (Unswitched Power). Outputs/Inputs will not be disabled separately from the communication node.

LED Status




OFF Output module currently not supplying an output signal. Output Status Amber

ON Output module currently supplying an output signal.


Page 32

TDG22FFTM1-0EN 8/08



Eight Inputs/Eight Outputs per Connector - M23 19 Pin Female Module

Internal Status Bits Module

Part No. Replacement I/O Board

Part No. I/O Type

Short Circuit Protection

Inputs Outputs

Input Points

Output Points

Module Size


4 PIN MALE

19 PIN FEMALE

LED'S


Fuse(4.0 A)

Part No.140-933

(Located on Horizontal Circuit Board)

U

P

S

X

UP

SX

Jumper Settings

Jumpered Pins

Description

“X” and “P”

Factory Default - Power is supplied by pin No. 1 of the local 12mm Auxiliary Power Connector. Outputs/Inputs can be enabled/disabled via the Local 12mm Auxiliary Power Connector (External Power).

“S” and “P”

Power is supplied by the +24 VDC (Valves and Outputs) pin of the Auxiliary Power Connector. This allows discrete outputs/inputs to be disabled without disabling power to communication node (Switched Power).

“U” and “P”

Output/Input power is supplied by the +24 VDC (Node and Inputs) pin of the Auxiliary Power Connector. This allows discrete outputs/inputs to be supplied by the same connection that powers the communication node (Unswitched Power). Outputs/Inputs will not be disabled separately from the communication node.

Connector Pin-Out


Page 33

TDG22FFTM1-0EN 8/08



Eight Inputs/Eight Outputs per Connector - M23 19 Pin Female Module Continued

Configuration Jumper Settings

Fuse(4.0 A)

Part No.140-933

12

34

J1

J2

12

3

J2

1 2 31 2 3

4J1

Jumper Settings

Jumpered Pins

Description

“2” and “4” Factory Default - Allows Pin No. 12 of the M23 connector to be internally supplied from the +24 VDC (Node and Inputs) pin of the communication node Auxiliary Power Connector.

“1” and “2” Allows Pin No. 12 of the M23 connector to be externally supplied from Pin No. 4 of the local 12mm Auxiliary Power Connector.

J1

“2” and “3” Converts Pin No. 12 of the M23 connector into an Earth Ground. This is necessary when using a distribution block.

“1” and “2”

Factory Default - Allows Pin No. 19 of the M23 connector to be externally supplied from Pin No. 1 of the local 12mm Auxiliary Power Connector. NOTE: Power jumper MUST be set to “X and P”.

J2

“2” and “3”

Allows Pin No. 19 to be internally supplied from the communication node Auxiliary Power Connector. NOTE: Power jumper MUST be set to “S and P” or “U and P”.

LED Status



OFF Output module currently not supplying an output signal. Output Status Amber

ON Output module currently supplying an output signal.

OFF Internal fuse is OK (only when using the 4-pin 12mm power connector). Fuse Status Red

ON Internal fuse is open (only when using the 4-pin 12mm power connector).

OFF Output module is currently not being supplied power through the 12mm connector. PWR Green

ON Output module is currently being supplied power through the 12mm connector.


Page 34

TDG22FFTM1-0EN 8/08



I/O Module(s) Wiring Diagrams

Sinking/Sourcing Definitions

Sinking Descriptions • NPN

• Switching Negative

• Positive Common

Sourcing Descriptions • PNP

• Switching Positive

• Negative Common

Sinking (NPN) Input Connection

Sourcing (PNP) Input Connection

Mechanical Sensor TypeElectric Sensor Type

2

4

3

1

2

4

3

1

LOAD

LOAD

Mechanical Sensor TypeElectric Sensor Type

2

4

3

1

2

4

3

1


Page 35

TDG22FFTM1-0EN 8/08



I/O Module(s) Wiring Diagrams Continued

Sinking (NPN) Output Connection

Sourcing (PNP) Output Connection


Page 36

TDG22FFTM1-0EN 8/08



Node Commissioning Device Descriptions and Methods

A Device Description is similar to a driver for the device. For fieldbus devices, the Device Description includes the calibration procedures, parameter procedures, and other information required by the control system to communicate with the fieldbus device. Standard Device Descriptions are provided by the Fieldbus Foundation and optional, incremental Device Descriptions are provided by the device manufacturer. Device Descriptions are written in the Device Description Language (DDL) and the host system such as the DeltaV system uses library functions called Device Descriptions Services to read the Device Descriptions. Device Description technology enables interoperability among fieldbus devices. Interoperability, a key benefit of fieldbus technology, is the ability of a host system to operate multiple devices, independent of manufacturer, on the same fieldbus segment without loss of minimum functionality.

The DeltaV system supports a number of fieldbus devices from different manufacturers. The device description files necessary to support these devices are included in the DeltaV install image. If a fieldbus device is not included in the DeltaV install image, you must install the device description for that device. The device description is specific to the device type and revision. Download the device description files from www.easydeltav.com. The device description files must include a file with an .fhx extension to work with the DeltaV system. You can download the device description files to a disk, CD, or directory on your system.

For DeltaV versions before v9.3, use the DeltaV Explorer to add the device type to the DeltaV Explorer library. Install the device description files on the ProfessionalPLUS workstation and the DeltaV system synchronizes the device descriptions on the other workstations. Refer to DeltaV Explorer help for information on how to use the Add Device Type command.

For DeltaV version starting v9.3, AMS v9.0 must be installed to add the Device Description. Use the ‘Add Device Type’ functionality of the AMS software.

Create a Device Placeholder

Device support files must be installed before you can add a device to the segment or create a device placeholder. The DeltaV system includes built-in support for a number of fieldbus devices from different device manufacturers.

About Device Placeholders A device placeholder is an electronic representation of a device that exists in the DeltaV database with no associated physical device. You can use a placeholder to configure block parameters offline and have your control strategy in place prior to attaching the device to the segment. When you are ready, you can attach the device to the segment and use the DeltaV system to reconcile any differences between the placeholder and the device when you commission the device.

Note: The use of placeholders is optional and depends on the size and requirements of your fieldbus application. However, it is recommended that you use placeholders for large applications. If you do not want to use placeholders, you can attach your devices directly to the segment.

1. Click Start | DeltaV | Engineering | DeltaV Explorer to open DeltaV Explorer.

2. Navigate to the fieldbus ports. The ports are under the fieldbus H1 card. The card is under the I/O subsystem.


Page 37

TDG22FFTM1-0EN 8/08



3. Right-click the port to which you want to attach the device placeholder and select New Fieldbus Device. The Fieldbus Device Properties dialog opens.

4. Enter the appropriate information about the device in the dialog box. The DeltaV system selects an address. You can customize this field, but it is not necessary. Select the device type and revision based on the type of device as follows:

Manufacturer: Numatics Device Type: Numatics Fieldbus Transmitter Device Revision: 1 The Numatics Fieldbus Transmitter is Link Master capable, and to enable this check the box for the option “Use as backup Link Master.” The device will be automatically assigned the address 20.

Fieldbus devices often provide error detection for a variety of device conditions. Select the Alarms and Displays tab in the Fieldbus Device Properties dialog to enable Device Alarms to be reported by the device.

Note: The alarms and displays tab is shown because the Numatics Fieldbus Transmitter supports device alerts. Device alerts are supported by Series 2 H1 cards.

Each device can also be configured with a primary control display and faceplate. DeltaV software includes a standard device faceplate.

5. Click OK to add the device placeholder to the segment. The device appears as a decommissioned device on the segment.

6. When device alarms are enabled, alarms become visible in the right pane in DeltaV Explorer when you select the Fieldbus Device Alarms icon for the device. Select an alarm and right-click properties to enable or disable it or to change the alarm's priority.

Commissioning a Device

Commissioning a device assigns it an address on the segment and makes the device available to the DeltaV system. You use the DeltaV Explorer to commission devices. You can reconcile any differences between the device and the placeholder during the commissioning process. After commissioning a device, you download.

1. Attach the device to the segment.

2. Click Start | DeltaV | Engineering | DeltaV Explorer to open the DeltaV Explorer.

3. The device should appear under Decommissioned Fieldbus Devices. It may take a minute for the device to appear. Tip: Press the F5 key to update the list.

4. The device must be in the Standby state before you can commission it. To determine if a device is in Standby, select Decommissioned Devices, click View | Details from the menu bar, and be sure that the words "Standby Fieldbus Device" appear under Type in the right pane.


Page 38

TDG22FFTM1-0EN 8/08



If the device is not in Standby, select the device in the right pane, click the right mouse button, and select Standby. It may take a minute or so for the device to transition to Standby.

5. Now be sure that the decommissioned device's properties, Device Type, Manufacturer, and Device Revision, match the placeholder properties. To check the properties, select the item, click the right mouse button, and select Properties. If necessary, edit the placeholder properties to match the device properties.

6. Select the device from the Decommissioned Fieldbus Devices list and drag it to the placeholder.

The Device Commissioning Wizard - Start opens.

7. Read the information on the Device Commissioning Wizard - Start dialog and click Next to open the Device Commissioning Wizard – Reconcile Device dialog.


Page 39

TDG22FFTM1-0EN 8/08



We will use this dialog to reconcile any differences between the placeholder and the device.

8. Click the Reconcile Device button. (If you do not click this button and click Next instead, the parameters in the device will remain as they are and will overwrite the parameters in the placeholder when you commission the device.) The Reconcile Device dialog shows two sets of fieldbus device configuration parameters: parameters in the placeholder and parameters in the device. This dialog allows you to transfer parameters from a placeholder to a device and edit parameters in the device.


Page 40

TDG22FFTM1-0EN 8/08



9. The following figure shows the dialog for reconciling resource block parameters.

Click the Help button and read about reconciling device parameters. Click the Transducer block in the upper left corner of the Reconcile dialog to reconcile the transducer block parameters. Read the device documentation before reconciling transducer block parameters.

10. Click OK when you are finished reconciling parameters and then click Finish to commission the device.


Page 41

TDG22FFTM1-0EN 8/08



It may take a little while to commission the device. Several factors contribute to the time it takes to commission. Among these are the number of function blocks and devices and the time it takes for devices to move through the various device states.


Page 42

TDG22FFTM1-0EN 8/08



General Block Information Modes

The Resource, Transducer, and all function blocks in the device have modes of operation. These modes govern the operation of the block. Every block supports both automatic (AUTO) and out of service (OOS) modes. Other modes may also be supported.

Changing Modes

To change the operating mode, set the Target Mode to the desired mode. After a short delay, the parameter Actual Mode should reflect the mode change if the block is operating properly.

Permitted Modes

It is possible to prevent unauthorized changes to the operating mode of a block. To do this, configure Permitted Mode to allow only the desired operating modes. It is recommended to always select OOS as one of the permitted modes. Also only OOS and Auto are the possible permitted modes for Resource, GPIO, Logic and VMS transducer blocks.

Types of Modes

For the procedures described in this manual, it will be helpful to understand the following modes:

• AUTO

The functions performed by the block will execute. If the block has any outputs, these will continue to update. This is typically the normal operating mode.

• Out of Service (OOS)

The functions performed by the block will not execute. If the block has any outputs, these will typically not update and the status of any values passed to downstream blocks will be “BAD”. To make some changes to the configuration of the block, change the mode of the block to OOS. When the changes are complete, change the mode back to AUTO.

• MAN

In this mode, variables that are passed out of the block can be manually set for testing or override purposes. Other Types of Modes are Cas, RCas, ROut, IMan and LO. MAN mode is only applicable to DI, DO, MDI and MDO function blocks.

NOTE: When an upstream block is set to OOS, this will impact the output status of all downstream blocks. The figure below depicts the hierarchy of blocks: If for example Resource Block is in OOS mode, the DI, DO, MDI and MDO will all go to actual mode of OOS.


Page 43

TDG22FFTM1-0EN 8/08



Link Active Scheduler

The NUMATICS Fieldbus Transmitter can be designated to act as the backup Link Active Scheduler (LAS) in the event that the Primary LAS is disconnected from the segment. As the backup LAS, the NUMATICS Fieldbus Transmitter will take over the management of communications until the host is restored.

Link Master A Link Master device controls when devices access the fieldbus and executes the link schedule which synchronizes communications with function block execution on the fieldbus. The H1 card or any field device that supports Link Master functionality can function as a Link Master device. Only one Link Master device can be active at a time on the fieldbus segment. This device is called the LAS. The DeltaV system can configure one Link Master device to function as the primary Link Master device. When the primary Link Master device is attached to the fieldbus, it takes over as the LAS. The H1 card always functions as the primary Link Master. When the H1 card is redundant, the secondary H1 functions as the primary Link Master if the primary H1 card fails. All other Link Master devices are backup Link Master devices that can take over as LAS only if the primary Link Master device fails. One backup Link Master field device is supported per fieldbus segment. The fieldbus devices communicate on a schedule (executed by the LAS) as required to implement the control strategy.

Block Instantiation The NUMATICS Fieldbus Transmitter is pre-configured with 12 function blocks instantiated at the factory. The default configuration is listed below that includes 4 DI and 8 DO function blocks. This device supports a maximum of 12 function bocks.

• 4 Discrete Input Blocks

• 8 Discrete Output Blocks

• 0 Multiple Discrete Input Block

• 0 Multiple Discrete Output Block

These function blocks can be deleted or added in any order by the Hosts that support Block Instantiation.

The NUMATICS Fieldbus Transmitter supports the use of Function Block Instantiation. When a device supports block instantiation, the number of blocks and block types can be defined to match specific application needs. The number of blocks that can be instantiated is only limited by the amount of memory within the device and the block types that are supported by the device. Instantiation does not apply to standard device blocks like the Resource, I/O Transducer, and Logic Transducer, VMS Transducer Block.


Page 44

TDG22FFTM1-0EN 8/08



Capabilities Virtual Communication Relationship (VCRs)

There are a total of 20 VCRs. Two are permanent and 18 are fully configurable by the host system. 25 link objects are available.

Block Execution times

Discrete Input = 70 ms Discrete Output = 70 ms Multiple Discrete Input = 70 ms Multiple Discrete Output = 70 ms

Resource Block FEATURES and FEATURES_SEL

The parameters FEATURES and FEATURE_SEL determine optional behavior of the NUMATICS Fieldbus Transmitter.

FEATURES

The FEATURES parameter is read only and defines which features are supported by the NUMATICS Fieldbus Transmitter. Below is a list of the FEATURES of the NUMATICS Fieldbus Transmitter.

REPORTS

The NUMATICS Fieldbus Transmitter supports alert reports. The Reports option bit must be set in the features bit string to use this feature. If it is not set, the host must poll for alerts.

SOFT WRITE LOCK and HARD WRITE LOCK

Inputs to the security and write lock functions include the hardware security switch, the hardware and software write lock bits of the FEATURE_SEL parameter, the WRITE_LOCK parameter, and the DEFINE_WRITE_LOCK parameter.

The WRITE_LOCK parameter prevents modification of parameters within the device except to clear the WRITE_LOCK parameter. During this time, the block will function normally updating inputs and outputs and executing algorithms. When the WRITE_LOCK condition is cleared, a WRITE_ALM alert is generated with a priority that corresponds to the WRITE_PRI parameter. The FEATURE_SEL parameter enables the user to select a hardware or software write lock or no write lock capability. To enable the hardware security function, enable the HW_SEL bit in the FEATURE_SEL parameter. When this bit has been enabled the WRITE_LOCK parameter becomes read only and will reflect the state of the hardware switch. In order to enable the software write lock, the SW_SEL bit must be set in the FEATURE_SEL parameter. Once this bit is set, the WRITE_LOCK parameter may be set to “Locked” or “Not Locked.” Once the WRITE_LOCK parameter is set to “Locked” by either the software or the hardware lock, all user requested writes as determined by the DEFINE_WRITE_LOCK parameter shall be rejected.


Page 45

TDG22FFTM1-0EN 8/08



The DEFINE_WRITE_LOCK parameter allows the user to configure whether the write lock functions (both software and hardware) will control writing to all blocks, or only to the resource and transducer blocks. Internally updated data such as process variables and diagnostics will not be restricted by the security switch.

PlantWeb™ Alarms The Resource Block will act as a coordinator for PlantWeb alarms. There will be three alarm parameters (FAILED_ALARM, MAINT_ALARM, and ADVISE_ALARM) which will contain information regarding some of the device errors which are detected by the transmitter software. There will be a RECOMMENDED_ACTION parameter which will be used to display the recommended action text for the highest priority alarm. FAILED_ALARM will have the highest priority followed by MAINT_ALARM and ADVISE_ALARM will be the lowest priority.

PlantWeb General tab

• IB Comm Protocol Rev Mismatch

• Internal Communication Failure

• IO Board NV Memory Failure

• NV Write Deferred

• NV Memory Failure

• Electronics Failure

• PWA Simulate Active

Logic Transducer Block

• Prescaler Overflow

• Logic Block Configure Error

PlantWeb GPIO tab

• GPIO Block Config Error – slot configuration mismatch between “Actual Module Reported” & “Saved Module” reported

• Input Failure

• Output Failure

• Input Pulse Count Limit Alert – this alert is activated if the input parameter “Pulse Counter” exceeds the user selectable parameter “Pulse Count Limit”. This is available for all 32 inputs

• Output Pulse Count Limit Alert – this alert is activated if the output parameter “Pulse Counter” exceeds the user selectable parameter “Pulse Count Limit”. This is available for all 16 outputs

PlantWeb VMS tab

• Process Valve Life Cycle Exceeded – this is activated once the parameter “valve counter” exceeds user settable parameter “valve counter limit”. This is available for all 8 VMS channels.

• Time in Position Limit Exceeded – this is activated once the parameter “Time in Position” exceeds user settable parameter “Time in Position Limit”. This is available for all 8 VMS channels.

• Travel Time Open Limit Exceeded – this is activated once the “Travel time Open” parameter exceeds the “Calibrated Travel Time Open” + user settable “Tolerance Travel Time Open”. This is available for all 8 VMS channels.

• Travel Time Close Limit Exceeded – this is activated once the “Travel time Close” parameter exceeds the “Calibrated Travel Time Close” + user settable “Tolerance Travel Time Close”. This is available for all 8 VMS channels.


Page 46

TDG22FFTM1-0EN 8/08



• Break Time Open Limit Exceeded – this is activated once the “Break time Open” parameter exceeds the “Calibrated Break Time Open” + user settable “Tolerance Break Time Open”. This is available for all 8 VMS channels.

• Break Time Close Limit Exceeded – this is activated once the “Break time Close” parameter exceeds the “Calibrated Break Time Close” + user settable “Tolerance Break Time Close”. This is available for all 8 VMS channels.

• Travel Deviation; Lost Position – this alert is activated if the device detects incorrect valve position. For example, device has commanded the valve to OPEN position and device limit switch has confirmed it to be in OPEN position. Now for any reason, the device detects the valve position not be in OPEN any more without changing the command, this will trigger Travel Deviation, Lost Position alert.

• Initialization Failure – during initialization, the actuator is controlled (by this device) to OPEN/CLOSE 3 times & the OPEN/CLOSE inputs are used to measure the average travel & break times. Failure for this task to be performed successfully will enable this PWA.

FAILED_ALARMS

A failure alarm indicates a failure within a device that will make the device or some part of the device non-operational. This implies that the device is in need of repair and must be fixed immediately. There are five parameters associated with FAILED_ALARMS specifically, they are described below.

FAILED_ENABLED

This parameter contains a list of failures in the device which makes the device non-operational that will cause an alarm to be sent.

FAILED_MASK

This parameter will mask any of the failed conditions. A bit on means that the condition is masked out from alarming and will not be reported.

FAILED_PRI

Designates the alarming priority of the FAILED_ALM. The default is 0 and the recommended value is between 8 and 15.

FAILED_ACTIVE

This parameter displays which of the alarms is active. Only the alarm with the highest priority will be displayed. This priority is not the same as the FAILED_PRI parameter described above. This priority is not user configurable.

FAILED_ALM

Alarm indicating a failure within a device which makes the device non-operational.

MAINT_ALARMS

A maintenance alarm indicates the device or some part of the device needs maintenance soon. If the condition is ignored, the device will eventually fail. There are five parameters associated with MAINT_ALARMS, they are described below.


Page 47

TDG22FFTM1-0EN 8/08



MAINT_ENABLED

The MAINT_ENABLED parameter contains a list of conditions indicating the device or some part of the device needs maintenance soon. If the condition is ignored, the device will eventually fail.

MAINT_MASK

The MAINT_MASK parameter will mask any of the failed conditions. A bit on means that the condition is masked out from alarming and will not be reported.

MAINT_PRI

MAINT_PRI designates the alarming priority of the MAINT_ALM. The default is 0 and the recommended value is 3 to 7.

MAINT_ACTIVE

The MAINT_ACTIVE parameter displays which of the alarms is active. Only the condition with the highest priority will be displayed. This priority is not the same as the MAINT_PRI parameter described above. This priority is not user configurable.

MAINT_ALM

An alarm indicating the device needs maintenance soon. If the condition is ignored, the device will eventually fail.

Advisory Alarms

An advisory alarm indicates informative conditions that do not have a direct impact on the device's primary functions. There are five parameters associated with ADVISE_ALARMS, they are described below.

ADVISE_ENABLED

The ADVISE_ENABLED parameter contains a list of informative conditions that do not have a direct impact on the device's primary functions.

ADVISE_MASK

The ADVISE_MASK parameter will mask any of the failed conditions. A bit on means the condition is masked out from alarming and will not be reported.

ADVISE_PRI

ADVISE_PRI designates the alarming priority of the ADVISE_ALM. The default is 0 and the recommended value is 1 or 2.

ADVISE_ACTIVE

The ADVISE_ACTIVE parameter displays which of the advisories is active. Only the advisory with the highest priority will be displayed. This priority is not the same as the ADVISE_PRI parameter described above.

This priority is not user configurable.


Page 48

TDG22FFTM1-0EN 8/08



ADVISE_ALM

ADVISE_ALM is an alarm indicating advisory alarms. These conditions do not have a direct impact on the process or device integrity.

Recommended Actions for PlantWeb Alarms

RECOMMENDED_ACTION

The RECOMMENDED_ACTION parameter displays a text string that will give a recommended course of action to take based on which type and which specific event of the PlantWeb alarms is active.

Alarms

Use the following steps to configure the alarms, which are located in the Resource Block.

• Set the resource block to OOS.

• Set WRITE_PRI to the appropriate alarm level (WRITE_PRI has a selectable range of priorities from 0 to 15. Set the other block alarm parameters at this time.

• Set CONFIRM_TIME to the time, in 1/32 of a millisecond, that the device will wait for confirmation of receiving a report before trying again (the device does not retry if CONFIRM_TIME is 0).

• Set LIM_NOTIFY to a value between zero and MAX_NOTIFY. LIM_NOTIFY is the maximum number of alert reports allowed before the operator needs to acknowledge an alarm condition.

• Enable the reports bit in FEATURE_SEL.

• Set the resource block to AUTO.


Page 49

TDG22FFTM1-0EN 8/08



VMS Transducer Block The NUMATICS Fieldbus Transmitter can be operated in two different modes concurrently:

• General Purpose I/O (GPIO) – in this mode the maximum number of I/Os can be used is 32x16. Diagnostics are limited to:

o Pulse count – number of state changes that have occurred (high-low-high or low-high-low) o Open/Short Circuit Detection – open circuit detection only for pneumatics output o Fault conditions – in the event that internal Fieldbus and I/O boards communication is lost,

outputs can be programmed to move to a Fail Safe position (energize, de-energize, no action).

• VMS (Valve Monitoring System) – any I/Os used by VMS are not available for the GPIO, VMS can use a maximum of 16 inputs and 16 outputs. Any unassigned I/Os will default to GPIO mode. The user can also select which output or outputs should be associated to particular inputs (1 for OPEN/1 for CLOSE). In this mode, the user can operate 2 types of actuators:

o Single acting actuator – 2x1 (2 inputs, 1 output)

� One output – for use with single acting (spring-return) actuators. In this application, the output is energized to OPEN the actuator and de-energized to CLOSE the actuator.

� Two digital inputs – two sensors/switches are needed for detecting actuator position (1 for OPEN and 1 for CLOSE).

o Double acting actuator – 2x2 (2 inputs, 2 outputs)

� Two outputs – for use with double acting actuators. In this application, output #1 is energized to OPEN the actuator. Possible output states are:

o Both outputs OFF o Output #1 = ON and output #2 = OFF: to OPEN actuator o Output #1 = OFF and output #2 = ON: to CLOSE actuator

� Two digital inputs – two sensors/switches are needed for detecting actuator position

(1 for OPEN and 1 for CLOSE)

o Diagnostics available in VMS mode are: � Travel times open and close � Break times open and close � Cycle count and cycle count limit � Lost position

o Command was sent to CLOSE actuator. Inputs indicate valve is in the closed position. Next update cycle inputs indicate valve is not closed, but was never given command to change state.

o Command was sent to OPEN actuator. Inputs indicate valve is in open position. Next update cycle inputs indicate valve is not open, but was never given command to change state.


Page 50

TDG22FFTM1-0EN 8/08



Logic Transducer Block

Logic Equations

The NUMATICS Fieldbus Transmitter provides for 16 Logic Equations and 16 Output Equations. User can only change these equations if the block has been licensed at the factory. See Resource Block parameter XD_OPTION if the block has been licensed. The Output Equations drive the hardware outputs. Each logic equation consists of up to 80 characters with a semicolon as the last character. The equations are evaluated every 500 msec. However this may vary based on the number and complexity of the equations used. The logic block consists of variables that are connected to the hardware I/O, obtain values or send values over the bus and internally calculated variables.

The value or state of the logic block variables can be communicated on the bus by assigning the appropriate channel number of a DI or MDI block. The DO variables can be set externally by assigning the appropriate channel number in a DO or MDO function block. The DO function blocks do not drive the outputs directly. The DO function block can drive the output by referencing the appropriate DO variable in the output equations.

The following characters are allowed in a logic equation:

• Uppercase and lowercase alphabet, case insensitive, used to specify functions

• Digits 0-9, used to specify channel numbers and unsigned integer constants

• Comma, used to separate parameters in a function parameter list

• Parentheses() used to define the extent of the parameter list of a function

• Semicolon; used to terminate an equation

• Space (not tab), ignored by parser, may be used to make an equation more readable but counts as a character

The following characters are specifically not allowed in a logic:

• The period (dot) character is not allowed. There are no decimal numbers.

• The unary minus (-) character is not allowed. There are no negative integers.

• The math operators (+, -, *, /, **) are not allowed, nor are symbols for any logic operators (&, |, <, >, ...).

Functions must be from the list of Logic Functions below, and must have the specified number of parameters.

Channel Functions

The Logic Transducer Block can only reference channels 1-80.

The following functions read channel value and status. The number of instances of these functions is unlimited, except for PS. A channel value and status is set by the I/O processor at the beginning of an equation evaluation cycle, by the equations as they complete evaluation, or by macrocycle evaluations of any DO blocks attached to channels 33 through 48. The status of channels 33-48 is always good, even if the DO block has a bad status.

IN - The input hardware sets the values of channels 1-32. Configured DI blocks may specify these channels in order to read the specified hardware input. The value of an input may be referenced in an equation by the IN (i) function, where the channel number is placed between the parentheses. The range of ‘i’ is 1 to 32. Multiple references to any channel are allowed.


Page 51

TDG22FFTM1-0EN 8/08



ICR, ICF - I/O samples are taken every millisecond, which is considerably faster than equation executions. It is possible for an input to turn on and turn off during an equation evaluation cycle, so that it would not be seen by an IN (i) function. Each input has a counter for transitions (rise or fall). A transition is based on the output of the debounce filter, not the raw input. Filtering can be set to zero. The counter is read and cleared at the beginning of each evaluation cycle. The method relies completely on the counter and does not use the latch configuration. The ICR (i) function is true for one evaluation cycle if a rising transition occurred, and its opposite ICF (i) is true for a falling transition.

PS - When the hardware input consists of a continuous train of pulses at a rate less than 2 PPS, a prescaler can be used to reduce the pulse rate to something that does not change faster than the equation evaluation rate. The function is PS (i, divisor) where ‘i’ is the channel number (1-32) and ‘divisor’ is the number of pulses to count before setting its output true for one equation evaluation cycle. The counter rolls over at ‘divisor’ and keeps counting. The user must assure that there is always at least one execution cycle with a false value from PS for every true value. If the pulse rate exceeds the divisor times two, then the function returns Bad status and optionally a PlantWeb alert can be sent. Only ten of these functions are available because they require storage for previous values.

DO - Channels 33-48 are zero unless set by configured DO or MDO function blocks. This allows a function block link to set the value from a remote function block output or HMI screen switch. The values may be referenced in equations by the DO (d) function. The range of ‘d’ is 1 to 16. To directly drive an output from an external device the Output Equation would reference DO(d).

NOTE: The value of DO can change during an evaluation cycle if the macrocycle evaluates the DO block. This may require referencing the DO value in a single equation to “save” its state.

EQ - Channels 49-64 are set by the result of an equation specified by up to 80 characters and stored in parameter EQx, where x is the equation number. The equation results are available as a discrete value and status in parameter EQx_VALUE. They may be referenced by the EQ (u) function. The range of ‘u’ is 1 to 16. These are intended to be intermediate values that are used because the value is used in other equations or because the equation text was too long. A configured DI block may use an equation channel (range 49 to 64) in order to make the result available to other devices.

OUT – References outputs 1 to 16 (channels 65-80). The value of an output may be referenced in an equation by the OUT (i) function, where the channel number is placed between the parentheses. The range of ‘i’ is 1 to 16. Multiple references to any channel are allowed.

Logic Functions

A function has a name and a set of one or more arguments contained within a closed set of parentheses. The seven channel reference functions (IN, ICF, ICR, PS, DO, EQ, and OUT) have been described above. These are the only functions that take a channel number as an argument. The other functions require functions for all arguments unless the last argument is a constant number.

When a function is evaluated, it leaves its true or false value behind to be evaluated by the next function or used as the result of evaluating the equation. This is the result of using a simple and fast evaluation method known as Reverse Polish Notation (RPN). The RPN method requires nesting the functions like OR(IN(1),IN(2)) rather than using operator notation like IN(1) | IN(2). This can lead to the following:

AND(IN(1),OR(IN(2),AND(IN(3),OR(IN(4),AND(IN(5),OR(IN(6),AND(IN(7), IN(8))))))));

The equation is evaluated by evaluating the deepest functions first, IN(7) and (IN(8). If they are both true then the AND function evaluates to true. Then IN(6) is evaluated, then the OR evaluates to true, and so on working up from the deepest level in reverse order until the first (and top level) AND can be evaluated. The result is stored in the channel specified by EQx, which contains the text of the equation as explained above.


Page 52

TDG22FFTM1-0EN 8/08



Drawn as a ladder logic, the equation would look like the figure below:

Logic Operator Functions The following operators require a minimum of 2 and a maximum of 10 functions between the parentheses, each separated by a comma.

AND ( ) - Performs the logical ‘and’ of the argument functions.

OR ( ) - Performs the logical ‘or’ of the argument functions.

XOR ( ) - Performs the logical exclusive ‘or’ of the argument functions. An XOR function is false if all of the arguments are the same value, either all true or all false. Otherwise, it is true.

The following unary operator requires just one argument:

NOT ( ) - Performs the logical inversion of the argument function.

Limits on Functions

There is no limit to the number of functions described above, as long as they fit within the 32 equations described by 80 character strings. The following functions are limited to 10 of each within the entire set of 32 equations. This is because the functions require memory to store constants or last values. The size of a memory element is 16 bits, so the maximum size of a constant value is 65535. There are no signed numbers.

Edge Detection Functions

RISE ( ) - This function evaluates as false unless the previous value of the argument was false and now the argument evaluates to true. This function is true for only one equation evaluation cycle. It will always be false on the following cycle.

FALL( ) - This function evaluates as false unless the previous value of the argument was true and now the argument evaluates to false. This function is true for only one equation evaluation cycle. It will always be false on the following cycle.


Page 53

TDG22FFTM1-0EN 8/08



Clock Function

NOTE: All arguments of time are in 500 msec.

CLOCK (onTime,offTime) - The parameters onTime and offTime are constants. This function does not take other functions. CLOCK runs unconditionally with a period determined by onTime plus offTime. Time is specified in 500ms increments. The function will be true for onTime in 500ms increments. On the first evaluation cycle after the device starts up, the onTime interval will start because all of the dynamic values are zero. Use the NOT function to invert this behavior, and swap the on and off times.

Counter Functions

CTU (clock, reset, target)- The parameters clock and reset are functions. The target is a 16 bit constant. Whenever reset is true, the internal counter is set to zero and the value of the function is false. The value of clock is ignored while reset is true. If reset is false, the internal counter will increment once for each rise of the clock parameter. When the internal counter equals the target value, the value of the function is true and the counter stops counting in order to avoid rollover. The value of the function is false if the internal counter does not equal the target.

The internal counter is not visible from Fieldbus and is not available to any other function. The value of the internal counter is not retained during a device restart. This function is not suitable for a totalizer, but can be used as a prescaler to adjust the external mechanical counter rate. The pulse rate must be less than one per second.

The following expression increments the counter whenever hardware input 1 turns on. The counter is reset whenever hardware input 2 is on. If input one is from a mechanical displacement flowmeter that delivers 76.54 pulses per gallon, then the highest flow rate is 0.7 gallons per minute. The following equation will deliver one 0.5 second pulse per 100 gallons:

OUT1_EQ contains CTU(IN(1),OUT(1),7654);

Starting at zero, 7653 pulses go by and then pulse 7654 turns on the output. On the next evaluation cycle, the counter is reset because Output 1 is on. This is a result of the order of execution of equations. Output 1 becomes true because the count is reached, but the OUT(1) function has already been evaluated as false. The counter must reset before the next pulse comes in. The output pulse may be extended with a TP function.

TON (power, target) - Whenever power is false, the value of the internal timer is set to zero and the value of the function is false. When power is true then the value of the function will become true after the target amount f time has elapsed. This condition persists as long as power is true. The timer resets when power is false.

The following equation filters the level switch in a stirred tank so that high level bouncing of the float does not create nuisance alarms for the operator. Hardware input 1 senses the level switch and hardware output 1 drives the alarm annunciator with its big horn. The level switch must stay closed for 5 minutes before the alarm is energized and the operator is startled by the horn.

OUT1_EQ contains: TON(IN(1),600);

TOF (power, target) - Whenever power is true, the value of the internal timer is set to the target and the value of the function is true. The value of the function will become false after the target amount of time has elapsed. This condition persists as long as power is false.


Page 54

TDG22FFTM1-0EN 8/08



The following equation keeps the outlet valve open for about 5 seconds after the pump is shut off, so that the pressure across the pump can equalize. Hardware output 1 runs the pump and hardware output 2 opens the valve

OUT1_EQ contains: <something that controls the pump>;

OUT2_EQ contains: TOF(OUT(1),10);

TP (power, target) - Whenever power transitions from false to true, the value of the internal timer is set to the target and the value of the function is true. The value of the function will become false after the target amount of time has elapsed. This function is similar to TOF except that a timing cycle is only initiated by the rise of power. Power may go false or stay true without affecting the timing cycle. The cycle is restarted anytime that power goes true after the function has had at least one evaluation cycle as false.

Latching Functions

A latch is a two state device that can be set to true or reset to false. It will retain its state when both commands are false. It will not retain its state through a device restart. The initial state is Reset. Two latch functions are required to define the behavior when both commands are true, depending on which state should be dominant. The result of the function is the state of the latch.

SR (set, reset) - The parameters set and reset are functions. If both are true then set wins and the result of the function is true.

RS (reset, set) - The parameters set and reset are functions. If both are true then reset wins and the result of the function is false.

Shifting Functions

A shift register is a set of bits that moves each bit to the next bit position when the command to shift is given. The vacant bit is filled with the value of the input. The NUMATICS Fieldbus Transmitter shift functions contain 8 bit registers. The bit parameter selects the bit in the register to test. The value of the function is the value of the tested bit. The shift may be to the left or the right. The following table shows the state of the register for three shifts after the register has been reset. The input is true during the first shift evaluation and false thereafter. The right most bit is bit 1 and the left most bit is bit 8.

Direction Reset Shift 1 Shift 2 Shift 3 Left 00000000 00000001 00000010 00000100

Right 00000000 10000000 01000000 00100000

The reset parameter clears the register, overriding both input and shift. Reset is an optional parameter, but the function can be written with three parameters or four. Do not use an extra comma if reset is omitted.

The register data will be cleared on a processor restart (i.e. power cycle).

SHL (input, shift, reset, testbit) - The parameters input, shift, and reset are functions. The parameter testbit is a constant that is constrained to be in the range of 1 to 8. The reset function is optional. If reset is present and true, the 8 bit register is cleared to zero and the result of the function is false.


Page 55

TDG22FFTM1-0EN 8/08



Otherwise, if shift is true then bit 7 will be moved to bit 8, bit 6 to bit 7, bit 5 to bit 6, bit 4 to bit 5, bit 3 to bit 4, bit 2 to bit 3, bit 1 to bit 2, and the value of input will become the value of bit 1. Then the bit specified by testbit will be tested to determine the value of the function.

SHR (input, shift, reset, testbit) - The parameters input, shift and reset are functions. The parameter testbit is a constant that is constrained to be in the range of 1 to 8. The reset function is optional. If reset is present and true, the 8 bit register is cleared to zero and the result of the function is false.

Otherwise, if shift is true then bit 2 will be moved to bit 1, bit 3 to bit 2, bit 4 to bit 3, bit 5 to bit 4, bit 6 to bit 5, bit 7 to bit 6, bit 8 to bit 7, and the value of input will become the value of bit 8. Then the bit specified by testbit will be tested to determine the value of the function.

The following procedure is used to enter the logic equations.

1. Set MODE_BLK.TARGET to OOS 2. Enter the equations in parameters EQn or OUTn_EQ where n=1 to 16. Each equation ending with

a semicolon. 3. Set the MODE_BLK.TARGET to AUTO

The equations will then be evaluated and the status of the evaluation shown in the parameter PARSE_RESULT. If any errors were found, the block will remain in the OOS mode.

Status Propagation

The contact and Boolean value has a binary value and a good/bad status.

A status is applied to a channel value in one of the following ways:

The hardware input device maybe able to tell if it is shorted or open, in addition to on or off. If the hardware cannot tell then the status is always good, unless a device failure prevents reading the I/O data. The evaluation of an equation propagates either Good Non-cascade or Bad, both Non-specific.

Each function that is evaluated determines both a value and a status of either good or bad. The functions that provide status are the functions that test a channel number - IN, ICF, ICR, OUT, DO, PS and EQ. If any of the function’s parameters have a Bad or Uncertain status with any sub-status then the function terminates and returns a bad status, otherwise it returns a good value and status.

When an equation (set of functions) is evaluated, if a function returns a bad status then evaluation of that equation stops, and the equation channel status is set to Bad, Non-specific. If evaluation goes to completion, the channel status will be set to Good Process, Non-specific, not limited.

Status propagates forward, in the direction of the last output equation. If a function references an equation that is the equation being evaluated or a later equation, then the status of that equation will be ignored. The function will use the last good value of the referenced equation and call its status Good. This prevents forward references to equations that reference this equation from locking both equations into Bad status if either ever sets Bad status.

During initialization of the logic transducer block, before the first execution, each equation channel status is set to Bad, Non-specific, constant and the value is set to False.


Page 56

TDG22FFTM1-0EN 8/08



Logic Execution Timing

The Logic transducer block reads the hardware inputs, processes the equations and drives the outputs on a continuous cycle. The cycle time or frequency of execution will vary depending on the number and type of logic functions used in the equations.

Error Handling

The syntax of the entered equation is parsed when the target mode is transitioned from OOS to AUTO. Each equation is checked in order, and when an error is encountered in an equation, the parsing is suspended for the remaining equations, and the target mode is set back to OOS. The equation where the problem was encountered is indicated along with a message as shown in the table below.

Bounds checking on the values of parameters used in the functions are checked during run-time when ACTUAL MODE is AUTO. Errors of this type will be indicated by a bad status in the equations computed value.

Condition Status response No semi-colon appears in the equation. Missing semi-colon.

More left parenthesis than right parenthesis. Un-matched (. More right parenthesis than left parenthesis. Un-matched ).

A comma placed without a preceding function parameter. Badly placed comma. Open and Closed parenthesis without a parameter or statement

contained. Empty ().

A semicolon is contained prior to finishing an expression. Badly placed semicolon. A function call is missing one or more parameters. Too few parameters in function.

A bad character is present, or a parameter appears outside of a function call.

Syntax error.

An unknown function is called out. Unknown function. An opening parenthesis is located after the closing parenthesis

of a function call. Badly placed (.

A function call contains too many parameters. Too many parameters in function. A decimal number was found where an integer was expected. Invalid number. A function result was used as a function parameter where a

literal integer number was expected. Invalid parameters in function.

A function has been used more than the maximum allowed instances.

Insufficient resources.

An equation has been changed, but has not yet been parsed. Set Mode to Auto All equations were parsed successfully. Equation completed.


Page 57

TDG22FFTM1-0EN 8/08



Channels For Input And Output Blocks The table below lists all input/output channels available in this device. Individual Input and Output Blocks will use a subset which depends on the particular blocks individual characteristics. The channels supported are different for each block type. Operation of individual input/output blocks is covered in preceding sections.

Ch

ann

el

Description DI

DO

MD

I

MD

O

Ch

ann

el

Description DI

DO

MD

I M

DO

Ch

ann

el

Description DI

DO

MD

I

MD

O

1 Input 1 X X 41 DO 9 X 81 IN Packed 1 X 2 Input 2 X X 42 DO 10 X 82 IN Packed 2 X 3 Input 3 X X 43 DO 11 X 83 IN Packed 3 X 4 Input 4 X X 44 DO 12 X 84 IN Packed 4 X 5 Input 5 X X 45 DO 13 X 85 IN MDI 1 X 6 Input 6 X X 46 DO 14 X 86 IN MDI 2 X 7 Input 7 X X 47 DO 15 X 87 IN MDI 3 X 8 Input 8 X X 48 DO 16 X 88 IN MDI 4 X 9 Input 9 X X 49 EQ 1 X X 89 DO Packed 1 X 10 Input 10 X X 50 EQ 2 X X 90 DO Packed 2 X 11 Input 11 X X 51 EQ 3 X X 91 DO MDO 1 X 12 Input 12 X X 52 EQ 4 X X 92 DO MDO 2 X 13 Input 13 X X 53 EQ 5 X X 93 DO MDI 1 X 14 Input 14 X X 54 EQ 6 X X 94 DO MDI 2 X 15 Input 15 X X 55 EQ 7 X X 95 EQ MDI 1 X 16 Input 16 X X 56 EQ 8 X X 96 EQ MDI 2 X 17 Input 17 X X 57 EQ 9 X X 97 EQ Packed 1 X 18 Input 18 X X 58 EQ 10 X X 98 EQ Packed 2 X 19 Input 19 X X 59 EQ 11 X X 99 OUT MDI 1 X 20 Input 20 X X 60 EQ 12 X X 100 OUT MDI 2 X 21 Input 21 X X 61 EQ 13 X X 101 OUT Packed 1 X 22 Input 22 X X 62 EQ 14 X X 102 OUT Packed 2 X 23 Input 23 X X 63 EQ 15 X X 103 VMS 1 Command X 24 Input 24 X X 64 EQ 16 X X 104 VMS 2 Command X 25 Input 25 X X 65 Output 1 X X 105 VMS 3 Command X 26 Input 26 X X 66 Output 2 X X 106 VMS 4 Command X 27 Input 27 X X 67 Output 3 X X 107 VMS 5 Command X 28 Input 28 X X 68 Output 4 X X 108 VMS 6 Command X 29 Input 29 X X 69 Output 5 X X 109 VMS 7 Command X 30 Input 30 X X 70 Output 6 X X 110 VMS 8 Command X 31 Input 31 X X 71 Output 7 X X 111 VMS 1 Position X X

32 Input 32 X X 72 Output 8 X X 112 VMS 2 Position X X

33 DO 1 X 73 Output 9 X X 113 VMS 3 Position X X 34 DO 2 X 74 Output 10 X X 114 VMS 4 Position X X 35 DO 3 X 75 Output 11 X X 115 VMS 5 Position X X 36 DO 4 X 76 Output 12 X X 116 VMS 6 Position X X 37 DO 5 X 77 Output 13 X X 117 VMS 7 Position X X 38 DO 6 X 78 Output 14 X X 118 VMS 8 Position X X 39 DO 7 X 79 Output 15 X X 119 VMS Command Packed X 40 DO 8 x 80 Output 16 X X 120 VMS Command MDO X


Page 58

TDG22FFTM1-0EN 8/08



Latching

Reading a channel value will reset channel latch. If multiple input blocks ( DI , MDI) refer to the same input they will interfere with their latches, this behavior is undefined. If you want to use latches do not refer to the same input twice.


Page 59

TDG22FFTM1-0EN 8/08



Discrete Input Blocks (DI) The DI blocks are used to communicate the current value of a contact, the state of one of the Boolean equations, or the state of an output. The DI block chooses the value through the Channel parameter. Alternatively, the DI block can be configured to pass 8 values in a packed format to the host system (DeltaV) by using channels 81-84,97,98,101,102. To set the channel number, use the following procedure for each DI block.

1. Set MODE_BLK.TARGET to OOS 2. Select the Channel parameter 3. Select the desired channel number 4. Set MODE_BLK.TARGET to AUTO

Discrete Output Blocks (DO) The digital output blocks are used to receive a value from another device to be used to either drive a contact output or to use in the logic equations. The DO blocks make their values available to the NUMATICS Fieldbus Transmitter by placing the value in a variable called DO (n) where n=1 to 16. Like the DI block, all eight outputs can be communicated in a packed format by selecting the appropriate channel number. The DO block does not drive the outputs directly but sets the state of the internal variables DO(n). To drive an output from the DO block, the DO(n) variable is placed in one of the output equations.

OUT1_EQ = DO(1);

Multiple Discrete Input Block (MDI) The MDI block allows 8 values with their status in one block with 8 individual outputs.

Multiple Discrete Output Block (MDO) The MDO block allows 8 output values with their status in one block with 8 individual inputs.


Page 60

TDG22FFTM1-0EN 8/08



Packed I/O Channels Using Regular DI/DO • DeltaV does not support FF Spec MDI and MDO shadow blocks

• DeltaV could use regular DI and DO blocks and pack it with Multiple I/O information. One DI/DO could use 8 I/Os.

• DeltaV has BFI and BFO supporting blocks to pack and unpack the information just as easy.

• Regular DI/DO Channel can have any value between 0 and 255 along with its status(DS-66).

• In case of Packed I/O, each bit of Unsigned 8 value represent I/O value reducing it to only Zero or One.


Page 61

TDG22FFTM1-0EN 8/08



Multiple I/O – MDI/MDO Blocks

• MDI and MDO are specially designed for Manufacturing Automation I/O applications.

• Each MDI and MDO can support up to 8 I/Os.

• Non DeltaV hosts should be able to use these blocks instead of Packing DI/DO.

• MDI/MDO - each I/O has Unsigned 8 value along with individual 8 bit status (DS-66).


Page 62

TDG22FFTM1-0EN 8/08



Introduction To Valve Control Industrial valves have two general classifications, regulating and block. A regulating valve is designed to be stable at any one of a nearly infinite set of positions between open and closed. They are mostly used in control loops so that nonlinearity and friction are corrected by feedback control. A block valve is designed to be either tight shut or wide open. They are mostly used to change the configuration of process equipment, such as a heat exchanger that can be used to heat or cool, but not both at the same time. Block valves configure steam in and condensate out for heating or chilled brine in and return for cooling. Regulating valves are being used as block valves when the actual position of the valve must be known, but analog outputs are used.

Block valves generally have some kind of switch that is closed in the open position and another switch for the closed position. These are called confirm contacts even if they are proximity switches. The valve position is unknown when neither switch is closed. If the valve actuator has adequate power then it is rare to find both switches open, except for a period of time known as the travel time when the valve is moving from one position to the other. Actuators can be hydraulic pistons, pneumatic pistons or diaphragms, or motor driven screws, in order of increasing travel time. More than 80% of the actuators use compressed, oil and water free air for power. Valves are referred to as air to open or air to close.

A block valve may be controlled by push buttons or by a toggle switch. There is no contactor as there is for a motor. Permissive and interlock circuits may be applied. The actuator may require power to be applied to open it, with a spring to return it to the closed position, or vice-versa. A block valve may be required to stay in its last position on air or power failure, so there is one pilot actuator to open it and another pilot actuator to close it. The pilot actuator is not usually designed for continuous power, so a few second pulse may be all that is required. The actuator is called a pilot because it just directs the flow of fluid power, as by pushing a spool valve from one side to the other. The spool valve directs the main flow to one side of the main actuator or the other, like the pilot valve in a power steering system. Two pilot solenoid valves are required if the spool latches in position, or one if the spool has a spring return.

There are at least three permutations of any valve circuit: 1. Steady or pulse output to the pilot solenoid (or whatever, piezoelectric bars are in use). Steady

requires one output, pulse requires two. 2. Confirmed position switches for open, closed or both, using one or two inputs. 3. Automatic control or a local selector for Open-Auto-Close using no or two inputs (these are not

common). Interlock and permissive may be additional permutations.

Alarms

If a valve has one or both position switches then it is possible to alert the operator to the fact that the valve is not where it should be. This is not a permuted choice because the main reason for having position switches is to alarm this condition. It is not a simple alarm because time must be allowed for the valve to complete its stroke after it receives a command. An On Delay timer set for the travel time is required.

All numbers in the NUMATICS Fieldbus Transmitter equations are examples. The user will want to change them.


Page 63

TDG22FFTM1-0EN 8/08



Variations On Valve Control

Interlock

There may be a process condition where it is not safe to open the valve. If this condition can be detected and transformed into the change of state of a contact, then the normally closed contact may be inserted in series with the control output. If the interlocked condition occurs then the valve will close if open or stay closed. An example is the drain valve of a batch reactor, which may have two interlocks. One prevents opening the drain if any feed valve is open. The other will not let material in the reactor drain into a tank that isn’t ready for it.

Permissive

There may be a process condition that is required to be present when a valve is opened, but is not required once it has been opened. A contact that is closed when the permissive condition is true is placed in series with the open command. A latch is required because the permissive may go false after the valve is opened. One application for a permissive involves a gas storage tank. The pressure must be above a certain amount to allow the valve to be opened, but once opened, the pressure will fall below the permissive level.

Open-Auto-Close

An operator may be required to perform some function near the valve, such as unplugging a pipe or locally directing material flow. The valve is normally controlled by the central system but must have a local station to allow the local operator to control it. The local station has a three position switch for Open-Auto-Close selection. The control room has control when the switch is in the Auto position. If the switch is turned to Open then the valve will open, possibly bypassing interlocks, and the same for Close. There is no bump going through Auto because the command is either Open or Close.

Double Block and Bleed

If the valve absolutely must not leak into the process, then two valves are put in series and the short pipe between them is vented (bled) to an appropriate place. The bleed valve must be shut before the main valves can be opened, and the main valves must both be closed before the bleed valve can be opened.

Motorized Valve

The actuator is a reversible motor that turns a lead screw that moves the valve stem. Two confirms are required because the motor is only free to turn while the valve stem is traveling. Outputs are required for the Forward and Reverse motor directions. If a big motor-driven valve takes a minute to change position, that’s a long time to find out that it didn’t move. The crack time is a period of time in which the previously closed contact must open, to confirm that the actuator is moving and the valve is not stuck or powerless.

Heat Exchange Medium Selection

Batch heat exchangers have to use different media to heat and cool. If the media are compatible, like steam and chilled water, then a simple four valve manifold can handle the selection. The four valves are independent because it is necessary to drain one medium from the exchanger before using the other. There are many variations on this theme, for incompatible media or more than two choices.


Page 64

TDG22FFTM1-0EN 8/08



Boolean Expressions

The motor control descriptions used ladder logic. Another method that takes less room on the back of an envelope is the Boolean expression. The following is a comparison of Boolean and ladder operators (math operators are +,-,*,/). Only three operators are used in the examples:

Functions are the same as NUMATICS Fieldbus Transmitter functions. The examples use TON, TOF and TP.

Basic Valve Control

Since very few applications exist for local valve control that are more than a simple toggle switch (electric or pneumatic), all examples use a DO block to take a command from Fieldbus. The DO point is on for open and off for close in all cases.

Open-Auto-Close

Those applications that use a local switch with automatic control have a three-position switch arranged as Open-Auto-Close. Inputs 1 and 2 are used for confirms, so input 3 is used for Open and input 4 for Closed. No input is required for Auto.

• The Boolean expression is:

o OPNCMD = ( !IN4 & DO1 ) | IN3

• The NUMATICS Fieldbus Transmitter expression is:

o EQ1 contains OR(AND(NOT(IN(4)),DO(1)),IN(3));

Alarm Variations

If there is just one close confirm on input 2, then the Boolean expression is:

ALARM = TON ( ( !DO1 & !IN2 ) | ( DO1 & IN2 ), TravelTime)

If there is just one open confirm on input 1, then the Boolean expression is:

ALARM = TON ( ( DO1 & !IN1 ) | ( !DO1 & IN1 ), TravelTime)

If both confirms are used, then the Boolean expression is:

ALARM = TON ( ( !DO1 & !IN2 ) | ( DO1 & !IN1 ) | ( IN1 & IN2 ), TravelTime)

The equivalent NUMATICS Fieldbus Transmitter expressions are:

TON(OR(AND(NOT(DO(1)),NOT(IN(2))),AND(DO(1),IN(2))),100); TON(OR(AND(DO(1),NOT(IN(1)),AND(NOT(DO(1)),IN(1))),110); TON(OR(AND(NOT(DO(1)),NOT(IN(2))),AND(DO(1),NOT(IN(1)),AND(IN( 1),IN(2))),120);

The chosen expression goes in the last expression used, which must be linked to a DI to generate an alarm.


Page 65

TDG22FFTM1-0EN 8/08



Output Variations

A valve actuator may be spring return, requiring one output, or bistable, requiring two outputs. Output 1 is used for Open and output 2 for Close. Bistable valves often require a short pulse instead of maintained power. The NUMATICS Fieldbus Transmitter expressions for spring return are:

OUT1 contains DO(1);

or bistable has:

OUT1 contains TP(DO(1),30); OUT2 contains TP(NOT(DO(1)),30);

Output With Interlock

The interlock may be wired, or internal, or from the bus.

The example uses a DO from the bus:

OUT1 contains TP(AND(DO(1),DO(3)),30); spring return is AND(DO(1),DO(3)); OUT2 contains TP(OR(NOT(DO(1)),NOT(DO(3))),30);

Simple Valve Variations

A spring return valve with one close confirm:

EQ1 contains TON(OR(AND(NOT(DO(1)),NOT(IN(2))),AND(DO(1),IN(2))),100); OUT1 contains DO(1);

The fourth similar spring return valve in the same NUMATICS Fieldbus Transmitter:

EQ4 contains TON(OR(AND(NOT(DO(4),NOT(IN(8))),AND(DO(4),IN(8)))),100); OUT4 contains DO(4);

A bistable valve with both confirms and a local station:

EQ1 contains OR(AND(NOT(IN(4)),DO(1)),IN(3)); EQ2 contains TON(OR(AND(NOT(DO(1)),NOT(IN(2))),AND(DO(1),NOT(IN(1)),AND(IN( 1),IN(2)))),120); OUT1 contains TP(DO(1),30); OUT2 contains TP(NOT(DO(1)),30);

The second similar bistable valve in the same NUMATICS Fieldbus Transmitter:

EQ3 contains OR(AND(NOT(IN(8)),DO(2)),IN(7)); EQ4 contains TON(OR(AND(NOT(DO(2)),NOT(IN(6))),AND(DO(2),NOT(IN(5)),AND(IN( 5),IN(6)))),120); OUT3 contains TP(DO(2),30); OUT4 contains TP(NOT(DO(2)),30);

Permissive

The permissive may be wired, or internal, or from the bus. The example uses DO3 from the bus. The confirmed open switch is used to hold the valve open if the permissive goes away. If the valve is spring return:


Page 66

TDG22FFTM1-0EN 8/08



OUT1 contains AND(DO(1),OR(DO(3),IN(1)));

A bistable valve does not need a latch:

OUT1 contains TP(AND(DO(1),DO(3)),30); OUT2 contains TP(NOT(DO(1)),30);

Either way, the alarm equation for just the open confirm is:

TON(OR(AND(DO(1),NOT(IN(1))),AND(NOT(DO(1)),IN(1))),110);

The alarm equation for both confirms is:

TON(OR(AND(NOT(DO(1)),NOT(IN(2))),AND(DO(1),NOT(IN(1)),AND(IN(1),IN(2)))),120);

Double Block And Bleed

Certain materials must not leak through a valve that is supposed to be shut. Three valves are arranged in a leak-proof configuration as shown:

All three valves are spring return. V1 and V2 return to closed, V3 returns to open. All 3 valves must have closed confirm switches, which allows two instances per NUMATICS Fieldbus Transmitter. If open confirms are also used, the alarm logic is different and only one instance per NUMATICS Fieldbus Transmitter is possible. V1 and V2 must both confirm closed in order to open the bleed valve by removing power to it. V3 must be closed (powered) to allow V1 and V2 to open. Since V1 and V2 operate together, they are both powered by the same output. The second output operates V3. The close confirms take inputs of the same number as the valve. A second instance takes inputs of the same number as the valve plus four. Open confirms take inputs of the same number as the valve plus three. DO1 is still the open/close command.

The outputs are the same whether or not there are open confirms.

OUT1 contains AND(DO(1),IN(3)); OUT2 contains NOT(AND(NOT(DO(1)),IN(1),IN(2)));

For single closed confirms, the valve assembly is confirmed open if V1 and V2 do not confirm closed and V3 confirms closed. The assembly is confirmed closed if V1 and V2 confirm closed and V3 does not confirm closed. The alarm is true if any of these conditions is false after the travel time has expired. The equation will not fit on one line, so two must be used:

EQ1 contains AND(NOT(DO(1)),OR(NOT(IN(1)),NOT(IN(2)),IN(3))); EQ2 contains TON(OR(AND(DO(1),OR(IN(1),IN(2),NOT(IN(3))),EQ(1)),110);

For both confirms, the valve assembly is confirmed closed if V1 and V2 confirm closed and V3 confirms open. The assembly is confirmed open if V1 and V2 confirm open and V3 confirms closed.

EQ1 contains AND(NOT(DO(1)),NOT(AND(IN(1),IN(2),IN(6)))); EQ2 contains


Page 67

TDG22FFTM1-0EN 8/08



TON(OR(AND(DO(1),NOT(AND(IN(4),IN(5),IN(3)))),EQ(1)),140);

Motorized Valve

The motor runs forward to open the valve and reverse to close it. When the motor is off, the valve cannot move. Both confirms are required. Output 1 causes the motor to run forward, Output 2 is reverse. Only one output must be active at a time. Input 1 confirms that the valve is open and input 2 confirms closed.

OUT1 contains AND(DO(1),NOT(IN(1)),NOT(EQ(2))); OUT2 contains AND(NOT(DO(1)),NOT(IN(2)),NOT(EQ(2)));

The alarm interacts with the motor drive so that power is not applied after the travel time expires. This prevents burnout of small motors that do not have a motor starter. A crack time alarm is also used in case the valve is stuck. Since this works even for small motors, there is no point in making it optional. The crack time is 5 seconds in this example and the travel time is 30 seconds.

EQ1 contains TON(OR(AND(IN(1),IN(2)),AND(DO(1),IN(2)),AND(NOT(DO(1)),IN(2))),5,0); EQ2 contains OR(TON(OR(AND(NOT(DO(1)),NOT(IN(2))),AND(DO(1),NOT(IN(1))),300),EQ(1));

Heat Exchange Medium Selection

The media are steam and chilled water. DO1 is on to select heating with steam and off to select cooling with water. All four valves have both confirms, as follows:

Valve Output Opened Closed Steam In Out1 In1 In5

Steam Out Out2 In2 In6 Water In Out3 In3 In7

Water Out Out4 In4 In8

Steam condensate must drain and both steam valves be closed before the water valves are opened. The water must drain and both water valves be closed before the steam valves are opened. There is a steam trap after the steam outlet valve to prevent steam from blowing through the heat exchanger. The opening of the steam outlet valve is delayed to allow some condensate to form in the exchanger for proper operation of the trap.

OUT1 contains AND(DO(1),IN(7),IN(8)); OUT2 contains TOF(TON(OUT(1), 1200),1800); OUT3 contains AND(NOT(DO(1)),IN(5),IN(6)); OUT4 contains TOF(OUT(3),1600);

Heating is confirmed if In1 and In2 and In7 and In8 are on. Travel time must include the water drain delay time and the steam outlet opening delay. Cooling is confirmed if In3 and In4 and In5 and In6 are on. Travel time must include the steam drain delay time.

EQ1 contains TON(AND(NOT(DO(1)),NOT(AND(IN(3),IN(4),IN(5),IN(6)))),1900); EQ2 contains OR(TON(AND(DO(1),NOT(AND(IN(1),IN(2),IN(7),IN(8)))),2900),EQ(1));


Page 68

TDG22FFTM1-0EN 8/08



Foundation Fieldbus Configuration and Mapping

This device can be offered with valve outputs as well as digital inputs/outputs (I/O). Valve outputs are located to the right of the communication module, while digital I/O is located to the left. Each valve slot can be configured with dual solenoid (push-pull) 4 way valves or 3 way valves.

On the I/O side, each slot can be configured with sourcing (PNP) type modules with M12 (female), screw terminal style, DB25, & M23 (19 pin round) connections. Furthermore, each module contains either 8 or 16 I/Os per slot.

The enumeration scheme for I/Os (including valve outputs) is as follows:

• Valve side – location number assignment will always start on the valve side with the slot closest to the communication module and increasing in number as you go to the right. Since some valves are operated by 2 solenoids, each solenoid will be assigned a location number. The valves will be assigned to Slot 0.

o The valve solenoid coil output portion of the total output size is up to 2 bytes (16 solenoids).

o Solenoid coil output addressing begins at the 1st manifold station nearest the node allocating SLOT_POSITION 0 to the first output (solenoid 1), SLOT_POSITION 1 to the second, and continues in ascending order away from the communication node.

o Each manifold station allocates 1 or 2 output bits. This is dependent on the Z-Board™ type installed. A single Z-Board™ allocates 1 output bit. A double Z-Board™ allocates 2 output bits.

o Z-Boards™ can be used in any arrangement (all singles, all doubles, or any combination).

• I/O side

o Manual Configuration Module is an optional module that allows the user to manually set self test mode. If this is connected to the left of the FF Configuration Module, it will be assigned to Slot 1.

o Outputs – once all valve outputs are accounted for, the digital output side is assigned a location number starting with the slot closest to the communication module. The assigned location number of the digital output will start 1 number higher than the highest assigned # for valve outputs. Modules typically contain 4, 8, or 16 outputs per slot. Each of them will be assigned individual location numbers.

� The discrete output byte size portion is self-configuring in byte increments, after an output module is plugged into the back plane and power is applied.

� Outputs are mapped consecutively by module. The output bits from the 1st module will be mapped directly after the bits from the valve coils starting at the next available bit. The output bits from the second module will be mapped directly after the output bits from the 1st module and so on.


Page 69

TDG22FFTM1-0EN 8/08



o Inputs – location number assignment will again start with the slot closest to the communication module and increase as you go to the left. Since each module can contain as many as 16 I/O per slot, each of them will be assigned a location number.

� The discrete input byte size portion is self-configuring in byte increments, after an input module is plugged into back plane and power is applied.

� Inputs are mapped consecutively by module. The input bits from the second module will be mapped directly after the input bits from the 1st module and so on.

The number of I/Os (including valve outputs) is limited via fieldbus protocol to 32 inputs & 16 outputs (32x16).

Below is a screenshot showing the Transducer1100 block. This block contains the Slot Configuration.

Single solenoid valves can be used with double Z-BoardsTM. However, one of the two available outputs will remain unused.

NOTE!


Page 70

TDG22FFTM1-0EN 8/08



I/O Mapping Examples

Example:

Manifold I/O Configuration

PosNo.

Module Type

Part No.

0 PNP Valve

Coils

1 16I PNP

(Sourcing) 239-2500

2 16I PNP

(Sourcing) 239-2311

How to Order Qty

Part Number

1 AKCGE00003NDRM 5 123BB4Z2MN00061 1 NXGFF3200DFE02 1 239-2500 1 239-2311

Assumed Settings

- Double Z-BoardsTM used with double solenoid valves

SLOT 0 Valve coils

SLOT 1 16 Input (M12 connectors)

SLOT 2 I/O terminal strip

Fieldbus communication module


Page 71

TDG22FFTM1-0EN 8/08



I/O Mapping Table Example Continued

The diagram from the previous page will have the following slot assignments:

Slot 0 will contain Outputs 1 to 10.


Page 72

TDG22FFTM1-0EN 8/08



Slot 1 will contain Inputs 1 to 16.

Slot 2 will contain Inputs 17 to 32.


Page 73

TDG22FFTM1-0EN 8/08



Appendix Auto Initialization

The device Auto Initialization is only possible when the Transducer Block is in Out-Of-Service (OOS) mode. Auto Initialization for Single Acting Actuators is done with only 1 output. After the Initialization command is received, if the initial position is OPEN, the actuator will be CLOSED and will wait 3 seconds before the next step. The output is then energized to OPEN the actuator. Once the actuator is detected by OPEN_Input_2_SEL to be in the OPEN position, allow another 3 sec delay before the output is de-energized to CLOSE the actuator. Once the actuator is detected by CLOSE_Input_1_SEL to be in the CLOSED position, allow another 3 sec before repeating the cycle 2 more times for a total of 3 cycles. In this configuration Calibration Travel & Break times CLOSE-OPEN (initial position-final position) start at the command to energize Output_1_SEL. Calibration Travel & Break times OPEN-CLOSE start at the command to de-energize Output_1_SEL.

The device Auto Initialization is only possible when the Transducer Block is in Out-Of-Service (OOS) mode. For Double Acting Actuators, 2 outputs are needed. After the Initialization command is received, if the initial position is OPEN, the actuator will be CLOSED and will wait 3 seconds before next step. Output_1_SEL is energized to OPEN the actuator. Once the actuator is detected by OPEN_Input_2_SEL to be in the OPEN position, allow an extra 3 sec delay before de-energizing Output_1_SEL. After Output_1_SEL is de-energized, wait 1 machine cycle and Output_2_SEL can then be energized to CLOSE the actuator. Once the actuator is detected by CLOSE_Input_1_SEL to be in the CLOSED position, allow an extra 3 sec delay before de-energizing Output_2_SEL. The cycle can then be repeated 2 more times for a total of 3. In this configuration, Calibration Travel & Break times CLOSE-OPEN (initial position-final position) starts at the command to energize Output_1_SEL. Calibration Travel & Break times OPEN-CLOSE starts at the command to energize Output_2_SEL.

The valve is operated 3 times (CLOSE-OPEN & OPEN-CLOSE) and the average values are updated for the Calibration BREAK TIMES and TRAVEL TIMES with a resolution of 10mS. These values are automatically saved to NV. The I/O processor performs the timer calculations.


Page 74

TDG22FFTM1-0EN 8/08



System Specifications

Electrical

Supply Voltage Valves (2005, 2012, 2035): Node and Discrete I/O:

24 VDC + 10%, -15% 24 VDC +/- 10%

Current Total current on the Auxiliary Power Connector (“Valves and Outputs” and “Node and Inputs” Pins) must not exceed 8 Amps.

Internal Fuses

The Auxiliary Power Connector pins are each internally fused with a 4 Amp fuse on the Valve/Output pin and a 10 Amp fuse on the Node/Input pin. These fuses are MINI ATO type fuses and are the maximum current allowable through the G2-2 electronics.

Recommended External Fuse

External fuses should be chosen depending upon manifold configuration. Please refer to power consumption chart on page 14 for additional fuse sizing information.

Spike Suppression Output spike suppression is internally provided for both discrete and valve outputs.

Discrete Outputs (Sinking (NPN) or Sourcing (PNP))

Maximum 0.5 Amps per output (Sinking (NPN) or Sourcing (PNP)). All outputs are short circuit protected and have internal spike suppression. Contact factory for higher current requirements.

Valve Solenoid Coil Output Drivers

Maximum 0.5 Amps per output. All output points are short circuit protected and have internal spike suppression.

Operating Temperature for Electronic Components

23 to 114°F (-5 to 46°C)


Page 75

TDG22FFTM1-0EN 8/08



Factory Defaults Settings

Description Default

Node Address 248-251

Input Module Power Jumper PU (See Page 19 - 35)

Output Module Power Jumper PS (See Page 19 - 35)


Page 76

TDG22FFTM1-0EN 8/08



Troubleshooting

Symptom Possible Cause Solution

Fuse LEDs displays red Blown internal fuses

Check for external shorts to Input connector from external sensor devices or cable and repair. Replace internal fuse. If problem persists contact factory.

F2 Fuse keeps blowing. External sensor or sensor cable shorting

Replace defective sensor and/or sensor cable.

The wrong valve solenoid coils are being energized.

Z-BoardTM type mismatch. Single Z-BoardTM present where double Z-BoardTM expected or vice versa.

Check that correct Z-BoardTM types are installed. Check that ribbon cable (output group No. 2) is connected to appropriate valve station.

Valve outputs do not energize. All node LEDs normal.

Output power not present or connected in properly on Aux. Power connector.

Check for 24VDC on the +24 VDC (Valves and Outputs) pin of the MINI Aux. Power connector of the Comm. module. Check for 24VDC on Pin No. 1 and/or Pin No. 4 of 12mm local Aux. Power connector of 25 Pin Sub-D Discrete Output Module, if applicable.


Page 77

TDG22FFTM1-0EN 8/08



Device Manufacturer and Type Identifier

Identifier

Device Manufacturer 0x4E554D

Device Type 0x4732


Page 78

TDG22FFTM1-0EN 8/08



Glossary of Terms

The following is a list and description of common terms and symbols used throughout this document: Bit Smallest unit of digital information either a “0” or “1”.

Bit mapping Chart showing which bit is connected to which physical input or output point.

Byte 8 bits (1/2 word).

Comm. Fault One or more of the I/O connections have timed out.

Cyclic I/O message type in which data production is triggered by the expiration of the transmission timer.

DI Discrete input function block.

DO Discrete output function block.

Device Description (DD)

A Device Description (DD) provides an extended description of each object in the Virtual Field Device (VFD), and includes information needed for a control system or host to understand the meaning of data in the VFD.

Discrete I / O The Inputs / Outputs that are available via the “Discrete I/O” side of manifold

G2-2 A Numatics product series of electronics which features modular backplane technology that allows various Discrete I/O components and Communication modules to be added, removed or changed in the field.

Ground This term is used to indicate an earth ground.

H1 H1 is a term used to describe a fieldbus network operating at 31.25 kbit/second.

High Speed Ethernet (HSE)

High Speed Ethernet (HSE) is the Fieldbus Foundation’s backbone network running Ethernet and IP .

I/O Any combination of Inputs and Outputs.

Idle A zero (0) length poll message (i.e.: scanner in program mode).

Link A Link is the logical medium by which H1 Fieldbus devices are interconnected. It is composed of one or more physical segments interconnected by bus, Repeaters or Couplers. All the devices on a link share a common schedule, which is administered by that link’s current LAS. It is the data link layer name for a network.

Link Active Scheduler (LAS)

A Link Active Scheduler (LAS) is a deterministic, centralized bus scheduler that maintains a list of transmission times for all data buffers in all devices that need to be cyclically transmitted. Only one Link Master (LM) device on an H1 fieldbus Link can be functioning as that link’s LAS.

Link Master (LM) A Link Master (LM) is any device containing Link Active Scheduler (LAS) functionality that can control communications on an H1 fieldbus Link. There must be at least one LM on an H1 Link; one of those LM devices will be elected to serve as LAS.

Link Objects A Link Object contains information to link Function Block (FB) Input/Output (I/O) parameters in the same device and between different devices. The Link Object links directly to a Virtual Communications Relationship (VCR).

MDI Multiple Discrete input function block.

MDO Multiple Discrete output function block.

MCM Manual Configuration Module. A module that allows configurable parameters to be set manually via DIP switches and rotary switches. Not required for Foundation Fieldbus operation.

NEMA National Electrical Manufacturers Association

Polled I/O message type in which the device consumes I/O data from its master and produces I/O data when the master requests it.

Sinking (NPN) Method of connecting electrical circuits in which the zero (0) volt DC side is switched and the common is positive.

Sourcing (PNP) Method of connecting electrical circuits in which the positive side is switched and the common is zero (0) volts DC.

Spur A Spur is an H1 branch line connecting to the Trunk that is a final circuit. A Spur can vary in length from 1 m (3.28 ft.) to 120 m (394 ft.).

Terminator Impedance-matching device used at or near each end of a transmission line that has the same characteristic impedance of the line. Terminators are used to minimize signal distortion, which can cause data errors by converting between current variations. H1 terminators also have another even more important function. It converts the current signal transmitted by one device to a voltage signal that can be received by all devices on the network.

Trunk A Trunk is the main communication highway between devices on an H1 fieldbus network. The Trunk acts on a source of main supply to Spurs on the network.

Transducer Block (TB)

A Transducer Block (TB) decouples Function Block (FBs) from the local Input/Output (I/O) functions required to read sensors and command output hardware. Transducer Blocks (TBs) contain information such as calibration date and sensor type. There is usually one TB channel for each input or output of a Function Block (FB).

Virtual Communication Relationship (VCR)

Configured application layer channels that provide for the transfer of data between applications. Foundation Fieldbus describes three types of VCRs: Publisher/Subscriber, Client/Server, and Source/Sink.

Virtual Field Device (VFD)

A Virtual Field device (VFD) is used to remotely view local device data described in the object dictionary. A typical device will have at least two Virtual Field Devices (VFDs).

Status Input bit A bit in the input table that reports the health of a corresponding output. Indicates short circuit or open coil (load) diagnostics.

Word 2 Bytes (16 bits).

Z-BoardTM Circuit board installed in the valve sub-base which electrically connects the valve solenoid to the electrical /electronics interface. Available in single or double solenoid versions.


Page 79

TDG22FFTM1-0EN 8/08



Technical Support

For technical support, contact your local Numatics distributor. If further information is required, please call Numatics Inc. at (248) 887-4111 and ask for Technical Support. Issues relating to network set-up, PLC programming, sequencing, software related functions, etc… should be handled with the appropriate product vendor. Information on technical manuals, local distributors, and other Numatics, Inc. products and support issues can be found on the Numatics, Inc’s. WEB site at www.numatics.com Information on DD files can be found at:

• www. Fieldbus.org

• www.easydeltav.com

G2-2 Series Foundation Fieldbus (H1) Technical Manual Asset Library/TDG22FFTM1-0EN.pdf · G2-2...

Documents

Transcript of G2-2 Series Foundation Fieldbus (H1) Technical Manual Asset Library/TDG22FFTM1-0EN.pdf · G2-2...