similar to: nutdrv_qx does not support UPS, blazer_ups does

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:

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

Use the name from ups.conf in front of "@localhost". ?The re?sult is quite different ;) root at artu:~# upsc Elit at artu Init SSL without certificate database Error: Driver not connected > What if you try nutdrv_qx without specifying megatec? (It should > autodetect.) > ?Here is the result: ? root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller

Hi I have the RCT 3KVA Axpert solar hybrid inverter. It is also known as the MPP Solar PIP-MS series, the IPS-4000WM and the Voltronic Axpert MKS. I am trying to monitor the inverter using NUT on a Raspberry Pi (I have tried Ubuntu as well with the same results). I have tried most of the drivers with no success. The inverter came with the ViewPower software so I assumed that my best chance

@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

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

2008/4/10, David Erosa <david.erosa at gmail.com>: > Public bug reported: > > Binary package hint: nut > > After updating to last nut package (2.2.1-2.1ubuntu6), the megatec_usb > driver seems to be working, except for the charge percentage: > > $ /lib/nut/megatec_usb -DDDDD -a SAI > ... > Checking device (0665/5161) (001/007) > - VendorID: 0665 >

Please keep the list CC'd, thanks. 2016-10-07 8:54 GMT+02:00 MATHIEU Clement <clement.mathieu at gmail.com>: > Hello > thanks for your answer > i?ve tried with nutdrv_qx driver > and i got this result > > lsusb : > > Bus 001 Device 058: ID 0665:5161 Cypress Semiconductor USB to Serial > Bus 001 Device 005: ID 13ee:0001 MosArt > Bus 001 Device 004: ID

> Hope this helps. It did - thanks! I managed to hack around a bit earlier and did produce the driver binary but thought I would try from fresh with your steps and got the binary. Unfortunately the problem is still there... after a while connection is lost, updates stop, and upsc reports stale data. Log attached. What I'm thinking now is that I should run a cron job that regularly

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

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

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!

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

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.

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

Hi all, just landed here so apologize. I've googled a lot but I can't find a way to get my UPS working with NUT. here my ( relevant ) details: lsusb ... ... Bus 001 Device 027: ID 0001:0000 Fry's Electronics ... ... lsusb -v -d 0001:0000 Bus 001 Device 027: ID 0001:0000 Fry's Electronics Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB

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 -

Hi Thank you very much for the feedback. I will download and try to get it working on the Raspberry Pi. Regards Tom On Sun, Feb 14, 2016 at 1:49 AM, hyouko at gmail.com <hyouko at gmail.com> wrote: > > I have the RCT 3KVA Axpert solar hybrid inverter. It is also known as > the > > MPP Solar PIP-MS series, the IPS-4000WM and the Voltronic Axpert MKS. I > am > >

hi! When I turn on my pc everything works fine, but if I restart fails (I'm not sure if this is true at 100%)?(then, i can do 'sudo /etc/init.d/nut restart' and it works) But what is certain is that sometimes when start up the pc it works and sometimes fails, can be a problem with the start time (i have a fast ssd) and the initialization of the driver and the usb port? thanks! syslog: