similar to: patch file

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.

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

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

Hi, First of all I'd like to congratulate everyone engaged in this great project. I've been following this list since late 2014, when I acquired an APC UPS model BZ1200BR. APC bought a Brazilian company named Microsol, which NUT package had drivers for Solis and Rhino models. Since that time, I started developing a new driver for the models below, as a way to support my own device, but

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: microsol2_nut-2.0.3.patch Type: text/x-patch Size: 83845 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20060706/94d79f30/microsol2_nut-2.0.3-0001.bin

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

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

On 6/19/19 5:59 AM, Charles Lepple wrote: >> >> “The 62-nut-usbups.rules file looks pretty standard. Do you know if the changes to 42-usb-hd-pm.rules are needed? It seems like none of the USB devices would have the right permissions if 62-nut-usbups.rules isn't sufficient (though this happened in Debian once).” >> >> My means of testing wasn’t the most rigorous,

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

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 Conversion The device is registered as /dev/ttyACM0 and uses the kernel module 'cdc_acm' (USB

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

FYI Arnaud ---------- Forwarded message ---------- From: Silvino Benevides Magalhaes <sbm2yk at gmail.com> Date: 2009/10/14 Subject: Re: about solis and rhino To: Arnaud Quette <aquette.dev at gmail.com> Hi Arnaud, I was on holiday, so I only answer you now. About rhino, I received a document contains the its protocol and a little box with rhino firmware to testing driver

l?rdagen den 29 juni 2013 11.28.14 skrev Mike.: 8<------------------snip--------------------- Hi Mike, > > Thanks for the quick reply. > > I checked the log file (which, admittedly, I should have done before I > posted about the problem :) ). > > Here's the command and the corresponding log message: > > # upsrw -u au -p ap -s outlet.1.delay.shutdown=12

On 6/29/2013 at 6:16 PM Kjell Claesson wrote: |l??rdagen den 29 juni 2013 11.28.14 skrev Mike.: |8<------------------snip--------------------- |Hi Mike, |> |> Thanks for the quick reply. |> |> I checked the log file (which, admittedly, I should have done before I |> posted about the problem :) ). |> |> Here's the command and the corresponding log message: |>

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

l?rdagen den 29 juni 2013 15.22.44 skrev Mike.: 8<-------------snip----------------- Sorry for the delay. > Here is the console output of bcmxcp with -DDD specified: > > > [snip] > 13.721204 Auto delay on: 2 > > 13.721243 send_command: (4 bytes) => ab 01 35 1f > 13.821127 send_command: (4 bytes) => ab 01 33 21 > 13.920982

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, First of all I''m new to working with sockets, so the problems I''m having are probably because of my lack of understanding. What I''m trying to accomplish is to create a mac os x client gui to ruby-debug. When a application that includes ruby-debug is started, it starts listening for 2 connections; 8989, 8990 The connection is made by calling the connectToApp

On 18/5/25 22:07, Greg Troxel wrote: > Eyal Lebedinsky <eyal at eyal.emu.id.au> writes: > >> I am upgrading to f42. >> >> I get this failure doing "dnf system-upgrade download --releasever=42" >> >> 2025-05-17T21:13:37+1000 CRITICAL Error: Transaction test error: >> file /usr/bin/rhino conflicts between attempted installs of

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