search for: _source_code_management

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

On 2016-01-28 8:18 AM, Charles Lepple wrote: > I definitely like your approach. Thanks for moving some of the "magic numbers" to named constants, as well. Thanks. Always nice to have real coders sanity check anything I've written with a "thumbs up" response. (I'm more a hardware guy) And sscanf was working like poo -- so I figured I'd parse it differently with

...lled via the ports tree (as opposed to binary packages), you >> should have most of the dependencies installed. You might also need >> libtool and autoconf, as mentioned in the second link below: >> >> http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_source_code_management >> and >> 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/networkupstoo...

...d to binary > >> packages), you should have most of the dependencies installed. You > >> might also need libtool and autoconf, as mentioned in the second > >> link below: > >> > >> http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_source_code_management > >> and > >> 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 through...