当前位置：文档库 › Applicom_Interface_Reference_EP-DSX506

Applicom_Interface_Reference_EP-DSX506

Applicom Interface Reference

EP-DSX506

April 2010

Issue Date

7April 2010

Notice

This document contains Honeywell proprietary information. Information

contained herein is to be used solely for the purpose submitted, and no part of this

document or its contents shall be reproduced, published, or disclosed to a third

party without the express permission of Honeywell International Sàrl.

While this information is presented in good faith and believed to be accurate,

Honeywell disclaims the implied warranties of merchantability and fitness for a

purpose and makes no express warranties except as may be stated in its written

agreement with and for its customer.

In no event is Honeywell liable to anyone for any direct, special, or consequential

damages. The information and specifications in this document are subject to

change without notice.

Honeywell trademarks

Experion?, PlantScape?, SafeBrowse?, TotalPlant? and TDC 3000? are U.S.

registered trademarks of Honeywell International Inc.

Honeywell Enterprise Buildings Integrator? is a trademark of Honeywell

International Inc.

Other trademarks

Microsoft and SQL Server are either registered trademarks or trademarks of

Microsoft Corporation in the United States and/or other countries.

Trademarks that appear in this document are used only to the benefit of the

trademark owner, with no intention of trademark infringement.

Support and other contacts

For technical assistance, call your nearest Honeywell office.

https://www.wendangku.net/doc/5119072959.html,

Contents

1Getting started5 Support and documentation for Applicom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2Applicom setup7 Architecture for Applicom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Setting up an Applicom Communication Server card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Cabling and device configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Monitoring field devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3Applicom configuration and addressing11 Defining an Applicom channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Applicom channel Main properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Defining an Applicom controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Applicom controller Main properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Defining an Applicom address for a point parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Entering an address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Address syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Data formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Optimizing scanning performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 4Server tasks for Applicom21 Testing Applicom to field device communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Address restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Troubleshooting point configuration errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Errors when downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Errors when scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

CONTENTS

https://www.wendangku.net/doc/5119072959.html,

1 Getting started

This reference provides the information you need to set up, configure, and test an

Applicom system.

Steps for connecting and configuring an Applicom.

Complete each step before commencing the next step.

Step:Go to:

Set up Applicom card page9

Define channels using Quick Builder page12

Define controllers using Quick Builder page15

Download channel and controller definitions to the server

Test communications page22

Define controller points using Quick Builder page18

1 – GETTING STARTED

Support and documentation for Applicom

For information about supported devices and related documentation, see the

Software Change Notice or the Software Release Bulletin.

https://www.wendangku.net/doc/5119072959.html,

2 Applicom setup

This chapter describes how to set up an Applicom.

The tasks for setting up an Applicom are:

For:Go to:

Supported architecture page8

Setting up an Applicom Communication Server card page9

Set up communications indicator page10

2 – APPLICOM SETUP

Architecture for Applicom

The term Applicom Communication Server card refers to all supported Applicom

Communication Server cards. The cards come in a range of configurations, and

are installed in the server.

The Applicom can handle up to eight Applicom Communication Server cards,

and interacts with the card databases as shown in the following figure.

You need to define each Applicom Communication Server card as a channel, and

each part of the associated databases as a controller.

https://www.wendangku.net/doc/5119072959.html,

SETTING UP AN APPLICOM COMMUNICATION SERVER CARD

Setting up an Applicom Communication Server card

The interface between the server and an Applicom Communication Server card is

achieved by installing the software drivers supplied with the card.

To set up a card:

1Create the “Applicom” folder anywhere on the system.

2Add the Applicom folder to the System Path.

3Install the Applicom software drivers supplied with the card in the Applicom folder.

4Check that applicom.dll is in the Applicom folder.

5Install the card, with a suitable interrupt.

6Set the server’s CMOS in accordance with the selected interrupt.

7Add the Applicom device to Control Panel Devices.

8Run pcinisrv to ensure that the card is initialized by the pcinit service at system startup.

Cabling and device configuration

Cabling from the Applicom Communication Server cards to the field devices is

described in the APPLICOM Communication Server Manual. The manual also

describes the methods by which the data from field devices is stored in the

Applicom databases.

2 – APPLICOM SETUP

https://www.wendangku.net/doc/5119072959.html,

Monitoring field devices

The server only reads data from the Applicom Database, not directly from the field devices attached to the Applicom Communication Server Card. This means that it is possible for the server to remain unaware of a loss of communications with a field device.To overcome this:

1Allocate a word in the Applicom Word Database as a “communications indicator”.

