similar to: No battery.charge

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

Dear list, Can't make upssched notify me on event occured. OS: Debian, 2.6.26-1-amd64 Nut: 2.4.3-1.1squeeze1 UPS: Ippon Smart Winner 3000 connected via COM On event ( plug out the cord from UPS ) upsmon detect's status change to OB and gives WALL and syslog notify, but no script starting. In syslog no errors and no upssched process occured, just upsmon. There're no PIPE and LOCK

Greetings! I have successfully installed and configured nut package. All i want now is to power off ups. If i run upsmon -c fsd as root - everything goes fine, system and ups gracefully shutting down. If i unplug power cable from an ups, then system is down, but ups still on load. Any help would be appreciated. Debian Lenny x86 ups.conf [ippon] driver = megatec port = /dev/ttyS0

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,

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

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

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

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

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

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

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

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

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

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

Hello list, first of all, I'd like to report that my UPS N-Power MEV-3000LT (http://www.380v.ru/catalogue/micro-ups/mega-vision , in Russian), which is not in the hardware compatibility list, is mostly supported by the blazer_ser driver. I have very strong grounds to believe that this (and other) N-Power UPS'es are rebranded for Russian and Italian markets from their counterparts

Hi, FYI for all whom have the Sweex manageable UPS. I got my sweex manageable UPS500VA working with NetworkUPSTools using the ippon driver. Here is my the ups.conf file: [ups] driver = ippon port = /dev/cuad0 desc = "Server" Has anyone tried the ippon driver with Sweex 600VA, 700VA, and 800VA models? Regards, Jan

Full_Name: Axel Benz Version: 1.7.1 OS: Windows Submission from: (NULL) (137.251.33.43) Hello, I guess many people will answer me again that this is a S language feature, but I am only a stupid computer scientist and I simply do not understand this logic, despite of reading a lot about S: > test field tuckey 4 Kreis2 -1 5 Kreis5 -2 9 Metall -3 17

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

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