similar to: driver for Elite 2005 500VA

Hi, I recently bought a Nitram Elite 2005 UPS and i installed nut to monitor it. Unfortunatly, i often have timeout errors (20 timeout per days): Broadcast Message from aurelien at berkelium (no tty) at 18:05 CET... Communications with UPS Nitram at localhost lost Broadcast Message from aurelien at berkelium (no tty) at 18:05 CET... Communications with UPS Nitram(AT)localhost

Hi, I recently bought a Nitram Elite 2005 UPS and i installed nut to monitor it. Unfortunatly, i often have timeout errors (20 timeout per days): Broadcast Message from aurelien at berkelium (no tty) at 18:05 CET... Communications with UPS Nitram at localhost lost Broadcast Message from aurelien at berkelium (no tty) at 18:05 CET... Communications with UPS Nitram(AT)localhost

Arjen de Korte wrote: > Author: adkorte-guest > Date: Mon Nov 5 20:24:00 2007 > New Revision: 1154 > > Log: > Added experimental flag to this driver because it lacks support to shutdown the UPS. Now is a good time I to think about the 'experimental' flag. What level of support should a driver have, to warrant removal of that flag (apparently, the 'nitram'

Debian sid package v. 2.6.4-2.3 UPS nitram elite 2002 700VA (serial port) MOBO A7V8X-X ================================ Hi list, Everything work fine, except after an AC supply shortage: the UPS don't come back to a normal behavior, it stays on battery (of course, it works right w/o any cable). Is there something I can do recover a normal behavior? JY -- Too much of a good thing is

I've just noticed that cpsups isn't listed anymore in driver.list. Any reason not have removed it from the source too? Still on the way to 2.4; any update on your confidence level to remove nitram and cyberpower too? -- Arnaud

Arjen, I read the following in the upgrade notes and just wanted to see what the status was for the cyberpower driver? The note reads: - The cpsups and nitram drivers have been replaced by the powerpanel driver, and removed from the tree. The cyberpower driver may suffer the same in the future. What does this mean to me -- a cyberpower user? -- David C. Rankin, J.D.,P.E. Rankin Law

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

While working on the mge-hid subdriver, I wanted to add the 'beeper.mute' command. Unfortunately, the description I intended to use was used already by the 'beeper.off' instcmd: CMDDESC beeper.off "Temporarily mute the UPS beeper" Now of course we could add another instcmd 'beeper.reallyoff', but instead I would prefer to bite the buller and do the following:

I'm looking for people that are using the 'cyberpower' driver that has been available for some years now. It seems the overhauled 'powerpanel' driver could support your UPS too. The commands and status bytes used are identical, the only difference being the way the values read for battery charge, temperature and frequency are interpreted. If we can find a way to detect when to

I'm looking for people that are using the 'cyberpower' driver that has been available for some years now. It seems the overhauled 'powerpanel' driver could support your UPS too. The commands and status bytes used are identical, the only difference being the way the values read for battery charge, temperature and frequency are interpreted. If we can find a way to detect when to

I finally took some time to lay down a consolidated roadmap to the next major milestone (2.4), and some update on this. 1) new documentation (User and Developer Manuals) -------------------------------------------------------------------------------------- This is the biggest change for 2.4. We will use the new test.networkupstools.org website to create and maintain the content, based upon the

Arjan, I am forwarding your email to the nut-upsuser mailing list. I am not an expert on the Powermust driver; hopefully somebody on the mailing list will be able to help you! -- Peter Arjan DJ wrote: > > Dear Peter, > Some days ago I bought a Sweex UPS (500VA) and now I have set up NUT (using > the Powermust driver) and everything is working fine. Invoking upsmon -c fsd > gives

Hi, FYI for all whom have the Sweex manageable UPS. I got my sweex manageable UPS500VA working with NetworkUPSTools using the ippon driver. Here is my the ups.conf file: [ups] driver = ippon port = /dev/cuad0 desc = "Server" Has anyone tried the ippon driver with Sweex 600VA, 700VA, and 800VA models? Regards, Jan

Syndome Era Series *upsc output* * *battery.charge: 100 battery.runtime: 1000 <-- not reported by UPS (guesstimate) battery.voltage: 13.60 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.type: ups driver.flag.novendor: enabled driver.name: blazer_usb driver.parameter.chargetime: 43200 driver.parameter.idleload: 30 driver.parameter.pollinterval: 5

Hi all, First off thanks you for such a great tool - my searching so far indicates that the developers and community behind nut are committed and doing a great job! Background: I've just purchased a Plexus 500VA UPS for ebuyer because it was cheap. I didnt expect much but I've seen a few references to people getting the same and similar models to work with NUT so was encouraged to try!

Hello all, I'm having problems getting chan_capi 0.3.5 to work well with an Eicon Diva Server card using using the driver from linux kernel both 2.6.10 and 2.6.12 (vanilla versions). I have a (really two) producci?n system(s) running chan_capi in another identical Eicon Card using kernel 2.4.27 and the Diva Server drivers from Eicon. I installed an compiled the source level rpm

On Jun 7, 2017, at 12:54 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > > Hi, I have tried several drivers for make my Elite UPS working. > With blazer_usb I can contact it, but I have no informations. This is the best result. > > OS: Ubuntu Xenial 16.04.2 LTS > NUT Version: Nut 2.7.2-4Ubuntu1 (Installed from Ubuntu Software Center) > Device name: Elite UPS

On Jun 8, 2017, at 9:15 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > Thank you for your reply Charles, > this is the "upsc" result: > > root at artu:~# upsc ups at localhost > Init SSL without certificate database > Error: Unknown UPS > Use the name from ups.conf in front of "@localhost". > Trying with nutdrv_qx, protocol megatec

> root at artu:~# /lib/nut/nutdrv_qx -a Elit -u nut -DDDDD > Network UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2) > USB communication driver 0.32 > 0.000000 debug level is '5' ... > 0.574759 send: Q1 > 0.807418 received 46 (40) > 0.807475 read: (225.3 140.0 222.6 015 49.9 13.8 30.0 00001001 > 0.807516 qx_process_answer:

> Starting the driver with debug level 5 seems happier, but continue to cycle It is meant to 'cycle', it's working correctly. When you run the driver normally (i.e. not in debug mode), you don't see all that output (plus, after having established a connection with the device, the driver goes into the background), but it's doing exactly the same thing. > nutdrv_qx....