Knowledge Base /
Release Notes
Programmable Serial Interface Card Driver for Canberra Alpha Sentry ASM 1000 User Manual
By Noelle Weymer
Product: DeltaV Virtual IO Module - VIM2

1. INTRODUCTION

1.1 Scope

This document is the User Manual for the Canberra Alpha Sentry ASM 1000 serial communication driver firmware for the Emerson Process Management (EPM) DeltaV Control System.

It provides information required to install, configure, and maintain the driver firmware on the DeltaV Programmable Serial Interface Card (PSIC). The reader should be familiar with EPM’s DeltaV PSIC and connected devices using the ASM 1000 protocol.

The section Document Format briefly describes the contents of each section of this manual. System Specifications outlines hardware and software requirements for the Driver firmware.

1.2 Document Format

This document is organized as follows:

Introduction

Describes the scope purpose of this document.
Theory of Operation Provides a general functional overview of the ASM 1000 Driver.
Flashing Firmware Desribes flashing procedures for the ASM 1000 Driver firmware on to the DeltaV PSIC.
Configuration Information

Describes procedures and guidelines for configuring the DeltaV PSIC.

Operational Check Provides tips and assistance to ensure PSIC is
properly setup and configured.
DeltaV-Field Device Electrical Interface Describes the electrical interface between DeltaV
and the external Device. Also describes the cable pin
assignments for RS-232 and RS-422/485
communications.
Techincal Support Describes who to call if you need assistance.

1.3 System Specifications

The following table lists the minimum system requirements for the Canberra Alpha Sentry ASM 1000 Driver:

Table 1: System Specifications

Firmware

Driver Firmware v1.55 or later

Protocol Compatibility

Communcations with the external devices are based on the following document:

Alpha Sentry CAM System -- User Manual, V3.0. Document number 9231204G

Software Requirements

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

Serial Interface Port License (VE4102) if required.

Minimum DeltaV Hardware Requirements

DeltaV Series 2 Serial Module, Hardware Rev1.1r or later.

DeltaV M3, M5, M5+, MD, MD Plus or MX Controller, Power Supply and 8 wide controller carrier.

2. THEORY OF OPERATION

DeltaV comprises an I/O sub-system, in which the PSIC is one type of card. The purpose of the PSIC is to seriallyintegrate third-party devices, allowing data to be read into and written out from DeltaV. The PSIC has 2 communication ports that can be configured as RS-232, RS-485 (Half Duplex), or RS-422 (Full Duplex). Various communications parameters, such as baud rate, are configurable. Under each PSIC port, users can configure devices with unique addresses. Under each device, one or more datasets can be assigned. There are a maximum of 16 datasets available under each port.

In this PSIC driver, one ASM 1000 device per port will be supported. Communication between the PSIC and the ASM 1000 will optionally be RS485 half duplex if Model ASM01 is used, or RS232 if Model ASM02 is used. A maximum of 8 Continuous Air Monitor (CAM) head units will be supported under each ASM 1000. The system architecture will be as follows:

The driver works in Master mode only.

The PSIC driver functionality comprises a Continuous scan and User Commands.

On configuration download from the DeltaV Controller, the driver enters its continuous scan mode and starts scanning the status and CAM calculated data. This data is stored in dataset registers as changes are detected. Simultaneously, user commands from DeltaV to the ASM 1000 and CAMS are received and executed.

Continuous Scan- This is the default execution mode. Dataset 1, Special Data 1 is the scan enable mask value in the range 0-255. Each bit represents a CAM, with bit 0 controlling the scan for CAM 1 and bit 8 controlling CAM 8. The Special Data 1 mask value is transferred into Dataset 1, R4, before it is used. In this way, the user can dynamically modify the mask bits to enable/disable scan of individual CAM’s.

The driver uses ASM Commands 0x10 and 0x3A to read the ASM 1000 status bits. The returned data values are stored in Dataset 4 registers R1-R6.

For all CAMs with enabled scans, the driver uses ASM Command 0x11 to read the CAM status data. The returned values are stored in Dataset 4, registers R21-R100, and Dataset 5 registers R1-R80.

Dataset 4, register R4 is the bit mask indicating runtime sensor data available for each CAM. On first pass after download, the data availability flag is ignored and a CAM read is performed using ASM Commands 0x18, 0x3B and 0x19. Thereafter, each CAM is scanned only of the data availability bit is asserted by the ASM. The returned CAM data is stored in Datasets 6-13 as described in Table 8.

