You are on page 1of 36

ANT UNIT

ALARMS MANAGER - OMRON OVER IP

Rev.00 - 17/09/2010
Cod. MAN1003UUK USER MANUAL
Operative Office : via G. Amendola 9, 44028 Poggio Renatico (Fe) ITALY
C.C.I.A.A. 101 216
C.Fisc. e P.IVA IT00415540384

For information and assistance please contact the Elenos Technical Assistance Service :

Phone +39 0532 829965


Fax +39 0532 829177
E-mail for general information info@elenos.com
E-mail for support support@elenos.com

Or via Website :

www.elenos.com (in On line Support page)

Please, always you give us information about the device serial number (shown on the identifying label).

All Copyrights are reserved, you may not reproduce any part of this manual in any form without the express written
permission of Elenos S.r.l.
Revision

N° Date Description
00 17/09/2010 First release

Revision 3
Family variants

The units of this family are of two types: units with functionality of Omron over IP and Alarms
manager (subject of this documentation) and units with functionality of SNMP and Web Server
(see the specific manual).

In both cases the most important functions are carried out by an electronic board, the main
component of the unit.
In the unit with functionality of Omron over IP and Alarms manager there are the board men-
tioned above and another Elenos board, to manage additional accessories, best described in the
manual.
Units with functionality of SNMP and Web Server can have up to three main electronic boards.

Dimensions of main electronic board :


Length : 160mm
Width : 100mm
Height : 1U rack
Weight : 248g

Environmental specification of main electronic board :


Power supply current : 300mA @ 12v +/- 20%
Storage temperature : -20°C to +70°C
Operating temperature : 0°C to 50°C
Humidity : up to 90% NC

4 Family variants
Index

1 Product description.................................................................................................................... 7
1.1 Front panel.......................................................................................................................... 7
1.2 Rear panel........................................................................................................................... 9
2 Connections.............................................................................................................................. 11
2.1 Connections scheme......................................................................................................... 11
2.2 Cables schemes................................................................................................................. 13
3 Alarms manager...................................................................................................................... 17
3.1 Alarms manager features description.............................................................................. 17
3.2 How to use........................................................................................................................ 17
3.2.1 Alarm procedure........................................................................................................ 18
3.2.1.1 EXAMPLE............................................................................................................. 19
3.2.2 Omron over Modem.................................................................................................. 20
4 Omron over IP.......................................................................................................................... 23
4.1 Omron over IP features description.................................................................................. 23
4.2 How to use........................................................................................................................ 23
5 Annex....................................................................................................................................... 27
5.1 Alarms manager configuration......................................................................................... 27
5.1.1 Editing the equipmentconfig.cfg file........................................................................ 27
5.1.1.1 Station command............................................................................................... 28
5.1.1.2 Modem.x commands......................................................................................... 28
5.1.1.3 Pollspeed command.......................................................................................... 28
5.1.1.4 TimeBP command.............................................................................................. 28
5.1.1.5 SerialTimeout command.................................................................................... 28
5.1.1.6 Equipment.x commands.................................................................................... 29
5.1.1.7 Pollblock.x commands....................................................................................... 29
5.1.1.8 Pollgroup.x commands...................................................................................... 29
5.1.1.9 IDString parameter............................................................................................. 29
5.1.1.10 AlarmEnable parameter................................................................................... 30
5.1.1.11 Phone.x parameters......................................................................................... 30
5.1.1.12 WindowBetweenAlarms parameter................................................................ 30
5.1.1.13 DelayBetweenResends parameter.................................................................. 30
5.1.1.14 DelayBetweenRetrys parameter .................................................................... 30
5.1.1.15 PagerHangupDelay parameter........................................................................ 30
5.1.1.16 NumberOfResends parameter......................................................................... 30
5.1.1.17 NumberOfRetrys parameter............................................................................ 31
5.1.1.18 AlarmText parameter....................................................................................... 31
5.1.2 Configuration thru hostlink....................................................................................... 31
5.1.2.1 SaveDataToFile .................................................................................................. 31
5.1.2.2 ResetAlarm......................................................................................................... 31
5.1.2.3 RebootControlSystem......................................................................................... 31
5.1.2.4 ResetIPAddressToDefault.................................................................................... 31
5.1.2.5 ID_Machine_x.................................................................................................... 31
5.1.2.6 Enable_Machine_x............................................................................................. 31
5.1.2.7 Pollblock_Machine_x......................................................................................... 32
5.1.2.8 Pollblock_x_address_y...................................................................................... 32

Index 5
5.1.2.9 Device Model ID................................................................................................. 32
5.1.2.10 Software version n........................................................................................... 32
5.1.2.11 Data map version n°........................................................................................ 32
5.1.2.12 Ipaddress_octect_x.......................................................................................... 32
5.1.2.13 Netmask_octect_x........................................................................................... 32
5.1.2.14 Gateway_octect_x........................................................................................... 32
5.1.2.15 ID_String.......................................................................................................... 33
5.1.2.16 AlarmEnable..................................................................................................... 33
5.1.2.17 Number of retrys.............................................................................................. 33
5.1.2.18 Delay between retrys...................................................................................... 33
5.1.2.19 Delay between resends................................................................................... 33
5.1.2.20 Number of resends.......................................................................................... 33
5.1.2.21 PagerHangupDelay.......................................................................................... 33
5.1.2.22 WindowBetweenAlarms.................................................................................. 33
5.1.2.23 PhoneNx........................................................................................................... 33
5.1.2.24 PhoneEnableNx................................................................................................ 34
5.1.2.25 PhoneWrkModelNx.......................................................................................... 34
5.1.2.26 Station Name................................................................................................... 34
5.1.2.27 SMS Status Text................................................................................................ 34
5.1.2.28 SMS Status Ready............................................................................................. 34
6 “How to”.................................................................................................................................. 35
6.1 User information............................................................................................................... 35
6.1.1 Restore default IP address of the board................................................................... 35
6.1.2 Modify the IP address of the board (Alarms manager/Omron over IP functionali-
ties)..................................................................................................................................... 36

