luca2 Posted March 15, 2016 Share Posted March 15, 2016 Hi, can anyone help me out with the setupneeded for my UPS? I get the error "Lost communication". When I start the plugin I get the following. Is it a way to check if my Tower does connect to the UPS? Let me know if you need more info pls. I checked the "http://apcupsd.org/manual/manual.html#linux-usb-configuration" web, but I don´t get it how to make it work. In my USB Devices i get: Bus 006 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Rgds. EDIT: From acpupsd.org: #Verifying Device Detection and Driver To make sure that your USB subsystem can see the UPS, just do this from a shell prompt: cat /proc/bus/usb/devices# How can I do that in Unraid? Link to comment
RobJ Posted March 15, 2016 Share Posted March 15, 2016 That looks like a serial port adapter (COM RS232 Adapter). Does your UPS connect by serial port or USB port? What model is your UPS? USB to serial port adapters are notorious for being problematic, in many usage applications, it doesn't surprise me if you are having trouble with it, much better to do without. At the moment, it looks like the USB initialization is seeing the serial port adapter, but not past it. At a command prompt, you can try the lsusb command. Link to comment
luca2 Posted March 16, 2016 Author Share Posted March 16, 2016 I connected this ups using the provided USB cable to my other pc. It woks perfect in windows OS. I will post later the output of lsusb. My output: root@Tower:~# lsusb Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub root@Tower:~# Link to comment
RobJ Posted March 16, 2016 Share Posted March 16, 2016 Try lsusb -v. All it's showing so far is the flash boot drive and the serial port adapter. What model is the UPS? Can you attach your syslog, it usually identifies connected UPS units. Link to comment
luca2 Posted March 16, 2016 Author Share Posted March 16, 2016 root@Tower:~# lsusb -v Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 4.01 iManufacturer 3 Linux 4.1.13-unRAID ehci_hcd iProduct 2 EHCI Host Controller iSerial 1 0000:00:16.2 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 4 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable 0x00 PortPwrCtrlMask 0xff Hub Port Status: Port 1: 0000.0100 power Port 2: 0000.0100 power Port 3: 0000.0100 power Port 4: 0000.0100 power Device Status: 0x0001 Self Powered Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice 4.01 iManufacturer 3 Linux 4.1.13-unRAID ohci_hcd iProduct 2 OHCI PCI host controller iSerial 1 0000:00:16.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 4 wHubCharacteristic 0x0012 No power switching (usb 1.0) No overcurrent protection bPwrOn2PwrGood 2 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable 0x00 PortPwrCtrlMask 0xff Hub Port Status: Port 1: 0000.0100 power Port 2: 0000.0100 power Port 3: 0000.0100 power Port 4: 0000.0100 power Device Status: 0x0001 Self Powered Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice 4.01 iManufacturer 3 Linux 4.1.13-unRAID xhci-hcd iProduct 2 xHCI Host Controller iSerial 1 0000:07:00.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 31 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 bMaxBurst 0 Hub Descriptor: bLength 12 bDescriptorType 42 nNbrPorts 2 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere bHubDecLat 0.0 micro seconds wHubDelay 0 nano seconds DeviceRemovable 0x00 Hub Port Status: Port 1: 0000.02a0 5Gbps power Rx.Detect Port 2: 0000.02a0 5Gbps power Rx.Detect Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 15 bNumDeviceCaps 1 SuperSpeed USB Device Capability: bLength 10 bDescriptorType 16 bDevCapabilityType 3 bmAttributes 0x00 wSpeedsSupported 0x0008 Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 3 Lowest fully-functional device speed is SuperSpeed (5Gbps) bU1DevExitLat 0 micro seconds bU2DevExitLat 0 micro seconds Device Status: 0x0001 Self Powered Bus 001 Device 002: ID 0781:5571 SanDisk Corp. Cruzer Fit Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0781 SanDisk Corp. idProduct 0x5571 Cruzer Fit bcdDevice 1.26 iManufacturer 1 SanDisk iProduct 2 Cruzer Fit iSerial 3 4C532000050906121385 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 200mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 EDIT:ups is riello netpower npw600s syslog_2015_003_16_usb.txt Link to comment
RobJ Posted March 17, 2016 Share Posted March 17, 2016 I see on the Riello web site that many of their products are serial port related, and I know that many older UPS units began with serial port interfaces, so I have to assume that Riello took an existing design with serial connection and added a USB adapter internally, with the Cypress USB drivers. The kernel does see a low speed USB device on bus 6, but there's no indication it knows what it is. The apcusbd daemon starts up fine, but quickly complains of lack of UPS communications. The obvious reason must be that this UPS (like most) is not APC compatible, which means you'll have to try with the NUT plugin. I looked up the UPS on the NUT (Network UPS Tools) Hardware compatibility list, and your UPS is listed there, going to need the riello_usb driver. I suppose you know but you have a misbehaving drive, sdj (the Sandisk SSD), with both interface issues and XFS file system issues, auto-mounted (I think) by Unassigned Devices. Link to comment
luca2 Posted March 17, 2016 Author Share Posted March 17, 2016 Thx for pointing me to Nut. I will come to it as soon as I check for the drives. I will check for any cable issue. EDIT: Pls, how should I proceed with "XFS file system issues"? I cannot find them in the syslog. Anyway I don´t know how to solve them. Help is appreciated. Rgds. Link to comment
luca2 Posted March 17, 2016 Author Share Posted March 17, 2016 Hi, I managed to install NUT and it seems to connect to my UPS: NUT Status UPS Statistics battery.capacity: 7 battery.charge: 255 battery.runtime: 3932100 battery.voltage: 13.6 battery.voltage.nominal: 12 device.mfr: RPS S.p.a. device.model: USC6 device.serial: device.type: ups driver.name: riello_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.3 driver.version.internal: 0.03 input.bypass.frequency: 409.50 input.bypass.voltage: 4095 input.frequency: 50.00 input.voltage: 224 output.frequency: 50.00 output.frequency.nominal: 50.0 output.L1.current: 0 output.L1.power: 0 output.L1.realpower: 0 output.L2.current: 0 output.L2.power: 0 output.L2.realpower: 0 output.L3.current: 0 output.L3.power: 0 output.L3.realpower: 0 output.power.percent: 55 output.voltage: 224 output.voltage.nominal: 230 ups.firmware: SWM048-01-00 ups.load: 55 ups.mfr: RPS S.p.a. ups.model: USC6 ups.power.nominal: 600 ups.productid: 5500 ups.realpower.nominal: 360 ups.serial: ups.status: OL ups.temperature: 255 ups.vendorid: 04b4 Could anyone let me know how to test a simulated power shortage? Rgds. EDIT:Also, anyone installed https://sites.google.com/a/prynych.cz/knutclient/home/registry together with NUT? Is it possible/easy to do? Link to comment
BRiT Posted March 18, 2016 Share Posted March 18, 2016 Pull the ups plug from the electrical wall outlet, no? Link to comment
Alex.vision Posted March 18, 2016 Share Posted March 18, 2016 A note about just pulling the plug out of the wall. I think I remember something saying it can cause some ups systems to shut off if they don't detect a ground state. So that may or may not work. I would try it first with nothing plugged in so you know it won't just shut off if you pull the main plug. Link to comment
BRiT Posted March 18, 2016 Share Posted March 18, 2016 A note about just pulling the plug out of the wall. I think I remember something saying it can cause some ups systems to shut off if they don't detect a ground state. So that may or may not work. I would try it first with nothing plugged in so you know it won't just shut off if you pull the main plug. Some UPS wont even turn on without any load on the unit, so you might need to plug in at least a light and turn it on to test the ups. Link to comment
JonathanM Posted March 18, 2016 Share Posted March 18, 2016 Could anyone let me know how to test a simulated power shortage? Best way is to plug the UPS into a switchable outlet, like a power strip, and plug lamps approximately equal to the max server load (like during a parity check) into the UPS output. Keep the server plugged into an always on surge strip, and plug the UPS communication cable into the server. Turn off the power to the UPS, and make sure that the server shuts down properly before the lamps plugged into the UPS go out. Link to comment
luca2 Posted March 19, 2016 Author Share Posted March 19, 2016 Hi, there are 3 options to try that: Which did you choose and what values did you use? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.