thr3ads.net - Nut upsuser - [Nut-upsuser] CyberPower Value 2200E-GP [Dec 2010]

If this information is useful, please help other people find it:
Share via:

David Varley

2010-Dec-16 01:10 UTC

[Nut-upsuser] CyberPower Value 2200E-GP

I've just set up a CyberPower Value 2200E-GP on a system running Lucid
AMD64, with the current NUT package via apt-get, and it seems to be working
fine for me with the usbhid-ups driver, so I guess it can go in the HCL?

I'm using the system to host several virtual servers under KVM, and to make
things simple I set it up to hibernate rather than shutdown, that way all
the guest OS don't have to be shutdown, they just carry on happily from
where they were after power is restored. To achieve this I timed how long it
take to go into hibernation (30-40 seconds), and set the UPS to shutdown
after 60 seconds via the driver "offdelay" setting.
I then set:

    SHUTDOWNCMD "/sbin/upsdrvctl shutdown;/usr/sbin/pm-hibernate"

and under test it works well. I'm don't know if there is a better or
"right"
way to do this, obviously the heuristically determined off delay is a bit of
a risk, and as the system doesn't actually shut down perhaps there will be
other problems with NUT? The /etc/killpower flag isn't deleted, for
instance.

I've attached the output of  *usbhid-ups -DDD -a 2200LCD* as there seem to
be several errors reported in there. I can see the subdriver doesn't find
the serial number, for example, while the pwrstat code supplied by
CyberPower does.

