search for: ch341

...supposed to use. I tried megatec, without success. (/lib/nut/megatec -DDDD -a UPS1 returns with "Q1 => FAILED [timeout]" 5 times ) A potential gotcha is that I am using a USB to serial device to talk to the UPS. It looks like it has installed correctly (dmesg tells me: "usb 2-1: ch341-uart converter now attached to ttyUSB0"). The USB-Serial adapter is connected to the serial cable that came with the UPS. Some pictures of the UPS and parts of its manual can be found here<http://picasaweb.google.com/diederikjhattingh/Public?feat=email#>(The circuit board is just the s...

Something just occurred to me. My kernel does not include USB->Serial code. Long ago, I had to figure out how to build a module for the ch341 USB->Serial adapter I use for running my Heyu home automation system. I never built one for Cypress and that seems to be what the Belkin is using. I know this because I see a line for it using "lsusb" that disappears if I unplug the UPS. Using "dmesg|less" and searching...

...his is suggested by > http://networkupstools.org/stable-hcl.html?manufacturer=Powercom&connection=USB > ) OK, thanks! I read up about the stuff in the last paragraph, and it's not clear to me what I need to do to test this out. % ls /lib/modules/`uname r`/kernel/drivers/usb/serial/ ch341.ko cp210x.ko ftdi_sio.ko % lsusb Bus 004 Device 003: ID 0d9f:0002 Powercom Co., Ltd Black Knight PRO / WOW Uninterruptible Power Supply (Cypress HID->COM RS232) Bus 004 Device 001: ... root hub ... % The debian docs say: Look at the output of lsusb, and if it identifies the serial device, tr...

Hello all and thanks. I read here <https://mn3m.info/posts/configure-ups-monitor-using-nut-on-debian/> while searching around for my issue's resolution. In this I see that this nut driver is creating and using an entry in /dev (in this case ttyS0). So I "ll tty*" and see nothing with nut. Since this is a USB UPS, I suppose I should be looking for something in /dev/ttyUSB*.

In a separate discussion, on 6/26/17 4:04 AM, Arnaud Quette wrote: > Hi > > If you're sure it's a HID device, add an entry in drivers/powercom-hid.c > { USB_DEVICE(POWERCOM_VENDORID, 0x0002), NULL }, > > Then autogen.sh + configure... > Please also report back so that I can update the code > > Cheers > Arno Thanks! I don't *know* whether or not