search for: blazer_ups

Hello All, I tested our new UPS yesterday. I noticed that while the blazer_ups drivers support this device, the newer nutdrv_qx does not. I suppose that this should not be the case, as nutdrv_qx will replace blazer_ups(?). Versions: I installed Nut on Ubuntu 13.10 (64 bit) from the standard package (2.6.4-2.3ubuntu2), and I also installed from the source tarball (2.7.1), int...

Hi Manuel et.al, Going thru the documentation -- it seems this configuration specific to blazer_ups. https://networkupstools.org/docs/man/blazer_usb.html Kind Regards, Yogesh On Fri, May 15, 2020 at 12:53 PM Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > On 5/15/20 12:13 PM, Yogesh Bhanu wrote: > > [...] > > # Is it possible to calculate /estimate how much t...

...from Ubuntu package "nut 2.6.3-1ubuntu1.1" - exact device name and related information: AtlantisLand Host Power 851 (A03-HP851 rev.1.1) - driver: blazer_usb I have no problems with the operation of NUT. My only problem is that I would like to change the behavior of the NUT driver "blazer_ups" when you turn off the system but I do not know how to do. Currently, when the electricity is missing, the system is automatically turned off, the load is disconnected for a few seconds and then reloaded when power returns. If you instead turn off the system normally (manually), the UPS remai...

On 5/19/20 10:39 AM, Yogesh Bhanu wrote: > Hi Manuel et.al, > > Going thru the documentation -- it seems this configuration specific > to blazer_ups. > https://networkupstools.org/docs/man/blazer_usb.html > > Kind Regards, Other drivrs support that option as well. Here is a quote from the same config as before: [guardian]         driver = nutdrv_qx         port = auto Did you actually test and it failed ? > Yogesh > >...

...Message transf?r? ---------- From: "Jackobs, Marco" <Jackobs at MACLE.DE> To: "nut-upsdev at lists.alioth.debian.org" <nut-upsdev at lists.alioth.debian.org > Cc: Date: Thu, 13 Dec 2012 15:37:17 +0000 Subject: [HCL] <Grafenthal> <ET-1000> supported by <blazer_ups> Hello,**** ** ** we?ve tested the Grafenthal ET-1000 with the blazer_usb driver on a the Nas4Free (FreeBSD) OS. It works!**** ** ** ** ** support-level**** *2* device-type**** * ups* for uninterruptible power supply**** manufacturer**** Grafenthal**** model****...

...;8-- Kind Regards, Yogi On Tue, May 19, 2020 at 12:12 PM Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > On 5/19/20 10:39 AM, Yogesh Bhanu wrote: > > Hi Manuel et.al, > > > > Going thru the documentation -- it seems this configuration specific > > to blazer_ups. > > https://networkupstools.org/docs/man/blazer_usb.html > > > > Kind Regards, > > Other drivrs support that option as well. Here is a quote from the same > config as before: > > [guardian] > driver = nutdrv_qx > port = auto > > Did yo...

Hello guys, Please help me to resolve the issue. I bought 'SVEN Power Pro+ 500 USB' UPS few days ago and tried to setup NUT 2.6.0 to work with it. blazer_ups driver doesn't recognize the UPS :( The Manufacturer provides 'PowerD' software for linux with installation instractions on a CD (see example below). --------===------- Welcom to PowerManager System! -----===----- Copyright(C) 2001 Richcomm Technologies, Inc. 2001.10 . +-+=====...

Hi, This is a newbie post so please bear with me. After loosing my router to a random Subminute outage. I looked around for a fanless UPS and bought Tripp Lite SMX1000LCD The above constellation works. But I have some questions about outputs. Please see attache nut report for the config. upsc output: --8<-- fourpi01:~# upsc tripp Init SSL without certificate database battery.charge: 100

...s *usually* not found, because early in my tests (i.e. soon after boot) it was actually discovered as a device on the USB bus, but with no details and unrecognized as a known UPS. Actually, I've tracked this down to the USB device nodes changing ownership from nobody:nobody to root:root during blazer_ups driver startup :\ I am so far at a loss as to "The why". Even weirder, sometimes the device links get gone as well, and this recovers them: # devfsadm -Cv devfsadm[5083]: verbose: symlink /dev/usb/6da.3/0/devstat -> ../../../../devices/pci at 0,0/pci103c,1609 at 12/input at 5:6da.3.d...

...ecause early in my tests > (i.e. soon after boot) it was actually discovered as a device on > the USB bus, but with no details and unrecognized as a known UPS. > > Actually, I've tracked this down to the USB device nodes changing > ownership from nobody:nobody to root:root during blazer_ups driver > startup :\ I am so far at a loss as to "The why". Even weirder, > sometimes the device links get gone as well, and this recovers them: > > # devfsadm -Cv > devfsadm[5083]: verbose: symlink /dev/usb/6da.3/0/devstat -> > ../../../../devices/pci at 0,0/pci103c,1...