search for: soli

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 10.2-STABL...

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

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 (especially after the APC acquisition), and we tried to make sure t...

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 as a hobby too. The driver supports all features that the APC provided software provides and I implemented all information I could possibly get and set with NUT (for ex...

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 development. I say 5 stars to rhino support. About solis, I...

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

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) with a serial cable. > The version of the drive is 2005. > > Are there changes in the protocols or other parameter? >...

...al<->usb cable, usually uses the port "/dev/cuaU0". In mine, the serial<->usb chip is from FTDI, and its recognized by FreeNAS with any additional drivers. And for sure, you can never use the genuine APC driver with those Microsol nobreaks. 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: This will work for FreeNAS last version 9.2.1.5. http://forums.freenas.org/index.php?threads/nobreak-bz1200-br-back-ups-rs-1200va-600w-bivolt-115-nt.20247/ *Instructions: * 1) Open the &q...

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 was to change this line: i...

...: In function pw_comm_setup: bcmxcp_ser.c:259: warning: pointer targets in passing argument 2 of command_read_sequence differ in signedness bcmxcp_ser.c:271: warning: pointer targets in passing argument 2 of command_read_sequence differ in signedness gcc -I../include -O -Wall -Wsign-compare -c -o solis.o solis.c solis.c: In function getbaseinfo: solis.c:531: warning: pointer targets in passing argument 2 of ser_get_buf_len differ in signedness solis.c:539: warning: pointer targets in passing argument 1 of CommReceive differ in signedness solis.c:541: warning: pointer targets in passing argument...

...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 that it might get out of sync later, > but I don't want to change too much at once. Hi Charles ! By the constance of header and footer bytes, I think something different is going on now. It still identifying as a Solis...

(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 Hotmail at http://www.hotmail.com.

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

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 similarly-named model last year: http://article.gm...

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:

.../Library/Frameworks/R.framework (by typing ls /Library/Frameworks) and it does not appear. A global search for R.framework yields no results, so it seems that the installation is not working. (I was going to try command line execution.) Any help would be appreciated. Thanks! - RSS Ruben S. Solis

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

Hi all! The following files emits warnings when compiled with gcc 4.0: al175.c bcmxcp_ser.c belkinunv.c cyberpower.c everups.c powercom.c solis.c All warnings seem to be of this variety: everups.c:38: warning: pointer targets in passing argument 2 of 'ser_get_char' differ in signedness I suggest that those who fiddles with those drivers fixes the warnings and verifies that it works afterwards. I can provide the complete buildl...

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

...eader and footer bytes, I think something >>> different is going on now. >> >> Right, this is the resync code that @rpvelloso suggested. >> >> https://github.com/networkupstools/nut/issues/231#issuecomment-138971923 >> >>> It still identifying as a Solis 1.0 (which is not) but at least it >>> is doing it on its own, without gdb. >> >> If I remember correctly, Bruno was mainly looking for OB/LB status, >> so he mapped the APC model to the nearest Solis model. I've CC'd him >> in case he has any other insigh...