[Nut-upsdev] UPS (Megatec) with strange voltage values

[Luiz Angelo Daros de Luca]

I finally managed to have sometime to find out why NUT wasn't compiling...
autoreconf and not autoconf!

Carlos, the patch fixed the problem and compiled flawless.

I would sugest these values for batvolts

{ 240, 1.75*120, 2.33*120, 1.75*120, 2.09*120,  0.0 },   /* Lacerda Titan
Black */

I don't know where should the batvoltsmult would fit here. If it is intend
to work without parameters,
this table should have another collumn for batvoltsmult. If not, the value
present here migth be multiplied
by the config parameter (batvoltsmult) before being used.

Anyway, I'm defining them in config file.

[ups1]
  driver = megatec
  port = /dev/ttyUSB0
  model = "Titan Black tri-mono 10KVA"
  serial = A07k21124
  desc = "UPS1 10 KVA Lacerda (220v)"
  mfr = "Lacerda Sistemas de Energia"
  battvoltmult = 120
  battvolts=1.75:2.09
[ups2]
  driver = megatec
  port = /dev/ttyS0
  model = "Titan Black tri-mono 10KVA"
  serial = A08823221
  desc = "UPS2 10 KVA Lacerda (220v)"
  mfr = "Lacerda Sistemas de Energia"
  battvoltmult = 120
  battvolts=0.00:2.09

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

#define SEND_PACE    100000  /* interval between chars on send (usec) */

to 10000

Maybe this could be turned into a new parameter.

Thanks,

2008/10/9 Carlos Rodrigues <cefrodrigues at gmail.com>

> On Thu, Oct 9, 2008 at 8:03 AM, Arjen de Korte <nut+devel at de-korte.org<nut%2Bdevel at de-korte.org>>
> wrote:
> > Citeren Arjen de Korte <nut+devel at de-korte.org<nut%2Bdevel at de-korte.org>
> >:
> >
> >>> Perhaps the graphics should use a dynamic scale instead of a fixed
> >>> scale (there are many other models out there reporting nominal
> >>> voltages of 12V and then ~2V for the current battery voltage).
> >>
> >> This is the case. The problem here is that in this case the megatec
> >> driver reports 'battery.voltage' as single cell and
> >> 'battery.voltage.nominal' as the total string voltage.
> >
> > Have a look at changeset 1337 for the bestups driver, this suffered from
> a
> > similar problem a while back. It won't be a drop in replacement here
> since
> > that one didn't report a nominal battery voltage, so we try to guess that
> > based on the reported low/high battert voltage. But it too uses a battery
> > voltage multiplier so that the graphics report the battery string
> voltage,
> > instead of just the single cell voltage.
>
> The attached patch adds a "battvoltmult" parameter to the megatec
> driver in the trunk.
>
> It should work, but I'm away from a development environment, so it is
> totally untested (it wasn't even compiled to check for syntax errors).
> The changes are mostly harmless, though.
>
> --
> Carlos Rodrigues
>



-- 
     Luiz Angelo Daros de Luca
           luizluca at gmail.com
             ICQ: 19290419

I Know, "Where you wanted to go today",
   but I decided to stop here instead!
                       MS Windows
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20081015/fd194ce7/attachment.htm