similar to: Driver for a REDi Blazer 600VA UPS

The REDi Blazer 600VA (BLAZER600c) UPS found here [ro_RO]: http://www.emag.ro/ups-redi-blazer-600va-blazer600c/pd/EX5X2BBBM/ which is actually a Centralion Blazer 600VA [en_TW]: http://www.centralion.com/html/product/back-Product-ups-blazer400.htm works with the blazer_ser driver ----------shell output---------- # upsrw ups # upscmd -l ups Instant commands supported on UPS [ups]: beeper.toggle -

-----BEGIN PGP SIGNED MESSAGE----- Hello, I leave a mail here because I can't find any solution in order to get the nut working with this UPS despite I search everywhere on the net. I've bought this UPS recently after that an MGE-UPS Ellipse 1200 USB burn. I've those information about the UPS : Reseller link : http://www.alpha-power-technologie.com/images/GPi-usb.pdf In his

-----BEGIN PGP SIGNED MESSAGE----- Hello, I leave a mail here because I can't find any solution in order to get the nut working with this UPS despite I search everywhere on the net. I've bought this UPS recently after that an MGE-UPS Ellipse 1200 USB burn. I've those information about the UPS : Reseller link : http://www.alpha-power-technologie.com/images/GPi-usb.pdf In his

Hi, I've being using nut 2.2.2 (Debian Lenny) via megatec_usb driver for IPPON Back UPS 600. Then I upgraded to nut 2.4.3 (Debian Squeeze) with broken megatec_usb. I moved to blazer_usb, it connected IPPON. [myups] driver = blazer_usb port = /dev/usb/hiddev0 desc = "Local UPS" #from megatec.c: batteries[] = {{ 12.0, 9.0, 16.0, 9.7, 13.7, 0.0 },

Hi again, I've succeeded in compiling the svn trunk with the automake tools and wish to say thank you to Charles Lepple for his help. After fixing some parameters in the hotplug script I can now get access to the UPS on /dev/usb/hiddev0 (I added productid and vendorid of my ups to the usermap). I've decided to try the newhidups driver with -x generic parameter and got this response :

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:

Ok Guillaume, It is Megatec protocol. It sends Q1<cr> and answers with (227.2 227.2 227.2 038 50.1 13.5 25.0 00001001<cr> And if you check http://eu1.networkupstools.org/protocols/megatec.html it matches. And now, ho has time to code ? Kjell fre 2006-04-21 klockan 17:18 +0200 skrev Guillaume JAOUEN: > Hello, > > As I wish to help you the most I can in order to get a

Why this code doesn''t work as expected? It raises exceptions everytime. Tried with || operator, too. validates_each :x, :y do |record, attr| record.errors.add (attr, ''between 1 and 100'') if (attr.to_i>100 or attr.to_i<0) end -- They say money can''t buy happiness? Look at the smile on my face... ear to ear, baby!

Hi, a few days ago, I bought some of those Mustek UPSes that have both a serial and a USB connector. Currently only the serial port is supported by the megatec driver. This works fine so far. Now I have seen there is a megatec_usb driver, which currently only supports 2 other UPSes. How can I help to find out whether the PowerMust might actually work with the megatec_usb driver? -- Regards,

An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20090120/ffb91e55/attachment.htm

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

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

Hi Marcello, Marcello wrote: > a few days ago I bought a "Tecnoware Easy Power 1200" UPS for my little Linux > server, and in these days I haven't found nothing on the net apart the > "driver" for Linux (written in Java) on Tecnoware site (www.tecnoware.com<http://www.tecnoware.com> ). > So i tried NUT: while trying one by one all the possible supported

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

On Apr 6, 2014, at 8:43 AM, alezz wrote: > Hi Charles, > Thanks for reply. > I've took a look at the code you suggested me and 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

Hi all, Arjen can you enlighten me about the function of the blazer upsdrv_shutdown function. I think they are in the wrong order. Regards Kjell

ok, I'll try to sum up the thread and answers to the various point: 2005/10/24, Peter Selinger <selinger@mathstat.dal.ca>: > > Arnaud Quette wrote: > ... > > Any perl (or other well supported scripting) monger out there to take > over > > that one? > > Great idea. How about bash/sh? Still the most universally available > scripting language. I am

My UPS has an LCD that says the battery is 100% and the estimated run time is 12min. The uspc has similar results. The problem is when line power is lost the UPS batter goes to 0% very quickly (seconds). It charged to 85% when power was restored. 86-100% is slower. I did: $ upscmd desktop_ups test.battery.start.deep Username (admin): Password: OK Now the ups.test.result says there is a

Arnaud Quette wrote: > Anyhow, I would more see this as a merge of all these drivers, with > some autodetection or flag/param to switch the mfr/model and maybe > capabilities... Whatever the driver name is, a good thing would be the > name of the protocol or something generic enough, though powermust is > fine. Ok, I made some minor changes to powermust, to make it less

I have the classic case of: Posts, and Categories. When the user submits a post, he has a drop-down list of categories. I want to put a "Add category" link next to the list of categories. This is already inside a form, so a "link_to_remote" that creates a small AJAX form inside the "submit post" form will not work because that will mean to embed a form in another