Good evening,
Hoping someone can point me in the right direction..
I downloaded and installed the 2.6.5-6 Windows MSI and it installed
fine, although I nee to also get a libusb0.dll.
Connected USB to a Triplite, I could go to the Devices and Printers and
see the USB installed.
But no matter what I did I could not get nut to work. I tried various
commands, and got various errors.
my config has --
[myups1]
driver = usbhid-ups
port = auto
vendorid = 09ae
# cable = 1234
desc = "Something descriptive"
was trying bin\upsc myups1 and I tried bin\upsc myups1 at localhost:3493
Never could get it give me a snap shot of the UPS, just unknown
communication error --
Also tried, bin\upsdrvctl start & bin\upsdrvctl start myups1 Still had
multiple errors.
Also tried sbin\upsd would get the v4 & V6 listening but it would never
move beyond that --
--------------------------------------------------------------------------------------------------------------------------------
Tried another UPS with same basic results --
[Comtemp]
driver = usbhid-ups
port = auto
vendorid = 0463
# cable = 1234
desc = "Something descriptive"
----------------------------------------------------------------------------------------------------------------------------------
Normally, I use this on FreeBSD and have never had an issue, anyone know
what my problem might be with Win 7 64bit.
I did see a new build , but no msi for windows yet..
TIA,
Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160713/0bde7736/attachment.html>
[please use Reply-All to include the list. thanks!] On Jul 13, 2016, at 10:19 PM, Jeff Silberberg <jms at compudesigns.net> wrote:> > Never could get it give me a snap shot of the UPS, just unknown communication error -- >Hopefully one of the Windows experts can chime in, but in the mean time, here's a diagram of the NUT layers: http://networkupstools.org/docs/developer-guide.chunked/ar01s02.html#_the_layering For troubleshooting, you need to work from the bottom to the top of the diagram. It sounds like the UPS is connected. Since you mentioned libusb0.dll, make sure that the UPS is not being recognized as a regular HID UPS (instead, it should be claimed by libusb). You can try running "bin\upsdrvctl -D start myups1" to see the command line that it uses for the driver, then try running that. You might need to do this from an Administrator console - not sure how the Windows port handles permissions. Only then will upsd and upsc (upper layers in the diagram) have a chance of returning data. -- Charles Lepple clepple at gmail
On Jul 14, 2016, at 7:34 AM, Jeff Silberberg <jms at compudesigns.net> wrote:> > >> On Wed, Jul 13, 2016 at 11:28 PM, Charles Lepple <clepple at gmail.com> wrote: >> It sounds like the UPS is connected. Since you mentioned libusb0.dll, make sure that the UPS is not being recognized as a regular HID UPS (instead, it should be claimed by libusb) >> >> > Charles, > > I think this is exactly the issue.. The Microsoft USB driver grabbed the device when I plug in the USB cable, not sure how to stop that ? Can I just "update" the device driver through the devices properties,although I am sure there is probably a better approach.[please use Reply-All to include the list. thanks!] Not sure. I haven't used the Windows port of NUT. If I recall, it was first written prior to the introduction of WinUSB, so there will be some fiddling with drivers. From the installer file: "If the automatic USB driver installation fails, you can try to install a driver manually. For this go to : https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/ After installling libusb-win32, run libUSB's Inf Wizard and choose your device." -- https://github.com/networkupstools/nut/blob/6d53cfe37c9c2c5779ac5efd3dc5428586d67961/scripts/Windows/Installer/NUT-Installer.xml I'm CC'ing the list again so that hopefully one of the Windows developers will see this. -- Charles Lepple clepple at gmail