similar to: blazer_usb for SVEN Power Pro+ 500 USB

Hi to all and happy new year! I'm writing here as I'm trying to get nut supporting the UPS in the subject; I didn't check well before buying and nowI discovered this is kinda bad hardware (it doesn't have a valid USB id, it just reports 0000:0001 and linux support doesn't really work as they stated), but before changing it I wanted to try to find a solution to get it work with

Hi to everyone! I'm posting here after digging around the nut-upsuser and nut-upsdev mailing list, hoping I didn't miss something important. I'm trying to make my ups working with nut: it's a Tecnoware ERA LCD 0.85 which uses the so-hated UPSilon 2000 software to connect via usb. Personally I checked and seems that this junk software only works from windows, I'm trying to

@fsp Please forward to development, manufacturing and quality management department: Model EP1000(PPF6000/100), 431107300095, 4711140480534, Art-Nr. 8296861, 70539, 14Z00000, 35-0200116-01G @nut-users http://www.networkupstools.org/ 2.4.3 debian stable, 2.6.2 upstream, linux 2.6.38-debian-bpo # /usr/local/src/nut-2.6.2/drivers/blazer_usb -u root -DDDDD -a ups Network UPS Tools - Megatec/Q1

> We need to make sure this isn't something vm-related I suspect that this is definitely vm related now. I've tried Ubuntu server 10.10 as you suggested, and also Debian wheezy and both do the same thing. I saw in another thread that the author of the .vib of nut for ESXi is on this mailer - hopefully he can shed some light on what's happening. I would even be happy if I can

Hi I Bought a cheap Plexus 800VA UPS from ebuyer : http://www.ebuyer.com/product/240319 to use with my Netgear ReadyNAS duo. Initial version of NUT was very old and NAS didn't detect it although in the NAS log it said "UPS Disconnected". Syslog did send the following : Jan 25 12:46:36 nas-27lfc kernel: usb 1-1: new low speed USB device using uhci_hcd and address 2 Jan 25 12:46:37

No progress has been made: cable is UPS - PC 6 - 3 7 - 5 9 - 2 for ./blazer_ser -DDDDD -a infosec 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1" 0.000323 debug level is '5' 0.103068 send_to_all: SETINFO device.type "ups" 0.103104 send_to_all: SETINFO driver.version "2.7.3" 0.103118 send_to_all: SETINFO

Hi all, I've bought UPS FSP EP 850 because I have similar UPS, FSP EP 1000. It is working on my other server with with Fedora 14, kernel 2.6.35.14-106.fc14.x86_64 and installed nut-2.6.2-1. My new UPS is detected by kernel (see below lsusb output) and is partially detected by blazer_usb driver also. But it doesn't communicate with driver (see below blazer_usb output). I run all

