--- Kjell Claesson [EMAIL PROTECTED] wrote:
It check the iManufacturer and iProduct code.
This is not the same on the 5115 and 3110.
So that is why it can't open the device.
It should look like this.
dev-descriptor.iManufacturer == 4
Kjell Claesson wrote:
Then i have a problem. My computer is down due to a
faulty mainboard,
Youch. I hate it when that heppens. Hope it wasn't
because you got a power spike ;-)
Let me or Georg know if you want us to run any debug
code. Feels like a bcmxcp_usb driver bug to me since
the
I tried switching to the USB version of bcmxcp_usb and
get this error when I try starting up upsdrvctl or
bcmxcp_usb like so:
/etc/nut/bcmxcp_usb - -a powerware -u nut
I used this for ups.conf:
[powerware]
driver = bcmxcp_usb
port = auto
With the serial/usb dongle, I used
Looks like Georg and I have the same problem w/
different Powerware UPSes...
I get the same error :-P
ken
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--- Kjell Claesson [EMAIL PROTECTED] wrote:
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'.
Sounds like you basically have to run it in serial
mode to keep the Powerware from periodically sending
data when
I decided to try this to see if it worked better since
Powerware decided to build in some oddball USB
protocol instead of using a HID UPS profile, but it
doesn't seem to work. The USB/serial dongle is
recognized by Linux and added as /dev/ttyUSB0, owned
by group dialout, so I had to add the nut
6 matches
Mail list logo
