search for: tipstrad

...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 ------------------ TipsTrade Ltd. 16 Wornal Park, Menmarsh Road, Worminghall, Bucks. HP18 9JX T: +44 (0)1844 337 326 (Direct) M: +44 (0)7787 727 934 F: +44 (0)1844 337 337 E: john.bayly at tipstrade.net E-Mail Disclaimer Whilst TipsTrade Ltd. believes that the information is correct at the date of this e-mail, no warranty...

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

I've patched the belkin driver to add the test commands & beeper control, as well as reporting the beeper and test status. I've submitted them to the nut-upsdev list, but haven't heard anything back. Is there a place or person I can contact to submit changes to? Thanks, John

We're looking at supplementing our Belkin Regulator Pro 1400 with a 2nd UPS, and were contemplating the APC's 3kVA Smart UPS LCD. We'd still be using either our existing FreeBSD box or a CentOS box to control the UPS. I was just wondering if anyone's got much experience with using these with NUT. From the NUT compatibility guide, it says it uses the usb-hid driver. It also

In repsonse to the problem with "Belkin Regulator Pro dropping connection and halting" in ups-users, I've submitted the patch to help with the issue: https://alioth.debian.org/tracker/index.php?func=detail&aid=312877&group_id=30602&atid=411544 I didn't have any reports of people's eyes bleeding from reading the code, and it's been doing the job quite

On 14/01/2011 20:40, Arnaud Quette wrote: > Author: aquette > Date: Fri Jan 14 20:40:06 2011 > New Revision: 2832 > URL: http://trac.networkupstools.org/projects/nut/changeset/2832 > > +link:http://www.networkupstools.org/source/2.6/nut-2.6.0.tar.gz.sig[signature] May I suggest that you also provide checksums for the tarball? I'm updating the FreeBSD port, and wanted to

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"