similar to: Re: nut: Ippon driver with SmartWinner 1000: charge value fix

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:

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

Hi all! I have a nut 2.4.1 on FreeBSD 7.1 i386. UPS model is IPPON smart smart power pro 2000. When i try to see battery charge, in output it have not such variable, and i can't control other servers (Win2k3 + WinNUT) because they not knows about current battery charge. How i can solve that problem? Thanks! upsc IPPON at localhost:54672 --------------------------- battery.voltage: 27.50

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'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)!

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

-----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

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

-----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

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 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

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

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*

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 ups-devel, As I looked throw www.networkupstools.org site, haven't found any pointers where to send patches, so I hope this is the right place. (Please let me know weather this is the right place.) The patch contains a minor change in the logic of the driver, our Effekta MHD 3000 UPS continuously writes status data to the serial port, so one has to send a CR character and empty the

Hello, I am working on getting NUT working with my Smart-UPS 900 UPS (with the C c= able) For several years, I have used the apcupsd product, but because of the nagios support for nut, I am working on switching over. Under apcupsd, I get tons of information from my UPS: # /usr/local/sbin/apcaccess status DATE : Sat Jul 09 12:56:41 CDT 2005 HOSTNAME : homer RELEASE : 3.8.6 UPSNAME :

I finally got around to writing myself a NUT UPS monitoring tool. NUT's UPS monitoring CGI tools provide a detailed instantaneous view of the UPS's state at any moment, but provide no history. The attached tool, upswatch, uses Kiss Gabor's UPS::Nut module and Tobi Oetiker's rrdtool to provide a graphical history of the major UPS operating parameters via a web browser.

On May 11, 2017, at 1:51 PM, Jesse Molina <jmolina at swoncology.net> wrote: > > I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid at the same time. > > I am at a remote location from the computer and UPS, so I can't physically go over and check. I asked a

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