similar to: Commanding the UPS on and off

I'm doing testing of the UPS-side code, including being able to tell the UPS to shutdown and then come back up after a while (if power has returned). I'm trying to use upscmd so that I don't have to do an actual shutdown, but when I have it list the commands for my UPS, I just see 4 commands, and they're not the ones I thought I had specified. load.on load.off shutdown.return

Hi Rob I still have an unset draft answer to your previous mail... but you seem to have progressed... 2015-03-20 16:32 GMT+01:00 Rob Groner <rgroner at rtd.com>: > I?m doing testing of the UPS-side code, including being able to tell the > UPS to shutdown and then come back up after a while (if power has returned). > > > > I?m trying to use upscmd so that I don?t have to

>>I still have an unset draft answer to your previous mail... but you seem to have progressed... Heh?that?s been known to happen. ? I have the luxury of relatively un-interrupted development on this project, so it goes a lot faster now. Hopefully that lasts? >>>Could you please check if "usbhid-ups -D ..." does list the above HID data

I'm probably spending WAY too much time on this question, but.... If the goal is just to perform a clean shutdown, and the power might cycle a few more times before coming back completely, then shutdown.stayoff might make more sense. A human could come along and manually power it back on. ...by plugging the PC into a new power source? Because the UPS outlet would be shut off, so hitting the

Ok, so the reason I keep asking about this is in case I have to actually implement this in our UPS. I meant that a human could power the UPS back on. Nearly all of the UPSes I have worked on have momentary power buttons (either toggle on/off, or a pair of on and off buttons). So, when a power-off-stay-off comes through, then the UPS *itself* shuts down as well, and essentially goes into a

Thanks again Tim. I installed openSUSE from scratch, without installing libusb anything. I tried configure, and it failed because it couldn't find libusb. I used ldconfig to see what the system could see. It found 3 entries with "libusb" in them. I then built and installed the last update of libusb-0.1 (not libusb-compat or libusb-1.0). I tried configure, and it ran without

Faster than I expected, I've become somewhat disenchanted by the openups-usb driver. So, if I write my own subdriver for our UPS...how quickly can I expect that it will be incorporated in some downloadable version of nut that a user can then use? The main reason I ask is because I have to include a guide for getting the UPS to work in Linux. If I can simply stipulate that they have to

The "#! <shell>" is a *nix thing that exists in every *nix I have ever seen, for as long as I know (mid 1980's for me . . ) and is used to specify what shell is to be loaded to run that script, since there are many, and syntax is not compatible. Without it, the shell already running will try to run the script, which may well bomb, or no shell could be loaded at all. - Tim On

And now....suddenly, and so far unexplainably....it works again. I did the same as before, installed openSUSE 13.1 from scratch, then installed the libusb* libraries. And now...it works, so far reliably. I'm certain that there is some micro-step I started doing different than last time. For example, I used to install jedit from the command line after install, but I had started installing

Tim, Thanks for the help! No, I didn't already know that... I swear, the more time I spend at this, the less I seem to be understanding. I know that it had to be finding the libusb-compat I had just installed, because configure hadn't worked before that, and now it did. But finding useful version information seems to be almost impossible. Rob Groner Software Engineer Level II RTD

linux-5048:/home/rtd # ldd /usr/local/ups/bin/usbhid-ups linux-vdso.so.1 (0x00007fff403fc000) libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f7c34b56000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7c34939000) libc.so.6 => /lib64/libc.so.6 (0x00007f7c34590000) libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00007f7c34378000)

Charles, 3.16.6.-2-desktop Keep in mind, despite the subject line, that this has been openSUSE 13.2 recently. I had hoped it would work better than 13.1, but so far hasn't. When I was trying with openSUSE 13.1, it was kernel 3.11.6-2-desktop. Rob Groner Software Engineer Level II RTD Embedded Technologies, Inc. ISO 9001 and AS9100 Certified Ph: +1 814-234-8087

Roger, rtd at linux-5048> sudo /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) USB communication driver 0.32 0.000000 debug level is '3' 0.000405 upsdrv_initups... 0.004386 Checking device (0930/6545) (002/002) 0.004431 Failed to open device, skipping. (Permission denied) 0.004442 Checking device (1D6B/0002)

I found something particularly strange while trying out different things: I started up upsdrvctl, upsd, and upsmon. I then stopped upsdrvctl, and tried starting the usbhid-ups driver a few times. Each time I executed the driver, it indicated an instance was already running, stopped it, and then started it again....which is what it should do. I then added -DDDD to the command....and then it

For fun, if you want to see where the system thinks it is linking a library from, you can use "ldconfig -p" and it will give you a path to all known libraries that it can find. If you have one loaded, and it can't find it (odd directory, etc.) you can always amend "LD_LIBRARY_PATH" the same way as PKG_CONFIG_PATH I mentioned earlier . . . . PKG . . . is for the build

I am running tests on my system and UPS, making sure that it is reliably able to come up, detect power loss, shutdown safely, and then come back up when the power returns. It does that MOST of the time. However, a significant part of the time, the system comes up, and then doesn't respond to loss of power. Doing some checking, I find that the reason is because upsd never started. Capturing

Charles, dmesg doesn't say anything when "usbhid-ups -a rtdups -k" is executed. I'm not sure which USB lib it compiled against. I installed them via "zypper install libusb-*". I'll try to find the version that got installed, as that WOULD be one thing that might have changed since the last time I had this working. I'm not sure how to check for multiple

I didn't think to look for a log (attached), but now looking in it, I don't see anything more than I already thought I knew. It's as cryptic as configure itself. It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I can't make sense of the lines above that set "nut_have_libusb", as far as what

rtd at linux-5048:~> lsusb -vvv -d 2a37: Bus 001 Device 005: ID 2a37:5110 Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor

Thanks Charles, you were right about that. Here is what I tried...I installed openSUSE 13.1 from scratch (which means no libusb). I then took libusb-1.0 from the sourceforge site and built and installed it. Still it got the "cannot find libusb" error. So, looking at the sourceforge site, is see it mention that to work with the older libusb-0.1, you had to use libusb-compat-0.1.5.