[Nut-upsdev] APC Smart-UPS 1000 RM USB problems with newhidups

[Justin Maggard]

I was able to do a little more testing today.  I hooked up the UPS to 
another Linux FC4 box, running the newest stock Fedora kernel, 
2.6.14-1.1656_FC4.  I checked out the latest nut Development code from CVS; 
patched upsdrvctl.c so it will compile; and patched libusb.c to shorten 
desc->wDescriptorLength to 1040 if it is reported as 61939 (needed for 1000 
RM).
I set up the config files, and started newhidups and upsd.  I then pulled 
the power cord before running a little loop to monitor ups status using 
upsc.  Pretty soon after pulling the cord, newhidups died.  So, 2.6 behavior 
is not much better than 2.4.  Also, I did try the old hidups driver after 
newhidups died, and it worked fine except for the fact that it started 
adding an extra "0" to the end of the battery.charge line in upsc for some 
reason.  Here is output from the shell running the while loop using 
newhidups:
---  Pulled the power cord before starting typing ---
[root at FC4 clients]# while true; do ./upsc UPS at localhost|egrep 
'^battery.charge:|^battery.runtime:|^ups.status:'; sleep 10; done
battery.charge: 100
battery.runtime: 5280
ups.status: OL
battery.charge: 100
battery.runtime: 5280
ups.status: OL
battery.charge: 100
battery.runtime: 5280
ups.status: OL
battery.charge: 100
battery.runtime: 5280
ups.status: OL
battery.charge: 100
battery.runtime: 4980
ups.status: OL
battery.charge: 100
battery.runtime: 4980
ups.status: OL
battery.charge: 100
battery.runtime: 4980
ups.status: OL
battery.charge: 100
battery.runtime: 4980
ups.status: OB DISCHRG
battery.charge: 100
battery.runtime: 4800
ups.status: OB DISCHRG
Error: Driver not connected
Error: Driver not connected
Error: Driver not connected



>Well, after our first real extended power outage, I found out that even 
>though the UPS 1000 RM is recognized okay, it does not work properly.  It 
>never seems to see any change in UPS status.  It looks very similar to the 
>other issue I reported with the APC CyberFort 350.  I never was able to get 
>to the bottom of the CyberFort issue, but I'll bet it's the same issue as 
>we have with the APC 1000 RM.  Here's what I have done so far:
>* Machine is a AMD Athlon, running current Debian stable, 2.4.27 stock 
>Debian kernel
>* Machine has been verified working with a few APC BackUPS models with 
>newhidups
>1)  Tested by unplugging the power, right after a fresh boot.  --  
>Newhidups didn't see any change at all
>2)  Restarted the driver without rebooting.  --  Still said the UPS was 
>online
>3)  Stopped the driver, un/replugged the USB cable, restarted driver.  --  
>Newhidups saw that it was OB
>4)  Plugged in UPS power cable.  --  Newhidups saw battery level going up, 
>but still saw OB
>
>Then, I decided to try on my Toshiba Centrino laptop, running Fedora Core 
>4, stock 2.6.11 Fedora kernel.  I started just newhidups with -DD without 
>upsd or upsmon.  It did notice all the UPS events and battery level 
>changing, but segfaulted after a couple minutes.
>
>Does anyone have any ideas here?  George, I'm also wondering what kernel 
>you're running on the box you have attached to your SmartUPS 1000 RM.
>
>
>
>_______________________________________________
>Nut-upsdev mailing list
>Nut-upsdev at lists.alioth.debian.org
>http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev