search for: smart1000lcd

...twork UPS Tools: 0.29 USB communication driver - core 0.32 (2.2.1) >Using subdriver: TrippLite HID 0.2 (experimental) >Startup timer elapsed, continuing... ># /usr/local/ups/sbin/upsd -u root >Network UPS Tools upsd 2.2.1 >listening on 0.0.0.0 port 3493 >Can't connect to UPS [SMART1000LCD] (usbhid-ups-SMART1000LCD): No such file or directory >The processes are running: ># ps -eo pid,user,sz,vsize,nice,state,args | grep ups >24420 root 467 1868 0 S /usr/local/ups/bin/usbhid-ups -a SMART1000LCD -u root >24428 root 446 1784 0 S /usr/local/ups/sbin/upsd...

.../tripplite-hid.c @@ -71,6 +71,8 @@ static usb_device_id_t tripplite_usb_device_table[] = { { USB_DEVICE(TRIPPLITE_VENDORID, 0x2005), battery_scale_0dot1 }, /* e.g. TrippLite OMNI900LCD */ { USB_DEVICE(TRIPPLITE_VENDORID, 0x2007), battery_scale_0dot1 }, + /* e.g. TrippLite Smart1000LCD */ + { USB_DEVICE(TRIPPLITE_VENDORID, 0x2009), battery_scale_0dot1 }, /* e.g. TrippLite smart2200RMXL2U */ { USB_DEVICE(TRIPPLITE_VENDORID, 0x3012), battery_scale_1dot0 }, /* e.g. ? */ diff --git a/src/nut/nut-2.4.3/scripts/udev/52-nut-usbups.rules b/etc/udev/rules.d/52-...

Hi, I was wondering if Tripp lite SMART1000LCD is working in nut or what code I should change to get it to work. I saw some older posts about this model and the OMNI1000 LCD but the model I have has a different product ID, 2007 vs. 2005: Device descriptor: VID:09ae, PID:2007 Device release:0x10, USB release:0x110 Descriptor Length:18, Type...

I have just compiled and installed nut-2.4.1 and I get the following errors when I try it: There is no difference if I run it as root or normal user. Any help would be appreciated. # usbhid-ups -DDD -a SMART1000LCD Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 debug level is '3' upsdrv_initups... Checking device (1D6B/0002) (001/001) libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied. libusb requires write access to USB device nodes. Failed...

...river. Some features may not function correctly. Using subdriver: TrippLite HID 0.2 (experimental) HIDGetDataValue: Value too large for defined data type This began with r1072... I wanted to include a debug output but it does not seems to end: [root at teevee ~]# /usr/local/bin/usbhid-ups -D -a smart1000lcd Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.3.0-1352) Warning: This is an experimental driver. Some features may not function correctly. debug level is '1' upsdrv_initups... Using subdriver: TrippLite HID 0.2 (experimental) Path: UPS.PowerSummary.iProduct, Type: Featur...

Trying to get a Tripp-Lite to work with nut--Ubuntu 10.10. I was getting the error message "unable to claim USB device", tried to unbind the drivers to that device, and had the following delightful experience. In short, continue to get the same problem, and the drivers bound themselves back. Any suggestions? ----------- usb.conf has the following: [Tripp-Lite] driver = usbhid-ups port

Thanks Kjell for the help with the build problem. Thanks for your input, too, Charles. Now I have a new problem that I think has already been solved. I have Tripp Lite Smart1000LCD UPS (usb), but I can't get the newhidups driver to communicate correctly. I found a thread on the development list from last December where Jonathan Freedman described had a problem with this UPS in a thread called "Fun with TrippLite". The problem apparently was resolved with som...

Hey I recently picked up a couple SMART1000LCD TrippLite UPS's. These are similar to other usb ups's that have been mentioned on the list in the past few months. I tried a few patches posted last month and got some amount of success. That being said, I am thus far unable to get much love from the actual upsd itself. Any pointers in term...

...ew years ago, the NUT project got a large spreadsheet of testing results (mostly upsc output, rather than full end-to-end) from connecting many of their their USB UPS models to NUT from one of their sales offices. Interestingly, the following models have the same USB product ID as your UPS, and the Smart1000LCD was on that list: * http://networkupstools.org/ddl/Tripp_Lite/AVR900U.html * http://networkupstools.org/ddl/Tripp_Lite/G1010USB.html * http://networkupstools.org/ddl/Tripp_Lite/SMART1000LCD.html > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser...

At the company I work for, we are using many TrippLite OMNI900LCD UPSs and are having difficulty setting the lower transfer threshold voltage. On our other model, the Eaton MGE-3S550, this can be set using upsrw to set the input.transfer.lowsetting, but on the Omni900, this option is not available. In our testing, it defaults to ~95v but we want to set it to 84v. More info: - OS = OpenSuse 13.1 -

...ld use some help getting NUT to talk to my Tripp Lite G1000U. Searching Google for "Tripp Lite G1000U" returns exactly two hits at this writing, so that may not be a good sign. ;-) It may just be rebranded for sale through this source (Costco). Externally, the G1000U looks much like the SMART1000LCD: an amber LCD, jacks for coax and telephone, four protected receptacles and four non-protected, and a USB-only interface. Internally, it's product 2007, vendor 09ae. I am running FreeBSD 6.4 with a stock kernel (and so uhid is enabled) and I installed the FreeBSD port of NUT (nut-2.2.2) today...

Tripp Lite Smart1000LCD Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 This TrippLite device (09ae:2010) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not...

I have a Tripp-Lite BCPERS450, connected to a system running Ubuntu 16.04.3 LTS and NUT 2.7.2-4ubuntu1.2. I had to make my own /lib/systemd/system-shutdown/nutshutdown, but now everything is working except for powering on and off the UPS. Regardless of the settings of offdelay and ondelay in upsconf, and regardless of whether the AC power is on, when I say "upsdrvctl shutdown" the UPS