similar to: ALARM words

Displaying 20 results from an estimated 50000 matches similar to: "ALARM words"

2024 Oct 22
1
Why only the first of a series of calls to a function in my driver executing?
Hello, always nice to hear about new drivers :) OTOH, check for any variables you might have been re-using, so their earlier state impacts later runs - whether buffers allocated statically (or by caller without rewinding the pointer and maybe nulling the contents), or position counters, etc. Similarly, be sure to pre-initialize anything of value and not start out with random bits from the stack.
2024 Oct 22
1
Why only the first of a series of calls to a function in my driver executing?
Hello all, In my new driver I have a function that searches for the position of a known substring in a delimited string. I am trying to populate a series of integer variables with the position value of various substrings. The first call to the function performs correctly but the remaining calls in the code series are not being executed (there are six more calls after the first successful
2024 Oct 26
1
Getting the NUT pieces to work together...
Sounds great! By `connection error` it looks like the `upsc` client had nowhere to go. Is `upsd` started (and does it `LISTEN` on locahost or asterisk per `upsd.conf`)? Jim On Sat, Oct 26, 2024, 08:13 William R. Elliot <bill at wreassoc.com> wrote: > Hello again. > > I now have large chunks of the new driver working in the foreground and > wanted to see what upsc reports
2024 Oct 22
1
Why only the first of a series of calls to a function in my driver executing?
An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20241022/a5e3106d/attachment.htm>
2024 Oct 24
1
Unrecognized command-line options
An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20241024/4b16b621/attachment.htm>
2024 Oct 26
1
Getting the NUT pieces to work together...
An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20241026/ce542852/attachment.htm>
2012 Feb 28
2
NUT driver update process...
Hi Billy, switching back this thread to -upsdev 2012/2/27 William R. Elliot <bill at wreassoc.com>: > I have been able to set the 'FSD' from the driver and it is picked up by > upsmon.? That gives me the functionality that I was asked to put in the > driver.? If that is against the rules then I'll make an adjustment when the > allowed method is defined.? :-) yup,
2006 Jun 02
2
NUT shutdown on 'building alarm' (
Dear NUT developers, I am using NUT + bcmxcp + Powerware 9315. I would like to use NUT to shut down my systems if the air conditioning fails and the room get too hot. I want the same shutdown sequence as would be produced when the UPS goes on battery. The UPS has a terminal block at the front for up to six different 'building alarms'. I can connect a thermostat (35C) to the
2007 Aug 07
0
"ups.status" -> "ups.alarm"
The list of status bits we're seeing has increased over the years. Currently for instance, the usbhid-ups driver has defined no less than 20 status bits (and I intend to add two more in the next couple of days, FRANGE and FANFAIL): #define STATUS_ONLINE 0x00001 /* on line */ #define STATUS_DISCHRG 0x00002 /* discharging */ #define STATUS_CHRG 0x00004 /*
2005 Sep 19
3
[resend] [patch] driver for Eltek AL175 alarm module
Hello up there! Attached is my patch to add support for AL175 alarm module, Please ACK or NAK this. -- ?????? ??????? -------------- next part -------------- A non-text attachment was scrubbed... Name: al175.patch Type: text/x-diff Size: 35632 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20050919/84b639e0/al175-0001.bin
2012 Mar 02
0
Formalize use of the FSD flag (was: NUT driver update process...)
2012/2/28 Arnaud Quette <aquette.dev at gmail.com>: > Hi Charles > > 2012/2/28 Charles Lepple <clepple at gmail.com>: >> On Feb 28, 2012, at 3:44 AM, Arnaud Quette wrote: >> >>> Hi Billy, >>> >>> switching back this thread to -upsdev >>> >>> 2012/2/27 William R. Elliot <bill at wreassoc.com>: >>>> I
2005 Aug 24
1
Yellow Alarm issues with second TE410P installed
Hi, Ok, I put the new TE410 into our system last night - This is the second TE410P card. There is also TDM400P in Slot 5 with IRQ 9 which is shared with aic7xxx (SCSI) According to "cat /proc/interrupts", the new card is in the second slot using IRQ 11 (the first card is in slot 1 on IRQ 10 - but always has been). With only the original card install, there has been no issues with
2012 Feb 14
1
New variables?
An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120214/96cc8043/attachment.html>
2004 Dec 17
0
Red Alarm / Alarm Cleared Zaptel Issue (bug? )
Check with your telco. We had the same problem on 1 of our PRI's, every day at 5:00 sharp, red alarm, with all calls cut off for 30 seconds exactly. Turns out the equipment at the CO was going into a test loop at that time because of a forgotten setting by a tech. Man, what a finger pointing exercise that was. -----Original Message----- From: Matthew Boehm [mailto:mboehm@cytelcom.com] Sent:
2004 Dec 17
1
Red Alarm / Alarm Cleared Zaptel Issue (bug?)
Hello, About every 2 or 3 days I notice in the messages log file: Dec 17 08:39:27 WARNING[1220]: Detected alarm on channel 2: Red Alarm Dec 17 08:39:27 WARNING[1220]: Detected alarm on channel 3: Red Alarm Dec 17 08:39:27 WARNING[1220]: Detected alarm on channel 4: Red Alarm Dec 17 08:39:27 WARNING[1220]: Detected alarm on channel 5: Red Alarm Dec 17 08:39:27 WARNING[1220]: Detected alarm on
2012 Feb 27
1
Submitting updated driver
From private E-mail: > > My question to you is how I should go about getting > > the changes back into the system. My work has been exclusively on the ONEAC > > driver and man page. The driver .c file is almost completely redone. > >how can you warrant compat? >Ie, if it's a full rewrite, what have you done to ensure that >currently supported devices will still
2004 Jun 13
0
Red alarm on T1 PRI but not on zttool
SYNOPSIS Erratic red alarm T1 PRI on asterisk, but zttool running concurrently during alarm shows no errors, irq misses, or alarms, on any span. Using asterisk and quad Digium T405P, configured as follows: Span 1 connects to ISDN PRI (fractional 8 B channels, D channel 24). Span 2 connects to T1 Mux and analog stations. Span 3 connects to ISDN PRI Nortel BCM hybrid key system digital trunk.
2016 Jan 05
2
Detected alarm on channel 3: Red Alarm
Humm, if I put a filter in this lines, maybe back? 2016-01-05 12:36 GMT-02:00, Ryan, Travis <RyanT at oscarwinski.com>: > >> -----Original Message----- >> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users- >> bounces at lists.digium.com] On Behalf Of Vitor Mazuco >> Sent: Tuesday, January 05, 2016 9:21 AM >> To: Asterisk Users Mailing
2016 Jan 05
3
Detected alarm on channel 3: Red Alarm
Hi everyone! I have a Digium Card TDM410 But, it appear for me this massege chan_dahdi.c:8061 handle_alarms: Detected alarm on channel 3: Red Alarm But my line is ok! But sometimes it back sig_analog.c:3807 analog_handle_init_event: Alarm cleared on channel 2 But it again back to red alarm. What can be happen? My lines is all ok! But when I put on Digium Card TDM410 is very inconsistent
2011 Jan 11
1
Issue with Red Alarm with DAhDi
Hi! I have an analog line connected to my asterisk and when I try to answer a call I get this -- Starting simple switch on 'DAHDI/7-1' -- Executing [s at from-pstn:1] Answer("DAHDI/7-1", "") in new stack -- Executing [s at from-pstn:2] Playback("DAHDI/7-1", "vm-intro") in new stack -- <DAHDI/7-1> Playing 'vm-intro' (language