Hello...
I have a PowerWare 9120 attached via USB to my Debian system.
My ups.conf looks like this:
[ups1]
driver = bcmxcp_usb
port = auto
desc = "PowerWare 9120"
When testing the driver with "upsdrvctl -u root start" I get:
Network UPS Tools - UPS driver controller 2.0.4
Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4)
Communications with UPS lost: Receive error (Request command): BLOCK: 0,
COMMAND: 31!
Communications with UPS lost: checksum error!
Communications with UPS lost: Receive error (Request command): BLOCK: cb,
COMMAND: 31!
Model = PW9120 3000VA
Firmware = 02.60
Shutdown delay = 120 seconds
Communications with UPS lost: Receive error (Request command): BLOCK: fa,
COMMAND: 3c!
Communications with UPS lost: Receive error (Request command): BLOCK: 81,
COMMAND: 33!
When looking at the combatability chart at
http://www.networkupstools.org/compat/stable.html it
seems the PW9120 is supported by the bcmxcp driver and not bcmxcp_usb. I have
however found
suggestions that bcmxcp_usb supports the 9120:
http://osdir.com/ml/monitoring.nut.user/2006-04/msg00054.html
I have a SNMP card in the 9120, but my understanding is that the NUT SNMP-driver
does not allow the
UPS to be shut down. This is why I am now turning to USB.
Any ideas as to how I can get my setup running?
Thank you,
Tobias Balle-Petersen
Den Friday 02 November 2007 13.00.46 skrev Tobias Balle-Petersen:> Hello... >Hi Tobias.> I have a PowerWare 9120 attached via USB to my Debian system. > > > My ups.conf looks like this: > [ups1] > driver = bcmxcp_usb > port = auto > desc = "PowerWare 9120" > > > > > When testing the driver with "upsdrvctl -u root start" I get: > Network UPS Tools - UPS driver controller 2.0.4 > Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) > Communications with UPS lost: Receive error (Request command): BLOCK: 0, > COMMAND: 31! Communications with UPS lost: checksum error! > Communications with UPS lost: Receive error (Request command): BLOCK: cb, > COMMAND: 31! Model = PW9120 3000VA > Firmware = 02.60 > Shutdown delay = 120 seconds > Communications with UPS lost: Receive error (Request command): BLOCK: fa, > COMMAND: 3c! Communications with UPS lost: Receive error (Request command): > BLOCK: 81, COMMAND: 33! > >It looks like you have a problem with the usb connection. Check the cabling. The driver is using a binary protocol with checksum, and is hard on bit errors. The command 31 is asking for the identification block. Command 3c is extended limit block and 33 is tha status block. And as it answer with Modell and seems to start, it reads the Identification block after som errors.> > When looking at the combatability chart at > http://www.networkupstools.org/compat/stable.html it seems the PW9120 is > supported by the bcmxcp driver and not bcmxcp_usb. I have however found > suggestions that bcmxcp_usb supports the 9120: > http://osdir.com/ml/monitoring.nut.user/2006-04/msg00054.html >It is not a compatibility error, as it should hang on the same command. And it was developed on a 9120 but serial connected.> > > I have a SNMP card in the 9120, but my understanding is that the NUT > SNMP-driver does not allow the UPS to be shut down. This is why I am now > turning to USB. > > > Any ideas as to how I can get my setup running? >Use hi class usb cables, if You is unable to use the serial version of the driver. Use a short sheelded cable. Don't twist it around the powerlines. Then you should get new version of nut as 2.0.4 is past date. Regards Kjell
Tobias Balle-Petersen wrote:> Hmmm... I guess I need a kernel newer than the one in atable:Just realized I dont have the etch stable kernel on my testing system. Igonre the above. Thanks, Tobias
Hello.... Kjell Claesson wrote:> Then you should get new version of nut as 2.0.4 is past date.I have updated to nut 2.2.0-1 as suggested. Unfortunately I still get the same type of errors: Network UPS Tools - UPS driver controller 2.2.0- Network UPS Tools - BCMXCP UPS driver 0.11 (2.2.0-) Warning: This is an experimental driver. Some features may not function correctly. Model = PW9120 3000VA Firmware = Cont:02.60 Inve:02.60 Shutdown delay = 120 seconds Communications with UPS lost: Receive error (Request command): BLOCK: 17, COMMAND: 35! Communications with UPS lost: Receive error (Request command): COMMAND: 33 RECONNECT USB DEVICE Communications with UPS lost: Receive error (Request command): COMMAND: 33 RECONNECT USB DEVICE My ups.conf looks like this: [ups1] driver = bcmxcp_usb port = auto desc = "PowerWare 9120" Thanks, Tobias
Hello... Just to make sure I did a clean install of debian etch and tested. I still get the same errors. Nut 2.0.4. Tobias
"Arjen de Korte" wrote:> 1) Apparently, this UPS needs to be told only to reply to specific > requests and not send unsollicited status updates. The bcmxcp (serial) > driver supposedly does this, the bcmxcp_usb (USB) doesn't. However, the > UPS remembers the last status, so this might help.FYI, I had this problem about a year ago w/ the 9120 and I believe that was the same conclusion. It'd be really nice to get the USB port working. I've been using a serial->USB cable. Also, AFAIK, you can't tell the UPS not to send unsolicited status updates. I'll bet it has something to do w/ their software. They said just run their software when I asked them to document the USB protocol for their UPS ;-) ken __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Hello all. I have now connected the UPS via a serial-cable to a PC running Debian Etch and Nut 2.0.4. When running "upsdrvctl -u root start" I get: Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS re-established Connect to UPS on /dev/ttyS0 baudrate 9600 Model = PW9120 3000VA Firmware = 02.60 Shutdown delay = 120 seconds Is this the OK? Can I ignore the first errors? In 2006 Kjell wrote at http://osdir.com/ml/monitoring.nut.user/2006-04/msg00055.html : "The thing is that if you have run it on the serial before you go to use the bcmxcp_usb driver it should be set to 'request_only_mode'." How do I set my UPS to "request_only_mode"? Thanks, Tobias