similar to: multiple identical UPS on same server

[please keep the list CC'd. Thanks!] On Wed, Aug 13, 2014 at 9:33 AM, Marcello Vezzelli <mv at 3cx.com> wrote: > I noticed that 2 of Sweex UPS have an identical serial number 20100813, > which looks like a date. > The other one has an empty serial number. > > The blew one had the serial number, so I'm left with two different UPSes > from the serial number point of

On 13/08/2014 16:27, Charles Lepple wrote: >> The blew one had the serial number, so I'm left with two different UPSes >> from the serial number point of view. >> I wonder if an empty serial number is a valid serial number! > I haven't tried it, but an empty string (that is, iSerial is not zero, > but the string has length zero) should match the regex "".

On Thu, Aug 14, 2014 at 3:55 AM, Marcello Vezzelli <m.vezzelli at e-works.it> wrote: > I've found another strange issue that prevented me to test this solution. > VMware ESXi is filtering out serial number information, together with > iManufacturer and iProduct. Is it a permissions issue? The NUT udev configuration file changes the ownership and permissions to allow the NUT

On 14/08/2014 14:51, Charles Lepple wrote: > On Thu, Aug 14, 2014 at 3:55 AM, Marcello Vezzelli > <m.vezzelli at e-works.it> wrote: >> I've found another strange issue that prevented me to test this solution. >> VMware ESXi is filtering out serial number information, together with >> iManufacturer and iProduct. > Is it a permissions issue? The NUT udev

Hello, i try to setup NUT service to read/control my UPS but without success. Problem is when i try to start "/usr/local/ups/bin/upsdrvctl -DDDD -u root start" i got: /Network UPS Tools - UPS driver controller 2.6.2/ / 0.000000/ /If you're not a NUT core developer, chances are that you're told to enable debugging/ /to see why a driver

> Hello everyone. I try to connect four PowerMust 2000 ups's via usb to one > computer using megatec_usb driver. But megatec_usb completly ignores port > directive in ups.conf, I even try port = /dev/null and megatec_usb founds > ups and it works. The 'port' is not used for USB connected devices, it's only needed for compatibility reasons. > Problem is that

Hi Team, I've been experimenting with getting the PowerShield Defender 1200VA UPS working and it appears to be supported by the blazer_usb driver, although it did not have the correct permissions within udev to load the driver as the non-root user after an RPM install on Fedora Core 16. [root at localhost ~]# lsusb ... Bus 006 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial

Hi, Sometime ago [ June 2018 ] I posted a message about getting trying to get NUT to work with a Power Shield Defender 1200VA UPS. This model appears in the HCL at https://networkupstools.org/stable-hcl.html That UPS reported the following when queried using 'lsusb' on an iMac running macOS [ 10.15 ] Bus 001 Device 008: ID 0665:5161 Cypress Semiconductor USB to Serial Device Descriptor:

On Mon, Dec 2, 2013 at 2:25 PM, Charles Lepple <clepple at gmail.com> wrote: > > [Please subscribe to the mailing list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser ] > > On Nov 28, 2013, at 4:10 PM, Danijel ?ili wrote: > > > Since the provided drivers come with absolutely no installation instructions, I turned to NUT. > > > > The

Hi Charles, and thanks for your suggestion. I tried the nutdrv_qx and moved the rules file like you said, and re-attached the USB. It picked up to begin with, but within 10 minutes it lost the device again. $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.7.1 Network UPS Tools - Generic Q* USB/Serial driver 0.01 (2.7.1) USB communication driver 0.32 Using protocol: Megatec

Since the provided drivers come with absolutely no installation instructions, I turned to NUT. The compatibility list says "blazer_usb" should be used for PowerWalker's devices, so that's what I put in my conf: [pwvi] driver = blazer_usb port = auto desc = "PowerWalker VI 1500 LCD" Since I use Ubuntu Server 13.10 so I installed nut from apt.

@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

Hello, i have a server which supposed to control three Eaton UPS connected by USB cables. Each UPS is Eaton NV 2000H. (eaton_1, eaton_2, eaton_3) The connection is fine with each UPS, if it is configured alone. If i configure two or all three, the connections broke up. After nut started, tried to start upsdrv manually (eaton_1. The log: Apr 4 00:43:46 mail blazer_usb[10799]: Startup

[Please subscribe to the mailing list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser ] On Nov 28, 2013, at 4:10 PM, Danijel ?ili wrote: > Since the provided drivers come with absolutely no installation instructions, I turned to NUT. > > The compatibility list says "blazer_usb" should be used for PowerWalker's devices, so that's what I put in my

Hi Sergey, 2011/7/15 Sergey Talchuk <tals1975 at gmail.com> > Hi Arnaud, > > both configurations are ok :). Please find the file attached. > logic since the 2nd is automatically guessed from the first using USB Vendor and Product ID ;-) can you please send in upsc, upscmd and upsrw output. and also report the shutdown testing as described here:

Bonjour, Je souheterais utilis? la version qui permet le '-x generic',mais je ne sais pas ou la recuperer car ca devrait solutionner mon probleme (cf mail ci-dessous) DaneZ _____ From: DaneZ [mailto:david.guillotte@danez.no-ip.org] To: arnaud.quette@mgeups.com Sent: Sat, 08 Jul 2006 23:24:06 +0200 Subject: Fw: INFOSEC 500 XP en USB _____ Bonjour Arnaud, Je me

On Jan 2, 2012, at 10:51 AM, Vladimir Micovic wrote: >> Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial > Unfortunately, this device ID is used by several different vendors. What does "lsusb -vvv -d 0665:5161" show? > Also, what OS and kernel are you using? (I thought certain kernels had USB-to-serial drivers for that chip.) > -- > Charles

Hello, Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be supported. 1. I tried blazer_usb and usbhid-ups. Any other suggestions? 2. What would be needed to get it supported by NUT? ======== HW ======== HP Microserver Gen 8 ======== UPS ======== Working:Kstar Micropower Micro

# /lib/nut/megatec_usb -a myups Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] No supported devices found. Please check your device availability with 'lsusb' and make sure you have an up-to-date version of NUT. If this does not help, try running the driver with

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