Users Manual Ethernet IP v3.3.28

FMC Subsea Driver for

DeltaV Virtual I/O Module

For both Simplex and Redundant FMC TPU TCP Versions 1.0.x

IOD-4105

USER MANUAL

October 25, 2011

Disclaimers

©MYNAH Technologies 2006. All rights reserved.

Designs are marks of MYNAH Technologies; Emerson Process Management, DeltaV, and the DeltaV design are marks of Emerson Process Management. All other marks are property of their respective owners.

While this information is presented in good faith and believed to be accurate, Mynah Technologies does not guarantee satisfactory results from reliance upon such information. Nothing contained herein is to be construed as a warranty or guarantee, express or implied, regarding the performance, merchantability, fitness or any other matter with respect to the products, nor as a recommendation to use any product or process in conflict with any patent. Mynah Technologies reserves the right, without notice, to alter or improve the designs or specifications of the products described herein. All sales are governed by Mynah

Technologies‟ terms and conditions, which are available on request.

Table of Contents

1.

Introduction .......................................................................................................................................... 3

1.1.

Scope ............................................................................................................................................ 3

1.2.

Document Format ......................................................................................................................... 3

1.3.

System Specifications ................................................................................................................... 4

2.

Theory of Operation ............................................................................................................................. 5

2.1.

DeltaV Native I/O .......................................................................................................................... 7

2.2.

TPU Devices ................................................................................................................................. 7

2.3.

DeltaV Presentation of I/O and status data from the VIM ............................................................. 8

2.3.1.

DO I/O Points ........................................................................................................................ 8

2.3.2.

DI I/O Points .......................................................................................................................... 8

2.3.3.

AO I/O Points ........................................................................................................................ 8

2.3.4.

AI I/O Points .......................................................................................................................... 9

2.4.

Presentation of Global Data .......................................................................................................... 9

3.

VIMNet Explorer ................................................................................................................................. 10

3.1.

Installation of Simplex Virtual I/O Module (VIM) Hardware ......................................................... 10

3.2.

Installation of 2 Simplex Virtual I/O Modules for redundant TPU‟s ............................................. 11

3.3.

Installation of Software ................................................................................................................ 12

3.4.

Configuring VIM, Importing TPU and Tags ................................................................................. 17

3.4.1.

Adding a DeltaV Controller .................................................................................................. 17

3.4.2.

VIM Configuration................................................................................................................ 18

3.4.3.

Commission the VIM ........................................................................................................... 19

3.4.4.

TPU Configuration File ........................................................................................................ 21

3.4.5.

Import TPU configuration into VIM ...................................................................................... 21

3.4.6.

Assign TPU to DeltaV Device ............................................................................................. 23

3.4.7.

Configure TPU Tags ........................................................................................................... 24

3.4.8.

VIM Detail Display with imported TPU‟s ............................................................................. 27

3.4.9.

TPU Device Level Tag Display ........................................................................................... 28

3.4.10.

Tag Group Level Display ..................................................................................................... 29

3.4.11.

Data Set Level Display ........................................................................................................ 29

3.5.

Uploading a VIM Configuration ................................................................................................... 31

3.6.

Saving the VIM Configuration ..................................................................................................... 32

3.7.

Flash Upgrade of the VIM Firmware ........................................................................................... 35

3.8.

Configuring VIMs on Multiple Subnets ........................................................................................ 39

4.

Configuring DeltaV ............................................................................................................................ 42

4.1.

Configuring DeltaV with FHX import file ...................................................................................... 42

4.2.

Manually Configuring DeltaV....................................................................................................... 44

4.2.1.

Configure Serial Card and Ports ......................................................................................... 44

4.2.2.

Configure Devices ............................................................................................................... 46

4.2.3.

Configure Datasets.............................................................................................................. 47

4.3.

Configuring a Time Sync Module ................................................................................................ 51

4.4.

Configuring DeltaV writes to TPU ............................................................................................... 52

4.5.

TPU Tag definitions in DeltaV ..................................................................................................... 55

5.

VIMNet Diagnostics ........................................................................................................................... 57

5.1.

VIM Level Diagnostics ................................................................................................................. 58

5.2.

Port Level Diagnostics ................................................................................................................ 60

5.3.

Device Level Diagnostics ............................................................................................................ 61

5.4.

Dataset Level Diagnostics ........................................................................................................... 64

5.5.

Diagnostics Impact on Vim and network communications .......................................................... 65

6.

Operational Check ............................................................................................................................. 66

6.1.

Scope .......................................................................................................................................... 66

6.2.

Verify Hardware and Software Version Number ......................................................................... 66

6.3.

Verify Configuring ........................................................................................................................ 66

6.4.

Verify I/O Communication with Control Studio ............................................................................ 66

6.5.

Using DeltaV Diagnostics ............................................................................................................ 66

6.6.

LED Indication ............................................................................................................................. 67

7.

Figures ................................................................................................................................................ 68

8.

Tables .................................................................................................................................................. 69

9.

Technical Support .............................................................................................................................. 70

FMC 722 VIM User Manual

1. Introduction

1.1. Scope

This document is the User Manual for the Virtual I/O Module (VIM) with the FMC Subsea TCP master driver firmware for the Emerson Process Management (EPM) DeltaV Control System. It provides the information required to install, configure, and maintain the driver firmware on the VIM. The reader should be familiar with EPM‟s DeltaV Programmable Serial Interface Cards (PSIC), FMC722 protocol, and connected field devices (supporting the FMC722 TCP protocol).

The section Document Format briefly describes the contents of each section of this manual. System

Specifications outlines hardware and software requirements for the FMC722 Driver firmware.

1.2. Document Format

This document is organized as follows:

Introduction

Theory of Operation

VIMNet Explorer

DeltaV Configuration

VIM network diagnostics

Operational Check

Technical Support

Describes the scope and purpose of this document.

Provides a general functional overview of the FMC

Subsea TCP Driver.

Describes procedures to upgrade the FMC Subsea

TCP driver firmware in the VIM, as well as creating and uploading a configuration to the VIM.

Describes procedures and guidelines for configuring the DeltaV serial cards residing in the VIM.

Describes FMC Subsea TCP network device configuration.

Provides tips and assistance to ensure the VIM is properly setup and configured.

Describes who to call if you need assistance.

1-1 Document sections

_____________________________________________________________________________________________________

504 Trade Center Blvd. • Chesterfield, MO 63005 • Telephone (636) 728-2000 • Fax (636) 728-2001 • www.mynah.com

3


1.3. System Specifications

The following table lists the minimum system requirements for the FMC Subsea TCP Driver:

Firmware

VIMNet Explorer

Protocol Compatibility

Software Requirements

Minimum DeltaV Hardware

Requirements

VIM Hardware Requirements

Network Hardware

Requirements

FMC Subsea TCP Driver Firmware

Windows PC resident VIMNet Explorer Application.

FMC722 protocol conforming to “ FMC722 TPU

General Communications Protocol Specification

”, Rev j, Dec 23, 2010. This document is available from FMC Technologies.

DeltaV System Software (Release 6.3 or later) installed on a hardware-appropriate Windows workstation configured as a ProfessionalPlus for

DeltaV

Serial Interface Port License (VE4102), if required by the DeltaV version. One license is required for each serial port used. The VIM has a maximum of 8 available serial ports.

MYNAH VIM driver firmware IOD-4105

DeltaV M3, M5, M5+, MD, MDPlus, MX or S-Series

Controller

1 standard 2 wide controller carrier

1 standard Power Supply

MYNAH VIM part no. MIM-4207

Only Simplex VIM installations are supported: 1 standard 2-wide controller carrier (Model Number

VE3051C0) and 1 standard Power Supply (Model

Number VE5008)

For Redundant TPU installations, use two Simplex

VIM‟s in parallel: 2 standard 2-wide controller carrier

(Model Number VE3051C0) and 2 standard Power

Supply (Model Number VE5008)

Multiport 10/100BaseT Switch not shared with

DeltaV Control Network. Two network switches are required for Redundant TPU communication (one for each VIM/FMS subnet). Also for Redundant TPU systems, the VIMNet configuration PC requires two network interface cards, one for each FMC subnet.

1-2 FMC Subsea TCP Driver System Specifications

_____________________________________________________________________________________________________


4


2. Theory of Operation

SubSea system configuration is defined in terms of TPU (Topside Processing Unit) and their undersea sensors and actuators. It may be interfaced to a control system via the FMC722 (TPC) protocol. The

VIM acts as the interface for DeltaV

Figure 1: Subsea System Topography

The VIM FMC scanner is an online process in the VIM. It is designed to run continuously; updates to the configuration are by uploads from the VIMNet Explorer and downloads from DeltaV controller. Once installed, commissioned and uploaded, the VIM FMC scanner automatically opens its connection to the

TPU after DeltaV downloads the card configuration (all four cards in DeltaV). The I/O Point definitions are configured into the VIM scan table when the DeltaV configuration is loaded.

1. During the scan, each point type is processed, checking for updates from the mapped DeltaV output registers. Outputs to the TPU will be by exception on receipt of the output from the DeltaV database.

2. Inputs from the field (TPU) are monitored, and changed inputs are sent to DeltaV real-time database asynchronously to the DeltaV outputs as received.

3. FMC Pings are sent to TPU at a 10 second interval asynchronously to inputs and outputs. Ping responses are processed as part of the input monitoring process. Failure to receive ping response within the 10 second interval triggers a timeout. Following 3 retries, the TCP connection to field (TPU) will be terminated and will result in all associated datasets in DeltaV going to bad status.

On VIM restart (following power loss), the Configuration is read from EPROM in the VIM and the communications is automatically restored.

Each sensor/actuator I/O point is an object and consists of multiple parameters; each parameter is a separate DeltaV register. As each parameter value may of a different data type, the registers for an

_____________________________________________________________________________________________________


5

FMC 722 VIM User Manual individual I/O point will be mapped to separate dataset/register combinations. A register in a separate dataset will be assign for each parameter required for a point. This means there will be one dataset for each point value and the register in each dataset corresponds to the tag index (under the device, not

TPU).

There will be a maximum number of tags in a single VIM. This number will limit the number of SPCU‟s

(Subsea Power Communications and Control Unit) that may be connected to the VIM. The more tags in an individual SPCU, the fewer SPCU‟s. Based on how the tags are entered into the datasets under a device, there will be further limits on the total tags (as some datasets may not be fully utilized). Note also that 32-bit datasets (integer and floating point) in DeltaV only allow 50 registers while discrete, 8 and 16bit datasets allow 100.

The DeltaV Virtual I/O Module (VIM) provides a native DeltaV I/O interface to open plant

Ethernet networks and devices that use FMC722 (TCP) protocol. DeltaV controllers can read and write signals from the connected TPUs. As such, the VIM is a Network Gateway between DeltaV controllers and field subsea devices supporting network communications. This connectivity is illustrated below (note TPU pairs may be in the same cabinet):

Figure 2: Simplex/Redundant FMC Subsea TCP Network

_____________________________________________________________________________________________________


6


2.1. DeltaV Native I/O

The VIM provides a native DeltaV I/O interface by emulating four Programmable Serial Interface Cards or

PSIC ‟s. By design, the VIM acquires the last 8-wide I/O carrier of a DeltaV system, emulating cards 57-60 or 61-64 as a single, simplex unit. Installing 2 simplex VIMs side-by-side provides emulation of all 8 serial

I/O cards 57-64. The configuration of card group 57-60 or 61-64, and network properties of connected field devices is done in the VIMNet Explorer described in Section 3.

