search for: jfmxl

Changed the driver as you suggest ... # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2) USB communication driver 0.32 Using protocol: Q1 0.02 Can't autodetect number of battery packs [-1/13.50] Battery runtime will not be calculated (runtimecal not set) ... looks like it's connected to something, although maybe

Hello, Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 No matching HID UPS found Driver failed to start (exit status=1) I followed a thread with the same title, more or less, having permission problems. I applied that solution. My problem seems different. # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 010: ID 0665:5161

[please use reply-all to include the list - the headers are not mangled] > On Oct 18, 2016, at 9:02 PM, jfmxl at sdf.org wrote: > > So, apparently, my Eaton is sending > > Bus 002 Device 010: ID 0665:5161 Cypress Semiconductor USB to Serial Do you get a device named "/dev/ttyUSB0" when you plug in the UPS? We do have an entry for 0665:5161 in the nutdrv_qx driver (and blazer_usb,...

...but no /dev/ttyUSB0 How can I get one? Just make one? All the rest are 4,0-67 plus one 5,0 What ought the major number be? On 2016-10-20 07:33, Charles Lepple wrote: > [please use reply-all to include the list - the headers are not > mangled] > >> On Oct 18, 2016, at 9:02 PM, jfmxl at sdf.org wrote: >> >> So, apparently, my Eaton is sending >> >> Bus 002 Device 010: ID 0665:5161 Cypress Semiconductor USB to Serial > > Do you get a device named "/dev/ttyUSB0" when you plug in the UPS? > > We do have an entry for 0665:5161 in th...

> On Oct 20, 2016, at 8:25 AM, jfmxl at sdf.org wrote: > > Using protocol: Q1 0.02 > Can't autodetect number of battery packs [-1/13.50] > Battery runtime will not be calculated (runtimecal not set) > > ... looks like it's connected to something, although maybe the driver is not quite right? That looks rea...