similar to: driver development

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

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.

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

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

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

I want to use upsdebugx, upslogx in 'clients/upsclient.c', however this fails with the following error messages (I trimmed the path to the build directory to <path> in order to prevent line wrapping): <path>/clients/upsclient.c:941: undefined reference to `upsdebugx' <path>/clients/upsclient.c:910: undefined reference to `upslogx'

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

Fellows, time has come for a new NUT release: I'm planning on 2.6.1 next week (max Friday 27), and I'm currently processing remaining patches. If you have some more on your side, please send in. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

On Jul 2, 2013, at 5:16 PM, Kjell Claesson wrote: >> I hope other people can also test this. >> >> Regards >> Alf Hogemark > > Due to some crashes on the disks and lack of time I don't have the git on the > pc now. But maybe some other can commit this. I'd like to ask people to specifically try the bcmxcp branch on GitHub - it includes some changes

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

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

This mib used to work, so is there a way to go back to the version prior to this one without downgrading the whole package? * Starting UPS drivers... Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Generic SNMP UPS driver 0.44 (2.4.1) Detected GXT2-2000RT120 on host upswallleft (mib: ietf 1.3) [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.4.0: Error in

Hi Arnaud, Hi Scott, Hi list, Here is a patch to support the Zinto D from ONLINE USV-Systeme AG. I already sent a version to Russell Kroll (2006-04-09), without no response and I cannot find support for Zinto in svn until now. I found a discussion on this list about the Xanto from ONLINE, but the Zinto seems to use different commands. The commands are quite similar to those for Opti-UPS, so I

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the

Hi, I started updating smart driver with a few things I've been missing. While going through the source: - in upsdrv_shutdown(), there're loads of printfs - they kinda look like a leftover from older debug times. Shouldn't they be changed into upsdebugx() or upslogx() ?

Anybody knows what configure command settings FreeNAS use to compile NUT? More info on my journey: http://forums.freenas.org/index.php?threads/nobreak-bz1200-br-back-ups-rs-1200va-600w-bivolt-115-nt.20247/ Thanks Bruno -------------- next part -------------- An HTML attachment was scrubbed... URL:

Earlier this year, I added a patch to my local NUT tree to additionally print the value of usb_strerror() if usb_clear_halt() failed. (Ignore the commented-out goto.) Since these messages are at the LOG_ERR level, should we add usb_strerror() to all of the calls in nut_usb.c? diff --git a/drivers/nut_usb.c b/drivers/nut_usb.c index 494a1fa..4ca2691 100644 --- a/drivers/nut_usb.c +++

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