User Commands- Read/Write of Alarm, Calibration, Communication, and other Setup parameters is not a part of the continuous scan. Instead, a manual, user command mechanism is available in the driver so users can perform these functions on demand.

Logic in a DeltaV Control Module is used to initiate Read/Write commands. Dataset 1, registers R1, R2 and R3 are designated for commands. When reading data, the resulting response values are stored in Dataset 1, registers R30-R50, depending on the executed command. When writing data to the ASM 1000 or the CAM, Dataset 1, registers R10-R29 contain the parameter data. User Command details are discussed in Section 4.0.

3.FLASHING THE FIRMWARE

The driver software distribution contains 8 files. These files must be copied to the DeltaV directory on your ProPlus Workstation. The path is:

\DeltaV\ctl\ProgSerial\IOD-1195 ASM1000

Note that you will have to create this subdirectory. The following shows a completed copy operation:

After copy completion, you are ready to program (or upgrade) the Programmable Serial Card with the supplied custom driver software. The steps are as follows:

  1. Click on the Start button and select DeltaV-> Installation-> Controller Upgrade Utility as shown below, and the following dialog will appear:



  2. Click on the Upgrade I/O Modules radio button, and then click Next





  3. The above dialog will appear, listing all the available Controllers in your network. From this dialog, select the appropriate Controller and then Click Next.

  4. The following dialog will appear, listing all the I/O modules in your selected Controller. The shown list of I/O modules is an example only. Your list will be different.

    Note: The first time a standard Serial card is upgraded to the ASM 1000 Driver, the dialog will be as shown below (card 8). When upgrading an exisiting Programmable Serial Card, skip Steps 5 and 6, and go to Step 7.



  5. Click the Browse button and select the DeltaV path as shown below and click OK. Note that the disk drive could be C or D.



  6. Select the I/O module again as shown below and then click Next. Go to Step 9.



  7. If you are upgrading an existing Programmable Serial Card, the dialog will be as shown below. From this dialog, select the Programmable Serial Card I/O Module in the list.



    For example, we will select I/O Module 8. This will give you a dialog, from which you will select the file path to where the driver software is located. This path will be:
    DeltaV\ctl\ProgSerial\IOD-1195 ASM1000 Once you are in the specified directory, you will need to select the following file: ASM1000.S2F This is shown in the following dialog.



  8. After selecting the .S2F file, Click on Open. This dialog will close and you will be back to the following:



  9. In this dialog, Click Next again. You will get the following dialog, confirming the Controller and I/O Module to program.



  10. Click Next and the I/O Module upgrade process will begin. After completion, you will receive the following dialog, indicating success.



  11. This completes the I/O Module upgrade process.

4.CONFIGURATION INFORMATION

As a fixed configuration of thirteen (13) datasets is used. The device and dataset architecture will be as follows:

4.1 Port Configuration

First, enable the port. Then click on the Advanced Tab and select Master. Next, click on the Communications Tab and specify the Port type. Configure the parameters to match the ASM 1000 J103 port. The J103 port will be configured for RS232 (option ASM02) or RS485/Half Duplex (option ASM01) depending on the purchased option.

4.2 Device Configuration

Specify a device corresponding to the ASM 1000. The device address is used only if the ASM 1000 is connected via RS485.In this case, the ASM 1000 and Device address must match.The device address is in the range 1-255.

For additional information, please refer to the Alpha Sentry CAM system User’s Manual, Host Computer Interface, ASM 1000 Communications Setup, p144.

4.3 Dataset Configuration

A fixed architecture, comprising 13 datasets, is employed for communications with the ASM 1000. A summary of the required datasets is as follows:

Table 1 – Dataset Summary

Dataset Number Description
1 Command and control
2 String Data for CAM version and setup
3 String Data for CAM setup
4 ASM 1000 status and CAM 1-4 status
5 CAM 5-8 status
6 CAM 1 dynamic sensor data
7 CAM 2 dynamic sensor data
8 CAM 3 dynamic sensor data
9 CAM 4 dynamic sensor data
10 CAM 5 dynamic sensor data
11 CAM 6 dynamic sensor data
12 CAM 7 dynamic sensor data
13 CAM 8 dynamic sensor data
14-16 Not used


