[Nut-upsdev] Krauler UP-M500VA investigation

[Peter Selinger]

Hi Alex,

the 2.0.4 release is too old. Please try the newest version from
SVN. See http://www.networkupstools.org/source.html -> Development
tree. 

Use "autoreconf" to populate the sources after downloading them, then
"./configure", "make", "make install" as usual. 

The information from -x generic will be crucial. I can't guess how to
interpret it until I see it.

-- Peter

Alexander I. Gordeev wrote:
> 
> Hi, Peter,
> 
> Thanks for the answer! I tried hardly to make it working with
> currently available drivers, but it seems to be not supported at all :(
> I tried to change vendor id in all subdrivers to correspond to my
> hardware, but it didn't help. I've got a lot of messages about missing
> reports and objects.
> I checked docs/hid-subdrivers.txt also, very informative, thanks for
> the link. But what should I do to know these hex values for usages?
> 
> That's what I get as an output (with vendorid in subdrivers unchanged):
> 
> admin at router:/tmp/harddisk/share/pub/system/development/newbuild/opt/bin> ./newhidups -DD -u admin -x vendorid=0001 /dev/usb/hid/hiddev0
> Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4)
> 
> debug level is '2'
> Checking device (0000/0000) (003/001)
> - VendorID: 0000
> - ProductID: 0000
> - Manufacturer: Linux 2.4.20 ehci_hcd
> - Product: PCI device 1106:3104
> - Serial Number: 01:03.2
> - Bus: 003
> Trying to match device
> Device does not match - skipping
> Checking device (04FC/0C15) (003/002)
> - VendorID: 04fc
> - ProductID: 0c15
> - Manufacturer: Sunplus Technology Inc.
> - Product: USB to Serial-ATA bridge
> - Serial Number: SAMSUNG SPS09QJ1NL805434
> - Bus: 003
> Trying to match device
> Device does not match - skipping
> Checking device (0000/0000) (002/001)
> - VendorID: 0000
> - ProductID: 0000
> - Manufacturer: unknown
> - Product: USB UHCI Root Hub
> - Serial Number: 120
> - Bus: 002
> Trying to match device
> Device does not match - skipping
> Checking device (0000/0000) (001/001)
> - VendorID: 0000
> - ProductID: 0000
> - Manufacturer: unknown
> - Product: USB UHCI Root Hub
> - Serial Number: 100
> - Bus: 001
> Trying to match device
> Device does not match - skipping
> Checking device (0001/0000) (001/003)
> - VendorID: 0001
> - ProductID: 0000
> - Manufacturer: unknown
> - Product: unknown
> - Serial Number: unknown
> - Bus: 001
> Trying to match device
> Device does not match - skipping
> No appropriate HID device found
> No matching USB/HID UPS found
> 
> UPS is the last one for sure.
> By the way, option '-x generic' is not implemented.
> 
> Peter Selinger wrote:
> 
> > Hi Alexander,
> 
> > the driver you want is newhidups, not hidups. First check if your
> > device is already supported; this could be so even if it isn't in
> > data/driver.list (because often vendors just put their name on a UPS
> > engineered by someone else).
> 
> > If it's not already supported, have a look at docs/hid-subdrivers.txt.
> > That file explains several useful concepts, and gives you enough
> > information to get started. Particularly the output from
> 
> > drivers/newhidups -DD -u root -x generic -x vendorid=XXXX auto
> 
> > will be relevant. When the instructions run out, please report back to
> > the list for more assistance.
> 
> > -- Peter
> >  
> 
> -- 
>  Alexander                          mailto:lasaine at lvk.cs.msu.su
>