similar to: Small fixes needed for Riello driver

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:

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?

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

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

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

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 #

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

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

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

# reboot Connection to 192.168.5.81 closed by remote host. Connection to 192.168.5.81 closed. ppo at admin:/tmp$ ssh root at 192.168.5.81 root at 192.168.5.81's password: Last login: Tue Jul 30 14:10:49 2013 from pc-ppo.kh.ektos OpenBSD 5.3 (GENERIC.MP) #58: Tue Mar 12 18:43:53 MDT 2013 # ps -aux | grep ups root 2254 0.0 0.0 324 700 p0 S+ 5:29PM 0:00.00 grep ups # ps -aux

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 30, 2013, at 10:39 AM, Pavel Potcheptsov (EKTOS) wrote: > Is this a trouble? Driver use path /var/state/ups/ but upsd use path /var/db/nut/upsd.pid Yes, the driver and upsd need to agree on the path to the socket. From the FreeBSD ports tree: /usr/ports/sysutils/nut/Makefile: STATEDIR?= /var/db/nut [...] CONFIGURE_ARGS= --sysconfdir=${PREFIX}/etc/nut \

On Jul 30, 2013, at 3:28 AM, Pavel Potcheptsov (EKTOS) wrote: > another attempt: > # upsd > Network UPS Tools upsd 2.6.5 > fopen /var/db/nut/upsd.pid: No such file or directory > listening on 127.0.0.1 port 3493 > listening on ::1 port 3493 > Can't connect to UPS [senpro] (riello_ser-senpro): No such file or directory We need to determine whether upsd and the driver are

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