Configure the field device to update this word at a regular interval—less than 60 seconds. (You can do this even if the controller addresses the Bit Table, because the diagnostic address resides in the Applicom Word Database.)You configure the field device using the external utility supplied with the Applicom Communication Server Card (see APPLICOM Communication Server Manual ).

When you configure the Applicom controller in Quick Builder, specify this word in Diagnostic Address . See “Applicom controller Main properties” on page 16.

The Applicom Interface checks this address as part of its diagnostic request every 60 seconds, and compares the current value with the previous value. If the value has not changed after a number of retries, the controller is be deemed to have failed under the standard controller failure algorithm, and all associated point data is set to “bad” status. The Applicom Interface continues to read this address, so that when the value does change—indicating that communications has been restored—the controller can be automatically recovered.

3 Applicom configuration and

addressing

This chapter describes how to configure an Applicom using Quick Builder.

For information about:Go to:

Defining an Applicom channel page12

Defining an Applicom controller page15

Defining an address for a point parameter value page18

Optimizing scanning performance page20

3 – APPLICOM CONFIGURATION AND ADDRESSING

https://www.wendangku.net/doc/5119072959.html,

Defining an Applicom channel

To define a channel:

1Click to display the Add Items dialog.

2Select Channel as the item and Applicom as the type.

Set the property values on the Main tab—see “Applicom channel Main properties” on page 13.

DEFINING AN APPLICOM CHANNEL

Applicom channel Main properties

The Main tab defines the basic properties for an Applicom channel.

Property Description

Name The unique name of the channel. A maximum of 10

alphanumeric characters (no spaces, underscores or

double quotes).

Description (optional) A description of the channel. A maximum of 30

alphanumeric characters, including spaces.

Marginal Alarm Limit The communications alarm limit at which the channel is

declared to be marginal. When this limit is reached, a

high priority alarm is generated. This limit is the channel

barometer, which monitors the total number of requests

and the number of times the controller did not respond

or response was incorrect. The barometer is incremented

by 2 or more, depending on the error and decremented

for each good call.

To calculate an acceptable limit, multiply the square root

of the number of controllers on the channel with the

controllers’ Marginal Alarm Limit (generally, you

specify the same value for all controllers on a particular

channel). For example, if there are 9 controllers, and you

have set the controllers’ Marginal Alarm Limit to 10,

the value would be ÷9x10 (that is, 30).

Fail Alarm Limit The communications alarm limit at which the channel is

declared to have failed. When this barometer limit is

reached, an urgent alarm is generated.

Set this to double the value specified in Marginal

Alarm Limit.

Card Number The card’s ID in the server. A number between 1 and 8.

Connect Timeout The time, in seconds, the server attempts to connect to

the Station before giving up. The default value is 10

seconds.

Read Timeout The time, in seconds, the server attempts to read data

from the Station before giving up. The default value is 2

seconds.

Item Type Shows the type of item specified when this item was

created.

Last Modified Shows the date of the most recent modification to this

channel’s property details.

3 – APPLICOM CONFIGURATION AND ADDRESSING

Property Description

Item Number The unique item number currently assigned to this item.

You can change the item number if you need to match

your current server database configuration. The number

must be between 1 and the maximum number of

channels allowed for your system.

https://www.wendangku.net/doc/5119072959.html,

DEFINING AN APPLICOM CONTROLLER Defining an Applicom controller

To define a controller:

1Click to display the Add Items dialog.

2Select Controller as the item and Applicom as the type.

3Set the property values on the Main tab. See “Applicom controller Main

properties” on page16.

3 – APPLICOM CONFIGURATION AND ADDRESSING

Applicom controller Main properties

The Main tab defines the basic properties for an Applicom controller.

Property Description

Name The unique name of the controller. A maximum of 10

alphanumeric characters (no spaces, underscores or

double quotes).

Description (optional) A description of the controller. A maximum of 30

alphanumeric characters, including spaces.

Channel Name The Applicom channel on which the controller

communicates with the server.

Marginal Alarm Limit The communications alarm marginal limit at which the

controller is declared to be marginal. When this limit is

reached, a high priority alarm is generated. This limit is

the controller barometer, which monitors the total

number of requests and the number of times the

controller did not respond or response was incorrect.

The barometer is incremented by 2 or more, depending

on the error and decremented for each good call.

The default value is 25.

Fail Alarm Limit The communications alarm fail limit at which the

controller is declared to have failed. When this

barometer limit is reached, an urgent alarm is generated.

Set this to double the value specified in Marginal

Alarm Limit.

Controller Type The type of controller:

