I did get this ups working with nut with tripplite_usb. Not exactly sure
what fixed it. I think I had to specify the bus number in ups.conf.
All is well now. I thank everyone for their time.
Charles Lepple writes:
>Correct me if I am wrong, but for the Tripp Lite vendor ID (09AE),
>there are
On Sep 9, 2009, at 7:43 PM, Leslie Rhorer wrote:
interesting, I was thinking that tripplite_usb was for older
units, not
HID compliant.
the newer runs usbhid-ups, but I'm now wondering if these are HID
compliant.
but looking at the lsusb output, the report size seems too short for
this.
anyw
> >interesting, I was thinking that tripplite_usb was for older units, not
> >HID compliant.
> >the newer runs usbhid-ups, but I'm now wondering if these are HID
> >compliant.
> >but looking at the lsusb output, the report size seems too short for
> this.
> >anyway, just thinking out loudly.
>
> I
Citeren Chris Abel :
When using the tripplite_usb driver I get the same thing:
Checking device (09AE/0001) (001/002)
- VendorID: 09ae
- ProductID: 0001
- Manufacturer: TRIPP LITE
- Product: TRIPP LITE UPS
- Serial Number: unknown
- Bus: 001
Trying to match device
Device does not match - skipping
Arjen de Korte writes:
>We told you a couple of times already, this device is not supported by
>usbhid-ups (and never will either). Don't waste our time by repeatedly
>posting attempts to use this driver.
>
>Do as I told you before and run this driver with
>
> /path/to/tripplite_usb -D
Citeren Chris Abel :
Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1)
Warning: This is an experimental driver.
Some features may not function correctly.
Error: UPS [Tripp-Lite] is for driver usbhid-ups, but I'm tripplite_usb!
You failed to update the 'ups.conf' file. You *
Alright, I'm geting some where! Found out that the mac terminal does some
weird things with tabs and you cannot tab in it. I switched to linux and
all is well. This is what I receive when I try to start the driver with
tripplite_usb:
Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4
Citeren Chris Abel :
Am I the only one that has trouble compiling this with Ubuntu?
You clearly have a problem with control characters that are being
added somehow. Maybe it's the mail reader your using or some obscure
character set, I don't know. The attached shell script might work for
When I simply copy and replace the following I get this at the end of
./configure:
checking user to run as...
ups--with-group=nut--sysconfdir=/etc/nut/--mandir=/usr/share/man--libdir=/lib/cludedir=/usr/include/--without-ssl--without-hal--with-cgi--with-dev--enable-static--with-statepath=/var/run/nu
Citeren Chris Abel :
I have attached my config.log.
You have some strange characters in the ./configure line. Please try
again with the following:
./configure --with-user=ups \
--with-group=nut\
--sysconfdir=/etc/nut \
--mandir=
2009/9/8 Chris Abel
> I did manage to get tripplite_usb and upsdrvctl working with different
> tags in ./configure, but I still do not think it is correct. This is my
> output for tripplite_usb -D -a ups1:
> Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1)
> Warning: This
Citeren Chris Abel :
It seems that whenever I specify a different directory in a ./confgure tag
it does not get applied right.
Please post the contents of your 'config.log' file here.
Best regards, Arjen
--
Please keep list traffic on the list
___
I did manage to get tripplite_usb and upsdrvctl working with different
tags in ./configure, but I still do not think it is correct. This is my
output for tripplite_usb -D -a ups1:
Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.4.1)
Warning: This is an experimental driver.
Some
Arjen de Korte writes:
>In that case, try if adding
>
> --without-snmp
>
>to the configure command line helps. It shouldn't (since the
>prerequisites for building the snmp-ups driver should be checked
>automatically), but chances are this is failing for you.
I think I'm getting some where
Hi Chris,
> Arnaud Quette writes:
> >are you sure that you have re executed configure, and that you have the
> >above "build USB drivers: yes" message?
> >don't forget to call make too.
> >I see no reason for not having tripplite_usb if the above are met.
> >please, fix that point first.
>
> I s
Citeren Chris Abel :
Although I do have that tag in my ./configure, I do not have the directory
/lib/nut after running make install. I have a lot of errors after running
make and make install. All related to snmp-ups.c
In that case, try if adding
--without-snmp
to the configure command l
Arjen de Korte writes:
>If you followed the instructions Arnaud send before, you told the
>configuration script
>
> --with-drvpath=/lib/nut
>
>So when you ran 'make install' the drivers were probably installed
>there, so you may need to try
>
> /lib/nut/tripplite_usb -D -u root -a
Citeren Chris Abel :
then fire drivers/tripplite_usb -D -a
# drivers/tripplite_usb -D -a Tripp-Lite
bash: drivers/tripplite_usb: No such file or directory
# tripplite_usb -D -a Tripp-Lite
bash: tripplite_usb: command not found
If you followed the instructions Arnaud send before,
Arnaud Quette writes:
>are you sure that you have re executed configure, and that you have the
>above "build USB drivers: yes" message?
>don't forget to call make too.
>I see no reason for not having tripplite_usb if the above are met.
>please, fix that point first.
I suspect it is because of my
2009/9/8 Chris Abel
> Arnaud Quette writes:
> >seems you don't have libusb-dev installed on your system (needed to
> >compile the USB drivers).
> >you can see it in the configure report, ie:
> >...
> >build USB drivers: yes
> >...
> >
> >so "sudo apt-get install libusb-dev"
>
> I had already don
Arnaud Quette writes:
>seems you don't have libusb-dev installed on your system (needed to
>compile the USB drivers).
>you can see it in the configure report, ie:
>...
>build USB drivers: yes
>...
>
>so "sudo apt-get install libusb-dev"
I had already done this. To double check I did this again:
R
2009/9/8 Chris Abel
> Arnaud Quette writes:
> >ok, now you can recompile 2.4.1 with the flags mentioned before, and do
> >only a make (not install)
> >
> >then fire drivers/tripplite_usb -D -a >/etc/nut/ups.conf>
> # drivers/tripplite_usb -D -a Tripp-Lite
> bash: drivers/tripplite_usb:
Arnaud Quette writes:
>ok, now you can recompile 2.4.1 with the flags mentioned before, and do
>only a make (not install)
>
>then fire drivers/tripplite_usb -D -a /etc/nut/ups.conf>
# drivers/tripplite_usb -D -a Tripp-Lite
bash: drivers/tripplite_usb: No such file or directory
# tripplite_
2009/9/4 Chris Abel
> Arnaud Quette writes:
> >ok, before going to deep on this and wasting too much time on
> >compilation, I'd like to have:
> >- the output of "lsusb -vv -d09ae:0001".
> Bus 001 Device 002: ID 09ae:0001 Tripp Lite
> Device Descriptor:
> bLength18
> bDescripto
Arnaud Quette writes:
>ok, before going to deep on this and wasting too much time on
>compilation, I'd like to have:
>- the output of "lsusb -vv -d09ae:0001".
Bus 001 Device 002: ID 09ae:0001 Tripp Lite
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB
2009/9/4 Chris Abel
> Yes, This is my config summary:
>
> enable SSL development code: yes
> enable libwrap (tcp-wrappers) support: no
> enable IPv6 support: yes
> build CGI programs: no
> build and install the development files: no
> build serial drivers: yes
> build SNMP drivers: yes
> build US
Yes, This is my config summary:
enable SSL development code: yes
enable libwrap (tcp-wrappers) support: no
enable IPv6 support: yes
build CGI programs: no
build and install the development files: no
build serial drivers: yes
build SNMP drivers: yes
build USB drivers: yes
enable HAL support: no
bui
2009/9/2 Chris Abel
> Arnaud Quette writes:
> >do a make uninstall first, and then use:
> >./configure --prefix=/usr --exec-prefix=/
> >--sysconfdir=/etc/nut --mandir=/usr/share/man
> >--libdir=/lib --includedir=/usr/include
> >--without-ssl --with
On Wed, Sep 2, 2009 at 12:48 PM, Arnaud Quette wrote:
> do a make uninstall first, and then use:
> ./configure --prefix=/usr --exec-prefix=/
> --sysconfdir=/etc/nut --mandir=/usr/share/man
> --libdir=/lib --includedir=/usr/include
> --without-ssl --wi
please keep the list posted Chris
2009/9/2 Chris Abel
My bad. I thought for sure we have Ubuntu 9.04. After double checking I
see that we are using Ubuntu 8.04. I will compile and install from source
and get back to you.
2009/9/2 Chris Abel
> My bad. I thought for sure we have Ubuntu 9.04. Aft
2009/9/2 Chris Abel
> NUT user list writes:
> >What does 'lsusb' return for this device?
> >
> Bus 002 Device 002: ID 09ae:0001 Tripp Lite
> >
> >
> >We will also need some basic information:
> >
> >* What OS?
> >* Which distribution?
> >* Did you install from source?
>
> Linux, Ubuntu Server 9.0
NUT user list writes:
>What does 'lsusb' return for this device?
>
Bus 002 Device 002: ID 09ae:0001 Tripp Lite
>
>
>We will also need some basic information:
>
>* What OS?
>* Which distribution?
>* Did you install from source?
Linux, Ubuntu Server 9.04. I did not install it from source, but I can
On Sep 1, 2009, at 3:33 PM, Chris Abel wrote:
Model: Tripp-lite OMNIVS1500
What does 'lsusb' return for this device?
Error:
Network UPS Tools - UPS driver controller 2.2.1-
Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11
(2.2.1-)
Warning: This is an experimental driver.
So
Model: Tripp-lite OMNIVS1500
Error:
Network UPS Tools - UPS driver controller 2.2.1-
Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-)
Warning: This is an experimental driver.
Some features may not function correctly.
Detected a UPS: unknown/unknown
libusb_set_report() retu
Hi,
On Fri, May 30, 2008 at 09:25:59AM +0200, Arjen de Korte wrote:
> >> No, just remove (or comment out) the call to upsdrv_cleanup() in the
> >> reconnect_ups() function and rebuild the driver. I suspect that this
> >> will solve the problem.
> >
> > This didn't seem to solve the problem (still
>> No, just remove (or comment out) the call to upsdrv_cleanup() in the
>> reconnect_ups() function and rebuild the driver. I suspect that this
>> will solve the problem.
>
> This didn't seem to solve the problem (still got a segfault). Any other
> ideas?
It looks like upsdrv_cleanup() is called
Hi,
On Thu, May 29, 2008 at 09:37:43PM +0200, Arjen de Korte wrote:
> >> Arjen pointed out what is the most likely cause of the segfault (our
> >> reconnection code has changed a bit since the driver was first
> >> written), but the problem is that I won't have time to work on that
> >> for a week
>> Arjen pointed out what is the most likely cause of the segfault (our
>> reconnection code has changed a bit since the driver was first
>> written), but the problem is that I won't have time to work on that
>> for a week or so.
>
> Would it behoove me to downgrade nut?
No, just remove (or commen
Hi,
On Thu, May 29, 2008 at 03:03:15PM -0400, Charles Lepple wrote:
> On Thu, May 29, 2008 at 2:52 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> > ups.model: UPS
>
> Heh. What model does this correspond to?
It's an OMNIVS1500XL. I'm pretty sure this used to get read correctly, prior to
the upgra
On Thu, May 29, 2008 at 2:52 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> ups.model: UPS
Heh. What model does this correspond to?
Also, do you know off-hand if it is a 12V or 24V battery pack?
thanks,
--
- Charles Lepple
___
Nut-upsuser mailing list
Hi,
On Thu, May 29, 2008 at 02:45:09PM -0400, Charles Lepple wrote:
> On Thu, May 29, 2008 at 2:05 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> > On Thu, May 29, 2008 at 02:01:39PM -0400, Charles Lepple wrote:
> >> Arjen pointed out what is the most likely cause of the segfault (our
> >> reconnect
On Thu, May 29, 2008 at 2:05 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Thu, May 29, 2008 at 02:01:39PM -0400, Charles Lepple wrote:
>> Arjen pointed out what is the most likely cause of the segfault (our
>> reconnection code has changed a bit since the driver was first
>> written), bu
Hi,
On Thu, May 29, 2008 at 02:01:39PM -0400, Charles Lepple wrote:
> On Thu, May 29, 2008 at 1:00 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> > Next, I tried to generate a plain old core file with:
> >
> > # ulimit -c 5
> > # /lib/nut/tripplite_usb -a tripplite -DDD
> >
> > I still get the s
On Thu, May 29, 2008 at 1:00 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Wed, May 28, 2008 at 10:01:58PM -0400, Charles Lepple wrote:
>> On Wed, May 28, 2008 at 4:55 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
>> > May 28 15:43:34 logicserver tripplite_usb[27408]: Error reading B value:
Hi,
On Wed, May 28, 2008 at 10:01:58PM -0400, Charles Lepple wrote:
> On Wed, May 28, 2008 at 4:55 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> > May 28 15:43:34 logicserver tripplite_usb[27408]: Error reading B value:
> > Device detached? (error 0: error sending control message: Operation not
>
>> May 28 15:43:34 logicserver upsd[27410]: Data for UPS [tripplite] is
>> stale - check driver
>> May 28 15:43:34 logicserver tripplite_usb[27408]: Reconnect attempt #1
>> May 28 15:43:34 logicserver upsd[27410]: UPS [tripplite] disconnected -
>> check driver
>> May 28 15:43:34 logicserver upsd[27
On Wed, May 28, 2008 at 4:55 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> May 28 15:43:34 logicserver tripplite_usb[27408]: Error reading B value:
> Device detached? (error 0: error sending control message: Operation not
> permitted)
> May 28 15:43:34 logicserver upsd[27410]: Data for UPS [trippl
[this didn't make it to the list the first time.]
On Wed, May 28, 2008 at 4:55 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Thu, May 22, 2008 at 07:13:25PM -0400, Charles Lepple wrote:
>> On Thu, May 22, 2008 at 1:39 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
>> > I'm using nut 2.2.1 on
Hi,
On Thu, May 22, 2008 at 07:13:25PM -0400, Charles Lepple wrote:
> On Thu, May 22, 2008 at 1:39 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> > 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 l
On Thu, May 22, 2008 at 1:39 PM, Forest Bond <[EMAIL PROTECTED]> wrote:
> 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:
>
>
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 [EMAIL PROTECTED] failed
- Drive
On 1/18/2007 9:36 PM, Charles Lepple wrote:
> On 1/18/07, Eric A. Hall <[EMAIL PROTECTED]> wrote:
>> 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? up
On 1/18/07, Eric A. Hall <[EMAIL PROTECTED]> wrote:
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...
It depends on the UPS model.
OMN
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 opens
On 8/25/06, Rob Harris <[EMAIL PROTECTED]> wrote:
Charles Lepple wrote:
> On 8/25/06, Rob Harris <[EMAIL PROTECTED]> wrote:
>> - VendorID: 09ae
>> - ProductID: 2005
>
> For Tripp-Lite product IDs other than 1, please use the newhidups
> driver instead.
>
No dice...
Sorry, I thought the Tripp-L
Charles Lepple wrote:
On 8/25/06, Rob Harris <[EMAIL PROTECTED]> wrote:
- VendorID: 09ae
- ProductID: 2005
For Tripp-Lite product IDs other than 1, please use the newhidups
driver instead.
No dice...
tipper nut # ./newhidups -DDD -u root -a tipper
Network UPS Tools: New USB/HID UPS driver
On 8/25/06, Rob Harris <[EMAIL PROTECTED]> wrote:
- VendorID: 09ae
- ProductID: 2005
For Tripp-Lite product IDs other than 1, please use the newhidups
driver instead.
--
- Charles Lepple
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.o
Is it me, or is my USB not being recognized properly?
tipper nut # ./tripplite_usb -DDD -u root -a tipper -x vendor=09AE
Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.4)
Warning: This is an experimental driver.
Some features may not function correctly.
debug level is '3'
Ch
58 matches
Mail list logo
