<html>
<body>
<font size=3>Peter,<br>
I generated a new subdriver using the suggested method of
running<br>
./drivers/usbhid-ups -DDDD -u nut -x explore -x vendorid=ffff auto
>& /tmp/info<br><br>
followed by pumping this into <br>
./scripts/subdriver/path-to-subdriver.sh<br><br>
Then make all, and make install . I don't get any error messages, I just
don't seem to get what I expect, which is some of the details from the
UPS. <br><br>
Whilst I do have windows software for this device, I would
not know where to start to decode what it is doing so that I could
replicate it in the NUT system.<br><br>
Jon<br><br>
At 18:16 28/01/2007, Peter Selinger wrote:<br>
<blockquote type=cite class=cite cite="">Jon Gough wrote:<br>
> <br>
> Oooppss. Lets try with less data!<br><br>
Yes, I also had trouble posting to the list because of the size<br>
limit. It might help if you could teach your mailer not to repeat
the<br>
entire message in HTML at the end of each message.<br>
<br>
> Peter,<br>
> Here is the line that I pruned out.<br>
> <br>
> Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30
(2.1.0)<br>
> <br>
> When I start the driver with<br>
> /usr/local/ups/bin/upsdrvctl -u nut start<br>
> <br>
> I get the following messages<br>
> <br>
> Network UPS Tools - UPS driver controller 2.1.0<br>
> Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30
(2.1.0)<br>
> <br>
> Detected a UPS: UIS Ablerex/Ablerex USB Interface 049e<br>
> Using subdriver: Upsilon HID 0.1<br><br>
OK, so you are using some patch that I have not seen. There is no<br>
"Upsilon" subdriver in the official NUT sources.<br>
<br>
> Then I issue<br>
> /usr/local/ups/sbin/upsd -u nut<br>
> <br>
> and get<br>
> <br>
> Network UPS Tools upsd 2.1.0<br>
> upsd: listening on 0.0.0.0:3493<br>
> Connected to UPS [eclipse]: eclipse<br>
> <br>
> Then I try to see what is available from the driver with<br>
> /usr/local/ups/bin/upsc eclipse<br>
> <br>
> and get<br>
> <br>
> Activepower: 0<br>
> Apparentpower: 0<br>
> driver.name: usbhid-ups<br>
> driver.parameter.pollinterval: 2<br>
> driver.parameter.port: auto<br>
> driver.version: 2.1.0<br>
> Shutdown.Delay: 0<br>
> Startup.Delay: 0<br>
> ups.mfr: UIS Ablerex<br>
> ups.model: Ablerex USB Interface 049e<br>
> ups.status: WAIT<br><br>
OK, sure, you are getting ahead of the game. There is no point in
this<br>
unless the driver can first communicate with the UPS. <br>
<br>
> If I try<br>
> /usr/local/ups/bin/upsc eclipse battery.voltage<br>
> <br>
> I get<br>
> <br>
> Error: Variable not supported by UPS<br>
> <br>
> Yet battery.voltage is defined in the
hid_info_t variable.<br>
> <br>
> It looks like only part of the output is
being read. But at this <br>
> point I do not know what to do to get further information from the
<br>
> system. I have modified the stub to have the correct (I hope) labels
<br>
> for at least some of the values that should be returned, but they do
<br>
> not show up when I call the command processor.<br>
> <br>
> I seem to be missing something in this
process. Not sure what, <br>
> but I am getting confused about what I should have to do.<br>
> <br>
> Regards<br>
> Jon<br>
> <br>
<snip></font></blockquote>
<BR><BR>
<TABLE width=400><HR>
<P style="FONT: 9pt/11pt verdana"><a href="http://www.avast.com">avast! Antivirus</a>: Outbound message clean.
<P style="FONT: 8pt/11pt verdana">Virus Database (VPS): 000707-0, 27/01/2007<BR>Tested on: 28/01/2007 6:31:45 PM<BR><FONT color=gray>avast! is copyright (c) 2000-2007 ALWIL Software.</FONT></P>
<TBODY></TBODY></TABLE>
<BR>
</body>
<br>
</html>