similar to: riello_usb driver: randomly not working and usbfs flooding syslog

On 22 febbraio 2014 17:28:16 CET, Roberto Resoli <roberto at resolutions.it> wrote: >Hello, > >after some days running without problems, my riello idialog 800 ups >get disconnected, and usbfs started flooding syslog with messages like: > >usb 1-1.2: usbfs: process 57342 (riello_usb) did not claim interface 0 >before use > >Version is 2.7.1-1 debian packages, which

Il 22/02/2014 23:11, Roberto Resoli ha scritto: > On 22 febbraio 2014 17:28:16 CET, Roberto Resoli <roberto at resolutions.it> wrote: >> Hello, >> >> after some days running without problems, my riello idialog 800 ups >> get disconnected, and usbfs started flooding syslog with messages like: >> >> usb 1-1.2: usbfs: process 57342 (riello_usb) did not

Elio, please see below as well. On Feb 22, 2014, at 5:11 PM, Roberto Resoli wrote: > On 22 febbraio 2014 17:28:16 CET, Roberto Resoli <roberto at resolutions.it> wrote: >> Hello, >> >> after some days running without problems, my riello idialog 800 ups >> get disconnected, and usbfs started flooding syslog with messages like: >> >> usb 1-1.2: usbfs:

Hello, Some more data about my experiences with riello_ups on iDialog 800 In orderr to avoid "stale data" problems, i tried to increase pollinterval in ups.conf: ==== ups.conf ===== pollinterval = 4 maxretry = 3 [idg800] driver = riello_usb port = auto desc = "idg800" =================== It seems that pollinterval is ignored by the driver: # upsc idg800 | grep poll

Hello. I use nut 2.7.2 and have riello idialog 600 Ups.conf: [riello] driver = riello_usb port = auto desc = "riello" and get error root at server:/home/manu/Desktop# /lib/nut/usbhid-ups -a riello Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 Error: UPS [riello] is for driver riello_usb, but I'm usbhid-ups! When I chnge driver to usbhid-ups

Hello, I am triyng to shutdown my riello idg 800, (which is working quite well atm with nut 2.7.2 deb package under jessie), obtaining the result below; have I any chance to succeed? # /lib/nut/riello_usb -DDDD -a idg800 -k Network UPS Tools - Riello USB driver 0.02 (2.7.2) Warning: This is an experimental driver. Some features may not function correctly. 0.000000 debug level is '4'

Hello. Thanx for your answer. It work ! Riello Idialog present in list as IDL 600 But I have 2 bugs battery.charge: 255 ups.temperature: 255 battery.capacity: 7 battery.charge: 255 battery.runtime: 3932100 battery.voltage: 13.7 battery.voltage.nominal: 12 device.mfr: RPS S.p.a. device.model: UNV1 device.serial: device.type: ups driver.name: riello_usb driver.parameter.pollinterval: 2

Bonjour ? tous, Je n'arrive pas a faire marcher NUT avec HomeAssistant. Cela fait des mois que je suis la-dessus, mais sans succ?s ! Je ne vois plus quoi faire ! Help ! * Ubuntu 23.10 * NUT version = 2.7.4-14ubuntu2 * NUT installation method: Package * exact device name and related information : Riello IDG800 Voici les commandes que je tape sur le PC connect?

Hello everyone, I recently bought a Riello IPG 600 UPS ( http://www.riello-ups.com/products/1-ups/39-iplug) to prevent hardware damage to my server in case of power outages (already lost two hard drives because of this) and I managed to successfully configure it with NUT version 2.7.4 available for Ubuntu 17.04: nut/zesty-updates,zesty-updates,now 2.7.4-5ubuntu2.1 all [installed]

Hi all, attached there is a patch for a new version of riello drivers: Changes: - small changes in riello_usb.c that solved some problem with managing transmission errors between the raspberry pi and Riello ups (thanks to Fredrik ?berg): introducing timeout in reading ups data in cypress_command; enhanced handling error codes; - small changes in Riello_ser.c: enhanced handling error

On Feb 26, 2018, at 4:58 AM, Elio Parisi <e.parisi at riello-ups.com> wrote: > > Hi Charles, > this type of UPS doesn't support realtime autonomy calculation, instead a fixed countdown must be used. > > How we can fix non supported values? If a value is not supported, the driver should not publish it with the dstate API. Dhould the driver be modified to not return

On Oct 17, 2014, at 6:24 AM, Elio Parisi <e.parisi at riello-ups.com> wrote: > Hi all, > attached there is a patch for a new version of riello drivers: Merged, thanks. Also, have you seen this issue? https://github.com/networkupstools/nut/issues/124 from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738122 -- Charles Lepple clepple at gmail

Hi Charles, I see the issue but I don't be able to reproduce it on the Debian SID. The steps I followed are: - start from debian wheezy; - upgrade to debian testing; - upgrade to debian sid; - in debian sid test nut with riello_usb driver; In this situation there are no trace of error (claim interface) in /var/log/syslog at the moment of attach of cypress usb or at the moment of

Hello, I'm setting up nut on a Riello IDG800 ups, using riello_usb driver. I backported nut 2.7.1-1 debian packages from sid to wheezy, and installed nut-client, nut-server and nut-cgi. All seems to work quite nicely, but I want to submit the output of upsc, because some values are not correct (battery.charge, battery.runtime, ups.temperature, for instance): battery.capacity: 7

>I'm afraid I am just the messenger - @bigon (Laurent Bigonville, on GitHub) is a Debian maintainer of NUT, and he was pointing out the >bug report filed with Debian: >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738122 >With other drivers, we sometimes see the "did not claim interface 0 before use" error if a driver gets out of sync with its PID file, >and

On Mar 23, 2016, at 10:43 AM, Ivan Kurnosov wrote: > > Hello. I use nut 2.7.2 and have riello idialog 600 > Ups.conf: > [riello] > driver = riello_usb > port = auto > desc = "riello" > > and get error > root at server:/home/manu/Desktop# /lib/nut/usbhid-ups -a riello > Network UPS Tools - Generic HID driver 0.38 (2.7.2) > USB communication

Hi Arnaud, hi developers, attach there is the patch for riello drivers. Can you tell me if there is other to change in order to accomplish your rules and if the steps I have followed to create the patch are all rights? Cheers, Elio Parisi. Elio Parisi Centro Ricerche RPS SpA Viale Europa, 7 37045 Legnago VR Tel. +39 0442 635811 Fax. +39 0442 635934 Skype Id: - Voip: E-mail: E.Parisi

Hi, I'm using Nut 2.7.2 with riello_ser and riello_usb 0.3 (upgraded from 0.2). Raspbian on Raspberry PI model 2015. The drivers work on SENTR models. But on several GPSER the behaviour is erratic: - usually, the serial driver cannot connect with the UPS. But, when left on for several days, I found that it suddenly connected on one machine... - the usb driver connects immediately, but

On Jul 5, 2013, at 8:45 AM, Elio Parisi wrote: > But the diff file that I'll now produce is related to the 3857 revision, so is also > inclusive of previous changes (i.e. BYTE to uint8_t). Is it Ok for you? I can probably make that work, but in the long term, I would recommend either switching to Git, or if you prefer to stay with SVN, creating a new checkout from the GitHub SVN URL:

On Jul 5, 2013, at 5:44 AM, Elio Parisi wrote: > I tried to update sources (to eliminate the cast) with 'sudo svn update' but the response is: > > svn: No repository found in 'svn://svn.debian.org/nut/trunk' > > Can you verify svn server status? > > The code has been tested before and after the changes. The SVN server has been decommissioned as part of the