similar to: compatibility with Tripps SMART/OMNI/OMNISMART ?

Hey all, I have a omnismart 1050 which i've got working under nut 2.2.2. It starts fine, and seems to poll fine. The only thing that is throwing me for a loop is my UPS is reporting that battery.runtime isn't supported. Will this affect upsmon's ability to shutdown my system in a power outage? I can whip up a simple bash script to take care of it but ideally I'd like to work

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 -

I have a Tripp Lite OMNI900LCD. It has a usb connector and claims to be USB/HID. I haven't been able to get it to work with newusbhid or tripplite_usb. Here's lsusb -v output: Bus 001 Device 013: ID 09ae:2005 Tripp Lite Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level)

We have multiple TrippLite Omni900LCD UPS. There are a couple pieces of equipment connected to each UPS. I would like to connect the UPSs to one computer through USB which would shutdown the appropriate equipment based on events monitored by upsmon using upssched. I've configured NUT using usbhid-ups driver and compiled/installed NUT. I've done some testing and it seems to work.

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2

Hi! I am trying to get an Atlantis-Land 1501 UPS to work under OpenBSD. The UPS works OK under Linux + megatec_usb driver+nut_2.2.2. What I get under OpenBSD is: root at puffwall:~ # dmesg OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2

Thanks to some outside suggestions and contributions we now have another release. If you missed the original announcement, rbcomplete provides a vim7 omni-completion function (code completion) for vim. It is based on complete.rb, pycomplete.vim and ccomplete.vim. Any input is welcome. Whats New: ------------ At the request of many people, Object''s instance methods are no longer

It''s been a while, but I''m back again with a new version. If you missed the original announcement, rubycomplete provides a vim7 omni-completion function (code completion) for vim. It is based on complete.rb, pycomplete.vim and ccomplete.vim. Any input is welcome. I''ve joined up with the vim-ruby team, so you''ll find rubycomplete.vim in cvs at

Once again after some work we have another release, with may bugfixes and improvements. If you missed the original announcement, rubycomplete provides a vim7 omni-completion function (code completion) for vim. It is based on complete.rb, pycomplete.vim and ccomplete.vim. Any input is welcome. I''ve joined up with the vim-ruby team, so you''ll find rubycomplete.vim in cvs at

Hi all, I''ve hacked away at complete.rb and some of the existing vim7 omni-completion functions to create a ruby completion function. It "works for me", any input is welcome. As a note, it will attempt to load any modules required by the current buffer when attempting to complete. You can find the link here:

Once again after some work and outside contribution we have another release If you missed the original announcement, rubycomplete provides a vim7 omni-completion function (code completion) for vim. It is based on complete.rb, pycomplete.vim and ccomplete.vim. Any input is welcome. I''ve joined up with the vim-ruby team, so you''ll find rubycomplete.vim in cvs at

Hi, I am new to GlusterFS. I have 2 computers with Intel Omni-Path hardware/software installed. RDMA is running ok on those according to "ibv_devices" output. GlusterFS "server" installed and set up ok on those. Peer probes on TCP-over-OPA worked ok. I created a replicated volume with transport=tcp, then tested them by mounting the volume on one of servers. Things worked

I just purchased a new ups and I'm unsure about several things. For one thing I don't know what driver I need. Also, it uses a usb port and I had a serial port before. I'm not sure how this needs to be set up. Thanks in advance for help Barbara -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

I have added preliminary support for the TrippLite protocol number 2001 into tripplite_usb.c. The attached file is supplied as a patch against today's SVN. This patch adds support for TrippLite SMART550USB and some Omni models. Tested are On Line, On Battery, Battery Good, and Battery Bad indication. Everything else seems to work, but this UPS is attached to a critical system, and I can

These patches allow this device to function in nut.. diff --git a/trunk/drivers/tripplite-hid.c b/new/drivers/tripplite-hid.c index c36da98..dddd13c 100644 --- a/trunk/drivers/tripplite-hid.c +++ b/new/drivers/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

Hello all; I am new to this list. Recently we have been getting these cheap new Tripp-Lite "LCD" style UPS'es around here, and I was surprised to find the lack of Linux support. The model name is OMNI650LCD. Anyway, I tried the tripplite_usb driver and got a message instructing me to contact this mailing list. I might try to fix the problem myself, if I was more familiar with the

I've just written an NUT driver to manage a Masterguard UPS connected via USB, and some questions arose. Why I wrote a new driver? The servers in question only have two serial ports, so I want to use USB. I first wrote the low-level USB routines expecting to integrate them into the existing masterguard driver. However, that driver was so rudimentary I wrote my own one. It can be

I am having an issue running NUT and using an TrippLite OMNI900LCD. When I run ./upsdrvctl start I get : [player@V0002-S002 bin]$./upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) Detected a UPS: Tripp Lite /TRIPP LITE UPS Using subdriver: TrippLite HID 0.1 (experimental) dstate_setflags: base variable

Dear Nut-UPSdev Team, First of all I would like to appreciate the great job you are doing. Your work is very important and helpful for all UPS users. I found that you show compatibility with blazer_ser and blazer_usb for six of our models. Please inform me how we can make it happen that all our models become compatible? Who from your team added the compatibility with PowerWalker VI 850 LCD?

Why does > curve(function(y) y^2, from=0,to=1) not work, whereas > myf <- function(y) y^2 > curve(myf, from=0,to=1) work? For the former, I get the error message Error in curve(function(y) y^2, from = 0, to = 1) : 'expr' must be a function or an expression containing 'x' I'm using R1.7.0 under Windows XP. Damon Wischik.