search for: omni1500lcdt

Anyone familiar with Cyberpower's model numbers? I finally got sick of my Tripplite's USB port going south, all the time, so I'm looking to replace it. The HCL has an entry for a Cyberpower model CP1500AVRLCD. Not listed is the CP1500PFCLCD model, a newer, premium version of the unit; but the HCL does have an entry for the CP1000PFCLCD model. Pretty sure that the CP1500PFCLCD

OpenBSD 6.1/amd64 nut-2.7.4p0 (from OpenBSD package) UPS: Tripp-Lite OMNI1500LCDT I cannot get the driver for the UPS to load without error. Here are the commands, with the output, and the config files: ======================================================= # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) U...

On 5/13/2017 10:20 AM, Charles Lepple wrote: > On May 12, 2017, at 10:06 AM, Mike <the.lists at mgm51.com> wrote: >> >> >> OpenBSD 6.1/amd64 >> nut-2.7.4p0 (from OpenBSD package) >> UPS: Tripp-Lite OMNI1500LCDT >> >> I cannot get the driver for the UPS to load without error. >> >> Here are the commands, with the output, and the config files: >> >> ======================================================= >> # upsdrvctl start >> Network UPS Tools - UPS driver c...

...s > have an entry for the CP1000PFCLCD model. > > Pretty sure that the CP1500PFCLCD will work; but figure I ask if anyone > knows for sure. I saw you got the answers you asked for. But I just wanted to chime in, saying that I was in a similar situation as you. I have a TrippLite Omni1500LCDT which I was attempting to use. I ran into similar USB problems with the TrippLite. I documented my experiences with the TrippLite in this thread: http://lists.alioth.debian.org/pipermail/nut-upsuser/2017-May/010655.html And my experinces with the CyberPower in this thread: The CyberPower UPS t...

Hi, I'm trying to find, & set up a compatable driver for a Tripp-Lite OMNI1500LCDT ups. Not having any luck with tripplite_usb, or usbhid-ups. Running nut 2.6.2-1 on Fedora 14. Installed from package. Suggestions? Dick Lawson [root at Muleyputer ~]# upsdrvctl start Network UPS Tools - UPS driver controller 2.6.2 Network UPS Tools - Generic HID driver 0.35 (2.6.2) USB com...

On May 12, 2017, at 10:06 AM, Mike <the.lists at mgm51.com> wrote: > > > OpenBSD 6.1/amd64 > nut-2.7.4p0 (from OpenBSD package) > UPS: Tripp-Lite OMNI1500LCDT > > I cannot get the driver for the UPS to load without error. > > Here are the commands, with the output, and the config files: > > ======================================================= > # upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.4 > Network...

...I am confusing it with protocol 3016 devices. We actually added a lot of the protocol 2012 devices to the hardware compatibility list based on the test results that Eric provided, so I assume they worked then (about six years ago). The protocol 3016 devices (in particular, the SMART1500LCDT and OMNI1500LCDT) sometimes don't even stay on USB long enough to read a USB descriptor, and this does seem correlated with newer motherboards. Example: https://github.com/networkupstools/nut/issues/577 From where I stand, there really shouldn't be anything that a user-space program (like a NUT driver) c...

...be I am confusing it with protocol 3016 devices. We actually added a lot of the protocol 2012 devices to the hardware compatibility list based on the test results that Eric provided, so I assume they worked then (about six years ago). The protocol 3016 devices (in particular, the SMART1500LCDT and OMNI1500LCDT) sometimes don't even stay on USB long enough to read a USB descriptor, and this does seem correlated with newer motherboards. Example: https://github.com/networkupstools/nut/issues/577 From where I stand, there really shouldn't be anything that a user-space program (like a NUT driver) can...

...t with protocol 3016 devices. We actually added a lot of the protocol 2012 devices to the hardware compatibility list based on the test results that Eric provided, so I assume they worked then (about six years ago). >> >> The protocol 3016 devices (in particular, the SMART1500LCDT and OMNI1500LCDT) sometimes don't even stay on USB long enough to read a USB descriptor, and this does seem correlated with newer motherboards. Example: https://github.com/networkupstools/nut/issues/577 >> >> From where I stand, there really shouldn't be anything that a user-space program (lik...

Hi Network UPS Tools Support, I'm not sure if this is a question for the "user group" or the developer group". My name is David Zomaya and I work at Tripp Lite in our technical support department. Copied on this email are Eric Cobb from our Product Management group & Jonathan Manzanilla tech support subject matter expert for our single phase UPS product lines. Recently,

Hi Network UPS Tools Support, I'm not sure if this is a question for the "user group" or the developer group". My name is David Zomaya and I work at Tripp Lite in our technical support department. Copied on this email are Eric Cobb from our Product Management group & Jonathan Manzanilla tech support subject matter expert for our single phase UPS product lines. Recently,

...tocol 3016 devices. We actually added a lot of the protocol 2012 devices to the hardware compatibility list based on the test results that Eric provided, so I assume they worked then (about six years ago). >> >> The protocol 3016 devices (in particular, the SMART1500LCDT and >> OMNI1500LCDT) sometimes don't even stay on USB long enough to read a >> USB descriptor, and this does seem correlated with newer >> motherboards. Example: >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_netwo >> rkupstools_nut_issues_577&d=DwIFaQ&c=f9s1...

My UPS is connected to a Raspberry Pi by USB. After a few hours of working, the service fails. Looking at kernel messages I noticed that the device is repeatedly disconnecting and reconnecting. I have tried using a different USB port and using a brand new USB cable. I have not had success by changing config parameters like pollfreq/pollinterval/etc. What is causing the UPS to keep disconnecting?