Dataset details are as follows:

Table 2- Dataset 1- Command and Control

Data Direction Output
Output Readback Yes
DeltaV Datatype Floating Point with Status
Device Data Type 1
Data Start Address 0
Number of Values 50
Special Data 1 CAM scan bit mask with one bit for each CAM. Valid values are 0-255. 0 means no CAMs and 255 means all 8 CAMS are configured.
Special Data 2 0
Special Data 3 0
Special Data 4 0
Special Data 5 0
R1 Command # - see Section 4.4 below
R2 Command execute trigger
R3 Command Status
R4 CAM scan control- same value as Special data 1. User can dynamically change this value when online to control the scan.
R5-R9 Reserved
R10-R29 Output parameters
R30- R50 Input data from ASM 1000 and CAMs

Table 3- Dataset 2- String Data 1

Data Direction Input
Output Readback N/A
DeltaV Data Type String with Status
Device Data Type 2
Data Start Address 0
Number of Values 100
Special Data 1 0
Special Data 2 0
Special Data 3 0
Special Data 4 0
Special Data 5

0

R1

Command 21- Verison, Date/Time

The version date/time are read back from the ASM 1000. The data read back is stored in the following format:

Verision (R1:1-20): ASM V3.06A DD-MM-YY
Date/Time: (R1:22-39): DD-MM-YY HH:MM:SS

Command 22- CAM setup data

The CAM setup data format is as follows:

Eff Calibration Date (R1:1-8): DD/MM/YY
Eff Calibration Time (R11:10-17): HH:MM:SS
Air flow Calibration Date (R1:19-26): DD/MM/YY
Air flow Calibration Time (R1:28-35): HH:MM:SS

Table 4- Dataset 3- String Data 2:

Data Direction

Input

Output Readback

N/A

DeltaV Data Type

String with Status

Device Data Type

3

Data Start Address

0

Number of Values

100

Special Data 1

0

Special Data 2

0

Special Data 3

0

Special Data 4

0

Special Data 5

0

R1

Command 22- Addiitional CAM setup data

The CAM set up data format is as follows:

Id<space>S/N<space>version
Id has a maximum length of 39 characters
S/N has a maximum length of 12 characters
Version has a maximum lenght of 12 characters/

Table 5- Dataset 4- Status Data 1

Data Direction Input
Output Readback N/A
Delta V Data Type UINT16 with Status
Device Data Type 4
Data Start Address 0
Number of Values 100
Special Data 1 0
Special Data 2 0
Special Data 3 0
Special Data 4 0
Special Data 5 0

Table 5a- Dataset 4- ASM 1000 Status Data

R1-R20

ASM 1000 Status Data
One bit for each CAM
R1 Online Status- Bit mask value 0-255. Bit =1 implies online and counting; Bit=0 implies any other state.
R2 Radiation Alarm- Bit mask value 0-255. Bit=0 implies no radiation alarm.
R3 Trouble Alarm- Bit mask value 0-255. Bit=0-255. Bit=0 implies no trouble alarm
R4 Data Available- Bit mask value 0-255. Bit 1= implies data available.
R5 Maintenance- Bit mask value 0-255. Bit 1= implies CAM in maintenance state
R6-R20 Reserved.

Table 5b- Dataset 4- CAM 1-4 Status Data (see Table 7)

R21-R40

CAM 1 Status Data

R21

CAM State bit mask – value 0-65535

R22

Alarm bit mask – value 0-65535; Bit=0 implies no alarm

R23

Fault – value less than 0x8000 implies ASM fault. Otherwise bit mask value of CAM fault

R24-R40

Reserved.

R41-R60

CAM 2 Status Data

R41

CAM State bit mask – value 0-65535

R42

Alarm bit mask – value 0-65535; Bit=0 implies no alarm

R43

Fault – value less than 0x8000 implies ASM fault. Otherwise bit mask value of CAM fault

R44-R60

Reserved.

R61-R80

CAM 3 Status Data

R61

CAM State bit mask – value 0-65535

R62

Alarm bit mask – value 0-65535; Bit=0 implies no alarm

R63

Fault – value less than 0x8000 implies ASM fault. Otherwise bit mask value of CAM fault

R64-R80

Reserved.

R81-R100

CAM 4 Status data

R81

CAM State bit mask value
0-65535

R82

Alarm bit mask value 0-65535; Bit=0 implies no alarm