Cheers,

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20101216/8a8d89aa/attachment-0001.htm>
-------------- next part --------------
Results for CyberPower Value 2200E-GP
(Their pwrstat utility reports Serial: BFF7104#7N5)

sudo /lib/nut/usbhid-ups -DDD -a 2200LCD
Network UPS Tools - Generic HID driver 0.34 (2.4.3)
USB communication driver 0.31
   0.000000     debug level is '3'
   0.001882     upsdrv_initups...
   0.221831     Checking device (1D6B/0001) (005/001)
   0.221884     - VendorID: 1d6b
   0.221891     - ProductID: 0001
   0.221897     - Manufacturer: Linux 2.6.32-26-server uhci_hcd
   0.221903     - Product: UHCI Host Controller
   0.221909     - Serial Number: 0000:00:1d.3
   0.221915     - Bus: 005
   0.221920     Trying to match device
   0.221937     Device does not match - skipping
   0.221948     Checking device (0764/0501) (004/015)
   0.243852     - VendorID: 0764
   0.243865     - ProductID: 0501
   0.243871     - Manufacturer: CPS
   0.243877     - Product:  Value 2200E
   0.243883     - Serial Number: unknown
   0.243888     - Bus: 004
   0.243893     Trying to match device
   0.243960     Device matches
   0.243984     failed to claim USB device: could not claim interface 0: Device
or resource busy
   0.246013     detached kernel driver from USB device...
   0.253853     HID descriptor, method 1: (9 bytes) => 09 21 10 01 21 01 22
8b 01
   0.253870     HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22
8b 01
   0.253876     HID descriptor length 395
   0.306863     Report Descriptor size = 395
   0.306885     Report Descriptor: (395 bytes) => 05 84 09 04 a1 01 09 24 a1
00 85 01 09 fe
   0.306896      75 08 95 01 15 00 26 ff 00 b1 22 85 02 09 ff b1 22 85 03 05 85
09 89 b1 22
   0.306907      85 04 09 8f b1 22 85 05 09 8b b1 22 85 06 09 2c b1 22 85 07 75
08 95 06 25
   0.306918      78 09 83 09 8d 09 8e 09 8c 09 29 09 67 b1 22 85 08 75 08 95 01
65 00 09 66
   0.306929      81 a2 09 66 b1 a2 09 68 75 10 27 ff ff 00 00 66 01 10 81 a2 09
68 b1 a2 09
   0.306940      2a 26 58 02 81 a2 09 2a b1 a2 85 09 75 08 26 ff 00 05 84 09 40
67 21 d1 f0
   0.306951      00 55 06 b1 22 85 0a 09 30 b1 a2 65 00 55 00 09 02 a1 02 85 0b
75 01 95 06
   0.306962      25 01 05 85 09 d0 09 44 09 45 09 42 09 46 09 43 81 a2 09 d0 09
44 09 45 09
   0.306973      42 09 46 09 43 b1 a2 75 02 95 01 81 01 b1 01 c0 85 0c 05 84 09
5a 75 08 15
   0.306984      01 25 03 b1 a2 85 0d 09 fd 15 00 26 ff 00 b1 22 c0 05 84 09 1a
a1 00 85 0e
   0.306995      05 84 09 40 75 08 67 21 d1 f0 00 55 07 b1 22 85 0f 75 10 26 07
01 09 30 b1
   0.307006      a2 85 10 09 53 75 08 15 a0 25 a0 b1 22 75 10 09 54 16 07 01 26
07 01 b1 22
   0.307016      c0 09 1c a1 00 85 12 09 30 15 00 b1 a2 75 08 65 00 55 00 85 13
09 35 b1 a2
   0.307027      85 14 09 58 25 06 b1 a2 85 15 09 57 75 10 15 ff 26 ff 7f 35 c4
47 c4 ff 1d
   0.307038      00 66 01 10 b1 a2 85 16 09 56 b1 a2 85 17 09 6e 75 01 15 00 25
01 35 00 45
   0.307048      00 65 00 b1 a2 09 65 b1 a2 75 06 b1 01 85 18 75 10 09 44 26 c2
01 66 21 d1
   0.307056      55 07 b1 a2 c0 c0
   0.307133     Using subdriver: CyberPower HID 0.3
   0.310846     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.310858     Report[err]: (8 bytes) => 01 01 98 0d 2c 01 64 00
   0.310870     Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01,
Offset: 0, Size: 8, Value: 1.000000
   0.314846     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.314859     Report[err]: (8 bytes) => 02 02 98 0d 2c 01 64 00
   0.314869     Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID:
0x02, Offset: 0, Size: 8, Value: 2.000000
   0.318844     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.318856     Report[err]: (8 bytes) => 03 04 98 0d 2c 01 64 00
   0.318866     Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature,
ReportID: 0x03, Offset: 0, Size: 8, Value: 4.000000
   0.322847     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.322860     Report[err]: (8 bytes) => 04 03 98 0d 2c 01 64 00
   0.322875     Path: UPS.PowerSummary.iOEMInformation, Type: Feature, ReportID:
0x04, Offset: 0, Size: 8, Value: 3.000000
   0.326844     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.326855     Report[err]: (8 bytes) => 05 01 98 0d 2c 01 64 00
   0.326865     Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID:
0x05, Offset: 0, Size: 8, Value: 1.000000
   0.330842     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.330852     Report[err]: (8 bytes) => 06 02 98 0d 2c 01 64 00
   0.330862     Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID:
0x06, Offset: 0, Size: 8, Value: 2.000000
   0.334845     refresh_report_buffer: expected 7 bytes, but got 8 instead
   0.334856     Report[err]: (8 bytes) => 07 64 05 0a 14 0a 64 00
   0.334868     Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID:
0x07, Offset: 0, Size: 8, Value: 100.000000
   0.334877     Report[buf]: (7 bytes) => 07 64 05 0a 14 0a 64
   0.334886     Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature,
ReportID: 0x07, Offset: 8, Size: 8, Value: 5.000000
   0.334895     Report[buf]: (7 bytes) => 07 64 05 0a 14 0a 64
   0.334904     Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature,
ReportID: 0x07, Offset: 16, Size: 8, Value: 10.000000
   0.334918     Report[buf]: (7 bytes) => 07 64 05 0a 14 0a 64
   0.334927     Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature,
ReportID: 0x07, Offset: 24, Size: 8, Value: 20.000000
   0.334936     Report[buf]: (7 bytes) => 07 64 05 0a 14 0a 64
   0.334945     Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature,
ReportID: 0x07, Offset: 32, Size: 8, Value: 10.000000
   0.334954     Report[buf]: (7 bytes) => 07 64 05 0a 14 0a 64
   0.334963     Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature,
ReportID: 0x07, Offset: 40, Size: 8, Value: 100.000000
   0.338843     refresh_report_buffer: expected 6 bytes, but got 8 instead
   0.338854     Report[err]: (8 bytes) => 08 64 c6 0c 2c 01 64 00
   0.338869     Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID:
0x08, Offset: 0, Size: 8, Value: 100.000000
   0.338879     Report[buf]: (6 bytes) => 08 64 c6 0c 2c 01
   0.338888     Path: UPS.PowerSummary.RemainingCapacity, Type: Feature,
ReportID: 0x08, Offset: 0, Size: 8, Value: 100.000000
   0.338897     Report[buf]: (6 bytes) => 08 64 c6 0c 2c 01
   0.338907     Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID:
0x08, Offset: 8, Size: 16, Value: 3270.000000
   0.338915     Report[buf]: (6 bytes) => 08 64 c6 0c 2c 01
   0.338925     Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID:
0x08, Offset: 8, Size: 16, Value: 3270.000000
   0.338933     Report[buf]: (6 bytes) => 08 64 c6 0c 2c 01
   0.338943     Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input,
ReportID: 0x08, Offset: 24, Size: 16, Value: 300.000000
   0.338951     Report[buf]: (6 bytes) => 08 64 c6 0c 2c 01
   0.338961     Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature,
ReportID: 0x08, Offset: 24, Size: 16, Value: 300.000000
   0.342847     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.342860     Report[err]: (8 bytes) => 09 f0 c6 0c 2c 01 64 00
   0.342871     Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID:
0x09, Offset: 0, Size: 8, Value: 24.000000
   0.346842     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.346854     Report[err]: (8 bytes) => 0a d0 c6 0c 2c 01 64 00
   0.346865     Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0a,
Offset: 0, Size: 8, Value: 20.800000
   0.350843     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.350854     Report[err]: (8 bytes) => 0b 11 c6 0c 2c 01 64 00
   0.350865     Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input,
ReportID: 0x0b, Offset: 0, Size: 1, Value: 1.000000
   0.350873     Report[buf]: (2 bytes) => 0b 11
   0.350882     Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input,
ReportID: 0x0b, Offset: 1, Size: 1, Value: 0.000000
   0.350890     Report[buf]: (2 bytes) => 0b 11
   0.350898     Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input,
ReportID: 0x0b, Offset: 2, Size: 1, Value: 0.000000
   0.350906     Report[buf]: (2 bytes) => 0b 11
   0.350915     Path:
UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input,
ReportID: 0x0b, Offset: 3, Size: 1, Value: 0.000000
   0.350923     Report[buf]: (2 bytes) => 0b 11
   0.350931     Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input,
ReportID: 0x0b, Offset: 4, Size: 1, Value: 1.000000
   0.350939     Report[buf]: (2 bytes) => 0b 11
   0.350948     Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired,
Type: Input, ReportID: 0x0b, Offset: 5, Size: 1, Value: 0.000000
   0.350956     Report[buf]: (2 bytes) => 0b 11
   0.350964     Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature,
ReportID: 0x0b, Offset: 0, Size: 1, Value: 1.000000
   0.350972     Report[buf]: (2 bytes) => 0b 11
   0.350981     Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature,
ReportID: 0x0b, Offset: 1, Size: 1, Value: 0.000000
   0.350988     Report[buf]: (2 bytes) => 0b 11
   0.350997     Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature,
ReportID: 0x0b, Offset: 2, Size: 1, Value: 0.000000
   0.351005     Report[buf]: (2 bytes) => 0b 11
   0.351014     Path:
UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature,
ReportID: 0x0b, Offset: 3, Size: 1, Value: 0.000000
   0.351022     Report[buf]: (2 bytes) => 0b 11
   0.351030     Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type:
Feature, ReportID: 0x0b, Offset: 4, Size: 1, Value: 1.000000
   0.351038     Report[buf]: (2 bytes) => 0b 11
   0.351047     Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired,
Type: Feature, ReportID: 0x0b, Offset: 5, Size: 1, Value: 0.000000
   0.354843     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.354855     Report[err]: (8 bytes) => 0c 02 c6 0c 2c 01 64 00
   0.354865     Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature,
ReportID: 0x0c, Offset: 0, Size: 8, Value: 2.000000
   0.358843     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.358854     Report[err]: (8 bytes) => 0d 03 c6 0c 2c 01 64 00
   0.358864     Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID:
0x0d, Offset: 0, Size: 8, Value: 3.000000
   0.362844     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.362857     Report[err]: (8 bytes) => 0e e6 c6 0c 2c 01 64 00
   0.362868     Path: UPS.Input.ConfigVoltage, Type: Feature, ReportID: 0x0e,
Offset: 0, Size: 8, Value: 230.000000
   0.366841     refresh_report_buffer: expected 3 bytes, but got 8 instead
   0.366857     Report[err]: (8 bytes) => 0f f0 00 0c 2c 01 64 00
   0.366868     Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x0f, Offset:
0, Size: 16, Value: 240.000000
   0.370842     refresh_report_buffer: expected 4 bytes, but got 8 instead
   0.370854     Report[err]: (8 bytes) => 10 a0 07 01 2c 01 64 00
   0.370865     Path: UPS.Input.LowVoltageTransfer, Type: Feature, ReportID:
0x10, Offset: 0, Size: 8, Value: -96.000000
   0.370873     Report[buf]: (4 bytes) => 10 a0 07 01
   0.370883     Path: UPS.Input.HighVoltageTransfer, Type: Feature, ReportID:
0x10, Offset: 8, Size: 16, Value: 263.000000
   0.374841     refresh_report_buffer: expected 3 bytes, but got 8 instead
   0.374851     Report[err]: (8 bytes) => 12 f0 00 01 2c 01 64 00
   0.374861     Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x12, Offset:
0, Size: 16, Value: 240.000000
   0.378841     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.378852     Report[err]: (8 bytes) => 13 0e 00 01 2c 01 64 00
   0.378863     Path: UPS.Output.PercentLoad, Type: Feature, ReportID: 0x13,
Offset: 0, Size: 8, Value: 14.000000
   0.382844     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.382857     Report[err]: (8 bytes) => 14 01 00 01 2c 01 64 00
   0.382867     Path: UPS.Output.Test, Type: Feature, ReportID: 0x14, Offset: 0,
Size: 8, Value: 1.000000
   0.386840     refresh_report_buffer: expected 3 bytes, but got 8 instead
   0.386851     Report[err]: (8 bytes) => 15 ff ff 01 2c 01 64 00
   0.386862     Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID:
0x15, Offset: 0, Size: 16, Value: -60.000000
   0.390841     refresh_report_buffer: expected 3 bytes, but got 8 instead
   0.390852     Report[err]: (8 bytes) => 16 00 00 01 2c 01 64 00
   0.390862     Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID:
0x16, Offset: 0, Size: 16, Value: 0.000000
   0.394841     refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.394852     Report[err]: (8 bytes) => 17 00 00 01 2c 01 64 00
   0.394861     Path: UPS.Output.Boost, Type: Feature, ReportID: 0x17, Offset:
0, Size: 1, Value: 0.000000
   0.394869     Report[buf]: (2 bytes) => 17 00
   0.394878     Path: UPS.Output.Overload, Type: Feature, ReportID: 0x17,
Offset: 1, Size: 1, Value: 0.000000
   0.398842     refresh_report_buffer: expected 3 bytes, but got 8 instead
   0.398853     Report[err]: (8 bytes) => 18 28 05 01 2c 01 64 00
   0.398864     Path: UPS.Output.ConfigActivePower, Type: Feature, ReportID:
0x18, Offset: 0, Size: 16, Value: 296.000000
   0.398892     Report descriptor retrieved (Reportlen = 395)
   0.398900     Found HID device
   0.398906     Detected a UPS: CPS/ Value 2200E
   0.398919     Report[buf]: (2 bytes) => 03 04
   0.398927     Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature,
ReportID: 0x03, Offset: 0, Size: 8, Value: 4.000000
   0.409848     Report[buf]: (2 bytes) => 04 03
   0.409860     Path: UPS.PowerSummary.iOEMInformation, Type: Feature, ReportID:
0x04, Offset: 0, Size: 8, Value: 3.000000
   0.420849     Report[buf]: (7 bytes) => 07 64 05 0a 14 0a 64
   0.420861     Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature,
ReportID: 0x07, Offset: 24, Size: 8, Value: 20.000000
   0.420880     Report[buf]: (7 bytes) => 07 64 05 0a 14 0a 64
   0.420889     Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature,
ReportID: 0x07, Offset: 32, Size: 8, Value: 10.000000
   0.420905     Report[buf]: (6 bytes) => 08 64 c6 0c 2c 01
   0.420913     Path: UPS.PowerSummary.RemainingCapacity, Type: Feature,
ReportID: 0x08, Offset: 0, Size: 8, Value: 100.000000
   0.420928     Report[buf]: (6 bytes) => 08 64 c6 0c 2c 01
   0.420936     Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID:
0x08, Offset: 8, Size: 16, Value: 3270.000000
   0.420950     Report[buf]: (6 bytes) => 08 64 c6 0c 2c 01
   0.420959     Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature,
ReportID: 0x08, Offset: 24, Size: 16, Value: 300.000000
   0.420973     Report[buf]: (2 bytes) => 09 f0
   0.420981     Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID:
0x09, Offset: 0, Size: 8, Value: 24.000000
   0.420993     Report[buf]: (2 bytes) => 0a d0
   0.421001     Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0a,
Offset: 0, Size: 8, Value: 20.800000
   0.421016     Report[buf]: (2 bytes) => 13 0e
   0.421024     Path: UPS.Output.PercentLoad, Type: Feature, ReportID: 0x13,
Offset: 0, Size: 8, Value: 14.000000
   0.421037     Report[buf]: (2 bytes) => 0c 02
   0.421044     Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature,
ReportID: 0x0c, Offset: 0, Size: 8, Value: 2.000000
   0.421057     Report[buf]: (2 bytes) => 14 01
   0.421065     Path: UPS.Output.Test, Type: Feature, ReportID: 0x14, Offset: 0,
Size: 8, Value: 1.000000
   0.421078     Report[buf]: (3 bytes) => 18 28 05
   0.421087     Path: UPS.Output.ConfigActivePower, Type: Feature, ReportID:
0x18, Offset: 0, Size: 16, Value: 296.000000
   0.421111     Report[buf]: (3 bytes) => 16 00 00
   0.421119     Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID:
0x16, Offset: 0, Size: 16, Value: 0.000000
   0.421132     Report[buf]: (3 bytes) => 15 ff ff
   0.421140     Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID:
0x15, Offset: 0, Size: 16, Value: -60.000000
   0.421157     Report[buf]: (2 bytes) => 0b 11
   0.421165     Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature,
ReportID: 0x0b, Offset: 0, Size: 1, Value: 1.000000
   0.421177     Report[buf]: (2 bytes) => 0b 11
   0.421184     Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature,
ReportID: 0x0b, Offset: 1, Size: 1, Value: 0.000000
   0.421195     Report[buf]: (2 bytes) => 0b 11
   0.421202     Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature,
ReportID: 0x0b, Offset: 2, Size: 1, Value: 0.000000
   0.421214     Report[buf]: (2 bytes) => 0b 11
   0.421221     Path:
UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature,
ReportID: 0x0b, Offset: 3, Size: 1, Value: 0.000000
   0.421232     Report[buf]: (2 bytes) => 0b 11
   0.421240     Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type:
Feature, ReportID: 0x0b, Offset: 4, Size: 1, Value: 1.000000
   0.421251     Report[buf]: (2 bytes) => 0b 11
   0.421258     Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired,
Type: Feature, ReportID: 0x0b, Offset: 5, Size: 1, Value: 0.000000
   0.421269     Report[buf]: (2 bytes) => 17 00
   0.421277     Path: UPS.Output.Boost, Type: Feature, ReportID: 0x17, Offset:
0, Size: 1, Value: 0.000000
   0.421287     Report[buf]: (2 bytes) => 17 00
   0.421294     Path: UPS.Output.Overload, Type: Feature, ReportID: 0x17,
Offset: 1, Size: 1, Value: 0.000000
   0.421305     Report[buf]: (2 bytes) => 0e e6
   0.421312     Path: UPS.Input.ConfigVoltage, Type: Feature, ReportID: 0x0e,
Offset: 0, Size: 8, Value: 230.000000
   0.421325     Report[buf]: (3 bytes) => 0f f0 00
   0.421333     Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x0f, Offset:
0, Size: 16, Value: 240.000000
   0.421347     Report[buf]: (4 bytes) => 10 a0 07 01
   0.421355     Path: UPS.Input.LowVoltageTransfer, Type: Feature, ReportID:
0x10, Offset: 0, Size: 8, Value: -96.000000
   0.421370     Report[buf]: (4 bytes) => 10 a0 07 01
   0.421378     Path: UPS.Input.HighVoltageTransfer, Type: Feature, ReportID:
0x10, Offset: 8, Size: 16, Value: 263.000000
   0.421393     Report[buf]: (3 bytes) => 12 f0 00
   0.421401     Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x12, Offset:
0, Size: 16, Value: 240.000000
   0.421416     Report[buf]: (2 bytes) => 14 01
   0.421424     Path: UPS.Output.Test, Type: Feature, ReportID: 0x14, Offset: 0,
Size: 8, Value: 1.000000
   0.421435     Report[buf]: (2 bytes) => 14 01
   0.421442     Path: UPS.Output.Test, Type: Feature, ReportID: 0x14, Offset: 0,
Size: 8, Value: 1.000000
   0.421454     Report[buf]: (2 bytes) => 14 01
   0.421461     Path: UPS.Output.Test, Type: Feature, ReportID: 0x14, Offset: 0,
Size: 8, Value: 1.000000
   0.421472     Report[buf]: (3 bytes) => 15 ff ff
   0.421480     Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID:
0x15, Offset: 0, Size: 16, Value: -60.000000
   0.421492     Report[buf]: (3 bytes) => 16 00 00
   0.421499     Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID:
0x16, Offset: 0, Size: 16, Value: 0.000000
   0.421511     Report[buf]: (3 bytes) => 15 ff ff
   0.421519     Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID:
0x15, Offset: 0, Size: 16, Value: -60.000000
   0.421541     Report[buf]: (2 bytes) => 0c 02
   0.421549     Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature,
ReportID: 0x0c, Offset: 0, Size: 8, Value: 2.000000
   0.421561     Report[buf]: (2 bytes) => 0c 02
   0.421568     Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature,
ReportID: 0x0c, Offset: 0, Size: 8, Value: 2.000000
   0.421579     Report[buf]: (2 bytes) => 0c 02
   0.421586     Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature,
ReportID: 0x0c, Offset: 0, Size: 8, Value: 2.000000
   0.463554     Report[buf]: (2 bytes) => 0c 02
   0.463566     Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature,
ReportID: 0x0c, Offset: 0, Size: 8, Value: 2.000000
   0.463579     Report[buf]: (2 bytes) => 0c 02
   0.463586     Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature,
ReportID: 0x0c, Offset: 0, Size: 8, Value: 2.000000
   0.463606     upsdrv_initinfo...
   0.463617     upsdrv_updateinfo...
   0.715837     libusb_get_interrupt: Connection timed out
   0.715857     Got 0 HID objects...
   0.715864     Quick update...
   0.715874     Report[buf]: (3 bytes) => 16 00 00
   0.715882     Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID:
0x16, Offset: 0, Size: 16, Value: 0.000000
   0.715893     Report[buf]: (3 bytes) => 15 ff ff
   0.715902     Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID:
0x15, Offset: 0, Size: 16, Value: -60.000000
   0.715911     Report[buf]: (2 bytes) => 0b 11
   0.715919     Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature,
ReportID: 0x0b, Offset: 0, Size: 1, Value: 1.000000
   0.715927     Report[buf]: (2 bytes) => 0b 11
   0.715934     Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature,
ReportID: 0x0b, Offset: 1, Size: 1, Value: 0.000000
   0.715942     Report[buf]: (2 bytes) => 0b 11
   0.715949     Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature,
ReportID: 0x0b, Offset: 2, Size: 1, Value: 0.000000
   0.715958     Report[buf]: (2 bytes) => 0b 11
   0.715965     Path:
UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature,
ReportID: 0x0b, Offset: 3, Size: 1, Value: 0.000000
   0.716034     dstate_init: sock /var/run/nut/usbhid-ups-2200LCD open on fd 6
   0.716050     upsdrv_updateinfo...

Arjen de Korte

2010-Dec-16 09:05 UTC

head link

[Nut-upsuser] CyberPower Value 2200E-GP

Citeren David Varley <davidavarley op gmail.com>:
> I've just set up a CyberPower Value 2200E-GP on a system running Lucid
> AMD64, with the current NUT package via apt-get, and it seems to be working
> fine for me with the usbhid-ups driver, so I guess it can go in the HCL?
Probably. We'll just need a little more information like the 'upsc'
output for this UPS (to see if we need to add additional mappings).
> I'm using the system to host several virtual servers under KVM, and to
make
> things simple I set it up to hibernate rather than shutdown, that way all
> the guest OS don't have to be shutdown, they just carry on happily from
> where they were after power is restored. To achieve this I timed how long
it
> take to go into hibernation (30-40 seconds), and set the UPS to shutdown
> after 60 seconds via the driver "offdelay" setting.
> I then set:
>
>     SHUTDOWNCMD "/sbin/upsdrvctl shutdown;/usr/sbin/pm-hibernate"
>
> and under test it works well. I'm don't know if there is a better
or "right"
> way to do this, obviously the heuristically determined off delay is a bit
of
> a risk, and as the system doesn't actually shut down perhaps there will
be
> other problems with NUT? The /etc/killpower flag isn't deleted, for
> instance.
Remember that the 'upsd' server will latch the FSD (forced shutdown)  
flag when it has detected an "OB LB" condition. The only way to reset
this, is to restart NUT. Otherwise after resuming, NUT will  
immediately shutdown again. Many systems will allow you to run scripts  
when going into hibernation and after resuming. You'll want to stop  
NUT when hibernating and restart it when resuming (this will take care  
of the /etc/killpower flag as well). I'd prefer to run the 'upsdrvctl  
shutdown' command from the hibernation script as well. Also remember  
that there is a slight risk that if hibernation fails, the UPS will  
power off anyway. If that worries you, it might be better to stick  
with a full shutdown of the system.
> I've attached the output of  *usbhid-ups -DDD -a 2200LCD* as there seem
to
> be several errors reported in there. I can see the subdriver doesn't
find
> the serial number, for example, while the pwrstat code supplied by
> CyberPower does.
There are some issues with the usbhid-ups driver in nut-2.4.3. Most of  
these have been resolved in the development version of NUT. I would be  
grateful if you could try out this. Most (if not all) of the errors  
you're seeing now should be fixed.

We could add some code to add reading the serial number, but we really  
need it before claiming the device (which seems to be broken in either  
your UPS or the version of libusb you're using).

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)

David Varley

2010-Dec-17 05:59 UTC

head link

[Nut-upsuser] CyberPower Value 2200E-GP

Arjen,

I've appended the output of upsc

I'll keep in mind your warning about the upsd server latching the FSD flag
and requiring a restart, however I'm just running the packaged Ubuntu/Lucid
version at this stage so I don't have too much flexibility. NUT seems to be
set up as a service, so that it starts correctly on system boot, however it
was probably assumed it would run until a system shutdown as the scripts
don't handle stopping the service. When I :

  *sudo service nut stop*

the NUT processes continue running. I doubt I'll have a chance to spend more
time on this before Christmas.

Regards, David


david at xeno:/etc/nut$ upsc 2200LCD at localhost
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 20
battery.mfr.date: CPS
battery.runtime: 3270
battery.runtime.low: 300
battery.type: PbAcid
battery.voltage: 13.9
battery.voltage.nominal: 24
device.mfr: CPS
device.model:  Value 2200E
device.type: ups
driver.name: usbhid-ups
driver.parameter.offdelay: 60
driver.parameter.ondelay: 70
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 0501
driver.parameter.vendorid: 0764
driver.version: 2.4.3
driver.version.data: CyberPower HID 0.3
driver.version.internal: 0.34
input.transfer.high: 263
input.transfer.low: -96
input.voltage: 240.0
input.voltage.nominal: 230
output.voltage: 240.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 14
ups.mfr: CPS
ups.model:  Value 2200E
ups.productid: 0501
ups.realpower.nominal: 296
ups.status: FSD OL
ups.test.result: Done and passed
ups.timer.shutdown: -60
ups.timer.start: 0
ups.vendorid: 0764

_______________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20101217/d783e2fd/attachment.htm>

David Varley

2010-Dec-17 12:51 UTC

head link

[Nut-upsuser] CyberPower Value 2200E-GP

Regarding my observation that the processes keep running after I "sudo
service nut stop", I found this isn't exactly the case. I think what
happens
is that if I forget the "sudo" in front of the command, it comes up
with the
"Stopping Nut Tools... Done" line, as if it worked, however it
actually
failed and the processes are still running. If I then start the services
again, it actually starts another instance, that is there are two copies of
the usb driver running. (And leaving complaining messages in the log!)
If I then stop the services (correctly, with the sudo) one still remains,
and it can only be stopped with an explicit kill command. This is what I was
seeing.

As far as setting the shutdown command in a script run when hibernating, I
did this. I created a script, 48nut, in /etc/pm/sleep.d, as follows:

#!/bin/sh
# If we are hibernating due to power-fail, initiate a delayed UPS shutdown
and then stop the nut services
# If we are thawing after this event, start the nut service
# DAV 17DEC10

if (test -f /etc/killpower)
then
case "$1" in
hibernate|suspend)
echo "Initiating UPS Powerdown Sequence"
/sbin/upsdrvctl shutdown
echo "Stopping nut service"
service nut stop
;;
thaw|resume)
service nut start
;;
*) exit $NA
;;
esac
fi

