similar to: Tripp-lite SMART1050SLT

I was doing some testing with the 2.6.0-1 beta Windows installer and a Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the usbhid-ups driver if the UPS is lost on the UPS bus. This is on a Windows XP SP3 system. USB device access is via libusb 1.2.4.0 (driver mode, not filter) in case that matters. Everything seems to work just fine so far while the UPS is connected (so kudos,

On Sep 14, 2016, at 9:29 AM, Jeff Bowman <jeff.bowman at intexx.com> wrote: > C:\Users\Admin>upsc ups at localhost > battery.charge: 100 ... > ups.status: OL If ups.status follows the state of line power, the driver is working (and upsc talks to upsd, so that connection is working as well). > So this all represents significant progress. But we're not out of the woods

I have 2 SmartUOS1050SLT's that apparently protocol 3004, has there been any progress on getting these units supported under nut? I am running version 2.4.1, and get the following output when starting the driver. #lsusb Bus 005 Device 002: ID 09ae:0001 Tripp Lite # upsdrvctl -DDDD start Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: tripplite exec: /lib/nut/tripplite_usb -a

Original Message >I have 2 SmartUOS1050SLT's that apparently protocol 3004, has there >been >any progress on getting these units supported under nut? I am running >version 2.4.1, and get the following output when starting the driver. >#lsusb >Bus 005 Device 002: ID 09ae:0001 Tripp Lite ># upsdrvctl -DDDD start >Network UPS Tools - UPS driver controller 2.4.1

> I suspect you will want the newer version for production (there was some > issue regarding the popups when certain events happen), but let's get this > version working first before changing another variable. Appreciate that. Agreed. > For reference, I think the source code to NUT.exe is here: > https://github.com/networkupstools/nut/blob/Windows-v2.6.5- >

Hello! I have tested APC Back UPS ES 700 and NUT 2.6.5-3 a few days ago and I have got some news. This device is detected by nut-scanner as: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 700 FW:829.D2 .I USB FW:D2 " serial =

Hello! I tried NUT 2.6.5-1 (Windows port) with my APC Back UPS ES. It seems I have configured NUT properly, nut-scanner found my UPS: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 525 FW:851.t3.I USB FW:t3" serial = "8B0745R23575

> On Sep 11, 2016, at 3:37 PM, Jeff Bowman <jeff.bowman at intexx.com> wrote: > > > > Using subdriver: APC HID 0.95 > > > > ...and then hangs for 45 seconds before returning to a command prompt. No > UPS hardware information is printed. > > It can take about that long to read the descriptors. The non-Windows NUT > drivers will print that message,

Well, I have good news and bad news. I have a Tripp Lite SmartPro UPS attached to a Linux server running Ubuntu 5.10, and I'm running the just-released nut 2.0.3. I had error -71 from the UPS, which Charles Lepple correctly called out as a likely cable problem (thank you, Charles.) The cable provided with the UPS by Tripp Lite was just plain bad. Not too long, mind you- defective. I

I have a new SMART1050SLT Tripp Lite UPS that both tripplite and tripplitesu drivers hate. Both simply time out with a "can't find" message. Does anyone know about the SmartPro series?

I was cleaning up some digital detritus when I ran across an old SVN branch for the proprietary Tripp Lite 3004 USB protocol (the non-PDC variety). It looks very similar to the binary 3005 protocol, which has been added to NUT, but I'd like to have someone sanity-check things before we claim compatibility. Any volunteers? I'm not sure what models this covers, except maybe the

> On Thu, 8 Sep 2016, Jeff Bowman wrote: > > > (Note: running > > 'upsc ups at localhost' echoes only a blank line to the screen, as do > > both 'upsmon' and 'upsd.') > > Something is wrong here. Is the daemon upsd running? On a Unix/Linux > system, the command ps aux | grep ups gives the report > > upsd 3196 0.0 0.0 13228

Hi, I kludged support for the TrippLite SU2200XLA into nut-2.4.3 as follows: --- ./drivers/tripplite-hid.c.0 2010-03-03 15:53:20.000000000 -0500 +++ ./drivers/tripplite-hid.c 2010-03-03 15:53:40.000000000 -0500 @@ -81,6 +81,8 @@ { USB_DEVICE(TRIPPLITE_VENDORID, 0x4002), battery_scale_1dot0 }, /* e.g. TrippLite SmartOnline SU1500RTXL2ua */ {

Hi I have installed nut 2.6.5-6 using the msi installer, but during the install popped up a box asking me to manually install libusb0.dll The msi package doesn't seem to contain the libusb0.dll, the question is, where do I get it from? Thx -------------- next part -------------- An HTML attachment was scrubbed... URL:

I am also having Windows Issues, Refer back to the post I received from Charles Lepple. He gave me the details on how to resolve the missing USB driver issue - Although I would be very interested in what you find as I have not found time to revisit the issue yet.. ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Jul 2016 17:28:51

?Hello, There is a new intermediate Windows binaries release available at : http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-2.msi This fixes three regressions: - upssched was not working - Event logging was not working (unless for NUT service binary itself) - usbhid-ups was not working with Back-UPS ES ups. Feedback is highly appreciated. Regards, Fred -- Eaton

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.

Looking at the project site the latest Windows Binary is a few back - 2.6.5.6 Has any one built a more recent version that they can upload and update the Project site ? Looking for Windows 7 / Windows 8, not running Windows 10 on any of my tool Laptops and I need to check some battery packs and overall status on a series of UPS units in shelters, The build 2.6.5.6 gives my grirf in a number of

I've been able to get the latest Windows port installed on my Hyper-V 2012 R2 instance and start the service. But as I'm an absolute beginner I'm not sure how to proceed further. I've browsed the archives, but discussions here tend to assume at least an intermediate level of understanding; thus it's still quite a bit over my head. Your patience and slow explanations are

Test machine: Windows 7 Pro x64, NUT 2.6.5-3 UPS model: Tripp-Lite Internet Office UPS (INTERNET525U) I needed a UPS and I had this old, but lightly used Tripp-Lite in storage. On the compatibility list I see a (?similar?) INTERNETOFFICE700 using the tripplite_usb driver. But the driver is not liking this particular model that I have. I'll be receiving a 3S550 soon, so I'm not