R83

Fault – value less than 0x8000 implies ASM fault. Otherwise bit mask value of CAM fault

R84-R100

Reserved.

Table 6- Dataset 5

Data Direction Input
Output Readback N/A
DeltaV Data Type UINT 16 with Status
Device Data Type 5
Data Start Address 0
Number of Values 100
Special Data 1 0
Special Data 2 0
Special Data 3 0
Special Data 4 0
Special Data 5 0

Table 6a- Dataset 5- CAM 5-8 Status Data (See Table 7)

R1-R20

CAM 5 Status Data

R1

CAM State bit mask – value 0-65535

R2

Alarm bit mask – value 0-65535; Bit=0 implies no alarm

R3

Fault – value less than 0x8000 implies ASM fault. Otherwise bit mask value of CAM fault

R4-R20

Reserved.

R21-R40

CAM 6 Status Data

R21

CAM State bit mask – value 0-65535

R22

Alarm bit mask – value 0-65535; Bit=0 implies no alarm

R23

Fault – value less than 0x8000 implies ASM fault. Otherwise bit mask value of CAM fault

R24-R40

Reserved.

R41-R60

CAM 7 Status Data

R41

CAM State bit mask – value 0-65535

R42

Alarm bit mask – value 0-65535; Bit=0 implies no alarm

R43

Fault – value less than 0x8000 implies ASM fault. Otherwise bit mask value of CAM fault

R44-R60

Reserved.

R61-R80

CAM 8 Status data

R61

CAM State bit mask value 0-65535

R62

Alarm bit mask value 0-65535; Bit=0 implies no alarm

R63

Fault – value less than 0x8000 implies ASM fault. Otherwise bit mask value of CAM fault

R64-R80

Reserved.

Table 7- CAM Status Data Details

CAM State Data

This is a bit mask – value 0-65535

Bit 0: 0-auto; 1-manual

Bit 1: x

Bit 2: 1-primed

Bit 3: x

Bit 4: 1-maintenance

Bit 5: x

Bit 6: 1-linearizing

Bit 7: 1-initializing

Bit 8: x

Bit 9: x

Bit 10: x

Bit 11: 1-dropped

Bit 12: 1-not counting

Bit 13: 1-not defined

Bit 14: x

Bit 15: x

x means not used

Alarm Data

This is a bit mask – value 0-65535

Bit 0: acute release

Bit 1: chronic release

Bit 2: low air flow

Bit 3: high air flow

Bit 4: sampling head pwr fail

Bit 5: detector pwr fail

Bit 6: door open

Bit 7: no data collect

Bit 8: no spectral data

Bit 9: sampling head offline

Bit 10: high background

Bit 11: energy cal. Shift exceeded

Bit 12: peak shift exceeded

Bit 13: not used

Bit 14: instrument fault

Bit 15: not used

Fault Data

Value less than 0x8000 implies ASM fault

0001: invalid start channel for linearization

0002: linearization compensation limit exceeded

0003: error building linearization table

0004: insufficient linearization data

0005: hard CAM initialization

0006: invalid CAM efficiency

0007: invalid filter change date

0008: invalid CAM flow table

0009: invalid energy slope value

CAM Fault data

This is a bit mask value 0-65535

Bit 0: flow out of limit

Bit 1: +12V out of limit

Bit 2: 24V out of limit

Bit 3: 10V out of limit

Bit 4: 5V out of limit

Bit 5: -12V out of limit

Bit 6: PROM checksum error

Bit 7: RAM test error

Bit 8: watchdog timer not programmed

Bit 9: EEPROM error

Bit 10: command exec error

Bit 11: amplified error

Bit 12: not used

Bit 13: not used

Bit 14: not used

Bit 15: CAM fault

Table 8 - Dataset 6-13

Data Direction Input
Output Readback N/A
DeltaV Data Type Floating Point with Status
Device Data Type 6-13
Data Start Address 0
Number of Values 50
Special Data 1 0
Special Data 2 0
Special Data 3 0
Special Data 4 0
Special Data 5 0

R1-R13

CAM x data since last count cycle
Where x =1-8

R1

Air Volume

Liters

R2

Air Flow

L/min

R3

CPM

R4

CPM Error

%

R5

Uncorrected CPM

R6

Uncorrected CPM Error

%

R7

DAC-Hrs

R8

