On Monday 25 October 2010 22:19:44 Arjen de Korte wrote: > First thing for you to try is if the blazer_usb driver is able to > communicate with your UPS.
thank you very much for all hints. i've read manuals, setup configs with blazer_usb driver and tested hardware today's morning. generally, it works in 99%... quering works: # upsc orvaldi battery.voltage: 13.50 battery.voltage.nominal: 12.0 beeper.status: enabled device.mfr: device.model: device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: port_config_value_is_unused_in_usb_drivers driver.version: 2.4.3 driver.version.internal: 0.03 input.current.nominal: 3.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 238.0 input.voltage.fault: 238.0 input.voltage.nominal: 230 output.voltage: 238.0 ups.delay.shutdown: 30 ups.delay.start: 180 ups.firmware: V1.13APO-E ups.load: 31 ups.mfr: ups.model: ups.productid: 5161 ups.status: OL ups.temperature: 45.0 ups.type: offline / line interactive ups.vendorid: 0665 closing system on low-battery works: Oct 26 07:37:55 localhost blazer_usb[3188]: Startup successful Oct 26 07:37:55 localhost upsd[3195]: listening on 127.0.0.1 port 3493 Oct 26 07:37:55 localhost upsd[3195]: listening on ::1 port 3493 Oct 26 07:37:55 localhost upsd[3195]: Connected to UPS [orvaldi]: blazer_usb-orvaldi Oct 26 07:37:55 localhost upsd[3196]: Startup successful Oct 26 07:37:59 localhost upsmon[3155]: Poll UPS [orva...@localhost] failed - Write error: Broken pipe Oct 26 07:37:59 localhost upsmon[3155]: Communications with UPS orva...@localhost lost Oct 26 07:38:00 localhost upsmon[3155]: Signal 15: exiting Oct 26 07:38:00 localhost upsmon[3154]: upsmon parent: read Oct 26 07:38:00 localhost upsmon[3228]: Startup successful Oct 26 07:38:00 localhost upsd[3196]: User [email protected] logged into UPS [orvaldi] Oct 26 07:40:00 localhost upsmon[3229]: UPS orva...@localhost on battery Oct 26 07:40:24 localhost blazer_usb[3188]: Communications with UPS lost: status read failed! Oct 26 07:40:26 localhost blazer_usb[3188]: Communications with UPS re-established Oct 26 07:41:42 localhost blazer_usb[3188]: Communications with UPS lost: status read failed! Oct 26 07:41:44 localhost blazer_usb[3188]: Communications with UPS re-established (...) but has some communications problems... (...) Oct 26 07:55:08 localhost blazer_usb[3188]: Communications with UPS lost: status read failed! Oct 26 07:55:10 localhost blazer_usb[3188]: Communications with UPS re-established Oct 26 07:55:15 localhost upsmon[3229]: UPS orva...@localhost battery is low Oct 26 07:55:15 localhost upsd[3196]: Client [email protected] set FSD on UPS [orvaldi] Oct 26 07:55:15 localhost upsmon[3229]: Executing automatic power-fail shutdown Oct 26 07:55:15 localhost upsmon[3229]: Auto logout and shutdown proceeding Oct 26 07:55:20 localhost init: Switching to runlevel: 0 and finally, during idle daytime it crashes silently twice: [14133.306369] blazer_usb[2349]: segfault at 0 ip 0000000000402a8c sp 00007fff6b833f80 error 4 in blazer_usb[400000+10000] [21514.196361] blazer_usb[18593]: segfault at 0 ip 0000000000402a8c sp 00007fff552a90b0 error 4 in blazer_usb[400000+10000] _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
