similar to: Seriously confused...

OS = NAS4Free (FreeBSD Revision: 199506) NUT Version = 2.7.3 for other parts of NUT version is listed below NUT is part of the NAS4Free distribution Device = Tripp Lite SMART1300LCDT URL http://www.tripplite.com/line-interactive-ups-system-desktop-tower-1300va-120v-usb-port-lcd-screen~SMART1300LCDT/ PROBLEM: NUT is ABLE to see the UPS BUT it is not getting the right(?) descriptor? I am using

We're looking at replacing some old APC SmartUPS 5000s with something that has USB so NUT can more easily talk with it (and yes, I've tried USB-RS232 adapters and every one I tried started kicking out errors within a few hours). One of the bids we have is for a "Tripp Lite UPS Smart Online 5000VA 4500W Rackmount 5kVA 200V/240V" as the potential replacement unit. I have no

Here are couple of things I tried. 1) Changed the USB cable. Same problem 2) I put an old CyberPower CP550SL w/USB&SERIAL and it recognize it right away via the USB port I don?t know if that will give you any insight or eliminate certain things with the Tripp Lite SMART1300LCDT or not. Sent from Mail for Windows 10 From: Charles Lepple Sent: Tuesday, August 18, 2015 6:37 PM To: Johnny

On Aug 19, 2015, at 9:00 AM, Charles Lepple <clepple at gmail.com> wrote: > > On Aug 19, 2015, at 12:08 AM, Johnny Wong <e430benz98 at yahoo.com> wrote: >> >> Here are couple of things I tried. >> >> 1) Changed the USB cable. Same problem >> 2) I put an old CyberPower CP550SL w/USB&SERIAL and it recognize it right away via the USB

Hi Everyone, I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine, connected via a USB cable. I installed Nut 2.7.4 from the Mint package repository via sudo apt update && sudo apt install nut. Everything works great: NUT issues low battery warning when it reaches the set low battery point and then issues shutdown commands...computer shuts down..then the UPS shuts

> Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only >write a PID file when the driver goes into the background, and "-D" prevents that. I don't see another usbhid-ups running ... unless its "hidden".... I would have to install the unhide package then.... /var/run/devd.pid

I have gotten the links to the ./configure for NUT for NAS4Free see nas4free build makefile http://sourceforge.net/p/nas4free/code/ ... t/Makefile config files: http://sourceforge.net/p/nas4free/code/ ... nut/files/ I hope this give some insights On Wednesday, August 19, 2015 6:00 AM, Charles Lepple <clepple at gmail.com> wrote: On Aug 19, 2015, at 12:08 AM, Johnny Wong

Tripp Lite SMART1300LCDT # upsc ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.runtime: 2951 battery.type: PbAC battery.voltage: 0.0 battery.voltage.nominal: 24.0 device.mfr: Tripp Lite device.model: TRIPP LITE UPS device.serial: 2250AVLSM872100251 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

> > battery.charge: 3 > battery.charge.low: 10 > battery.charge.warning: 30 > battery.runtime: 93 > battery.temperature: 32.9 > battery.type: PbAC > battery.voltage: 46.4 > battery.voltage.nominal: 48.0 Is it possible that battery.charge is really 30% rather than 3%? The 3016 protocol models have issues with scaling on some of the voltages and frequencies. You can see

On Aug 7, 2013, at 10:43 AM, Matthew Lenz wrote: > Tripp Lite SMART1300LCDT > > # upsc ups [...] > battery.voltage: 0.0 > battery.voltage.nominal: 24.0 [...] > input.frequency: 5990.0 > input.transfer.high: 150.0 > input.transfer.low: 92.0 > input.voltage: 0.0 > input.voltage.nominal: 120 > output.current: 100.00 > output.frequency: 5990.0 >

Did my last message get through? I got a message from the list saying it "bounced" or something like that? Sent from Mail for Windows 10 From: Charles Lepple Sent: Wednesday, August 19, 2015 6:00 AM To: Johnny Wong Cc: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] Need help with Tripp Lite SMART1300LCDT NUT v2.7.3 On Aug 19, 2015, at 12:08 AM, Johnny Wong

So when the UPS is communicating with the driver... it seems to work.? Problem is now that it keeps disconnecting.? Any recommendation on how to keep the drivers from disconnecting using the usb_set_altinterface?? (PS.? Is there a specific value to use?)? Or this confirms there is an issue with the usbhid-ups driver with the FreeBSD 10.2 kernel? upsc upstl1300 battery.charge: 100

> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a

Hi Everyone, New to the list. Thanks in advance for any assistance you are able to provide. I have a TrippLite SMART2200RM2UN UPS. I have installed and configured NUT as instructed on the website, and am able to monitor the status of the UPS without much problem. The only problem I am seeing is that I cannot get the machine to actually send a Low Battery ( LB ) signal. When I run

Thanks again for your help, Charles. I was able to install the Tripp Lite software on my Ubuntu machine, and it sort of works. It does something which continually changes the USB device ID of the UPS, and prints voluminous error messages in the log. However, one of the things that it can do is to schedule a UPS shutdown, which Nut does not know how to do. So I monitored the USB port with

Hello, https://networkupstools.org/ddl/Tripp_Lite/AVR750U.html Going off of this page, it looks like this should be supported by usbhid-ups, but it seems to be failing. Attached is a log of my attempts to start the driver. Let me know what I can do to help. -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Aug 17, 2015, at 1:00 AM, Johnny Wong <e430benz98 at yahoo.com> wrote: > > OS = NAS4Free (FreeBSD Revision: 199506) What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) > NUT Version = 2.7.3 for other parts of NUT version is listed below > NUT is part of the NAS4Free distribution > Device = Tripp Lite SMART1300LCDT URL

Hi, I'm trying to get a better understanding of what a timer is, so I added the following line to upssched.conf # Debug - turn on long-running timer to find out where upssched puts it AT ONBATT * START-TIMER where-am-I 1000 I can then start this timer by pulling the power cord from the wall for just a few seconds. I now have 1000 seconds to find the timer. I don't see it in

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

I?m setting up a new system and installed a new UPS with nut. System Specifics: OS: Debian 3.16.36 Nut version: 2.7.2 Install method: apt-get Device: TRIPPLITE SMART1300LCDT using usbhid-ups driver Problem: The output from upsc has a few incorrect values. They appear to be a matter of scale. root at server:/etc/nut# upsc tripplite at localhost Init SSL without certificate database