beautypg.com

Deletion or loss of the listeners' list, Maintenance of the listeners' list (alive), Reception of events – CIRCUTOR EDS-3G Series User Manual

Page 5

background image

EDS-3G

M98240601-03-13B

4.3.8.3.- Deletion or loss of the listeners' list

The producer can completely or partially lose or eliminate the
listeners' list for different reasons:

-

The listener does not answer: when new events or
changes in these events take place, the producer
instantaneously informs all listeners on the list. When the
producer is faced with a communication problem with a
listener, a total of fifty retries are made to send information.
If the listener does not respond to these requests, the
producer deregisters the listener from the distribution list.

-

The producer has rebooted or has temporarily stopped
operating
: if the producer receives an update or generates
a reset for any reason, (firmware, update, loss of power
supply, etc), the entire listeners' list is lost and from then on
stops sending events to the previously associated listeners.

4.3.8.4.- Maintenance of the listeners' list (alive)

Given that there are several reasons why the listeners' list
might be totally or partially affected, the external integration
system needs to implement an (alive) test system against the
producer to ensure that the IP is kept active for a long period
in the distribution list.

It is recommended that the test system is automatic and at
intervals of no more than 10 minutes between each test frame
dispatch. The (alive) test system is based on the updating of
the listener IP, again against the producer, although only the
event changes are requested (False):

http://ip_producer:port/services/user/listener.xml

This request must contain the following body in the message,
in which the listener and the type of data to be received are
again defined:

ip_listener

80

F

-

If the external integration application has remained inactive
for a long period of time, a request to the producer asking
for the entire list of active events is recommended using a
True request. This way the listener again has all the
information lost during the period of inactivity.

4.3.8.5.- Reception of events

When there is any change in the events, the request that the
producer creates against the listeners' distribution list giving
information about the events will be PUT type with the
following syntax:

http://ip_oyente:port/services/user/producer.xml

The request contains the following information in XML format
in the body of the message: information about the events
produced:

T/F

driverId.driverId.driverId…eventId

Evento 1

Descripción 1

Anotación 1

25112010201034

ACTIVATION

driverId.driverId.driverId…eventId

Evento 2

Descripción 2

Anotación 2

25112010201034

25112010201103

disabledDateTime >

DEACTIVATION

-

all: all the events (True) or changes(False)

-

event-id: producer and identifier of the event

-

whyFired: ACTIVATION, DEACTIVATION

Notes referring to the active events:

-

Note: if the producer has implemented http authentication
by user and password, it must be implemented in the
listener by the user.

4.3.9.- Forcing of variables

This request is used to send the variable forcing order (or
writing) to the system. The request should include the name of
the device that wants to make the request. It is important to
incorporate the authentication data when this is necessary.

...

...

...

-

forceVariables: field identifying the XML as a request

-

forceVar: Information from each variable to be forced

-

forceName: variable name in device.variable format

-

field: identifies each field

5.-

Technical features

Power circuit:

-

Single-phase (phase – neutral) A1 – A2 :

-

Frequency:

-

Maximum consumption:

-

Working temperature:

-

Humidity (non-condensing):

Standard version

85…264 V

ac

/ 120…300 V

dc

50…60 Hz

6-10 VA (AC) / 3-4 W (DC)

-10 …+ 60 ºC

5 … 95%

Output Features:

-

Type:

-

Maximum operating power:

-

Maximum operating voltage:

-

Maximum switching current:

-

Electrical life (250 Vac / 5 A):

-

Mechanical working life:

Relay

750 VA

250 V

ac

5 A with resistive load

3 x 104 operations

2 x 107 operations

Mechanical features:

-

Case material:

-

Device protection degree:

-

Dimensions (mm):

-

Weight:

-

Maximum operating height:

UL94 - V0 self-extinguishing plastic

IP 20

105 x 70 x 90 mm (6 modules)

385 g

2,000 m

LED symbols:

-

Power :

-

Slaves:

-

GPRS/3G link:

-

Left RJ45 led:

-

Right RJ45 led:

Equipment power supply and CPU activity

Communicating slave devices shutdown

GPRS or 3G connection linked to the operator

Green: Full duplex / Yellow: Half duplex / Activity

Green: 100 Mb/s / Yellow: 10 Mb/s / Link

Inputs features:

-

Type:

-

Maximum activation current:

-

Insulation:

Voltage-free opto-insulated (dry contact)

50 mA

1500 V

Display:

-

Type:

-

Characters:

-

Back lighting:

2 lines, alphanumeric

20

Yes

Network interface:

-

Type:

-

Connector:

-

Network protocols:

Ethernet 10BaseT / 100BaseTX self-detectable

RJ45

HTTP / Modbus/RTU in RS-485 bus

Safety:

Installation category Class III / EN61010 double-insulated electric shock protection class II.

Connect the device to a power circuit protected with gl fuses in compliance with IEC 269, or

M fuses, with values from 0.5 to 1A. It must be fitted with a circuit breaker switch or

equivalent device, in order to be able to disconnect the device from the power supply. The

power supply cable must have a cross-section of at least 1mm

2

.

Standards:

EC, UL 94, EN61010-1, EN55011, EN 61000-4-2, EN 61000-4-3,

61000-4-11, EN 61000-6-4, EN 61000-6-2, EN 61000-6-1, EN 61000-6-3, EN 61000-4-5

Modem:

-

Work bands (Data only):

UMTS/HSPA - 2100 / 900 Band

GSM - 850 / 900 / 1800 / 1900 Band

Serial interface:

-

Type:

-

Transmission speed (configurable):

-

Data bits:

-

Parity:

-

Stop bit

Three-wire RS-485 (A/B/S)

4800, 9600, 19,200, 34,800, 57,600, 115,200 bps

8

No parity, odd, even

1