similar to: Sven Power Pro 1000+

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.

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!

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

Hi all! Maybe possible adds something in megatec_usb driver for normal working with ippon 2000? This is output for drivers megatec_usb and blazer_usb: =========================================================== gate# /usr/local/libexec/nut/megatec_usb -DDDD -a IPPON Network UPS Tools - Megatec protocol driver 1.6 (2.4.1) Serial-over-USB transport layer 0.10 debug level is '4' Checking

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.

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'm running blazer_usb on my home orvaldi ups and i'm observing in dmesg one, two or three segafults of blazer_usb per day and notifications about broken/re-established communication like this: blazer_usb[2985]: Communications with UPS lost: status read failed! blazer_usb[2985]: Communications with UPS re-established today i've started ups service again with attached (c)gdb

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, 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

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

mmh.. I looked quickly at the logs: - from time to time some character is swapped with something other (just like in the 'F' reply of your previous logs), but this shouldn't be a big problem; - then, suddenly, the queries timeout (just like when you relaunch the driver after a stale) - this is the problem. We need to make sure this isn't something vm-related (if so, having almost

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

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

Hi Charles, I am done with few things: I made the cable - looks good, because I see some activities. I upgraded NUT to 2.7.3. but I have no success to start driver(this are the outputs) nut.cfg MODE = netserver ups.conf [infosec] driver = nutdrv_qx (or blazer_ser) port = /dev/ttyS1 desc = "XP Pro 2500 RM" output(nutdrv_qx cmd upsdrvctl -DDD start) Network UPS

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

> 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

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

@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

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

Hello, I am new to UPS stuff, please be patient with me ;-) Archlinux i686, kernel 3.0-ARCH #1 SMP PREEMPT. nut 2.6.1 installed from source via Arch's AUR repository. Mother board GA D525TUD with two serial ports, both enabled in BIOS. I got some old Orvaldi 520 PL UPS [1], which is supposed to be supported by the vendor [2] with sw called UPSmart. The statically compiled i386 binary ran