search for: parisy

>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

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

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 Elio, once more, your email was blocked due to the 40 Kb limits... note that here, NUT Monitor screenshots were not needed. upsc output is sufficient. From: Elio Parisi <E.Parisi at riello-ups.com> > To: "nut-upsdev at lists.alioth.debian.org" < > nut-upsdev at lists.alioth.debian.org> > Cc: > Date: Fri, 23 Nov 2012 15:05:49 +0100 > Subject: Riello patch

Hi all, we should have been found the problem. Attach the patch inclusive of this problem and the previous (Riello IDG400 wrong values & not powering off). Best regards, -----Messaggio originale----- Da: Nut-upsdev [mailto:nut-upsdev-bounces+e.parisi=riello-ups.com at lists.alioth.debian.org] Per conto di nut-upsdev-request at lists.alioth.debian.org Inviato: mercoled? 7 marzo 2018 13:03 A:

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

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

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

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

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:

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:

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?

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

Dear developers we are glad to participate to the NUT development. Me and my colleague Elio Parisi e.parisi at riello-ups.com<mailto:e.parisi at riello-ups.com> we will work to support the Riello UPS protocols. For any question please don't hesitate to contact me. Best Regards Massimo Zampieri Technical Marketing - UPS Software Product Manager RPS SpA Viale Europa, 7 37045 Legnago

(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, I''m new to shorewall and to this list. I just switched from custom iptables-based scripts to shorewall, and everything seems to work smoothly. There''s only one thing I wasn''t able to port : rules similar to this one : iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 5190 -j REDIRECT --to-ports 5190 Can this be expressed using shorewall config files ? Or

Hello there. I've been having problems with printers, and I could not find anything on google, thats why I'm writing you. A piece of the logfile: [2004/01/13 17:03:51, 2] rpc_server/srv_spoolss_nt.c:find_printer_index_by_hnd(263) find_printer_index_by_hnd: Printer handle not found: _spoolss_fcpn: Invalid handle (OTHER:2730:3433) [2004/01/13 17:03:51, 2]

Hi all, I set up a Samba server (version 3.0.24) names "Lamp" on a Debian Etch distribution. It provides a "guest" (guest ok = yes, guest only = yes, security = SHARE) access to a "share" directory, which works fine. Indeed, I can access \\lamp\share from a Windows machine (named "Ginger") without issuing a password. I can also ping the Linux machine