search for: tripplite_usb

...gument 3 of usb_interrupt_read differ in signedness gcc -I../include -O -Wall -Wsign-compare -c bcmxcp_usb.c bcmxcp_usb.c: In function get_answer: bcmxcp_usb.c:47: warning: pointer targets in passing argument 3 of usb_interrupt_read differ in signedness gcc -I../include -O -Wall -Wsign-compare -c tripplite_usb.c tripplite_usb.c: In function hex2d: tripplite_usb.c:350: warning: pointer targets in passing argument 1 of __builtin_strncpy differ in signedness tripplite_usb.c:350: warning: pointer targets in passing argument 2 of __builtin_strncpy differ in signedness tripplite_usb.c:352: warning: pointer tar...

Hi, When I start upsd under normal conditions, I get this: -------------------------------------------------------------------------------- Network UPS Tools upsd 2.0.4 /etc/nut/upsd.conf is world readable Can't connect to UPS [tripplite] (tripplite_usb-auto): No such file or directory /etc/nut/upsd.users is world readable Synchronizing........ giving up -------------------------------------------------------------------------------- Looking at the state directory, it is obvious what the problem is: ----------------------------------------------...

...s on line power, correct? I will update the nut-server init script with the sleep/reboot logic per FAQ #51. My larger concern is testing the UPS to ensure it shuts down correctly and comes back up correctly as well. My concern is driven by my observation that with older versions of NUT using the tripplite_usb driver, this UPS has *not* correctly shut down while on battery, thus the batteries drained and the UPS never supplied load power once line power had been restored. I assume the next logical test would be to do the same test (/lib/nut/tripplite_usb -a tripplite -k -DDD) while the UPS is on battery...

He everyone, I have a Tripplite SMART700DVa using the tripplite_usb from NUT 2.5 (rev 2217) driver running in Solaris 10x86. My driver hangs when trying to connect. Once the driver sends the watchdog command ("W\0"), it can no longer receive any signals and eventually exits. The UPS responds to other watchdog commands ("W5" for example), but the...

All, I recently purchased a Tripp-Lite OmniVS1500XL and am running NUT on a Centos-based system. Based on the compatibility list I specified the tripplite_usb driver. When I query the unit I get: [root@chryxus ~]# upsc UPS@localhost battery.voltage.nominal: 24 driver.name: tripplite_usb driver.version: 2.0.3-pre2 driver.version.internal: 0.6 input.voltage.nominal: 120 ups.debug.0: 20 01 58 58 58 58 0d '..XXXX.' u...

On Dec 16, 2008, at 10:36 AM, Bradley Feldman wrote: > Looking at the syslog, I noticed that the tripplite_usb driver > segfaulted > once it switched to battery (see below). I'm not sure whether you > still > maintain the driver or if I need to file a bug somewhere. I still have the unit in question; however, since the segfault happened inside libc, I won't be able to reproduce i...

Hi, my nut version is 2.2.2-6.4, debian lenny The ups we use is a tripplite OMNIVS1000 USB The drivers i tried are tripplite_usb and usbhid-ups, googled very long about the problems, but didn't get it to run. Does someone has experiences or similar problems? lsusb and lsmod are all right in /etc/udev/rules.d/52_nut-usbups.rules I found one line according to the modell ---- # Tripp Lite - tripplite_usb SYSFS{idVendor...

On 6/21/07, Arjen de Korte <nut+devel at de-korte.org> wrote: > Charles, > > The same remarks as for the reconnect_ups() patch for usbhid-ups.c go for > the function with the same name in tripplite_usb.c. This is also blocking > and thereby locking up the communication between driver and server. I > don't think this is intentional, since the MAX_RECONNECT_TRIES in > usb_comm_fail() is effectively a no-op then. I also seems to duplicate > some things in usb_comm_fail(), like upsdrv...

Hi, I'm using nut 2.2.1 on Ubuntu Hardy. Everything is fine, upsc works, upsmon is working. Then, after twenty minutes or an hour or maybe even longer, it all breaks down and I see these messages in the log: May 22 13:39:04 logicserver upsmon[28319]: Poll UPS [tripplite at localhost] failed - Driver not connected Restarting upsd fixes the problem temporarily. Any ideas? Thanks, Forest

