search for: microsol

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, I've been trying to set this UPS up on a Synology NAS DS218+ which uses NUT, and even though they are using NUT, they don't have all drivers available as NUT has them at NUT's website. Please see that below: root at DSAltaCloud:/usr/syno/etc/ups# upsdrvctl start Network UPS Tools - UPS driver controller DSM6-2-1-newmodel-repack-23796-180722 Network UPS Tools - Generic HID

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 its recognized by FreeNAS with any additional drivers. And for sure, you can never use the genuine APC dr...

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

...; 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 Douglas, It sounds like you have an UPS which was originally manufactured by Microsol. http://forums.freenas.org/index.php?threads/nobreak-bz1200-br-back-ups-rs-1200va-600w-bivolt-115-nt.20247/ http://article.gmane.org/gmane.comp.monitoring.nut.devel/6685 Bruno, Does your UPS show up as a USB ACM device in FreeBSD? Do you think that you and Douglas have the same basic UPS...

...0 ttyU0.init ttyU0.lock cuaU0 cuaU0.init cuaU0.lock ugen1.2 (ugen1.2 -> usb/1.2.0) (no umodem0 device shows) ** ups.conf [lobos] driver = solis port = /dev/ttyU0 (or cuaU0, or ugen1.2) *** RESULTS ** ugen1.2 [>]/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' 0.001551 tcgetattr(/dev/ugen1.2): Inappropriate ioctl for device ** ttyU0 [>]/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 i...

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

...amp; 0xF0) == 0xB0 ) Unfortunately some important information, as for instance the battery charge, do not work (e.g., battery charge is always zero). But at least now I have access to whether the UPS is on battery or not. Please let me know if you are interested in fully supporting such class of Microsol UPS in the upstream version. I do not understand the whole thing to do it on my own, but I am willing to help you on this. Thank you very much. Best regards, -- Douglas A. Augusto

...t;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 received a solis hardware and a Microsol Windows application sources in Delphi. This application contained the protocol, but a juggle on solis firware was obscure, its internal rotate ?calendar, so I did need to discovery by hand, to allow adjust its internal date, as you see in solis driver code. I say 4 stars to solis support. cheers,...

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

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. Em qui, 20 de jun de 2019 às 08:11, Roberto Panerai Velloso &l...

...ERSION, upsversion()); experimental_driver = 1; } Index: drivers/rhino.c =================================================================== --- drivers/rhino.c (revision 916) +++ drivers/rhino.c (working copy) @@ -789,7 +789,7 @@ void upsdrv_banner(void) { printf("Network UPS Tools - Microsol Rhino UPS driver %s (%s)\n", - DRV_VERSION, UPS_VERSION); + DRV_VERSION, upsversion()); printf("by Silvino B. Magalhaes for Microsol - sbm2yk at gmail.com\n\n"); } Index: drivers/safenet.c =================================================================== --- drivers/...

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.gmane.org/gmane.comp.monitoring.nut.user/8554 The binary...

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

...s (look for the nut-* link under step 5): > > http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/389 > Here is what I got from running the just-compiled nut-2.7.3.1.tar.gz: [~]>/usr/local/libexec/nut/solis -a lobos -u root -D -D -D Network UPS Tools - Microsol Solis UPS driver 0.63 (2.7.3.1) 0.000000 debug level is '3' 0.001946 getbaseinfo: sending CMD_UPSCONT and ENDCHAR to sync 0.002111 getbaseinfo: requesting 25 bytes from ser_get_buf_len() 0.963327 getbaseinfo: received 25 bytes from ser_get_buf_len() 0.963360...

...r}=="050d", ATTRS{idProduct}=="0551", ENV{UPOWER_BATTERY_TYPE}="ups" Index: data/driver.list.in =================================================================== --- data/driver.list.in (revision 3782) +++ data/driver.list.in (working copy) @@ -644,6 +644,8 @@ "Microsol" "ups" "5" "Rhino 10.0" "10000VA" "rhino" "Microsol" "ups" "5" "Rhino 20.0" "20000VA" "rhino" +"Minibox" "ups" "5" "openUPS Intelligent UPS"...

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

On Aug 23, 2015, at 6:26 PM, Mario Lobo <mlobo at digiart.art.br> wrote: > > I hope it helps! It is a bit easier to read than the ktrace output. Here are the bytes received, without the other messages: Network UPS Tools - Microsol Solis UPS driver 0.63 (2.7.3.1) CommReceive: RecPack: (25 bytes) => 00 17 91 49 5e 5e bc fe bb 46 88 ac 1b 0a a0 ed 01 07 07 bb 46 82 ae 1b 09 CommReceive: RecPack: (25 bytes) => a0 04 02 06 1d 0d 03 00 00 00 01 00 17 91 49 5e 5e dc fe bb 47 83 ad 1a 09 CommReceive: RecPack: (25 bytes) =>...

...e constance of header and footer bytes, I think something different is going on now. It still identifying as a Solis 1.0 (which is not) but at least it is doing it on its own, without gdb. Here is the output: /usr/local/libexec/nut/solis -a lobos -u root -D -D -D Network UPS Tools - APC/Microsol Solis UPS driver 0.64 (2.7.3.1) 0.000000 debug level is '3' 0.001843 getbaseinfo: sending CMD_UPSCONT and ENDCHAR to sync 1.330248 getbaseinfo: received 25 bytes from ser_get_buf_len() 1.330283 CommReceive: RecPack: (25 bytes) => bb 47 88 ad 1b 0a a0 18 02 30...

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: