similar to: Problem with nut 2.4.1 & Ippon 2000 Smart power on FreeBSD

Hi all! I have a ups Ippon smart power pro 2000. And it connects to my FreeBSD 7.2 x86 server throught usb. I'm try to setup it in nut with megatec_usb driver... But it is not recognizes ups. I'm try set productid and vendorid in ups.conf, but this is not help. Nut version 2.4.1 below i'm add output of lsusb, my ups.conf and /usr/local/libexec/nut/megatec_usb -a IPPON -DDD

Hello all, I am trying to set up my brother's UPS (remotely over internet) on an OpenIndiana-based storage box. According to him, the UPS is probably an Ippon Back Power Pro 600 dated around 2003 (battery recently replaced), and it has an USB connection. Sorry for a relatively long post with a log of my successes and failures, in the hopes that someone would point out what I did wrong.

Hello i need your help regarding the following issue : i have a hero touch ups from infosec. it is connected via USB to a raspberry pi 3. i?ve configure ups.conf file as below [HERO] driver = blazer_usb vendorid = 0665 productid = 5161 either with port = auto or port = /dev/hidraw0 or port = /dev/ttySo the connection never works i get the

System: Cenots Linux 6.9 Application: nut-2.7.5-0.20170613gitb1314c6 [with usb 0.1 from distro] Device: Mustek PowerMust 1060 LCD Comunication log file: dump.txt We are looking at the possibility of successful communicating with this device UPS Mustek PowerMust 1060 LCD. PS: wolfy on the list gives me assistance and i can install any new compiled nut version from sources. Thanks, Catalin.

Greetings Gentlemen, I have Mustek NetGuard 1000 UPS which is equivalent to Ippon SmartWinner 1000. I have tried to run several latest builds of NUT, but run megatec_usb driver still failed with my device. I hope the information below might help. Regards, Oleg Here is the information which may help: lsusb -v Bus 002 Device 002: ID 06da:0003 Phoenixtec Power Co., Ltd Device Descriptor:

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

Hi, i recently bought an UPS from Integra Tech (http://www.integra-ups.com/eu/es/main.htm), the ePlus 450-850va model (http://www.integra-ups.com/eu/es/eplus1.htm), sorry i didn't find it in english, and i'd like to know if there will be support on this brand and model. When i reconnect it, i get this: [739610.568073] usb 1-1: USB disconnect, address 2

On 11/9/2013 5:24 AM, Jim Klimov wrote: > Hello all, > > I am trying to set up my brother's UPS (remotely over internet) > on an OpenIndiana-based storage box. According to him, the UPS is > probably an Ippon Back Power Pro 600 dated around 2003 (battery > recently replaced), and it has an USB connection. > > Sorry for a relatively long post with a log of my successes

Hi all, can anybody sugggest a proper solution to the problem described here: http://nut-upsuser.alioth.debian.narkive.com/wIMnftV0/installing-nut-for- powerwalker-vi-1500-lcd Righet now I am trying to make it go and running on version: root at raspberrypi:/home/pi/deb# apt-cache policy nut nut: Installed: 2.7.2-4 Candidate: 2.7.2-4 Version table: *** 2.7.2-4 0 500

Hello! I can't get my UPS to get detected. I have tried to search the internet for several hours. I have a Mustek Powermust 1400 USB that has both a USB and serial port. OS: openSUSE 20151209 (x86_64) VERSION = 20151209 CODENAME = Tumbleweed Kernel: 4.2.1-1-desktop Nut: nut-2.7.3-1.5.x86_64 installed with zypper dmesg |grep usb [94414.680765] usb 1-1.1: new low-speed USB device number 4

@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'm not the maintainter for the "megatec_usb" driver (in fact, I'm no longer maintainer for the base "megatec" either), so I don't really know the status for that particular UPS. I'm forwarding this to the NUT mailing-list though. Regards, -- Carlos Rodrigues On Fri, Dec 5, 2008 at 10:30 AM, Adrian Czerniak <adrian.czerniak at becomo.com> wrote:

Hi, I'm not the maintainter for the "megatec_usb" driver (in fact, I'm no longer maintainer for the base "megatec" either), so I don't really know the status for that particular UPS. I'm forwarding this to the NUT mailing-list though. Regards, -- Carlos Rodrigues On Fri, Dec 5, 2008 at 10:30 AM, Adrian Czerniak <adrian.czerniak at becomo.com> wrote:

Hello. I've been experimenting with the USB connection of an Ippon BackComfoPro 800. This is the device "06da:0003 Phoenixtec Power Co., Ltd". The current SVN version of NUT does not work with this device. The megatec_usb driver can't get a proper reply to a Q1 request, failing with an error message about "short read (14 bytes)" instead. I have found the reason for

Hi. My Belkin UPS F6C1100-UNV works fine with megatec_usb version 1.6 (2.4.1). However, it doesn't work with 2.4.2 nor 2.4.3. # /lib/nut/megatec_usb_old -D -a belkin Network UPS Tools - Megatec protocol driver 1.6 (2.4.1) Serial-over-USB transport layer 0.10 debug level is '1' Starting UPS detection process... 0 out of 5 detection attempts failed (minimum failures: 2). Cancelling

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, windows10pro version 1511 os build 10586.29 nut 2.6.5-6 windows binary package device ups: poweron vs 950 when I do testing shutdown it does not shutdown. Thank's. driver debug output: C:\Program Files (x86)\NUT\bin>blazer_usb -DD -a myups Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (Windows-v2.6.5-5-7-g72f380c) 0.000000 debug level is '2' 0.000000

On 10/30/2017 03:19 PM, Alexa Catalin wrote: > System: Cenots Linux 6.9 > Application: nut-2.7.5-0.20170613gitb1314c6? [with usb 0.1 from distro] > Device:??Mustek PowerMust 1060 LCD > Comunication log file: dump.txt > > We are looking at the possibility of successful communicating with > this device UPS?Mustek PowerMust 1060 LCD. > > PS: wolfy on the list gives me

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.