similar to: Tripp-Lite SMART1500LCDT

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

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

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 port > I don?t know if that will give you any insight or eliminate certain things with the Tripp Lite

On May 22, 2016, at 10:18 AM, Stuart Gathman wrote: > > I have a ticket open with TrippLite, but at this point it seems to be a > software, rather than hardware problem, since with the newer kernel and > usbhid-ups, the ups stays on the bus, and I could kludge around the > problem by making systemd keep restarting nut-driver. They seem to be > interested in actually resolving

[please use reply-all to include the list - the NUT lists do not add a reply-to header.] On Oct 23, 2015, at 2:03 AM, Null <null at wuffleton.com> wrote: > > Hi List, > > I recently picked up a Tripp Lite SMART1500LCDT while they were on sale to pair with my home server, and have tried getting it set up with NUT, since it seems to be supported. I can get the whole NUT stack up

On 08/03/2016 05:25 AM, Stuart Gathman wrote: > I've made some progress getting this Tripplite to work: > http://gathman.org/2016/07/30/Standard_Schmandard/ > > Basically, plug it into a USB hub that actually implements USB2.0, then > power cycle the port when it hangs. It does seem to be a hardware > problem with the USB controller. Finally an idea;-) I had the same problem

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

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

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

I bought this UPS to use with NUT. I've used Belkin, APC, CyberPower, Best, Powerware upses with NUT on dozens of servers beginning with RHEL3. http://www.amazon.com/Tripp-Lite-Display-Protection-SMART1500LCDT/dp/B009TZTGWK Since this was advertised as USB HID, I didn't expect any problems. Bad idea (should have gotten the Cyberware with somewhat less runtime). Initially, it seems to

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 >

On 08/05/2016 01:36 PM, Stuart D. Gathman wrote: > On Fri, 5 Aug 2016, Marco Walther wrote: > >> On 08/03/2016 05:25 AM, Stuart Gathman wrote: >>> I've made some progress getting this Tripplite to work: >>> http://gathman.org/2016/07/30/Standard_Schmandard/ >>> >>> Basically, plug it into a USB hub that actually implements USB2.0,

I've made some progress getting this Tripplite to work: http://gathman.org/2016/07/30/Standard_Schmandard/ Basically, plug it into a USB hub that actually implements USB2.0, then power cycle the port when it hangs. It does seem to be a hardware problem with the USB controller. On 05/24/2016 09:06 AM, Charles Lepple wrote: > On May 22, 2016, at 10:18 AM, Stuart Gathman wrote: >> I

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

Hi List, I recently picked up a Tripp Lite SMART1500LCDT while they were on sale to pair with my home server, and have tried getting it set up with NUT, since it seems to be supported. I can get the whole NUT stack up and running, but the driver seems to only stay up for a couple minutes before crashing out. I've uploaded the level 6 debug output of the driver (with my serial number

On Wed, Aug 7, 2013 at 6:47 PM, Charles Lepple wrote: > 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

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

On 2015-10-23 5:42, Charles Lepple wrote: > So the interesting part is that I was testing the master branch yesterday (same commit) on an older Debian box (3.16 kernel). The driver had trouble starting, but once it got going, it has been running continuously. > > I'm not really sold on this approach (due to the testing needed on other hardware), but this pull request reworks the USB

On 08/05/2016 03:03 PM, Marco Walther wrote: > On 08/05/2016 01:36 PM, Stuart D. Gathman wrote: >> On Fri, 5 Aug 2016, Marco Walther wrote: >> >>> On 08/03/2016 05:25 AM, Stuart Gathman wrote: >>>> I've made some progress getting this Tripplite to work: >>>> http://gathman.org/2016/07/30/Standard_Schmandard/ >>>> >>>>

On Fri, 5 Aug 2016, Marco Walther wrote: > On 08/03/2016 05:25 AM, Stuart Gathman wrote: >> I've made some progress getting this Tripplite to work: >> http://gathman.org/2016/07/30/Standard_Schmandard/ >> >> Basically, plug it into a USB hub that actually implements USB2.0, then >> power cycle the port when it hangs. It does seem to be a hardware >>