On Tue, 19 Sep 2006, Kjell Claesson wrote:
Hi Kipp, some followup on the last mail.
I have checked up the manual of the ups.
on http://www.powerware.com/Products/end_of_life_Manuals.asp
Powerware 9 Prestige Series User's Guide 600 VA-1800 VA.
To run it on LanSafe it should be set in printer mode, and
the driver works like LanSafe. So check your communication
settings on the ups.
Hi,
Thanks for this suggestion. Unfortunately, I followed the instructions in
the manual to put the UPS into "Printer Mode, 2400 Baud", and nothing
changed. I still get:
root% upsdrvctl -v start
Network UPS Tools - UPS driver controller 2.0.4
exec: /lib/nut/bcmxcp -a powerware
Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4)
Connected to UPS on /dev/ttyS0 baudrate: 2400
Model = Powerware Prestige 1000VA
Firmware = 01.06
Shutdown delay = 120 seconds
Communications with UPS lost: Receive error (Request command): 9!!!
Communications with UPS lost: Receive error (Request command): 9!!!
Communications with UPS lost: Receive error (Request command): 9!!!
Communications with UPS lost: Error executing command
Could not communicate with the ups: Success
Driver failed to start (exit status=1)
Am I supposed to use the same driver (bcmxcp), or am I supposed to try a
different one?
-Kipp
Regards
Kjell
mån 2006-09-18 klockan 22:58 -0500 skrev Kipp Cannon:
Hi,
I've got a Powerware Prestige 9 1kVA UPS that seems to not be working with
nut. It's not in the current "supported hardware" list, but the old
bcmxcp page lists it as being a UPS that speaks that protocol.
I have the following in my ups.conf
[powerware]
driver = bcmxcp
port = /dev/ttyS0
desc = "Powerware Prestige 9 EXT"
baud_rate = 2400
And when I start the driver I get
root% upsdrvctl -v start
Network UPS Tools - UPS driver controller 2.0.4
exec: /lib/nut/bcmxcp -a powerware
Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4)
Connected to UPS on /dev/ttyS0 baudrate: 2400
Model = Powerware Prestige 1000VA
Firmware = 01.06
Shutdown delay = 120 seconds
Communications with UPS lost: Receive error (Request command): 9!!!
Communications with UPS lost: Receive error (Request command): 9!!!
Communications with UPS lost: Receive error (Request command): 9!!!
Communications with UPS lost: Error executing command
Could not communicate with the ups: Success
Driver failed to start (exit status=1)
So it's definitely talking to the UPS: it gets the model number and
firmware revision, neither of which are things I've told it. But then
there are errors and the driver finally gives up.
Can anyone give me a hand getting this working?
-Kipp
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