Unfortunately it didn't work, perhaps the service is stopped before the
shutdown has a chance to take effect. In /var/log/pm-suspend.log. On
hibernate I see:

/etc/pm/sleep.d/48nut hibernate hibernate:Initiating UPS Powerdown Sequence
*Startup timer elapsed, continuing...*
Network UPS Tools - UPS driver controller 2.4.3
Stopping nut service
* Stopping Network UPS Tools
...done.
success.
/usr/lib/pm-utils/sleep.d/49bluetooth hibernate hibernate:not applicable.

Then on thaw I see:

/usr/lib/pm-utils/sleep.d/49bluetooth thaw hibernate:not applicable.
/etc/pm/sleep.d/48nut thaw hibernate: * Starting Network UPS Tools

however the shutdown never occurs, and after the thaw the nut services are
not running!
If I have the shutdown command in the script, but not the command to stop
the nut services, then the UPS does shut down.

So, for now I'm going back to my single line SHUTDWNCMD which actually
worked.

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20101217/9573ae8b/attachment.htm>

David Varley

2010-Dec-17 22:58 UTC

head link

[Nut-upsuser] CyberPower Value 2200E-GP

On Fri, 17 Dec 2010 17:41:39 +0100, Arjen de Korte
<nut+users at de-korte.org<nut%2Busers at
de-korte.org>> wrote:
>
>
> Citeren David Varley <davidavarley at gmail.com>:
>
>  As far as setting the shutdown command in a script run when hibernating, I
>> did this. I created a script, 48nut, in /etc/pm/sleep.d, as follows:
>>
>> #!/bin/sh
>> # If we are hibernating due to power-fail, initiate a delayed UPS
shutdown
>> and then stop the nut services
>> # If we are thawing after this event, start the nut service
>> # DAV 17DEC10
>>
>>   if (test -f /etc/killpower)
>>   then
>>        case "$1" in
>>                hibernate|suspend)
>>                        echo "Initiating UPS Powerdown
Sequence"
>>                        /sbin/upsdrvctl shutdown
>>                        echo "Stopping nut service"
>>                        service nut stop
>>
>
> This won't work. In order to send a poweroff command to the UPS, the
> drivers must be restarted from scratch. Therefor you must run 'service
nut
> stop' before doing that, otherwise the backgrounded drivers will not
have
> exited.
>
> It also is a good idea to put a 'sleep 2' between the two commands,
to give
> the drivers some time to respond to the KILL signal they receive:
>
>    echo "Stopping nut service"
>    service nut stop
>    sleep 2
>    echo "Initiating UPS Powerdown Sequence"
>    /sbin/upsdrvctl shutdown
>
> Best regards, Arjen
>
Arjen, now I'm a bit confused. In your script you are saying to shut down
nut before issuing the upsdrvctl command to tell the UPS to start a delayed
shutdown. But as shutting down nut causes the usbhid-ups driver to exit, I
thought that would prevent the command being sent to the UPS? I know that if
I just have the upsdrvctl shutdown command without telling the nut service
to exit, the UPS shuts down after the 60 second delay. I can understand
adding the delay after giving the shutdown command and before stopping the
services, but not the other way around. What am I missing here?

