similar to: blazer_usb: compatibility with Ippon BackPro UPSes (Phoenix Power Co., Ltd usb-to-serial controller)

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 all! Maybe possible adds something in megatec_usb driver for normal working with ippon 2000? This is output for drivers megatec_usb and blazer_usb: =========================================================== gate# /usr/local/libexec/nut/megatec_usb -DDDD -a IPPON Network UPS Tools - Megatec protocol driver 1.6 (2.4.1) Serial-over-USB transport layer 0.10 debug level is '4' Checking

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello 2All. Today I had purchased Ippon Smart Power Pro 1400 UPS for my home PC. It is a higher class device relative to Ippon Back Pro model line. It has one RS232 port and one USB port to connect the monitoring station to. UPS talks with megatec protocol, RS232 works as usual. USB connection is done through Cypress Semiconductor usb-to-serial chip

Hi all! I have a ups Ippon smart power pro 2000. And it connects to my FreeBSD 7.2 x86 server throught usb. I'm try to setup it in nut with megatec_usb driver... But it is not recognizes ups. I'm try set productid and vendorid in ups.conf, but this is not help. Nut version 2.4.1 below i'm add output of lsusb, my ups.conf and /usr/local/libexec/nut/megatec_usb -a IPPON -DDD

Citeren Roman Mamedov <roman at rm.pp.ru>: >> Another useful thing would be to run the bundled driver on a Windows >> box while running 'usbsnoop' so that we can get an idea what it is >> doing. Maybe we're missing something here. I still would like to see that. > Keep in mind that the patched megatec_usb driver (which I use since > yesterday) can

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 friends! It is not any answer to my previous letter about problem with nut 2.4.1 and ippon smart power 2000 UPS with megatec_usb driver. Maybe any additional information needed? Please help, any required info i get. -- ? ?????????, vk mailto:vk at union-metall.ru

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:

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, Thanks to some older discussions on this list I found it quite easy to eventually track down problem with using USB cable with some more of Megatec/Q1 UPSes. The trick (which is done in megatec_usb, but not in blazer_usb) is to read in the junk that somehow gets into read buffers before sending any commands. (I inserted debug statements so it's easy to see that the data read is really

Hello, i'm trying to use nut with ippon back power pro 700 on FreeBSD 9.1-R with USB driver blazer_usb, and connection with UPS is unstable. I'm starting it: office at root # /usr/local/etc/rc.d/nut start Network UPS Tools - UPS driver controller 2.6.5 addchar: discarding invalid character (0xe2)! addchar: discarding invalid character (0x80)! addchar: discarding invalid character (0xb3)!

Hello! I'm trying to use nut with a Ippon Smart Winner 3000 UPS (http://shop.key.ru/photo/items/45535.jpg) which looks like a custom-labeled OEM model of the megatec branch. I tried both the megatec_usb and the blazer_usb drivers for it, with a obvious config section: [ippon] driver = blazer_usb port = auto vendorid = 06da productid = 0003 desc = "Ippon Smart Winner 3000" If I

after I starting battery test on my laptop I see in my logs some error and ups (IPPON Smart Power Pro 1400. usb interface) isn't monitoring now [ippon] driver = megatec_usb port = auto desc = "local" Feb 16 23:22:09 f37 upsd[17150]: Instant command: stlk at 127.0.0.1 did test.battery.start on ippon Feb 16 23:22:12 f37 megatec_usb[17249]: ser_get_line: Device detached? (error

Hi to everybody. Some days ago, I bought an UPS by Forza Power Technologies, model SL-1001. This Forza SL-1001 is line-interactive, has 14,4 A/h charge and is rated at 1000VA. Before, I had a TrippLite Omni 500 (or something like that), a simple contact-closure UPS, and I used nut with the simple genericupsdriver, so I'm new with this type of UPSs. NUT doesn't list Forza as a

Hello, I have a UPS branded as "Energit MXE II" that comes with the infamous Winpower software (as already discussed in this old thread <http://nut-upsdev.alioth.debian.narkive.com/m0FWk43o/blazer-usb-compatibility-with-ippon-backpro-upses-phoenix-power-co-ltd-usb-to-serial-controller>). This same UPS appears to be sold as "Centralion Titan Elite" and maybe other names

On Dec 7, 2013, at 5:43 AM, Denis Yantarev wrote: > Ippon Back Power Pro responses are always padded to 64 bytes beyond \r payload terminator. When checking that command was successful (i.e. not echoed back) code relies on the response length reported by blazer_command which will always be 64. To fix this ippon_command should return actual payload length. This change also affects

Hello, I'm trying to get my UPS working with nut-hal-drivers, and it seems be detected correctly with Megatec protocol, but it provides wrong battery level. I read that I can use battvolts option to fix this problem, but HAL version of nut does not come with any config files. So, I'm guess it should be somehow fixed in sources? Parameters of Ippon Back Comfo Pro 800: VA = 800 max

Hi! I'm having problems connecting Ippon Smart power pro 1000 UPS to nut via usb under FreeBSD 7-stable The UPS uses megatec protocol and works fine via RS232 (UPS has RS232 and USB connectors) When I connect USB /dev/uhid0 is created. Tried port=/dev/uhid0 - doesn't work. Kernel rebuild w/o option uhid. On connect I get 2 devices /dev/ugen1, /dev/ugen1.1. Tried both of them.

Hello! I've got an "Ippon Back Power Pro 700 USB" UPS. The system is Gentoo/Calculate. The NUT version is *2.6.0-r1* I've made all necessary instructions to make NUT work properly with my UPS using USB "blazer_usb" driver. But, when I start *upsdrv* it tells me the following: * * Starting UPS drivers ...* *Network UPS Tools - UPS driver controller 2.6.0*

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