similar to: Tecnoware ERA LCD (UPSilon 2000) communication problem

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 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 not a very happy owner of "Designed in Italy and manufactured in China" Tecnoware ECO LCD 650 UPS. Plan was to use it with FreeNAS 8 on HP Microserver... But this plan gone bad. I want to ask you to look at another "Megatec USB" protocol implementation. This UPS controlled by UPSilon 2000 program (Windows OS). Protocol type Mega(USB). Bad things: - Program does

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

@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

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!

> 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 Marcello, Marcello wrote: > a few days ago I bought a "Tecnoware Easy Power 1200" UPS for my little Linux > server, and in these days I haven't found nothing on the net apart the > "driver" for Linux (written in Java) on Tecnoware site (www.tecnoware.com<http://www.tecnoware.com> ). > So i tried NUT: while trying one by one all the possible supported

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

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

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

On Dec 17, 2011, at 3:53 AM, Arnaud Quette wrote: > Author: aquette > Date: Sat Dec 17 08:53:41 2011 > New Revision: 3363 > URL: http://trac.networkupstools.org/projects/nut/changeset/3363 > > Log: > Try to fix language ID support for USB units from LDLC, Dynamix and no names in blazer_usb (reworked patch, from Brian R. Smith and Aur?lien Grenotton) ... > + if

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, i've got similar problem with an OVISLINK 1000VA UPS on Debian. I've tried to connect with it using different drivers and this is what I get with each of them: [UPS] driver = blazer_usb vendorid = 0001 productid = 0000 port = auto subdriver = phoenix sweethome:~# /lib/nut/blazer_usb -a UPS -u root -DDD Network UPS Tools - Megatec/Q1 protocol USB driver 0.08 (2.6.4) 0.000000

Hi all, After some research I've found that this device should run with the blazer_usb driver. Jun 3 16:15:38 pegasus kernel: ugen0.4: <vendor 0x0001> at usbus0 Jun 3 16:15:38 pegasus kernel: uhid0: <vendor 0x0001 product 0x0000, class 0/0, rev 1.00/1.00, addr 4> on usbus0 However, even after shoehorning it; [crees at pegasus]/usr/local/libexec/nut% sudo ./blazer_usb -a zigor

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

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

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:

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

UPS: PowerWalker VFI 3000RT LCD CentOS 6.5, nut installed from RPM package: nut-2.6.5-2.el6.x86_64 nut-client-2.6.5-2.el6.x86_64 Driver: blazer_usb Problem description: USB device "loops" when starting blazer_usb. USB device permissions are ok. Receives some information. Error messages: "failed to claim USB device: could not claim interface 0: Device or resource busy"