For redundant TPU support, 2 VIMs are installed side-by-side and configured as simplex units. There is no VIM redundancy switchover available or triggered from DeltaV, rather DeltaV modules write to both

VIM‟s and select inputs from the registers based on status returns from the input fields. For example, if there is a communication error for a tag on card 57 that requires a switchover, the DeltaV module will switch to reading its partner (61), the same for 58 (62), 59 (63) and 60 (64). This allows redundancy switching of individual tags rather than complete TPU‟s.

The emulated serial cards appear to DeltaV as real serial I/O. The configuration of data tables to be read and written is done at the DeltaV Explorer level, in the same manner as required for a serial PLC device.

This allows communications with any TPU SEM device that supports the FMC Subsea TCP messaging.

Each PSIC has 2 ports configured under it. There are 16 datasets under each port. Consequently, the

VIM has the capacity of 128 datasets. One dataset is equivalent to 100 16-bit registers, 50 32 bit registers, or 50 floating point (32 bit) registers. These 128 datasets are user mapped to DeltaV devices as required for your application.

2.2. TPU Devices

The FMC TPU IP address is unique in the serial cards port domain. Specifically, within a serial port, all configured TPU devices are unique. You can, however, configure the same TPU with the same address under multiple ports.

The TPU typically communicates serially with its slaves (actuators and sensors). For example, a chock valve, DI points, etc. These are devices that communicate with the TPU and with DeltaV via the FMC722 protocol with the VIM. The message packets from the VIM are converted from FMC722 in the TPU as necessary and transmitted to slave devices. The subsequent responses are converted back to FMC722 in the TPU and transmitted to the VIM.

The VIM has the capacity to communicate with up to 32 network devices simultaneously; however as each tag requires a single register in from 2 to 6 datasets, and as the number of tags in a TPU may be in the hundreds, the VIM will normally be expected to handle two TPU connections. The communications tasks in the VIM are all active concurrently, each handling the messaging for the configured device (with its unique IP address).

In general each TPU is sent write requests in packet form, multiple messages added to one packet.

These may be writes from one or more datasets, or may be configuration writes, time sync writes, or FMC protocol pings. Inputs to the Vim are generated by the TPU independently of the VIM with multiple tag and control messages sent without prompting from the VIM on data change and at user specified intervals (specified with the SmartTool utility in the TPU). Depending on CPU load on the device the turnaround can be as low as 10 msec. or as high as 200 msec. per dataset group scan.

_____________________________________________________________________________________________________


7


2.3. DeltaV Presentation of I/O and status data from the VIM

There are four types of I/O tag points that have data presented to DeltaV in VIM card dataset registers.

The registers are split between multiple datasets based on the data type required for each register. The number of datasets for each type is defined by the number and data type of accessible parameters of the tag type (either 100 registers/dataset for UINT16, or 50 for UINT32 and floating point parameters). The number of datasets is therefore dependent on the number of each type of tag times the number of parameters for the tag. Also datasets must be configured in DeltaV as they are in the VIM as the structures generated are presented in this manner.

Status is OPC format, 16-bit unsigned integer register. Least significant byte (LSB, the second byte in message buffer) holds TPU status; High byte is masked out (zeroed) by TPU. In DeltaV each dataset represents a single parameter for group of TPU tags.

2.3.1. DO I/O Points

FMC DO Points are Discrete actuator points, these send a setpoint to the field and receive a “read-back” signal.

Field

Setpoint

Read-back value

Read back status

Check back

DeltaV Register

Type

UINT32

UINT16

UINT16

UINT32

TPU Data

Type Size

UINT16* 2

UINT16 2

UINT16 2

UINT32 4

FMC

Protocol

DOToIO

DOFromIO

DOFromIO

DOFromIO

2-1 DO Point Registers

*Low 16-bit word is TPU value, High 16-bit word is VIM transfer status

2.3.2. DI I/O Points

DI points are discrete sensor inputs

Field

Input value

Input status

DeltaV Register

Type

UINT16

UINT16

TPU Data

Type Size

UINT16 2

UINT16 2

FMC

Protocol

DIFromIO

DIFromIO

2-2 DI Point Registers

2.3.3. AO I/O Points

AO points are analog output devices such as flow valves, these take a mode command and a floating point value from DeltaV and send back a step and read-back value.

Field

Mode**

Setpoint (EU)*

Read-back step

Read-back value (EU)

Read back status

Check back

DeltaV Register

Type

UINT32

Float

UINT32

Float

UINT16

UINT32

TPU Data

Type Size

UINT16* 2 float

UINT32

Float

UINT16

UINT32

4

4

4

2

4

FMC

Protocol

AOToIO

AOToIO

AOFromIO

AOFromIO

AOFromIO

AOFromIO

2-3 AO Point Registers

*Low 16-bit word is TPU value, High 16-bit word is VIM transfer status

_____________________________________________________________________________________________________


8


**AO points require two values from separate datasets for the AO message; AO points in DeltaV send outputs to the field. The output is a command and an optional floating point value for the command. The

TPU responds with a command response (ACK or NACK) message (asynchronously). The field also independently sends current field value with status (and timestamp) on changes. Note Output from

DeltaV is to two independent datasets (command is 32-bit; value is in floating point dataset). These are received by the VIM asynchronously. Both must be sent to the field as a match pair. To enforce this, the output value must be sent first. The output command must be sent by DeltaV on the next module scan.

Receipt of the output command will trigger the AO write in the VIM.

2.3.4. AI I/O Points

AI Points are analog input signals from the field.

Field

Input value (EU)

Input status

DeltaV Register

Type

Float

UINT16

TPU Data

Type Size

Float 4

UINT16 2

FMC

Protocol

AIFromIO

AIFromIO

2-4 AI Point Registers

2.4. Presentation of Global Data

Each VIM has global data that is accessed by DeltaV, either read, written, or both. These registers are stored in a global control dataset. This is a required dataset, it contains data for time sync updates to the

TPU‟s configured in the VIM, The VIM to TPU connection will not complete without an initial time sync message.

Reg Field Direction* Description

1

2-17 DeltaV Time Valuer

18

19

DeltaV TimeSync

Trigger

VIM TimeSync Trigger Out/In

TPU Online Status

20-35 TPU Watchdog Words In/Out

36 VIM Watchdog Word

37-50 Unused

In

Out

In/Out

In/Out

This is a bit array set/reset by the VIM. Each bit in this register represents a TPU. The VIM sets the bit to prompt

