Displaying 20 results from an estimated 100 matches similar to: "blazer_usb vs. Ippon Smart Power Pro 1400"
blazer_usb: compatibility with Ippon BackPro UPSes (Phoenix Power Co., Ltd usb-to-serial controller)
2010 Jan 06
1
blazer_usb: compatibility with Ippon BackPro UPSes (Phoenix Power Co., Ltd usb-to-serial controller)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Good day to all.
In one of the offices I'm administering there are about 15 UPS marked with the
brand "Ippon BackPro". This brand is widely popular in Russian Federation, while
by itself is a 'Made in PRC' megatec clone. Depending on the model this UPSes
have got either one standard serial RS-232C interface (cheaper models like
2007 Jan 08
0
Re: nut: Ippon driver with SmartWinner 1000: charge value fix
Hello Ace,
2007/1/6, ace <ace@ezotop.ru>:
> Hello Arnaud,
>
> Ippon driver with SmartWinner 1000: charge value fix
>
> nut-2.0.2:ippon.c:line 31:
> -- bcharge = ((atof (batvlt) - 10.2) / 3.4) *100.0;
> ++ bcharge = ((atof (batvlt) - 24.0) / 3.4) *100.0;
>
> sorry for no comments, i'm bad in english
the ippon driver has just been removed from the nut trunk,
2008 Sep 16
1
ippon smart power pro 1000
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.
2008 Dec 20
1
Ippon BackComfoPro (06da:0003 Phoenixtec Power)
Roman,
I don't think I already asked, but could you post the output of
lsusb -v -d 06da:0003
Just to be sure that we're not exceeding some buffer limitations of
the device.
Best regards, Arjen
--
Please keep list traffic on the list
2008 Dec 20
0
Fwd: Re: megatec_usb: Ippon BackComfoPro (06da:0003 Phoenixtec Power)
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
2009 Jun 30
2
Is any ideas about Ippon smart power 2000?
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
2011 Jul 28
1
Ippon Back Power Pro 700 USB driver.
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*
2013 Dec 07
0
[nut] Ippon response length fix (#80)
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
2008 Jun 25
1
[nut-hal-drivers] Battery level is not correct for Ippon Back Comfo Pro UPS with Megatec protocol.
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
2009 Jun 18
0
Question about nut 2.4.1 and Ippon smart power pro 2000
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
2013 Apr 28
1
ippon back power pro 700 on FreeBSD 9.1-R
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)!
2011 Feb 16
3
Ippon Smart Winner 750/1000/1500/2000/3000
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
2008 Dec 19
1
megatec_usb: Ippon BackComfoPro (06da:0003 Phoenixtec Power)
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
2009 Aug 02
2
Driver fix for Ippon BCP800 (06da/0003), blazer_usb.c
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
2010 Feb 22
1
Is the NUT site down?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all,
Had anybody noticed that the http://networkupstools.org/ had been inaccessible
for several days? At least I can't access the site from three different Moscow
ISPs, and it seems also to be inaccessible through http://anonymouse.org/. Is
that normal?
- --
Best regards,
Alexey Loukianov mailto:mooroon2 at
2006 Aug 04
1
RE nut drivers
Hi Alexander,
> I've UPS named PowerMan RealSmart 1000, it is not listed in
> compatibility list. I found that it works with "fentonups" driver and
> have ups.model "Unknown S163-1000". Ithink "1000" is from capacity -
> I've seen in Internet someone have RealSmart 800 identified "S163-800".
> Also PowerMan have
2008 Sep 11
2
Ippon device does not work
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
2009 Jul 19
1
Problem with nut 2.4.1 & Ippon 2000 Smart power on FreeBSD
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
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:
2010 Jan 16
1
ETIME on FreeBSD
This looks like the commit that triggered the following FreeBSD build
failure:
http://buildbot.ghz.cc/public/nut/FreeBSD-i686/builds/53
One thing that stands out is that ETIME is not negated like the other
error codes. What returns it?
- Charles
On Jan 13, 2010, at 8:04 AM, Arjen de Korte wrote:
> Author: adkorte-guest
> Date: Wed Jan 13 13:04:42 2010
> New Revision: 2243
>