[Nut-upsdev] APC CyberFort 350 problems with newhidups

[Justin Maggard]

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
> >
>