Hi, I'm new to this list but I have some contribution to do (or new problem!) At this mailing list archive, october, last year, I could see that there is a demand for a nut-driver for some brazilian SMS UPS. (Monophase: Net+ and Senoidal models). The first version is running under some limitations, but it is going on. If anyone has interest for improvements, suggestions, then I can provide the source code. Regards, Ulisses Guedes
I have a Net 4+ Expert and I could help testing. On Wed, Jan 23, 2013 at 3:51 PM, Rodrigo Vigna <skrull at gmail.com> wrote:> I have a Net 4+ Expert and I could help testing. > > On Wed, Jan 23, 2013 at 3:44 PM, Ulisses Guedes <uli1958 at hotmail.com> wrote: >> >> Hi, >> >> I'm new to this list but I have some contribution to do (or new problem!) >> >> At this mailing list archive, october, last year, I could see that there is a demand for a nut-driver for some brazilian SMS UPS. (Monophase: Net+ and Senoidal models). >> >> The first version is running under some limitations, but it is going on. >> >> If anyone has interest for improvements, suggestions, then I can provide the source code. >> >> Regards, >> >> Ulisses Guedes >> >> >> >> >> >> >> _______________________________________________ >> Nut-upsdev mailing list >> Nut-upsdev at lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
Sorry, I mispelled. I spotted another bug. input.current and output.current are wrong because qq.PotenciaSaida is ups output load in percentage units. I patched for ups.load qq.PotenciaSaida. Unless we have a way to figure ups capacity automatically my suggestion is to add a driver option to set ups capacity manually, and hard-code ups power-factor and efficiency in the driver (it is specified in tech specs of each model) then we could simulate input.current and output.current. Rodrigo On Wed, Jan 23, 2013 at 6:24 PM, Rodrigo Vigna <skrull at gmail.com> wrote:> More feedback. > > Using vendor software, UPS load is 25-35%. You driver is showing 0.2 > to 0.3 on output.current.
You are right. Since input /output current is not supplied by SMS firmware, i guess that should better replace them by voltage, power and frequency statistics (maximum and minimum), as vendor software does. What you think about this? After we get a stable release i would implement other features. Ulisses> From: skrull at gmail.com > Date: Wed, 23 Jan 2013 20:01:23 -0200 > To: nut-upsdev at lists.alioth.debian.org > Subject: Re: [Nut-upsdev] nut driver for SMS (brazil) UPS > > Sorry, I mispelled. > > I spotted another bug. > > input.current and output.current are wrong because qq.PotenciaSaida is > ups output load in percentage units. I patched for ups.load > qq.PotenciaSaida. > > Unless we have a way to figure ups capacity automatically my > suggestion is to add a driver option to set ups capacity manually, and > hard-code ups power-factor and efficiency in the driver (it is > specified in tech specs of each model) then we could simulate > input.current and output.current. > > Rodrigo > > On Wed, Jan 23, 2013 at 6:24 PM, Rodrigo Vigna <skrull at gmail.com> wrote: > > More feedback. > > > > Using vendor software, UPS load is 25-35%. You driver is showing 0.2 > > to 0.3 on output.current. > > _______________________________________________ > Nut-upsdev mailing list > Nut-upsdev at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev