similar to: Solis 1.5 driver NUT (Network UPS Tools)

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.

Hello everyone, Maybe we should separate matters? Rollback to latest working version of Solis driver and create a separate driver for the brazilian APC? I have the decompiled Java source code from the official manufacturer's driver. Also, I have found some bugs introduced in the Solis driver due to APC's support, but had no time to fix it yet (although these bugs should not be

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

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

Hi all, In 1995 I had developed Solis and Rhino drivers, so I think that this driver must be preserved compatibility, because there are Solis and Rhino actives nowadays, I have one Solis 1.5 KVA still working. Why not a new one for new power supply? Silvino Benevides Magalh?es -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

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 Em qua, 19 de jun de 2019 às 03:39, Manuel Wolfshant < wolfy at nobugconsulting.ro> escreveu: > On 6/19/19 5:59 AM, Charles Lepple wrote: > > > “The

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

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,

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

Hello List, I'm having a problem with a windows95 client under Samba server 1.9.17p4. I've created a bat file, named user1.bat, user1 is the name of the ordinary user in use, under the home directory: /home/samba/netlogon. The matter is that when windows logs the bat file is not loaded automatically. The commands inside of it are very simple, as shown in the list below: NET TIME

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

Is anyone besides me using gcc 4.*.*? I noticed that NUT generates an enormous amount of warning noise with that compiler, mostly due to implicit casts between signed/unsigned pointer types. Any volunteers to de-noise the code a bit? The easy way is to insert typecasts; the better way is to actually take care about signedness. -- Peter gcc -I../include -O -Wall -Wsign-compare -c -o everups.o

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

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: nut-patch.zip Type: application/zip Size: 18721 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20060706/c4c32226/nut-patch.zip

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

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