Concentration

DPM/m3

R9

Concentration Error

%

R10

Critical Level

R11

Filter Time

Hrs

R12

Slope

MeV/Channel

R13

Intercept

MeV

R21-R33

CAM x data since last Alarm count cycle
Where x =1-8

R21

Air Volume

Liters

R22

Air Flow

L/min

R23

CPM

R24

CPM Error

%

R25

Uncorrected CPM

R26

Uncorrected CPM Error

%

R27

DAC-Hrs

R28

Concentration

DPM/m3

R29

Concentration Error

%

R30

Critical Level

R31

Filter Time

Hrs

R32

Slope

MeV/Channel

R33

Intercept

MeV

4.4 Read/Write Command Procedure

The procedure to send commands to the ASM 1000 is as follows. User commands are detailed in below. The first three registers in Dataset 1 are used to send user commands. R1 is the command number; R2 is the command execute trigger; and R3 contains the error code if there is an error or 0 if no error.

1. Write command number to Dataset 1, register R1. Any parameters required for the command are also written into their respective registers. See Section 4.5 for command parameter specification details.

2. Write a 1 to Dataset 1, register R2. This indicates that a new command is ready to be sent.

3. R2 transition to 1 triggers the command mechanism in the driver. The driver will write the command number +100 into R1, and a 0 to R2 and R3, and send the command to the ASM 1000.

4. Upon receiving a good response, the driver will write a 0 to R3.

5. If the response received has an error code, it will be parsed and written to R3. See Table 9.

6. The driver will then update the DeltaV Controller and return to wait for the next user command.

Table 9- Command/Response Error Codes

Error Code

Description
0 No Error
1 Invalid Command (response from ASM 1000)
2 Checksum Error in command
3 Specified parameter is outside of expected range
4 Head is unavailable
5 Invalid parameter specified
6 Specified command number is invalid

4.5 User Commands

The following subset of the available ASM 1000 commands is implemented in the driver.

Table 10- Supported Commands

Driver

Command

ASM Command Number

Description

1

0x20

Read ASM Setup Parameters

2

0x21

Read ASM System Parameters

3

0x23

Write ASM Setup Parameters

4

0x24

Write ASM System Parameters

5

0x22

Read CAM Setup Parameters

6

0x25

Write CAM Setup Parameters

7

0x28

Stop Alarm

8

0xD3,0x29

Read Acute Alarm

9

0xC3,0x29

Write Acute Alarm

10

0xD3,0x2A

Read Number of Retries Parameter

11

0xD3,0x2B

Read Retry-Wait Parameter

12

0xD3, 0x2C

Read Post Command Delay Parameter

13

0xD3,0x2D

Read Pre Command Delay Parameter

14

0xC3,0x2A

Write Number of Retries Parameter

15

0xC3,0x2B

Write Retry-Wait Parameter

16

0xC3,0x2C

Write Post Command Delay Parameter

17

0xC3,0x2D

Write Pre Command Delay Parameter

18

0xD3,0x2E

Read Calibration Frequency Parameter

19

0xD3,0x2F

Read Calibration Warn Ahead Parameter

20

0xD3,0x30

Read Activate Trouble Light Parameter

21

0xC3,0x2E

Write Calibration Frequency Parameter

22

0xC3,0x2F

Write Calibration Warn Ahead Parameter

23

0xC3,0x30

Write Activate Trouble Light Parameter

Table 11- ASM 1000 Commands

Command Number

Description

1

Read ASM Setup Parameters (ASM Cmd 0x20)

This command requires 1 parameter: CAM number. Specify the CAM in Dataset 1 R10.

The response contains 9 values which will be stored in Dataset 1, registers 30-38, as follows:

R30 – Low air flow alarm limit (L/min)

R31 – high air flow alarm limit (L/min)

R32 – count cycle time (minutes)

R33 – DAC hr alarm limit

R34 – DAC factor (uCi/cm3)

R35 – upper energy limit (MeV)

R36 – analysis window (MeV)

R37 – confidence level (sigma)

R38 – Acute alarm minimum count limit

2

Read ASM System Parameters (ASM Cmd 0x21)

This command does not require any parameters.

The response contains 3 string values which will be stored in Dataset 2.

3

Write ASM Setup Parameters (ASM Cmd 0x23)

This command requires 10 parameters, specified

in Dataset 1, registers 10-19, as follows:

