similar to: How to post a device dump to the DDL?

Daniele, thank you.See attached file.Yuri -------- Исходное сообщение --------От: Daniele Pezzini <hyouko at gmail.com> Дата: 05.03.2019 3:09 (GMT+03:00) Кому: "Yuri V. Mednitski" <ranger at ranger.ru> Копия: nut-upsuser at alioth-lists.debian.net Тема: Re: [Nut-upsuser] How to post a device dump to the DDL? Either open a pull request on our GitHub

Hi Daniele and Arnaud, While tracking down the Cyber Power voltage scaling issue, I found the DDL repository extremely helpful. Instead of searching across all of the old mailing list posts, I was able to run 'git grep' in the Cyber Power directory, and the consistency of the data made it an easy task. I had a motherboard failure on my main computer, and I was trying to recreate the

> Is this the current layout? > > nut-website (branch: dll-hll) > \__ nut submodule (branch: master) > \__ ddl submodule (branch unknown?) nut-website (branch: dll-hll) \__ nut submodule (branch: master @ abc0006 [not updated to avoid conflicts when merging back to master]) \__ ddl submodule (branch: master @ bbfd79f; now updated to ab6166c) > The "ddl" branch

On 8/19/20 12:55 PM, Marc Franquesa wrote: > Thanks all for the quick responses on the question (always a good sign > of this mailing list). > > (Tim Dawson, Manuel Wolfshant): > Regarding root cause of my current problem pointing to a faulty > battery, this is not the first time that someone points to it. However > I made a simple test with the vendor tools (Windows) and

Hello. In continuation to http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-June/002880.html Inelt Monolith II 1000 (don't know about LT) actually requires sending shutdown command twice, with delay of 5 to 8 seconds, according to my experiments. The attached patch enables the megatec driver to repeat shutdown command with configurable delay (cmdrepeat, in milliseconds). Default

Device manufacturer: Fideltronik INIGO Device name: Viper 1200 Device type: UPS Bus type: USB WWW: http://fideltronikinigo.com/viper/viper-1200/ " nut-scanner -U" output: [nutdev1] driver = "blazer_usb" port = "auto" vendorid = "0001" productid = "0000" product = "MEC0003" vendor =

We're looking at replacing some old APC SmartUPS 5000s with something that has USB so NUT can more easily talk with it (and yes, I've tried USB-RS232 adapters and every one I tried started kicking out errors within a few hours). One of the bids we have is for a "Tripp Lite UPS Smart Online 5000VA 4500W Rackmount 5kVA 200V/240V" as the potential replacement unit. I have no

Hi, I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date (NUT) but BATTDATE shows the correct date of 2016/05/11. While NUT shows the battery.date as 2001/09/25 which doesn't make sense. Any ideas? Pfsense 2.4.3-RELEASE-p1 (amd64) NUT 2.7.4_6 NUT installed through

Hi folks, Dan is right, and this approach is the best for us to minimize the overhead. There may however be some points of improvement to give the right visibility to users, and avoid the confusion of "things being visible on the website though not yet published as a release". not much details from my side on this for now, though... cheers, Arno 2016-06-07 0:50 GMT+02:00 hyouko at

The Hardware Compatibility List page on our website said to report any omissions in the list to this address. I bought a CyberPower UPS Model *LX1500GU*. It looks similar to the *CP1500AVRLCD*. My intention is to configure it in FreeNAS (FreeBSD). The FreeNAS user guide says it uses NUT to provide UPS support an contains a link to your website for a list of drivers of supported UPS devices. I

Anyone familiar with Cyberpower's model numbers? I finally got sick of my Tripplite's USB port going south, all the time, so I'm looking to replace it. The HCL has an entry for a Cyberpower model CP1500AVRLCD. Not listed is the CP1500PFCLCD model, a newer, premium version of the unit; but the HCL does have an entry for the CP1000PFCLCD model. Pretty sure that the CP1500PFCLCD

Hi, I am using a ALLNET 91500 UPS with blazer_usb driver /usr/lib/ups/driver/blazer_usb -a ups91500 -L Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (2.7.1) I have this settings: upsc ups91500 at localhost battery.charge: 100 battery.runtime: 12000 battery.voltage: 27.50 battery.voltage.high: 27.3 battery.voltage.low: 18.0 device.type: ups driver.flag.novendor: enabled driver.name:

Gene's posting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011654.html contains a NUT 2.7.4 update for the APC Smart-UPS_1500 device dump at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html Please note the changes since the 2.7.2 report, e.g. ups.delay.start is no longer supported. Roger

We only have a few open items that I think should be resolved before releasing 2.7.3. The list grew a bit in the past week, but we'll cover that later. Here is the list: * #93: Devices Dumps Library improvements <https://github.com/networkupstools/nut/issues/93> * #158: Powerware BCMXCP advanced features <https://github.com/networkupstools/nut/pull/158> * #185: insecure storage

Hi I have just purchased a Cyberpower CP1300EPFCLCD UPS. It is not listed in your Compatibility List http://networkupstools.org/stable-hcl.html I am very new to all this but do have a background in IT. I have been retired for 18 years so am a bit out of touch so please excuse if I am a bit fuzzy. I will try my best to explain my issue below. When I plug my UPS into my Synology NAS

Thank you for the commands... Please find attached log... Im not sure if the Load.on worked, because in the end I had to manually start the UPS (with button). Anyway, let me know should I need to perform some steps again (probably yes, since I believe it was off). Jakub On 11.03.2015 20:11, hyouko at gmail.com wrote: > 2015-03-11 14:21 GMT+01:00 Jakub Scepka <jakub.scepka at

Thanks! Now merged into master, it'll be in the upcoming 2.7.3. As icing on the cake, we'd appreciate a upsc/upsrw/upscmd dump for our own DDL: http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/ https://github.com/networkupstools/nut-ddl

> However, this was not an error I was expecting to see when rebuilding: > > http://buildbot.networkupstools.org/public/nut/builders/Debian-website/builds/55/steps/shell/logs/stdio > [...] > Makefile:796: *** target pattern contains no '%'. Stop. > > Any ideas? I think we don't support colons in names of files and dirs: -

> > > root at artu:~# upsc Elit at artu > > Init SSL without certificate database > > battery.voltage: 13.90 > > battery.voltage.high: -1.08 > > battery.voltage.low: -0.87 > > device.type: ups > > driver.name: blazer_usb > > driver.parameter.pollinterval: 2 > > driver.parameter.port: auto > > driver.version: 2.7.2 > >

Network UPS Tools version 2.7.3 has been released: http://www.networkupstools.org Direct access: - Download: http://www.networkupstools.org/source/2.7/nut-2.7.3.tar.gz - News: http://www.networkupstools.org/source/2.7/new-2.7.3.txt - ChangeLog: http://www.networkupstools.org/source/2.7/ChangeLog Please note that, with this release, the Device Dumps Library is now available online: