<HTML><BODY>Hello list,<br><br>first of all, I'd like to report that my UPS<br><br>N-Power MEV-3000LT<br>(http://www.380v.ru/catalogue/micro-ups/mega-vision , in Russian),<br><br>which is not in the hardware compatibility list, is mostly supported<br>by the blazer_ser driver. I have very strong grounds to believe that<br>this (and other) N-Power UPS'es are rebranded for Russian and<br>Italian markets from their counterparts produced by Powerbank<br>Electronics Corporation in Taiwan<br>(http://www.powerbank.com.tw/products.php?cat=65&lang=en).<br>I believe they are the same not only because they look the same,<br>have the same specifications etc but also because being in Taipei<br>first I wanted to buy a Powerbank UPS and they told me that they<br>obliged not to sell these UPSes in Taiwan and sent me to<br>Moscow to N-Power, suggesting to buy from them.<br><br>So I believe the compatibility list deserves two new lines.<br><br>Now what doesn't work.<br><br>1. Shutdown<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br># /lib64/nut/blazer_ser -amv -k -DDD<br>Network UPS Tools - Megatec/Q1 protocol serial driver 1.55 (2.6.5-Unversioned directory)<br> 0.000000 debug level is '3'<br> 0.108370 Initiating UPS shutdown<br> 0.108561 send: 'C'<br> 0.150967 read: 'NAK'<br> 0.151021 instcmd: command [shutdown.stop] failed<br> 0.151162 send: 'C'<br> 0.193506 read: 'NAK'<br> 0.193598 instcmd: command [shutdown.stop] failed<br> 0.193725 send: 'C'<br> 0.236016 read: 'NAK'<br> 0.236093 instcmd: command [shutdown.stop] failed<br> 0.236127 Shutdown failed!<br><br>Probably the 'C' command has some unlocking mechanism. I remember around 15 years ago<br>I had a cheap Ippon UPS which spoke the same protocol. This UPS fed a Windows PC and<br>had the following problem: during Windows boot-up, when Windows started their own (that time,<br>non-standard) COM-port plug-n-play enumeration of devices, the UPS with a small probability<br>perceived this sequence as 'C' (or 'T', if I still remember right the protocol) and after 30 second<br>switched off the computer being boot. I had to reverse engineer the program is this UPS and<br>discovered commands to lock/unlock shutdown commands which solved the problem. Probably<br>a similar mechanism is implemented in this my UPS but shutdown commands are locked by<br>default. I do not insist on this version, I just want to share this idea.<br><br>Maybe this is a known problem, then I would appreciate any pointer to find the solution.<br><br>2. Reporting battery.runtime and battery.charge.<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>I am not sure this has to do with the support of this very specie, likely this is rather a bug in the driver<br>or in the documentation.<br><br>With this bare configuration:<br>[mv]<br> driver = blazer_ser<br> port = /dev/ttyS0<br> desc = "N-Power MegaVision 3000LT"<br><br>and with a fully charged battery the driver reports the following variables:<br><br>battery.charge: 100<br>battery.voltage: 109.44<br>battery.voltage.high: 104.00<br>battery.voltage.low: 83.20<br>battery.voltage.nominal: 96.0<br>device.type: ups<br>driver.name: blazer_ser<br>driver.parameter.pollinterval: 2<br>driver.parameter.port: /dev/ttyS0<br>driver.version: 2.6.5-Unversioned directory<br>driver.version.internal: 1.55<br>input.current.nominal: 13.0<br>input.frequency: 50.1<br>input.frequency.nominal: 50<br>input.voltage: 209.8<br>input.voltage.fault: 225.1<br>input.voltage.nominal: 230<br>output.voltage: 230.7<br>ups.beeper.status: enabled<br>ups.delay.shutdown: 30<br>ups.delay.start: 180<br>ups.load: 15<br>ups.status: OL<br>ups.temperature: 41.5<br>ups.type: online<br><br>Now I would elaborate the config and make use of the runtime guestimation.<br>I added the following lines:<br><br>runtimecal = 2000,100,5000,50<br>chargetime = 86400<br>default.battery.voltage.high = 109.6<br>default.battery.voltage.low = 84.4<br>default.battery.capacity = 40<br><br>I didn't do any measuerements yet and these data are based solely on the datasheet of<br>my batteries and common sense. Now I get<br><br>battery.capacity: 40<br>battery.charge: 0<br>battery.runtime: 1<br>battery.voltage: 109.44<br>battery.voltage.high: 109.6<br>battery.voltage.low: 84.4<br>battery.voltage.nominal: 96.0<br>...<br><br>Hello list,<br><br>first of all, I'd like to report that my UPS<br><br>N-Power MEV-3000LT<br>(http://www.380v.ru/catalogue/micro-ups/mega-vision , in Russian),<br><br>which is not in the hardware compatibility list, is mostly supported<br>by the blazer_ser driver. I have very strong grounds to believe that<br>this (and other) N-Power UPS'es are rebranded for Russian and<br>Italian markets from their counterparts produced by Powerbank<br>Electronics Corporation in Taiwan<br>(http://www.powerbank.com.tw/products.php?cat=65&lang=en).<br>I believe they are the same not only because they look the same,<br>have the same specifications etc but also because being in Taipei<br>first I wanted to buy a Powerbank UPS and they told me that they<br>obliged not to sell these UPSes in Taiwan and sent me to<br>Moscow to N-Power, suggesting to buy from them.<br><br>So I believe the compatibility list deserves two new lines.<br><br>Now what doesn't work.<br><br>1. Shutdown<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br># /lib64/nut/blazer_ser -amv -k -DDD<br>Network UPS Tools - Megatec/Q1 protocol serial driver 1.55 (2.6.5-Unversioned directory)<br> 0.000000 debug level is '3'<br> 0.108370 Initiating UPS shutdown<br> 0.108561 send: 'C'<br> 0.150967 read: 'NAK'<br> 0.151021 instcmd: command [shutdown.stop] failed<br> 0.151162 send: 'C'<br> 0.193506 read: 'NAK'<br> 0.193598 instcmd: command [shutdown.stop] failed<br> 0.193725 send: 'C'<br> 0.236016 read: 'NAK'<br> 0.236093 instcmd: command [shutdown.stop] failed<br> 0.236127 Shutdown failed!<br><br>Probably the 'C' command has some unlocking mechanism. I remember around 15 years ago<br>I had a cheap Ippon UPS which spoke the same protocol. This UPS fed a Windows PC and<br>had the following problem: during Windows boot-up, when Windows started their own (that time,<br>non-standard) COM-port plug-n-play enumeration of devices, the UPS with a small probability<br>perceived this sequence as 'C' (or 'T', if I still remember right the protocol) and after 30 second<br>switched off the computer being boot. I had to reverse engineer the program is this UPS and<br>discovered commands to lock/unlock shutdown commands which solved the problem. Probably<br>a similar mechanism is implemented in this my UPS but shutdown commands are locked by<br>default. I do not insist on this version, I just want to share this idea.<br><br>Maybe this is a known problem, then I would appreciate any pointer to find the solution.<br><br>2. Reporting battery.runtime and battery.charge.<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>I am not sure this has to do with the support of this very specie, likely this is rather a bug in the driver<br>or in the documentation.<br><br>With this bare configuration:<br>[mv]<br> driver = blazer_ser<br> port = /dev/ttyS0<br> desc = "N-Power MegaVision 3000LT"<br><br>and with a fully charged battery the driver reports the following variables:<br><br>battery.charge: 100<br>battery.voltage: 109.44<br>battery.voltage.high: 104.00<br>battery.voltage.low: 83.20<br>battery.voltage.nominal: 96.0<br>device.type: ups<br>driver.name: blazer_ser<br>driver.parameter.pollinterval: 2<br>driver.parameter.port: /dev/ttyS0<br>driver.version: 2.6.5-Unversioned directory<br>driver.version.internal: 1.55<br>input.current.nominal: 13.0<br>input.frequency: 50.1<br>input.frequency.nominal: 50<br>input.voltage: 209.8<br>input.voltage.fault: 225.1<br>input.voltage.nominal: 230<br>output.voltage: 230.7<br>ups.beeper.status: enabled<br>ups.delay.shutdown: 30<br>ups.delay.start: 180<br>ups.load: 15<br>ups.status: OL<br>ups.temperature: 41.5<br>ups.type: online<br><br>Now I would elaborate the config and make use of the runtime guestimation.<br>I added the following lines:<br><br>runtimecal = 2000,100,5000,50<br>chargetime = 86400<br>default.battery.voltage.high = 109.6<br>default.battery.voltage.low = 84.4<br>default.battery.capacity = 40<br><br>I didn't do any measuerements yet and these data are based solely on the datasheet of<br>my batteries and common sense. Now I get<br><br>battery.capacity: 40<br>battery.charge: 0<br>battery.runtime: 1<br>battery.voltage: 109.44<br>battery.voltage.high: 109.6<br>battery.voltage.low: 84.4<br>battery.voltage.nominal: 96.0<br><br><br>Hello list,<br><br>first of all, I'd like to report that my UPS<br><br>N-Power MEV-3000LT<br>(http://www.380v.ru/catalogue/micro-ups/mega-vision , in Russian),<br><br>which is not in the hardware compatibility list, is mostly supported<br>by the blazer_ser driver. I have very strong grounds to believe that<br>this (and other) N-Power UPS'es are rebranded for Russian and<br>Italian markets from their counterparts produced by Powerbank<br>Electronics Corporation in Taiwan<br>(http://www.powerbank.com.tw/products.php?cat=65&lang=en).<br>I believe they are the same not only because they look the same,<br>have the same specifications etc but also because being in Taipei<br>first I wanted to buy a Powerbank UPS and they told me that they<br>obliged not to sell these UPSes in Taiwan and sent me to<br>Moscow to N-Power, suggesting to buy from them.<br><br>So I believe the compatibility list deserves two new lines.<br><br>Now what doesn't work.<br><br>1. Shutdown<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br># /lib64/nut/blazer_ser -amv -k -DDD<br>Network UPS Tools - Megatec/Q1 protocol serial driver 1.55 (2.6.5-Unversioned directory)<br> 0.000000 debug level is '3'<br> 0.108370 Initiating UPS shutdown<br> 0.108561 send: 'C'<br> 0.150967 read: 'NAK'<br> 0.151021 instcmd: command [shutdown.stop] failed<br> 0.151162 send: 'C'<br> 0.193506 read: 'NAK'<br> 0.193598 instcmd: command [shutdown.stop] failed<br> 0.193725 send: 'C'<br> 0.236016 read: 'NAK'<br> 0.236093 instcmd: command [shutdown.stop] failed<br> 0.236127 Shutdown failed!<br><br>Probably the 'C' command has some unlocking mechanism. I remember around 15 years ago<br>I had a cheap Ippon UPS which spoke the same protocol. This UPS fed a Windows PC and<br>had the following problem: during Windows boot-up, when Windows started their own (that time,<br>non-standard) COM-port plug-n-play enumeration of devices, the UPS with a small probability<br>perceived this sequence as 'C' (or 'T', if I still remember right the protocol) and after 30 second<br>switched off the computer being boot. I had to reverse engineer the program is this UPS and<br>discovered commands to lock/unlock shutdown commands which solved the problem. Probably<br>a similar mechanism is implemented in this my UPS but shutdown commands are locked by<br>default. I do not insist on this version, I just want to share this idea.<br><br>Maybe this is a known problem, then I would appreciate any pointer to find the solution.<br><br>2. Reporting battery.runtime and battery.charge.<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>I am not sure this has to do with the support of this very specie, likely this is rather a bug in the driver<br>or in the documentation (if one understand the documentation wrongly, this is probably a bug in there).<br><br>With this bare configuration:<br>[mv]<br> driver = blazer_ser<br> port = /dev/ttyS0<br> desc = "N-Power MegaVision 3000LT"<br><br>and with a fully charged battery the driver reports the following variables:<br><br>battery.charge: 100<br>battery.voltage: 109.44<br>battery.voltage.high: 104.00<br>battery.voltage.low: 83.20<br>battery.voltage.nominal: 96.0<br>device.type: ups<br>driver.name: blazer_ser<br>driver.parameter.pollinterval: 2<br>driver.parameter.port: /dev/ttyS0<br>driver.version: 2.6.5-Unversioned directory<br>driver.version.internal: 1.55<br>input.current.nominal: 13.0<br>input.frequency: 50.1<br>input.frequency.nominal: 50<br>input.voltage: 209.8<br>input.voltage.fault: 225.1<br>input.voltage.nominal: 230<br>output.voltage: 230.7<br>ups.beeper.status: enabled<br>ups.delay.shutdown: 30<br>ups.delay.start: 180<br>ups.load: 15<br>ups.status: OL<br>ups.temperature: 41.5<br>ups.type: online<br><br>Now I would elaborate the config and make use of the runtime guestimation.<br>I added the following lines:<br><br>runtimecal = 2000,100,5000,50<br>chargetime = 86400<br>default.battery.voltage.high = 109.6<br>default.battery.voltage.low = 84.4<br>default.battery.capacity = 40<br><br>I didn't do any real measuerements yet and these data are based solely on the<br>datasheet of my batteries and common sense. Now I get<br><br>battery.capacity: 40<br>battery.charge: 0<br>battery.runtime: 1<br>battery.voltage: 109.44<br>battery.voltage.high: 109.6<br>battery.voltage.low: 84.4<br>battery.voltage.nominal: 96.0<br><br>with battery.charge and battery.runtime slowly (very slow!) grossing.<br><br>Is this expected?<br><br><br>I would appreciate any help with these two problems. I would be happy to provide any<br>details.<br><br>Thanks and regards.<br>Alexander.<br><br></BODY></HTML>