similar to: Fwd: about solis and rhino

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

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

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

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

2012/10/4 Vinicius Vollrath <vinicius at terradigital.com.br> > Hi Arnaud, Hi Vinicius, > I talked with Silvino Benevides Magalhaes. > I cc'ed him, and the NUT users list, for info. > I use an Solis 1.5 (APC) with Debian 6 - Squeeze, 64-bit. > The error is ever "Solis not detected! Aborting ..." > > I use the ttyS0 port (with correct permissions)

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:

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

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

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

Hello there, Offending source code is ????? if(? ( BattVoltage> 129 ) || ( BattVoltage < 144 ) ) Maybe swap || for && would be better. This problem I found by using cppcheck. It said [rhino.c:190]: (warning) Logical disjunction always evaluates to true: BattVoltage> 129 || BattVoltage < 144. Regards David Binderman

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

Hi all, I attached a driver for MiniBox openUPS device ( http://www.mini-box.com/OpenUPS) and a dump of the hid usages. I had the possibility to make a few adjustments to the device firmware for HID usages, and although I haven't managed to produce a good structure many issues from previous firmware were at least fixed and new information added. ATM the driver only shows pertaining

Description: Fix warning: variable set but not used [-Wunused-but-set-variable]. bugs.debian.org/633756. Related drivers were not tested. Last-Update: Sat, 13 Aug 2011 14:04:48 +0300 Index: b/drivers/belkinunv.c =================================================================== --- a/drivers/belkinunv.c 2011-05-31 13:36:49.000000000 +0300 +++ b/drivers/belkinunv.c

I would like to have your comments regarding: 1) drivers/rhino.c ------------------ The following patch addresses some problems in drivers/rhino.c. Or that is what I think. I don't use this hardware. The patch: 1. Eliminates some usefulness definitions. 2. It removes code that evaluate the time. I can't see how the code actually does useful work. 3. The

Had a fairly horrible lightning storm night before last, and four of eight ports in a 1.4.20 machine stopped answering. In the CLI: budsw*CLI> zap show channels Chan Extension Context Language MOH Interpret pseudo default en default 1 from-zaptel en default 2 from-zaptel en default

The if() statement always evaluated to true. Detected by "cppcheck", not tested on real hardware. Signed-off-by: Thomas Jarosch <thomas.jarosch at intra2net.com> --- drivers/rhino.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/rhino.c b/drivers/rhino.c index ca66169..e478bcb 100644 --- a/drivers/rhino.c +++ b/drivers/rhino.c @@ -187,7 +187,7