Hello Barry,
Too bad PowerCom didn't accept to give you their HID usage table... As
if it is a confidential and very important information... Are you sure
you still want to use an UPS from such a manufacturer ?
When will manufacturer understand that linux is not just a dream or a
children game ?
Hi Jonathan
I did find in the trunk/drivers directory a powercom.c/.h and see it is
all serial based
could this not be adapted to USB as well ??
Thanks
Barry
Jonathan Dion wrote:
Hello Barry,
Too bad PowerCom didn't accept to give you their HID usage table... As
if it is a confidential and
Hi Barry
On 8/4/06, Barry Fawthrop [EMAIL PROTECTED] wrote:
Hi Jonathan
I did find in the trunk/drivers directory a powercom.c/.h and see it is
all serial based
could this not be adapted to USB as well ??
Yes, there is a driver for serial powercom UPS.
Halas, serial and USB don't use the
Hi Jonathan
OK Powercom will not release the HID usage table
Not sure if someone else can try they were very unhelpful when I called
So I guess I'll have to write from scratch
Thanks
Barry
Jonathan Dion wrote:
Hi Barry
On 8/2/06, Barry Fawthrop [EMAIL PROTECTED] wrote:
Hi Jonathan
I will
hello !
On 8/1/06, Barry Fawthrop [EMAIL PROTECTED] wrote:
Ok I have install the trunk version in /svn/trunk and ran it's newhidups
drivers/newhidups
here is what I get and it scrolls
drivers/newhidups -DDD -u root -x generic -x vendorid=0d9f auto
Network UPS Tools: 0.28 USB communication
Hi Barry
On 8/2/06, Barry Fawthrop [EMAIL PROTECTED] wrote:
Hi Jonathan
I will try all options
Where do I find a current subdriver to use as a template / example and
then how would I attach it so that NUT can use it ?
I'm willing to do all I can for the NUT community
what everI get I'll share
Hi Barry, Jonathan, etc,
I just caught up with this thread. Yes, I agree with Jonathan's
diagnosis that this might be a HID device, although it is not 100%
sure. The many Input features make me suspicious that it could still
be a fancy serial-over-USB.
[ A general remark to anyone on this
Hello again,
I'm sorry I am new on this mailing list, so I didn't think to reply
to all and not just reply. So I post against my response :
8-sniping
# lsusb
Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd
Bus 001 Device 001: ID :
8sniping a little more
No
Hi Jonathan
To know that, run :
newhidups -DD -u root -x generic -x vendorid=0d9f auto
Look what is exposed, and see if another drivers expose the same
variable. If it exist, modify the claim function so it claim your UPS
(and if it work, please send us a patch ^_^)
I could not find a
Hi Barry
On 8/1/06, Barry Fawthrop [EMAIL PROTECTED] wrote:
Hi Jonathan
To know that, run :
newhidups -DD -u root -x generic -x vendorid=0d9f auto
Look what is exposed, and see if another drivers expose the same
variable. If it exist, modify the claim function so it claim your UPS
(and
/lib/nut/newhidups -DD -u root -x generic -x vendorid=09df auto
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3)
Fatal error: 'generic' is not a valid flag for this driver.
Look in the man page or call this driver with -h for a list of
valid variable names and flags.
Hi Charles
If this is some type of USB to serial converter How then do I link or
makr /dev/usb/hiddev0 something like /dev/ttyS0 ?
What would be the process here ?
Thanks
Barry
Barry Fawthrop wrote:
lsusb -v
Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd
Device Descriptor:
tis 2006-08-01 klockan 09:11 -0400 skrev Barry Fawthrop:
/lib/nut/newhidups -DD -u root -x vendorid=09df auto
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3)
Here you state 09df as vendorID.
debug level is '2'
Checking device (0D9F/0001) (001/003)
- VendorID: 0d9f
- ProductID:
Hello,
I'm sorry, I didn't think to a little detail :
On 8/1/06, Barry Fawthrop [EMAIL PROTECTED] wrote:
/lib/nut/newhidups -DD -u root -x generic -x vendorid=09df auto
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3)
Fatal error: 'generic' is not a valid flag for this driver.
Look in
Me again
8---snipe
then run drivers/newhidups -DD -u root -x generic -x vendorid=09df auto
Oh yes, Kjell is right ! it is 0d9f. But I verified, no subdriver
claim vendo 0d9f neither.
If this is some type of USB to serial converter How then do I link or
makr /dev/usb/hiddev0 something
Thank Kjell
even changing to 0D9F I get
/lib/nut/newhidups - -u root -x vendorid=0d9f auto
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3)
debug level is '4'
Checking device (0D9F/0001) (001/003)
- VendorID: 0d9f
- ProductID: 0001
- Manufacturer: unknown
- Product: unknown
-
Ok I have install the trunk version in /svn/trunk and ran it's newhidups
drivers/newhidups
here is what I get and it scrolls
drivers/newhidups -DDD -u root -x generic -x vendorid=0d9f auto
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0)
ProductID: 0001
- Manufacturer:
Hi Charles
Thanks for the info I was not aware that hidups was downgraded
Here are my conf files
ups.conf
=
[Ultra1]
DRIVER = hidups
PORT = /dev/usb/hiddev0
upsd.conf
=
ACL all 0.0.0.0/0
ACL localhost 127.0.0.1/32
ACL network 192.168.0.0/24
ACCEPT localhost
On 7/31/06, Barry Fawthrop [EMAIL PROTECTED] wrote:
ups.conf
=
[Ultra1]
DRIVER = hidups
PORT = /dev/usb/hiddev0
I believe driver and port should be lowercase.
--
- Charles Lepple
___
Nut-upsuser mailing list
On 7/31/06, Barry Fawthrop [EMAIL PROTECTED] wrote:
/dev/usb/hiddev0 is the UPS I'm sure (but not 100%)
It may be that it is just a simple USB-to-serial converter, and not a
standards-compliant PDC UPS.
Can you post the output from running 'lsusb -vvv' as root?
--
- Charles Lepple
lsusb -v
Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0
Hi Jonathan
using
driver = newhidups
port = auto
in ups.conf
I get this
* Starting UPS drivers ...
Network UPS Tools - UPS driver controller 2.0.3
Can't start /lib/nut/newhidups: No such file or directory
* Failed to start UPS
drivers! [ !! ]
*
Hi all
I recompiled nut and now have newhidups
/etc/init.d/upsd start
* Caching service dependencies
...
[ ok ]
* Starting UPS drivers ...
Network UPS Tools - UPS driver controller 2.0.3
Network UPS Tools: New
Hi All
I'm trying to get my Ultra UPS connected. It connects using a standard
USB cable
I have --with-drivers=hidups in the configure command and I have lsusb
showing
Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd
Bus 001 Device 001: ID :
I have /dev/usb/hiddev0
now matter
On 7/30/06, Barry Fawthrop [EMAIL PROTECTED] wrote:
Can't start /lib/nut/(null): No such file or directory
Please post your config files.
Also note that the hidups driver is deprecated, and will go away in a
future release. A more comprehensive driver is newhidups.
--
- Charles Lepple
25 matches
Mail list logo
