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 /var/state/ups: No such file or directory
Driver failed to start (exit status=1)
The new .h file reads as this ?
/* Output page */
{ "output.voltage", 0, 0, "Lv", "%05.1f",
VOLT, TRUE },
{ "output.voltage.nominal", ST_FLAG_RW | ST_FLAG_STRING, 5,
"Lv ?", "%05.1f", VOLT, TRUE },
{ "output.current", 0, 0, "Lc", "%05.1f",
AMPERE, TRUE },
If I copy the old driver back, it works fine ? so I?m guessing I?ve got
something wrong with the compile or syntax!
Welcome your thoughts ? the ESV22+ was a beast I came across which didn?t work ?
I managed to pick up some replacement batteries and it?s now protecting a load
of audio and comms equipment in a charitable community centre in Northern
Romania!
Thanks again
Dave
It's a long time since I've not dive into the UTalk code and devices.
The last time was more than a decade ago.Happy to see some ESV+ alive :)
Then, even reading the spec, I'm not sure what was the exact difference
between Lv and Iv, at least for a small UPS like ESV+.
So you can add the following line after "output.voltage in mge-utalk.h:
"{ "output.voltage.nominal", ST_FLAG_RW | ST_FLAG_STRING, 5,
"Lv ?", "%05.1f", VOLT, TRUE },"
By adding the above, you'll be able to have the nominal output voltage
reading and report (Lv ?) and to use upsrw to set nominal output voltage (Lv
24000).
Please tell us back if the above works fine for you, so that we can update the
driver.
Otherwise, simply test by replacing the "Lv ?" with "Iv ?".
thanks and cheers,
Arno
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170312/84a01baf/attachment-0001.html>
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 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 /var/state/ups: No such file or directory > > Driver failed to start (exit status=1)To match the Raspbian build, I think the configure parameters should look like this: ./configure --build=arm-linux-gnueabihf --prefix= --includedir=/usr/include \ --mandir=/usr/share/man --infodir="\${prefix}/share/info" --sysconfdir=/etc/nut \ --localstatedir=/var --libexecdir="\${prefix}/lib/nut" --enable-maintainer-mode \ --libdir=\${prefix}/lib/arm-linux-gnueabihf --with-ssl --with-nss --with-cgi --with-dev \ --enable-static --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut \ --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut \ --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut --datadir=/usr/share/nut \ --with-pkgconfig-dir=/usr/lib/arm-linux-gnueabihf/pkgconfig \ --with-user=nut --with-group=nut --with-udev-dir=/lib/udev \ --with-systemdsystemunitdir=/lib/systemd/system Source: https://buildd.debian.org/status/fetch.php?pkg=nut&arch=armhf&ver=2.7.4-4&stamp=1475019180&raw=0 (so if the paths are slightly different, it's because the log is from stock Debian vs. Raspbian) You might not need all of those options for just one driver, but it should save some trial-and-error to just copy-and-paste everything, then rebuild.> The new .h file reads as this ? > > > > /* Output page */ > > { "output.voltage", 0, 0, "Lv", "%05.1f", VOLT, TRUE }, > > { "output.voltage.nominal", ST_FLAG_RW | ST_FLAG_STRING, 5, "Lv ?", > "%05.1f", VOLT, TRUE }, > > { "output.current", 0, 0, "Lc", "%05.1f", AMPERE, TRUE }, > > > > If I copy the old driver back, it works fine ? so I?m guessing I?ve got > something wrong with the compile or syntax!The .h file looks good, as far as I can tell.> Welcome your thoughts ? the ESV22+ was a beast I came across which didn?t > work ? I managed to pick up some replacement batteries and it?s now > protecting a load of audio and comms equipment in a charitable community > centre in Northern Romania!Always good to hear about equipment being saved from the dump, and put to good use!
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 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 /var/state/ups: No such file or directory > > > > Driver failed to start (exit status=1) > > To match the Raspbian build, I think the configure parameters should > look like this: > > ./configure --build=arm-linux-gnueabihf --prefix> --includedir=/usr/include \ > --mandir=/usr/share/man --infodir="\${prefix}/share/info" > --sysconfdir=/etc/nut \ > --localstatedir=/var --libexecdir="\${prefix}/lib/nut" > --enable-maintainer-mode \ > --libdir=\${prefix}/lib/arm-linux-gnueabihf --with-ssl --with-nss > --with-cgi --with-dev \ > --enable-static --with-statepath=/var/run/nut > --with-altpidpath=/var/run/nut \ > --with-drvpath=/lib/nut --with-cgipath=/usr/lib/cgi-bin/nut \ > --with-htmlpath=/usr/share/nut/www --with-pidpath=/var/run/nut > --datadir=/usr/share/nut \ > --with-pkgconfig-dir=/usr/lib/arm-linux-gnueabihf/pkgconfig \ > --with-user=nut --with-group=nut --with-udev-dir=/lib/udev \ > --with-systemdsystemunitdir=/lib/systemd/system > > Source: https://buildd.debian.org/status/fetch.php?pkg=nut&arch> armhf&ver=2.7.4-4&stamp=1475019180&raw=0 > (so if the paths are slightly different, it's because the log is from > stock Debian vs. Raspbian) > > You might not need all of those options for just one driver, but it > should save some trial-and-error to just copy-and-paste everything, > then rebuild. > > > The new .h file reads as this ? > > > > > > > > /* Output page */ > > > > { "output.voltage", 0, 0, "Lv", "%05.1f", VOLT, TRUE }, > > > > { "output.voltage.nominal", ST_FLAG_RW | ST_FLAG_STRING, 5, "Lv > ?", > > "%05.1f", VOLT, TRUE }, > > > > { "output.current", 0, 0, "Lc", "%05.1f", AMPERE, TRUE }, > > > > > > > > If I copy the old driver back, it works fine ? so I?m guessing I?ve got > > something wrong with the compile or syntax! > > The .h file looks good, as far as I can tell. > > > Welcome your thoughts ? the ESV22+ was a beast I came across which didn?t > > work ? I managed to pick up some replacement batteries and it?s now > > protecting a load of audio and comms equipment in a charitable community > > centre in Northern Romania! > > Always good to hear about equipment being saved from the dump, and put > to good use! >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170321/7c98e4b7/attachment.html>