6 Index
1 Product description

1.1 Front panel


b
1 2 3 5 c
a

4 6

h
d e f i

On the front panel there are :


1. RS232 connector, DB9 female (a). This connector is used both by specialists for de-
bugging, for manufacturer reserved purposes, for software updates and initialization
of the board, both, in this specific application, for connection to a PSTN modem. The
layout of the circuit is typical of RS232 type, so a 1:1 standard serial cable can be
used to PC connection. For modem connection, however, see “Connections” chapter.

Scheme of DB9 connector


on front panel

Product description 7
2. Status led (b). The meaning is clear through the symbols that represent them. Spe-
cifically:
• n°1-2 are flashing if it is being a transmission/reception over RS232 or a transmis-
sion/reception on RS485;
• n°3 if it is on it indicates that the unit is under power;
• n°4 shows the “vitality” of the equipment. In normal operation this led flashes
every 2 seconds, and if the unit is locked or has problems, the led is always on or
always off;
• n°5 if it is on it indicates the presence of an alarm;
• n°6 if it is on it indicates that an SNMP query was successful;
• n°7 are switched respectively if there is an on going transmission/reception over
Ethernet or a transmission/reception over the fixed network.
3. Ethernet socket (c). For more details, see “Connections” chapter.

On the front panel, on the left, there are:


4. DB15 HD connector (d). This connection is used to interrupt power to the modem.
Normally the modem is switched off and its power is driven by the main electronic
board. After a switching on it resets the modem if the sequence of initialization is
in the configuration file and, thanks to this link, sending a reset also the modem is
turned off, then turned on and eventually resetted. For details, see “Connections”
chapter.
5. Led (green) “CLOSED” (e). Indicates whether the modem is turned on or off. If the
modem is turned on, the led is just lit.
6. Led (red) “ALARMS” (f). If it is on it indicates the presence of at least one active
alarm, if it is off indicates that no alarm is active, while if it is flashing, at least one
of the connected equipment has been banned from the poll. Disabling in fact an
equipment and giving the command to reset you can receive alarms (for details
“Alarms manager” chapter). The led is a “reminder” that a signal received from the
alarms manager remains pending. To remove the flashing signal, having solved the
problem, to rehabilitate the machine excluded from polling function.
7. “RESET” button (g). It has the function to reset the entire system. The user, in fact, is
informed of an alarm only if it is the first, then it does not run any more alarm until
it gets reset. To enable the command the button must hold down for 5 seconds.
8. Led (green) (h). This led is blinking for 5 seconds by pressing the RESET button. At
the end of 5 seconds the reset command is sent to all parts of the system. The led
is always ON if the ANT unit is in LOCAL mode (as the blue led, near the switch-key,
appears ON), it is always OFF if the ANT unit is in REMOTE mode.

8 Product description
9. Key switch (i). To put the machine in LOCAL or REMOTE mode. In REMOTE mode the
alarm procedure is enabled. In LOCAL mode the alarm procedure is not enabled, but
the polling function of all equipment and the Omron over IP or over modem fun-
ctions remain active. If the unit is in local mode the blue led is on. This is an useful
configuration to the maintenance locally.

1.2 Rear panel


On the rear panel there are :

a e b
e d c

1. Two RS485 connectors, BD9 female (a). Their use is equivalent.For more details, see
“Connections” chapter.

Pin Description Pin-out DB9 connector on


rear panel
1 RD B

2 RD A

3 TD B

4 TD A

5 NC

6 NC

7 NC

8 NC

9 GND and shield cable

2. Outlet to recharge the battery (b).


3. Socket with switch for power (c).
4. Earth connection (d).
5. Fuses (e).

Product description 9
10 Product description
2 Connections

2.1 Connections scheme


The connections of this device with other elements with which it interacts must meet
the requirements below.

Connect CAB0450_0 cable from DB9 RS485 on rear panel of ANT unit (these connectors
are two and it does not matter what you use) to any RS485 port on front or on rear
panel of any Elenos device.
If the connection is on RS485 port on rear panel of an Elenos device the transfer rate
is 38400 baud, if it is RS485 port on front panel of an Elenos device the transfer rate is
9600 baud.

One exception is Echos3 (telemetry), where the connection should be made through the
back port of the telemetry with CAB0507_1 cable and the transfer rate is 38400 baud.

Then, connect CAB0502_1 cable from DB9 on front panel of ANT unit to DB25 on a PSTN
modem. The transfer rate can be set freely, depending on the type of modem (typically
9600, 19200 or 38400 baud).

Connect CAB0485_0 cable one hand to DB15 HD on front panel of ANT unit, other side
to modem power supply and to power connector of modem.

The Ethernet connector is used or to realize the function Omron over IP, or to change
the system configuration file. In this case just an FTP client (like Filezilla, freeware) and
username and password are required.

Switch on the apparatus, having connected to the mains (230VAC), with the switch to
“1”.

Connections 11
ANT unit connected to
Elenos devices

Mains

230VAC

230VAC
CAB0450_0 (38400 baud)

Rear Rear
ELENOS DEVICE
(Echos3 except)
230V

RS485

RS485

RS485
DB15 HD
Ethernet
RS232

RS485
ANT UNIT

Modem power supply


Front Front

CAB0502_1
230V CAB0450_0 (9600 baud)

CAB0485_0 CAB0485_0
Pin

CAB0485_0
Crossover cable
Modem

Ethernet network PC
DB25

Power

Eth Eth Eth

Alternative link

ANT unit connected to


Echos3

Mains
230VAC

230VAC

CAB0507_1 (38400 baud)

Rear Rear
ECHOS3
230V

RS485

RS485

RS485
DB15 HD
Ethernet
RS232

ANT UNIT

Modem power supply


Front Front

CAB0502_1
230V

CAB0485_0 CAB0485_0
Pin

CAB0485_0
Crossover cable
Modem

Ethernet network PC
DB25

Power

Eth Eth Eth

Alternative link

12 Connections
ELENCO DEI MATERIALI

ARTICOLO QUANTITA'

CONNETTORE DB9 MASCHIO PER FILO A SALDARE 2


GUSCIO PER CONNETTORE DB9 A VITI LUNGHE 2
CAVO MULTIPOLARE IN GUAINA CON CALZA( 24AWG) 1500 ca.


CN1 CN2

DB9 Maschio a saldare in guscio con v iti lunghe
DB9 Maschio a saldare in guscio con v iti lunghe
1 Marrone
6 Giallo 1
2.2 Cables schemes

2 Rosso 6
7 Arancio 2
3 Giallo 7
8 Marrone 3
4 Arancio 8
9 Rosso 4
5 9
5

DB9 M.
DB9 M.

1500 mm

 DESCRIZIONE QUOTE SENZA IND. TOLL.

Connections
CABLAGGIO UNITA’ CONTROLLO SNMP
 TUTTE LE QUOTE, SE NON
MATERIALE
DIVERSAMENTE SPECIFICATO, SI
TRATTAMENTO INTENDONO IN MILLIMETRI

DISEGNATORE DATA CONTROLLATO DATA REVISIONE SCALA N° PEZZI


FOGLI N. 17/12/2009
FILE DISEGNO
 CAB0450_0.DOC
CODICE DISEGNO
 CAB0450_0
 CAB0450_0

13
ELENCO DEI MATERIALI
CN1 CN2
ARTICOLO QUANTITA'
1 MARRONE 1
6 6
2 ROSSO 2 CONNETTORE DB9 MASCHIO A SALDARE 1
7 7
3 ARANCIONE 3 CONNETTORE DB9 FEMMINA A SALDARE 1
8 8
4 GIALLO 4
9 NERO 9 GUSCIO A VITI LUNGHE PER CONNETTORE DB9 2
5 5
CAVO MULTIPOLARE AWG24 + CALZA METALLICA 1500mm ca.
DB9 M. DB9 F.



COLLEGARE LA CALZA METALLICA CONNETTORI IN GUSCIO
AL CORPO DEI CONNETTORI A VITI LUNGHE
CN1 CN2
DB9 MASCHIO DB9 FEMMINA
1500mm

Connections
DESCRIZIONE QUOTE SENZA IND. TOLL.
CABLAGGIO SERIALE ANTENNA NORD – ECHOS 3
MATERIALE TUTTE LE QUOTE, SE NON
DIVERSAMENTE SPECIFICATO, SI
TRATTAMENTO INTENDONO IN MILLIMETRI
DISEGNATORE DATA CONTROLLATO DATA REVISIONE SCALA N° PEZZI
MELITO L. 05/07/2010 20/07/2010 1
FILE DISEGNO
1 20/07/2010 Modificato Pinout  CAB0507_1.DOC
CODICE DISEGNO
Rev. Data Descrizione revisione
 CAB0507_1

CAB0507_1

14
ELENCO DEI MATERIALI
1 1
14 6 ARTICOLO QUANTITA'
2 2
15 7 DB9 MALE CONNETTORE DB25 MASCHIO
3 3
1
VOLANTE A SALDARE (CN1)
16 8
4 4 CN2 GUSCIO A VITI LUNGHE PER
1
17 9 CONNETTORE DB25 (CN1)
5 5 CONNETTORE DB9 MASCHIO
18 1
6 VOLANTE A SALDARE (CN2)
DB25 MALE 19 GUSCIO A VITI LUNGHE PER
7 1
20 CONNETTORE DB9 (CN2)
CN1 8 CAVO TRIPOLARE (O PIU’)
21 1000mm ca.
9
SCHERMATO DA 0,25mmq
22
 10
23
 11
24
12
25
13

CONNETTORE DB25 MASCHIO COLLEGARE LA CONNETTORE DB9 MASCHIO


