4 Data Array Parameters ................................................................................................................................... 6
5 Configuring the FieldServer as a EST3 Client ................................................................................................... 7
5.1 Client Side Connection Parameters ..................................................................................................................... 7
5.2 Client Side Node Parameters ............................................................................................................................... 8
5.3 Client Side Map Descriptor Parameters .............................................................................................................. 8
5.3.1 FieldServer Related Map Descriptor Parameters .......................................................................................... 8
5.3.2 Driver Related Map Descriptor Parameters .................................................................................................. 9
5.3.3 Map Descriptor Example 1 .......................................................................................................................... 12
5.3.4 Map Descriptor Example 2:......................................................................................................................... 12
5.3.5 Map Descriptor Example 3:......................................................................................................................... 12
Appendix A Useful Features ................................................................................................................................. 13
Appendix A.6. Object Types and Required Parameters ........................................................................................... 18
Appendix A.7. Set Date and Time To Panel ............................................................................................................. 19
Appendix B Troubleshooting ................................................................................................................................ 20
Appendix B.1. Multiple Com Errors ......................................................................................................................... 20
Appendix C Reference .......................................................................................................................................... 21
Appendix C.1. EST3 Data Format: ............................................................................................................................ 21
Appendix C.1.1. Input data format ...................................................................................................................... 21
Appendix C.1.2. Output data format ................................................................................................................... 24
The EST3 External Communications Protocol (ECP) driver allows the FieldServer to transfer data to and from EST
devices over RS-232 or RS-485 (with converter) serial ports using the EST3 ECP protocol. In the EST application the
FieldServer always emulates a Client.
The FieldServer makes use of the following ECP Services:
Read Operations:
Report Service Delta Service
Write Operations:
Command Service
All read points are continually updated using the Report Service; response times are enhanced using Delta Service
broadcasts by the EST3 panel.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Specify which port the device is connected to the FieldServer
P1-P8, R1-R21
Baud
Specify baud rate
9600, 192002
Parity*
Specify parity
None
Data_Bits*
Specify data bits
8
Protocol
Specify protocol to be used by this port
EST3
// Client Side Connections
Connections
Port
, Baud
, Parity
, Data_Bits
, Protocol
P1
, 19200
, None
, 8
, EST3
1
2
5 CONFIGURI NG T H E F I E LDSERVER AS A EST3 CLI E N T
For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The
information that follows describes how to expand upon the factory defaults provided in the configuration files
included with the FieldServer (See “.csv” sample files provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to communicate
with an EST3 Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable
the FieldServer for EST3 communications, the driver independent FieldServer buffers need to be declared in the
“Data Arrays” section, the destination device addresses need to be declared in the “Client Side Nodes” section, and
the data required from the servers needs to be mapped in the “Client Side Map Descriptors” section. Details on
how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default
5.1 Clie nt S ide Connection P arameters
Example
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.
Edwards Recommends 19200-baud minimum in order to prevent buffer overruns in the EST3 panel
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Specify which port the device is connected to the FieldServer
P1-P8, R1-R2
3
Timeout
Specify time allowed between poll and response
≥10 seconds
IC_Timeout
The Ic_Timeout parameter monitors the time between
characters in a response. If the time exceeds the Ic_Timeout,
the response is discarded and is considered a Timeout.
0-0.5s, 0.05s,
recommended 0.5s
EST_MX_Read_Points*
Specify the maximum number of points that can be polled in
single request. Legacy panel firmware (prior to spec version
5.20) supports a maximum of 34, but new firmware supports a
maximum of 15
1-34
EST_StatusTime_Format*
Specify the format to store status time in
EST_StatusTime_DA Data Array
yyyy, mm, dd, hh,
mm, ss
// Client Side Nodes
Nodes
Node_Name
, Node_ID
, Protocol
, Port
, Timeout
, IC_Timeout
, EST_Mx_Read_Points
EST_1
, 1
, EST3
, P1
, 10s
, 0.5s
, 15
Column Title
Function
Legal Values
Map_Descriptor_Name
Name of this Map Descriptor
Up to 32 alphanumeric characters
Data_Array_Name
Name of Data Array where data is to be stored in
the FieldServer
One of the Data Array names from
Section 4.
Data_Array_Offset
Starting location in Data Array
0 to maximum specified in Section
4.
Function
Function of Client Map Descriptor
RDBC, WRBC4, WRBX
3
4
5.2 Clie nt S ide Node Parameters
Example
5.3 Clie nt S ide Map Descriptor P aram eters
5.3.1 FieldServer Related Map D e s c r i pt o r P ar a m eters
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.
WRBC is not recommended, as startup values may be invalid
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Length of Map Descriptor.
Longer map descriptors (where possible)
are better from a performance point of
view, as well as from a memory use point of
view, since each map descriptor comes with
a memory overhead as well as a protocol
handshaking overhead.
Reads: 1 to maximum address of panel
and card. A length of up to 34 is
recommended. Older panels do not
accept odd numbers. Writes: 1
Data Array to store Point Status. See
example in Section 5.3.5
One of the Data Array Names declared
in Section 4
EST_Alarm_DA*
Data Array to store Alarm state5
EST_Trouble_DA*
Data Array to store Trouble state5
EST_Supervisory_DA*
Data Array to store Supervisory state5
EST_Monitor_DA*
Data Array to store Monitor state5
EST_COActive_DA*
Data Array to store CO active state5
EST_Others_DA*
Data Array to store state other than Alarm,
Trouble, Supervisory or Monitor5
EST_Active_DA*
Data Array to store the raw value of the
active bit.
EST_Relay_Conf_DA*
Relay confirmation state. Refer to
Appendix A.5 for more information.
EST_Types_DA*
Data Array to hold Types category. Refer to
Appendix A.6
DA_Bit_Name*
Acknowledge State. See Appendix A.5.4
EST_Report_Type*
Store information from particular Report
-, Point I/O Status, Sensitivity, Date
Time
EST_Store_Type*
This parameter is applicable only to Map
Descriptors where EST_Report_Type is
‘Point I/O Status’.
If this parameter is not defined and/or the
value is other than ‘Status’, the Driver will
store raw 16 Bit data in the Data Array
pointed to by the Data_Array_Name
parameter of the Map Descriptor.
If the value of this parameter is ‘Status’
then the Driver will store the most recent
status of the point. Since the
Data_Array_Name Data Array and the Data
Array under EST_Status_DA will hold the
same data, EST_Status_DA may be omitted.
Refer also to Section 5.3.5
Status
All other values will be ignored and will
not have any affect.
EST_StatusTime_DA*
Data Array to store FieldServer's time when
Point Status changes.
By default or when Node parameter
EST_StatusTime_Format is set to ss, driver
will store FieldServer's Time in seconds
since 1 Jan 1970.
One of the Data Array Names declared
in Section 4
5
Refer to Appendix A.4 and Section 5.3.4
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
If EST_StatusTime_Format is
yyyymmddhhmmss driver will store time as
year, month(1-12), date(1-31) hour(0-23)
minutes(0-59) seconds (0-59) in 6
sequential data array locations.6
6
Timestamp will be recorded only when MD is configured to store Point Status i.e. either EST_Status_DA is used or
EST_Store_Type is set to 'Status'
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
This Map Descriptor will cause the specified EST point to be read every 50 seconds (subject to throughput constraints); the full 16-bit status values received
from regular polls will be stored in Data Array DA_AI_01 at offsets 0 – 19, and the Alarm, Trouble, Supervisory, Monitor or Other status (received by regular
poll, or Delta message) will be stored in Data Arrays TROUBLES and ALARMS, SUPERVISORY, MONITOR, OTHERS also at offsets 0 – 19. Refer also to Appendix C.
5.3.5 Map Descriptor Example 3 :
This Map Descriptor will cause the specified EST point to be read every 50 seconds (subject to throughput constraints). The full 16-bit status values received
from regular polls will be stored in Data Array DA_AI_01 at offsets 0 – 19, and the Classification as Alarm, Trouble, Supervisory, Monitor , Other, Relay
Confirmation, COActive, Pre-Alarm, Disabled or Test status in the Data Array STATUS at offsets 0 – 19. Refer also to Appendix C.1.
The classification values are as follows:
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
The 8 PanelMask parameters combine to form a 64-bit field in which each bit denotes an EST panel in the network.
Commands that use the PanelMasks are executed by each panel for which the corresponding bit is set. The Map
Descriptor need only define non-zero bytes in the PanelMask. Typically this will be EST_Panel_Mask_1 with a
value of 1.
Appendix A.2. Setting up Multiple Parameters
The multiple parameters required by a command must be stored in consecutive locations in the Data Array
specified by the Map Descriptor, starting at the specified Data_Array_Offset. All parameters must be set up before
the EST command is executed. This is done using a Block Write (if supported by the protocol originating the data)
All parameters are set up in a single write operation, and the EST command is triggered with all values in place.
Appendix A.3. Priority:
The write priority has the possible values of Set, Latch, Low, Medium, and High. These are encoded as 00h, 01h,
02h, 03h and 04h respectively.
Appendix A.4. Report and Delta Service:
The EST ECP3 Report and Delta services report point status slightly differently. The FieldServer EST3 driver deals
with these differences as follows:
Appendix A.4.1. Report Service (regular polling):
The full 16-bit point status is stored to the Read Map Descriptor’s Data Array. If optional Data Arrays are
configured, then the point status is also interpreted according to its Alarm, Trouble, Supervisory or Monitor status
and the corresponding Data Array is updated. See Appendix A.5 for detail.
Appendix A.4.2. Delta Service (unsolicited messages):
Delta Service messages do not provide the same 16-bit status value as supplied by the Report Service. For this
reason, ONLY the optional Data Arrays will be updated when a Delta message is received. Delta messages will
therefore only have an effect when optional Data Arrays have been configured. The delta service will be sent out
through ECP automatically. There's no panel setting for this. The EST3 panel always sends a delta frame when
there is a state change. Refer also to Appendix A.5
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Appendix A.4.3. Example Configuration using Delta Mode only
Note: It is recommended that at least one active Map Descriptor is defined to alert the Driver if the connection fails. As many passive Clients as desired can
then be appended.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
When optional parameters (EST_Alarm_DA, EST_Trouble_DA, EST_Supervisory_DA, EST_Monitor_DA, or
EST_COActive_DA) are used, the driver automatically separates the Alarm Trouble, Supervisory, Monitor, CO
Active bit from the incoming EST message and places the bit(s) in these Data Arrays at the same offset as the
incoming message. Other types can be stored in EST_Others_DA Data Array. Only one Data type will be reported
as active at a particular time; i.e. if Alarm is reported Driver will set Alarm bit and reset corresponding bits from
Trouble, Supervisory and Monitor Data Arrays. The Driver does not correlate Other types with Alarm, Trouble,
Supervisory or Monitor types. For different point types the active bit has a different meaning. If the user is
interested in the meaning, the EST_Supervisory_DA Data Array should be configured. If the user is interested in
the raw value of the Active bit, the data array EST_Active_DA should be configured.
Appendix A.5.1. Relay Confirmation State
The driver can store the relay confirmation state of a point in a Data Array under the parameter
EST_Relay_Conf_DA parameter.
0 – Relay state is not confirmed; 1 – Relay state confirmed.
Appendix A.5.2. EST_Types_DA
If it is necessary to override the default Types and Category list (Appendix C.1.1) the EST_Types_DA parameter
should be used.
Example:
To put HEAT type into the “Monitor” category where all other defaults remain the same, preload the data array as
follows:
Preload_Data_Index is the type of device and Preload_Data_Value holds the category for the specified device type.
The legal values for Preload_Data_Value are listed below
Appendix A.5.3. EST_Types_Update
If this parameter is not defined or is “yes”, the driver will update its internal driver list according to the parameters
preloaded under EST_Types_DA. If the parameter is set to “New List”, the driver will use ONLY the parameters
defined under EST_Types_DA and will not reference or update the default list at all. The driver will therefore not
store any data for types that do not have preloaded categories.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
The dirtiness of a device can be stored as a value *10 for System Sensor Devices and as the actual value for other Device Typ es (The panel sends % for other
Device Types)
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Each input device is associated with a 16-bit value. The contents of the 16 bits are used to generate status types as shown in
the table below. Each incoming event is allocated to a status type depending on its device type as shown in the table. It is
possible to override this default status type allocation. Refer to Appendix A.5 for more information.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
TestActive1
Places the device in its primary active state (Alarm, Monitor, Supervisory, SecurityAlarm, etc.
201h
TestTrouble
Places the device in CommonTrouble
301h
TestActive2
Places Security devices capable of tamper, in SecurityTamper.
Places sensors capable of PreAlarm in Prealarm
401h
Appendix C.1.2. Output data format
Each output device is associated with a 16-bit value. This value consists of two byte fields, the command (LSB) and the
attribute (MSB).
These values are provided by the EST panel and are described in the EST3 ECP protocol specification as follows. These values
will be put in the Command field.
The attribute byte must be set for writes to Relay, LED outputs and DeviceTest
For Relays, the attribute values are:
For LED’s, the attribute values are:
For DeviceTest (Signature Devices Only), the attribute values are:
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
The driver lost communications with the panel (due to panel reset or power-cycle or cable
interruption) and is trying to re-establish communications over the communications link or
connection
Gateway Type
ECP Gateway Type I/II/III
Data Rx Char
Data Bytes Received
Data Rx Msg
Data Messages Received
Data Tx Char
Data Bytes Transmitted
Data Tx Msg
Data Messages Transmitted
Conn Rx Char
Total Bytes Received on Connection
Conn Rx Msg
Total Messages Received on Connection
Conn Tx Char
Total Bytes Transmitted on Connection
Conn Tx Msg
Total Messages Transmitted on Connection
Delta Rx Char
Delta Message Bytes Received
Delta Rx Msg
Delta Messages Received
Appendix C.2. EST3 ECP Connection Statistics:
The EST3 ECP protocol has two distinct levels:
A poll-response connection is maintained by the EST panel acting as the master. The bytes transferred in this process
are displayed on the FieldServer as SCADA bytes transmitted and received.
The FieldServer acts as a client by inserting requests into its response messages; the EST panel then inserts the
requested data into its subsequent polling messages. The bytes transferred in this process are displayed on the
FieldServer as PLC bytes transmitted and received.
The following statistics are available on the Driver Aspects screen when viewing Connection Details (select the EST
Connection in Connection Overview, and press space repeatedly to page to this screen):
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
EST3:#01 FYI. For an Old
EST3 Panel, Read MD length
must be even.
This message will be displayed once if any Map Descriptor in a configuration file has an odd
length. Old EST3 Panels (before 2002) simply do not communicate if length is odd.
This message can be ignored if it is new EST3 panel. But if it is old or unknown, try changing
the Map Descriptor length to an even value before contacting technical support.
EST3:#02 Err. Read MD
length must > 0 and <= %d
Numbers of addresses to be read per request are limited.
Edit configuration file to set Map Descriptor length within specified range.8
EST3:#03 Err. Write MD
must have length = 1
One Map Descriptor can write only 1 value. Change length to 18.
EST3: #04 Unknown Escape
Sequence 1B %02X
considered as %02X
This message is printed if the FieldServer receives sequences that are not specified.
Specified sequences are 1B 82, 1B 8D and 1B 9B. This message is for information only and
can be ignored unless the data stored by the FieldServer is invalid in which case, call Tech
support.
8
Appendix C.3. Driver Error Messages
Upload the configuration file, make the necessary changes, download to the FieldServer and cycle power to the FieldServer for the changes to take effect.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com