similar to: megatec and blazer drivers for (brand)Tuncmatik (series)Newtech Pro 1KVA

Displaying 20 results from an estimated 300 matches similar to: "megatec and blazer drivers for (brand)Tuncmatik (series)Newtech Pro 1KVA"

2011 Mar 15
0
FW: [newtech-1] Uncovering Spoken Phrases in Encrypted Voice over IP Conversations
Thought this might interest a few people on the asterisk list as well Cheers, Dean ________________________________ From: Dean Collins Sent: Tuesday, March 15, 2011 1:49 PM To: 'newtech-1 at meetup.com' Subject: RE: [newtech-1] Uncovering Spoken Phrases in Encrypted Voice over IP Conversations Wow, of course how stupid, when someone says hello at the start of the call
2008 Apr 02
1
FW: [newtech-1] Skype 24 Hour Rolling Analytics
While not asterisk specific related - would be interesting to see something similar done against straight voip calls. You could maybe plot it against e.164.org polls but I think this would be too small a sample set. Can anyone think of something else Asterisk related we could plot this against? Cheers, Dean http://deancollinsblog.blogspot.com/2008/04/skype-24-hour-rolling-analyt ics.html
2013 Apr 02
3
blazer driver: Possible bugs with battery packs
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
2008 Jul 01
8
megatec process die
An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20080701/3140c7d2/attachment.htm
2015 Mar 13
2
(no subject)
Hello, I had running OpenMediaVault server with NUT 2.4.3 megatec_usb driver. After the OMV upgrade, NUT also upgraded to 2.6.4. I realised that megatec_usb removed in this version. So I have configured to use blazer_usb driver. However NUT behaves incorrectly after switching blazer_usb. System is being halted upon booted up. Is it possible to use megatec_usb driver in the new version? # NUT
2013 Apr 22
0
Fwd: Not receiving real data from a Eaton E series DX 1000H UPS
On 18.4.2013 ?. 22:24 ?., Arnaud Quette wrote: > > 2013/4/18 Pladi Computers Ltd. <pladi at lovechnet.com > <mailto:pladi at lovechnet.com>> > > UPS: > http://www.eaton.com/Eaton/ESeriesUPS/DXUPS/index.htm?wtredirect=www.eaton.com/DXUPS > > I have the same problem on two different computers. The first one > is running Ubuntu 12.10 i386 , the
2010 Dec 30
1
Blazer upsdrv_shutdown function
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
2011 Apr 12
1
blazer & megatec drivers
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 },
2013 Nov 06
0
Merging blzr as blazer (and un-merging voltronic?)
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
2013 Nov 06
1
Merging blzr as blazer (and un-merging voltronic?)
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
2014 Apr 12
0
[nut] blazer_soi: blazer driver, serial port over tcp/ip (#116)
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
2005 Sep 23
1
Tecnoware Easy Power 1200 and blazer driver (was: Re: Suggestion)
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
2005 Oct 25
0
Managing configuration and driver names changes (was: About blazer, powermust and mustek)
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
2013 Nov 01
3
Merging blzr as blazer (and un-merging voltronic?)
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
2009 Feb 19
2
megatec_usb vs Mustek NetGuard / Ippon SmartWinner problem
Greetings Gentlemen, I have Mustek NetGuard 1000 UPS which is equivalent to Ippon SmartWinner 1000. I have tried to run several latest builds of NUT, but run megatec_usb driver still failed with my device. I hope the information below might help. Regards, Oleg Here is the information which may help: lsusb -v Bus 002 Device 002: ID 06da:0003 Phoenixtec Power Co., Ltd Device Descriptor:
2005 Dec 19
1
MGE Pulsar ES 8+
Hi! I have a MGE Pulsar ES 8+ UPS. Here is the response of some commands: - Si --> 3000 44 0 - Si 1 --> Pulsar ES8+ 0 - Ai --> 5 0 It's not recognized very well by the current (from CVS) mge-utalk driver: [root@srv01 ~]# /home/rog/src/nut/drivers/mge-utalk -i 20 -DDD -u root /dev/ttyS0 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.86 (2.1.0) debug level is '3'
2005 Oct 10
1
Re: About blazer, powermust and mustek
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
2012 May 10
3
battery.charge and other fixes needed for X-Power Tigra 1kVA
Hello all, been 5 years since I posted on this list, glad to be back :) I have a number of X-power Tigra 1kVA online UPS units. From some knowledgeable folks working for the local distributor, I learnt that from inside this looked like a Best 610 ups unit. Before, I had this UPS hooked via serial to my Windows 2003 server. For monitoring, some winpilot/upspilot software was also provided.
2018 Jul 31
0
Adding drivers to NUT?
Dear Daniele, I have some news regarding the Driver: I applied the patch you sent me (https://github.com/zykh/nut/tree/issue-441) and it works correctly (obviously in Level 5 of Debug I see "missing CR...etc.."). As for now there are 2 modification I'd like to suggest you: - For Online Type UPSs the Megatec protocol describes that the battery voltage is provided in the form of V
2012 Jun 04
4
Driver for a REDi Blazer 600VA UPS
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