IN GUSCIO A VITI LUNGHE CALZA METALLICA IN GUSCIO A VITI LUNGHE
AL CORPO DEI
CONNETTORI

CN2
CN1

1000mm

DESCRIZIONE QUOTE SENZA IND. TOLL.


CABLAGGIO MODEM ANALOGICO – UNITA’ TCP/IP (ANTENNA NORD)
MATERIALE TUTTE LE QUOTE, SE NON

Connections
DIVERSAMENTE SPECIFICATO, SI
TRATTAMENTO INTENDONO IN MILLIMETRI

DISEGNATORE DATA CONTROLLATO DATA REVISIONE SCALA N° PEZZI


MELITO L. 22/06/2010 06/07/2010 1
FILE DISEGNO
1 06/07/2010 Modificato pin-out lato DB25  CAB0502_1.DOC
Rev. Data Descrizione revisione CODICE DISEGNO
 CAB0502_1

CAB0502_1

15
ELENCO DEI MATERIALI
J2
ARTICOLO QUANTITA'
J1 BOCCOLA
CONNETTORE DB15HD (3 FILE DA 5 POLI)
1 2 1
2 FEMMINA A SALDARE
3 GUSCIO PER CONNETTORE DB9 A VITI
1
1

4
5
LUNGHE
6 PRESA PER ALIMENTAZIONE DIAMETRO
7 1
8
CONTATTO EST. 5,5mm - INT. 2,1mm
9 SPINA PER ALIMENTAZIONE DIAMETRO
1
10 CONTATTO EST. 5,5mm - INT. 2,1mm
11 J3
12 CAVO BIPOLARE IN GUAINA 0,5mmq / 20AWG 4000mm
13 SPINA
14
 15 2

1
DSUBHD 15P F.


2000

Connections
DB15HD FEMMINA
IN GUSCIO A VITI DESCRIZIONE QUOTE SENZA IND. TOLL.
CABLAGGIO COMMUTAZIONE ALIMENTAZIONE MODEM ESTERNO
LUNGHE
MATERIALE TUTTE LE QUOTE, SE NON
DIVERSAMENTE SPECIFICATO, SI
TRATTAMENTO INTENDONO IN MILLIMETRI
DISEGNATORE DATA CONTROLLATO DATA REVISIONE SCALA N° PEZZI
MELITO L. 07/05/2010 0
FILE DISEGNO
 CAB0485_0.DOC
CODICE DISEGNO
 CAB0485_0

CAB0485_0

16
3 Alarms manager

3.1 Alarms manager features description


Through the RS232 port, positioned in ANT unit front panel, you can make both de-
bugging/updating (usually applications reserved to the constructor) and implement
“Alarms manager/Omron over Modem” features, connecting over a modem or a PC,
emulating a modem.
The sole modem suitable for this unit is the PSTN one. The ANT unit is not yet able to
manage GSM modems.
Specifically, since the communication is bidirectional, when the alarms manager dials
the enabled devices (datacenters and pagers), it sends them the alarms messages
(alarms manager function), when the system administrator dials the ANT unit, he may
manage the whole system thru the Omron over modem function.

Through the Ethernet port, however, placed in ANT unit front panel, you can make both
debugging/firmware updating/configuration (usually applications reserved to the con-
structor), and implement Omron over IP feature. This application is equivalent to Omron
over Modem, but in fact is realized on IP.
See “Omron over IP” chapter.

The communication is based, on both ports, on Omron Protocol.


We report here a tutorial link reference on Omron Protocol:
http://forums.mrplc.com/index.php?autocom=downloads&showfile=907

The main characteristic of “Alarms manager” is to focus the state of all devices connec-
ted to it and analyze it in terms of alarms.
When a malfunction happens, it is communicated to all users enabled to receive it.
An administrator may link with the unit (Omron over Modem or Omron over IP) and
may check alarms, query the system machines (including ANT unit) and check the sta-
tus of devices connected to the bus 485.
Hostlink tables describe the available parameters. Elenos will provide these informa-
tions to customers developing their own remote management software.
In general, these include : address, meaning and mode of interaction (reading and wri-
ting) of each variable.

Warning : all issues relating to the implementation and network management,


security and communications are under the responsibility of the end user.

3.2 How to use


Made all the necessary connections (including to a PSTN modem) the ANT unit can start
its functions.
If the modem is ON, the green led, called CLOSE (“e” in the picture of “Product descrip-
tion” chapter) will be ON, otherwise will be OFF.
Identified to how many and to which addresses is linked (information that is retrieved
in configuration file. cfg, installed by the manufacturer on the electronic board) the
alarms manager starts to poll the connected devices in order to determine the presence
of an error state.
Alarms manager 17
At the first error found alarms manager starts the alarm procedure and on the front
panel the red led is ON (“f” in the picture of “Product description” chapter).
Other errors states don’t activate other alarm procedures until reset.
User may decide to disable from the polling (locally or remotely) the device in error
status and set the reset.
In this phase the green led “h” will flash for 5 seconds, after which the reset will be
sent to all equipment.
In this way, the alarms manager will again start new allarm procedures if it identifies
other errors.
The red led will now be flashing to indicate that a device has been disabled by the
control.
Solved the problem on that device, the user can enable it to the polling.
The red led turns off.

3.2.1 Alarm procedure


