similar to: Cannot connect to a GPSER on serial, USB returning wrong data

On Apr 15, 2015, at 3:56 PM, Dan Craciun <dany.craciun at gmail.com> wrote: > 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

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

# 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

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

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

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 # ls -la /var/db/nut/ total 12 drwx------ 2 _ups wheel 512 Jul 30 10:22 . drwxr-xr-x 10 root wheel 512 Jul 29 16:41 .. -rw-r--r-- 1 _ups

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

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:

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

Here is what I did: # cd /root/nut/ # nut here it's checkouted repository # ./configure --with-user=_ups --with-group=_ups # cd drivers/ # make riello_ser # chgrp bin riello_ser # cp riello_ser /usr/local/bin # here I copied builder driver to folder where nut-package will store their files/drivers # pkg_add nut-2.6.5p1 # ls -la /dev/tty00 crw-rw---- 1 _ups _ups 8, 0 Jul 30

Thanks for you reply. I have installed asciidoc with "pkg_add asciidoc" And it returns something: # asciidoc fgh asciidoc: FAILED: input file /root/nut/fgh missing # which asciidoc /usr/local/bin/asciidoc Maybe there is any way to skip building man pages. This is not the such main thing as a new devices support. I also could built the driver that I need # make riello_ser but I don't

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 #

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

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

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