similar to: NUT driver scheduler

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

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

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

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

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

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

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

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:

Citeren Frederic BOHE <fbohe-guest op alioth.debian.org>: > --- branches/windows_port/scripts/Windows/wininit.c Tue Jan 18 > 08:57:03 2011 (r2838) > +++ branches/windows_port/scripts/Windows/wininit.c Tue Jan 18 > 10:05:01 2011 (r2839) > @@ -285,8 +285,11 @@ > char fn[SMALLBUF]; > FILE *nutf; > char buf[SMALLBUF]; > + const char * conf_path; > > -

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

Hi: 1. Samba PDC and OpenOffice: I've an strange problem with OpenOffice (2.3 and 2.4) and Samba as PDC (Debian version 3.0.24-6etch10): I have a Windows XP Professional (SP3) connected to a Samba PDC. When I click on a document located in my desktop, OO seems to freeze for more than one minute, and then it loads the document. If I try to load more documents, they load normally. But,

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

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

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

(sorry for my english) Hi, I'm a Network Admin and I've a BIG problem... I start the SMB services, but, one moment later... it's stopped... The NMB service are allright... I've the version 2.0.6... and I'm going crazy... If someone can helpme.... Jordi Solis _________________________________________________________________________ Get Your Private, Free E-mail from MSN