?Word Table. Addresses the Applicom word

database.

?Bit Table. Address the Applicom bit database.

Only status points can address this controller.

Note: You can only build Analog and Accumulator

points on Word Table controllers.

https://www.wendangku.net/doc/5119072959.html,

DEFINING AN APPLICOM CONTROLLER

Property Description

Offset For a Bit Table controller, the offset is the starting bit

number address in the 32K bit database of the Applicom

Communication Server Card. All bit numbers in the

range 0 to 32767 are valid.

For a Word Table controller, the offset is the starting

word number address in the 32K word database of the

Applicom Communication Server Card. All word

numbers in the range 0 to 32767 are valid.

After defining the offset, the controller can address the

maximum number of either consecutive bits (8192) or

consecutive words (8192) depending on the controller

type. For example, an offset of 10 for a Word Table

controller specifies that the controller can be used to

address words 10 to 8201 in the Applicom word

database.

Diagnostic Address The address in the Applicom word database that is

written to by the field device to indicate that the

communications link is working. See “Monitoring field

devices” on page10.

Item Type Shows the type of item specified when this item was

created.

Last Modified Shows the date of the most recent modification to this

controller’s property details.

Item Number The unique item number currently assigned to this item.

You can change the item number if you need to match

your current server database configuration. The number

must be between 1 and the maximum number of

channels allowed for your system.

3 – APPLICOM CONFIGURATION AND ADDRESSING

https://www.wendangku.net/doc/5119072959.html,

Defining an Applicom address for a point parameter

Entering an address

For PV Source Address , Source Address , and Destination Address , the format for an Applicom controller address is:

ControllerName Address

If you would like help when defining an address, click

next to Address to

display Address Builder. For details, see the help.

Address syntax

The format for the address is:

Address [DataFormat |[BitNumber [MODE]]

Part

Description

ControllerName The name of the Applicom controller.

Address

The address within the controller where the value is stored. For more details, see “Address syntax” on page 18.

Part

Description

Address

The byte to read from the field device. This address is the absolute address in the range 0 to 32767, not an address relative to the controller offset.

DataFormat Applicable to an analog point. See “Data formats” on page 19.

BitNumber

Only applicable to status points defined in the word table. The valid range is 0 (default) to 15, where 0 is the right most bit in the register.

MODE

Only applicable to the MD parameter. Controls the bit width. If you specify MODE, the mode is 3-bit; if you don’t, the mode defaults to 1-bit.

DEFINING AN APPLICOM ADDRESS FOR A POINT PARAMETER

Data formats

The data format is valid only for Analog and Accumulator points. The formats are shown in the following table.

“S” and “U” range format types are scaled by the 0% and 100% of the HOST range values. “C” types are not scaled and the 0% and 100% range values are used for adjusting the height of the display bar only.

Example

The following example is for a 16-bit signed value read from address 2048.

2048 C16

The following example is for a status value (for a status point) starting at bit address 1000. The width is indicated by the input or output width.

1000

The following example is for a 1-bit MD parameter value, starting at bit 2 of word address 2000.

2000 2

The following example is for a 3-bit MD parameter value, starting at bit 0 of word address 2000.

2000 MODE

Data Format Description

Counts

Scaled C1616-bit, signed. This is the default format.-32767 to 32768

No IEEEFP Single-precision floating point. Only applicable to analog points No S16B 16-bit, signed -32767 to 32768 Yes U16B

16-bit, unsigned

0 to 65535Yes

3 – APPLICOM CONFIGURATION AND ADDRESSING

Optimizing scanning performance

An Applicom scan packet can consist of up to 2033 bits (for a Bit Table

controller) and 128 16-bit words (for a Word Table controller). The scan packet

may be located anywhere along the full address range of the controller.

In order to be in a scan packet, within the block, points must reside in the one

controller and have the same scan period. In addition, they must be addressed

within the 2033-bit or 128-word range that defines the block. Blocks may contain

status, accumulator and analog points.

Try to make each packet as close to the maximum size possible. Ensure there are

no small packets being scanned at fast rates.

If more than one parameter references the same address in a controller, only one

scan packet entry is created. If the parameters do not have the same scan rate, the

scan entry will be created for the fastest scan rates for those parameters.

You can verify your scanning strategy by using the List Scan utility, lisscn, to list

the scan packets you have built.

Two types of scan packets are built for the Applicom:

?Hardware Diagnostic. One scan per controller every 60 seconds for

automatic recovery from communications failure with the controller.

?Periodic data acquisition scan. One per scan packet.

https://www.wendangku.net/doc/5119072959.html,