Re: [Nut-upsuser] Can't get iDowell to work
Citeren Charles Lepple clep...@gmail.com: Technically, HID only needs to be specified on the interface class (device class can be 0), so this descriptor is correct in that regard. If the device is auto detected by Windows and Apple, it is quite possible that this is indeed a HID PDC device. Not sure why it didn't match, though... That's pretty obvious. No subdriver supports this VID:PID combination, so you'll get no match for any of them. What Kjell forgot to mention is that Mick will need to add the 'explore' flag to 'ups.conf' (see 'man 8 usbhid-ups'), so that at least we'll get some debugging output. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS
Hi Michael Hatzakis Jr 2011/1/2 Michael Hatzakis Jr m...@hatzakis.net Arnaud Quette, I have read in depth your page regarding APC UPS programming. I hope you don’t mind taking a moment to assist me. I see that Russel Kroll has long since retired. I read your APC smart protocol page as well as that of Jjoseph, http://www.jjoseph.org/notes/apc_smartups_battery_float_voltage regarding programming the APC SU2200 and SU1500. In particular, I am interested in the use of the battery gain control, B + and B – commands to reduce or increase the battery voltage by changing the gain setting. What is interesting to me is that in reading multiple posts and sites, on some unit, this changes the battery control voltage and in others, it changes only the read voltage of the A/D converter. I tried this on my APC SU2200XL and changing the gain, actually, changed the read voltage only, and did not change the real voltage on the output of the battery terminals. Appears opposite what yours and Joseph’s page suggests for the SUA1500 but similar to that of the SU700. My bottom line is that I need to reduce my float voltage as it is now at 56volts, too high for a float and will ultimately damage my new batteries. Do you have any insight on how to reduce the output voltage, NOT, just what the unit reads? Do you have any insight on the inconsistency of the B command on various UPS? I have personally no insight on these units, have never worked on this driver (apart from applying trivial patches) and have no clue on the serial protocol. so your best bet is to subscribe to the NUT user mailing list, and start (continue!) a discussion on this topic. cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next size (fast):
0x012c9870 ***
Can you give us some background information about this system? What OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided package, or
something from another package repository? Which version of Ubuntu?
Running valgrind might produce similarly opaque results without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and others if needed
otherwise...
That is a bit
more involved, though (especially if you want to keep the installed
files in the same place) so I'd try that after Arjen's suggestion with
-DDD.
seconded for a first run.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NetworkUPS tools Compatibility update
2011/1/4 Among The Living stinkysmelly...@gmail.com battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 3600 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 20.2 battery.voltage.nominal: 12 driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.2 driver.version.data: CyberPower HID 0.1 driver.version.internal: 0.33 input.transfer.high: 140 input.transfer.low: 90 input.voltage: 117.0 input.voltage.nominal: 120 output.voltage: 117.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 10 ups.mfr: CPS ups.model: UPS RF1025 ups.productid: 0501 ups.realpower.nominal: 88 ups.status: OL ups.timer.shutdown: -60 ups.timer.start: 0 ups.vendorid: 0764 fine, thanks. I've just commited your entry (r2799). I missed to ask: have you tested low battery condition too? ie http://new.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Testing_shutdowns I just double checked, the vendorid is in fact cyberpower, one question? :) If the vendorid is actually derived from the device and not computed, you should let users know to cross reference the vendorid against an online database (if you haven't already). Totally didn't occur to me until I was talking with a friend today :) well, 2.8 work around user interface (not only graphical!) to detect (when possible), configure, test and monitor your devices will greatly improve the situation. many pieces of this are already in place. so 2.8.0 should be there quite quickly. On Mon, Jan 3, 2011 at 3:43 PM, Arnaud Quette arnaud.que...@free.fr wrote: Hi James, 2011/1/1 Among The Living stinkysmelly...@gmail.com Hey there, After a few hours with tampering I got my UPS up and running. It's a RocketFish 1025/1000va (The model varies and is listed as 1000va as well as 1025va). I got it working with the usbhid-ups driver, which I guess is a no brainer :P. Just figured I'd let you know. This product (As I found out by using good ole google cache on gentoos forums), is just a rebrand of CyberPower's UPS's. thanks for your report. can you please post an upsc output, so that we can validate that everything cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
Citeren Mick michaelkintz...@gmail.com: [ snip ] 0.171361 refresh_report_buffer: expected 4 bytes, but got 8 instead 0.171403 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x11, Offset: 0, Size: 24, Value: 0.00 0.171446 Report descriptor retrieved (Reportlen = 412) 0.171461 Found HID device 0.171475 Detected a UPS: iDowell/iBox 0.171490 find_nut_info: unknown info type: load.off.delay 0.171503 find_nut_info: unknown info type: load.on.delay 0.171515 find_nut_info: unknown info type: load.off.delay 0.171542 upsdrv_initinfo... 0.171574 upsdrv_updateinfo... 0.186562 Got 10 HID objects... [snip ...] This keeps going on and on, so I attach the rest as a zipped file to keep the noise down. We probably should have warned you that we only need the first thirty seconds worth of output. Nevertheless, this device indeed speaks HID PDC, so it should be trivial to add this to the usbhid-ups driver. I don't recognize a familiar subset/pattern of commands, so I guess this warrants adding a new subdriver. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
On Tuesday 04 January 2011 20:46:26 Arjen de Korte wrote: Citeren Mick michaelkintz...@gmail.com: [ snip ] 0.171361 refresh_report_buffer: expected 4 bytes, but got 8 instead 0.171403 Path: UPS.PowerSummary.DelayBeforeStartup, Type: Feature, ReportID: 0x11, Offset: 0, Size: 24, Value: 0.00 0.171446 Report descriptor retrieved (Reportlen = 412) 0.171461 Found HID device 0.171475 Detected a UPS: iDowell/iBox 0.171490 find_nut_info: unknown info type: load.off.delay 0.171503 find_nut_info: unknown info type: load.on.delay 0.171515 find_nut_info: unknown info type: load.off.delay 0.171542 upsdrv_initinfo... 0.171574 upsdrv_updateinfo... 0.186562 Got 10 HID objects... [snip ...] This keeps going on and on, so I attach the rest as a zipped file to keep the noise down. We probably should have warned you that we only need the first thirty seconds worth of output. Nevertheless, this device indeed speaks HID PDC, so it should be trivial to add this to the usbhid-ups driver. I don't recognize a familiar subset/pattern of commands, so I guess this warrants adding a new subdriver. Thank you guys! :-) Please let me know if you need anything more from me. -- Regards, Mick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
