similar to: help creating custom genericups configuration - RNG only!

On Jun 20, 2013, at 9:48 PM, Reed Hedges wrote: > UPSPORT=/dev/ttyS0 > > # type cablep kill t powerok battok cableok > robot --- RI 0 /RI --- --- > ? > > Is there an equivalent of ?---? in genericups? I think it's pretty much any value other than a valid

OK, I'll try "none" and see what happens. -----Original Message----- From: Charles Lepple [mailto:clepple at gmail.com] Sent: Thursday, June 20, 2013 10:14 PM To: Reed Hedges Cc: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] help creating custom genericups configuration - RNG only! On Jun 20, 2013, at 9:48 PM, Reed Hedges wrote: > UPSPORT=/dev/ttyS0 >

It look to me that overwriting UPSTYPE CP signal or polarity in ups.conf have no effect. Looking at drivers/main.c source show that &upstab[upstype].line_norm is set to custom CP in initinfo() only _AFTER_ the serial signals are actually set by upsdrv_initups().

It look to me that overwriting UPSTYPE CP signal or polarity in ups.conf have no effect. Looking at drivers/main.c source show that &upstab[upstype].line_norm is set to custom CP in initinfo() only _AFTER_ the serial signals are actually set by upsdrv_initups().

I am using nut 2.2.2 and I have a CyberPower CP550SL. According to the drivers list, I should be using genericups with upstype set to 7, but when I try that and when I run upsc I get: driver.name: genericups driver.parameter.LB: 04 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups driver.parameter.upstype: 7 driver.version: 2.2.2 driver.version.internal: 1.34 ups.mfr: CyberPower

I am using nut 2.2.2 and I have a CyberPower CP550SL. According to the drivers list, I should be using genericups with upstype set to 7, but when I try that and when I run upsc I get: driver.name: genericups driver.parameter.LB: 04 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups driver.parameter.upstype: 7 driver.version: 2.2.2 driver.version.internal: 1.34 ups.mfr: CyberPower

All, I just bought a Belkin F6C1100-UNV and am trying to get it to work with NUT. I have tried many drivers ( "belkin", "belkinunv", "genericups upstype=4", and "genericups upstype=7", "bestups", "fentonups"). None of them seem to work. Does anyone have any experience with this device? If there is some utility that you all use to

I am working with a number of our customers to ensure that NUT works with different UPS's on Freebsd 9.1. The current one I am looking is support for: *Upsonic Commercial UPS CXR 2000 - 2000VA/1200W - Rack/Tower* What seems to be supported in Freebsd is: CXR1000 blazer_ser LAN Saver 600 genericups upstype=0 Power Guardian genericups upstype=7 PrOffice 650 USB blazer_usb DS-800 USB

Hi All, I'm new to Nut and had been looking for a way of monitoring a small UPS we have just designed. We are using simple contact closure circuit, but I don't appear to be able to get the Genericups driver to work. I've followed the documentation and have decided to try the APC upstype = 1 If I type 'genericups -x upstype=1 /dev/ttys0' , I get an error: 'Fatal error:

Thx for the info Charles. Here is what I am seeing from 'usbconfig list' ugen0.1: <EHCI root HUB Intel> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.1: <EHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: <product 0x0024 vendor 0x8087> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.2: <product 0x0024 vendor

Hi everybody, I've got an Unitek iZi UPS 525 with a serial interface. The supplied cable looks fairly simple: RX->RX , TX->TX and GND->GND. Using this cable and Minicom with 2400 8N1 I'm able to issue commands to the UPS using the "Megatec Protocol" http://www.networkupstools.org/protocols/megatec.html so I know the UPS is fairly "intelligent" :-) and the

On Jan 31, 2014, at 3:14 PM, Chris Duffy wrote: > The current one I am looking is support for: > > Upsonic Commercial UPS CXR 2000 - 2000VA/1200W - Rack/Tower > > What seems to be supported in Freebsd is: Small clarification: the hardware compatibility list isn't broken down by operating system (theoretically, the drivers should work on any POSIX system, with additional

Hi Having followed this guide: http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/and seeing support for Apollo UPSes mentioned on the compatibility list (genericups, type=4) I tried to set up Nut as follows. OS: Ubuntu Server 12.04 Nut: 2.6.3 (I believe - from Ubuntu repos) ups.conf: > [apollo] > driver = genericups > upstype = 4 > port = /dev/ttyUSB0

Hi, is there a way to use my Belkin F6H650 on the USB port? I already installed usbhid-support, but neither the hidups worked (reports "/dev/usb/hiddev0 is not a UPS") nor genericups with upstype=7 and the hiddev set as device ("ioctl TIOCMSET: Invalid argument") worked. I have installed the debian sarge package of nut 2.0.1 (2.0.1-4) Regards, Philipp

Hi, I'm trying to get a sweex ups working with nut on debian sarge. This one: http://www.sweex.com/producten.php?lang=1&%20sectie=&item=59&artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl

Hello all, Some time ago, you all were very helpful in getting nut running on an OpenBSD system, using--for what it's worth--a CyberPower 1500AVR. So I finally got my FreeBSD system's UPS, also a CyberPower 1500AVR, within reach of its serial cable and I'm trying to get nut running here. I'm going nuts. Basically, I copied the OpenBSD configuration over to the FreeBSD system

Hi, Is there any way to debug a failure of NUT to shut a machine down AFTER the even occurs? (Be it a config issue {Though the standard "It hasn't changed since install" applies}, or a UPS failure, or a program failure). Its showing up (after reboot) as : valhalla# upsc robanton at localhost driver.name: genericups driver.parameter.pollinterval: 2 driver.parameter.port:

This code, added to drivers/genericups.h, supports the CyberPower SL series UPSes. I've tested with my 725SL - the online/on battery transition, and low battery status, and finally the shutdown signal all work as expected. *** genericups.h.orig Sun Nov 2 16:54:24 2003 --- genericups.h Mon Oct 3 13:49:00 2005 *************** *** 220,225 **** --- 220,234 ---- TIOCM_ST

Hello, I got this information from the manufacturer of my ups Kobian/Mercury and were tested wtih powstatd on Linux (Works OK). Now i want to configure it with NUT and i didn't have any luck (it always says OB) Initiliasation for monitoring: RTS = 1 (High) Main power fail: CTS = 0 (Low) Batter low: DCD = 0 (Low) Kill UPS: DTR = 0 (Low) How would the ups.conf look like? Reagards, Lep

On Feb 3, 2014, at 9:05 PM, Chris Duffy wrote: > Thx for the info Charles. > > Here is what I am seeing from > 'usbconfig list' [...] > ugen1.3: <USB UPS PPC> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > > > The last line I guess is key. Unfortunately, it is not very unique: the vendor can pick the string "USB UPS PPC", but the drivers