similar to: Can anyone give me some ideas?

Arjen de Korte ha scritto: > Citeren Nick Warr <nick at mobilia.it>: > >>> How is the driver failing? >> It says there's no Megatec protocol UPS on that port more or less. > > Could you run the driver in debug mode and post the (gzip'ed) logs as > an attachment? > > /path/to/megatec -DDD -a upsname > > The upsname should be the name as

Hello. I have this UPS: Krauler UP-D1200VA Megatec USB protocol Vendor ID: 0x0001, Device ID: 0x0000 #KRAULER UP-D1200VA VER6.00 #220.0 004 23.50 50.0 Currently I have nut 2.2.0 installed from sources. Installation was successful except that I had to change a string in 52-nut-usbups.rules from: SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" to:

Hello Peter! Peter Selinger wrote: > This is useful information. I don't think the device is currently > supported, but the information printed above is enough to write a > subdriver for it. Note that the purpose of the "-x generic" option is > precisely to produce this output. [...] >> Apparently the UPS is recognized but no communication is >>

I have an UPS, that claims to be IPPon Back Power Pro 700. I'm trying to connect it using USB. lsusb -v says: Bus 1 Device 3: ID 06da:0003 Phoenixtec Power Co., Ltd Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0

Hi Stefanos, you should mail to the NUT list, and try the megatec driver, which is only available from subversion for the moment (but should be included in the next stable release). Carlos might give you some help with this driver. Arnaud Quette -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

UPS: PowerWalker VFI 3000RT LCD CentOS 6.5, nut installed from RPM package: nut-2.6.5-2.el6.x86_64 nut-client-2.6.5-2.el6.x86_64 Driver: blazer_usb Problem description: USB device "loops" when starting blazer_usb. USB device permissions are ok. Receives some information. Error messages: "failed to claim USB device: could not claim interface 0: Device or resource busy"

Hello, I have a Yunto e a Zanto ups connected with usb with id 06da:0002 and 06da:0601. I have seen that people had some success using megatec driver. But now megatec is replaced by blazer-usb and I am not able to use my upses under nut. Can you help me? Thanks! Mario

Hi! This is the weirdest problem I have found for a long time! Using nut-2.0.5 and a Gentoo powered HP Proliant ML350 I setup the config files just the same as I always do and tried to get the megatec driver chatting to the UPS. It worked fine on a Windoze server with Upsilon2000 so I have a bit of confidence in cable etc! When I ran upsc after starting upsd to complained about stale data! Most

Hi, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

Hello, I have bought Powerman Optima 500 Plus UPS. While this product might be unknown outside Russia, it is shipped with megatec software and obviously works with megatec driver in NUT. besides the following problems (I think they are caused by one reason): 1) megatac driver is able to load and detect UPS only on second or third run. On the first run it typically fails. Later if daemon is

Sorry for the huge delay and thanks Charles for taking care of this topic. >> I'm running OpenSuse 13.1 and I have a Lupus 500 USB (Fideltronik) >> >> After quite a bit of playing around I managed to get the status of the UPS using the blazer_usb driver and running NUT 2.6.5. >> But unfortunately none of the Instcmds such as load.off etc. worked. > > Can you post

Hello. I've been experimenting with the USB connection of an Ippon BackComfoPro 800. This is the device "06da:0003 Phoenixtec Power Co., Ltd". The current SVN version of NUT does not work with this device. The megatec_usb driver can't get a proper reply to a Q1 request, failing with an error message about "short read (14 bytes)" instead. I have found the reason for

Hi, This is my first post ever on a technical forum, so please forgive any poor etiquette etc. Also I'm totally new to Linux all of my experience has been trying to get this UPS to work. So please bear this in mind. I'm running OpenSuse 13.1 and I have a Lupus 500 USB (Fideltronik) After quite a bit of playing around I managed to get the status of the UPS using the blazer_usb driver and

Sorry for my delay, I've only just read this mail. At first glance the driver looks like it should work, I will test it tomorrow (if possible) and let you know. I'll also give a reply to your questions. Many thanks for the work you've already put into this. -------------------------------------------------- From: <hyouko at gmail.com> Sent: Monday, June 30, 2014 12:42 AM To:

Hi again, I tested several times using the Megatec driver from nut 2.2.2 to no avail, as it definitely never "sees" the UPS. Always getting : # drivers/megatec -DDD -a Alpha Network UPS Tools 2.2.2 - Megatec protocol driver 1.5.14 [megatec] Carlos Rodrigues (c) 2003-2008 debug level is '3' Starting UPS detection process... Asking for UPS status [Q1]... Q1 => FAILED

Hi there, A couple years ago, I had patched the "fentonups" nut driver to allow it to work with my Unitek Alpha 500 UPS. My patch had been accepted and incorporated in the standard fentonups driver. I have had no time to stay involved in the "nut" project since (and besides this I'm not a developper...). 2 days ago I upgraded from Ubuntu Gutsy to Ubuntu Hardy and got

Hello, i've a problem, this is my configuration: - Atlantis Land UPS with serial port - a generic RS232 to USB cable adapter (QinHeng Electronics HL-340 USB-Serial adapter for linux). The problem is in the syslog file where i find: [...] Aug 19 09:07:25 ProLiant megatec[1126]: Communications with UPS lost: No status from UPS. Aug 19 09:07:26 ProLiant megatec[1126]: Communications with UPS

Hi All! I have a traoble whith my ups, - megatec driver can not calculating % of charging and voltage on battery: # uname -a FreeBSD backup.*.*.* 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Wed Sep 22 12:25:01 EEST 2010 ups.conf [Powercom] driver = megatec port = /dev/cuau0 #battvolts=12:24 desc = "powercom sxl-1000A" # ./nut start Network UPS Tools - UPS driver controller 2.4.1

Have anybody expirience with Ippon Smart Winner 750/1000/1500/2000/3000 with serial interface ? I have tryed megatec and blazer_ser drivers with no success: [IPPON] driver = megatec port = /dev/ttyd0 desc = "IPPON smart winner 1500VA" model = "Smart Winner 750/1000/1500/2000/3000" # ./megatec -a IPPON -DDD Network UPS Tools - Megatec

Am Trying to use nut (2.2.0 - on an SMEServer V8 aka Centos 5.5) on the above UPS, I've tried the megatec driver in serial and USB mode (the device has both types of connection), but no success. An Example: [root at mailserver ~]# megatec_usb -a UPS -DDDDDDDD Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport