Re: [Nut-upsuser] APC Smart-UPS 1000

2011-01-22 Thread Arjen de Korte

Citeren Kevin bakd...@gmail.com:

I'm posting the debug file again in case it gives any more clues.  I  
modified the version number to make sure I was actually using the  
patched driver. I don't know, but these lines may be significant:


# grep Value: 90 APC-1000.patched.txt
  1.397898 Path: UPS.Output.APCShutdownAfterDelay, Type: Input,  
ReportID: 0x26, Offset: 0, Size: 16, Value: 90
  1.397898 Path: UPS.Output.APCShutdownAfterDelay, Type:  
Feature, ReportID: 0x26, Offset: 0, Size: 16, Value: 90


Does this mean the value has not changed?


Sorry for the confusion. Yes the value hasn't changed, but I didn't  
expect that to happen. It should however be modifiable through  
'upsrw', so that you might be able to set it to a lower value.


In the usbhid-ups driver, the 'ups.delay.(start|shutdown|reboot)'  
values are driver variables. They are only send to the UPS when you  
initiate the corresponding command. However, on the APC it seems to be  
possible (mandatory) to store them in the UPS itself.


So try if you can change this value through upsrw to something like 20  
seconds and lower the 'offdelay' value to 30 seconds.


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


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] APC Smart-UPS 1000

2011-01-22 Thread Kevin

on 22/01/2011 15:35 Arjen de Korte wrote:

Sorry for the confusion. Yes the value hasn't changed, but I didn't 
expect that to happen. It should however be modifiable through 'upsrw', 
so that you might be able to set it to a lower value.


In the usbhid-ups driver, the 'ups.delay.(start|shutdown|reboot)' values 
are driver variables. They are only send to the UPS when you initiate 
the corresponding command. However, on the APC it seems to be possible 
(mandatory) to store them in the UPS itself.


So try if you can change this value through upsrw to something like 20 
seconds and lower the 'offdelay' value to 30 seconds.


I don't pretend to understand this fully at the moment, the 
driver.parameter.offdelay is set to 1, as is the ups.delay.shutdown:


# ./clients/upsc apc1500
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2007/07/07
battery.runtime: 5880
battery.runtime.low: 120
battery.temperature: 32.4
battery.type: PbAc
battery.voltage: 27.4
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1000
device.serial: AS0727233122
device.type: ups
driver.name: usbhid-ups
driver.parameter.offdelay: 1
driver.parameter.ondelay: 250
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.0
driver.version.data: APC HID 0.95-patched
driver.version.internal: 0.35
input.sensitivity: high
input.voltage: 230.4
output.voltage: 230.4
output.voltage.nominal: 230.0
ups.beeper.status: disabled
ups.delay.shutdown: 1
ups.delay.start: 250
ups.firmware: 652.13.I
ups.firmware.aux: 7.3
ups.load: 5.8
ups.mfr: American Power Conversion
ups.mfr.date: 2007/07/07
ups.model: Smart-UPS 1000
ups.productid: 0002
ups.serial: AS0727233122
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.timer.start: -1
ups.vendorid: 051d

#./clients/upsrw -s ups.delay.shutdown=30 -u apcmon -p pass123 apc1500
OK

This sets it to 30:

# ./clients/upsc apc1500
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2007/07/07
battery.runtime: 5880
battery.runtime.low: 120
battery.temperature: 32.4
battery.type: PbAc
battery.voltage: 27.4
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1000
device.serial: AS0727233122
device.type: ups
driver.name: usbhid-ups
driver.parameter.offdelay: 1
driver.parameter.ondelay: 250
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.0
driver.version.data: APC HID 0.95-patched
driver.version.internal: 0.35
input.sensitivity: high
input.voltage: 230.4
output.voltage: 230.4
output.voltage.nominal: 230.0
ups.beeper.status: disabled
ups.delay.shutdown: 30
ups.delay.start: 250
ups.firmware: 652.13.I
ups.firmware.aux: 7.3
ups.load: 5.8
ups.mfr: American Power Conversion
ups.mfr.date: 2007/07/07
ups.model: Smart-UPS 1000
ups.productid: 0002
ups.serial: AS0727233122
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.timer.start: -1
ups.vendorid: 051d

but doesn't affect the initial value of ups.timer.shutdown (90) after 
the shutdown.return command:


# ./clients/upscmd -u apcmon -p pass123 apc1500 shutdown.return
OK

