similar to: blazer_usb Shutdown

(please use reply-all - this list does not alter reply-to headers) On Sep 10, 2015, at 6:23 AM, Thomas Aichinger <taich at qpl.at> wrote: > > Hi, > > I am using a ALLNET 91500 UPS with blazer_usb driver > > /usr/lib/ups/driver/blazer_usb -a ups91500 -L > Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (2.7.1) [...] > I set delay.shutdown to 600 sec but UPS

Device manufacturer: Fideltronik INIGO Device name: Viper 1200 Device type: UPS Bus type: USB WWW: http://fideltronikinigo.com/viper/viper-1200/ " nut-scanner -U" output: [nutdev1] driver = "blazer_usb" port = "auto" vendorid = "0001" productid = "0000" product = "MEC0003" vendor =

Hello, I have a Salicru UPS in a Debian Wheezy connected with a USB HUB: # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ... Bus 001 Device 003: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial The problem is that I have some failed messages: # dmesg ... [90941.136274] usb 1-3.7: usbfs:

On Nov 25, 2013, at 4:56 PM, Fabio Cecamore wrote: > Hi all, > after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: > > [...] > [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 "ret

Hello, I am trying to make my UPS system working with NUT but with no success. I got "No supported UPS detected" message. I use the blazer_usb driver since it was proposed to me by the web site. My NUT version is : 2.7.1 (installed from standard RPM), release 2.41 The UPS identification: INFOSEC X4 RM PLUS linux-2qya:~ # /usr/lib/ups/driver/blazer_usb -a infosec Network UPS Tools -

Hello I am using Freenas 11.3 (freebsd like) with a GREENCELL usb ups. with nut 2.7.4_13 pre installed But, this ups is not detected as "blazer_usb" on port "auto" neither "ugen0.4"! Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4) No supported devices found. detail below. Another info : This

Hi, another UPS piece supported by blazer_usb: ALLSAI model LV 2K upsc output: battery.voltage: 82.08 battery.voltage.nominal: 72.0 beeper.status: enabled device.mfr: device.model: LV 2K device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.internal: 0.03 input.current.nominal: 18.0 input.frequency: 59.9

On Mar 7, 2014, at 4:12 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > Are the messages a problem? Or could I ignore? Since they aren't happening on each poll interval, they are not a big problem. The driver should recognize -110 as a timeout, and retry the query.

2014-03-08 14:26 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 7, 2014, at 4:12 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > >> Are the messages a problem? Or could I ignore? > > Since they aren't happening on each poll interval, they are not a big problem. The driver should recognize -110 as a timeout, and retry the query. Thanks for the

On Apr 3, 2015, at 1:54 PM, Humberto M?ckel <hamberthm at gmail.com> wrote: > I've successfully configured UPSMON to monitor the UPS status, and do the shutdown procedure by calling the SHUTDOWNCMD on a simple bat file I've made. This bat file is as follows: > > cd C:\Program Files (x86)\NUT\bin > blazer_usb -a HAMUPS -k > pause > > So this should send the

Hi all, after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: [...] [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [256789.640795] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8

Device web page http://www.samurai-power.com/samurai-smart-1000-lcd UPS is marked as Micropower LCD 1000, but in Slovenia is remarked as Samurai LCD 1000 [ups] driver = blazer_usb port = auto vendorid = 0001 productid = 0000 upsc ups Init SSL without certificate database battery.charge: 100 battery.voltage: 27.40 battery.voltage.high: 26.00 battery.voltage.low: 20.80 battery.voltage.nominal:

Hello, I've recently bought two cheap UPS (http://www.ldlc.com/fiche/PB00109242.html). They're not supported natively by NUT (even though the monitoring software is UPSilon from megatec). After some investigation, they almost use the krauler-type communication already supported in the blazer_usb driver. However, the UPS won't reply if the language ID is not 0x4095... Therefore, I

Lyonn CTB-1200 root at frambuesa:~# upsc lyonn at localhost battery.voltage: 27.20 battery.voltage.nominal: 24.0 beeper.status: enabled device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.internal: 0.03 input.current.nominal: 5.0 input.frequency: 49.9 input.frequency.nominal: 50 input.voltage: 213.3

Hi to all! Path send by Brian R. Smith with subject "[Nut-upsdev] Dynamix 650 VA USB - broken, have rough fix" really works! Tested with no-name UPS (works with UPSilon 2000 Windows software) and has USB vendorid=0001 productid=0000 Please, add it to the main branch of blazer_usb.c I belive that several users agree this.

I have Tecnoware EcoStrip 1100VA UPS which unfortunately uses Upsilon 2000 software. Their Linux software does not work but Windows version does so I made pcap file of the usb traffic with Wireshark available at http://www.dumbot.net/problems/EcoSrip1100VA.pcap I've read many posts on problems with these devices and tried all variations available with the blazer_usb driver without any luck.

Hi Charles >> Obviously the usb ports work good, I think is a bug in the driver or something like.. > Could be a cable problem, too. I'll try to change the USB cable but is hard to be fault, it's new.. > What version of NUT? We increased the timeout in 2.7.1. Network UPS Tools - Megatec/Q1 protocol USB driver 0.09 (2.6.5) > > Also, devices that talk to blazer_usb are

Hi everybody, following UPS is successfuly tested. Model: FSP Champ Tower 1k https://www.fsp-europe.com/CS/champ-tower-series-1k2k3k/ lsusb: Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial ups.conf: [powerpal]     driver = blazer_usb     port = /dev/hidraw0 Mode = standalone Distro = CentOS 8 What I did to get UPS communicate. In terminal run as root: ln -s

Hi, Thanks to some older discussions on this list I found it quite easy to eventually track down problem with using USB cable with some more of Megatec/Q1 UPSes. The trick (which is done in megatec_usb, but not in blazer_usb) is to read in the junk that somehow gets into read buffers before sending any commands. (I inserted debug statements so it's easy to see that the data read is really

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello 2All. Today I had purchased Ippon Smart Power Pro 1400 UPS for my home PC. It is a higher class device relative to Ippon Back Pro model line. It has one RS232 port and one USB port to connect the monitoring station to. UPS talks with megatec protocol, RS232 works as usual. USB connection is done through Cypress Semiconductor usb-to-serial chip