Hello, I have a Tripplite SMART1500 UPS, and I'm having a little luck with the tripplite_usb driver. Only a LITTLE though. It's working better than any of the other drivers I've tried, but I'm not getting a status from it. Here's the output of upsc: battery.voltage: 0.00 battery.voltage.nominal: 36 driver.name: tripplite_usb driver.parameter.port: /dev/hiddev0 driver.vers...

Hi, I'm working with svn trunk rev 815, testing tripplite_usb with this model. I haven't gotten far in my testing, but thought I'd notify the list of this error message. Is this message of any consequence, and is it worthwhile for me to continue testing prior to resolving this? I am happy to help debug any driver issues, so please let me know if I...

Short version - can I run NUT on an AIX box with UPS that has a USB interface, like a Tripplite OMNI1500 XL? I downloaded the source and compiled it, but then noticed that while the source file tripplite_usb.c file is present, it wasn't compiled (this is the driver shown on the compatibility list for my ups). So I started looking at the make files and noticed there were no entries in drivers/Makefile under USB_DRIVER_LIST. I added tripplite_usb and tried make build-usb. I now get an error messag...

...correct? I will update the nut-server init script with the sleep/reboot logic per FAQ #51. Correct. > My larger concern is testing the UPS to ensure it shuts down correctly and comes back up correctly as well. My concern is driven by my observation that with older versions of NUT using the tripplite_usb driver, this UPS has *not* correctly shut down while on battery, thus the batteries drained and the UPS never supplied load power once line power had been restored. To be honest, most of my testing with Raspbian has been just debugging drivers during normal operation, not with the shutdown scripts...

I got FreeBSD up and running last night (many thanks to Charles Sprickman for a ton of useful suggestions along the way), and took a look at tripplite_usb on an OMNIVS1000. The tripplite_usb driver basically sends old-school Tripp Lite serial commands to the UPS via HID SetReport packets, and receives responses over the first Interrupt IN pipe. Later UPSes seem to be more deterministic in this regard, but the OMNIVS1000 requires that you send a com...

I keep getting this kind of stuff in /var/log/messages Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt() returned -110 instead of 8 Should I be worried about it? upsc seems to work fine... I tried building the 2.0.5 but none of the included spec files seemed to work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to work out well either. Building f...

I keep getting this kind of stuff in /var/log/messages Jan 18 17:45:03 bulldog tripplite_usb[9979]: libusb_get_interrupt() returned -110 instead of 8 Should I be worried about it? upsc seems to work fine... I tried building the 2.0.5 but none of the included spec files seemed to work with opensuse 10.2 and adapting their 2.0.4 spec file didn't seem to work out well either. Building f...

As I understand it from looking through the archives of this mailing list and the source for the driver, tripplite_usb should work for this device. I tried to go through the source as best I could to see if I could add support myself, but got a bit lost. Anyhow, here's hoping that someone has some experience with this model. My system is using the latest CVS checkout of the Development branch (as of this messa...

...the alternate interface to 0 in drivers/libusb.c? I have seen some documentation which indicates that this should already done by the OS when the device is enumerated. If that is the case, then there is no reason why we should hardcode the alternate interface to 0. If I remove the following code, tripplite_usb seems to work*: /* set default interface */ usb_set_altinterface(udev, 0); Any objections to removing this? Can I get some volunteers to try this out on their non-OS X systems? I am using libusb-0.1.12 on Mac OS X 10.5.8. * I did have to monkey wit...

...he system is probably properly configured, but there may be a communication issue with the UPS. (may or may not be a logical assumption) Next, I provided non-UPS power to the NUT master and shut down all the loads connected to the UPS. I then manually issued the shutdown via the driver (/lib/nut/tripplite_usb -a tripplite -k -DDD) but the UPS still remained up. I don't know enough about NUT to debug this completely, but my hunch is that the problem is with the communication between the driver and the UPS, I'm just not clear on how to debug further. Thanks for any additional assistance and insi...

Hello, I've got Tripplite Smart Int 1000 UPS with lan4.1 serial interface. Quite sympathetic UPS, I must say from first glance. I have made a proper serial cable (btw i hate all those constructor's decisions to make distinct serial wiring for each and every UPS type from each and every manufacturer!) I use [tripplite] driver for NUT and I can use upsc to get report from UPS, but