similar to: Zigor on Mac Os X

On 10/08/2012 21:58, nut-upsuser-request at lists.alioth.debian.org wrote: >>> Arnaud Quette<aquette.dev<at> gmail.com> writes: >>>> 2012/6/3 Chris Rees<crees<at> freebsd.org>: >>>>> Hi all, >>>> Hi Chris, >>>> >>>>> After some research I've found that this device should run with the

Hi Arnaud and NUT team You may recall some time ago, I and a few others posted questions about the above referenced (cheap and cheerful) USB-based UPS - specifically regarding FreeBSD USB support in NUT. The original posting was entitled "Zigor Ebro 650 compatibility". I've since tried the latest Windows port of NUT with my WinXP laptop connected to the Zigor Ebro and finally

Hi all, After some research I've found that this device should run with the blazer_usb driver. Jun 3 16:15:38 pegasus kernel: ugen0.4: <vendor 0x0001> at usbus0 Jun 3 16:15:38 pegasus kernel: uhid0: <vendor 0x0001 product 0x0000, class 0/0, rev 1.00/1.00, addr 4> on usbus0 However, even after shoehorning it; [crees at pegasus]/usr/local/libexec/nut% sudo ./blazer_usb -a zigor

2013/9/16 Martyn Hill <martyn.joseph.hill at gmail.com>: > Hi Arnaud and NUT team > > You may recall some time ago, I and a few others posted questions about the > above referenced (cheap and cheerful) USB-based UPS - specifically regarding > FreeBSD USB support in NUT. The original posting was entitled "Zigor Ebro > 650 compatibility". > > I've since

http://www.zigor.com/uk/index.php/en/products/upssystems/danubioseries Ships with UPSilon 2000 software, and appears to work with blazer_usb to a certain extent with the following config: [danubio] driver = blazer_usb langid_fix = 0x409 port = stupidly, I seem to have to set this even though it's ignored vendorid=0001 productid=0000 Yes, vendor 0001,

Hi Folks, I'm trying to use a ZIGOR Danubio 2000 ups with NUT on Debian squeeze (AMD64). OS/NUT are all the latest official release (as of last week) with NUT installed from packages. As the usb descriptor presents MEC (and the Fry's electronics) I chose to use the blazer_usb driver. All appears to work well excepting that the UPS does not appear to accept the shutdown instcmd to turn

Dear Charles and team Just thought to share my findings getting a Sweex PP200 650VA UPS working with NUT (I didn't see this particular model listed on the HCL.) I picked-up one of these units quite cheaply at a Maplins store (before the chain closed-down) as a second UPS for my home/office - the first being an old Zigor Ebro650 - a long story for another post... NUT v2.7.4_7 is running

Hi, I have a strange problem. At a site where there are 20+ phones, there is one phone that cannot make outbound (to PSTN) calls. Each call is dropped after 20s with "no response to our critical packet". Calls to voicemail and internal extensions work fine. I understand that everything points to a NAT problem, but I don't understand how it could be because: 1) It does not affect

Hello, It is 3 or 4 weeks ago since, i want to set communication with my ups a MGE NOVA 1100 AVR. I do it first with manual configuration but after no success, i prefered to install mgeups-psp package to do it directly. But since when i execute psp, the attempt finish with an "No communication with UPS" error. Same is when i type: mge-shut -u root -DDDDDDDDDD /dev/ttyS0 . I unplog

Hi, i've got similar problem with an OVISLINK 1000VA UPS on Debian. I've tried to connect with it using different drivers and this is what I get with each of them: [UPS] driver = blazer_usb vendorid = 0001 productid = 0000 port = auto subdriver = phoenix sweethome:~# /lib/nut/blazer_usb -a UPS -u root -DDD Network UPS Tools - Megatec/Q1 protocol USB driver 0.08 (2.6.4) 0.000000

Hi. I use NUT on embedded system, and after update distro to fresh one I've got a non-working usbhid APC monitoring. There's 2 troubles: 1) I/O error for root on usbhid device 2) Permissions error for nut user Root log: # /usr/bin/usbhid-ups -u root -DDDDDD -a infocom Network UPS Tools - Generic HID driver 0.37 (5.1.2-beta1-28-g04cd334) USB communication driver 0.31 0.000000

I've been running tincd on several machines without a problem. I'm now setting up a new intel-type dual-processor machine, with a custom compiled 2.4.9 linux kernel. When I start the daemon: tincd -n vpn -dddddddddd I get the following debug information in in /var/log/messages Aug 27 17:26:49 q tinc.vpn[971]: Process 972 (tinc-up) exited with non-zero status 255 Aug 27 17:26:49 q

Ladies and Gentlemen, Running newhidups with -DD shows the following line that starts with "-> String:" occasionally, with no contect that it is related to: ...... Can't find object UPS.Battery.Temperature -> String: PbAc (len = 4/4) Can't find object UPS.Output.PercentLoad ...... However, running newhidups with -DDD, shows the proper context: ...... hu_find_infoval:

Hi. I use NUT on embedded system, and after update distro to fresh one I've got a non-working usbhid APC monitoring. There's 2 troubles: 1) I/O error for root on usbhid device 2) Permissions error for nut user Root log: # /usr/bin/usbhid-ups -u root -DDDDDD -a infocom Network UPS Tools - Generic HID driver 0.38 (5.1.2-beta1-28-g04cd334) USB communication driver 0.32 0.000000

I'm stuck behind a corporate NAT that I obviously have absolutely no control over. The nice thing is that the firewall rules, AFAIK, are very nice. I've had tinc running before from behind nazi firewalls with no NAT. Been fiddling with tinc for many hours, but have been SOL. The local machine is the client (has ConnectTo in the conf), and remote is the server (has Listen in the conf).

Hi all, Hope somebody can help-I really am stumped as to why this won't work. I realise that this isnt an Asterisk problem (Please dont bash me on the list) and I have emailed the SER list but I havent received a reply and maybe someone on this list can help...Once this problem is solved I am going to use Asterisk for voicemail etc with SER (I have it set up) I currently have SER set up and

Hello i am trying to use this exmple with SER-0.9.3 but still NATED Clients are not working any other requirement http://www.voip-info.org/tiki-index.php?page=SER+example+NAThelper ----------------------------------------------------------- # $Id: ser.cfg,v 1.21 2003/06/04 13:47:36 jiri Exp $ # # simple quick-start config script # # ----------- global configuration parameters

Hi! Normally nut was just worked and worked for me! Not this time though! Distro is Gentoo withe latest nut-2.6.0 emerged today. Linux kernel version is 2.6.36 UPS is PowerCom BNT2000AT "Driver" is powercom ups.conf looks like this! Okay so APC1 is not and APC! [APC1] driver = powercom type = BNT port = /dev/ttyS1 numOfBytesFromUPS = 16

Hi! Normally nut was just worked and worked for me! Not this time though! Distro is Gentoo withe latest nut-2.6.0 emerged today. Linux kernel version is 2.6.36 UPS is PowerCom BNT2000AT "Driver" is powercom ups.conf looks like this! Okay so APC1 is not and APC! [APC1] driver = powercom type = BNT port = /dev/ttyS1 numOfBytesFromUPS = 16

Hi, We are testing a SIP solution * + ser solution for a large implementation. All the clients are nated. When a client is dialing outside the domain (to a FWD sip account for example) all is perfect ! ;-) But ,when a call is done to a sip account, the client is ringing, then the caller can hear the nated client very well, but the nated client does'nt hear anything. RTP issue no ? I've