[Nut-upsuser] Powerware Prestige 1000VA
Hi all, I've more-or-less got NUT 2.0.4 working with my Powerware Prestige 1000VA UPS (serial), but unfortunately NUT is flagging LOW_BATTERY continuously, which is a tad embarrassing when power fails ;-) The numbers from upsc [EMAIL PROTECTED] seem reasonable: ambient.temperature: 24.5 battery.charge: 99 battery.runtime: 3999 battery.voltage: 69.2 driver.name: bcmxcp driver.parameter.port: /dev/ttyS0 driver.version: 2.0.4 driver.version.internal: 0.10 input.frequency: 50.0 input.voltage: 239.0 output.frequency: 50.0 ups.firmware: 02.07 ups.load: 0.2 ups.model: Powerware Prestige 1000VA ups.power.nominal: 1000 ups.serial: ** ups.status: OL LB ups.voltage.nominal: 240 but I suspect the 'LB' in ups.status is the clue. Does this indicate low battery? I'm curious as the battery charge is shown as 99% and the battery voltage is OK (for the 5x 12V batteries is has). Could it be the battery pack has failed self-test? Any clues gratefully received! ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware Prestige 1000VA
Hi, lör 2007-05-19 klockan 14:24 +0100 skrev [EMAIL PROTECTED]: Hi all, I've more-or-less got NUT 2.0.4 working with my Powerware Prestige 1000VA UPS (serial), but unfortunately NUT is flagging LOW_BATTERY continuously, which is a tad embarrassing when power fails ;-) Can you upgrade to 2.0.5, or any better if you can use the svn trunk. There is a bug in 2.0.4 in the shutdown, so the shutdown delay would not work as expected. And in 2.0.5 I use the topologi block that is not present in older ups'es using the bcmxcp protocol. But this is fixed in the svn trunk. But the error you get come from another thing. Some powerware ups'es signaling the OB an LB via the alarm block. So the driver is made to check if the alarm is present, then it use this to set the LB status. There may be a different alarm-map in your ups. Start up the driver like this. /pat/to/bcmxcp -DD -a blah And sen me the output then i can see what alarms you have. The numbers from upsc [EMAIL PROTECTED] seem reasonable: ambient.temperature: 24.5 battery.charge: 99 battery.runtime: 3999 battery.voltage: 69.2 driver.name: bcmxcp driver.parameter.port: /dev/ttyS0 driver.version: 2.0.4 driver.version.internal: 0.10 input.frequency: 50.0 input.voltage: 239.0 output.frequency: 50.0 ups.firmware: 02.07 ups.load: 0.2 ups.model: Powerware Prestige 1000VA ups.power.nominal: 1000 ups.serial: ** ups.status: OL LB ups.voltage.nominal: 240 but I suspect the 'LB' in ups.status is the clue. Does this indicate low battery? I'm curious as the battery charge is shown as 99% and the battery voltage is OK (for the 5x 12V batteries is has). Could it be the battery pack has failed self-test? Any clues gratefully received! Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Powerware Prestige 1000VA
Hi, Kjell, Kjell Claesson wrote: Can you upgrade to 2.0.5, or any better if you can use the svn trunk. Thanks very much for your pointer. I'm currently trying to compile but it appears to be broken on my Debian (stable) system. The issue here is that the configure script appears to assume that both libgd and libXpm will be in the same place, but here libgd is indeed in /usr/lib, but libXpm is in /usr/X11R6/lib. I know how to fix that in a plain makefile (adding -L/usr/X11R6/lib just before -lXpm) but I'm not very good on autoconf stuff. Anyway, here's the list of alarms you asked about: ommunications with UPS re-established Shutdown delay = 120 seconds Index Offset Format NUT 001561 None 0021000461 None 0023000861 None 0027001261 output.frequency 0028001661 input.frequency 0029002061 None 0033002461 battery.voltage 00340028f0 battery.charge 00350032f0 battery.runtime 00360036f0 None 0056004061 input.voltage 0059004461 None 0062004861 ambient.temperature 0071005261 None 0074005661 None 0075006061 None Length of alarm map: 25 Index Alarm Supported INVERTER_AC_OVER_VOLTAGEYes 0001INVERTER_AC_UNDER_VOLTAGE Yes -001INVERTER_OVER_OR_UNDER_FREQ No -001BYPASS_AC_OVER_VOLTAGE No -001BYPASS_AC_UNDER_VOLTAGE No -001BYPASS_OVER_OR_UNDER_FREQ No 0002INPUT_AC_OVER_VOLTAGE Yes 0003INPUT_AC_UNDER_VOLTAGE Yes -001INPUT_UNDER_OR_OVER_FREQNo -001OUTPUT_OVER_VOLTAGE No -001OUTPUT_UNDER_VOLTAGENo -001OUTPUT_UNDER_OR_OVER_FREQ No -001REMOTE_EMERGENCY_PWR_OFFNo -001REMOTE_GO_TO_BYPASS No -001BUILDING_ALARM_6No -001BUILDING_ALARM_5No -001BUILDING_ALARM_4No -001BUILDING_ALARM_3No -001BUILDING_ALARM_2No -001BUILDING_ALARM_1No -001STATIC_SWITCH_OVER_TEMP No -001CHARGER_OVER_TEMP No -001CHARGER_LOGIC_PWR_FAIL No -001CHARGER_OVER_VOLTAGE_OR_CURRENT No 0004INVERTER_OVER_TEMP Yes 0005OUTPUT_OVERLOAD Yes 0006RECTIFIER_INPUT_OVER_CURRENTYes -001INVERTER_OUTPUT_OVER_CURRENTNo 0007DC_LINK_OVER_VOLTAGEYes 0008DC_LINK_UNDER_VOLTAGE Yes -001RECTIFIER_FAILEDNo -001INVERTER_FAULT No -001BATTERY_CONNECTOR_FAIL No -001BYPASS_BREAKER_FAIL No 0009CHARGER_FAILYes -001RAMP_UP_FAILED No -001STATIC_SWITCH_FAILEDNo -001ANALOG_AD_REF_FAIL No -001BYPASS_UNCALIBRATED No -001RECTIFIER_UNCALIBRATED No -001OUTPUT_UNCALIBRATED No -001INVERTER_UNCALIBRATED No -001DC_VOLT_UNCALIBRATEDNo -001OUTPUT_CURRENT_UNCALIBRATED No -001RECTIFIER_CURRENT_UNCALIBRATED No -001BATTERY_CURRENT_UNCALIBRATEDNo -001INVERTER_ON_OFF_STAT_FAIL No -001BATTERY_CURRENT_LIMIT No 0010INVERTER_STARTUP_FAIL Yes -001ANALOG_BOARD_AD_STAT_FAIL No 0011OUTPUT_CURRENT_OVER_100 Yes -001BATTERY_GROUND_FAULTNo -001WAITING_FOR_CHARGER_SYNCNo -001NV_RAM_FAIL No -001ANALOG_BOARD_AD_TIMEOUT No -001SHUTDOWN_IMMINENT No -001BATTERY_LOW No 0012UTILITY_FAILYes -001OUTPUT_SHORT_CIRCUITNo -001UTILITY_NOT_PRESENT No -001FULL_TIME_CHARGING No -001FAST_BYPASS_COMMAND No -001AD_ERRORNo -001INTERNAL_COM_FAIL No -001RECTIFIER_SELFTEST_FAIL No -001RECTIFIER_EEPROM_FAIL No -001RECTIFIER_EPROM_FAILNo -001INPUT_LINE_VOLTAGE_LOSS No -001BATTERY_DC_OVER_VOLTAGE No -001POWER_SUPPLY_OVER_TEMP No -001POWER_SUPPLY_FAIL No -001POWER_SUPPLY_5V_FAILNo -001POWER_SUPPLY_12V_FAIL No -001HEATSINK_OVER_TEMP No -001HEATSINK_TEMP_SENSOR_FAIL No -001RECTIFIER_CURRENT_OVER_125 No -001RECTIFIER_FAULT_INTERRUPT_FAIL No -001RECTIFIER_POWER_CAPASITOR_FAIL No -001INVERTER_PROGRAM_STACK_ERRORNo -001INVERTER_BOARD_SELFTEST_FAILNo -001INVERTER_AD_SELFTEST_FAIL No -001INVERTER_RAM_SELFTEST_FAIL No -001NV_MEMORY_CHECKSUM_FAIL No -001PROGRAM_CHECKSUM_FAIL No -001INVERTER_CPU_SELFTEST_FAIL No -001NETWORK_NOT_RESPONDING No -001FRONT_PANEL_SELFTEST_FAIL No -001NODE_EEPROM_VERIFICATION_ERROR No -001OUTPUT_AC_OVER_VOLT_TEST_FAIL No -001OUTPUT_DC_OVER_VOLTAGE No 0013INPUT_PHASE_ROTATION_ERROR Yes -001INVERTER_RAMP_UP_TEST_FAILEDNo -001INVERTER_OFF_COMMANDNo -001INVERTER_ON_COMMAND No -001TO_BYPASS_COMMAND No -001FROM_BYPASS_COMMAND No -001AUTO_MODE_COMMAND No -001EMERGENCY_SHUTDOWN_COMMAND No -001SETUP_SWITCH_OPEN No -001INVERTER_OVER_VOLT_INT No -001
