[Nut-upsuser] bcmxcp - Powerware 9125

[Kjell Claesson]

Hi Gorm.

The PW9125 have given us some trouble. The problem we have was
that it hade some trouble to start. Starting it at 1200Bps
then reverting back to 9600Bps seems to make it start.

This was not so good as the driver needed to be recompiled every time.
So in the new driver i made some changes.

The baud-rate is configurable by setting the baud_rate in the 
ups.conf.

baud_rate = 9600

If it not responding it goes into baud-hunting. Then tell you the
speed it connect at. ( This fix the HP 3000 ups also as it run at
19200Bps)

Then one more thing is done during start-up, it sends the 
authorization string and set it to requested mode only.

This make the ups to only respond to poll. So it may be that
you are using the 0.08 driver and the ups is in unrequested mode.

In unrequested mode the ups is periodic sending the status block
meter block alarm block.
If this is the case it can flod the receive buffer and make it
miss the requested status. The ups would start-up in unrequested
if it was set to this before power-down. So if your ups have been
running in that mode it have to be set to requested mode only.
 
About the 3110. It is a old small ups that was equipped with usb
port in march of 2004. It's usb 1.1 and has a very low revision on
the software in the ups. The problem is that it have been superseded
by the 3105 ( ? ) that use usb2. I run one of them at the moment to
my computer. (Saved me yesterday, when a fuse was blown).

The 3110 can be used with the generic driver as it use dry contact
on the Db9 connector. 

The usb driver is not setting the ups to requested mode at start-up
at present time. Hopefully we can fix this in a near future.

So to Benjamin. Try starting it with the serial driver ( or maybe you
have a computer that don't have any com port. Common this days)

I have running a 5115 for about 1 year without problem (serial).

Thank you for the feedback.

You can try the 0.10 driver. Now back-ported to Testing branch 
(2.0.3).

Regards
Kjell
   
  


sön 2005-10-09 klockan 21:14 +0200 skrev Gorm J. Siiger:
> I'm currently testing the bcmxcp driver for NUT, and it causes me some
> trouble. And when scanning the archives it seems like the 3110 USB problem
> reported recently.
> 
> The bcmxcp daemon stops running, and the logs shows the following:
> 
> Oct  6 14:22:32 host.dom.tld bcmxcp[82628]: Communications with UPS lost:
> Receive error (data): got -1 bytes instead of 28!!!
> Oct  6 14:22:33 host.dom.tld bcmxcp[82628]: Communications with UPS
> re-established
> 
> Oct  6 14:23:02 host.dom.tld bcmxcp[82628]: Communications with UPS lost:
> checksum error!
> Oct  6 14:23:02 host.dom.tld bcmxcp[82628]: Communications with UPS lost:
> Receive error (Request command): 9!!!
> Oct  6 14:23:03 host.dom.tld bcmxcp[82628]: Communications with UPS
> re-established
> 
> Oct  6 14:55:29 host.dom.tld bcmxcp[82628]: Communications with UPS lost:
> checksum error!
> Oct  6 14:55:29 host.dom.tld bcmxcp[82628]: Communications with UPS lost:
> Receive error (Request command): 9!!!
> Oct  6 14:55:29 host.dom.tld bcmxcp[82628]: Communications with UPS
> re-established
> 
> 
> Network UPS Tools - UPS driver controller 2.0.2
> Network UPS Tools (version 2.0.2) - APC Smart protocol driver
>         Driver version 1.99.7, command table version 2.0
> Detected SMART-UPS 2200 [GS9850005011] on /dev/cuaa5
> Network UPS Tools - BCMXCP UPS driver 0.08 (2.0.2)
> 
> Modell = PW9125 1000i    1000VA
> Firmware = 11.00
> Shutdown delay =  120 seconds
> Network UPS Tools upsd 2.0.2
> Connected to UPS [UPS-1]: apcsmart-cuaa5
> Connected to UPS [UPS-2]: bcmxcp-cuaa4
> Synchronizing...done
> Network UPS Tools upsmon 2.0.2
> UPS: UPS-1 at localhost (master) (power value 1)
> Using power down flag file /etc/killpower
> 
> Any idea why this happens, the serial port is running just fine. An APC has
> been connected for at litte over a year now on that port. ?
>