Damn, I knew there'll be trouble as soon, as the manufacturer's program didn't work.<br>I guess, if I want to make it work, I'll have to write my own driver, and that's not very likely to happen in the nearest future also ;)
<br>Thanks for the help so far!<br><br>Dominik Goraczkowski<br><br><div><span class="gmail_quote">2007/1/23, Peter Selinger <<a href="mailto:selinger@mathstat.dal.ca">selinger@mathstat.dal.ca</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
=?windows-1252?Q?Dominik_Gora=3Bczkowski?= wrote:<br>><br>> Peter Selinger napisa?(a):<br>> > I don't know if it would be possible to write a driver for your UPS.<br>> > There is currently a project for getting a serial-over-usb megatec
<br>> > protocol to work.<br>> ><br>> > If you send the output of<br>> ><br>> > newhidups -DD -u root -x explore -x vendorid=0d9f auto<br>> ><br>> > , I might be able to tell you whether it resembles other devices that
<br>> > we have seen. -- Peter<br>> ><br>> Here's the output - the messages are suggesting, that the newhidups<br>> driver recognizes the UPS somehow:<br><br>Yes, the -x explore option forces that. But there is a big difference
<br>between being able to open a device, and understanding the language it<br>speaks. The output from your device, unfortunately, does not resemble<br>anything we have seen before. Very unlikely that there'll be a driver
<br>for it in NUT anytime soon, unless somebody volunteers to take up the<br>project, which would mean experimenting.<br><br>Since there is only one "Input" and one "Output" field, it is perhaps<br>likely that the device expects serial data to be written and read from
<br>these. However, it is not clear in what format.<br><br>So, sorry for the bad news. -- Peter<br><br>> Checking device (0D9F/0002) (001/005)<br>> - VendorID: 0d9f<br>> - ProductID: 0002<br>> - Manufacturer: POWERCOM CO., LTD.
<br>> - Product: USB to Serial<br>> - Serial Number: unknown<br>> - Bus: 001<br>> Trying to match device<br>> Device matches<br>> HID descriptor retrieved (Reportlen = 37)<br>> Report descriptor retrieved (Reportlen = 37)
<br>> Found HID device<br>> Report Descriptor size = 37<br>> Detected a UPS: POWERCOM CO., LTD./USB to Serial<br>> Using subdriver: EXPLORE HID 0.1<br>> Can't find object ffa00001.ffa00001<br>> Path:
ffa00001.ffa00001, Type: Input<br>> Path: ffa00001., Type: Input<br>> Path: ffa00001., Type: Input<br>> Path: ffa00001., Type: Input<br>> Path: ffa00001., Type: Input<br>> Path: ffa00001., Type: Input<br>> Path: ffa00001., Type: Input
<br>> Path: ffa00001., Type: Input<br>> Can't find object ffa00001.ffa00002<br>> Path: ffa00001.ffa00002, Type: Output<br>> Path: ffa00001., Type: Output<br>> Path: ffa00001., Type: Output<br>> Path: ffa00001., Type: Output
<br>> Path: ffa00001., Type: Output<br>> Path: ffa00001., Type: Output<br>> Path: ffa00001., Type: Output<br>> Path: ffa00001., Type: Output<br>> Path: ffa00001.ffa00003, Type: Feature, Value: 0.000000<br>> Path: ffa00001., Type: Feature
<br>> Path: ffa00001., Type: Feature<br>> Path: ffa00001., Type: Feature<br>> Path: ffa00001., Type: Feature<br>> upsdrv_updateinfo...<br>> dstate_init: sock /var/state/ups/newhidups-auto open on fd 8<br>> upsdrv_updateinfo...
<br>> Waiting for notifications...<br>> upsdrv_updateinfo...<br>> Waiting for notifications...<br>> (repeating)<br>><br>> Dominik Goraczkowski<br>><br><br></blockquote></div><br>