search for: nitram

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...

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...

Hello, I've just finish a new driver for the Nitram UPS Elite 2005 500VA (compiled and tested with nut-2.0.1 and nut-2.1.0). Currently, all Nitram UPS are made by CyberPower, but the protocol is different than cyberpower.c. I don't have other model to test with, but I think this driver could monitor all Nitram 2005 UPS. I don't have the...

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 n...

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

Is anyone working on anything to support the Cyberpower CP550SL/AE550 Serial? Any idea if it uses the same or similar protocol as the other Cyberpower models? I have an HP 4952A Serial Protocol Analyzer and a Cyberpower CP550SL. Once I get the CP550SL up and working in Windows over RS232 I'll hook up the 4952A and see whats going on. I'm not sure what it uses for default baud rate.

...7 > 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' driver never had this)? At the very least, I think it must be able to reliably detect OL, OB and LB states and be able to shutdown the UPS in such a way that it will restart when the power comes back. The latter is so vital in unattended operation, that this should be a requirement. Any thoug...

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 Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Teleph...

...ibly add a real 'beeper.off' command. It looks to me that the HID subdrivers should support that (value=1) and the belkinuniv driver too. Of course this will have consequences for drivers that already implement this command: apc-hid belkin-hid belkinunv energizerups metasys mge-hid nitram powerpanel safenet tripplite-hid upscode2 Any thoughts? Best regards, Arjen

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

...king copy) @@ -100,7 +100,7 @@ void upsdrv_banner(void) { printf("Network UPS Tools - %s %s (%s)\n", - DRIVER_NAME, DRIVER_VERSION, UPS_VERSION); + DRIVER_NAME, DRIVER_VERSION, upsversion()); } /* --------------------------------------------------------------- */ Index: drivers/nitram.c =================================================================== --- drivers/nitram.c (revision 916) +++ drivers/nitram.c (working copy) @@ -328,7 +328,7 @@ void upsdrv_banner(void) { printf("Network UPS Tools - Nitram UPS driver %s (%s)\n\n", - DRV_VERSION, UPS_VERSION); + DRV...

I've solved the detached-branch problem! It wasn't actually the branch-rename overwrites that were doing this - turns out I was trying to remove cvs2svn-generated junk commits too soon and in the process deleting critical branch links. I've uploaded a new tarball to http://www.catb.org/esr/nut-conversion/nut-conversion.tar.gz with the 2.0-pre3 version of reposurgeon in it. That

...now) and when we need to map them in some weird way (the existing 'cyberpower' driver), we have a single driver for all CyberPower equipment with a serial connection (binary and text protocol). From a user (support) perspective, this is much better than the four drivers (cyberpower, cpsups, nitram and powerpanel) we have now for CyberPower UPSes. This might be as simple as looking at the firmware revision, or maybe we need something more sophisticated. In order to find that out, I would like to see the output from 'upsc <upsname>' for both the 'cyberpower' and 'pow...

...now) and when we need to map them in some weird way (the existing 'cyberpower' driver), we have a single driver for all CyberPower equipment with a serial connection (binary and text protocol). From a user (support) perspective, this is much better than the four drivers (cyberpower, cpsups, nitram and powerpanel) we have now for CyberPower UPSes. This might be as simple as looking at the firmware revision, or maybe we need something more sophisticated. In order to find that out, I would like to see the output from 'upsc <upsname>' for both the 'cyberpower' and 'pow...

Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with

...me, point the driver maintainer, ...) The result of this can already be watched in the branches/trunk-upsdrv-info-struct - unified sec/gamatronic driver: Julius and Nadav, I hope you're reading ;-) - newmge-shut completion and takeover (old mge-shut removal) - powerpanel takeover (cpsups, nitram, cyberpower removal) - "-p" probe flag: break after upsdrv_initinfo() printing the "Detected..." message. This will be useful for configuration tools essentially. 4) The sandbox ------------------------- These are various points that need investigation. Some will enter 2.4, ot...

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

Hi all! The following files emits warnings when compiled with gcc 4.0: al175.c bcmxcp_ser.c belkinunv.c cyberpower.c everups.c powercom.c solis.c All warnings seem to be of this variety: everups.c:38: warning: pointer targets in passing argument 2 of 'ser_get_char' differ in signedness I suggest that those who fiddles with those drivers fixes the warnings and verifies that it works

...The first problem I found was having no response when making a call in 2.6.12. After searching the list I downgraded to 2.6.10 and I was able to made a call. Then I found the patch(es) in the comments at "Asterisk How to connect with CAPI" at voip-info.org. I'm using the one from nitram that seems very similar to the one from irroot but more complete. With this patch chan_capi is mostly working with 2.6.12 but I have some problems I don't have with Eicon's driver in 2.4.27. And the same synthoms occur both with 2.6.12 or 2.6.10. The worst first: 1- When I made a cal...