similar to: Can't get iDowell to work

Hi Recently i bought a MicroDoWell BP50, and with it followed a USB 2 serial converter. When i plug it into my 2.6.19 kernel, dmesg shows hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:04.2-2 usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver So, i figured i should use usbhid-ups,

Hi All, I'm using an iDowell UPS with the usbhid-ups driver: $ upsc iDowell at localhost battery.charge: 100 battery.charge.low: 15 battery.runtime: 650 battery.type: Pb acc device.mfr: iDowell device.model: iBox device.serial: 00000001 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto

Thanks Charles, On Saturday 05 Apr 2014 12:53:06 Charles Lepple wrote: > On Apr 5, 2014, at 7:18 AM, Mick wrote: > > $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost > > Username (suzy): admin > > Password: > > OK > > This command is sending the value to the UPS (via the usbhid-ups driver). > > > $ upsc iDowell at localhost

Hello There, I tried your advice and i don't think it works either, See the logs, " /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... Network UPS Tools - Generic HID driver 0.52 (2.8.0-2557-g81fca30b2) USB communication driver (libusb 1.0) 0.46 ?? 0.000000??? [D3] main_arg: var='port' val='auto' ??

<facepalm ;)> the ellispis "something=..." were supposed to be replaced by your device ID numbers, etc. On Sat, Sep 23, 2023, 18:26 FatGear <fatgear1 at free.fr> wrote: > Hello There, > > I tried your advice and i don't think it works either, > > See the logs, > > " > > /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x

Hello All I have a MicroDowell ups (BBox BP 1000) connected to a Gentoo box by serial cable. If I try to start the driver , I see the following : Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. debug level is '13' ups_sync: send [\rP4\r] ups_sync: got ret 46 [#1000VA

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

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

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

BTW, I did a run with a higher debug level that resulted with this... > [root at cornelius ups]# powerpanel -a office -D -D -D -D -D -D -D -D > Network UPS Tools - CyberPower text/binary protocol UPS driver 0.25 (2.6.5) > Warning: This is an experimental driver. > Some features may not function correctly. > > 0.000000 debug level is '8' > 0.011347

@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

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

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 -

I've just committed a rough version of the idowell-hid subdriver to the trunk. It is already integrated in the usbhid-ups, but I lack the time to complete the NUT to HID mapping in it. The following message on the nut-upsuser mailinglist should provide enough clues to add most of them: http://lists.alioth.debian.org/pipermail/nut-upsuser/2011-January/006506.html I would be

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 First things first, thanks for great work with NUT. For years I used Informer compact 3kVA UPS http://www.informups.com/informer_compact.html with nut/megatec serial driver, but it stopped working when I switched to blazer_ser with 2.6.0 upgrade. I'm using 2.6.0 on gentoo. Blazer_ser seems to connect with UPS, but upsmon reports driver not connected. uname -a Linux localhost

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:

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

Hello all, long time away from this list, glad to be around again! I have this Powercom Vanguard VGN VGD-20K31. Some details of this model: * 3-phase input, single phase output * Model has 240V / 12V9AH x 20 x 2SET, plus another set of 20 batteries. All in all, 3 sets * Serial connection to Windows 2k3 server with UPSMon Now I was strongly considering replacing the bundled no-good upsmoon

Hey all, Finally got around to hooking up my Powercom BNT-1500AP to nut. It's the old serial interface. Connects okay and gets most information, but a couple of data are way off. Any config recommendations or upgrade recommended? I've played with config a little, but no hits yet. Details: NUT version 2.4.3 ups.conf: [ups] driver = powercom port = /dev/ttyS0