Thanks, David
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20101218/a574b6c0/attachment.htm>

David Varley

2010-Dec-18 12:21 UTC

head link

[Nut-upsuser] CyberPower Value 2200E-GP

Arjen de Korte <nut+users at de-korte.org <nut%2Busers at
de-korte.org>> wrote:

...
> You missed reading the docs/suspend-to-disk.txt file, where it is
> explained how you should set this up. If you want to know the details
> about this, start reading the remainder of the documents in docs/
> before asking.
>
> Best regards, Arjen
Arjen,

That document would be really useful to know about!

I started out wanting to use this package, and I installed the
packaged version for my OS in the usual way, and read all the man
pages. No mention of suspend there.

I read through the online documentation on the web site. Nothing there, either.

So I downloaded the source to the latest stable release, and I read
everything in the /docs folder. Nothing there, no suspend-to-disk.txt
or any mention of suspend.

It was only at this point that I finally  made my first request to the
list for help!

Ok, now you told me there is a docs/suspend-to-disk.txt file, I looked
further. In the development release files on the web site. No, not
there.

Can Google find it for me? No, it seems it hasn't been indexed anywhere
either.

Given all this, no doubt it is somewhere obvious, when you know where to
look. But I was not planning to be a developer, just a user, and I have a
huge stack of work in front of me and Xmas coming up, and I would really
like to get this nailed down and move on, so if you could please point me to
the required documentation I would be most grateful.

