similar to: Tripp-Lite SU2200XLA problem (fwd)

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 */ {

Your suggestion of rebuilding the driver fixed the issue of the UPS turning back during a power failure. Now the UPS shuts down the clients, then powers off appropriately. If power returns it turns back on also. The only bug is if power returns before the UPS has turned the load off. In that case the UPS will remain off until it is manually turned on. This might just be a limitation of this

On Jul 30, 2013, at 10:39 AM, Pavel Potcheptsov (EKTOS) wrote: > Is this a trouble? Driver use path /var/state/ups/ but upsd use path /var/db/nut/upsd.pid Yes, the driver and upsd need to agree on the path to the socket. From the FreeBSD ports tree: /usr/ports/sysutils/nut/Makefile: STATEDIR?= /var/db/nut [...] CONFIGURE_ARGS= --sysconfdir=${PREFIX}/etc/nut \

I see, so you kept the load.on.delay command but removed the check to see if it was handled. Did you do the same thing for the shutdown.stayoff logic? https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L562 This might be a dumb question but did this require you to recompile the kernel? These types of changes are way beyond my depth. Thank you for the direction! On Thu, Jan

Hi Charles, I've been monitoring for the past few days and NUT has been running solid. Tested and everything's working as it should. Thanks for all of your help on this, great to have it running well again and learned lot. ________________________________ From: Daniel Shields <grungelizard9 at hotmail.com> Sent: Tuesday, October 25, 2016 8:01 PM To: Charles Lepple Subject:

Hi, Just started using NUT with a Liebert PSI-XR 3000 with an Intellislot web card. It seems I can't get it to run properly. I am using NUT 2.6.0 built from source on Ubuntu 8.0.4 . My build parameters are : ./configure --enable-strip --with-linux-hiddev=/usr/include/linux/hiddev.h --with-udev-dir=/lib/udev \ --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \

Hi, Charles I'm trying compilation but there is no configure command in the cloned git directory of nut. D?a 08.10.2017 o 23:47 Charles Lepple nap?sal(a): > On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: >> Thank You for You reply, Charles >> >> >> D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): >>> Is the "lan4.1" cable different

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() returned -1 instead of 8 Could not reset watchdog. Please send model information to nut-upsdev mailing

I?m wondering if what I have done is good : # get the source from github on my computer # autogen.sh # name=nut # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-pidpath=/var/run/$name

On Jul 31, 2013, at 9:07 AM, James HORLEY wrote: > I?m wondering if what I have done is good : > # get the source from github on my computer > # autogen.sh > # name=nut > # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man > --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name > --with-statepath=/var/run/nut

On Sat, Mar 11, 2017 at 7:15 PM, David Baker <david at baker.im> wrote: > Hi Arnaud & Charles, > > > > You?ll have to forgive my low level of Linux Understanding here?. > > > > I downloaded the source files, modified the appropriate driver file, > re-compiled it (all of this was a lot of research and learning!) > > > > When I use the new driver I

On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: > > Thank You for You reply, Charles > > > D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): >> Is the "lan4.1" cable different from this one? http://networkupstools.org/cables.html#_tripp_lite > > Yes, it is different. The correct cable for this interface version looks like this: >

sending to the list for posterity. > On Oct 27, 2016, at 6:43 AM, Raymond Day wrote: > > Thank you. > > Looked like that worked. > > I put your code in /etc/nut/nut.conf just at the end of that file. > > Then did. > > upsdrvctl start > > upsc serverups > > Got this date back: > > battery.charge: 100 > battery.charge.low: 10 >

Anybody knows what configure command settings FreeNAS use to compile NUT? More info on my journey: http://forums.freenas.org/index.php?threads/nobreak-bz1200-br-back-ups-rs-1200va-600w-bivolt-115-nt.20247/ Thanks Bruno -------------- next part -------------- An HTML attachment was scrubbed... URL:

My apologies, I forgot a step. See below. > On Oct 9, 2017, at 1:59 PM, tuharsky at misbb.sk wrote: > > Hi, Charles > > I'm trying compilation but there is no configure command in the cloned git directory of nut. > > > D?a 08.10.2017 o 23:47 Charles Lepple nap?sal(a): >> On Oct 8, 2017, at 4:34 PM, tuharsky at misbb.sk wrote: >>> Thank You for You

I've been wanting to build the trunk since Arjen added the powerpanel driver... been having a little trouble... after running these commands: /usr/local/libexec/automake19/aclocal -I m4 /usr/local/libexec/autoconf259/autoheader /usr/local/libexec/automake19/automake -ac /usr/local/libexec/autoconf259/autoconf ./configure --with-cgi --with-user=nutmon

I'm pretty sure, I've install pkg-config, but I will check it monday after my holliday. This is my test steps: - Shutting down nut-client (upsmon) - Only nut-server (driver + upsd) is running - upsmon.conf have been revert to normal shutdown, no upssched - upsc myups return ups stats then: upsmon -K -DDDDD, here is the output: kill: No such process UPS: myups at

- Charles > On Oct 16, 2016, at 3:34 AM, Daniel Shields <grungelizard9 at hotmail.com> wrote: > > I've been testing with debug further and there's a few extra lines when the nut-server stops communicating as opposed to when it's running. > > > Backtrace after stale data, UPS nailbunny at localhost is unavailable: > Sorry to take a while to get back to you

Dear Arnaud, > guys, > > sorry for the lag in jumping over there. > You anyway do a good job! Thanks for prompt answers! > > If you want to do it yourself: > - look here for the needed build tools > http://www.debian.org/doc/maint-guide/ch-start.en.html#s-needprogs > - svn co svn://svn.debian.org/nut/trunk > - cd trunk > - ln -s packaging/debian > - fakeroot

Thank You for You reply, Charles D?a 07.10.2017 o 14:30 Charles Lepple nap?sal(a): > Is the "lan4.1" cable different from this one? > http://networkupstools.org/cables.html#_tripp_lite Yes, it is different. The correct cable for this interface version looks like this: http://pinouts.ru/UPS/tripplite_smartpro_cable_pinout.shtml > Are you comfortable with rebuilding the