similar to: HCL <FSP> <Champ Tower 1k> supported by <blazer_usb>

Hi ups-devel, As I looked throw www.networkupstools.org site, haven't found any pointers where to send patches, so I hope this is the right place. (Please let me know weather this is the right place.) The patch contains a minor change in the logic of the driver, our Effekta MHD 3000 UPS continuously writes status data to the serial port, so one has to send a CR character and empty the

Hi all RESTORATION of POWER I seem to have cabling & drivers set up correctly for a contact closure UPS ............as below the logs should indicate that. BUT .......... But after power Restoration between commencement of (shutdown -h +20) ....... & execution of (shutdown -h +20) during the 20 minute wait period of shutdown or whatever the "time" variable is.

Hi There, i have a strange problem with a fenton powerpal 660. When you switch off the power to the UPS (from the wall), the server (IBM xSeries 203) attached to it dies...However, if you unplug the cable from the server to the UPS and plug it back in again (with the power still out to the UPS), the server starts up again (set to power up after a power failure) and runs with no issues. I have

Hi there Would anybody happen to know the correct driver for a Fenton Powerpal S series? upsdrvctl reports: Network UPS Tools - UPS driver controller 1.2.2 Network UPS Tools - Fenton UPS driver 0.90 (1.2.2) Unknown ups - please report this ID string: #FENTON S Series V4.04EG503 Detected Unknown Series on /dev/ttyS0 Alternatively, does anyone know if the manufacturer is likely to

Hi There, Running on debian sarge. This was working a while ago, but here goes.. When viewing the upsstats.cgi page, im getting a message "Not Supported" in the Model column with a "ONLINE" message, but no other stats. Here is the syslog when booting nut: Oct 15 14:28:40 mx1 upsmon[4835]: Signal 15: exiting Oct 15 14:28:40 mx1 upsmon[4834]: upsmon parent: read: Success Oct

Hi, I have a Fenton Powerpal L660, when I try and configure nut with either the metatec or fentonups driver, and start upsd, the UPS instantly turns itself off. It used to work, until I changed my motherboard and CPU, which means it has a different bios and serial port setup. This is happening with Nut 2.0.1 and also Nut 2.0.5. I have an AMD64 bit processor, Mandriva 2007 64 bit. Any

Gidday all - I'm a new user to nut. I've got some cheap powerpal UPSs working fairly well. However I also have a new Dynamix UPS-1700D and an old Powercom KIN-1700 something unit that I cannot make work right. The best method I've found is "trial and error" which sounds a bit last-resort. Is there any better way to find out what protocol is used? -- Criggie

2007/2/19, Glen Ogilvie <nelg@linuxsolutions.co.nz>: > Hi, > > I have a Fenton Powerpal L660, when I try and configure nut with either the > metatec or fentonups driver, and start upsd, the UPS instantly turns itself > off. > > It used to work, until I changed my motherboard and CPU, which means it has > a different bios and serial port setup. > > This is

2007/2/19, Glen Ogilvie <nelg@linuxsolutions.co.nz>: > Hi, > > I have a Fenton Powerpal L660, when I try and configure nut with either the > metatec or fentonups driver, and start upsd, the UPS instantly turns itself > off. > > It used to work, until I changed my motherboard and CPU, which means it has > a different bios and serial port setup. > > This is

Hi all... I've tested my installation and everything seems OK, but I'll note a couple of things. System is debian, UPS is Fenton Powerpal 660 L First of all, the ups software did not restart because I had not changed 'no' to 'yes' in /etc/default/nut. Maybe it's a debian thing, I don't know. But I don't remember seeing it noted anywhere in nut docs.

Hi Henning, you should get in touch with Carlos, who his developing a generic megatec driver (available from svn: http://eu1.networkupstools.org/source.html) Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer -

Hi David As per the link http://www.llondel.org/ups.shtml & the final testing paragraph. I have set up a Lantech UPS similiar to your write up for your Powersure Proactive and Powersure Personal UPS's On LOW BATT it shuts down OK. BUT as with other many UPS's during the wait period from low batt to start of shutdown ... IE [SHUTDOWNCMD "/sbin/shutdown -h +20"]

Hi! Using this guide: http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/ and systematically testing the usb capable driver on your site I managed to get my FSP EP650 (by http://www.fspgroupusa.com/ ) working (after reboot). Im running Ubuntu 9.10 desktop x64 standard install. This is the output from running "upsc ups1" ----- battery.voltage: 13.50

Am Trying to use nut (2.2.0 - on an SMEServer V8 aka Centos 5.5) on the above UPS, I've tried the megatec driver in serial and USB mode (the device has both types of connection), but no success. An Example: [root at mailserver ~]# megatec_usb -a UPS -DDDDDDDD Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport

Hi all, I've bought UPS FSP EP 850 because I have similar UPS, FSP EP 1000. It is working on my other server with with Fedora 14, kernel 2.6.35.14-106.fc14.x86_64 and installed nut-2.6.2-1. My new UPS is detected by kernel (see below lsusb output) and is partially detected by blazer_usb driver also. But it doesn't communicate with driver (see below blazer_usb output). I run all

Hey everyone, I'm trying to get Sim Tower (ya...old game lol) to run in wine. andi t installs more or less untill the end, where it says something about "Unable to start DDE communication with Program Manager" and i can either abort, retry or ignore. retry just goes in a loop, and the others do as they should. When i click ignore a bunch of times, it finally says "installation

On Feb 5, 2014, at 10:12 AM, Chris Duffy wrote: > However, we are using NUT 2.6.5. > > Are we missing something by running 2.6.5 rather then > 2.7.1? If so, I can build/install 2.7.1. Well, 2.6.5 is from August 2012, so it's not the newest. And eventually, we would like people to switch to the shiny new nutdrv_qx driver which is in 2.7.1. But I'm pretty much guessing here

Thanks to Kevin and Paul for responses. We use a modified Tower of Hanoi scheme (on top of rsync and --link-dest and recycling) for deciding which backups to keep. Here is a sample of our holdings for one area: home.20111124.seq.0 set 0 home.20130512.seq.512 set 10 home.20140203.seq.768 set 9 home.20140414.seq.832 set 7 home.20140708.seq.896 set 8 home.20140815.seq.928 set 6

Charles, here is the command(s) output using uhidd.... # uhidd -v -u /dev/ugen1.3ugen1.3[0]-> HID interface ugen1.3[0]-> Report descriptor size = 27 ugen1.3[0]-> Kernel driver is active ugen1.3[0]-> kernel driver detached! ugen1.3[0]-> Find IN interrupt ep: 0x81 packet_size=0x8 # /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -DDDD 0.000000 debug level is

On Feb 5, 2014, at 9:03 PM, Chris Duffy wrote: >> Please run this: >> >> /usr/local/libexec/nut/blazer_usb -a UPSonic -u root -D >> >> and send the output back to the list. >> > Output from the above command: > > 0.000000 debug level is '1' > 0.248714 Supported UPS detected with megatec protocol > 1.268575