Re: [foxboro] Alarm panel
- From: "Grace, Kathy" <kgrace@xxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 31 Oct 2002 11:08:15 -0500
Duplicate C:B entries in the AAtab file has never been a supported feature.
This goes all the way back to the beginning of I/A. The rule is each C:B can
be mapped to only one key.
If you use the FoxPanels configurator (or even the very old Alarm Table
Configurator - 20 series) this would not be allowed at configuration time.
However if the edit the AAtab file with a text editor there is obviously no
check.
Regards,
Kathy
-----Original Message-----
From: Marsman, Bram [mailto:bmarsman@xxxxxxxxxxx]
Sent: Thursday, October 31, 2002 9:15 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] Alarm panel
If you say that there are blinking lights, but no alarms, how do you know?
Do you mean that if you push the button next to the light, you don't see any
alarms on the appearing display?
If this is the case, most of the time this is because you generated your
AAtab file from your display, and thus (possibly) adding blocks to your
AAtab file that do not trigger something on the display.
When these block go into alarm, you see a light blinking, press the button
and no alarms appear on your display.
Try, if possible, to Acknowlegde ALL alarms in your system (Set all UNACK
parameters of all compounds to 0) and see if your annunciator light stops
blinking. If not, your annunciators are "out of phase".
I have seen this happen with older verions of MircoIA/CP30/CP40s, where
certain acknowledgements didn't reach the annunciator, but this was fixed a
long time ago...
Also, having multiple entries (same block) in your Tab file can cause some
problems.
-----Original Message-----
From: JL Joachim Leuker [mailto:Joachim_Leuker@xxxxxxxxxxxxxxxxx]
Sent: donderdag 31 oktober 2002 12:22
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] Alarm panel
Hello, Bram,
thank you for your answer. It is a first entry for discussion and thus
helpful.
I think we have gone through all the issues you mention, but I will =
inspect
them again.
The "defective" AAtab file seems ok to me, but:
- It has no empty line at the end and
- the entries are unsorted with respect to panel and key numbers.
Is this really ok?
Not "correctly" means, that the panels do work but they blink where =
there is
no alarm.
Thank you again, regards
Joachim Leuker
--
Dr. Joachim Leuker - Client Manager
Actemium - HMS Planung & Automation GmbH
Duisburg, Germany
http://www.actemium.de
ACTEMIUM - A BRAND OF GTIE
-----Urspr=FCngliche Nachricht-----
Von: Marsman, Bram [mailto:bmarsman@xxxxxxxxxxx]
Gesendet am: Donnerstag, 31. Oktober 2002 10:57
An: 'foxboro@xxxxxxxxxxxxx'
Betreff: Re: [foxboro] Alarm panel
Hi Joachim,
I will answer you although it probably doesn't help much!
My experience has always been that increasing MAX_ACTIONS works, on =
both NT
and UNIX, in init.user.
So, here are some obvious things, maybe you overlooked one....
- Did you reboot?
- Did you remove the # in front of MAX_ACTIONS
- Did you perhaps add you "own" MAX_ACTIONS and is it overwritten later =
in
the file?
- Even more stupid suggestion: Did you perhaps changed init.user.rel in
stead of init.user?
You say the panels do not work "correctly". Do they work at all? Do =
they
only work for blocks 1-2000? Are there any syntax errors in your AAtab
files?
As a last resort: You could try to change MAX_ACTIONS in wp51_glbls, =
however
this has never been necessary in my experience, besides its "illegal". =
(own
risk etc)
Good Luck,
Bram Marsman
Invensys Systems Netherlands.
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