# ./clients/upsc apc1500
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2007/07/07
battery.runtime: 5880
battery.runtime.low: 120
battery.temperature: 32.4
battery.type: PbAc
battery.voltage: 27.0
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1000
device.serial: AS0727233122
device.type: ups
driver.name: usbhid-ups
driver.parameter.offdelay: 1
driver.parameter.ondelay: 250
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.0
driver.version.data: APC HID 0.95-patched
driver.version.internal: 0.35
input.sensitivity: high
input.voltage: 230.4
output.voltage: 229.6
output.voltage.nominal: 230.0
ups.beeper.status: disabled
ups.delay.shutdown: 30
ups.delay.start: 250
ups.firmware: 652.13.I
ups.firmware.aux: 7.3
ups.load: 5.8
ups.mfr: American Power Conversion
ups.mfr.date: 2007/07/07
ups.model: Smart-UPS 1000
ups.productid: 0002
ups.serial: AS0727233122
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: 82
ups.timer.start: 242
ups.vendorid: 051d


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


[Nut-upsuser] Building and configuring nut 2.6.0 - documentation issue?

2011-01-22 Thread Mike.

This morning I finished building and configuring nut 2.6.0 on OpenBSD
4.8, and it is running fine.

While I was in the config files, I noticed what looks like it may be a
discrepancy between the config file commetns and the configure script
default.

uspd.conf has the following comment:

# STATEPATH path
# STATEPATH /var/run/nut
#
# Tell upsd to look for the driver state sockets in 'path' rather
# than the default that was compiled into the program.




When I read that, I thought the default path compiled into the program
would be /var/run/nut

However, configure --help shows the following:


 --with-statepath=PATH   path for ups state files (/var/state/ups)



implying that /var/state/ups was the default.


Am I reading this incorrectly, or is there a [minor] discrepancy?

Thanks.





___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] APC Smart-UPS 1000

2011-01-22 Thread Arjen de Korte

Citeren Kevin bakd...@gmail.com:

[...]

but doesn't affect the initial value of ups.timer.shutdown (90)  
after the shutdown.return command:


# ./clients/upscmd -u apcmon -p pass123 apc1500 shutdown.return
OK

# ./clients/upsc apc1500
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2007/07/07
battery.runtime: 5880
battery.runtime.low: 120
battery.temperature: 32.4
battery.type: PbAc
battery.voltage: 27.0
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1000
device.serial: AS0727233122
device.type: ups
driver.name: usbhid-ups
driver.parameter.offdelay: 1
driver.parameter.ondelay: 250
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.0
driver.version.data: APC HID 0.95-patched
driver.version.internal: 0.35
input.sensitivity: high
input.voltage: 230.4
output.voltage: 229.6
output.voltage.nominal: 230.0
ups.beeper.status: disabled
ups.delay.shutdown: 30
ups.delay.start: 250
ups.firmware: 652.13.I
ups.firmware.aux: 7.3
ups.load: 5.8
ups.mfr: American Power Conversion
ups.mfr.date: 2007/07/07
ups.model: Smart-UPS 1000
ups.productid: 0002
ups.serial: AS0727233122
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: 82
ups.timer.start: 242
ups.vendorid: 051d


Could you try this again with

  { ups.delay.shutdown, ST_FLAG_RW | ST_FLAG_STRING, 10,  
UPS.Output.APCShutdownAfterDelay, NULL, %.0f, HU_FLAG_SEMI_STATIC,  
NULL },


changed to

  { ups.delay.shutdown, ST_FLAG_RW | ST_FLAG_STRING, 10,  
UPS.Output.APCShutdownAfterDelay, NULL, %.0f, HU_FLAG_QUICK_POLL,  
NULL },


and run this test again? I'm not sure if the value is actually  
modified in the UPS. I fear that the HU_FLAG_SEMI_STATIC flag may have  
prevented the driver from reading back the value from the UPS.


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


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] APC Smart-UPS 1000

2011-01-22 Thread Kevin

on 23/01/2011 03:41 Arjen de Korte wrote:


Could you try this again with

  { ups.delay.shutdown, ST_FLAG_RW | ST_FLAG_STRING, 10, 
UPS.Output.APCShutdownAfterDelay, NULL, %.0f, HU_FLAG_QUICK_POLL, 
NULL },


and run this test again?


Sure...

