2014-11-09 16:29 GMT+01:00 Charles Lepple clep...@gmail.com:
On Nov 8, 2014, at 7:01 PM, hyo...@gmail.com wrote:
Since this UPS seems to be supported by UPSmart2000I, it could use a
serial-over-usb implementation of the megatec protocol.
Dan, that is a good point - I had not considered it. I
Sorry for the bad formatting of the previous message...I tried to use plus
signs as bullet points, and that caused a problem somehow.
Ok...I discovered that if I do the autoreconf after the first failed make (and
the autoreconf still gives that error message), and then do make again...it
Nice!
By the way, to avoid the initial protocol autodetection procedure and
to speed up the startup, you should set 'protocol=megatec'.
Do the various instant commands seem to work? Can you test them all
and report back the logs (a debug level of 5 should be enough)?
Also, what's the output of
Ok, I tried this from scratch on a fresh 2.7.2 directory. I followed the web
instructions, specifically:
+ I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info.
+ I put them in the drivers subdir
+ I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically
I just would like to confirm that I face very similar issue when I want to
connect UPS to VM machine (on ESX server). I blame VmWare USB passthrough.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
On Mar 9, 2015, at 12:00 PM, Rob Groner rgro...@rtd.com wrote:
1) Autoreconf *must* be run, and not ./configure? I had thought that putting
in my *.c and *.h files and making the makefile changes and then executing
./configure for the first time would be enough.
Each tool serves a
On Mar 9, 2015, at 11:28 AM, hyo...@gmail.com wrote:
2014-11-09 16:29 GMT+01:00 Charles Lepple clep...@gmail.com:
On Nov 8, 2014, at 7:01 PM, hyo...@gmail.com wrote:
Since this UPS seems to be supported by UPSmart2000I, it could use a
serial-over-usb implementation of the megatec protocol.
7 matches
Mail list logo
