[Nut-upsdev] APC CyberFort 350 problems with newhidups

Justin Maggard jmaggard10 at hotmail.com
Tue Feb 28 23:54:17 UTC 2006 

That's exactly what I thought.  I was assured that those logs were during 
the power failure simulation test.  My plan now is to try using the older 
hidups driver, and have my contact over there retry the same power failure 
simulation.  He said he tried the same UPS connected to a Windows machine 
with the APC software, and it worked as expected.  I will post the results 
of the hidups test once I get them.

>From: selinger at mathstat.dal.ca (Peter Selinger)
>To: jmaggard10 at hotmail.com (Justin Maggard)
>CC: nut-upsdev at lists.alioth.debian.org
>Subject: Re: [Nut-upsdev] APC CyberFort 350 problems with newhidups
>Date: Tue, 28 Feb 2006 17:58:17 -0400 (AST)
>
>This is bizarre. The following five lines mean that the driver is
>processing data from the UPS, and very clearly the UPS is saying that
>it is not charging or discharging, that it is online (not on battery),
>that the battery is not low, and that shutdown is not imminent.
>
>process_status_info: !chrg
>process_status_info: !dischrg
>process_status_info: online
>process_status_info: !lowbatt
>process_status_info: !shutdownimm
>
>If the UPS is really sending this data *while* it is on battery, as
>you are saying, then something is really wrong - not with the driver,
>but with the UPS. I cannot think of any possible explanation for this,
>except that the UPS you are monitoring is not in fact the same one of
>which you pulled the power, or the UPS is buggy, or there is some
>really strange driver bug that only manifests itself with your UPS and
>nobody else's.
>
>Unsure how to proceed... -- Peter
>
>Justin Maggard wrote:
> >
> > The behavior on this one seems very reproducible.  It's as if the driver 
>has
> > no idea that the UPS status has changed.  Here is output from newhidups 
>-DD
> > during a simulated power failure.  I had someone just unplug the UPS 
>power
> > cord, and let the battery run down.  He let it run down until the beep
> > pattern changed, indicating the battery level reached the critical 
>point;
> > waited 30 seconds, and then plugged the power cord back in.
> > process_status_info never changes.  Here is the newhidups -DD output:
> > debug level is '2'
> > Checking device (0000/0000) (003/001)
> > - VendorID: 0000
> > - ProductID: 0000
> > - Manufacturer: unknown
> > - Product: USB UHCI Root Hub
> > - Serial Number: 5c001020
> > - Bus: 003
> > Trying to match device
> > Device does not match - skipping
> > Checking device (051D/0002) (003/002)
> > - VendorID: 051d
> > - ProductID: 0002
> > - Manufacturer: American Power Conversion
> > - Product: Back-UPS ES/CyberFort 350 FW: 3.1.I USB FW: d1
> > - Serial Number: AB0210142465
> > - Bus: 003
> > Trying to match device
> > Device matches
> > HID descriptor retrieved (Reportlen = 402)
> > Report descriptor retrieved (Reportlen = 402)
> > Found HID device
> > Network UPS Tools: New USB/HID UPS driver 0.28 (2.1.0)
> >
> > Report Descriptor size = 402
> > Detected a UPS: American Power Conversion/Back-UPS ES/CyberFort 350 FW:
> > 3.1.I USB FW: d1
> > Using subdriver: APC/CyberPower HID 0.9
> > Path: UPS.PowerSummary.iProduct, Type: Feature, Value: 1.000000
> > Path: UPS.PowerSummary.iSerialNumber, Type: Feature, Value: 2.000000
> > Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, Value: 4.000000
> > Path: UPS.PowerSummary.iOEMInformation, Type: Feature, Value: 3.000000
> > Path: UPS.PowerSummary.Rechargeable, Type: Feature, Value: 1.000000
> > Path: UPS.PowerSummary.Charging, Type: Input, Value: 0.000000
> > Path: UPS.PowerSummary.Charging, Type: Feature, Value: 0.000000
> > Path: UPS.PowerSummary.Discharging, Type: Input, Value: 0.000000
> > Path: UPS.PowerSummary.Discharging, Type: Feature, Value: 0.000000
> > Path: UPS.PowerSummary.APCStatusFlag, Type: Input, Value: 8.000000
> > Path: UPS.PowerSummary.APCStatusFlag, Type: Feature, Value: 8.000000
> > Path: UPS.PowerSummary.ManufacturerDate, Type: Feature, Value: 
>11366.000000
> > Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, Value: 12.000000
> > Path: UPS.PowerSummary.Voltage, Type: Feature, Value: 13.000000
> > Path: UPS.PowerSummary.iManufacturer, Type: Feature, Value: 0.000000
> > Path: UPS.PowerSummary.CapacityMode, Type: Feature, Value: 0.000000
> > Path: UPS.PowerSummary.RemainingCapacity, Type: Input, Value: 100.000000
> > Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, Value: 
>100.000000
> > Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, Value: 1380.000000
> > Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, Value: 1380.000000
> > Path: UPS.PowerSummary.DesignCapacity, Type: Feature, Value: 100.000000
> > Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, Value: 
>100.000000
> > Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, Value: 
>50.000000
> > Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, Value: 
>1.000000
> > Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, Value:
> > 10.000000
> > Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, Value: 
>1.000000
> > Path: UPS.PowerSummary.ACPresent, Type: Input, Value: 1.000000
> > Path: UPS.PowerSummary.ACPresent, Type: Feature, Value: 1.000000
> > Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Input, Value:
> > 0.000000
> > Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Feature, 
>Value:
> > 0.000000
> > Path: UPS.PowerSummary.ShutdownImminent, Type: Input, Value: 0.000000
> > Path: UPS.PowerSummary.ShutdownImminent, Type: Feature, Value: 0.000000
> > Path: UPS.PowerSummary.APCPanelTest, Type: Feature, Value: 0.000000
> > Path: UPS.PowerSummary.APCBattReplaceDate, Type: Feature, Value:
> > 198146.000000
> > Path: UPS.APCGeneralCollection.APCForceShutdown, Type: Feature, Value:
> > 0.000000
> > entering identify_ups(0x051d, 0x0002)
> >
> > Can't find object UPS.PowerSummary.RemainingTimeLimit
> > Can't find object UPS.Battery.ConfigVoltage
> > Can't find object UPS.Battery.Temperature
> > -> String: PbAc (len = 4/4)
> > Can't find object UPS.Battery.ManufacturerDate
> > Can't find object UPS.Battery.APCBattReplaceDate
> > Can't find object UPS.Output.PercentLoad
> > Can't find object UPS.PowerConverter.PercentLoad
> > Can't find object UPS.PowerSummary.DelayBeforeShutdown
> > Can't find object UPS.APCGeneralCollection.APCDelayBeforeShutdown
> > Can't find object UPS.Output.DelayBeforeShutdown
> > Can't find object UPS.Battery.Test
> > Can't find object UPS.Output.Test
> > Can't find object UPS.Battery.Temperature
> > Can't find object UPS.PowerSummary.AudibleAlarmControl
> > Can't find object UPS.ManufacturerDate
> > Can't find object UPS.Output.ConfigActivePower
> > Can't find object UPS.PowerSummary.PresentStatus.ACPresent
> > Can't find object UPS.PowerSummary.PresentStatus.Discharging
> > Can't find object UPS.PowerSummary.PresentStatus.Charging
> > Can't find object UPS.PowerSummary.PresentStatus.ShutdownImminent
> > Can't find object 
>UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit
> > Can't find object UPS.PowerSummary.PresentStatus.Overload
> > Can't find object UPS.PowerSummary.PresentStatus.NeedReplacement
> > Can't find object 
>UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired
> > Can't find object UPS.PowerSummary.PresentStatus.BatteryPresent
> > process_status_info: !chrg
> > process_status_info: !dischrg
> > process_status_info: online
> > process_status_info: !lowbatt
> > process_status_info: !shutdownimm
> > Can't find object UPS.PowerSummary.PresentStatus.FullyCharged
> > Can't find object UPS.Output.Overload
> > Can't find object UPS.Output.Boost
> > Can't find object UPS.Input.Voltage
> > Can't find object UPS.Input.ConfigVoltage
> > Can't find object UPS.Input.LowVoltageTransfer
> > Can't find object UPS.Input.HighVoltageTransfer
> > Can't find object UPS.Output.Voltage
> > Can't find object UPS.Output.ConfigVoltage
> > Can't find object UPS.BatterySystem.Battery.Test
> > Can't find object UPS.BatterySystem.Battery.Test
> > Can't find object UPS.BatterySystem.Battery.Test
> > Can't find object UPS.APCPanelTest
> > Can't find object UPS.APCPanelTest
> > Can't find object UPS.PowerSummary.DelayBeforeShutdown
> > Can't find object UPS.APCGeneralCollection.APCDelayBeforeShutdown
> > Can't find object UPS.Output.DelayBeforeShutdown
> > Can't find object UPS.PowerSummary.DelayBeforeStartup
> > Can't find object UPS.Output.DelayBeforeStartup
> > Can't find object UPS.APCGeneralCollection.APCDelayBeforeShutdown
> > Can't find object UPS.PowerSummary.DelayBeforeShutdown
> > Can't find object UPS.Output.DelayBeforeShutdown
> > Can't find object UPS.PowerSummary.AudibleAlarmControl
> > Can't find object UPS.PowerSummary.AudibleAlarmControl
> > upsdrv_updateinfo...
> > -> String: PbAc (len = 4/4)
> > process_status_info: !chrg
> > process_status_info: !dischrg
> > process_status_info: online
> > process_status_info: !lowbatt
> > process_status_info: !shutdownimm
> > dstate_init: sock /var/run/nut/newhidups-auto open on fd 5
> > upsdrv_updateinfo...
> > Waiting for notifications...
> > upsdrv_updateinfo...
> > Waiting for notifications...
> > ..........last two lines repeated several times........
> > -> String: PbAc (len = 4/4)
> > process_status_info: !chrg
> > process_status_info: !dischrg
> > process_status_info: online
> > process_status_info: !lowbatt
> > process_status_info: !shutdownimm
> > upsdrv_updateinfo...
> > Waiting for notifications...
> > ..........repeated several times........
> >
> >
> > >From: selinger at mathstat.dal.ca (Peter Selinger)
> > >To: jmaggard10 at hotmail.com (Justin Maggard)
> > >CC: nut-upsdev at lists.alioth.debian.org
> > >Subject: Re: [Nut-upsdev] APC CyberFort 350 problems with newhidups
> > >Date: Thu, 23 Feb 2006 09:00:14 -0400 (AST)
> > >
> > >I don't know. Stale data sometimes happens when things have been
> > >started in the wrong order, or the UPS disconnected for some reason.
> > >Usually, these problems go away after the first time. Assuming that
> > >your driver is actually working, the easiest thing to try is:
> > >
> > ># stop everything
> > >upsmon -c stop
> > >upsd -c stop
> > >upsdrvctl stop
> > >
> > ># re-start driver and daemon everything
> > >upsdrvctl start
> > >upsd
> > >
> > ># check if it's working, potentially allow a few seconds' delay
> > >upsc myusb at localhost
> > >
> > ># if yes, restart monitor
> > >upsmon
> > >
> > >-- Peter
> > >
> > >Justin Maggard wrote:
> > > >
> > > > Sorry, I should have included that info originally.  It's using the
> > >latest
> > > > stuff from the Development tree.
> > > > Newhidups - 0.28
> > > > Nut - 2.1.0
> > > > APC-HID - 0.9
> > > >
> > > > I haven't been able to get output from newhidups -DD yet, but in the
> > > > meantime I just wanted to see if someone has seen the same thing.  I 
>was
> > > > told that the newhidups, upsd, and upsmon had been started shortly
> > >before
> > > > the power outage test.  I'll try to get some -DD output soon.
> > > >
> > > > >From: selinger at mathstat.dal.ca (Peter Selinger)
> > > > >To: jmaggard10 at hotmail.com (Justin Maggard)
> > > > >CC: nut-upsdev at lists.alioth.debian.org
> > > > >Subject: Re: [Nut-upsdev] APC CyberFort 350 problems with newhidups
> > > > >Date: Wed, 22 Feb 2006 19:46:54 -0400 (AST)
> > > > >
> > > > >What driver are you using? What version? When did you last restart 
>the
> > > > >driver? upsmon? upsd? Did you try running the driver with -DD to 
>get
> > > > >debug output? -- Peter
> > > > >
> > > > >Justin Maggard wrote:
> > > > > >
> > > > > > Does anyone on this list have a CyberFort 350?  It's a European
> > >model,
> > > > >and
> > > > > > should be equivalent to the US BackUPS ES 350 model.  What I'm
> > >seeing is
> > > > > > upsd reporting stale data.  While the battery is running down, 
>upsc
> > > > >doesn't
> > > > > > see the battery % changing, so I'm assuming the driver isn't
> > >collecting
> > > > >data
> > > > > > at that point.  Unfortunately, the system/UPS is not here (I'm 
>in
> > >the
> > > > >US) so
> > > > > > I can't do a whole lot of debugging.  I'm just trying to figure 
>out
> > >if
> > > > > > anyone else has seen similar issues.  The hidups driver seems to
> > >work
> > > > >fine.
> > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Nut-upsdev mailing list
> > > > > > Nut-upsdev at lists.alioth.debian.org
> > > > > > http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
>

More information about the Nut-upsdev mailing list