R10 – CAM number (1-8)

R11 – Low air flow alarm limit

(14.16 <= flow < 282.92 L/min)

R12 – high air flow alarm limit

(14.16 <= flow < 282.92 L/min)

R13 – count cycle time

(31 minutes; consult Canberra for options)

R14 – DAC hr alarm limit

(0.1 <= limit < 100)

R15 – DAC factor

(1.0E-16 < factor < 10.0E-8 uCi/cm3)

R16 – upper energy limit

(0.0 < limit < 10 MeV)

R17 – analysis window

(0.0 < value < 10 MeV)

R18 – confidence level (sigma)

(1.0E-2 < value < 0)

R19 – Acute alarm minimum count limit

(0.0 <= limit < 255)

4

Write ASM System Parameters (ASM Cmd 0x24)

This command requires two parameters, specified in dataset 1, register 10 and 11.

R10 – system date (format DDMMYY)

R11 – system time (format HHMMSS)

Table 12- CAM Commands

Command Number

Description

5

Read CAM Setup Parameters (ASM Cmd 0x22)

This command requires 1 parameter: CAM number. Specify the CAM in Dataset 1 R10.

The response contains 9 values which will be stored in Dataset 1, 2 and 3, as follows:

DS1, R30 – Number of no count alarm limits.

DS1, R31 – detector calibrated efficiency (%)

DS2 – efficiency and air flow calibration date/time

DS3 – CAM ID, serial number, version

6

Write CAM Setup Parameters (ASM Cmd 0x25)

This command requires 2 parameters, specified in dataset 1, registers R10 and 11.

R10 – CAM number (1-8)

R11 – Number of no counts alarm limit (1-255)

Table 13- Alarm Commands

Command Number

Description

7

Stop Alarm (ASM Cmd 0x28)

This command does not require any parameters

8

Read Acute Alarm (ASM Cmd 0xD3,0x29)

This command requires 1 parameter, specified in dataset 1, registers R10.

R10 – CAM number (1-8)

The response contains 1 value which will be stored in Dataset 1:

R30 – Value (0-255)

9

Write Acute Alarm (ASM Cmd 0xC3,0x29)

This command requires 2 parameters, specified in dataset 1, registers R10 and R11.

R10 – CAM number (1-8)

R11 – Alarm value (0-255)

Table 14- Communication Commands

Command Number

Description

10

Read Number of Retries Parameter (Communication Cmd 0xD3, 0x2A)

This command requires 1 parameter, specified in dataset 1, register R10.

R10 – CAM number (1-8)

The response contains 1 value which will be stored in Dataset 1:

R30 – Value (0-255)

11

Read Retry-Wait Parameter

(Communication Cmd 0xD3, 0x2B)

This command requires 1 parameter, specified in dataset 1, register R10.

R10 – CAM number (1-8)

The response contains 1 value which will be stored in Dataset 1:

R30 – Value (0-65535)

12

Read Post-Command Delay Parameter

(Communication Cmd 0xD3, 0x2C)

This command requires 1 parameter, specified in dataset 1, register R10.

R10 – CAM number (1-8)

The response contains 1 value which will be stored in Dataset 1:

R30 – Value (0-32767)

13

Read Pre-Command Delay Parameter

(Communication Cmd 0xD3, 0x2D)

This command requires 1 parameter, specified in dataset 1, register R10.

R10 – CAM number (1-8)

The response contains 1 value which will be stored in Dataset 1:

R30 – Value (0-32767)

14

Write Number of Retries Parameter (Communication Cmd 0xC3, 0x2A)

This command requires 2 parameters, specified in dataset 1, register R10 and R11.

R10 – CAM number (1-8)

