[Nut-upsdev] Question on weird output from a Compaq R3000

[Ted Mittelstaedt]

Hi All,

   I'm still getting periodic errors from my Compaq UPS and the upscode2
driver.  Here's a recent log for example:

Sep 28 18:04:33 mail upscode2[90734]: Unknown response to UPDS: .00 MIUL1
Sep 28 18:04:34 mail upscode2[90734]: Unknown response to UPDS: 0119.10 
MBUUU
Sep 28 18:04:34 mail upscode2[90734]: Unknown response to UPDS: 0050.80 
MOUL1
Sep 28 18:04:34 mail upscode2[90734]: Unknown response to UPDS: 0119.10 
MOIL1
Sep 28 18:04:34 mail upscode2[90734]: Unknown response to UPDS: 0015.50 
MOPL1
Sep 28 18:04:34 mail upscode2[90734]: Unknown response to UPDS: 0001.82 
MOSL1
Sep 28 18:04:34 mail upscode2[90734]: Unknown response to UPDS: 0001.83 
MOFFF
Sep 28 18:04:37 mail upscode2[90734]: Communications with UPS lost: 
Empty value from UPS for UPDS 0060.00!
Sep 28 18:04:37 mail upsd[90736]: Data for UPS [R3000] is stale - check 
driver
Sep 28 18:04:41 mail upscode2[90734]: Communications with UPS re-established
Sep 28 18:04:41 mail upsd[90736]: UPS [R3000] data is no longer stale


   I did some digging and in the Eaton Protocol Library here:

http://old.networkupstools.org/protocols/eaton/

   I looked through the UPScode II Concept Description and it lists the
codes below that are "unknown response"  They are as follows:

.00 MIUL1  :  INPUT VOLTAGE PHASE L1 * : actual measurement value

0119.10 MBUUU  :  BATTERY VOLTAGE  : actual measurement value

0050.80 MOUL1  :  OUTPUT VOLTAGE PHASE L1 * : actual measurement value

0119.10 MOIL1  :  OUTPUT CURRENT PHASE L1 *  :  actual measurement value

0015.50 MOPL1  :  OUTPUT KW PHASE L1 *  : calculated value

0001.82 MOSL1  :  OUTPUT KVA PHASE L1 * : calculated value

0001.83 MOFFF  :  OUTPUT FREQUENCY  :  actual measurement value

   Anyway, if you look you will see that the values associated with the 
codes are offset - the starting .00 is a value for some unknown code, 
then the 0119.10 is the value for the input voltage, then the 0050.80 is 
the value for the battery voltage, the 0119.10 is then the output
voltage value, and so on.

   It looks to me like somehow the communication between NUT and the UPS
is getting out of sync - some response perhaps isn't issuing a correct
value or other - then the upscode2 driver eventually stumbles on a 
command and issues the "Empty value from UPS for UPDS" which is a dump 
command, then the "Data for UPS is stale" error message and then 
re-initializes the communications and then everything is good again.

   Since this is happening when the battery alarm light goes on my guess
is the UPS's self test is happening then issuing something to the NUT 
driver that isn't being parsed properly.  Does anyone have any 
suggestions on figuring this out?

   And, the ups DOES support the load when power is shut down.  So,
why is the UPS showing a battery alarm when it self-tests?

Ted

On 9/22/2013 4:34 PM, Ted Mittelstaedt wrote:
> Hi All,
>
> I put my Compaq R3000 UPS on NUT.
>
> Every once in a while the battery alarm light turns on, on the front of
> the UPS. Maybe once every couple of days or so. When that happens
> I get the following output in /var/log/messages:
>
> Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: .20 MOUL1
> Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: 0119.20
> MOIL1
> Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: 0015.57
> MOPL1
> Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: 0001.82
> MOSL1
> Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: 0001.83
> MOFFF
> Sep 22 01:51:49 mail upscode2[90734]: Communications with UPS lost:
> Empty value from UPS for UPDS 0060.00!
> Sep 22 01:51:49 mail upsd[90736]: Data for UPS [R3000] is stale - check
> driver
> Sep 22 01:51:53 mail upscode2[90734]: Communications with UPS
> re-established
> Sep 22 01:51:53 mail upsd[90736]: UPS [R3000] data is no longer stale
>
>
> I just replaced the batteries in this UPS about 5 months ago. Does the
> fact that battery.charge equal 92.7 have anything to do with this?
>
> Here's the status output:
>
> root at mail:/var/log # upsc R3000 at localhost
> battery.capacity.nominal: 17.00
> battery.charge: 92.7
> battery.runtime: 420
> battery.voltage: 55.20
> battery.voltage.maximum: 56.40
> battery.voltage.minimum: 40.00
> battery.voltage.nominal: 48.00
> device.mfr: unknown
> device.model: UPS 3000 VA FW -0026
> device.serial: E00202401
> device.type: ups
> driver.name: upscode2
> driver.parameter.pollinterval: 2
> driver.parameter.port: /dev/cuau0
> driver.version: 2.6.5
> driver.version.internal: 0.88
> input.phases: 1
> input.voltage: 121.00
> input.voltage.maximum: 145.00
> input.voltage.minimum: 84.00
> input.voltage.nominal: 120.00
> output.current: 15.15
> output.current.maximum: 28.50
> output.current.nominal: 25.00
> output.frequency: 60.00
> output.frequency.maximum: 63.00
> output.frequency.minimum: 57.00
> output.phases: 1
> output.power: 1.82
> output.realpower: 1810.00
> output.realpower.nominal: 2250.00
> output.voltage: 121.00
> output.voltage.maximum: 128.00
> output.voltage.minimum: 108.00
> output.voltage.nominal: 120.00
> ups.delay.reboot: 060
> ups.delay.shutdown: 180
> ups.load: 60.6
> ups.mfr: unknown
> ups.model: UPS 3000 VA FW -0026
> ups.power.nominal: 3000.00
> ups.serial: E00202401
> ups.status: OL
> root at mail:/var/log #
>
>
> Thanks,
> Ted