search for: smart1500lcd

...issue. In the end what worked for me was tweaking the udev rules. I have had no USB disconnects or stale data warnings so far. I only used one rule for my UPS: # /etc/udev/rules.d/62-nut-usbups.rules SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" # TrippLite # e.g. TrippLite SMART1500LCD - usbhid-ups ACTION=="add|change", SUBSYSTEM=="usb|usb_device", SUBSYSTEMS=="usb|usb_device", ATTR{idVendor}=="09ae", ATTR{idProduct}=="2012", MODE="664", GROUP="nut", RUN+="/sbin/upsdrvctl stop; /sbin/upsdrvctl start"...

...<nut-upsuser-bounces+david_zomaya= > tripplite.com at alioth-lists.debian.net> on behalf of Charles Lepple < > clepple at gmail.com> > *Sent:* Sunday, December 8, 2019 8:36 PM > *To:* Layne Fowler > *Cc:* nut-upsuser > *Subject:* [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD > repeatedly disconnecting and reconnecting > > This is an *EXTERNAL* email. Please take a moment and think before > clicking any links or opening any attachments from this email. If > suspicious, please forward to ishelpdesk at tripplite.com for review. > ------------------------...

..._____________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Charles Lepple <clepple at gmail.com> Sent: Sunday, December 8, 2019 8:36 PM To: Layne Fowler Cc: nut-upsuser Subject: [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD repeatedly disconnecting and reconnecting This is an EXTERNAL email. Please take a moment and think before clicking any links or opening any attachments from this email. If suspicious, please forward to ishelpdesk at tripplite.com for review. ________________________________ On Dec 8, 2019, at 5:4...

...n.net/pipermail/nut-upsuser/2019-June/011451.html> (you may need to do some RedHat-to-Debian translation for some of the pathnames.) > > OS - Raspbian GNU/Linux 10 (buster) > Kernel - 4.19.75-v7+ > Nut version - 2.7.4-8 > Installation method - From package > UPS - Tripp Lite SMART1500LCD Thanks for including all of the version information. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20191208/808c6eca/attachment.html>

On 12/8/19 8:18 PM, David Zomaya wrote: > > I haven't tried it on RaspberryPi, but if there's some specific Tripp > Lite information I can help with, let me know. > We had that discussion about the SMART1500LCDT  & USB a long time ago:-( I bought mine in 2013 (still going strong on the second set of batteries) and in August 2016 we had some discussions about the USB disconnects. I now use an USB hub which can turn it's ports off via software commands and when my Linux box (Odroid X2 - ARM) l...

My serial # is 2835BY0SM886900639, model # SMART1500LCD. Using stock nut, my UPS will turn back on after load off, even with no power connected. Servers boot up and fail when the UPS finally dies. Using my patched nut, the UPS will fail to turn on if the power returns after the shutdown command but before actual load off. It seems like this UPS is mi...

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.....

[when responding, please use reply-all - the list does not mangle the reply-to header] > On Aug 21, 2017, at 12:45 AM, Whiteshell Tech <neil at whiteshell-tech.com> wrote: > > I have attempted to set the delay higher using "upsrw -s ups.delay.shutdown=120 TrippLiteUPS at localhost" and confirmed the value with "upsc TrippLiteUPS at localhost" Still the UPS

Layne Fowler writes: > On Mon, Dec 9, 2019 at 12:58 AM Marco Walther > <<URL:mailto:marco at sonic.net>marco at sonic.net> wrote: > > Lite information I can help with, let me know. > > We had that discussion about the SMART1500LCDT  & USB a long time ago:-( I Ditto. > bought mine in 2013 (still going strong on the second set of batteries) > and in August 2016 we had some discussions about the USB disconnects. I junked mine. I couldn't get it to talk to nut, reliably. Dumb thing kept disconnecting. &...

Hi, Layne. I had a similar problem with my Tripp-Lite BCPERS450. You can see the previous correspondence by searching for site:alioth-lists.debian.net/pipermail/nut-upsuser BCPERS450 shutdown with Google. In particular, I fixed (well, worked around) the problem, as I wrote in https://alioth-lists.debian.net/pipermail/nut-upsuser/2018-March/011082.html I've been running with this code for

From: Layne Fowler <layne.fowler at gmail.com> Date: Fri, 3 Jan 2020 16:22:10 -0500 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? I didn't, because I don't use that functionality, though it does look as though it should be modified in just the same way. This might

Hi, Layne. Glad my changes helped. It's not surprising that there are some remaining race conditions. I'm afraid I can't remember whether I have this particular problem or not. My variable settings shown by upsc are below. I think the general plan should be to run the system on the UPS for as long as possible, then shut it down with the shortest delay possible that still allows for

Hi, David. Thanks for the offer of help. I have BCPERS450 serial number 2701DVHBC809300177. Unfortunately I'm about to go on a trip and will be away until the end of the month, so I don't have much time to discuss these things at the moment, but maybe Layne will have something to say. My understanding from when I was working on this a couple years ago is that the main problem in

On Aug 21, 2017, at 1:35 PM, Whiteshell Tech <neil at whiteshell-tech.com> wrote: > > I ran it again on battery and upsd running, set upsrw ok and then shutdown.return gave an "ERR CMD-NOT-SUPPORTED" Odd thing is after running that I am getting random timed ups powering off for one or two seconds then turns back on even on battery. Server then starts shutting down. Some

...low up. ________________________________ From: Ken Olum <kdo at cosmos.phy.tufts.edu> Sent: Tuesday, January 14, 2020 1:35:10 PM To: David Zomaya Cc: kdo at cosmos.phy.tufts.edu; layne.fowler at gmail.com; nut-upsuser at alioth-lists.debian.net Subject: [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD will not stay shut down when power is disconnected This is an EXTERNAL email. Please take a moment and think before clicking any links or opening any attachments from this email. If suspicious, please forward to ishelpdesk at tripplite.com for review. ___________________________________________...

...ec 9, 2019 at 12:58 AM Marco Walther <marco at sonic.net> wrote: > On 12/8/19 8:18 PM, David Zomaya wrote: > > I haven't tried it on RaspberryPi, but if there's some specific Tripp Lite > information I can help with, let me know. > > We had that discussion about the SMART1500LCDT & USB a long time ago:-( > I bought mine in 2013 (still going strong on the second set of batteries) > and in August 2016 we had some discussions about the USB disconnects. > > > I now use an USB hub which can turn it's ports off via software commands > and when my Linux...

...Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> On Behalf Of Ken Olum Sent: Tuesday, January 14, 2020 11:24 AM To: Layne Fowler <layne.fowler at gmail.com> Cc: nut-upsuser at alioth-lists.debian.net Subject: [EXTERNAL] Re: [Nut-upsuser] Tripp Lite SMART1500LCD will not stay shut down when power is disconnected This is an EXTERNAL email. Please take a moment and think before clicking any links or opening any attachments from this email. If suspicious, please forward to ishelpdesk at tripplite.com for review. ___________________________________________...

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

Greetings all, Anyone have a clue on this behavior (see below) on this behavior with FreeNAS-8.3.0-RELEASE-x64 (r12701M) on a TrippLite 1500LCD UPS? NUT version is 2.6.5 Using the following profile: Tripp-Lite ups 2 Smart1500LCD USB (usbhid-ups) I get the following: Dec 10 21:40:12 nas6 kernel: uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.02, addr 2> on usbus1 Dec 10 21:40:12 nas6 notifier: Will not 'restart' nut because nut_enable is NO. Dec 10 21:40:12 nas6 notifier: Will not 'restart'...

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