R11 – value (0-255

15

Write Retry-Wait Parameter

(Communication Cmd 0xC3, 0x2B)

This command requires 2 parameters, specified in dataset 1, register R10 and R11.

R10 – CAM number (1-8)

R11 – value (0-65535

16

Write Post-Command Delay Parameter

(Communication Cmd 0xC3, 0x2C)

This command requires 2 parameters, specified in dataset 1, register R10 and R11.

R10 – CAM number (1-8)

R11 – value (0-32767

17

Write Pre-Command Delay Parameter

(Communication Cmd 0xC3, 0x2D)

This command requires 2 parameters, specified in dataset 1, register R10 and R11.

R10 – CAM number (1-8)

R11 – value (0-32767)

Table 15- Calibration Commands

Command Number

Description

18

Read Calibration Frequency Parameter

(Communication Cmd 0xD3, 0x2E)

This command requires 1 parameter, specified in dataset 1, register R10.

R10 – CAM number (1-8)

The response contains 1 value which will be stored in Dataset 1:

R30 – Value (0-9999)

19

Read Calibration Warn Ahead Parameter

(Communication Cmd 0xD3, 0x2F)

This command requires 1 parameter, specified in dataset 1, register R10.

R10 – CAM number (1-8)

The response contains 1 value which will be stored in Dataset 1:

R30 – Value (0-255)

20

Read Activate Trouble Light Parameter

(Communication Cmd 0xD3, 0x30)

This command requires 1 parameter, specified in dataset 1, register R10.

R10 – CAM number (1-8)

The response contains 1 value which will be stored in Dataset 1:

R30 – Value (0-1)

21

Write Calibration Frequency Parameter

(Communication Cmd 0xC3, 0x2E)

This command requires 2 parameters, specified in dataset 1, register R10.

R10 – CAM number (1-8)

R11 – Value (0-9999)

22

Write Calibration Warn Ahead Parameter

(Communication Cmd 0xC3, 0x2F)

This command requires 2 parameters, specified in dataset 1, register R10.

R10 – CAM number (1-8)

R11 – Value (0-255)

23

Write Activate Trouble Light Parameter

(Communication Cmd 0xC3, 0x30)

This command requires 2 parameters, specified in dataset 1, register R10.

R10 – CAM number (1-8)

R11 – Value (0-1)

5.OPERATIONAL CHECK

5.1 Scope

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

5.2 Verify Hardware and Software Version Number

The user can verify that the driver has been installed using the DeltaV diagnostics tool. The Diagnostic tool will show the Hardware Revision No. (HwRev) and the Software Revision No. (SwRev).

To begin the DeltaV Diagnostic tool, select Start -> DeltaV-> Operator-> Diagnostics. In the Diagnostices 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 Hardware Revision 1.1 (or later)

SwRev Software Revision P1.55 (or later)

5.3 Verify Configuration

  • Verify port configuration: The serial port must be enabled. User needs to make sure communication settings such as baud rate, parity and number of data bits match the field device settings.
  • Verify dataset configuration: The datasets configured must be shown above.

5.4 Verify I/O Communication With Control Studio

User can create I/O modules in the control studio to verify correct values are read from the PSIC. For AI and DI data, the values should be changed in the field device and verfied that the new data is correctly reported in DeltaV. Similiarly, verify that the AO and DO data is being written correctly from DeltaV to the field device.

5.5 Using Diagnostics

  • Verify PSIC communication: Select PSIC on Diagnostics and press the right mouse button. Select Display Real- Time Statistics from the drop down menu. If the Progammable Serial Interface Card is funtioning, then the user will see the Valid Responses counter and the Async and/or Sync Transactions counters incrementing. There will not be any error counting up.
  • Verify port statistics: Select the Port on the Programmable Serial Interface Card and press the right mouse button. Then select Display Port Statistics from the drop down menu. Verify that the port communications statistics are 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 menu. Verify that the dataset values are displayed as expected.
  • Verify that there are not errors at the dataset level.

5.6 LED Indication

The Yellow LED for the port shuold be on solid when all communcations on that port are valid. The Yellow LED should be blinking if there is some valid communcations and some communications with errors on that port. The Yellow LED should be OFF if there are no valid communcations on that port.

6. Connecting DeltaV PSIC to the ASM 1000

The electrical interface between DeltaV PSIC and ASM 1000 conforms to the RS-232 and RS-485 standards. If the ASM02 option is used, the electrial interface is RS-485. If the ASM01 option is used, the electrical interface is RS-232. The serial driver supports both options.

The following is the cable pinout.


7. Techincal Support

For technical support or to report a defect, please call MYNAH Technologies at +1.636.728.2000. If a defect is discovered, please document it in as much detail as possible and open a support ticket. For more information about creating a MYNAH My Account please refer to the link below.

http://www.mynah.com/knowledge-base/my-account-mynahcom-features-and-directions


8. Revision History

Revision Number

Checked By

Approved By

Date

Description

1.55

NFW

NFW

Jan, 2012

Internal Release