Hello, I have a UPS branded as "Energit MXE II" that comes with the infamous Winpower software (as already discussed in this old thread <http://nut-upsdev.alioth.debian.narkive.com/m0FWk43o/blazer-usb-compatibility-with-ippon-backpro-upses-phoenix-power-co-ltd-usb-to-serial-controller>). This same UPS appears to be sold as "Centralion Titan Elite" and maybe other names

Hi Arnaud and NUT team You may recall some time ago, I and a few others posted questions about the above referenced (cheap and cheerful) USB-based UPS - specifically regarding FreeBSD USB support in NUT. The original posting was entitled "Zigor Ebro 650 compatibility". I've since tried the latest Windows port of NUT with my WinXP laptop connected to the Zigor Ebro and finally

Hello! I'm trying to use nut with a Ippon Smart Winner 3000 UPS (http://shop.key.ru/photo/items/45535.jpg) which looks like a custom-labeled OEM model of the megatec branch. I tried both the megatec_usb and the blazer_usb drivers for it, with a obvious config section: [ippon] driver = blazer_usb port = auto vendorid = 06da productid = 0003 desc = "Ippon Smart Winner 3000" If I

Merry Christmas to you all and best wishes! I ran into exactly the same problem as described. OS: FreeBSD 9.0-Rel UPS: Eaton E-Series NV 600H NUT: from Ports, nut-2.6.5_1 driver: blazer_usb I am sure the problem is not permission-related as it occurs even when the driver runs as root. My tested recipe for USB permissions is: 1. run usbconfig to find where the device is connected. In my case:

I'm running Ubuntu 14.04.1 with nut 2.7.1-1ubuntu1, using a Powerwalker/INNO TECH ups. It used to working fine, but lately blazer_usb just executes a few commands and then terminates with a "Got disconnected by another driver" message. Any suggestions? Example output from blazer_usb with loads of debug: # /lib/nut/blazer_usb -DDDDDDDDDDDDDDDDDDDDDD -a nasups Network UPS Tools -

On Nov 20, 2015, at 12:17 PM, R?bert SZAKSZ <robert at szaksz.eu> wrote: > > No progress has been made: > > cable is UPS - PC > 6 - 3 > 7 - 5 > 9 - 2 > Maybe pins 4 and 7 (ground) both need to be connected on the UPS side? > for ./blazer_ser -DDDDD -a infosec > 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1" > 0.000323

Hi, I have used the truss command as directed. I have attached both the driver output and the last few sections of truss output leading to the hang. Both outputs end at the CTRL+C i pressed when i was forced to end the processes. Hope this is helpful. Please bear with me if i didn't run it with the right options etc - as I mentioned, I'm a little new to Solaris. Regards, Richard On

It seems like it works (partially?) with NUT/driver you mentioned. I will test it more when I return home. root at Failure:/lib/nut# ./nutdrv_qx -a test -x subdriver=fuji -u root -x productid=0000 -x vendorid=0001 -DDDDDD Network UPS Tools - Generic Q* USB/Serial driver 0.13 (2.7.2.5) USB communication driver 0.32 0.000000 debug level is '6' 0.001247 upsdrv_initups...

On 10/08/2012 21:58, nut-upsuser-request at lists.alioth.debian.org wrote: >>> Arnaud Quette<aquette.dev<at> gmail.com> writes: >>>> 2012/6/3 Chris Rees<crees<at> freebsd.org>: >>>>> Hi all, >>>> Hi Chris, >>>> >>>>> After some research I've found that this device should run with the

Hello. I recently upgraded from Ubuntu Maverick to Natty and hence upgraded nut from 2.4.3-1ubuntu5 to 2.6.0-1ubuntu3. My Sven PowerPro+ 1000 UPS ( http://en.sven.ru/catalog/ups/power_pro_plus_1000.htm ) worked fine with the previous version, using megatec_usb driver, but doesn't work with the current version, since megatec_usb is no longer available. Here is the output from blazer_usb.

Hello, I have just installed nut_2.6.0 from Debian testing, do anyone know the correct driver for this ups? The blazer_usb don't report battery-charge, the bundled software report charge and runtime. root at pluto<~>upsc powerwalker battery.voltage: 40.86 battery.voltage.nominal: 36.0 beeper.status: enabled device.mfr: device.model: HV 1K device.type: ups driver.name: blazer_usb

cmd test.battery.start.deep was not tested yet. cmd test.battery.start.quick works as expected. cmd test.battery.start 120 works as expected. cmd test.battery.stop works as expected. cmd beeper.toggle works as expected. cmd shutdown.return works as expected. cmd shutdown.reboot does not work entirely. After a minute, UPS is shut down but didn't come back. (Issuing shutdown.stop power up it

> > hmm, apparently the UPS doesn't close the replies to our queries with > the expected CR and we (I) did not consider that case in nutdrv_qx -- > noted: > https://github.com/networkupstools/nut/issues/441 > > But blazer_usb, being less strict on the terminating CR of Q1 replies, > should work with your device. > > > root at artu:~# upsc Elit at artu > >