Found an error state the unit starts to dial in order to report the alarm.
The telephone numbers enabled are in the configuration file .cfg.
These numbers can be both DATA CENTER and PAGER. If it is DATA CENTER the unit will
send a string (see below the format) and will be shut down communication. If it is PA-
GER the unit will send 5 alphanumeric characters, defined by the user, and will be shut
down communication.

Data center string :


ELENOS;ANT_UNIT;$STATION ID;$OMRON_ID;$ERR_N°;$ERR_DESCRIPTION
where
• $STATION ID is the identification number of the station
• $OMRON_ID is ANT unit Omron ID, it is 0
• ERR_N° is error number
• ERR_DESCRIPTION is error string “COMUNICATION FAULT : ID N° xx DOESN’T ANSWER”, with xx =
Omron ID of device with problems.

For each enabled number a call is authorized, if the number is busy or does not respond
in PagerHangupDelay seconds the unit waits for DelayBetweenRetrys seconds and
try again.
The maximum number of proofs is equivalent to NumberOfRetrys times and then goes
to the next number.
Completed a first cycle of calls, it waits for WindowBetweenAlarms seconds. In this
time it continues to make the polling with enabled equipment and it waits calls on the
modem or connections on the Ethernet port.
In fact, during a cycle of phone calls the unit does not accept incoming calls, while in
the waiting time between cycles it accepts calls.
Warning : a call to the alarms manager stops momentarily operations unit.
If the connected user disables a device from the polling and gives the reset, the call
procedure is interrupted.
Otherwise the procedure is repeated for NumberOfResends cycles.

18 Alarms manager
3.2.1.1 EXAMPLE
Configuration :
IDString=”Test Elenos”
AlarmEnable=1 Phone.1=0123456789; 1; 0
Phone.2=9876542123; 0; 0
Phone.3=2154569872,1234; 1; 1
Phone.4=2587452148; 0; 0
Phone.5=4251862145,1234; 1; 1
WindowBetweenAlarms=600
DelayBetweenRetrys=60
PagerHangupDelay=50
NumberOfResends=10
NumberOfRetrys=2
Worst case : any number answer.

Explanation :
The alarm manager is scheduled to call, in case of alarm, 3 numbers and each number
is called 2 times.
The time between calls is 60 seconds, while it waits 50 seconds from dialing, then it
calls the next number.
At the end of a cycle of 3x2 calls (3 = number of calls, 2 = number of calls per user), so
here after 360 seconds, it stops the “short” round of calls (Phase A).
The alarms manager starts to count both PagerHangupDelay and DelayBetweenRetrys
in the same moment. So the two times overlap and the most important is the longest
time.
So Phase A can take up to six calls per 60 seconds maximum.
At the end of the last 60 seconds, in which the alarms manager is deaf to incoming
calls, it starts the period for accepting the call, so it waits 600 seconds (Phase B) before
resuming a new round of 3x2 calls (PHASE A ).
Phase A and phase B are alternating, A is 360 seconds and B is 600 seconds.
If a data center calls the modem during the PHASE A the alarms manager doesn’t accept
the incoming call, while alarms manager listens to the ring during any single stage B.

For a better understanding of the configuration parameters, please, see “Alarms mana-
ger configuration” annex.

TIME

0 PagerHangupDelay

DelayBetweenRetrys WindowBetweenAlarms
PHASE A PHASE B PHASE A

Call to 1°number

Call to 2°number

Call to 3°number

Alarms manager 19
3.2.2 Omron over Modem
The product described here is an open system, in fact to “talk” with the ANT unit can
choose the Omron over IP interface created by Elenos or a management software crea-
ted by the user to Omron over IP or Omron over Modem communication.

The modem connection with a PC with a PSTN modem.


The procedure, for example, is as follows:
Windows Start / All Programs / Accessories / Communications / Network connections.

In the opened window click “Create a new connection.”


It starts the wizard:
Connection to the corporate network/Remote connection.
Enter the name of the station.
Enter the phone number to call (unit ANT number).
A new network connection is created. The administrator may use it each time to con-
nect the unit.

20 Alarms manager
Alarms manager 21
22 Alarms manager
4 Omron over IP

4.1 Omron over IP features description


Omron over IP functionality, described here, is a web application written in PHP which
allows, through Omron protocol, to read/change the data of an Elenos apparatus or
system.
The data are sent from the application over Internet.
ANT unit must be connected through the Ethernet port, located on its front panel, to the
Ethernet network, while a remote user must have his PC connected to Internet.
The IP address assigned to the ANT unit must be public or must be realized a VPN net-
work.
The application can be installed on any type of web server and therefore can work on
any operating system.
The product comes from Elenos or already installed and configured on a PC; or the
installation/configuration is delegated to the user, if he is specialized and expert on the
subject.
For a basic installation you can use the Zend Server CE, which integrates in a single
procedure the Apache web server istallation, MySQL database server installation, the
management web interface and PHP interpreter.

4.2 How to use


After installation and database configuration you can proceed to open the application,
accessing through a browser, to http://localhost address.
After an authentication phase, entering username and password, it opens the interface
homepage.

Omron over IP 23
Select the “Hosts”, you get the list of equipment of the system that you want to moni-
tor.
There is the IP address to which the system responds and its port.

Click the IP address, it opens the page that represents the equipment configuration.
A synopsis identifies not only the equipment that we can monitor, but also how they
are related to one another in terms of links.
To see the operating status of individual devices simply click on the lens.

