similar to: Microdowell B BOX N30 support

Hello, is it to possible to monitor Microdowell B-Box N30 with latest nut? I have tried but wihout any success. Others ups works fine with nut. What about driver to this ups model? Best Regards, Viktorija

Hello, i am newbie to this soft, but at this moment i like it. I have a few microdowell ups, but i can't get it working with nut 2.0.2 version. I saw that in 1.* was microdowell driver, but in 2.0.2 it doesn't. How can i get work nut 2.0.2 with microdowell ups? Thank You! Viktorija

Hello All I have a MicroDowell ups (BBox BP 1000) connected to a Gentoo box by serial cable. If I try to start the driver , I see the following : Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. debug level is '13' ups_sync: send [\rP4\r] ups_sync: got ret 46 [#1000VA

Hi I got an offer for some microdowell enterprise N- series UPS'ses. The NUT homepage only lists the B.Box BP series. Does anyone know if the Enterprise N- series works with NUT? JonB

Hi all, first message to the list. :-) I've got an iBox made by iDowell: http://store.apple.com/uk/product/TR423ZM/A This seems to be similar to the smaller Microdowell UPS: http://idowell.eu/ I cannot get it recognised by the drivers. This is what I get when I plug in the USB connector: Jan 3 19:27:26 compaq kernel: usb 3-2: new low speed USB device using uhci_hcd and address 47

Hi Recently i bought a MicroDoWell BP50, and with it followed a USB 2 serial converter. When i plug it into my 2.6.19 kernel, dmesg shows hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:04.2-2 usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver So, i figured i should use usbhid-ups,

I'd like to share some of my experience with this UPS. I've compiled nut from the Debian sid sources. Version is 2.2.1. I'm using the powerpanel driver. It seems shutdown.return does in fact what shutdown.return should do. I'll just copy&paste some of my notes made yesterday: Commands were issued as follows: "upscmd -u admin -p admin bbox at localhost

Hi, I'm running a Debian server (amd64) with the latest nut package (2.0.3-4). The server is connected to a Cyberpower OP750E ups. This seems to be connectable using nut with the cpsups driver. I've configured /etc/nut/ups/conf with the correct information. Here is what i get when trying to load the driver : serveurmeteo:/home/did# /sbin/upsdrvctl -v start myups Network UPS Tools -

Hi there First a big thank you to all nut developers. I tried the 2.0.4 as well as the 2.0.5-pre1 versions with my CyberPower OP1000E connected to a serial to USB converter. All I got was the following: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5-pre1 Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5-pre1) Warning: This is an

Hello all. I have installed Nut on a Raspberry PI and all looks to be configured correctly, but I get stale data and communications lost at random intervals. I tried running nut-driver in gcc to see if I could find any clues there, but it ran for about 24 hours with no sign of an issue. However, when I let Nut run normally, it seems to be anywhere from 2 to 8 hours and the data goes stale and

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

Citeren Arnaud Quette <aquette.dev at gmail.com>: > Author: keyson-guest > Date: Wed Feb 4 15:03:36 2009 > New Revision: 1765 > > Log: > - Added mocrodowell.c/h into drivers/. add man/microdowell.8. Adjusted > drivers/Makefile.am and man/makefile.am. Adjusted the code for 2.4.0 in the > microdowell.c. Besides the things already mentioned by others and the obvious

On Mar 17, 2015, at 10:32 PM, Charles Lepple <clepple at gmail.com> wrote: > A bit of explanation on the debug output: the "Report Descriptor: (739 bytes)" hex dump is the HID representation of the individual reports available. NUT parses that out, and iterates over all of the "Usage IDs" (status variables, and settings). The values for the usages are grouped in

Hi Charles, That package is supposed to install both server and client (according to the description at https://packages.debian.org/stretch/nut anyway). I'll try both server and client individually later and see if that helps. Cheers, ST On 3 Aug 2017 7:26 a.m., "Charles Lepple" <clepple at gmail.com> wrote: > On Aug 2, 2017, at 12:09 PM, Song Teck <songteck at

Hi Charles, Thanks for your reply. So the Jessie or stretch versions will work then since those are 2.7.2 and 2.7.4... I will have to update my sources.list and follow this? https://backports.debian.org/Instructions/ Will give it a go later and update either way. Thanks, ST Via mobile On 1 Aug 2017 19:44, "Charles Lepple" <clepple at gmail.com> wrote: > On Aug 1, 2017, at

On Aug 1, 2017, at 12:01 PM, Song Teck <songteck at gmail.com> wrote: > > Hi Charles, > > Ok, I missed the absence from the backports as well. Again, some unfamiliarity here, so > > 1) I presume I cannot use a metapackage meant for jessie or stretch on wheezy? Or if I can, is there a way to deploy it from console? The "nut" metapackage just depends on

Hi Charles, Have managed to make some progress after a fashion. Got the unit to work on the jessie version of NUT (2.7.2). upsc does output the unit parameters, along with the mis-scaled voltage readings described at http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to get the shutdown sequence to work properly. Have been following this:

Hi Charles, Ok, will try the ignore lb flag later. How do I go about capturing the log? I might as well do it while testing the flag... Cheers, ST On 15 August 2017 at 20:42, Charles Lepple <clepple at gmail.com> wrote: > On Aug 15, 2017, at 5:24 AM, Song Teck <songteck at gmail.com> wrote: > > > > Hi Charles, > > > > Have managed to make some progress

Hello, Would like to see if I could get some help with this UPS on a debian set-up. Am not the best with linux and have tried what I managed to find elsewhere on the list so am just trying here. 1) Device seems supported: http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html 2) lsusb -v -d 04d8: seems to give the right parameters including product name, max power etc from the unit 3)

Hi Charles, thanks for the clarification on the libusb. that indeed does work to get the value in ./configure. I've tried installing a .deb sudo dpkg -i nut_2.7.4-5_all.deb (Reading database ... 103447 files and directories currently installed.) Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ... Unpacking replacement nut ... Setting up nut (2.7.4-5) ... which