The Cypress USB-Serial Configuration Utility provides an easy-to-use graphical interface to configure manufacturing settings and options for Cypress USB-Serial devices. With this utility, you can connect to USB-Serial devices, modify the configuration settings. Cypress CY7C652xx USB-Serial Bridge Controllers are the first in the industry to offer configurable serial channels for UART/I2C/SPI interfaces, with industry's lowest power consumption in stand-by mode (5µA).
Hail to the Gurus! Because I live in an area with lost of sudden power failures, I have purchased a Powerwalker UPS to avoid frequent shut-downs and power instabilities. For this system, they bundle a software called Powerwalker Viewpower, also available in a Linux version, which I have installed. It is running from the box - but it does not find the UPS. So I have no way to monitor and configure it. I cannot access it. It is supposed to be accessed through a USB connection, seems it has an interface that transfers USB to serial.
When I check with 'lsusb', I get, amongothers, the response 'Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial' which is supposed to be the UPS. The software Viewpower opens my internet browser, the address is, and when I start the monitor, it opens another browser window for, the /192.xxx.1.yyy being my local PC which should be monitoring. The Connection seems to ask for the port 15178, so I have tried to open that in the firewall. Not sure if it worked. (The rules in the firewall config menu are red).
So now I am at a loss what to do next. I have contacted Powerwalker support, but so far they have also not been able to help. Does anybody have an idea How I can get this program to recognize my UPS?
Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest.
By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links: If you have any problems with the registration process or your account login, please. If you need to reset your password,. Having a problem logging in?
Please visit to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. To receive this Complete Guide absolutely free.
Code: $lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 005: ID 1058:1010 Western Digital Technologies, Inc. Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 002: ID 046d:c061 Logitech, Inc. RX1500 Laser Mouse. Code: $dmesg grep usb usb 7-1: new low speed USB device using uhcihcd and address 5 usb 7-1: New USB device found, idVendor=0665, idProduct=5161 usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 7-1: Product: USB to Serial usb 7-1: Manufacturer: Cypress Semiconductor generic-usb 0003:0665:5161.0005: hiddev96,hidraw1: USB HID v1.00 Device Cypress Semiconductor USB to Serial on usb-0000:00:1d.1-1/input0I'm trying configure NUT without success because I don't know the port and the driver too. I already tried the UPS software to linux. It is a.bin file and give me error on install.
I think it is because don't support Slackware or it is a 32 bits software. I need really some help on this. Code: $sh /etc/rc.d/rc.ups start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3) libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied.
Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/002/001: Permission denied.
Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/002/002: Permission denied. Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/003/001: Permission denied. Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/004/001: Permission denied. Libusb requires write access to USB device nodes.
Libusb couldn't open USB device /dev/bus/usb/005/001: Permission denied. Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/006/001: Permission denied. Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/007/001: Permission denied.
Libusb requires write access to USB device nodes. Supported UPS detected with mustek protocol Vendor information unavailable Battery runtime will not be calculated (runtimecal not set) Network UPS Tools upsd 2.4.3 stat /etc/nut/upsd.conf: No such file or directory. Code: # sh /etc/rc.d/rc.ups start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3) libusb couldn't open USB device /dev/bus/usb/001/001: Permission denied. Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/002/001: Permission denied.
Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/002/002: Permission denied. Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/003/001: Permission denied. Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/004/001: Permission denied.
Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/005/001: Permission denied.
Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/006/001: Permission denied. Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/007/001: Permission denied. Libusb requires write access to USB device nodes.
Libusb couldn't open USB device /dev/bus/usb/007/002: Permission denied. Libusb requires write access to USB device nodes.
Libusb couldn't open USB device /dev/bus/usb/008/001: Permission denied. Libusb requires write access to USB device nodes. Libusb couldn't open USB device /dev/bus/usb/008/002: Permission denied. Libusb requires write access to USB device nodes. No supported devices found. Please check your device availability with 'lsusb' and make sure you have an up-to-date version of NUT. If this does not help, try running the driver with at least 'subdriver', 'vendorid' and 'productid' options specified.
Please refer to the man page for details about these options (man 8 blazer). Driver failed to start (exit status=1)Now I don't know what do get this thing working. If you have NUT running as root, you shouldn't need any udev rules for the usb device. You just need to make sure that it exists. From your first post, it looks like the USB device is a USB-to-serial.
I recommend that you remove any custom udev rules, reboot, connect the UPS, and run 'ls -al /dev/ttyUSB.' . This will confirm that the UPS device shows up as a usb-to-serial device, and named ttyUSB0 or ttyUSB1. Once you have confirmed the device is /dev/ttyUSB0, try using this as your ups.conf.