similar to: Best UPS protocol for home-made firmware?

Hello, I've got Tripplite Smart Int 1000 UPS with lan4.1 serial interface. Quite sympathetic UPS, I must say from first glance. I have made a proper serial cable (btw i hate all those constructor's decisions to make distinct serial wiring for each and every UPS type from each and every manufacturer!) I use [tripplite] driver for NUT and I can use upsc to get report from UPS, but

Hi, I'm building a DIY UPS for a Raspberry Pi using a 12V SLA battery, charger, and an off the shelf 5V regulator. To monitor the battery level I'd like to use an Arduino or similar type device. Since the Arduino can have a serial over USB connection with the Pi I'd like to implement a protocol that can be used with NUT. Does anyone know if something like this has already been done?

Luke-Jr wrote, On 9/18/2013 1:02 PM: > I wanted to suggest some rating for functionality. I got the UPS available > that seemed to have the best possible rating from NUT's list (Eaton Powerware > UPS 1500), and found out it doesn't support telling me battery level or > runtime! :/ I'm avoiding Eaton/Powerware because the lack of usbhid support, the bcmxcp driver

Hi, I just acquired a Ritmo AS-800VA. Unfortunately, it doesn't work out of the box with nut - so I had to do a bit of reverse engineering on the protocol to get it working. Am now posting my findings here in the hope it will get this added to the next release. There are also 1000VA and 12000VA versions that this should work with. The protocol is very similar to the megatec protocol -

I wanted to suggest some rating for functionality. I got the UPS available that seemed to have the best possible rating from NUT's list (Eaton Powerware UPS 1500), and found out it doesn't support telling me battery level or runtime! :/ Luke

On Aug 19, 2018, at 3:31 PM, Glenn Ramsey <gr at componic.co.nz> wrote: > > Hi, > > I'm building a DIY UPS for a Raspberry Pi using a 12V SLA battery, charger, and > an off the shelf 5V regulator. To monitor the battery level I'd like to use an > Arduino or similar type device. Since the Arduino can have a serial over USB > connection with the Pi I'd like

Hello, I'm trying to get my UPS working with nut-hal-drivers, and it seems be detected correctly with Megatec protocol, but it provides wrong battery level. I read that I can use battvolts option to fix this problem, but HAL version of nut does not come with any config files. So, I'm guess it should be somehow fixed in sources? Parameters of Ippon Back Comfo Pro 800: VA = 800 max

Couple of things: 1. Like Darrell suggested, you should enable stat-prefetch and increase client and server event threads to 4. # gluster volume set <VOL> performance.stat-prefetch on # gluster volume set <VOL> client.event-threads 4 # gluster volume set <VOL> server.event-threads 4 2. Also glusterfs-3.10.1 and above has a shard performance bug fix -

Hello Developers and *, I am working on a "24V DC ATX PSU" for Photopholtaik Systems which can have input voltages from 18V to 27.7 Volt and is entirely modular, which mean, you can select the desired module/s (up to 6) from ATX (96/144/240/300W), P4 (144W), SATA (82/305W) and Device (34/68/136W) And last not least, I want to build a "PowerWhatch" module which should be

[Adding gluster-users] On Mon, Jun 19, 2017 at 8:16 PM, Chris Boot <bootc at bootc.net> wrote: > Hi folks, > > I have 3x servers in a "hyper-converged" oVirt 4.1.2 + GlusterFS 3.10 > configuration. My VMs run off a replica 3 arbiter 1 volume comprised of > 6 bricks, which themselves live on two SSDs in each of the servers (one > brick per SSD). The bricks are

On 08:09, Fri 26 Sep 14, Charles Lepple wrote: > Well, I ended up linking to the latest version of those files, so this shows the change better: > > https://github.com/networkupstools/nut/commit/f61edb5161de97944074867832edc014323340b1 > > Still a magic constant, but now it has the nominal voltage factored in. Just building your latest code now. Which commit is this in (just to

https://bugzilla.netfilter.org/show_bug.cgi?id=871 Summary: Running two instances of ulog causes abort in libnfnetlink Product: ulogd Version: SVN (please provide timestamp) Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: ulogd AssignedTo:

Le samedi 12 septembre 2009 ? 01:59 -0300, Vitor Choi Feitosa a ?crit : > Hi Arnaud, Hi Vitor, > I found your email on the contact page and since you seem to work for > Eaton and is involved in the NUT community I think you're the right > person to contact. > > I've got an Eaton NV 1000H and just installed it here. Before NUT > configuration I've checked the HCL

On 22:17, Thu 25 Sep 14, Charles Lepple wrote: > > I think the OMNIVS800 protocol 2012 entry came from Tripp Lite test results. (There have definitely been naming collisions in the past; hence, the messages in the drivers if you accidentally choose the wrong one.) > > Confusingly, if the USB ProductID is 0001, the Tripp Lite specific "Protocol" number (shown in

On Tue, 15 Oct 2013 21:56:16 -0400 Charles Lepple <clepple at gmail.com> wrote: > >> What are you trying to optimize? > > > > nothing, but I just did not want another daemon running, or at > > least I do not want a port open that can access the UPS, because I > > will not be using it; it is more of a minor security issue than > > anything. The

On Sep 26, 2014, at 8:31 AM, Dave Williams <dave at opensourcesolutions.co.uk> wrote: > On 08:09, Fri 26 Sep 14, Charles Lepple wrote: >> Well, I ended up linking to the latest version of those files, so this shows the change better: >> >> https://github.com/networkupstools/nut/commit/f61edb5161de97944074867832edc014323340b1 >> >> Still a magic constant,

Have you tried with: performance.strict-o-direct : off performance.strict-write-ordering : off They can be changed dynamically. On 20 June 2017 at 17:21, Sahina Bose <sabose at redhat.com> wrote: > [Adding gluster-users] > > On Mon, Jun 19, 2017 at 8:16 PM, Chris Boot <bootc at bootc.net> wrote: > >> Hi folks, >> >> I have 3x servers in a

On Sep 26, 2014, at 3:48 AM, Dave Williams <dave at opensourcesolutions.co.uk> wrote: > On 22:17, Thu 25 Sep 14, Charles Lepple wrote: >> >> I think the OMNIVS800 protocol 2012 entry came from Tripp Lite test results. (There have definitely been naming collisions in the past; hence, the messages in the drivers if you accidentally choose the wrong one.) >> >>

Hello, I have a UPS unit with a USB Interface that appears to work with the blazer_usb and nutdrv_qx drivers. I have tried all combinations of subdriver and protocol and the result is always the same. The values returned are all zero's. The issue seems to be the same as https://github.com/networkupstools/nut/issues/307 Attempts to send a command to silence the beeper or trigger a battery

Dear Krutika, Sorry for asking so naively but can you tell me on what factor do you base that the client and server event-threads parameters for a volume should be set to 4? Is this metric for example based on the number of cores a GlusterFS server has? I am asking because I saw my GlusterFS volumes are set to 2 and would like to set these parameters to something meaningful for performance