similar to: Tecnoware Easy Power 1200 and blazer driver (was: Re: Suggestion)

Hi to everyone! I'm posting here after digging around the nut-upsuser and nut-upsdev mailing list, hoping I didn't miss something important. I'm trying to make my ups working with nut: it's a Tecnoware ERA LCD 0.85 which uses the so-hated UPSilon 2000 software to connect via usb. Personally I checked and seems that this junk software only works from windows, I'm trying to

Hello! I'm not a very happy owner of "Designed in Italy and manufactured in China" Tecnoware ECO LCD 650 UPS. Plan was to use it with FreeNAS 8 on HP Microserver... But this plan gone bad. I want to ask you to look at another "Megatec USB" protocol implementation. This UPS controlled by UPSilon 2000 program (Windows OS). Protocol type Mega(USB). Bad things: - Program does

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 -

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

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

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

Hi to all and happy new year! I'm writing here as I'm trying to get nut supporting the UPS in the subject; I didn't check well before buying and nowI discovered this is kinda bad hardware (it doesn't have a valid USB id, it just reports 0000:0001 and linux support doesn't really work as they stated), but before changing it I wanted to try to find a solution to get it work with

I'm running NUT 2.6.3 on Debian wheezy [ with a 3.3.0 i686 kernel ] I've installed NUT via Debian APT [ package nut version 2.6.3-1 ] I have a REDi Blazer 600VA (BLAZER600c) UPS and I want to detect power failures. I have tried the following drivers: * gamatronic: Can't talk to UPS on port /dev/ttyS1! * bestups: Unable to detect a Best/SOLA or Phoenix protocol UPS * blazer_ser: No

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

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

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

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

Cheers, One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 The gist of it is that "battery.voltage" and "battery.charge" were not always reported correctly with nutdrv-qx driver (might be handled better by blazer drivers though), and the overrides

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.

2010/10/13 Vitaly Lavrov > I found bug in nut/drivers/megatec.c - force shutdown may dont work. > See patch. > could you please give a try to blazer, since it is set to replace megatec with 2.6.0. Arjen will quite probably comment on your patch usefulness within the blazer scope. thanks for your contrib. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton -

Attached is a patch to hopefully improve the wording of some of the man pages. I will commit this in the next few days, but I wanted to give the driver authors a chance to comment. One thing that I feel is important is cross-referencing between the man pages. On the off-chance that someone does RTFM, it would be good if we make sure that a user doesn't have to read too far in order to find

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

Hi, They say one should never argue with people that know more than you, so please bear with me. On 2013/10/24 09:47 PM, hyouko at gmail.com wrote: > The driver is expecting either 'ACK' or no reply at all in case of > success and the command itself echoed back in case of errors. > On the other hand, your UPS replies '(ACK' in case of success and > '(NAK' on