similar to: New version of riello driver

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

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

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

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:

Hi Arnaud, attached there are a new patch (fixed ups.upspower.nominal in GPSER protocol and device.mfr) and three devdumps. Let me know if this time all is correct, 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 at riello-ups.com Web: www.riello-ups.com

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? In alternatively could you modify the row (166 of riello_ser.c) of the file deleting the only cast that exist? Elio Parisi Centro Ricerche RPS SpA Viale Europa, 7 37045 Legnago VR Tel. +39 0442 635811 Fax. +39 0442 635934 Skype Id:

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

Elio, 1) The comment block in drivers/riello.h points to the Megatec protocol documentation. Are the links in drivers/riello.c correct? If so, we can change the .h file to match the .c file. 2) clang caught this bug: drivers/riello.c:984:28: warning: argument to 'sizeof' in 'memset' call is the same expression as the destination; did you mean to provide an explicit length?

(forwarding msg because of attachments too big) @Massimo: prefer to send references instead of actual documents, whenever you mail to the list. We have a 40Kb limit, to not overload our readers. Please also avoid Microsoft OpenXML (Ie, .xlsx, .docx, ...) and prefer PDF or anything else that is actually inter-operable . Thus I've converted the XLSX spreadsheet to PDF. To all: I've added

Hi Charles, I fixed (and tested) the source file according to your tips. The patch are attached. Let me know if there still something that do not reflect your guidelines. 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 at riello-ups.com Web: www.riello-ups.com

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 I backported from sid to wheezy. Any hint? rob

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

On Jul 31, 2013, at 3:36 AM, Pavel Potcheptsov (EKTOS) wrote: > Does it looks good? I think so - 40.8 volts with a nominal of 36 volts is 13.6 V/cell, which agrees with the 100% charge value. Hopefully the line voltages and frequency make sense for your region. > Another question what does riello experimental driver warning mean? We add that to all new drivers. This driver was written by

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

Hi Charles, attached there is a patch for a new version of riello drivers: Changes: - small changes in riello_usb.c and riello_ser that solved problem with UPS that not support realtime autonomy calculation (and also internal temperature); - the second problem I think is related to the first because the shutdown command that I sent to UPS by NUT monitor works without problems; Cheers, Elio

Thank you very much!! I have tried configure downloaded source with # ./configure --with-user=_ups --with-group=_ups --with-statepath=/var/db/nut/ and then build driver and copy again. but this doesn't help (driver pid still in the /var/state/ups). Maybe I must add more arguments to change driver's pid location, but I did next, I changed this argument in openbsd ports: # pkg_delete nut #

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