ALU 2 1

[Marcoz]

Hi, I have BC10 and Group Hunting ACD.
I've instead a ALU 2 board.
1° question: How can I do to see where the alarms go?
can I see the configuration of this board?
2° question: It's possible to configure this board for receive the alarm to my PC? I must have the Event Manager I see..

 

[Isinor]

If you have ALEX you will find diagrams and details of the ALU2 board in: Basic Exchange, Installation, Installation, Exchange, Installation Instruction Basic, then in Chapter 10 you find the details of the ALU2.

The ALU2 is the old way of doing alarms; you can get audible and visual alarm indication. You can send alarms in to the ALU2; via strapping on the card you have control of electrical signals ETH, LOOP or BATTERY for alarm input/output.

If you have WinFiol on a V24 or Ethernet you can get it to do several things upon receiving an alarm. This will have to be programmed via AL & IO commands…

On the MD110…
Find a free IO Device
IODDP;

If you need to initial an IO Device I would recommend using Ethernet…
IOEQI:EQU=1-0-xx-4,IODEV=ALARMS,TYPE=NETWORK,USAGE=OUT;

To output CLASS 3 & 4 Alarms to the ‘ALARMS Device’ (Ethernet)
ALAPI :IODEV=ALARMS,CLA=3&4;


In WinFiol…
Make sure you have the ‘Monitoring’ Plugin active (Windows Start Menu… WinFiol & Tools Configuration)

1. Choose the menu Run, Monitoring in WinFiol.
2. Click on the ‘New Event’ button.
3. Optionally select a channel, then choose Alarm …from exchange.
4. You can now have several ‘Actions’ such as SMS message and/or Email on receipt of an alarm. (You will need suitable access to SMS gateways Email Servers etc to do this)

Note: At step 3 above you could enter an alarm CLASS and trigger separate events for CLASS 3, or you could also trigger events for an alarm category e.g. 261.

This as always with my answers this is just a rough guide.

Hope this helps.

 

[rednaxela]

Hey Isinor!

Maybe you can finetune the rough guide for me. I've created an IO-device but I can't set the output:

SYSN ALARMS 001-0-60-4 - NETWORK/OUT IN SERVICE

ALAPI:IODEV=ALARMS,CLA=3&4;NOT ACCEPTED
ALARMS
NOT INITIATED

What does this mean, ALARMS not initiated ?

 

[Isinor]

You need to initiate an IO Device using…
IOEQI:EQU=1-0-60-4,IODEV=ALARMS,TYPE=NETWORK,USAGE=OUT;

IODDP; To see the IODEV names

Then you can use it...
ALAPI:IODEV=ALARMS,CLA=3&4;

 

[rednaxela]

Isinor,

I'm doing something wrong Any tips ? It's no problem that I've used the same port for MML-IN usage ?

<IODDP;I/O DEVICE DATA
NODE IODEV/SUBFS BPOS/EQU SIPOS TYPE/USAGE STATUS AUTH
SYSN - 001-0-60 - - IN SERVICE
SYSN SYSDISK1 001-0-60-0 3 ADTX IN SERVICE
SYSSUBFS11
SYSSUBFS21
TMFS
SYSN SYSTERMINAL 001-0-60-1 - MML - 7
SYSN SYSTERMINAL2 001-0-60-2 - MML - 7
SYSN ALARMS 001-0-60-4 - NETWORK/OUT IN SERVICE
SYSN NIU 001-0-60-4 - NETWORK/MML - 7
SYSN NIU1 001-0-60-4 - NETWORK/MML - 7
SYSN NIU3 001-0-60-4 - NETWORK/MML - 7
SYSN NIU6 001-0-60-4 - NETWORK/MML - 7
SYS2 - 002-2-60 - - IN SERVICE
SYS2 CALL-LOGGING 002-2-60-1 - OUT IN SERVICE
SYS2 DNA 002-2-60-4 - NETWORK/OUT IN SERVICE
SYS2 NIU2 002-2-60-4 - NETWORK/MML - 7
SYS2 NIU4 002-2-60-4 - NETWORK/MML - 7
SYS3 - 003-2-60 - - IN SERVICE
SYS3 VMSYS 003-2-60-2 - OUT IN SERVICE
SYS3 NIU-NETW11 003-2-60-4 - NETWORK/MML - 7
END

<IOEQE:iodev=alarms;EXECUTED

<IOEQI:EQU=1-0-60-4,IODEV=ALARMS,TYPE=NETWORK,USAGE=OUT;EXECUTED

<ALAPI:IODEV=ALARMS,CLA=3&4;NOT ACCEPTED
ALARMS
NOT INITIATED

 

[lalrl]

ioeqi is wrong: usage must be mml

 

[rednaxela]

Thanx LALRL ! So far so good:

<aldip;ALARM DISTRIBUTION
DATE: 26FEB03 TIME: 16:28:14
IODEV FUNCTION FORMAT INT/CLA DATE TIME
ALARMS ALARM PRINTOUT ASCII 1,2,3,4
ALARMS HEART BEAT ASCII 00:15 26FEB03 16:28

END

I've received some alerts, for example:

02 PWC-AMSTER 260203 145200
0051 2 0 0007 461 002-2-40-15 077 00015

The heartbeat also worked! But then the channel auto logged-off and after reconnect no alerts or heartbeats are given. Is it something in my channel settings or in my monitor functions ? Please assist ! Thanx already....