Regards,

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20101218/fe64c33f/attachment.htm>

Charles Lepple

2010-Dec-18 17:00 UTC

head link

[Nut-upsuser] CyberPower Value 2200E-GP

On Dec 18, 2010, at 7:21 AM, David Varley wrote:> So I downloaded the source to the latest stable release, and I read  
> everything in the /docs folder. Nothing there, no suspend-to- 
> disk.txt or any mention of suspend.
It appears that suspend-to-disk did not make it into the 2.4.3 tarball.

Here it is in the new User Manual:

http://buildbot.networkupstools.org/~buildbot/cayenne/docs/latest/website/output/docs/user-manual.chunked/ar01s06.html#_using_suspend_to_disk

Possibly Parallel Threads

Search for more seemingly similar threads

Nut upsuser - Dec 2010 - CyberPower Value 2200E-GP

[Nut-upsuser] CyberPower Value 2200E-GP

[Nut-upsuser] CyberPower Value 2200E-GP

[Nut-upsuser] CyberPower Value 2200E-GP

[Nut-upsuser] CyberPower Value 2200E-GP

[Nut-upsuser] CyberPower Value 2200E-GP

[Nut-upsuser] CyberPower Value 2200E-GP

[Nut-upsuser] CyberPower Value 2200E-GP

Possibly Parallel Threads