similar to: Data stale error after short while

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,

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

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

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

(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

Hi Having followed this guide: http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/and seeing support for Apollo UPSes mentioned on the compatibility list (genericups, type=4) I tried to set up Nut as follows. OS: Ubuntu Server 12.04 Nut: 2.6.3 (I believe - from Ubuntu repos) ups.conf: > [apollo] > driver = genericups > upstype = 4 > port = /dev/ttyUSB0

On Jan 2, 2015, at 4:27 PM, Mike Raath <raathm at gmail.com> wrote: > Maybe usbpassthrough is something I should look at? I'll do some reading. You may have found this already, but this (plus the followup KB item #1021345) seems to imply that you can bind the USB-to-serial adapter to the NUT VM:

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:

Hi Manuel, 2017-06-14 15:16 GMT+02:00 Manuel Wolfshant <wolfy at nobugconsulting.ro>: > Hello > > > > On 06/14/2017 03:32 PM, Arnaud Quette wrote: > > > > On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> > wrote: > >> > >>> > If that matters, the OS is a fully updated CentOS 6.9 and this >>>

Dear Charles and team Just thought to share my findings getting a Sweex PP200 650VA UPS working with NUT (I didn't see this particular model listed on the HCL.) I picked-up one of these units quite cheaply at a Maplins store (before the chain closed-down) as a second UPS for my home/office - the first being an old Zigor Ebro650 - a long story for another post... NUT v2.7.4_7 is running

On Nov 12, 2014, at 2:49 AM, Klint Gore <kgore4 at une.edu.au> wrote: > Can someone give me a push in the right direction with this? I?m trying to get an upsonic IRT1000 to work on ubuntu 14.04lts using the usb connection. The most likely drivers (blazer_usb and usbhid-ups) don?t seem to recognize it or I?ve got the configuration parameters wrong. I?ve got no idea what driver it

In my opinion, there might be just one problem: the blzr driver doesn't provide anymore two splitted drivers (serial and usb), so this isn't going to be a 'silent update' for those using these drivers (should we provide symlinks or the like?). If this doesn't sound like a problem to you, I'll take care of the rename. Plus, if you could take a look to the blazer-fix pull

On Jan 30, 2015, at 4:22 PM, Melvin Call <melvincall979 at gmail.com> wrote: > At this point I unplugged the UPS and plugged it into a different USP port, but > that did not change the above. Figuring this was likely a udev problem, I > created the following /etc/udev/rules.d/52-nut-usbups.rules (based on an example > on our database server, and changing the vendor and product

On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > running autogen.sh was triggered automatically. but even if I do it explicitly, I still get: > + autoreconf -i > configure.ac:887: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body

Hi Thank you very much for the feedback. I will download and try to get it working on the Raspberry Pi. Regards Tom On Sun, Feb 14, 2016 at 1:49 AM, hyouko at gmail.com <hyouko at gmail.com> wrote: > > I have the RCT 3KVA Axpert solar hybrid inverter. It is also known as > the > > MPP Solar PIP-MS series, the IPS-4000WM and the Voltronic Axpert MKS. I > am > >

Can someone give me a push in the right direction with this? I'm trying to get an upsonic IRT1000 to work on ubuntu 14.04lts using the usb connection. The most likely drivers (blazer_usb and usbhid-ups) don't seem to recognize it or I've got the configuration parameters wrong. I've got no idea what driver it actually wants though there's an old thread that seems to have got

Centos 6.7 Linux man8.m1.manifest.co.uk 2.6.32-573.12.1.el6.i686 #1 SMP Tue Dec 15 18:25:17 UTC 2015 i686 i686 i386 GNU/Linux Installed: nut.i686 2.6.5-2.el6 @epel nut-cgi.i686 2.6.5-2.el6 @epel nut-client.i686 2.6.5-2.el6 @epel I'm struggling to control an

Hello, Control HP R1500 G2 with nut via USB. Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-72-generic x86_64) nut V2.7.1 installed from repository /etc/nut/ups.conf [HPR1500] driver=usbhid-ups port=auto After dealing hours with this, hope this will help some : rename udev rule to higher priority and move it to its right location, reload udev rules mv /lib/udev/rules.d/52-nut-usbups.rules