[Nut-upsuser] New NUT user with HP R3000XR problem

[Kjell Claesson]

> On Tue, May 26, 2009 at 09:51:31PM -0400, Brother Railgun of Reason wrote:
Hi,
> > ups.conf looks like this:
> >
> > [tokamak]
> >     driver      = bcmxcp
> >     port        = /dev/tty00
> >     baud_rate   = 19200
> >     desc        = HP R3000XR (main rack)
>
> (Oops.  That's *after* changing to the 19200 rate the driver claims to
> autodetect.)
That sound strange. It should hit 19200 direct if it is in the config.
And the HP R3000XR is communicating at 19200 default. That type
is the reason the baud changing got into the driver.

>
> > Am I using the correct cable here?  If not, what's the correct cable to
> > use?
If it say it connect it is talking to the ups. But to be sure about that, you 
may run it in debug mode, like this.

/path/to/bcmxcp -DD -a tokamak
(stop it by hitting ctrl-c)

Now it would spit out some info. I'm interested in the output. There may
be some problems how the HP is counting the load-segments.
It depends on the version of the firmware in the ups.

>
> The other detail I forgot to add was that, just out of sheer
> constructive paranoia, I tried using an APC 940-0024C cable instead of
> the HP cable, which as far as I can tell with a DVM is just a dumb
> serial cable wired all nine pins straight through.  With the HP cable,
> the driver thinks it has comm sync at 19200, but upsdrvctl can't talk to
> it; with the APC cable, the driver can't even establish communication at
> all.

/Kjell