similar to: Unable to set up a "serial-over-USB" UPS (APC BZ2200BI-BR)

On Mar 20, 2014, at 10:01 AM, Douglas A. Augusto wrote: > Dear NUT users/developers, > > I'm having trouble while trying to configure the UPS APC BZ2200BI-BR[1] in NUT, > which despite having a USB cable it apparently communicates using the serial > protocol. > > The relevant output of 'lsusb' is: > > Bus 002 Device 004: ID 051d:c812 American Power

Hello Charles and Douglas, I really believe that BZ2200-BR model is the same as mine BZ1200-BR, with different capacity. If you see the BZ2200-BR specs you will notice the manufacturer "APC-Microsol". Those no-breaks have a USB port in it, but in fact it is a serial<->usb cable, usually uses the port "/dev/cuaU0". In mine, the serial<->usb chip is from FTDI, and

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

Anybody knows what configure command settings FreeNAS use to compile NUT? More info on my journey: http://forums.freenas.org/index.php?threads/nobreak-bz1200-br-back-ups-rs-1200va-600w-bivolt-115-nt.20247/ Thanks Bruno -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 04/06/2014 at 09:44, Bruno Salvador <bruno.salvador at gmail.com> wrote: > What Douglas can do is to patch the solis executable in > /usr/local/libexec/nut/solis inside freenas, with the patches that I have > posted in the forum: Dear guys, Following your suggestions I was able to make NUT recognize my UPS model. Actually, the only modification I had to introduce in solis.c

On Sun, 23 Aug 2015 11:09:03 -0400 Charles Lepple <clepple at gmail.com> wrote: > On Aug 21, 2015, at 10:10 AM, Mario Lobo <mlobo at digiart.art.br> wrote: > > > >> Not sure what to look for yet. It might be easier to add in the > >> debug calls to the source code-- can you try building NUT from > >> source? If you installed via the ports tree (as

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:

Hello, I've been trying to set this UPS up on a Synology NAS DS218+ which uses NUT, and even though they are using NUT, they don't have all drivers available as NUT has them at NUT's website. Please see that below: root at DSAltaCloud:/usr/syno/etc/ups# upsdrvctl start Network UPS Tools - UPS driver controller DSM6-2-1-newmodel-repack-23796-180722 Network UPS Tools - Generic HID

On Aug 20, 2015, at 6:33 PM, Mario Lobo <mlobo at digiart.art.br> wrote: > > ** cuaU0 > > [>]/usr/local/libexec/nut/solis -D -a lobos -u root > Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3) > 0.000000 debug level is '1' > 21.065536 Solis not detected! aborting ... It looks like /dev/cuaU0 is the port that was suggested for a

On Aug 23, 2015, at 6:26 PM, Mario Lobo <mlobo at digiart.art.br> wrote: > > I hope it helps! It is a bit easier to read than the ktrace output. Here are the bytes received, without the other messages: Network UPS Tools - Microsol Solis UPS driver 0.63 (2.7.3.1) CommReceive: RecPack: (25 bytes) => 00 17 91 49 5e 5e bc fe bb 46 88 ac 1b 0a a0 ed 01 07 07 bb 46 82 ae 1b 09

On Tue, 8 Sep 2015 22:25: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

I use Centos 7.6.1810 in my server with nut-2.7.2-4.el7.x86_64 which contains Solis version 0.60 08/18/2005, my last version. My hardware related by upsc is Microsol Solis 1.5, the same used to develop the driver. It's an ancient nobreak, but i still works, by the way, an excellent hardware, using the third set of batteries. If you need more information, please let me know. Greeting, Silvino.

On Jun 19, 2019, at 11:56 AM, Silvino Benevides Magalhaes wrote: > > Unfortunately I do not use the latest versions of NUT, the driver I created, solis, was changed, not by me, and now does not work on my nobreak, which I used to create the driver. > > greetings > > Silvino B. Magalhaes Silvino, We have had several changes to solis over the years to add new models

On Aug 21, 2015, at 10:10 AM, Mario Lobo <mlobo at digiart.art.br> wrote: > >> Not sure what to look for yet. It might be easier to add in the debug >> calls to the source code-- can you try building NUT from source? If >> you installed via the ports tree (as opposed to binary packages), you >> should have most of the dependencies installed. You might also need

Hi Charles; I tried both of your suggestions: 1) run stty -f /dev/cuaU0 raw jusbefore running solis 2) Unplug/plug, and run solis right after. The problem still persists. [~]>stty -a -f /dev/cuaU0 speed 9600 baud; 0 rows; 0 columns; lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc

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

On Sep 11, 2015, at 8:11 AM, Mario Lobo <mlobo at digiart.art.br> wrote: > > On Thu, 10 Sep 2015 22:31:08 -0400 > Charles Lepple <clepple at gmail.com> wrote: > >> On Sep 9, 2015, at 2:06 PM, Mario Lobo <mlobo at digiart.art.br> wrote: >>> >>> By the constance of header and footer bytes, I think something >>> different is going on

On Fri, Sep 11, 2015 at 10: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

Dear friends, I installed NUT and followed all suggested procedures to verify if my ups is supported. No driver recognized my ups, and the genericups tests get wrong. Here I send some informations about it: The ups model is APC BZ1200-BR I use Ubuntu, and the lsusb results Bus 003 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC for ups. The

Dear nut-upsdev, I writed one small function to test if batteries was really bad (using solis driver). Isn't so acurated but it's what we need. Just wait 100% batteries charge, turn off input, wait some time (10% from previst autonomy) and turn on input again. Looking startAutonomy - stopAutonomy we can know the basic batteries state. To scheduler the tests I have one new parameter on