search for: blazer_s

Daniele, Thanks again for your work on both the voltronic and blzr drivers. To get the most exposure to new drivers, what we have typically done in the past is to rename the existing driver as *-old, so that users get the new driver by default when they upgrade (but the old driver is still available if there are regressions). This is how we are incorporating Michal's apcsmart updates. On

On Nov 1, 2013, at 9:03 AM, Charles Lepple wrote: > But if blzr supersedes both voltronic and blazer, I propose we rename blazer_{ser,usb} to blazer_{ser,usb}_old, then rename blzr* to blazer*, and revert the voltronic merge. Dan, The pull request against master looks good - thanks! What do you think about the renaming of blazer to blazer_old, and making blzr the new blazer driver? I still

On Jan 2, 2015, at 1:07 PM, Mike Raath <raathm at gmail.com> wrote: > I built a single VM to monitor the UPS (Ubuntu Server 14.04 i386) and installed NUT on the box from the apt packages. I set it up as per the previous box with the blazer_usb driver and all goes well, for a while. Initially, the UPS reports correctly via upsc, but after a while I get the "Data stale" error,

A couple of years ago, Arnaud helped me get my Apollo Line Interactive UPS working, using the blazer_usb driver. Now I've run into another problem, having rebuilt my HP Proliant Microserver into an ESXi 5.5 managed hypervisor with various VMs. One of the VMs is a FreeNAS server which manages the storage for the other VMs so graceful shutdowns are important. I built a single VM to monitor the

Hi, thanks for the reply. On 2014-05-29 05:21, Charles Lepple wrote: >> Now my questions: >> 1. should the blazer_ser's high voltage be the voltage during charging >> or right after I've unplugged it from the mains? > sounds like during charging (or more accurately, during float charging at the end of the cycle): > > http://www.networkupstools.org/docs/man/blazer.html#_extra_arguments Are...

In my opinion, there might be just one problem: the blzr driver doesn't provide anymore two splitted drivers (serial and usb), so this isn't going to be a 'silent update' for those using these drivers (should we provide symlinks or the like?). If this doesn't sound like a problem to you, I'll take care of the rename. Plus, if you could take a look to the blazer-fix pull

As a follow up on my last message, where I talked about loss of USB communication with my Asium P700 UPS, I was thinking about some possible improvements.? 1.? When communications are lost, instead of shutting down immediately why not set a flag and then stop the driver and then restart the driver.? If communication is not re-established, and the flag was set, then shut down the system.? Perhaps

...tested it with my device. > That patch implements tcp connection in serial.c, this is a more > flexible approach, as it is applicable to all serial drivers. However > the drivers then make ioctl calls to setup the tty port, and these fail. > At least, this is what happens to me with blazer_ser. Maybe the patch > has not been finished? The patch is from several years ago, so it definitely hasn't been tested much. I don't know the original driver it was intended for. > In my patch tcp is implemented only for blazer, but it works and it was > simple for me to write it...

- OS name and version: Ubuntu 12.04 - exact NUT version: 2.6.3 - NUT installation method: from Ubuntu package "nut 2.6.3-1ubuntu1.1" - exact device name and related information: AtlantisLand Host Power 851 (A03-HP851 rev.1.1) - driver: blazer_usb I have no problems with the operation of NUT. My only problem is that I would like to change the behavior of the NUT driver

Not of a big help here, but I think it's a voltronic power vesta 650: http://www.voltronicpower.com/oCart2/index.php?route=product/product&path=37&product_id=52 If that is the case, it should work both with the blazer drivers (i.e. all but the shutdown sequence) and with the now defunct voltronic ones. With arno's words: "We are currently merging a new driver to replace

On Jun 2, 2014, at 12:25 PM, Andreas Lausch / TBT wrote: > > Hi, > > thanks for the reply. > > On 2014-05-29 05:21, Charles Lepple wrote: >>> Now my questions: >>> 1. should the blazer_ser's high voltage be the voltage during charging >>> or right after I've unplugged it from the mains? >> sounds like during charging (or more accurately, during float charging at the end of the cycle): >> >> http://www.networkupstools.org/docs/man/blazer.html#_ext...

On Nov 8, 2013, at 3:23 AM, Josu Lazkano wrote: > Hello, I have a Salicru SPS One 700VA device, I want to manage it with > Debian Whezzy. > > I read some information in the net about how to configure but I can > not get it working. I'm assuming you mean this blog post? http://blog.ciberterminal.net/2013/04/28/ups-salicru-en-nut/ > Could you help with this? > >

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

[please keep the discussion on the nut-upsdev list. thanks!] On Jan 30, 2014, at 10:20 AM, Jos? Sosa wrote: > Dear Mr. Lepple > > I am Leonardo Sosa and I am watching this issue with Rodolfo and Ronaldo. (in copy) > > See below our answers of your questions. > > What should I do now in order to include our code sgs_command in your code blazer_usb.c? As I mentioned to

Hello, I have a Salicru SPS One 700VA device, I want to manage it with Debian Whezzy. I read some information in the net about how to configure but I can not get it working. Could you help with this? This is the log when I connect the USB: [ 3194.688204] usb 4-4: new low-speed USB device number 2 using ohci_hcd [ 3194.857239] usb 4-4: New USB device found, idVendor=0665, idProduct=5161 [

Hi Users NUT, I want monitor a UPS of brand SMS (Sinus Double 8 KVA) using a raspberry-pi. In compatibility list, is listed to use the blazer_ser driver. I use a USB adapter to RS-232 conected in to the No-Breake. Follow the comands e confs. root at rasp:/home/pi# lsusb *Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Ad...

On Oct 25, 2016, at 8:08 PM, Michael Evans wrote: > > It seems that the UPS I bought is actually served by the blazer_usb driver. > > USB ids 06da:0003 (lsusb DB thinks it's a "Phoenixtec Power Co., Ltd 1300VA UPS", but this has apparantly been re-used by Eaton 5E2200USB-LA) > > It's sold as an Eaton 5E 1,100W 2,200VA 6-Outlet UPS > > SKU: 147140 Mfr

I recently purchased a UPS from http://www.microcenter.com/product/470131/5E_1,100W_2,200VA_6-Outlet_UPS It's sold as an Eaton 5E 1,100W 2,200VA 6-Outlet UPS SKU: 147140 Mfr Part #: 5E2200USB-LA UPC: 743172064875 "The Eaton 5E is an essential line interactive UPS that provides cost effective and reliable power protection against power outages and bad power quality. Thanks to its small

...0.045788 - Product: 87XXUPS 0.045841 - Serial Number: unknown 0.045899 - Bus: /dev/usb 0.045951 Trying to match device 0.046011 Device matches 0.046187 Trying megatec protocol... 0.049547 send: Q1 0.101572 read: (217.0 2 0.101674 blazer_status: short reply 0.101733 Status read 1 failed 1.266722 send: I/O error 1.266900 blazer_status: short reply 1.266956 Status read 2 failed 1.267648 Checking device (06DA/0003) (/dev/usb/6da.3/0) 1.271661 - VendorID: 06da 1.271763 - ProductID:...