Thanks for the response. No /dev/ttyUSB0. /dev/tty and /dev/tty1 ... /dev/tty63 /dev/ttyS0 ... /dev/ttyS3 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 the nutdrv_qx driver (and > blazer_usb, which is deprecated in favor of nutdrv_qx) but given that > it is the ID for a USB-to-serial converter, it might not be the same > protocol. Give it a shot, and let us know how it goes.
> but no /dev/ttyUSB0 > > How can I get one? Just make one? All the rest are 4,0-67 plus one 5,0They are created automatically by udev, so I'm guessing it won't work. What happens if you change "driver = usbhid-ups" to "driver = nutdrv_qx" in ups.conf?
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 the driver is not quite right? On 2016-10-20 18:39, Charles Lepple wrote:>> but no /dev/ttyUSB0 >> >> How can I get one? Just make one? All the rest are 4,0-67 plus one 5,0 > > They are created automatically by udev, so I'm guessing it won't work. > > What happens if you change "driver = usbhid-ups" to "driver > nutdrv_qx" in ups.conf?