#define APC_HID_VERSION APC HID 0.95-patch2
[...]
  { ups.timer.start, 0, 0, UPS.PowerSummary.DelayBeforeStartup, 
NULL, %.0f, HU_FLAG_QUICK_POLL, NULL},
  { ups.timer.shutdown, 0, 0, UPS.PowerSummary.DelayBeforeShutdown, 
NULL, %.0f, HU_FLAG_QUICK_POLL, NULL},
  { ups.timer.reboot, 0, 0, UPS.PowerSummary.DelayBeforeReboot, 
NULL, %.0f, HU_FLAG_QUICK_POLL, NULL},

  /* used by APC SmartUPS RM */
  { ups.delay.start, ST_FLAG_RW | ST_FLAG_STRING, 10, 
UPS.Output.DelayBeforeStartup, NULL, DEFAULT_ONDELAY, HU_FLAG_ABSENT, 
NULL},
  { ups.delay.shutdown, ST_FLAG_RW | ST_FLAG_STRING, 10, 
UPS.Output.APCShutdownAfterDelay, NULL, %.0f, HU_FLAG_QUICK_POLL, 
NULL },
  { ups.delay.shutdown, ST_FLAG_RW | ST_FLAG_STRING, 10, 
UPS.Output.DelayBeforeShutdown, NULL, DEFAULT_OFFDELAY, 
HU_FLAG_ABSENT, NULL},
  { ups.timer.start, 0, 0, UPS.Output.DelayBeforeStartup, NULL, 
%.0f, HU_FLAG_QUICK_POLL, NULL},



The ups.delay.shutdown value starts at what is set in the ups.conf (1):

# ./clients/upsc apc1500
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2007/07/07
battery.runtime: 5880
battery.runtime.low: 120
battery.temperature: 32.8
battery.type: PbAc
battery.voltage: 27.4
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1000
device.serial: AS0727233122
device.type: ups
driver.name: usbhid-ups
driver.parameter.offdelay: 1
driver.parameter.ondelay: 250
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.0
driver.version.data: APC HID 0.95-patch2
driver.version.internal: 0.35
input.sensitivity: high
input.voltage: 228.9
output.voltage: 228.9
output.voltage.nominal: 230.0
ups.beeper.status: disabled
ups.delay.shutdown: 1
ups.delay.start: 250
ups.firmware: 652.13.I
ups.firmware.aux: 7.3
ups.load: 5.8
ups.mfr: American Power Conversion
ups.mfr.date: 2007/07/07
ups.model: Smart-UPS 1000
ups.productid: 0002
ups.serial: AS0727233122
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.timer.start: -1
ups.vendorid: 051d

And I can change what is reported by upsc with:

# ./clients/upsrw -s ups.delay.shutdown=30 -u apcmon -p pass123 apc1500
OK

# ./clients/upsc apc1500
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2007/07/07
battery.runtime: 5880
battery.runtime.low: 120
battery.temperature: 32.8
battery.type: PbAc
battery.voltage: 27.4
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1000
device.serial: AS0727233122
device.type: ups
driver.name: usbhid-ups
driver.parameter.offdelay: 1
driver.parameter.ondelay: 250
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.0
driver.version.data: APC HID 0.95-patch2
driver.version.internal: 0.35
input.sensitivity: high
input.voltage: 230.4
output.voltage: 230.4
output.voltage.nominal: 230.0
ups.beeper.status: disabled
ups.delay.shutdown: 30
ups.delay.start: 250
ups.firmware: 652.13.I
ups.firmware.aux: 7.3
ups.load: 5.8
ups.mfr: American Power Conversion
ups.mfr.date: 2007/07/07
ups.model: Smart-UPS 1000
ups.productid: 0002
ups.serial: AS0727233122
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.timer.start: -1
ups.vendorid: 051d


But this doesn't affect the minimum timer.shutdown value:

# ./clients/upscmd -u apcmon -p pass123 apc1500 shutdown.return
OK

# ./clients/upsc apc1500
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2007/07/07
battery.runtime: 5880
battery.runtime.low: 120
battery.temperature: 32.8
battery.type: PbAc
battery.voltage: 27.0
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1000
device.serial: AS0727233122
device.type: ups
driver.name: usbhid-ups
driver.parameter.offdelay: 1
driver.parameter.ondelay: 250
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.0
driver.version.data: APC HID 0.95-patch2
driver.version.internal: 0.35
input.sensitivity: high
input.voltage: 230.4
output.voltage: 229.6
output.voltage.nominal: 230.0
ups.beeper.status: disabled
ups.delay.shutdown: 30
ups.delay.start: 250
ups.firmware: 652.13.I
ups.firmware.aux: 7.3
ups.load: 5.8
ups.mfr: American Power Conversion
ups.mfr.date: 2007/07/07
ups.model: Smart-UPS 1000
ups.productid: 0002
ups.serial: AS0727233122
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: 84
ups.timer.start: 244
ups.vendorid: 051d

Regards,
Kevin.

___
Nut-upsuser mailing list