similar to: MGE ESV+ and Power Trim

On Mar 3, 2017, at 8:21 AM, Charles Lepple <clepple at gmail.com> wrote: > > On Mar 2, 2017, at 3:38 PM, David Baker <david at baker.im> wrote: >> >> I?ve read the documentation, and it would appear that this can be set by the U-Talk protocol (page 34 of http://networkupstools.org/protocols/mge/9261zwfa.pdf) but I can?t seem to figure out how to send the device the

Hi Arnaud & Charles, You?ll have to forgive my low level of Linux Understanding here?. I downloaded the source files, modified the appropriate driver file, re-compiled it (all of this was a lot of research and learning!) When I use the new driver I get ? Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.93 (2.7.4.1) Can't chdir to

Hi David and Charles Le 3 mars 2017 2:35 PM, "Charles Lepple" <clepple at gmail.com> a ?crit : > On Mar 3, 2017, at 8:21 AM, Charles Lepple <clepple at gmail.com> wrote: > > > > On Mar 2, 2017, at 3:38 PM, David Baker <david at baker.im> wrote: > >> > >> I?ve read the documentation, and it would appear that this can be set > by the

On Mar 2, 2017, at 3:38 PM, David Baker <david at baker.im> wrote: > > I?ve read the documentation, and it would appear that this can be set by the U-Talk protocol (page 34 of http://networkupstools.org/protocols/mge/9261zwfa.pdf) but I can?t seem to figure out how to send the device the command, or manage to terminal into the unit (once disabling NUT services) and send the command.

On Sat, Mar 11, 2017 at 7:15 PM, David Baker <david at baker.im> wrote: > Hi Arnaud & Charles, > > > > You?ll have to forgive my low level of Linux Understanding here?. > > > > I downloaded the source files, modified the appropriate driver file, > re-compiled it (all of this was a lot of research and learning!) > > > > When I use the new driver I

2017-03-12 4:02 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Sat, Mar 11, 2017 at 7:15 PM, David Baker <david at baker.im> wrote: > > Hi Arnaud & Charles, > > > Hi Dave, any news on your side from this venerable ESV+? -- Arno > You?ll have to forgive my low level of Linux Understanding here?. > > > > > > > > I downloaded

Hi all! I'm wondering if there's anyone doing any hacking on the snmp-ups driver at the moment. I've started looking at implementing 3phase-support, and this uncovered some rather unpleasant stuff in the snmp-ups driver that I really need to fix in order to get things sane. Those of you that's allergic to SNMP might want to stop reading now, this is rather icky ;)

Hi David, 2017-03-21 20:06 GMT+01:00 David Baker <david at baker.im>: > Hi, > > > Thanks for checking in ? I managed to re-compile it but was getting the > same error ? I then had other things to do so didn?t get further in my > investigation. > same error being "Can't chdir to /var/state/ups: No such file or directory"? if so, ensure that you use

W dniu 24.08.2018 o 13:10, Charles Lepple pisze: > Sorry, I didn't mean to imply that the master branch was necessarily going to be different, just wanted to make sure you had everything set up to recompile. The real test is to see if things change after commenting out that line (such as by changing it to start with "//"): > > // { "shutdown.return", 0, 0,

Hi, Thanks for checking in ? I managed to re-compile it but was getting the same error ? I then had other things to do so didn?t get further in my investigation. I?m going to delete the installation and the re-make / install it to see if that sorts it. I?ll let you know how I get on! Dave From: Arnaud Quette [mailto:aquette.dev at gmail.com] Sent: 21 March 2017 15:10 To: Charles Lepple Cc:

Gentlemen, I have now had a chance to run some initial tests of my changes to apc-hid.c of the current development tree. Running newhipups and inspecting the -DDDD output seems to indicate that with the fix below everything seems to work as expected. However, I have not yet shut my system in order to take the UPS out of action so that I can do my various tests with a lightbulb load. I still hope

On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: > On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: > >>> The upsrw command was designed for changing variables that are typically >>> stored in non-volatile memory on the UPS. Unfortunately, your UPS doesn't >>> seem to do that. >> >> Well, if it doesn't do that,

On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote: > On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: > > On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: > >>> The upsrw command was designed for changing variables that are > >>> typically stored in non-volatile memory on the UPS. Unfortunately, > >>> your UPS

On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: >> The upsrw command was designed for changing variables that are typically >> stored in non-volatile memory on the UPS. Unfortunately, your UPS doesn't >> seem to do that. > > Well, if it doesn't do that, how come upsc reports the changed value? It is > only after I reboot the PC

On Jun 3, 2014, at 1:28 AM, Mick wrote: > On Saturday 05 Apr 2014 16:28:24 Charles Lepple wrote: >> On Apr 5, 2014, at 10:39 AM, Charles Lepple wrote: >>> On Apr 5, 2014, at 8:52 AM, Mick <michaelkintzios at gmail.com> wrote: >>>>> The upsrw command was designed for changing variables that are >>>>> typically stored in non-volatile memory on

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120214/3ac7d3df/attachment.html>

Hello Charles, Thank you for your reply. For the discrete value thing, this morning I did try to run sudo upsrw -s input.transfer.low=x -u * -p * ups I changed "x" value from 60 to 96 then checked upsc result. All the script return OK but only 84 and 96 got picked up and working. Out model is Eaton 3S 500. And in windows it has a Eaton Personal Solution Pac. In Battery transfer

On Jun 5, 2014, at 10:53 PM, Charles Lepple wrote: > As you have seen, the "default.*" and "overwrite.*" names are not actual variables: they are configuration options to change what is returned from upsc. That is why you get VAR-NOT-SUPPORTED. typo; should have been "override.*" -- Charles Lepple clepple at gmail

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:

Thanks Charles, On Saturday 05 Apr 2014 12:53:06 Charles Lepple wrote: > On Apr 5, 2014, at 7:18 AM, Mick wrote: > > $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost > > Username (suzy): admin > > Password: > > OK > > This command is sending the value to the UPS (via the usbhid-ups driver). > > > $ upsc iDowell at localhost