similar to: Setting up Apollo Line Interactive UPS on Ubuntu

Ok - before stale data: After stale data: $ lsusb -d 0665: Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial After stale data: And the gzipped log attached: On 2 January 2015 at 21:56, Charles Lepple <clepple at gmail.com> wrote: > On Jan 2, 2015, at 2:43 PM, Mike Raath <raathm at gmail.com> wrote: > > Not sure what other logs I can provide to try

Sorry, I messed up my reply a bit. The output of the lsusb command is the same before and after the data goes stale. $ lsusb -d 0665: Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial And the output of the /lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 command is the same as in the previous attachment. I truncated the "before" log because it just carried on with

On Jan 2, 2015, at 3:33 PM, Mike Raath <raathm at gmail.com> wrote: > Sorry, I messed up my reply a bit. > > The output of the lsusb command is the same before and after the data goes stale. > > $ lsusb -d 0665: > Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial > OK. That usually means that the VM kernel doesn't see that the device is

Hi Charles, and thanks for your suggestion. I tried the nutdrv_qx and moved the rules file like you said, and re-attached the USB. It picked up to begin with, but within 10 minutes it lost the device again. $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.1 Network UPS Tools - Generic Q* USB/Serial driver 0.01 (2.7.1) USB communication driver 0.32 Using protocol: Megatec

On Jan 2, 2015, at 2:43 PM, Mike Raath <raathm at gmail.com> wrote: > Not sure what other logs I can provide to try to troubleshoot this? > Two things: - the output of 'lsusb -d 0665:' before and after the 'stale data' warning - the output of '/lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 | tee /tmp/nutdrv_qx.log' (Please gzip nutdrv_qx.log before

As per request by Arnaud in the users list Device manufacturer: Apollo Device name: 1085VC (Retailer's product page: http://shop.esquire.co.za/ProductDescription.aspx?id=583072) upsc on mains power: > $ upsc apollo > battery.voltage: 13.50 > battery.voltage.nominal: 12.0 > beeper.status: enabled > device.mfr: > device.model: > device.type: ups > driver.name:

A couple of years ago, Arnaud helped me get my Apollo Line Interactive UPS working, using the blazer_usb driver. Now I've run into another problem, having rebuilt my HP Proliant Microserver into an ESXi 5.5 managed hypervisor with various VMs. One of the VMs is a FreeNAS server which manages the storage for the other VMs so graceful shutdowns are important. I built a single VM to monitor the

On Feb 18, 2014, at 10:15 PM, Charles Lepple wrote: > On Feb 18, 2014, at 5:55 PM, Thiago Tiedtke dos Reis wrote: > >> Hi, >> >> Recently I got three units of this nobreak [0]: > ... >> [0] http://www.sms.com.br/produtos/Nobreak-SMS/Manager-III-Senoidal > > According to the HCL, for the Manager III, you might want to try the blazer_ser (or in 2.7.1,

On Jan 2, 2015, at 1:07 PM, Mike Raath <raathm at gmail.com> wrote: > I built a single VM to monitor the UPS (Ubuntu Server 14.04 i386) and installed NUT on the box from the apt packages. I set it up as per the previous box with the blazer_usb driver and all goes well, for a while. Initially, the UPS reports correctly via upsc, but after a while I get the "Data stale" error,

(sorry about the top-posting) I did a killall on blazer_usb and nutdrv_qx, then did a lsusb, got the following: $ lsusb -d 0665: Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial Then I started the driver in DDD mode, log attached, beyond the point where communication fails (591.465153). Lastly, I did the lsusb again and got this: $ lsusb -d 0665: Bus 002 Device 005: ID

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

Hi Charles, I'll try the blazer_ser and the nutdrv_qx with version 2.7.1 later. Below, the result of 'lsusb -vvv' requested: Bus 004 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level)

Dear friends, I installed NUT and followed all suggested procedures to verify if my ups is supported. No driver recognized my ups, and the genericups tests get wrong. Here I send some informations about it: The ups model is APC BZ1200-BR I use Ubuntu, and the lsusb results Bus 003 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC for ups. The

2009/4/28 mvochin <mvochin at elcom.pub.ro> > Hi Arnaud, > Hi > > Regarding ups compatibility list, Apollo 1000A, and 1000F Line > Interactive Series is also supported as genericups upstype=4 (I guess the > whole apollo family is supported with this driver) > http://www.apollotw.com/products-li.html I have some hard time trying to access it. anyway, I've

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*.

I just bought an Ultra UPS system for my linux server, and I need help getting it set up. It's an Ultra 700VA UPS. NUT INFORMATION: Package (apt-get install nut) NUT VERSION: Latest Driver: I don't have one? Here's the device information from my syslog: Code: Jul 7 23:25:27 eric-desktop kernel: [ 3045.609066] usb 2-1: USB disconnect, address 3 Jul 7 23:25:30 eric-desktop

Hello, I am trying to understand how to create a custom configuration for the genericups driver. My system simply signals RI on a serial port on low battery. That's it, nothing else. This serial port is also being used for communications so the other lines are going to be changing all the time, unrelated to the UPS state. Is there a "null" upstype I can use, and then add LB=RNG?

Hi Users NUT, I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. In compatibility list, is listed to use the blazer_ser driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. root at rasp:/home/pi# lsusb *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* Bus 001 Device 003: ID 0424:ec00 Standard

I am using nut 2.2.2 and I have a CyberPower CP550SL. According to the drivers list, I should be using genericups with upstype set to 7, but when I try that and when I run upsc I get: driver.name: genericups driver.parameter.LB: 04 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups driver.parameter.upstype: 7 driver.version: 2.2.2 driver.version.internal: 1.34 ups.mfr: CyberPower

I am using nut 2.2.2 and I have a CyberPower CP550SL. According to the drivers list, I should be using genericups with upstype set to 7, but when I try that and when I run upsc I get: driver.name: genericups driver.parameter.LB: 04 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups driver.parameter.upstype: 7 driver.version: 2.2.2 driver.version.internal: 1.34 ups.mfr: CyberPower