Hello I recently switched from apcupsd to NUT2.2.2 without any troubles. I tried to figure out how I can configure the self-test intervall. The command upsrw lists only the variables battery.charge.low battery.runtime.low ups.delay.shutdown ups.delay.start The command usbhid-ups -D and the listing under http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart at localhost&treemode show no hint on appropriate variable. I scanned to log files and found no hint on successfull self-test. bye, wildi
Arnaud Quette
2009-Sep-02 14:44 UTC
[Nut-upsuser] Selftest intervall, APC Smart-UPS 750 RM
2009/9/2 Markus Wildi <wildi.markus at bluewin.ch>> Hello > > I recently switched from apcupsd to NUT2.2.2 without > any troubles. > > I tried to figure out how I can configure the self-test > intervall. The command upsrw lists only the variables > > battery.charge.low > battery.runtime.low > ups.delay.shutdown > ups.delay.start > > The command usbhid-ups -D and the listing under > > > http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart at localhost&treemode > > show no hint on appropriate variable. > > I scanned to log files and found no hint on successfull self-test. >it seems APC doesn't support this, or at least we have nothing mapped for this. for example, on Eaton / MGE units, we have "UPS.BatterySystem.Battery.TestPeriod" mapped to "ups.test.interval" to validate this, please upgrade to a more recent version (ie 2.4.1) and post back the output of usbhid-ups -D cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090902/89644148/attachment.htm>
Hello Arnaud I compiled the source of nut-2.4.1 and you'll find the output of usbhid-ups -D -a apcsmart below. The UPS did regularly report a self-test while running under apcupsd. It reports in addition e.g. the last reason for a on battery event. bye, wildi obsvermes:/usr/local/src/nut-2.4.1/drivers # ./usbhid-ups -D -a apcsmart Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 debug level is '1' upsdrv_initups... Using subdriver: APC HID 0.93 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8, Value: 2.000000 Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x03, Offset: 0, Size: 8, Value: 3.000000 Path: UPS.PowerSummary.iOEMInformation, Type: Feature, ReportID: 0x04, Offset: 0, Size: 8, Value: 3.000000 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x05, Offset: 0, Size: 8, Value: 4.000000 Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x06, Offset: 8, Size: 8, Value: 2.000000 Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID: 0x0e, Offset: 0, Size: 8, Value: 100.000000 Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, ReportID: 0x0e, Offset: 8, Size: 8, Value: 100.000000 Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x0c, Offset: 0, Size: 8, Value: 100.000000 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x0c, Offset: 0, Size: 8, Value: 100.000000 Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, ReportID: 0x10, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, ReportID: 0x10, Offset: 8, Size: 8, Value: 1.000000 Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 8, Value: 50.000000 Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, ReportID: 0x11, Offset: 0, Size: 8, Value: 10.000000 Path: UPS.PowerSummary.ManufacturerDate, Type: Feature, ReportID: 0x09, Offset: 0, Size: 16, Value: 13534.000000 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x0d, Offset: 0, Size: 16, Value: 2340.000000 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x0d, Offset: 0, Size: 16, Value: 2340.000000 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x12, Offset: 0, Size: 16, Value: -1.000000 Path: UPS.PowerSummary.DelayBeforeReboot, Type: Feature, ReportID: 0x13, Offset: 0, Size: 24, Value: -1.000000 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, ReportID: 0x08, Offset: 0, Size: 24, Value: 120.000000 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, ReportID: 0x08, Offset: 0, Size: 24, Value: 120.000000 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 16, Value: 24.000000 Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0b, Offset: 0, Size: 16, Value: 27.400000 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Input, ReportID: 0x14, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x07, Offset: 0, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x07, Offset: 0, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x07, Offset: 1, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x07, Offset: 1, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x07, Offset: 2, Size: 1, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x07, Offset: 2, Size: 1, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x07, Offset: 3, Size: 1, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Feature, ReportID: 0x07, Offset: 3, Size: 1, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x07, Offset: 4, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x07, Offset: 4, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input, ReportID: 0x07, Offset: 5, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Feature, ReportID: 0x07, Offset: 5, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x07, Offset: 6, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature, ReportID: 0x07, Offset: 6, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x07, Offset: 7, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Feature, ReportID: 0x07, Offset: 7, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Input, ReportID: 0x07, Offset: 8, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Feature, ReportID: 0x07, Offset: 8, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x07, Offset: 9, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Feature, ReportID: 0x07, Offset: 9, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Overload, Type: Input, ReportID: 0x07, Offset: 10, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Overload, Type: Feature, ReportID: 0x07, Offset: 10, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Input, ReportID: 0x07, Offset: 11, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Feature, ReportID: 0x07, Offset: 11, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x07, Offset: 12, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Feature, ReportID: 0x07, Offset: 12, Size: 1, Value: 0.000000 Path: UPS.Battery.Test, Type: Input, ReportID: 0x16, Offset: 0, Size: 8, Value: 6.000000 Path: UPS.Battery.Test, Type: Feature, ReportID: 0x16, Offset: 0, Size: 8, Value: 6.000000 Path: UPS.Battery.APCBattCapBeforeStartup, Type: Input, ReportID: 0x17, Offset: 0, Size: 8, Value: 0.000000 Path: UPS.Battery.APCBattCapBeforeStartup, Type: Feature, ReportID: 0x17, Offset: 0, Size: 8, Value: 0.000000 Path: UPS.Battery.ff86001a, Type: Input, ReportID: 0x1b, Offset: 0, Size: 8, Value: 3.000000 Path: UPS.Battery.ff86001a, Type: Feature, ReportID: 0x1b, Offset: 0, Size: 8, Value: 3.000000 Path: UPS.Battery.ff86001b, Type: Input, ReportID: 0x1c, Offset: 0, Size: 8, Value: 0.000000 Path: UPS.Battery.ff86001b, Type: Feature, ReportID: 0x1c, Offset: 0, Size: 8, Value: 0.000000 Path: UPS.Battery.ManufacturerDate, Type: Input, ReportID: 0x15, Offset: 0, Size: 16, Value: 13534.000000 Path: UPS.Battery.ManufacturerDate, Type: Feature, ReportID: 0x15, Offset: 0, Size: 16, Value: 13534.000000 Path: UPS.Battery.RemainingCapacity, Type: Feature, ReportID: 0x18, Offset: 0, Size: 16, Value: 100.000000 Path: UPS.Battery.RemainingTimeLimit, Type: Input, ReportID: 0x1a, Offset: 0, Size: 16, Value: 120.000000 Path: UPS.Battery.RemainingTimeLimit, Type: Feature, ReportID: 0x1a, Offset: 0, Size: 16, Value: 120.000000 Path: UPS.Battery.RunTimeToEmpty, Type: Feature, ReportID: 0x19, Offset: 0, Size: 16, Value: 2340.000000 Path: UPS.Battery.Temperature, Type: Feature, ReportID: 0x1e, Offset: 0, Size: 16, Value: 294.700000 Path: UPS.Battery.ConfigVoltage, Type: Feature, ReportID: 0x1f, Offset: 0, Size: 16, Value: 24.000000 Path: UPS.Battery.Voltage, Type: Feature, ReportID: 0x1d, Offset: 0, Size: 16, Value: 27.400000 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x20, Offset: 0, Size: 16, Value: 234.700000 Path: UPS.Input.ff860052, Type: Input, ReportID: 0x21, Offset: 0, Size: 8, Value: 5.000000 Path: UPS.Input.ff860052, Type: Feature, ReportID: 0x21, Offset: 0, Size: 8, Value: 5.000000 Path: UPS.Input.ff860061, Type: Input, ReportID: 0x22, Offset: 0, Size: 8, Value: 2.000000 Path: UPS.Input.ff860061, Type: Feature, ReportID: 0x22, Offset: 0, Size: 8, Value: 2.000000 Path: UPS.Output.PercentLoad, Type: Feature, ReportID: 0x2c, Offset: 0, Size: 16, Value: 29.900000 Path: UPS.Output.Frequency, Type: Feature, ReportID: 0x2a, Offset: 0, Size: 16, Value: 50.000000 Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x2b, Offset: 0, Size: 16, Value: 234.700000 Path: UPS.Output.ConfigVoltage, Type: Input, ReportID: 0x2d, Offset: 0, Size: 16, Value: 230.000000 Path: UPS.Output.ConfigVoltage, Type: Feature, ReportID: 0x2d, Offset: 0, Size: 16, Value: 230.000000 Path: UPS.Output.HighVoltageTransfer, Type: Input, ReportID: 0x23, Offset: 0, Size: 16, Value: 253.000000 Path: UPS.Output.HighVoltageTransfer, Type: Feature, ReportID: 0x23, Offset: 0, Size: 16, Value: 253.000000 Path: UPS.Output.LowVoltageTransfer, Type: Input, ReportID: 0x24, Offset: 0, Size: 16, Value: 208.000000 Path: UPS.Output.LowVoltageTransfer, Type: Feature, ReportID: 0x24, Offset: 0, Size: 16, Value: 208.000000 Path: UPS.Output.APCDelayBeforeStartup, Type: Input, ReportID: 0x25, Offset: 0, Size: 16, Value: 60.000000 Path: UPS.Output.APCDelayBeforeStartup, Type: Feature, ReportID: 0x25, Offset: 0, Size: 16, Value: 60.000000 Path: UPS.Output.APCShutdownAfterDelay, Type: Input, ReportID: 0x26, Offset: 0, Size: 16, Value: 90.000000 Path: UPS.Output.APCShutdownAfterDelay, Type: Feature, ReportID: 0x26, Offset: 0, Size: 16, Value: 90.000000 Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID: 0x27, Offset: 0, Size: 16, Value: -1.000000 Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID: 0x28, Offset: 0, Size: 16, Value: -1.000000 Path: UPS.Output.DelayBeforeReboot, Type: Feature, ReportID: 0x29, Offset: 0, Size: 24, Value: -1.000000 Path: UPS.iProduct, Type: Feature, ReportID: 0x2e, Offset: 0, Size: 8, Value: 5.000000 Path: UPS.iSerialNumber, Type: Feature, ReportID: 0x2f, Offset: 0, Size: 8, Value: 2.000000 Path: UPS.iManufacturer, Type: Feature, ReportID: 0x30, Offset: 0, Size: 8, Value: 3.000000 Path: UPS.iName, Type: Feature, ReportID: 0x31, Offset: 0, Size: 8, Value: 6.000000 Path: UPS.APC_UPS_FirmwareRevision, Type: Feature, ReportID: 0x34, Offset: 0, Size: 8, Value: 7.000000 Path: UPS.APC_USB_FirmwareRevision, Type: Feature, ReportID: 0x37, Offset: 0, Size: 8, Value: 8.000000 Path: UPS.APCPanelTest, Type: Feature, ReportID: 0x32, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.ManufacturerDate, Type: Feature, ReportID: 0x35, Offset: 0, Size: 16, Value: 13534.000000 Path: UPS.ff860027, Type: Feature, ReportID: 0x3e, Offset: 0, Size: 32, Value: 0.000000 Path: UPS.ff860028, Type: Feature, ReportID: 0x3f, Offset: 0, Size: 32, Value: 0.000000 Path: UPS.AudibleAlarmControl, Type: Input, ReportID: 0x36, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.AudibleAlarmControl, Type: Feature, ReportID: 0x36, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.PresentStatus.Charging, Type: Input, ReportID: 0x33, Offset: 0, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.Charging, Type: Feature, ReportID: 0x33, Offset: 0, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.Discharging, Type: Input, ReportID: 0x33, Offset: 1, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.Discharging, Type: Feature, ReportID: 0x33, Offset: 1, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.ACPresent, Type: Input, ReportID: 0x33, Offset: 2, Size: 1, Value: 1.000000 Path: UPS.PresentStatus.ACPresent, Type: Feature, ReportID: 0x33, Offset: 2, Size: 1, Value: 1.000000 Path: UPS.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x33, Offset: 3, Size: 1, Value: 1.000000 Path: UPS.PresentStatus.BatteryPresent, Type: Feature, ReportID: 0x33, Offset: 3, Size: 1, Value: 1.000000 Path: UPS.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x33, Offset: 4, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x33, Offset: 4, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.ShutdownRequested, Type: Input, ReportID: 0x33, Offset: 5, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.ShutdownRequested, Type: Feature, ReportID: 0x33, Offset: 5, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x33, Offset: 6, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.ShutdownImminent, Type: Feature, ReportID: 0x33, Offset: 6, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x33, Offset: 7, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.RemainingTimeLimitExpired, Type: Feature, ReportID: 0x33, Offset: 7, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.CommunicationLost, Type: Input, ReportID: 0x33, Offset: 8, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.CommunicationLost, Type: Feature, ReportID: 0x33, Offset: 8, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x33, Offset: 9, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.NeedReplacement, Type: Feature, ReportID: 0x33, Offset: 9, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.Overload, Type: Input, ReportID: 0x33, Offset: 10, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.Overload, Type: Feature, ReportID: 0x33, Offset: 10, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.VoltageNotRegulated, Type: Input, ReportID: 0x33, Offset: 11, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.VoltageNotRegulated, Type: Feature, ReportID: 0x33, Offset: 11, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.ff860080, Type: Input, ReportID: 0x33, Offset: 12, Size: 1, Value: 0.000000 Path: UPS.PresentStatus.ff860080, Type: Feature, ReportID: 0x33, Offset: 12, Size: 1, Value: 0.000000 Detected a UPS: American Power Conversion/Smart-UPS 750 RM FW:619.3.I USB FW:8.1 On Wednesday 02 September 2009 16:44:21 you wrote:> 2009/9/2 Markus Wildi <wildi.markus at bluewin.ch> > > > Hello > > > > I recently switched from apcupsd to NUT2.2.2 without > > any troubles. > > > > I tried to figure out how I can configure the self-test > > intervall. The command upsrw lists only the variables > > > > battery.charge.low > > battery.runtime.low > > ups.delay.shutdown > > ups.delay.start > > > > The command usbhid-ups -D and the listing under > > > > > > http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart at localhost&tre > >emode > > > > show no hint on appropriate variable. > > > > I scanned to log files and found no hint on successfull self-test. > > it seems APC doesn't support this, or at least we have nothing mapped for > this. > for example, on Eaton / MGE units, we have > "UPS.BatterySystem.Battery.TestPeriod" mapped to "ups.test.interval" > > to validate this, please upgrade to a more recent version (ie 2.4.1) and > post back the output of usbhid-ups -D > > cheers, > Arnaud
Arnaud Quette
2009-Sep-03 12:00 UTC
[Nut-upsuser] Selftest intervall, APC Smart-UPS 750 RM
2009/9/2 Markus Wildi <wildi.markus at bluewin.ch>> Hello Arnaud > >Hi Markus, thanks for having cc'ed the list ;-)> I compiled the source of nut-2.4.1 and you'll > find the output of usbhid-ups -D -a apcsmart > below. > > The UPS did regularly report a self-test while > running under apcupsd. It reports in addition > e.g. the last reason for a on battery event. >if apcupsd can do it, NUT can do it too ;-) the last self test report should already be available through ups.test.result (linked to the HID path UPS.Battery.Test, with the current value "No test initiated"). I've just commited a patch that adds: - input.transfer.reason - input.sensitivity (which is settable) can you test the development version (Subversion trunk, r1952) to validate this. Some helpful info are available here: http://buildbot.ghz.cc/~buildbot/docs/r1950-97/website/download.html please send back an upsc output too. if you still see differences with apcupsd, please tell me back. It's quite possible that I've missed something more about how APC units work. (...)>thanks for these data. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090903/4ad119db/attachment.htm>
Hello I'm now at r1957 and I find no input.transfer.reason in the output of upsc. usbhid-ups -DDDDD -a apcsmart shows no UPS.BatterySystem.Battery.TestPeriod ups.test.interval Hope that helps, bye wildi On Friday 04 September 2009 10:28:48 you wrote:> 2009/9/3 Arjen de Korte > > > Citeren Arnaud Quette > > > > strange indeed. the data is there, and now know. > > > >> I've made a minor fix (r1955). > >> please test it and tell me back if input.transfer.reason appears now. > > > > No, it won't. The 'input.transfer.reason' value is set through the VRANGE > > and FRANGE status bits. In the absence of either, it will be cleared. > > Therefor, you can't treat this as an ordinary variable. There are HID PDC > > fields that use these, so we'll have to be careful to change this in > > order not to break other subdrivers in the process. > > ooch, right! I completely missed that. thanks for pointing it Arjen ;-) > > I just commited a fix (r1956): it only reports voltage or frequency out of > range, and not over/under voltage / ripple / force / selftest as it was in > the previous version. > Is it fine like that Markus? > > cheers, > Arnaud
Arnaud Quette
2009-Sep-04 16:36 UTC
[Nut-upsuser] Selftest intervall, APC Smart-UPS 750 RM
2009/9/4 Markus Wildi> Hello >Hi> I'm now at r1957 and I find no input.transfer.reason >ah, blind development... please send me the debug output (level 5) of the driver.> in the output of upsc. > > usbhid-ups -DDDDD -a apcsmart shows no > > UPS.BatterySystem.Battery.TestPeriod > > ups.test.interval >you might have misunderstood me: I've not found anything (in the HID dump nor in apcupsd) that shows that this variable exist. it may be in the remaining unknown/unmapped data (prefixed by ff86). do you have access to this settings in powerchute or apcupsd? cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090904/564a305c/attachment.htm>
Arnaud Quette
2009-Sep-06 13:44 UTC
[Nut-upsuser] Selftest intervall, APC Smart-UPS 750 RM
2009/9/5 Markus Wildi> Good morning Arnaud >hi Markus> find attached the output of the driver (debug level 5). > > > Here is an output of apcupsd command apcaccess status > > > https://azug.minpet.unibas.ch/wikiobsvermes/index.php/Apcupsd#Useful_Commands > > Have a look at > LASTXFER : Low line voltage > > and here an excerpt of the log file > > Feb 19 17:28:51 obsvermes apcupsd[2055]: UPS Self Test switch to battery. > Feb 19 17:28:58 obsvermes apcupsd[2055]: UPS Self Test completed: Battery > OK > >ok, I see why: currently, there are few values that are not mapped due to the boolean mechanism used in usbhid-ups to process (either outvolt or outfreq or nothing). these values are commented in the code (your unit is currently reporting "5 => self test"): /* these input.transfer.reason can't be mapped at the moment... */ { 3, "ripple", NULL }, /* Ripple */ { 5, "self test", NULL }, /* Self Test or Discharge Calibration commanded * Test usage, front button, or 2 week self test */ { 6, "forced", NULL }, /* DelayBeforeShutdown or APCDelayBeforeShutdown */ { 10, "forced", NULL }, /* Graceful shutdown by accessories */ { 11, "self test", NULL }, /* Test usage invoked */ { 12, "self test", NULL }, /* Front button initiated self test */ { 13, "self test", NULL }, /* 2 week self test */ adding support for these would means changing some more code, and I'm not sure it's forth just for reporting the above... moreover, the data you reported are not coherent: considering the log file, LASTXFER should have the value "Self Test" and not "Low line voltage"... just to be sure, apart from transfer.reason, everything is equivalent to apcupsd? btw, what is that eeprom thing in apcupsd? is it equivalent to upsrw? cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090906/6b4e7fab/attachment.htm>