similar to: Patch #312877 - Update to belkin driver to fix datastale reports

After installing NUT, I've noticed that the belkin driver capabilities are rather basic. We have a Belkin Regulator Pro 1400VA (F6C1400-EUR), so I've updated the driver to support control of the buzzer & tests, as well as adding test result reporting. I've attached the following patches. Hopefully they can be added to any upcoming versions. -- John Bayly Systems Administrator

Hi, I've submitted a patch to the Alioth tracker but thought to give a heads up here as well, I have an issue with nut not working when the clock is moved backwards. I provided a patch[1] to use clock_gettime with CLOCK_MONOTONIC to fix this, based on comments from Charles Lepple I made a few changes and it can be seen in a git branch I created at [2]. Let me know what you think. Baruch

Julius: I just realized after committing Michal's patch that you have a more comprehensive patch on the tracker that approaches this piece of code differently. We can go ahead and apply the following patch to the trunk if you still think it's relevant: https://alioth.debian.org/tracker/index.php?func=detail&aid=303719&group_id=30602&atid=411544 If you have a newer version of

Hi Stepan, > Here are the cabling diagrams for the three most important APC UPS cables. > These are absolutely confirmed to be correct by disassembling the real APC > cables and tripple checking. Perhaps they should be posted on the NUT web > site for the benefit of other NUT users. Thanks for your contribution, queued for inclusion:

Arnaud Quette wrote: > > not sure you've seen this. It might interest you: > https://alioth.debian.org/tracker/index.php?func=detail&aid=302259&group_id=30602&atid=411544 > > Arnaud > -- > PS: I've not looked at it. Hi Arnaud, this is great! Someone posted a technical document on Alioth describing a "Delta USB Report Descriptor Protocol". This

Hi Marek, thanks for your report, forwarded to the dev list, and logged in the patch tracker: https://alioth.debian.org/tracker/index.php?func=detail&aid=303209&group_id=30602&atid=411544 thanks to also post back the ID string inside double quote to validate the exact string (use my present gmail address if you don't want to subscribe to upsdev). Arnaud -- Linux / Unix Expert -

Hi Peter, I've fwded your info to the list, as other people might be interested in. I've also logged a patch tracker so that you can follow its inclusion: https://alioth.debian.org/tracker/index.php?func=detail&aid=302882&group_id=30602&atid=411544 As a side note, there is a work underway to merge the similar driver (mustek, powermust, ...) into one named megatec. This one

Hi, Am 13.02.2012 um 18:58 schrieb Arnaud Quette: > 2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: >> Hi, > > Hi Thomas, > >> I want the driver report the battery status from ABM charging controllers >> -patch attached- : > > For now, I've tracked your patch here: >

2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: > Hi, Hi Thomas, > I want the driver report the battery status from ABM charging controllers > -patch attached- : thanks for your patch. since it introduces a new variable (battery.status.abm), I prefer to step back and think to something useful more widely. thus, I'm thinking about a generic

Hi Ted, Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: > > Note that since the UPS relies on the voltage from the battery pack to > determine state of charge, it is quite useful to add in the battery pack > voltage to the logs as such: > > --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700 > +++ upslog.c 2014-02-20 09:23:14.000000000 -0800 > @@ -50,6 +50,7

I've a Belkin Regulator Pro (F6C1400-EUR) connected via serial to a FreeBSD machine using NUT v.2.4.3 Sometimes I get a series of logged messages saying that the data is switching between stale and valid, this in itself isn't an issue, however occasionally when the communication is re-established, upsmon gets a "On battery" message followed quickly by "Battery low"

I've discovered an issue (which may be unique to my UPS) with this commit. init_communication now returns -1, instead of 0 if it failed to read the manufacturer info, this makes sense after all. With my UPS (Belkin F6C1400-EUR), the response to the Manufacturer command returns only 6 spaces (rather than "BELKIN"), this means that init_communications fails, and the driver fails

Are there any plans to allow us to specify UPS variables in ups.conf, eg: [evo_s_3000] driver = usbhid-ups port = auto desc = "Eaton Evolution S 3000" vendorid = 0463 productid = ffff ups.delay.shutdown = 120 ups.delay.start = 130 The reason I ask is that I'm using FreeBSD & gmirror and need to extend the gracetime

OK, I asked this about a week back and met with no repsonse at all. But perhaps its worth trying again. Does anyone on-list have * running BRI to their local telco? I'm considering this as an alternative to my TDM400p card. Michael -- Michael Graves mgraves@pixelpower.com Sr. Product Specialist www.pixelpower.com Pixel Power Inc.

THANKYOUTHANKYOUTHANKYOUTHANKYOU!!!!!! There was a smaller patch posted to the list for lines -1389,9 +1390,10 a couple years ago, it helped some - BUT - it was still buggy. I have a Compaq R3000, I will get this patch integrated pronto and test Note that since the UPS relies on the voltage from the battery pack to determine state of charge, it is quite useful to add in the battery pack

Hi I'm sending this to you as it appears that you are the person who looks after and/or supervises the code for NUT's Belkin drivers. I'm using the address you use for the Nut-upsdev mailing list ( selinger at mathstat.dal.ca ). Anyway... I have a Belkin Universal UPS and, having just upgraded my Fedora Core system from 4 to 5 and had to go back through the system RC files

Hi all, I'm not sure wether it is a bug or not, so I'm asking for your opinion before submitting it to the bugtracker. The problem: I use asterisk with in sip.conf a non standard bind port of 5070 set. Now when asterisk sends out an Invite message to my sip proxy, the contact header in de request is something like: Contact: <sip:12329123 at 123.123.123.123> The call succeeds and

I have been using Tinn-R with R without any problems but when I try to use it with REvolution R I get the following error message when Tinn-R runs the configuration script and gets to the trDDEInstall() function: ## Start DDE trDDEInstall() > trDDEInstall() Error in structure(.External("dotTcl", ..., PACKAGE = "tcltk"), class = "tclObj") : [tcl] invalid command

Hi there, (context: I was optimizing Roundcube mailbox list server response, and in that 300-400ms response time, around 170ms is spent on single fgets() call which is waiting IMAP repsonse to "SELECT MyMailbox" command) I straced dovecot and of the whole request/response process, around 30ms is spent for everything else, and overwhelming majority of time (150-170ms) is spent for

Hello, > upsmon doesn't work on amd64. > On i686 everything is OK. Configs are the same. > I'm attaching strace - could You help? this might be linked to that: https://alioth.debian.org/tracker/index.php?func=detail&aid=301880&group_id=30602&atid=411544 when you say work", can you give a bit of detail (ie doesn't receive events, crash (seems not as per