similar to: Device not supported?

On 06/24/2017 04:52 AM, Charles Lepple wrote: > On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote: >> "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" >> but my device (SU2200RTXLCD2U) is supported, as clearly state here. > No, the HCL also mentions "protocol 4001". For Tripp-Lite,

>From section 4.23 of the Developer Guide: "There are a few USB UPS devices that are not HID devices. These devices typically implement some version of the manufacturer?s serial protocol over USB (which is a really dumb idea, by the way). An example is the Tripplite USB. Such devices are *not* supported by the usbhid-ups driver, and are not covered in this document." I guess that

Hello I asked Tripplite the serial protocol implemented in the UPS model SU2200RTXLCD2U. The protocol is the 4006, which is not supported by the NUT. I connected my UPS unit to a serial terminal client (both from a Windows machine and a Linux machine), set the communication parameters to those indicated in the protocol spec, and tried to open the communication, unfortunately with no success. I

Thank you for your answer. I will try to investigate the possibility that the Tripplite serial cable has a different pinout than a standard RS-232 serial cable. I wouldn't use the NUT at this point because I don't think I will be able to write a software update to adapt the NUT to my needs. My idea was first to test the protocol via a serial terminal client directly connected to the UPS,

I've eventually installed Manuel's packages (nut and nut-client). When I run the driver as root (for my tripplite ups) I get: /usr/sbin/upsdrvctl start Network UPS Tools - Generic HID driver 0.42 (v2.7.4-418-gb1314c62.7.4.1) USB communication driver (libusb 0.1) 0.33 writepid: fopen /var/run/nut/usbhid-ups-trippliteups.pid: Permission denied Can't claim USB device [09ae:1330]: could

On 07/06/2017 02:18 AM, Charles Lepple wrote: > On Jul 5, 2017, at 5:34 PM, Ambrogio Coletti <ambrojohn at gmail.com > <mailto:ambrojohn at gmail.com>> wrote: >> >> From section 4.23 of the Developer Guide: >> >> "There are a few USB UPS devices that are not HID devices. These >> devices typically implement some version of the manufacturer?s

On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote: > > "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" > but my device (SU2200RTXLCD2U) is supported, as clearly state here. No, the HCL also mentions "protocol 4001". For Tripp-Lite, a USB PID other than 0001 is generally the protocol

Hello I am not a linux expert. The output of uname -r on my system returns: 2.6.32-696.3.1.el6.x86_64 hence I am trying to install this rpm: sudo yum install nut-2.7.4-9.fc27.x86_64.rpm but I got failed dependencies. Is there a repository I am supposed to set up to get those dependencies from? Regards Ambrogio -------------- next part -------------- An HTML attachment was scrubbed... URL:

I don't have the Tripp-Lite model that you have, however the NUT HCL http://networkupstools.org/stable-hcl.html suggests that the SU2200RTXLCD2U ought to work via USB. Tripp-Lite sometimes uses proprietary serial cables, so you may need to hunt down a pinout for the serial cable this unit requires. If you need to use a serial connection, I'd start by looking at how their PowerAlert

On Jul 3, 2017, at 12:48 PM, Ambrogio Coletti wrote: > > I wouldn't use the NUT at this point because I don't think I will be able to write a software update to adapt the NUT to my needs. > > My idea was first to test the protocol via a serial terminal client directly connected to the UPS, and then write some simple code from scratch to implement the protocol and use it for

On Jul 5, 2017, at 5:34 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote: > > From section 4.23 of the Developer Guide: > > "There are a few USB UPS devices that are not HID devices. These devices typically implement some version of the manufacturer?s serial protocol over USB (which is a really dumb idea, by the way). An example is the Tripplite USB. Such devices are

Hi, I've been looking for this information, but I couldn't find it anywhere. I have a samba (2.2.3) on debian (woody) and I mean to configure this server with winbind so it can authenticate domain users. The PDC is at a NT server. My question is is very simple ... what are the *exact* privileges I need to give the user I use to join the domain? Winbind docs says use

Dear Sirs, no way to play mp3 on Centos 7. I tried all suggestions w/o success! Could you please tell me how to? Thank you in advance. Best regards, Ambrus

Hi; I'm having some trouble to comunicate with my just bought (08/17/15) Ups. According to SOLIS(8): SUPPORTED HARDWARE This driver has been tested with : Solis 1000 VA Solis 1500 VA Solis 2000 VA Solis 3000 VA Back-UPS BZ1200-BR Back-UPS BZ2200BI-BR So solis is the one to go for. Here is my scenario: SW: nut-2.7.3 (compiled from ports) OS: FreeBSD

On 06/23/2017 01:51 AM, Ambrogio Coletti wrote: > Hello > > I am not a linux expert. > > The output of uname -r on my system returns: > 2.6.32-696.3.1.el6.x86_64 > > hence I am trying to install this rpm: > sudo yum install nut-2.7.4-9.fc27.x86_64.rpm > > but I got failed dependencies. > You are trying to install packages built for Fedora 27 on a CentOS 6

On Thu, 22 Jun 2017, Ambrogio Coletti wrote: > Hello > > I am not a linux expert. > The output of uname -r on my system returns: > 2.6.32-696.3.1.el6.x86_64 Hi, Linux 2.6.32 was released 3 December, 2009. That's nearly 8 years ago. Linux has now reeched version 4.11. > hence I am trying to install this rpm: > sudo yum install nut-2.7.4-9.fc27.x86_64.rpm > >

(forwarding msg because of attachments too big) @Massimo: prefer to send references instead of actual documents, whenever you mail to the list. We have a 40Kb limit, to not overload our readers. Please also avoid Microsoft OpenXML (Ie, .xlsx, .docx, ...) and prefer PDF or anything else that is actually inter-operable . Thus I've converted the XLSX spreadsheet to PDF. To all: I've added

Hi, I'm trying to set up a squid with ntlm authentification, and as I follow the instructions I read in the squid FAQ I run into this problem. When I try to do a ``wbinfo -a <domain>\\<user>%<passwd>'' the process tells me that the authentification did not succeded (both, plaintext passwords authentification and challenge/response password authentification). This

I have created a lattice bwplot that suffers from axis label overplotting. The box plot contains grid lines, and I thought that only plotting the labels for corresponding vertical grid lines would not only cure the overplotting but also be more aesthetically pleasing. Unfortunately hours of poring over manuals, documentations, mailing list archives, and other R-related text hasn't helped.

On Jan 21, 2015, at 3:41 AM, Maurizio Iacaruso <maurizio.iacaruso at gmail.com> wrote: > The ?device? is this http://www.dlink.com/it/it/business-solutions/network-storage/network-video-recorders/dnr-322l-cloud-network-video-recorder , a NVR with USB port for monitoring UPS. It doesn?t support monitoring by LAN. > So, my aim is to ?replicate? the state of the UPS, in the sense that