24 Omron over IP
The rotating indicator shows the feedback system, that is loading data.

After loading you can see its contents.


The operating parameters are shown in a table and grouped according to categories
which are listed under the item Details.
The system updates the parameters every 5 seconds.

Omron over IP 25
If the system is unable to answer, a box will highlight the problem type.
In this case, simply return to the summary page of the hosts through the link “Back to
Device List”,under the table.

26 Omron over IP
5 Annex

5.1 Alarms manager configuration


The setup of alarms manager can be made whether editing the equipmentconfig.cfg
file or writitng parameters into the hostlink table.

5.1.1 Editing the equipmentconfig.cfg file


Needs: a PC with an Ethernet socket, OS Windows or Linux, Filezilla or other FTP softwa-
res, an Ethernet twisted pair cable between PC and ANT unit.
In case the computer and ANT unit are connected directly to the local Ethernet network,
it doesn’t need the twisted pair cable.
Filezilla is an FTP freeware software and it may be downloaded from http://filezilla-
project.org/download.php?type=client.

• Launch Filezilla, insert as host the IP address of the board, insert username and
password. Then push the connect pushbutton.
• On the “home/ant/cfg” directory you may find the equipmentconfig.cfg file.

Annex 27
• Click on it with the right mouse button and transfer this file on PC.
• Then you may modify the copy saved into your computer.
• After the modifications, you may download the updated file into the board simply
clicking on it with right mouse button.
• In order to make the configuration file modifications active, switch off and then on
the board, or send a reset command thru Omron messages.

Warning : alarms manager operation depends on the contents of the configuration


file. Enter parameters with incorrect values determines the malfunctioning equip-
ment.

We report here a list of commands and parameters.


Each text row starting with the char ‘*’ is a comment and it will take no notice of its
content.

5.1.1.1 Station command


This is the identification string that identifies the whole station.
Syntax:
Station=Stringa
The String field (9 chars max) following the ‘=’ char is the station identifier name sent
to the Data Center when a communication alarm happens on ANT unit.

5.1.1.2 Modem.x commands


This is the list of initialization commands sent to the modem after the reset or the
power-on of the unit.
Valid values of X parameter are between 1 and 32, it means it is possible to list up to 32
commands.
Syntax:
Modem.1=ModemComandString

5.1.1.3 Pollspeed command


It settles the baud rate for the serial communication on 485 bus. Thru this bus, unit and
the other devices send and receive all OMRON messages.
WARNING: do not modify this value! If this value will be modified or erased, the whole
station will not work in the right way.
Syntax:
pollspeed=38400

5.1.1.4 TimeBP command


