<div dir="ltr">I finally managed to have sometime to find out why NUT wasn't compiling... autoreconf and not autoconf!<br><br>Carlos, the patch fixed the problem and compiled flawless. <br><br>I would sugest these values for batvolts<br>
<br>{ 240, 1.75*120, 2.33*120, 1.75*120, 2.09*120, 0.0 }, /* Lacerda Titan Black */<br><br>I don't know where should the batvoltsmult would fit here. If it is intend to work without parameters, <br>this table should have another collumn for batvoltsmult. If not, the value present here migth be multiplied<br>
by the config parameter (batvoltsmult) before being used.<br><br>Anyway, I'm defining them in config file.<br><br>[ups1]<br> driver = megatec<br> port = /dev/ttyUSB0<br> model = "Titan Black tri-mono 10KVA"<br>
serial = A07k21124<br> desc = "UPS1 10 KVA Lacerda (220v)"<br> mfr = "Lacerda Sistemas de Energia"<br> battvoltmult = 120<br> battvolts=1.75:2.09<br>[ups2]<br> driver = megatec<br> port = /dev/ttyS0<br>
model = "Titan Black tri-mono 10KVA"<br> serial = A08823221<br> desc = "UPS2 10 KVA Lacerda (220v)"<br> mfr = "Lacerda Sistemas de Energia"<br> battvoltmult = 120<br> battvolts=0.00:2.09<br>
<br>BTW, the second UPS I have has a problem with NUT. It ignores the chars sent to serial port if the time between char is greater than 60000 useconds. To fix this, I reduced<br><br>#define SEND_PACE 100000 /* interval between chars on send (usec) */<br>
<br>to 10000<br><br>Maybe this could be turned into a new parameter.<br><br>Thanks,<br><br><div class="gmail_quote">2008/10/9 Carlos Rodrigues <span dir="ltr"><<a href="mailto:cefrodrigues@gmail.com">cefrodrigues@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Thu, Oct 9, 2008 at 8:03 AM, Arjen de Korte <<a href="mailto:nut%2Bdevel@de-korte.org">nut+devel@de-korte.org</a>> wrote:<br>
> Citeren Arjen de Korte <<a href="mailto:nut%2Bdevel@de-korte.org">nut+devel@de-korte.org</a>>:<br>
<div class="Ih2E3d">><br>
>>> Perhaps the graphics should use a dynamic scale instead of a fixed<br>
>>> scale (there are many other models out there reporting nominal<br>
>>> voltages of 12V and then ~2V for the current battery voltage).<br>
>><br>
>> This is the case. The problem here is that in this case the megatec<br>
>> driver reports 'battery.voltage' as single cell and<br>
>> 'battery.voltage.nominal' as the total string voltage.<br>
><br>
</div>> Have a look at changeset 1337 for the bestups driver, this suffered from a<br>
> similar problem a while back. It won't be a drop in replacement here since<br>
> that one didn't report a nominal battery voltage, so we try to guess that<br>
> based on the reported low/high battert voltage. But it too uses a battery<br>
> voltage multiplier so that the graphics report the battery string voltage,<br>
> instead of just the single cell voltage.<br>
<br>
The attached patch adds a "battvoltmult" parameter to the megatec<br>
driver in the trunk.<br>
<br>
It should work, but I'm away from a development environment, so it is<br>
totally untested (it wasn't even compiled to check for syntax errors).<br>
The changes are mostly harmless, though.<br>
<br>
--<br>
<font color="#888888">Carlos Rodrigues<br>
</font></blockquote></div><br><br clear="all"><br>-- <br> Luiz Angelo Daros de Luca<br> <a href="mailto:luizluca@gmail.com">luizluca@gmail.com</a><br> ICQ: 19290419<br><br> I Know, "Where you wanted to go today",<br>
but I decided to stop here instead!<br> MS Windows<br>
</div>