search for: solis_debug

Turns out another user reported the same issue with a slightly different model: https://github.com/networkupstools/nut/issues/231 <https://github.com/networkupstools/nut/issues/231> The "stty -f /dev/cuaU0 raw" trick should help, but I am confused as to why FreeBSD has different "raw" settings than what is set up at the same time as the baud rate:

...d >> http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building >> > > Yes I did build it through ports. I try to build a debug version of it. Mario, I added a few debug statements throughout the solis driver: https://github.com/networkupstools/nut/tree/solis_debug If you run into trouble with the initial build, there will be a tarball snapshot here shortly that bypasses some of the autoconf/libtool issues (look for the nut-* link under step 5): http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/389 -- Charles Lepple clepple at...

@rpvelloso on Github suggested some changes (driver version v0.64) that should help with the initial sync: https://github.com/networkupstools/nut/commit/debc8e0280ea4de9a0db5ca34aa66705b285f61f It's the solis_debug branch on Github. Does that help? I'm concerned that it might get out of sync later, but I don't want to change too much at once.

...54 AM, Mario Lobo <mlobo at digiart.art.br> wrote: > I know the battery is fully charged and that the load is more than 7.2%. > > The battery voltage seems correct. Mario, I realize some of the variables are not yet correct, but is this better than before? I would like to merge the solis_debug branch in to the master branch. Bruno, Any ideas? Mario mentioned his model is getting mis-detected as a Solis 1.0. -- - Charles Lepple

Hi; I'm having some trouble to comunicate with my just bought (08/17/15) Ups. According to SOLIS(8): SUPPORTED HARDWARE This driver has been tested with : Solis 1000 VA Solis 1500 VA Solis 2000 VA Solis 3000 VA Back-UPS BZ1200-BR Back-UPS BZ2200BI-BR So solis is the one to go for. Here is my scenario: SW: nut-2.7.3 (compiled from ports) OS: FreeBSD

...54 -0400 Charles Lepple <clepple at gmail.com> wrote: > @rpvelloso on Github suggested some changes (driver version v0.64) > that should help with the initial sync: > > https://github.com/networkupstools/nut/commit/debc8e0280ea4de9a0db5ca34aa66705b285f61f > > It's the solis_debug branch on Github. > > Does that help? I'm concerned that it might get out of sync later, > but I don't want to change too much at once. Hi Charles ! By the constance of header and footer bytes, I think something different is going on now. It still identifying as a Solis 1.0 (w...

...r-guide.chunked/ar01s03.html#building > >> > > > > Yes I did build it through ports. I try to build a debug version of > > it. > > Mario, > > I added a few debug statements throughout the solis driver: > > https://github.com/networkupstools/nut/tree/solis_debug > > If you run into trouble with the initial build, there will be a > tarball snapshot here shortly that bypasses some of the > autoconf/libtool issues (look for the nut-* link under step 5): > > http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/389 &...