It settles the time interval between an Omron command sending and the next one.
The value following the ‘=’ char establishes the interval value in ms (min=0, max=1000.
Syntax:
TimeBP=500

5.1.1.5 SerialTimeout command


It settles the greatest time interval allowed between an Omron command sending and
its anwer reception.
The value following the ‘=’ char establishes the interval value in tenths of seconds
(min=0, max=10).
If after SerialTimeout tenths of seconds the destination unit doesn’t answer, unit signals
a communicaiton error.
Syntax:
SerialTimeout=5

28 Annex
5.1.1.6 Equipment.x commands
They settle the list of the Omron devices controlled by unit thru the 485 serial connec-
tion.
Syntax:
equipment.x=y;z;a
where:
• x Device position into the devices list. Valid values are between 1 and 16. Do not
use x=0. List all devices in order, starting from x=1, do not skip any value. Malfun-
ctionings may happen when this rule is not obeyed.
• y Device Omron ID. Valid values are between 1 and 49.
• z Device pollblock (see below).
• a Polling priority(1=higher priority, 32=lower priority).
WARNING: only modify the ID value, in accordance with the ID settled on the devices.
Keep 1 as pollblock and 1 as priority. If these values will be modified or erased, the
whole station will not work in the right way.

5.1.1.7 Pollblock.x commands


They settle the list of the Omron commands.
Syntax:
pollblock.x=y1;y2;y3....
where:
• x Pollblock identifier. Valid values are between 1 and 16.
• y1;... List of the used pollgroups (see below). Use 16 pollgroups.
• 0 means not enabled pollgroup.

WARNING: do not modify there values. The only valid command is


pollblock.1=1;2;3;4;0;0;0;0;0;0;0;0;0;0;0;0
If this value will be modified or erased, the whole station will not work in the right
way.

5.1.1.8 Pollgroup.x commands


These are the descriptions of the read single Omron commands.
Syntax:
pollgroup.x=y;z;p
where:
• x Pollgoup ID. Valid values are between 1 and 32.
• y Starting address for the read command on the slave Omron device hostlink.
Valid values are between 0 and 999.
• z Number of words for the read command. Valid values are between 1 and 64.
• p Priority of the command (1=higher priority, 32= lower priority).

WARNING: do not modify these values. THE ONLY VALID SEQUENCE IS:
pollgroup.1=610;28;1
pollgroup.2=638;28;1
pollgroup.3=666;24;1
pollgroup.4=770;1;1
If these values will be modified or erased, the whole station will not work in the right
way.

5.1.1.9 IDString parameter


It contains an identification string (max 16 chars). Reserved for future functions.
Syntax:
IDString=”Test Elen

Annex 29
5.1.1.10 AlarmEnable parameter
It enables the alarms dispatch procedure
Syntax:
AlarmEnable=1

WARNING: do not modify this value.


If this value will be modified or erased, the whole station will not work in the right
way.

5.1.1.11 Phone.x parameters


They list the telephone numbers enabled or not to be called during alarm procedure.
Syntax:
phone.x=n;a1;a2
where:
• x Telephone number ID. Valid values are between 1 and 5.
• n Telephone number (max 22 chars).
• a1 Number enable parameter (1 = enable, 0 = disabled).
• a2 DST mode (0 =data center, 1 = pager).

WARNING: carefully modify these values.


If these values will be wrongly modified or erased, the whole station will not work in
the right way.
In the case of a number enables as pager, the telephone number and the message
string have to be separated by a comma. See the example below.
Es. Phone.2=004789024028,9999#;1;1

5.1.1.12 WindowBetweenAlarms parameter


This parameter settles the time interval in seconds between a calls cycle and the fol-
lowing one during a alarm procedure. Valid values are between 0 and 600.
Syntax:
WindowBetweenAlarms=300

5.1.1.13 DelayBetweenResends parameter


Reserved. Available for future releases.
WARNING: settle it to same value for the WindowsBetweenAlarms parameter.
Syntax:
DelayBetweenResends=300

5.1.1.14 DelayBetweenRetrys parameter


This parameter settles the time interval in seconds between a not successful calls and
the following attempt. Valid values are between 0 and 600.
Syntax:
DelayBetweenRetrys=60

5.1.1.15 PagerHangupDelay parameter


This parameter settles the greatest time interval in seconds allowed between a dial and
the connection. Valid values are between 0 and 600.
Syntax:
PagerHangupDelay=60

5.1.1.16 NumberOfResends parameter


This parameter settles the max number of alarm calls cycles. Valid values are between
1 and 10.
Syntax:
30 Annex
NumberOfResends=5

5.1.1.17 NumberOfRetrys parameter


This parameter settles the max number of not successful calls to a phone number, befo-
re to call the following phone number. Valid values anre between 1 and 10.
Syntax:
NumberOfRetrys=3

5.1.1.18 AlarmText parameter


This string contains the alarm message. This message will be sent to datacenter ena-
bled numbers when a communication fault happens.
Syntax:
AlarmText=ELENOS;CONC_UNIT;00;001;Communication error - unit n 01

WARNING: do not modify this parameter.

5.1.2 Configuration thru hostlink


On alarms manager a memory space is available for exchange data using Omron proto-
col. This area, called hostlink, contains all parameters requested for the configuration of
the unit itself.
Here below the description of the availaable informations.

5.1.2.1 SaveDataToFile
(address 100 ,1 word)
This value is usually 0. Writing 1 on this memory location, all parameter on hostlink will
be saved into the equipmentconfig.cfg file.

5.1.2.2 ResetAlarm
(address 101 ,1 word)
This value is usually 0. Writing 1 on this memory location reset command will be sent to
the devices connected to alarms manager thru Omron bus and enabled.

5.1.2.3 RebootControlSystem
(address 102,1 word)
This value is usually 0. Writing 1 on this memory location alarms manager will reboot.
The execution of this command stops the Omron connection between alarms manager
and the remote administrator.

5.1.2.4 ResetIPAddressToDefault
(address 103,1 word)
This value is usually 0. Writing 1 on this memory location IP address will be set to
default 192.168.4.89, Netmask value to default 255.255.255.0 and Gateway address to
default 192.168.4.1.
These modifications will take effect only after alarms manager reset.

5.1.2.5 ID_Machine_x
(address 120...135,16 word)
This array contains the Omron ID numebrs for the connected devices. Valid ID numbers
are between 1 and 49. Writing a 0 means a not connected device.
Any modification will take effect only after alarms manager reset.

5.1.2.6 Enable_Machine_x
(address 152...167,16 word)

Annex 31
This array contains enabling flags for the connected devices. If an element value is 1,
then alarms manager will do the polling of the matching device.
Any modification will take effect immediately.

5.1.2.7 Pollblock_Machine_x
(address 184...198 ,16 word)
This array contains the pollblock numbers for the connected devices.
WARNING: The only valid pollblock number is 1.
If this value will be modified or erased, the whole station will not work in the right
way.

5.1.2.8 Pollblock_x_address_y
(address 220...347 ,128 word)
This array contains the adresses for up to 8 pollblocks. Each pollblock contains up to 16
adresses.
Any modification will take effect only after alrms manager reset.

5.1.2.9 Device Model ID


(address 400 ,1 word)
This is the model ID for the alarms manager.
WARNING: Do not modify this value.

5.1.2.10 Software version n.


(address 401,1 word)
This is the FW release number for the alarms manager.
WARNING: Do not modify this value.

5.1.2.11 Data map version n°


(address 402,1 word)
This is the hostlink release number for the alarms manager.
WARNING: Do not modify this value.

5.1.2.12 Ipaddress_octect_x
(address 410...413,4 word)
This array contains 4 octets of the IP address for the alarms manager.
The default IP addres is 192.168.4.89. This is the value after any IP reset (address 102).
Any modification will take effect only after alarms manager reset.

5.1.2.13 Netmask_octect_x
(address 414...417,4 word)
This array contains 4 octets of the Netmask value for the alarms manager.
The default Netmask value is 255.255.255.0. This is the value after any IP reset (address
102).
Any modification will take effect only after alarms manager reset.

5.1.2.14 Gateway_octect_x
(address 418...421,4 word)
This array contains 4 octets of the IP address for the gateway.
The default gateway addres is 192.168.4.1. This is the value after any IP reset (address
102).
Any modification will take effect only after alarms manager reset.

32 Annex
5.1.2.15 ID_String
(address 430...439,10 word)
This is the identification string for the device (max 16 chars). For future releases.

5.1.2.16 AlarmEnable
(address 440,1 word)
It enables (AlarmEnable = 1) the alarm sending procedure.
WARNING: do not modify this field.

5.1.2.17 Number of retrys


(address 444,1 word)
This parameter settles the max number of not successful calls to a phone number, befo-
re to call the following phone number. Valid values anre between 1 and 10.
Any modification will take effect only after alarms manager reset.

5.1.2.18 Delay between retrys


(address 445 ,1 word)
This parameter settles the time interval in seconds between a not successful calls and
the following attempt. Valid values are between 0 and 600.
Any modification will take effect only after alarms manager reset.

5.1.2.19 Delay between resends


(address 446,1 word)
Reserved. Available for future releases.
WARNING: settle it to same value for the WindowsBetweenAlarms parameter.

5.1.2.20 Number of resends


(address 447,1 word)
This parameter settles the max number of alarm calls cycles. Valid values are between
1 and 10.
Any modification will take effect only after alarms manager reset.

5.1.2.21 PagerHangupDelay
(address 448,1 word)
This parameter settles the greatest time interval in seconds allowed between a dial and
the connection. Valid values are between 0 and 600.
Any modification will take effect only after alarms manager reset.

5.1.2.22 WindowBetweenAlarms
(address 449,1 word)
This parameter settles the time interval in seconds between a calls cycle and the fol-
lowing one during a alarm procedure. Valid values are between 0 and 600.
Any modification will take effect only after alarms manager reset.

5.1.2.23 PhoneNx
(address 450...524,75 word)
This array contains the telephone numbers (up to five numbers) as destination for the
alarm messages and calls. Each number has max 22 chars.
Any modification will take effect only after alarms manager reset.
WARNING: carefully modify these values. If these values will be wrongly modified or
erased, the whole station will not work in the right way.

Annex 33
5.1.2.24 PhoneEnableNx
(address 530...534,5 word)
Phone number enabling flag (1 = enabled, 0 = disabled).
Any modification will take effect only after alarms manager reset.
WARNING: carefully modify these values. If these values will be wrongly modified or
erased, the whole station will not work in the right way.

5.1.2.25 PhoneWrkModelNx
(address 535...539,5 word)
DST mode (0 =data center, 1 = pager).
In the case of a number enables as pager, the telephone number and the message
string have to be separated by a comma. See the example below.
Ex. 004789024028,9999#;1;1
Any modification will take effect only after alarms manager reset.
WARNING: carefully modify these values. If these values will be wrongly modified or
erased, the whole station will not work in the right way.

5.1.2.26 Station Name


(address 550...554,5word)
This string contains the Station Name.
WARNING: note that the string length has to be less than or equal to 9 chars, and a
string terminator follows last char.

5.1.2.27 SMS Status Text


(address 610...690,80 word)
This string contains the alarm message, when communication errors happen on alarms
manager.
WARNING: do not modify this field.

5.1.2.28 SMS Status Ready


(address 770,1 word)
This is the alarm flag when communication errors happen. If its value is 1, alarms ma-
nager has a fault.
WARNING: do not modify this field.

34 Annex
6 “How to”

6.1 User information


6.1.1 Restore default IP address of the board
To reset the IP address of the electronic board to the default value 192.168.4.89, you
must follow these steps:

• Pull out the board from ANT unit rack by unscrewing the 4 screws on the front pa-
nel.
• You can see on the board 8 dip switches. The configuration of these is: all OFF, ex-
cept 2 and 4 are ON. Move the dip switch 7 from OFF to ON.
Dip switch configuration

Dip switch configuration to


restore the IP address

• Insert the card in the rack and turn on the unit.


• Wait that SNMP led and the led placed above flash alternately.
• Pull out the board from the rack. It does not matter turn it off before.
• Put switch 7 as OFF.
• Insert the card in the rack.
• Now the IP address of the board is 192.168.4.89.

"How to" 35
6.1.2 Modify the IP address of the board (Alarms manager/Omron
over IP functionalities)
In order to modify the IP address (default board IP = 192.168.4.89) of a board program-
med with the Omron over IP firmware, please follow the below procedure:

• Connect thru modem/RS232 or IP to the board, activating the transparent Omron


mode.
• Modify the board IP address writing the new address on memory locations at the
address 410…413 of the hostlink table.
• Modify the board IP mask writing the new mask on memory locations at the ad-
dress 414…417 of the hostlink table.
• Modify the board gateway address writing the new address on memory locations at
the address 418…421 of the hostlink table.
• Save the modified data writing the value 1 on memory location at the address 100
of the hostlink table.
• Send a system reset writing the value 1 on memory location at the address 102 of
the hostlink table.

36 "How to"

You might also like