DeltaV for a timestamp value (register in 2-17 range based on

TPU index. On receipt of the value, the VIM sends a

TimeSync message to the TPU then resets the bit.

Output time value (UTC) from DeltaV, this should be sent whenever the input trigger value is set, and should not be sent if the bit is not set.

This is a bit array set by DeltaV to trigger a manual TimeSync message to a TPU. Each bit represents one of the TPUs.

When the VIM sees a bit set, it will trip the manual operation and reset the bit.

This is a bit array set in VIM when the TPU processing is

“online”. If DeltaV writes to this value it will be reset on the next scan.

This is an array of words, one for each active TPU (offset is the index of the TPU). The VIM will continuously increment this value on each TPU process scan. If DeltaV writes a zero

(0) to this value, the VIM will re-start the count sequence.

The VIM will continuously increment this in its main process loop (at a 200 ms interval). If DeltaV writes a zero (0) to this register, the VIM will increment from the new value.

*direction with respect to DeltaV,

2-5 Global Configuration Dataset Data

_____________________________________________________________________________________________________


9


3. VIMNet Explorer

3.1. Installation of Simplex Virtual I/O Module (VIM) Hardware

You will need a 2-wide carrier with power supply and DeltaV controller with either one or two 2-wide carriers each holding one VIM and its power supply. Power supplies should be mounted on the mounted on the left side of the carrier, and the DeltaV controller or the VIM on the right side. Connect VIM(s) to the left or right edge of the Controller 2-wide carrier. Repeat this step for all simplex VIM installations. The final assembly should be as follows with VIM(s) connected on the left:

Figure 3 Simplex VIM Assembly

Figure 4 Two Simplex VIM Assembly ‟s

Connect a network cable from the VIM bottom port to a single isolated switch on the appropriate TPU subnet.

Do not use the DeltaV Primary or Secondary switches for VIM field communications.

Note

Connect the PC with the VIMNet software to the switch connected to the VIM. The DeltaV ProPlus PC may be used to host the VIMNet Explorer. However, a separate network card (NIC) must be used for

VIMNet communications.

Multiple VIM‟s may be connected to the same NIC in the PC as long as they are on the same subnet.

_____________________________________________________________________________________________________


10


3.2. Installation of 2 Simplex Virtual I/O Modules for redundant

TPU’s

You will need three 2-wide carriers, 3 power supplies, one DeltaV controller and two VIMs. Mount a power supply on the left side and the DeltaV controller on the right side of one 2-wide carrier. Mount a power supply on the left side and the VIM on the right side of the other two 2-wide carriers. Connect the two 2-wide VIM carriers together and to the left edge of the Controller 2-wide carrier. Repeat this step for all redundant TPU installations. The final assembly should be as follows. Note that t he VIM‟s can also be installed on the right of the controller.

Figure 5: Redundant TPU Assembly

Connect a network cable from each VIM Ethernet port to a separate dedicated isolated switch. In operation both VIM‟s communicate to the paired TPU independently, therefor LED indicators will normally show field communications.

Do not use the DeltaV Primary or Secondary switches for VIM field communications.

Note

Connect the PC with the VIMNet software to both FMC subnets with the isolated switches connected to the VIMs (using separate network interface cards for each subnet). The DeltaV ProPlus PC may be used to host the VIMNet Explorer; however different network cards must be used for VIMNet and DeltaV communications.

If a single NIC in the configuration PC is used, the connection may be manually switched between VIM‟s and the configuration VIMNet PC if it is desired to keep the two networks separate.

_____________________________________________________________________________________________________


11


3.3. Installation of Software

3.3.1. MSI Selection

Distributions use a single MSI file called VimNet_x.MSI as shown below, where x is the version number.

Double Click on MSI to install VIMNet.

Figure 6:Installation MSI file

_____________________________________________________________________________________________________


12


3.3.2. Launch VimNet

Launch the VIM Plug & Play Server by going to Start –> Programs –> VIMNet Explorer -> VIMNet

Explorer.

Figure 7: XP Menu Selection

Figure 8: Windows 7 Menu Selection

_____________________________________________________________________________________________________


13


The following main VIMNet Explorer screen will be displayed:

Figure 9: Initial VIMNet Screen

3.3.3. Initial IP Addresses

Right click on Physical Network and go to Properties. You will be prompted to enter the IP Address of the network communicating with the VIM. The IP address shown is a default. Change this to the IP address you are using, and then click OK.

Figure 10: Default IP Address Selection

Alternatively, you will see a dialog allowing configuration of one or more network interfaces in the PC for commu nications to VIM‟s on multiple subnets.

_____________________________________________________________________________________________________


14


Figure 11: Advanced IP Selection Dialog

You select a NIC from the Available NIC list, select “Add” to add to the used address list. If needed selecting an entry in the used address list enables the “Delete” button, allowing the removal from the list.

You should add all subnets over which this utility will communicate to VIM‟s.

This dialog also allows enabling of dynamic updates (polls for online configuration systems). If not enabled, the VIMNet I/O tree will not show bad (non-responsive) VIM modules.

Figure 12: Dynamic Status Updates Overrides



All Enabled Sets all commissioned VIMs in I/O tree to be polled for status.



All Disabled Sets all commissioned VIMs in I/O tree to non-polling status.



Individually Enabled L eaves all VIM‟s in their current state, but allows then to be toggled from the VIM level in the I/O tree (this is the default if “Dynamic Status

Updates” is not checked here.

The VIM‟s may also be enabled/disabled individually at the VIM level in the VIMNet Explorer I/O tree, if done so there, when this dialog is re-opened, these fields will be updated appropriately.

_____________________________________________________________________________________________________


15


3.3.4. VimNet Global Properties

Some global properties may be selected to modify the behavior of VimNet Explorer. These are accessed via the VimNet Properties selection on the context menu VimNet level in the IO tree.

Figure 13 VimNet context menu

Selecting this opens the properties dialog:

Figure 14 VimNet Properties Dialog

VimNet Open Parameters:

Field Checked

Use Default

Configuration

VimNet opens to the default vio file selected

(an item is added to the VimNet context menu to allow selection of a loaded vio file to be the default).

Unchecked

Behavior depends on other selections.

Open to

Select File

VimNet initially opens with a select file dialog defaulting to the last vio file. This allows the selection of the vio file to open.

VimNet opens to the last vio file saved.

_____________________________________________________________________________________________________


16


Field

Use Default

Storage

Path

Checked

VimNet uses a specific directory for vio files.

This is intended for use of network storage of a vio file so multiple configuration PC‟s may access the same file (if one user has it open, other users have read-only access).

Unchecked

Selection of vio file determines the directory location

Default path is editable and browse-able.

Sp

Configurable Devices

Some Modbus/TCP devices allow specification of registers to be accessed, where registers may not be sequential or there are restrictions on access. This combo box displays the files generated (see

Modbus/TCP VIM manual for details).

Import

This allows setting of the default path for imports. This is also changed whenever a new directory is used for an import.

Prevent Access to Invalid IP (mismatched NIC)

When checked, no attempts are made to communicate with VIM‟s that have an IP address that does not match the default NIC. This has been superseded by selection of NIC for a VIM in the VIM properties dialog (“Nic Specified” checkbox).

Store last VIM type created

When checked this causes the default VIM type to match the last VIM created. If not selected, the default is Modbus/TCP.

3.4. Configuring VIM, Importing TPU and Tags

Once the VIM has been added to the VIMNet I/O tree, it is necessary to configure the communications parameters of the VIM, set the Firmware type and import the TPU and associated Tags.

3.4.1. Adding a DeltaV Controller

Right click on I/O Net and select New Controller menu option. This will create a controller object underneath I/O Net. The controller will have a default name, e.g., Node1. Rename the created controller to match the controller name in DeltaV.

Figure 15: I/O Network Context Menu

_____________________________________________________________________________________________________


17


3.4.2. VIM Configuration

Right click on the Controller to Add Virtual I/O Module (VIM) placeholder.

Figure 16: Controller Context Menu

A dialog box will appear to Add Virtual I/O Module:

Figure 17: VIM properties Dialog

Fill in the parameters as follows: a. Type – The firmware in the VIM is specified by selecting “I/O VIM –FMC Subsea 1.x” from the

Type list. b. Virtual Cards – select card group to be emulated by VIM, i.e., cards 57-60, or 61-64 c. Name – Unique 16 character VIM name d. IP Address – an IP address in your network which is not currently being used e. Subnet Mask – remains as default f. DeltaV version 10.x or earlier (or M-Series IO) set to match the DeltaV controller.

_____________________________________________________________________________________________________


18

FMC 722 VIM User Manual g. Configuration version. This is a user editable field and may be used to identify different versions to prevent the upload of an out of date configuration, or one that is in being edited for future use. This field consists of two user defined parameters (major and minor revisions) and one that is incremented on each upload resulting in fo rmat:” major.minor.upload”. This may be used to determine if the file being displayed is acceptable for download (as part of a site upload procedure). This is displayed in the detail window when the VIM branch is selected in the I/O tree. The upload number may also be edited to match a current configuration, but will still be incremented on next upload.

After filling out the parameters, select OK.

3.4.3. Commission the VIM

Commissioning the VIM allow communications with the actual VIM. This may be done now, or later if VIM is not currently available.

The Virtual I/O placeholder module has been added (note that the Virtual Cards appear and you are ready to commission).

Figure 18: VIM Detail Display

_____________________________________________________________________________________________________


19


Click on Decommissioned VIMs to display all available decommissioned VIMs. This list is dynamically populated as VIMs are detected on the network. Click the Decommissioned VIMs object in the left pane and verify the VIMs appear in the list in the right pane.

Figure 19: Decommissioned VIMs Detail Display

Right click on the VIM placeholder under I/O Net and select the Commission menu option.

Figure 20: VIM Context Menu (Decommissioned) a. Select the VIM to be commissioned from the List of Decommissioned VIMs

_____________________________________________________________________________________________________


20


Figure 21: Commission VIM Dialog b. Select “Start Flashing” to identify the VIM you are commissioning. Once the correct VIM has been located, select Stop Flashing and then select OK.

If not located check the network connection and power supply. Cancel the dialog and repeat.

Note the address specified is tested and displayed as either “Address Available” or “Address In Use” if a device on the network responds to a ping.

When commissioned, the Active LED will stay steady green and your state on the VIMNet Plug and Play

Server will indicate that the commission is good. The Standby LED will remain off.

Repeat this steps for all VIM to be commissioned.

3.4.4. TPU Configuration File

Create a TPU import definition file. Use the FMC SmartTool configuration utility to open the configuration file containing the TPU pair definitions. At the field level, select “Export”, then “SCU-int-1: Export std IO- list for branches as a text file ” (or the menu item for the interface that is attached to DeltaV if it is not interface 1).

Note: Selecting “SCU-int1 Only: Export std IO- list for branches as a text file” will export tags that are

only assigned to the interface 1, if a tag is assigned to any other interface as well as interface 1 (tags may be assigned to multiple interfaces) then that tag will not be in the export.

3.4.5. Import TPU configuration into VIM

To complete VIM configuration, network devices and TPU tags must be added to the virtual cards. Right click on the VIM and select Import FMC TPU File and browse to the SmartTool export file.

_____________________________________________________________________________________________________


21


Figure 22: FMC VIM Context Menu (Commissioned)

The file is read and the TPU tag Import dialog is displayed.

Figure 23: TPU Import Dialog

Note: If no branches are displayed below the Field level, check the type of import, there are three separators that may be used. The default separator is a semicolon (“;”) is used in the original export from SmartTool. Alternatively if the file is modified in excel, the file may use a comma for a separator (“,”).

Finally it is possible a tab character may be used. These may be selected in the VIMNet level properties dialog.

_____________________________________________________________________________________________________


22


3.4.6. Assign TPU to DeltaV Device

Assign TPU to the VIM. Select the tree element with the TPU needed in the VIM. Right click and select

“Assign TPU”:

Figure 24: SPCU (TPU) Context Menu (Unassigned)

Figure 25: TPU Properties Dialog

Fill in the parameters as follows: a. Name. This is the TPU name form the SmartTool (up to 32 characters) and should be left as imported. b. Set the IP address and of the TPU and the interface port that will be used for the connection. c. The maximum buffer is set to 1600; this must match the maximum that the TPU may accept. d. If the TPU is to receive a time-sync from DeltaV, leave this checked. The global configuration dataset location may be edited if necessary , selecting “Create” adds the defined dataset to the

V IM configuration and changes the button to “Delete”. The “Delete” button removes the

_____________________________________________________________________________________________________


23

FMC 722 VIM User Manual configured dataset from the VIM configuration, enables the edit field, and changes the button to

“Create” allowing the entry of a different dataset path, in the format card, port, device, and dataset numbers . Selecting the “Create” button re-adds the dataset at the new location. This is made available to allow moving the global status dataset if it is required to add more tag group datasets for one or more of the TPU‟s configured for the VIM, and the location of the configuration dataset interferes with this process. e. The CRC is optional set for processing, this must match the setting in SmartTool configuration file for the TPU, if CRC is enabled in the TPU configuration, then this must be enabled. f. Individual Configuration Requests allows individual messages to be sent for each tag during startup. By default, a single request is made for all configured tags. This will normally be left unchecked, but if a subset of tags assigned to the TPU interface are to be accessed, then this field should be checked. g. DS Scan Rate sets the update rate for DeltaV input datasets. This is configured on a TPU (or the

tag group section 3.4.10) level. This value from 50ms to 1 sec is the minimum interval between

updates to the DeltaV database. This value defaults to 50ms, but may be raised if multiple TPU‟s are configured in a single VIM. For four TP U‟s, a value of 200 ms may be required to maintain good communications from the VIM to DeltaV. This is a tuning parameter. The "Update" button will write to all input datasets in the TPU (with the exception of ones locket with tag group context menu (Lock DS updates), and set with (Set DS Update Rate). The special word 3 is then set in the FHX file. You can also set the value in DeltaV, but should make sure all input datasets in a tag group have the same value. The special word 3 low byte has the value (0-255, which is the update rate divided by 50 ms units). This is a tunable parameter and is only needed when multiple TPUs (3 or 4) are attached to the VIM.

3.4.7. Configure TPU Tags

Add Tags to VIM. Right click on the branch in the list and select “Add Tags”. This may be done from the

TPU level or any sub level allowing either the complete list to be added or a subset. As each tag in the list is added new devices and datasets will as necessary. Datasets are added as groups under the device based on the tag type. Tags are added as they appear in the list, but separated in groups by type

(DO, DI, AO, or AI) and number (where more tags exist than a single dataset group may allow). If tags have been assigned at or under the selected branch, then the “Delete Tags” menu item will be enabled, allowing the removal of I/O tags as ordered by TPU device, well, etc. If all tags at the selected branch, or below, have been assigned, then the “Add Tags” menu item is disabled.

Figure 26: TPU Context Menu (Assigned)

When a new I/O tree instance of the TPU device is required, the device definition dialog is displayed:

_____________________________________________________________________________________________________


24


Figure 27: TPU Device Instance Dialog

The device address is specified is the first address available under the port (1-255). This is the device number that will be addressed in DeltaV, but will access the TPU under which the tags are being added.

Selecting Edit will bring up the TPU definition dialog. The description defaults to the TPU name of the parent TPU.

The mapping of device address to IP address and tags to dataset registers are the most critical part of the VIM configuration. Care must be exercised to ensure correctness.

Selecting OK will accept the device definition and continue processing the tags in the selected branch.

Selected I/O tags in the tree are displayed in bold. As shown below, the number of tags total and assigned as well as datasets required (total required and assigned), for each branch are displayed when that branch is selected. The display is divided by I/O type and totalized.

Figure 28: Import Dialog

This allows the determination of the number of each type of tag (and datasets) already assigned, and the number available for assignment.

Repeat steps 3.4.6 and 3.4.7

for all TPU‟s in the VIM. When the new TPU is assigned, you may select a new IP address (or one currently assigned). This allows the re-opening of an import file even if the TPU name in the VIM (or SmartTool export file) has been changed.

_____________________________________________________________________________________________________


25


Figure 29: TPU Device Selection Dialog

Once all tags have been added, exit the import dialog. The partner VIM may be configured from the same SmartTool export file.

_____________________________________________________________________________________________________


26


3.4.8. VIM Detail Display with imported

TPU’s

Returning to the VIMNet Explorer display, the detail of the VIM branch will now display the TPU definitions (including tags total and assigned for each I/O type), as well as the TPU instances of each

TPU in the I/O tree (with location).

Figure 30: VIM Detail Display

You may edit the TPU definition by using the context menu on the TPU in the VIM I/O branch detail display.

Figure 31: TPU Device Context Menu

This display also shows the location of the control dataset that contains the time-sync data and control registers as well as the locations of all TPU device instances assigned to the VIM I/O tree.

.

_____________________________________________________________________________________________________


27


3.4.9. TPU Device Level Tag Display

The device level in the I/O tree shows the definition of the device and the tag groups assigned to the device in the detail panel:

Figure 32: TPU Device Instance Detail Display

The device I/O branch has a context menu to allow manually adding tag group place holder (Add Tag

Group). This may be used to reserve space for future tag imports to the device.

Figure 33: TPU Device Context Menu

The dialog opened provides a selection of Tag Group types that may be inserted under the device (on this port). This may not be all types, depending on the available datasets.

Figure 34: Manual Tag Group Selection

Selecting a type and the OK button will enter the tag group in the I/O tree. There will be no tags associated with the group. This may be entered using the import utility from the VIM I/O branch menu.

Other menu items are:



Delete May be used to delete a TPU from the I/O tree.

_____________________________________________________________________________________________________


28




Diagnose



Properties

Opens VIMNet Diagnostic utility with this device instance selected.

Opens the TPU properties dialog for this device.



What Is This? Brings up context sensitive help for this menu

3.4.10. Tag Group Level Display

The detail win dow of the “Tag Group” branch in the I/O tree shows all tags in the group with the path to the tag in the TPU and the description from the TPU. The device level has a

Figure 35: Tag Group Context Menu



Lock/Unlock DS Updates Lock or unlock this tag group so changes to the scan rate set from TPU device properties will not (or are allowed) to change the groups scan rates.



Set DS Update Rate Set a scan rate for individual input datasets in this tag group (for setting all rates see

You can raise the minimum scan rate of the input datasets in a tag group, this is a tuning parameter.

Increasing the minimum will give a better railbus response, with the consequence of increasing the lag time receiving a change (for 200 ms, the oldest data in a 1 second scan being processed by DeltaV should be about 200 ms). This is a matter of system responsiveness and must be determine the exact rate to use on a site basis. Setting some dataset higher will allow the remaining datasets to update faster.

Note: This change only affects input datasets in the tag group.

Note: The value generated here (or from the TPU properties dialog) will be included in the FHX export for

DeltaV. This requires an import into DeltaV after changes here, or manual modifications to the DeltaV

datasets to match the detail display here (see 3.4.11)

The tag group dataset scan interval may be set for individual groups or for all groups in a TPU device

(See Figure 25: TPU Properties Dialog)

3.4.11. Data Set Level Display

The dataset branch in the I/O tree shows the configuration of the dataset as it must be configured in

DeltaV. This allows manual modification to the DeltaV configuration. Simply match the values in the dataset dialog in DeltaV to those shown here.

It also shows the registers in the dataset, and the tag associated with each register and the path to the tag (in the TPU).

_____________________________________________________________________________________________________


29


Figure 36: Dataset Context Menu

The context menu for a dataset in the I/O tree has the “Properties” element. This shows the dataset configuration in the same format that would be see in DeltaV Explorer. This is to allow comparison and display the expected values for DeltaV datasets and the data may not be edited in the properties dialog

(any changes are lost on exiting the dialog).

When you are finished configuring VIMs, continue to Section 3.5. A simplex VIM used for a redundant

TPU uses the same procedure as the primary, but importing from TPU-B configuration.

_____________________________________________________________________________________________________


30


3.5. Uploading a VIM Configuration

VIMNet configuration creates a mapping between DeltaV device addresses and IP addresses. This mapping must be uploaded into the VIM for proper communications. A configuration that has not been uploaded to the VIM is indicated with a blue triangle next to the VIM icon. To upload a configuration, the

VIM must first be commissioned.

Uploading a new configuration into the VIM will cause all field communications to terminate. After upload completion, the VIM will automatically reboot.

VIM upload must be done with the process in safe mode.

Right click on the VIM and select VIM Configuration Upload.

Figure 37: VIM Context Menu Upload Selection

If there have been changes, you will be prompted to save these (see section 3.6).

Figure 38: Upload Save Prompt Dialog

_____________________________________________________________________________________________________


31


Figure 39: Upload Warning Dialog

The Uploading VIM Configuration progress bar will indicate the status of the upload:

Figure 40: Upload Status Dialog

This includes the device address/IP assignments, device instance references, and tag definition packets.

Upon successful completion of the VIM Configuration Upload, click OK.

Figure 41: Upload Completion Dialog

The upload process terminates all communications with DeltaV over the railbus. Upon upload completion, the VIM automatically reboots and goes online. Click OK to terminate the dialog.

If your upload is unsuccessful, you will need to decommission and re-commission the VIM and try again.

Contact MYNAH Support if you are not successful in uploading.

3.6. Saving the VIM Configuration

VIMNet configuration is saved in a file with a VIO extension. This file can be located anywhere in the PC local or network folder. The current state of commissioned VIMs, as well as VIM network device configurations is contained in this file. The VIMNet Explorer does not have to be online all the time.

_____________________________________________________________________________________________________


32


However, if it is restarted, this file should be reopened so that the current state of VIMs does not show as error.

When the VIMNet Explorer is restarted, it will start scanning for VIMs on the network, and display what is found. Commissioned VIMs found on the network will be compared with configured placeholders and there current state displayed. Mismatched VIMs, i.e., those which do not exist as placeholders, or mismatches in MAC address or IP address will be displayed in the Decommissioned list as errors. The following shows VIMs in error.

Figure 42: Decommissioned VIM Dialog (Invalid VIM)

If the original configuration file is not available, the VIMs in error must be manually cleared. The options are to either "Reset" the VIM in the decommissioned list, or to "Reconcile" the mismatched VIM with a configured placeholder in the I/O Net.

To Reset a VIM, right click on the VIM in the Decommissioned list to get the context menu. Then select

Reset as shown below. The VIMNet Explorer will send a Decommission command over the network, and clear the VIM from its list. It is anticipated that the Decommission command will be accepted by the VIM resulting in a decommissioned VIM. The VIM will then appear as an unconfigured, decommissioned VIM in the VIMNet Explorer list.

Figure 43: Decommissioned VIM Context Menu

_____________________________________________________________________________________________________


33


Performing a Reset will decommission a VIM. This will terminate all field communications.

The process of reconciling a detected, commissioned VIM, with an unassigned placeholder allows you to reconstruct a configuration file without decommissioning and then recommissioning the VIM. To reconcile a VIM, right click on the VIM in the I/O Net to get the context menu, and then select Reconcile VIM menu option as shown below.

Figure 44: VIM Context Menu (Reconcile)

This will launch a dialog as follows, showing all the detected, commissioned, and unattached VIMS.

Figure 45: Reconcile VIM Dialog

The reconcile process with immediately create the link without further prompts.

The reconciled VIM will appear as normal and commissioned, and the decommissioned list will be cleared. Note that if you are creating a new configuration file, you must recreate the field device network definitions and then upload to the VIM.

_____________________________________________________________________________________________________


34


3.7. Flash Upgrade of the VIM Firmware

For VIM functionality changes, MYNAH Technologies will issue firmware upgrade files as required. The new firmware files must be flashed into the VIM.

VIM‟s must be commissioned prior to flashing. If the VIM is of a different firmware type, it must be commissioned as that type of VIM, flashed to the FMC firmware, then decommissioned and recommissioned as a FMC VIM.

If the VIM has simulation firmware, it must be commissioned via a placeholder in the “Simulation Net” branch of the I/O tree. For I/O VIM‟s the commissioning is under the “I/O Net” branch.

Flashing VIM with new firmware will cause all field communications to terminate (if a partner

VIM is communicating this will not be interrupted). Upon flash completion, the VIM will automatically reboot, but contain no configuration.

VIM flash must be done with the process in safe mode.

To do this, right click on the target VIM object and select Properties. The following dialog box will appear:

_____________________________________________________________________________________________________


35


Figure 46: VIM Properties Dialog (Commissioned)

Click Flash Upgrade. A warning will appear as follows:

Figure 47: Image Flash Warning

Click "Yes" to start the flash process. Note that while flashing the VIM, all communications with DeltaV

Controller are terminated.

_____________________________________________________________________________________________________


36


Browse to select the firmware file. Firmware files have a .HEX extension. Please contact Mynah

Technical Support for the correct file to use.

Figure 48: Flash Update Open File Dialog

Using an incorrect firmware file may render the VIM inoperable.

Select the file to continue the flash upgrade process.

Note that the file format for the VIM should be:

„vim-FMC722-vmajor_version.minor_version.maintenance_build.hex.

Once the file has been selected, a connection is opened to the VIM and the flash system is downloaded.

During the download, a progress bar will display as follows:

Figure 49: Flash Progress Dialog

_____________________________________________________________________________________________________


37


On completion of flash the status dialog is displayed:

Figure 50: Flash Completion Dialog

Upon completion, the VIM will reboot, however, there will be no configuration in the VIM even if one was present prior to the flash. In order to go online, the VIM now requires an upload of the configuration

(section 3.5) and the configuration to have been imported into DeltaV (section 4.1) and downloaded to the

controller.

In case of two VIMs used for redundant communications to the field, both should be flashed separately to the same firmware revision. Flashing each unit will terminate communications to the field for that unit; however the partner simplex VIM will still maintain communications to the field and control of the TPU(s).

_____________________________________________________________________________________________________


38


3.8. Configuring VIMs on Multiple Subnets

Normally VIM‟s in a VIMNet Explorer configuration (vio file) are configured on the same subnet. VIM‟s may be configured on different subnets in the same configuration file, however each subnet must have a

NIC on the configuration PC with an address on the subnet of each of the VIM‟s. Communications over a router are not currently supported.

When multiple NICs‟ are configured used for connection to VIM‟s then at any one time only one VIM will be directly tied to the VIMNet “master” IP. Several modifications have been made to VIMNet Explorer to allow accessing the required NIC‟s.

If the VIM specified is not on the specified “master IP”, then the detail display for the VIM will have a read

“X” on the IP address line. This signifies VIMNet Explorer cannot communicate with the VIM and

Figure 51: VIM Detail Display (IP Addressing) certain context menu options for the VIM may be grayed out.

Figure 52: VIM Context Menu (Grayed Items)

Open the physical networks properties (context menu on Physical Network in the VIMNet I/O tree). This opens the network settings dialog. By default the “Master IP” address is selected here. You may see all

NIC addresses available in the hosting PC in the “Available NIC” combo box. Selecting an item this and

_____________________________________________________________________________________________________


39


Figure 53: Physical Properties Dialog selecting the NIC that is on the subnet of the VIM in question will enable the “Add” button if the item is not already in the “Used Address” list. If the item is in the list, then it will be highlighted and set as the current

“Master IP”.

If the item is not in the “Used Address” list, then select the “Add” button to add it to the list.

Figure 54: Physical Properties Dialog (Selected Used Address)

When a NIC address is selected in the “Used Address” list the default “Master IP” is set to this value, the

“Delete” button is also enabled, allowing removal of the NIC from the list.

After a NIC is added to or removed from the list and the “Ok” button is selected, the new values are saved. These are save on the machine, not in the VIMNet “vio” file. Now VIMNet will listen to all the selected NIC‟s (subnets) for broadcast messages from VIM‟s in the field, it will use the first IP address in this NIC list which has a subnet that matches the VIM IP address to send and receive message, and it will broadcast on all of these NIC‟s to communicate with the field (such messages as refresh decommissioned list use broadcasts).

If there is an issue with the autom atic selection of NIC‟s for communications with a VIM, each VIM may also have a specific local NIC selection. This is available in the VIM properties dialog (and Add VIM dialog). For the Primary (and when enabled, the secondary partner) in the dialog the NIC specified check

_____________________________________________________________________________________________________


40

FMC 722 VIM User Manual box will enable the selection of one of the NIC‟s in the list of available NIC‟s. Selecting this will override the automatic search for the correct NIC when VIMNet attempts to communicate with the VIM.

Figure 55: VIM Properties (Specified NIC)

When moving the configuration from one PC to another, the NIC IP address will not necessarily match. If this is the case, when VIM net explorer is started the user will be prompted to select one or more NIC IP addresses as necessary to match the subnet of the VIM IP address. Selecting cancel from dialog will remove the IP address, potentially resulting in a loss of communications. Also if the address of a NIC in the PC is changed while VIMNet is running, opening the Physical Network properties and selecting the

“Reset” button will trigger this process.

Figure 56: Alternative NIC Selection Dialog

_____________________________________________________________________________________________________


41


4. Configuring DeltaV

For each VIM module used, four Programmable Serial Cards must be configured in the DeltaV Explorer.

A maximum of 2 VIM modules can be used with each DeltaV controller. The simplex serial cards required must be configured in slots 57-60, or 61-64. To add these cards, follow the steps below. Note that cards can also be added via the DeltaV Explorer, using the Auto-sense I/O cards menu option (following the commissioning and optionally uploading of the VIM). All four cards must be configured, even if you are not using all of them. In addition, disable all unused serial card ports.

4.1. Configuring DeltaV with FHX import file

To simplify the process of creating DeltaV dataset the VIM level in the VIMNet Explorer I/O tree has a context menu item “Export FHX File”. Selecting this will allow the creation of an FHX file for import into

DeltaV containing the card configuration including device and datasets as configured in the VIM.

Figure 57: VIM Context Menu (Export FHX)

If in run on a DeltaV ProPlus or Appstation, this will access the OPC server to get version. If run on a separate PC, versions 6.3, 9.3, 10.3, or 11.3 may be generated. If another DeltaV version is in use, then the FHX file must be migrated to the needed version.

_____________________________________________________________________________________________________


42


This file may be imported using DeltaV Explorer “File”\“Import”\“Standard DeltaV Format…”

Figure 58: DeltaV Explorer Import FHX Context Menu

As cards will not be overwritten by an import, the cards must be first removed if already present in the configuration prior to importing the FHX.

_____________________________________________________________________________________________________


43


4.2. Manually Configuring DeltaV

When manually configuring DeltaV I/O tree with DeltaV Explorer, you may use the VIMNet port, device, and dataset detail displays to get the required parameters. The settings in DeltaV must match those uploaded to the VIM for proper communications to be initialized.

4.2.1. Configure Serial Card and Ports

In DeltaV, configure the serial card. This will create a Programmable Serial Card and define 2 ports under it, P01 and P02. Select the Card is always configured as simplex, do not check the “Card is r edundant” checkbox. Cards must be configured in the 57 to 64 range, and must be added in groups of

4. Each VIM emulates 4 cards and all 4 must be configured in DeltaV or the VIM will not initialize communications with DeltaV (or the field).

Figure 59: DeltaV Card Properties Dialog

Right mouse click on Port 1. The following dialog will appear.

_____________________________________________________________________________________________________


44


Figure 60: DeltaV Port Properties Dialog (General Tab)

Make sure that you Enable the port to be used by clicking on the Enabled box in the. Unused ports

Note

should be left disabled.

Next, select the “Advanced” tab. The following dialog will appear. In this dialog, select “Master”. Also select the fsmessage time parameters. All FMC devices configured under a given port will use the same time parameters. Timeout for a FMC device is the greatest value specified for any port on which device is configured. The timeout should be 1000 ms, with no retries. Best practice is to set all ports containing a

TPU device to same value

Figure 61: DeltaV Port Properties Dialog (Advanced Tab)

Increasing the transmit delay will increase the interval between I/O scans for the devices specified under the port. This is specified in 100 micro second intervals rather than the displayed ms. With zero (0) being

_____________________________________________________________________________________________________


45

FMC 722 VIM User Manual the default value of 10000 microseconds (or 10 ms). Selecting 200 will specify a 20 ms interval (20000 microsecond) interval, 500 a 50n ms. All FMC devices under a port will have the same value, inter-scan delay for a FMC device is greatest value specified for any port on which device is configured. Best practice is to set all ports containing a TPU device to same value

Next, click the Communications tab. The following dialog will appear. These parameters are not used.

Simply select the defaults and click OK. Repeat for second port if used

Figure 62 DeltaV Port Properties Dialog (Communications Tab)

4.2.2. Configure Devices

Configure a Serial Device under the Port by doing a Right Mouse click and selecting New Serial Device.

The following dialog will appear: There may be multiple devices under a port with datasets under the devices. For FMC types there will always be at least 2 datasets as the smallest tag group size is 2 for DI and AI points.

Figure 63: DeltaV Device Properties Dialog

Specify the device address and description. Then click OK. This will add the serial device.

The Device Address must correspond to the device address in VIMNet Explorer.

Note

_____________________________________________________________________________________________________


46


4.2.3. Configure Datasets

Next, configure datasets in the Serial Device. Each Serial Device can have 16 datasets under it. Or you can have 16 devices with 1 dataset each. A dataset can be input or output. To add a new dataset, right mouse click on the Serial Device and select New Dataset. Datasets must be assigned in groups as required for each TPU point type (one dataset for each parameter in the point type). The following dialog will appear.

Figure 64: DeltaV Dataset Properties Dialog (General Tab)

Configure the data direction to be input or output. In the above example, we are configuring an input dataset.

If the dataset direction is Output, you must select the Output mode. Output mode of 0 indicates Block outputs, i.e., the entire dataset is written out if any dataset register changes. An Output mode of 1 indicates Single value output, i.e., only the value that has changed will be written out. Select 1 (individual outs) to allow individual writes to the tags assigned to the dataset

Output datasets can also be read back from the VIM by selection the “Output read back” checkbox. Note that for Output datasets with read-back, pending output changes always have precedence. Select readback for the DO setpoint and AO mode registers, leave this unselected for AO floating point value datasets.

_____________________________________________________________________________________________________


47


Next, click the DeltaV tab. The following dialog will appear:

Figure 65: DeltaV Dataset Properties Dialog (DeltaV Tab)

In this dialog, configure the data type needed for DeltaV. You can see the available types by clicking on the drop down list. In the above example, we are configuring the input data type to be floating point.

Please see 5.6 “DeltaV register definitions for TPU Tag Point Types” for additional details for this parameter.

Next click the PLC tab. The following dialog will appear.

Figure 66: DeltaV Dataset Properties Dialog (PLC Tab)

In this dialog, we will map DeltaV data types to PLC (or external Device) data types. PLC data type values and correspond to the tag point type, registers addresses in the dataset are based on this:

Device Tag Type

DO

DI

AO

AI

Device data type

1

2

3

3

Data Start Address

0 ,50,100…

10000 ,10100,10200,…

20000

,20050,2010,0…

30000

,30050,30100,…

Number of Values

50

100

50

50

TimeSync Dataset 6 0 50

_____________________________________________________________________________________________________


48


Device Tag Type

Reserved

Device data type

All other values

Data Start Address Number of Values

30

4-1 PLC Data Type Values, Registers, Start Addresses, and Sizes

The Start Address specifies where in the tag index that will be assigned to the tag for communications with the TPU. A starting address of 10000 results in registers with addresses (and tag indexes of 10001 to 10050 (for AI only 50 registers are allowed in datasets).

Lastly, for each dataset click on the Special data tab. The following dialog will appear:

Figure 67: DeltaV Dataset Properties Dialog (Special Data Tab)

5

6

7

1

2

3

4

Special Word 1

In word 1, enter the tag parameter that will be accessed via this dataset. These are shown in the following table:

Code DO DI AO AI AI Ext

SP

PV (read-back)

PV (readback)Status

Check-back

PV

PV Status

SP

SP Mode

PV (read-back)

PV (readback)Status

PV (readback)Step

Check-back

PV

PV Status PV Status

PV

Sensor

Sensor Status

4-2 FMC Dataset Special Word 1 (Parameter Type)

_____________________________________________________________________________________________________


49


Special Word 3

Special word 3 is used to configure non-default input access timing. These values are specified to prevent excessive updates to DeltaV. This contains an integer value comprised of multiple access bytes. If addressed in HEX, the format will be displayed as 0xBBAA, where the bytes specify specific actions in the VIM.

Byte Field Description Values

AA 1-255 = 50 to 12750 ms, or

0 is the default value of 50.

BB updateDelayinterval This is the minimum interval for the VIM firmware to send updates to DeltaV. As each register in the dataset will be updated asynchronously from the TPU and each incoming message could trigger an update to the DeltaV database, this byte may be used to prevent the continuous streaming of individual register updates, but instead will allow time for multiple registers to be updated prior to a single message. forcedUpdateInterval This register specified the maximum interval between updates to DeltaV. If there is no change in the field within this time period, The

DeltaV database will be refreshed with the current value.

1-255: 0 is the default value of 500 ms. Other values may be used, i.e., 50 to

12750 ms.

4-3 Special Word 3 format

Special word 3 in the FHX import file generated by VIMNet Explorer is set to 0 (the default values). This may be changed as necessary in DeltaV Explorer and downloaded to modify the behavior of the TPU input updates.

Repeat dataset configuration for all datasets configured in the VIM. This must match that shown in VIMNet Explorer. Or the VIM may not properly enable communications to the TPU.

_____________________________________________________________________________________________________


50


4.3. Configuring a Time Sync Module

The FMCTimeSync function requires capture of the current UTC time from the DeltaV controller and transmission of this time to the associated TPU. Without the time sync module, the VIM will never receive the timestamp from DeltaV and will never initialize communications with the field TPU. This TimeSync is triggered when the VIM initially connects to the TPU, re-connects following receipt of a welcome message from the TPU, or on a daily basis (24 hours intervals after initial connection). The VIM does not maintain the time but when the TimeSync function is triggered sets a bit in an input register in DeltaV, then waits for the DeltaV to send the current time in one of its registers. The VIM then immediately adds this to a packet and sends it to the TPU. On receipt of an Ack message from the TPU the VIM resets the register bit that triggers the re-write from DeltaV. DeltaV should continuously send the time value while the register is set. The VIM will only read this if the TimeSync operation is active. The value will be re-read if the VIM receives a Nak or does not receive a reply (timeout). The registers are defined in the “Global Ctrl

Tag Group” automatically assigned when the first TPU with TimeSync enable is added. This group contains one dataset, 32-bit unsigned integer output w/read-back (50 registers used). The first register is the DeltaV write trigger, in this register bit 0 is the trigger for writes to device 1, bit 1 is for device 2, etc.

Registers 2 to 3 are reserved for devices 2 to 3 if configured in the VIM. The remaining registers are reserved for future use.

The time sync module in DeltaV should have the following layout:

Figure 68: DeltaV Time Sync Function Block Code

In here the Input trigger register is tied to the input of a calc block. The block monitors this input and on non-zero value, writes to the appropriate output register(s). The expression in the block is:

TRIP_VALUE :='//NODE1/IO1/C60/P02/DEV01/DS01/R1.CV';

IF (TRIP_VALUE != 0) THEN

TimeValue := time('$time_format:UTC');

IF (IN1 & 1) THEN

REM Device 1

'//NODE1/IO1/C60/P02/DEV01/DS01/R2.CV');

ENDIF;

'//NODE1/IO1/C60/P02/DEV01/DS01/R2.CV' := time('$time_format:UTC');

'^/FMC01_A_UPD' := TIME_TO_STR("%y/%m/%d %h:%i:%s",

IF (IN1 & 2)THEN

REM Device 2




ENDIF;

_____________________________________________________________________________________________________


51


IF (IN1 & 4)THEN

REM Device 3




ENDIF;

IF (IN1 & 8)THEN

REM Device 3


ENDIF;



ENDIF;

The DeltaV function “ time('$time_format:UTC'); ” is used to get the time directly into the internal output parameter for the device(s), i.e., CURRENT_GMT_DEV1, 2, or 3 as specified here. This function should go to the parameter and not to the output of the calc block as when written to the calc bock output it is update at 1 second intervals rather than immediately on write (it is also written to the output parameter for display purposes only.

If DeltaV is not configured to write the time sync value when prompted, the communications to the field will be suspended prior

Note

to initialization. Proper configuration of this module is essential.

Each TPU is referenced by a trip bit in the trip register. The input value is

“AND”‟d with the appropriate bit to determine if the time value for that TPU is needed by the VIM. You cannot test the register for a single value, but must test for bits as multiple bits may be set at the same time.

Note: A manual trip of the time sync process is possible by setting the appropriate bit in the force trip register specified in the module.

4.4. Configuring DeltaV writes to TPU

When updating a value in a DeltaV module, if the current value matches that in the DeltaV database, the value is not written to the field. For an analog output (AO) or discrete input (DI) tag, this means if the mode written in the module does not change, it will not be written to the TPU. As the VIM only writes outputs by exception (on update from DeltaV), this would prevent sending an AO with the same mode and value (such as move 10).

To allow this type of update, the output registers (DO setpoint and AO mode) are configured as 32-bit unsigned integers with read-back. The VIM will use the high 16 bits as an update field. When the VIM receives the value from DeltaV it sets the update field as received (0x0008), this value is changed to sending (0x0004) when the message is added to the outgoing packet. When an acknowledgment is received from the TPU the value is updated to (Acked: (0x0001 or Nacked: 0x0002), finally if there is no response from the TPU, then field is set as failed (0x0018).

This means on read-back of the output register (distinguished from the tag read-back input value), the output register in the DeltaV module will have a value consisting of the update field and the output from

DeltaV, therefore the value for this output register in the DeltaV database will always be different from the

_____________________________________________________________________________________________________


52


1

1

1

1

0

0

0

1

SP

0

0

0

2

2

2

1

2

2

2 required setpoint, and the value will always be able to be written from DeltaV. This also gives diagnostic information from the VIM on the state of the write.

Status

Hex

0x0010

Decimal

0x0008

0x0004

0x0001

0x0002

0x0018

Meaning of value

Waiting VIM has received the configuration for the tag (during initialization or spontaneously from TPU) and is waiting for an output of the SP value or mode (DeltaV

Processing

Sent

Acked has not written the value)

VIM has received value from DeltaV and is processing message

VIM has sent message, waiting for ACK from TPU

Nacked

TimedOut

VIM has received and acknowledgment from the TPU for the tag update.

VIM has received and negative acknowledgment from the TPU for the tag update (update failed).

VIM has send the value to TPU but has not received a response within the timeout period, message or response may have been lost due to collision or other reason. The timeout is based on the highest interval on any port on which the device is instantiated, best practice is to set all ports with the device to the same value, default 1000 ms.

4-4 Output Status Values

Examples:

Update Field

Hex Meaning

0x0008 Processing

0x0004 Sent

0x0001 Acked

0x0002 Nacked

0x0010 Waiting For Output

0x0018 TimedOut

0x0008 Processing

0x0004 Sent

0x0001 Acked

0x0002 Nacked


0x0018 TimedOut

0x0008 Processing

0x0004 Sent

0x0001 Acked

0x0002 Nacked


0x0018 TimedOut

Read-back

(SP register)

0x0000

0x0000

0x0000

0x0000

0x0000

0x0000

0x0001

0x0001

0x0001

0x0001

0x0001

0x0001

0x0002

0x0002

0x0002

0x0002

0x0002

0x0002

Value

Hex

0x00080000

0x00040000

0x00010000

0x00020000

0x00100000

0x00180000

0x00080001

0x00040001

0x00010001

0x00020001

0x00100002

0x00180001

0x00080002

0x00040002

0x00010002

0x00020002

0x00100002

0x00180002

Decimal

524288

262144

65536

131072

1048576

1572864

524289

262145

65537

131073

1048577

1572865

524290

262146

65538

131074

1048578

1572866

4-5 Output (SP) Register read-back Examples

_____________________________________________________________________________________________________


53


This means the status word value of 0x10 (16) or 0x01 (1) are both valid status values for the read back of the setpoint (DO) and mode (AO). This value is set because when the VIM receives a configuration response it gets the read-back value (step for AO) from the field, not the setpoint (or mode). The setpoint

(mode) defaults to 0 and may not match the value that is used to get the specified read-back. The VIM cannot determine what the setpoint or mode should be and so marks this for DeltaV as waiting.

Note: DeltaV should be able to write the correct value (with the expected high word, i.e., 65536 or 65537 for setpoint of 0 or 1, or other setpoint/mode value as appropriate) to set the value without triggering a write to the field. This is because writing a value with the high word non-zero will not trigger the write, but will update the new value in the register returned to DeltaV (to prevent multiple writes of the same value.

Alternatively writing the value with a zero (0) for the high word will trigger a write to the field and return the expected value (or failed status if write fails).

0x0010 and 0x0018 show a non-written or failed write to field. A 0x0002 shows a rejection of the value by the TPU.

For AO tags, the analog value should be written on scan prior to the mode value. This will insure the appropriate values are written together as the output is triggered by the write to the mode.

_____________________________________________________________________________________________________


54


4.5. TPU Tag definitions in DeltaV

A TPU DeltaV cross-reverence csv file may be exported from VIMNet Explorer

Figure 69: VIM Context Menu (Export TPU CSV File)

This file may be imported into Excel and used as a reverence between the DeltaV I/O addresses

(Card\Port\Device\Dataset\Register) and the TPU path for each parameter of every tag.

"TPU","Tag Type","Tag","Path","Name","Description","DS Description","DeltaV IOPath","Controller

Node","Card","Port","Device","DataSet","Register"

"SPCU P40-A - TPU 1A"," DO","2AMVG411A$1368","SPCU P40-A - TPU 1A\G411 SEM

A\Actuators","AMV","AMV","Setpoint Value","NODE01/IO1/C57/P01/DEV01/DS01/R1","NODE01",57,1,1,1,1


A\Actuators","AMV","AMV","Read-back Value","NODE01/IO1/C57/P01/DEV01/DS02/R1","NODE01",57,1,1,2,1


A\Actuators","AMV","AMV","Read-back

Status","NODE01/IO1/C57/P01/DEV01/DS03/R1","NODE01",57,1,1,3,1


A\Actuators","AMV","AMV","Check-back","NODE01/IO1/C57/P01/DEV01/DS04/R1","NODE01",57,1,1,4,1

"SPCU P40-A - TPU 1A"," DO","2AWVG411A$1369","SPCU P40-A - TPU 1A\G411 SEM

A\Actuators","AWV","AWV","Setpoint Value","NODE01/IO1/C57/P01/DEV01/DS01/R2","NODE01",57,1,1,1,2


A\Actuators","AWV","AWV","Read-back Value","NODE01/IO1/C57/P01/DEV01/DS02/R2","NODE01",57,1,1,2,2


A\Actuators","AWV","AWV","Read-back

Status","NODE01/IO1/C57/P01/DEV01/DS03/R2","NODE01",57,1,1,3,2

. . .

Each tag point type has different parameters in the TPU. These parameters are also present in the VIM

datasets in the DeltaV controller, although some have different data types (See section 2.3). Each line in

the “.csv” file is one parameter for a tag, with tag and parameter name, description, TPU and DeltaV paths, as well as other details.

_____________________________________________________________________________________________________


55


Figure 70: TPU / DeltaV cross reference in Excel

_____________________________________________________________________________________________________


56


5. VIMNet Diagnostics

VIMNet Diagnostics are provided to assist you in troubleshooting abnormal situations, and to view network communications statistics. VIMNet Diagnostics can be launched multiple times, once for each active VIM in the network. Or a single instance of Diagnostics can be used to view all active VIMs. Vim‟s on different NIC cards in the PC may be accessed by selecting the NIC card to access in the

“File”/”Setting” menu item, only VIM‟s on the selected NIC may be communicated with. Launch the

Diagnostics application by right clicking on the commissioned VIM in the VIMNet Explorer as follows:

When using VIMNet Diagnostics, the polling rate for communications may be configured, see section 5.5.

When the diagnostics application is launched select “Enable VIM Communications” in the VIM context menu. This opens a network connection with the VIM specifically to poll (read) diagnostic information.

The information is continuously scanned and displayed in the window. You can select the scan rate,

however the default rate is 1 second (see section 5.5). This rate should have no impact on performance

of the VIM.

This is independent of the „Dynamic Status Updates‟, see Figure 11: Advanced IP Selection

Dialog.

Figure 71: VIMNet Diagnostics VIM Context Menu (Enable Communications)

Diagnostic information is displayed at each level of the VIM architecture. You can drill down to the dataset level, which is the lowest level. The following screens show diagnostic information at each level, starting with the VIM level. No polls are sent to unless an I/O branch of the VIM is selected. When diagnostics closes the VIM is no longer polled for status.

If the logger is started, the VIM spontaneously sends messages as triggered by events in the VIM, it also opens a dialog window on the PC that displays these messages. When Diagnostics (or the logging window) closes, this does not stop. Logging should be used with caution and only at the direction of

Mynah Technical support personal as this may have an impact on VIM communications performance.

When not used, it should be stopped (menu item should read “Start Logger”.

_____________________________________________________________________________________________________


57


5.1. VIM Level Diagnostics

The first screen after launch is as follows:

Figure 72: VIMNet Diagnostics VIM Detail Display

When the VIM diagnostics initial opens all VIMs have disable communications. This is independent of the

“Dynamic Status Updates” in section 3.9. Right click on the VIM and select Enable updates.

The information displayed in this window is explained in Table 2 below:

Diagnostic Item

VIM Mode

Data Poll Queue Number of messages waiting to be sent to DeltaV

Pending Message Queue Number of waiting diagnostics message responses to be sent to DeltaV

Railbus Message Queue

Description

Shows current mode: Commissioned, Failsafe, etc.

Serial Bus Poll

Number of waiting Railbus messages received from DeltaV to be processed

Counter of poll requests received from Controller

_____________________________________________________________________________________________________


58

Diagnostic Item

Dataset Value Reads

Dataset Value Writes

Default Reads

Pending Data Reads

Pending Data Writes

Railbus Ticker

Plug and Play Ticker

Dataset Handler Ticker

IP Address

DeltaV Devices

Network Devices

Application

Flash I/O Step

Flash I/O Connected

Flash I/O Error

Logging to

Total # DS

Maximum I/O Scan (ms)

Minimum I/O Scan (ms)

Average I/O Scan (ms)

Maximum packets (/s)

Minimum packets (/s

Average packets (/s

Maximum Msgs(/s)

Minimum Msgs (/s)

Average Msgs (/s)

Generation Rate (/s)

Poll Rate (/s)

Number of Buffers

% Available Buffers

Buffer Resets


Description

Counter of dataset value read requests received from Controller

Counter of dataset value write requests received from Controller

Counter of default read requests received from Controller

Counter of pending data read requests received from Controller

Counter of pending data write requests received from Controller

Ticker of process handling Railbus messages

Ticker of process handling Plug/Play messages

Ticker of process handling dataset updates

IP address of VIM

Number of DeltaV devices in configuration from Controller

Number of devices configured/found

Application type: FMC Subsea TCP (FMC722)

Reserved for Flash evaluation



IP address of PC if message logging is turned on

Total number of datasets in this configuration

Maximum scan time (ms) for I/O on devices

Minimum scan time (ms) for I/O on devices

Average scan time (ms) for I/O on devices

Maximum packets sent and received by VIM per second

Minimum packets sent and received by VIM per second

Average packets sent and received by VIM per second

Maximum tag messages received per second

Minimum tag messages received per second

Average tag messages received per second

Rate of DS changes detected in field data

Rate of DS Polls received from DeltaV controller

Number of available railbus buffers, maximum 255

Percent of railbus buffers available

Number of times the railbus buffer stack has been reset

5-1 VIM Diagnostics

_____________________________________________________________________________________________________


59


You can right click on the VIM to get a context menu. From this menu, you can clear all statistics by selecting Reset All Statistics. When the diagnostics utility first loads, all VIM connections initialize in disabled mode , i.e., it will not poll the VIM‟s in the I/O list for diagnostic data. Use this context menu to enable those VIM‟s that are being tested. This initializes polls to the VIM for the status of whichever branch of the I/O tree for the VIM that is selected. When the diagnostic utility closes all diagnostic polling is terminated.

Figure 73: VIMNet Diagnostics VIM Context Menu (Reset Statistics)

5.2. Port Level Diagnostics

Port level diagnostics show the port status, as well as status of datasets. Dataset status is shown as a character string corresponding to any error which might exist. This same error string is also displayed in

DeltaV Diagnostics.

The Link Status and Channel Status are shown as hexadecimal error codes. The error message column contains any error that might exist. If no error exists, then the status shown is "Good".

Figure 74: VIMNet Diagnostics Port Detail Display

_____________________________________________________________________________________________________


60


5.3. Device Level Diagnostics

Device level diagnostics show the statistics for selected device as follows:

Figure 75: VIMNet Diagnostics TPU Device Detail Display

Detail description of parameters:

Field Description

Device Network

Index

Communications

Type

Current Step

This is the index of the device in the VIM, must also the device address in DeltaV

(1-255).

Specifies the underlaying protocol (TCP), the TPU device IP address and port for communications.

Current communications step from “Field Device off line (0)” to“FMC_Field device onlin e (20)”. This value changes during communications initialization and

_____________________________________________________________________________________________________


61


Field

Connected

Socket error code

Network Timeouts

Packets Sent

Packets Received

Packets w/errors

No Ack/Nack

Description termination, the normal value is “FMC_Field device online (20)”.

Text

Field Device off line

Code

0

Description

Device is not communicating, no configuration, or failed connection.

Field Device initializing 1

Start I/O connect

Socket connecting

2

9

VIM is preparing to start an I/O connection to the field device, getting IP address, port, and required paramters.

Find device in field by IP address.

Socket connect failed

Socket connected

FMC Cmd step Initialize

FMC

FMC Cmd step Wait for accept

FMC Cmd step Send time sync

FMC Cmd step Wait time sync

FMC Cmd step Set tag indexes

FMC Cmd step Wait tag indexes

FMC Cmd step Get Cfgs

10

11

12

13

14

15

16

17

18

IP address has been found, attempting to open TCP connection to TPU

Unable to open TCP connection, check

IP address and port.

TCP connection is active

Start nnegotiations with TPU, initialize variables for FMC protocol.

Waiting for a “Welcome” message from

TPU

Request time from DeltaV

Waiting for time update from DeltaV, then response (ack) from field.

Sending assigned tag indexes to TPU for all configured tags

Waiting for responses (ack‟s) for all tags

FMC Cmd step Wait Cfgs

FMC_Field device online

19

20

Send request for tag configurations (all is default)

Waiting for all tag configurations

FMC_Net Connect Err Snd 1 22

FMC_Net Connect Err Snd 2 23

TPU is online and communicating

(sending input messages, accepting outputs)

Send socket unable to be written to

FMC_Comm Timeout Err

Snd

FMC_Comm Timeout Err

Rec

FMC_Config In Progress

24

25

26

Failed sending message to TPU

(internal)

Transmit timed out while sending bytes to socket

Receive timed out waiting for bytes in socket buffer

VIM is in configuration mode (upload from VIMNet)

ERR_ICMP Ping Failure 41 Unable to find TPU IP address (ICMP ping) during initialization.

Set to “Yes” when TCP connection is opened, also specifies number of retries on messages (should be 0, as TCP handles retries)

Error on socket connection, processing

Number of timeouts on network connections

Total FMC722packets sent by VIM

Total FMC722 packets received by VIM

Number of FMC722 packets with errors in formatting

Number of FMC722 messages sent with no response (for those that expect

_____________________________________________________________________________________________________


62


Field responses

Description either an Ack or Nack.

Message Retries

Device Delay/Msg

TO

RX TO Count

Number of retries of messages

Time between processing of device I/O (ms), default 10 ms. Also the time to wait for a complete message (ms), default is 1000.

Minimum Time (ms)

Average Time (ms)

Number of messages that were not completely received (received a sync byte, but unable to capture the rest of the message within the timeout period).

TX TO Count Number of messages than were unable to send within the timeout period.

Maximum Time (ms) The time between device I/O scans and the time to process the I/O for a single scan, maximum, minimum, and running average of last 10 scans.

Maximum Messages Should be one as messages are not poll-response, all messages are sent individually and sequentially.

Device Comm Ticker Incremented on each

Pings Sent Number of “FMC” pings sent to TPU, there should be one every 10 seconds

Ping Good Incremented on each valid response to the “FMC” ping

Response

Ping No Response

Ping Retries

Number of timeouts to “FMC” pings (10 second timeout period).

Number of times the VIM has retried sending a “FMC” ping, the connection will be failed after three consecutive timeouts.

Max Packet Interval The time between receiving packets from field device (TPU), maximum,

Min Packet Intervel minimum, and running average of last 10 scans.

Avg Packet Interval

Comm IP in use IP address of field device (active)

5-2 Device Diagnostic Values

You can right click on the device to get a device context menu as follows. This menu allows you to reset the statistics and also to search for configured datasets in this device if not updated when diagnostics program initializes.

Figure 76: VIMNet Diagnostics TPU Device Context Menu

_____________________________________________________________________________________________________


63


5.4. Dataset Level Diagnostics

By clicking on the individual dataset under Device diagnostics, you will get the dataset specific diagnostic information as follows:

Field

Tag Type

Messages Sent

Messages Received

Message Errors

No Responses

Message Retries

Dataset Scan (ms)

Time Between scans

Dataset Registers

Register update flags

Register n

Figure 77: VIMNet Diagnostics Dataset Detail Display

Description

Type of tag and parameter stored in this dataset

Number of messages sent to TPU for tags configured in this dataset, this only increments for output parameter datasets (SP and Mode). Number in parenthesis is number since last read.

Number of messages received from the TPU for tags configured in this dataset, this only increments for input parameters datasets. Number in parenthesis is number since last read.

Messages with received errors

No response to sent messages (ack/nack)

Number of retries on messages (0)

Number of messages send/received per second. This is calculated in diagnostics from number read per scan. Scan interval and poll response time are also displayed.

This is the interval between scans of the datasets and between updates to

DeltaV.

Number of registers (tags) configured for this dataset.

Flags for each register in dataset, toggled whenever a message is received for the tag.

Calculated interval between messages from TPU (accuracy depends on diagnostic‟s poll rate.

5-3 Dataset Level Diagnostics

_____________________________________________________________________________________________________


64


Items of specific interest at this level are the "Dataset scan" and the "Time between scans". These pieces of information tell us what the scan time for this dataset is, and how much time elapses between two consecutive scans and updates to DeltaV database.

5.5. Diagnostics Impact on Vim and network communications

All communications to and from a VIM have an impact on the overall network and on the VIM processing.

For the diagnostic utility, this impact is negligible as the default communications rate is polling at a 1 second interval. This rate is set by selectin g “Settings” in the “File” menu of the interface.

Figure 78: VIMNet Diagnostics File Menu

This poll rate may be increased to a maximum of 200 ms or decreased as low as 5 seconds. Also, individual VIM‟s in the I/O tree may be selected for polling (by default all are disabled when the window is opened).

Figure 79: VIMNet Diagnostics Settings Dialog

The logging window selected with the “Start Logger” item in the VIM context menu has a potentially greater impact on the VIM, however under normal operations there is almost no impact. This logging utility enables messages to be dynamically sent from the VIM when specific circumstances occur.

Note

While the diagnostic polls from the diagnostic utility terminate when the utility is closed, if the logger was started, then the VIM will continue to send messages to the logging IP unless the logger is stopped (“Stop Logger”).

_____________________________________________________________________________________________________


65


6. Operational Check

6.1. Scope

The following sections provide some assistance to ensure the interface is working properly.

6.2. Verify Hardware and Software Version Number

You can verify that the FMC Subsea TCP driver has been installed using the DeltaV Diagnostics tool.

The Diagnostics tool will show the Hardware Revision number (HwRev) and the Software Revision number (SwRev).

To begin the DeltaV Diagnostic tool select Start-> DeltaV-> Operator-> Diagnostics. In the Diagnostics tool, expand the Controller, I/O, and then double click on the Programmable Serial Interface Card that has the driver installed.

The following information will be displayed:

HwRev

SwRev

Hardware Revision 1.1 or later

Software Revision 1.0 or later

6-1 Verifying Hardware and Software Version Numbers

6.3. Verify Configuring

Verify the port configuration. The serial port must be enabled. You need to make sure those communication settings such as baud rate, parity, and number of data bits matches the field device settings.

Verify dataset configuration: The datasets configured must be as shown above.

6.4. Verify I/O Communication with Control Studio

You can create I/O modules in the control studio to verify correct values are read from the VIM. For AI and DI data, the values should be changed in the field devices and verified that the new data are correctly reported in DeltaV. Similarly, verify that the AO and DO data is being written correctly from DeltaV to the field devices.

6.5. Using DeltaV Diagnostics

Verify VIM communication: Select the emulated PSIC in Diagnostics and press the right mouse button.

Select Display Real -Time Statistics from the drop down menu. If the PSIC is functioning, then you will see the Valid Responses counter and the Async and/or Sync Transactions counter incrementing. There will not be any errors counting up.

Verify port statistics: Select the Port on the emulated PSIC and press the right mouse button. Then select

Display Port Statistics form the drop down menu. Verify that the port communications statistics are being displayed properly and are counting as expected for the protocol‟s functionality.

Verify dataset values: Select a dataset and press the right mouse button. Select View Dataset Registers from the Drop down window. Verify that the dataset values are displayed as expected.

_____________________________________________________________________________________________________


66


6.6. LED Indication

The VIM has six LEDs in front. Top to bottom, these are as follows:

1

Red

Power

Fault

Green Active

Green Standby

Amber Network Communications

Amber Railbus Communications

6-2 LED Indicators

Green

Red

Green

Green

Amber

Amber

Green

Red

Green

Green

Amber

Amber

Green

Red

Green

Green

Amber

Amber

Green

Red

Green

Green

Amber

Amber

Green

Red

Green

Green

Amber

Amber

If two VIMs are used to enable redundant access to the TPU pair, then both VIMs (or either VIM) may have active state displayed.

The following table describes the VIM operational state as indicated by the LEDs:

LED

Green

Red

Green

Green

Amber

Amber

State

ON

OFF

OFF

OFF

Blink

Off

Description

The VIM is Decommissioned. It does not have an assigned IP address.

Use the VIMNet Plug and Play Server to configure a VIM placeholder. The VIM placeholder contains the IP address for your network. Then commission the VIM as described in Section 3.

The VIM is Commissioned. It is not communicating on the Railbus. Verify that the DeltaV controller has been downloaded. Also, verify that the field device configuration has been uploaded into the VIM from the VIMNet Plug and Play Server.

ON

OFF

ON

OFF

ON

ON

ON

OFF

ON

OFF

Blink

OFF

ON

OFF

ON

OFF

Blink

ON

The VIM is Commissioned, and communicating with the field devices, as well as with the DeltaV controller.

The VIM is Commissioned, and communicating with the DeltaV controller. The field device communications have errors.

ON

OFF

ON

OFF

Blink

OFF

ON

ON

X

X

X

X

The VIM is Commissioned, but communications with the DeltaV controller are not active. The field device communications have errors.

The VIM is in fault. All other LED states (marked with X) are not significant.

6-3 Simplex VIM LED State Specifications

_____________________________________________________________________________________________________


67


7. Figures

Figure 1: Subsea System Topography ......................................................................................................... 5

Figure 2: Simplex/Redundant FMC Subsea TCP Network ........................................................................... 6

Figure 3 Simplex VIM Assembly ................................................................................................................. 10

Figure 4 Two Simplex VIM Assembly‟s ....................................................................................................... 10

Figure 5: Redundant TPU Assembly .......................................................................................................... 11

Figure 6:Installation MSI file ........................................................................................................................ 12

Figure 7: XP Menu Selection ...................................................................................................................... 13

Figure 8: Windows 7 Menu Selection ......................................................................................................... 13

Figure 9: Initial VIMNet Screen ................................................................................................................... 14

Figure 10: Default IP Address Selection ..................................................................................................... 14

Figure 11: Advanced IP Selection Dialog ................................................................................................... 15

Figure 12: Dynamic Status Updates Overrides........................................................................................... 15

Figure 13: I/O Network Context Menu ........................................................................................................ 17

Figure 14: Controller Context Menu ............................................................................................................ 18

Figure 15: VIM properties Dialog ................................................................................................................ 18

Figure 16: VIM Detail Display...................................................................................................................... 19

Figure 17: Decommissioned VIMs Detail Display ....................................................................................... 20

Figure 18: VIM Context Menu (Decommissioned) ...................................................................................... 20

Figure 19: Commission VIM Dialog ............................................................................................................ 21

Figure 20: FMC VIM Context Menu (Commissioned) ................................................................................. 22

Figure 21: TPU Import Dialog ..................................................................................................................... 22

Figure 22: SPCU (TPU) Context Menu (Unassigned) ................................................................................ 23

Figure 23: TPU Properties Dialog ............................................................................................................... 23

Figure 24: TPU Context Menu (Assigned) .................................................................................................. 24

Figure 25: TPU Device Instance Dialog ...................................................................................................... 25

Figure 26: Import Dialog .............................................................................................................................. 25

Figure 27: TPU Device Selection Dialog ..................................................................................................... 26

Figure 28: VIM Detail Display...................................................................................................................... 27

Figure 29: TPU Device Context Menu ........................................................................................................ 27

Figure 30: TPU Device Instance Detail Display .......................................................................................... 28

Figure 31: TPU Device Context Menu ........................................................................................................ 28

Figure 32: Manual Tag Group Selection ..................................................................................................... 28

Figure 33: Tag Group Context Menu .......................................................................................................... 29

Figure 34: Dataset Context Menu ............................................................................................................... 30

Figure 35: VIM Context Menu Upload Selection ......................................................................................... 31

Figure 36: Upload Save Prompt Dialog ...................................................................................................... 31

Figure 37: Upload Warning Dialog .............................................................................................................. 32

Figure 38: Upload Status Dialog ................................................................................................................. 32

Figure 39: Upload Completion Dialog ......................................................................................................... 32

Figure 40: Decommissioned VIM Dialog (Invalid VIM) ............................................................................... 33

Figure 41: Decommissioned VIM Context Menu ........................................................................................ 33

Figure 42: VIM Context Menu (Reconcile) .................................................................................................. 34

Figure 43: Reconcile VIM Dialog ................................................................................................................ 34

Figure 44: VIM Properties Dialog (Commissioned) .................................................................................... 36

Figure 45: Image Flash Warning ................................................................................................................. 36

Figure 46: Flash Update Open File Dialog .................................................................................................. 37

Figure 47: Flash Progress Dialog .............................................................................................................. 37

Figure 48: Flash Completion Dialog ............................................................................................................ 38

Figure 49: VIM Detail Display (IP Addressing)............................................................................................ 39

_____________________________________________________________________________________________________


68


Figure 50: VIM Context Menu (Grayed Items) ............................................................................................ 39

Figure 51: Physical Properties Dialog ......................................................................................................... 40

Figure 52: Physical Properties Dialog (Selected Used Address) ................................................................ 40

Figure 53: VIM Properties (Specified NIC) .................................................................................................. 41

Figure 54: Alternative NIC Selection Dialog ................................................................................................ 41

Figure 55: VIM Context Menu (Export FHX) ............................................................................................... 42

Figure 56: DeltaV Explorer Import FHX Context Menu ............................................................................... 43

Figure 57: DeltaV Card Properties Dialog ................................................................................................... 44

Figure 58: DeltaV Port Properties Dialog (General Tab) ............................................................................ 45

Figure 59: DeltaV Port Properties Dialog (Advanced Tab) ......................................................................... 45

Figure 60 DeltaV Port Properties Dialog (Communications Tab) ............................................................... 46

Figure 61: DeltaV Device Properties Dialog ............................................................................................... 46

Figure 62: DeltaV Dataset Properties Dialog (General Tab) ...................................................................... 47

Figure 63: DeltaV Dataset Properties Dialog (DeltaV Tab) ........................................................................ 48

Figure 64: DeltaV Dataset Properties Dialog (PLC Tab) ............................................................................ 48

Figure 65: DeltaV Dataset Properties Dialog (Special Data Tab) ............................................................... 49

Figure 66: DeltaV Time Sync Function Block Code .................................................................................... 51

Figure 67: VIM Context Menu (Export TPU CSV File) ................................................................................ 55

Figure 68: TPU / DeltaV cross reference in Excel ...................................................................................... 56

Figure 70: VIMNet Diagnostics VIM Context Menu (Enable Communications) .......................................... 57

Figure 71: VIMNet Diagnostics VIM Detail Display ..................................................................................... 58

Figure 72: VIMNet Diagnostics VIM Context Menu (Reset Statistics) ........................................................ 60

Figure 73: VIMNet Diagnostics Port Detail Display .................................................................................... 60

Figure 74: VIMNet Diagnostics TPU Device Detail Display ........................................................................ 61

Figure 75: VIMNet Diagnostics TPU Device Context Menu ....................................................................... 63

Figure 76: VIMNet Diagnostics Dataset Detail Display ............................................................................... 64

Figure 77: VIMNet Diagnostics File Menu .................................................................................................. 65

Figure 78: VIMNet Diagnostics Settings Dialog .......................................................................................... 65

8. Tables

1-1 Document sections .................................................................................................................................. 3

1-2 FMC Subsea TCP Driver System Specifications .................................................................................... 4

2-1 DO Point Registers ................................................................................................................................. 8

2-2 DI Point Registers ................................................................................................................................... 8

2-3 AO Point Registers ................................................................................................................................. 8

2-4 AI Point Registers ................................................................................................................................... 9

2-5 Global Configuration Dataset Data ......................................................................................................... 9

4-1 PLC Data Type Values, Registers, Start Addresses, and Sizes .......................................................... 49

4-2 FMC Dataset Special Word 1 (Parameter Type) .................................................................................. 49

4-3 Special Word 3 format .......................................................................................................................... 50

4-4 Output Status Values ............................................................................................................................ 53

4-5 Output (SP) Register read-back Examples........................................................................................... 53

5-1 VIM Diagnostics .................................................................................................................................... 59

5-2 Device Diagnostic Values ..................................................................................................................... 63

5-3 Dataset Level Diagnostics .................................................................................................................... 64

6-1 Verifying Hardware and Software Version Numbers ............................................................................ 66

6-2 LED Indicators ...................................................................................................................................... 67

6-3 Simplex VIM LED State Specifications ................................................................................................. 67

_____________________________________________________________________________________________________


69


9. Technical Support

For technical support or to report a defect, please give MYNAH Technologies a call at (636) 728-2000. If a defect is discovered, please document it in as much detail as possible and then fax your report to us at

(636) 728-2001.

You can also send us your questions via e-mail. Our address is: [email protected]

_____________________________________________________________________________________________________


70

Users Manual Ethernet IP v3.3.28

FMC Subsea Driver for

DeltaV Virtual I/O Module

For both Simplex and Redundant FMC TPU TCP Versions 1.0.x

IOD-4105

USER MANUAL

October 25, 2011

Disclaimers

1. Introduction

1.1. Scope

1.2. Document Format

1.3. System Specifications

2. Theory of Operation

2.1. DeltaV Native I/O

2.2. TPU Devices

2.3. DeltaV Presentation of I/O and status data from the VIM

2.3.1. DO I/O Points

2.3.2. DI I/O Points

2.3.3. AO I/O Points

2.3.4. AI I/O Points

2.4. Presentation of Global Data

3. VIMNet Explorer

3.1. Installation of Simplex Virtual I/O Module (VIM) Hardware

3.2. Installation of 2 Simplex Virtual I/O Modules for redundant

TPU’s

3.3. Installation of Software

3.3.1. MSI Selection

3.3.2. Launch VimNet

3.3.3. Initial IP Addresses

3.3.4. VimNet Global Properties

3.4. Configuring VIM, Importing TPU and Tags

3.4.1. Adding a DeltaV Controller

3.4.2. VIM Configuration

3.4.3. Commission the VIM

3.4.4. TPU Configuration File

3.4.5. Import TPU configuration into VIM

3.4.6. Assign TPU to DeltaV Device

3.4.7. Configure TPU Tags

3.4.8. VIM Detail Display with imported

TPU’s

3.4.9. TPU Device Level Tag Display

3.4.10. Tag Group Level Display

3.4.11. Data Set Level Display

3.5. Uploading a VIM Configuration

3.6. Saving the VIM Configuration

3.7. Flash Upgrade of the VIM Firmware

3.8. Configuring VIMs on Multiple Subnets

4. Configuring DeltaV

4.1. Configuring DeltaV with FHX import file

4.2. Manually Configuring DeltaV

4.2.1. Configure Serial Card and Ports

Make sure that you Enable the port to be used by clicking on the Enabled box in the. Unused ports

should be left disabled.

4.2.2. Configure Devices

4.2.3. Configure Datasets

4.3. Configuring a Time Sync Module

If DeltaV is not configured to write the time sync value when prompted, the communications to the field will be suspended prior

to initialization. Proper configuration of this module is essential.

4.4. Configuring DeltaV writes to TPU

4.5. TPU Tag definitions in DeltaV

5. VIMNet Diagnostics

5.1. VIM Level Diagnostics

5.2. Port Level Diagnostics

5.3. Device Level Diagnostics

5.4. Dataset Level Diagnostics

5.5. Diagnostics Impact on Vim and network communications

6. Operational Check

6.1. Scope

6.2. Verify Hardware and Software Version Number

6.3. Verify Configuring

6.4. Verify I/O Communication with Control Studio

6.5. Using DeltaV Diagnostics

6.6. LED Indication

7. Figures

8. Tables

9. Technical Support

Related manuals

Emerson

Mynah PLC-5

Rosemount