search for: ganze

Arnaud, > first, even if your battery is full, and your ups is online, there is a > small amount of power drawn. So having always is CHRG status is normal. > In fact, these complementary status are more interesting for higher end > UPSs. > > second, these status need not to be handled like LB, as each one clears the > other. While LB had no pending event (!LB) before... >

Peter, You may want to have a look at the comments to Bug 164524 at bugzilla@redhat.com: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=164524 I filed this a long while ago, because of the mess we get into when shutting down Linux via /etc/rc.d/init.d/halt, and the UPS device no longer being reachable when we want shut it down. There seem to be some changes to libusb on the way, that

Ladies and Gentlemen, I have been playing around with Arnaud's new HAL stuff a bit, and have some questions and observations. First my configuration: my UPS (Peter may remember): ups.mfr: APC ups.model: Back-UPS ES 650 ups.productid: 0002 ups.firmware: 818.w1.D ups.firmware.aux: w1 kernel: 2.6.18-92.1.6.el5 hal-0.5.8.1-35.el5, nut based on nut-2.2.2.tar.gz, small changes to

Ladies and Gentlemen, I have been trying to sort out a nasty kernel oops for which I would like to ask for some advice. I don't actually think that this is a nut problem, although it is triggered by upsdrvctl or usbhid-ups. I rather suspect the USB library or the associated kernel code. Here is the configuration information: * system: Centos-5.5 * kernel: 2.6.18-194.32.1.el5, latest vanilla

Gentlemen, I have now had a chance to run some initial tests of my changes to apc-hid.c of the current development tree. Running newhipups and inspecting the -DDDD output seems to indicate that with the fix below everything seems to work as expected. However, I have not yet shut my system in order to take the UPS out of action so that I can do my various tests with a lightbulb load. I still hope

Thomas, The none (-22) message in your log is an errno from the libusb_get_interrupt() call in HIDGetEvents() in libhid.c. It indicates an invalid ioctl type. In HIDGetEvents() there is a comment with that call: /* needs libusb-0.1.8 to work => use ifdef and autoconf */ You may want to make sure your libusb is up-to-date. Hope this helps, AG --

Charles, When sorting out the library problem for shutdown, please also keep in mind that the shutdown scripts (at least those that I have encountered so far) insist on unmounting /dev/usb. This requires that libusb does not rely on its presence to do the reconnection for the shutdown. I don't know if this is a part of the definition of the functionality of libusb and if it can safely be

Hello, I'm currently try to get newhidups running with the newhidups driver from nut 2.0.2. After some USB issues (usb_claim_interface() works only as root so far) newhidups is recognizing the device. Though it doesn't detect any state changes, meaning when I run the battery test mode it's not recognized. I wanted to try the CVS version but it seems anonymous CVS is broken. The

Peter, Just to let you know that I have done all my tests with the latest development stuff (Oct 3 23:46 to be specific, with NO local patches!), and everything turned out fine except for the cleaning up of ups.status: as presented by upsc that I reported earlier. I suspect that that cleanup is generic to newhidups, because a couple of month ago Arnaud made some changes for cleaning up LB

Peter, Thanks a lot for your latest changes to newhidups, which I like a lot. Unfortunately, when I tried to build the latest development tree stuff, I got a compile time error when compiling al175.c. It looks to me like my compiler, gcc-3.4.4-2.fc3, doesn't like the macro definition for "RECV(reg) do" because of a poorly inserted comment. I fixed the problem locally by the

Peter, Here are the transitions that I have tested with your latest changes (on the APC/Back-UPS ES 650): 1) OL ==> OB DISCHRG followed by OB DISCHRG ==> OL (no CHRG inbetween) 2) OL CHRG ==> OL 3) OL CHRG ==> OL CHRG LB (by manipulating battery.charge.low) 4) OL CHRG LB ==> OL CHRG (i.e. transition from below) 5) OB DISCHRG ==> FSD OB DISCHRG LB followed by proper shutdown In

Hi all, I hope this isn't a naive newbie question again. Here you can see column 264 of a data frame containing data of the same interview in May and September. Column 264 contains the answers of 49 persons to a question in May. > fbhint.spss1[,264] [1] teils/teils sehr wichtig <NA> <NA> sehr wichtig [6] sehr wichtig sehr wichtig sehr wichtig <NA>

ich hätte ein problem: im rahmen meiner projektarbeit stehe ich vor der aufgabe, einen beliebigen datensatzt einzulesen, die empirische verteilungsfunktion des datensatztes zu zeichnen, aber das ganze so, dass die y-achse nach der quantilsfunktion der exponetialverteilung mit parameter=1 transformiert werden soll! leider steh ich da jetzt wirklich an! würde mich serh freuen, wenn mir jemand weiterhelfen könnte, mit herzlichem dank, reka [[alternative HTML version deleted]]

In an earlier message Arnaud wrote: > before digging further, you'll have to make some test to > see if the data changes upon status change. > libhid is your friend, especially test_libhid. You'll have > to modify it a bit to get the values of the below path I just got the CVS tree, but I didn't find test_libhid, but it looks like this would indeed be what I would like to

Gentlemen, I am making progress with with my APC USB device. However, I have encountered a problem with the current build for newhidups. The problem is that on my system libusb.so resides in /usr/lib, which at the end of the shutdown sequence is no longer available. I believe that this is probably a relatively generic problem, and I think that the proper solution is to link all usb drivers

Gentlemee, I have just encountered a problem with low battery status in newhidups. Here is the situation: 1) The system goes through the shutdown sequence due to low battery, the UPS receives the shutdown.return and shuts off power, 2) After power returns, the UPS turns on power before its battery reserves have reached low battery level (a potentially risky situation if we get another

Gentlemen, On several occasions now I would have liked to start a complete set of (newhidups + upsd + upsmon) in the background, but with significantly more output to syslog. From a cursory look at the code, it looks to me that it might be easy to add an option similar to -D that doesn't stop putting the process into the background. I understand that higher levels of debug would create a

Gentlemen, I have determined that on my UPS (APC Back-UPS ES 650 FW:818.w1.D USB FW:w1), the variable UPS.PowerSummary.RemainingCapacityLimit is writeable. I am setting this variable to start shutdown a little earlier. Appended is an unconditional patch for apc-hid.h. If, as indicated by the original code, there are APC UPS devices that don't allow setting of this variable, it becomes

Gentlemen, I assume this is really for Arnaud: I am looking at the code in upsdrv_updateinfo() where it is processing a HID notification, i.e. it is not doing a full update: Question one, is it implicitely assumed that ups.status related items will always require a translation (i.e. item->hid2info != NULL) in order to be effective? I haven't seen any place where that is enforced, but

Gentlemen, I am using upsmon, upsd, and newhidups to control my UPS. The UPS allows setting of two variables that are re-initialized to their default values whenever the UPS is restarted (e.g. after FSD). I am currently using upsrw in a startup script to set the above variables. This works fine, except that it requires -u and -p in the commandline, which I don't like to do, because I