similar to: AEG - PROTECT HOME support using NUT with serial protocol

Hallo, I'm loocking for a driver to connect a AEG UPS Protection A 1500 mit nut. The Error-massage is this: Network UPS Tools - UPS driver controller 2.6.0 Network UPS Tools - Generic HID driver 0.35 (2.6.0) USB communication driver 0.31 This Liebert device (06da:0003) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but

Yes both UPS units are on different power supplies. MINSUPPLIES is set to 1. Afaik NUT waits for OB and LB before shutting down the system. Is there a way to change this behavior to only wait for OB? Then I would use FINALDELAY in case the power outage doesn't last long. I already tried to change the battery.runtime.low setting over the webinterface of the CS121 (snmp is readonly) but with

hi all, really simple fix for the bestups driver: In function: upsdrv_makevartable() you need to add the line addvar(VAR_VALUE, "battvoltmult", "Battery voltage multiplier"); There are a number of simple improvements I could make to this driver, but I'm assuming that since the above bug has been around since nut v2.4, not many people are using this driver. Is this

Hi Daniele, I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1. It looks like things mostly work: bestups: battery.charge: 100.0 battery.voltage: 13.9 battery.voltage.nominal: 12 device.mfr: Best Power device.model: Patriot Pro II 400 device.type: ups

Hi There, We have this rather large-ish floor-standing Best Axxium Pro, Model Series 0650. I tried using both the "bestups" and "blazer_ser" drivers with it, but no go. So before I go any further: *Should* one of these work with it and, if not, do I have any options? (E.g.: Modify a current driver, resuscitate one that was started and abandoned, etc.? I can code.) My test

Hi list, on my previous (lenny or squeeze) machine, I had it up and running, but that machine and configs are gone - and on my new jessie machine (see device and config details below) I cannot start the driver: # /lib/nut/bestups -DDDDD -a Patriot_Pro_II_750 0.000000 debug level is '5' 0.000806 send_to_all: SETINFO device.type "ups" 0.000842 send_to_all:

On Fri, Dec 16, 2016 at 02:29:28PM -0500, Jonathan Billings wrote: > The culprit? NetworkManager has /home open. I can't figure out > *WHY*. NetworkManager.service has 'ProtectHome=read-only', which keeps NM from writing there. I presume namespacing /home in this way counts against unmounting it. This is a good security protection for everyone running NM, so I can see it being

Yup, verified those options are *not* set in 7.2. For a quick test I simply removed them from /usr/lib/systemd/system/NetworkManager.service, did a systemctl daemon-reload, restarted NetworkManager, logged back in as root, and was able to whack /home (7.3). On Tue, Dec 20, 2016 at 11:07 AM, Matthew Miller <mattdm at mattdm.org> wrote: > On Fri, Dec 16, 2016 at 02:29:28PM -0500, Jonathan

> On October 28, 2017 at 1:41 PM Tobi <tobster at brain-force.ch> wrote: > > > Hello list > > I saw the response from Vlad in my queue (as dovecot was broken there > has been no delivery to mailbox) but after fix and queue flush Vlads > message does not show up in my mailbox. > > > Check the systemd unit for ProtectHome, and make sure that is turned >

Hi, I have a Liebert PowerSure Personal XT that I have connected via its USB interface. lsusb shows that it is there and when I plugged in I got the kernel messages: Jul 3 11:25:37 mint kernel: usb 2-2.2: new low speed USB device using address 4 Jul 3 11:25:38 mint kernel: hiddev96: USB HID v1.11 Device [LIEBERT PowerSure Personal XT] on usb-0000:00:10.0-2.2 The documentation suggests that

Hello all, been 5 years since I posted on this list, glad to be back :) I have a number of X-power Tigra 1kVA online UPS units. From some knowledgeable folks working for the local distributor, I learnt that from inside this looked like a Best 610 ups unit. Before, I had this UPS hooked via serial to my Windows 2003 server. For monitoring, some winpilot/upspilot software was also provided.

> I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1. > > It looks like things mostly work: Nice, merging bestups.c into nutdrv_qx has been on my todo list for a while, let's see how far we can get. > 1) The bestups driver uses an "ID"

Dear ladies and gentlemen, we are developer and producer of UPS devices. Now we would like to integrate a small UPS via USB connection to NAS systems. We heart from third party that we need a special driver for NAS systems to work fine and to display also the company name and UPS device name in the web page / software of NAS. Currently we have a UPS with USB and our own VID (0x2B2D) and PID

Some one might have answerd this, but I can not find any think yet I am trying to load a SOLA 610 700va ups up and keep getting : --------------------------------- Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.88 (2.0.5) .Detected Pulsar ESV11+ on /dev/cuaa0 Network UPS Tools - Best UPS driver 1.03 (2.0.5) Unknown model detected - please

Hi, i just got a Phoenix Technologies PH1200UPSB 1200va serial-port ups and it is only partially supported by bestups driver (needs manual ID or driver rewriting). It comes with a tool called UPSilon 2.1 on a CD (which worked better with TERM=linux). After [sl]tracing it i came to these results: COMMANDS : - Command: I Response: "#XPHOENIX TECH PH1200UPS VER2.00C " - Command: F

> Sure enough, it turned off after about 30 seconds (t=228). I unplugged it for about five seconds, and it came back on three minutes after I plugged it back in. However, the bypass bit inversion might be responsible for this: > > 228.304623 send: 'Q1' > 228.515426 read: '(119.0 119.0 000.0 000 60.0 13.5 XX.X 00001010' > 228.515494 ups_infoval_set: non

Hi Charles, thank you VERY MUCH for all your hints. > If you have a jumper wire handy, you can connect the PC's TxD to RxD I should have tried to connect from another computer in the first place. Or access another device known to work from this computer. It turned out that the shield I used to connect the mainboard connector to the PC case expected another mainboard pin layout. So all I

On Nov 1, 2014, at 9:28 PM, hyouko at gmail.com wrote: > Provided that the subdriver works, I'd like to see, if possible, the logs of: > - driver startup > - a command that succeeds > - a command that fails > - q1 when online and all's ok > - q1 on battery > - setting pins_shutdown_mode Attached is a log of most of these conditions. Looks like reading the status for