search for: al175

...;.deps/common.Tpo" ".deps/common.Po"; else rm -f ".deps/common.Tpo"; exit 1; fi . . . Making all in drivers if gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I/usr/sfw/include -Dsolaris_2 -xarch=v9 -Dsolaris2 -I. -I/usr/sfw/include -O -Wall -Wsign-compare -MT al175.o -MD -MP -MF ".deps/al175.Tpo" -c -o al175.o al175.c; \ then mv -f ".deps/al175.Tpo" ".deps/al175.Po"; else rm -f ".deps/al175.Tpo"; exit 1; fi gcc: language arch=v9 not recognized gcc: al175.c: linker input file unused because linking not done mv: cannot ac...

Hi Kirill, just to notify you that your al175 driver is being removed from the NUT tree, as of 2.4.0-pre1. if you wish to see it entering the tree again, please contact the Development mailing list to talk about it. Merry Christmas and happy New Year. Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS To...

...gt; 2009/1/27 Kirill Smelkov <kirr at mns.spb.ru> > > > On Tue, Jan 13, 2009 at 05:58:23PM +0300, Kirill Smelkov wrote: > > > Arjen, Arnaud, > > > first of all, I'm sorry for my late reply. > > > > > > If it's not too late, here is updated al175: > > > > > > > > > On Fri, Dec 26, 2008 at 11:37:04PM +0100, Arjen de Korte wrote: > > > > Citeren Kirill Smelkov <kirr at mns.spb.ru>: > > > > > > > > [...] > > > > > > > >> Yes, "All the world is...

...rectory `/export/home/zoly/Documents/trunk/drivers' /bin/sh ../libtool --tag=CC --mode=link gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/sfw/include -g -Dsolaris2 -I. -I/usr/sfw/include -O -Wall -Wsign-compare -o al175 al175.o ../common/libcommon.a ../common/upsconf.o ../common/parseconf.o ../common/state.o main.o dstate.o serial.o gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/sfw/include -g -Dsolaris2 -I. -I/usr/sfw/include -O -Wall...

...ffer in signedness solis.c: In function getupdateinfo: solis.c:633: warning: pointer targets in passing argument 2 of ser_get_buf_len differ in signedness solis.c:635: warning: pointer targets in passing argument 1 of CommReceive differ in signedness gcc -I../include -O -Wall -Wsign-compare -c -o al175.o al175.c al175.c: In function comli_prepare: al175.c:390: warning: pointer targets in passing argument 1 of snprintf differ in signedness al175.c: In function al_parse_reply_head: al175.c:547: warning: pointer targets in passing argument 1 of from_hex differ in signedness al175.c:553: warning: poi...

Hello up there! Attached is my patch to add support for AL175 alarm module, Please ACK or NAK this. -- ?????? ??????? -------------- next part -------------- A non-text attachment was scrubbed... Name: al175.patch Type: text/x-diff Size: 35632 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/2005...

Peter, Thanks a lot for your latest changes to newhidups, which I like a lot. Unfortunately, when I tried to build the latest development tree stuff, I got a compile time error when compiling al175.c. It looks to me like my compiler, gcc-3.4.4-2.fc3, doesn't like the macro definition for "RECV(reg) do" because of a poorly inserted comment. I fixed the problem locally by the following patch. However, I think this problem is not unique to my compiler, which is actually rather new...

Hi all! The following files emits warnings when compiled with gcc 4.0: al175.c bcmxcp_ser.c belkinunv.c cyberpower.c everups.c powercom.c solis.c All warnings seem to be of this variety: everups.c:38: warning: pointer targets in passing argument 2 of 'ser_get_char' differ in signedness I suggest that those who fiddles with those drivers fixes the warnings and ver...

On Nov 18, 2013, at 11:53 AM, Kirill Smelkov wrote: > Please find main description in github issue tracker > > https://github.com/networkupstools/nut/issues/69 > > and, for completness, both patches attached to this mail. This is now part of the 2.7.1 release. Regards, -- Charles Lepple clepple at gmail

...address the issues you've raised, and to describe my > rationale behind alarm(). The use of alarm() here is inappropriate (and possibly incorrect as well, see below). As stated before, none of the other drivers require the use of alarm(), you don't have demonstrated a reason why the AL175 does so it shouldn't use it either. The alarm() function has many side effects on other functions, most particularly with timer functions on some systems. Therefor, the use of this should be kept to a bare minimum in drivers. We intend to use the timer functions in the future, to prev...

...rsion.c (revision 0) +++ common/upsversion.c (revision 0) @@ -0,0 +1,10 @@ +#include "config.h" +#include "common.h" + +const char *upsversion(void) +{ + if (SVNREV[0]) + return UPS_VERSION " (" SVNREV ")"; + else + return UPS_VERSION; +} Index: drivers/al175.c =================================================================== --- drivers/al175.c (revision 916) +++ drivers/al175.c (working copy) @@ -1296,7 +1296,7 @@ void upsdrv_banner(void) { printf("Network UPS Tools - Eltek AL175/COMLI support module %s (%s)\n\n", - DRV_VERSION, UPS_...

...t know what i'm supposed to do next, it seams to download some >> things on my /tmp/nut/ but i don't know what is it. >> >> My kernel is Linux 5.4.0-162-generic x86_64 and i don't have >> huawei-ups2000 driver. >> >> I have "/lib/nut$ ls >> al175 blazer_usb metasys riello_ser >> apcsmart clone mge-shut riello_usb >> apcsmart-old clone-outlet mge-utalk safenet >> apcupsd-ups dummy-ups microdowell solis >> bcmxcp etapro nutdrv_atcl_usb tripplit...

...> download some >> things on my /tmp/nut/ but i don't know what is it. >> >> My kernel is Linux 5.4.0-162-generic x86_64 and i don't have >> huawei-ups2000 driver. >> >> I have "/lib/nut$ ls >> al175???????? blazer_usb??? metasys riello_ser >> apcsmart????? clone???????? mge-shut riello_usb >> apcsmart-old? clone-outlet? mge-utalk??????? safenet >> apcupsd-ups?? dummy-ups???? microdowell????? solis >> bcmxcp??????? etapro??????? nutdrv_atc...

...quot; indeed shuts the load on my APC/Back-UPS ES 650 instantaneously (not that I intended to test that!). BTW, I usually do the same types of builds that you reccommended, just from time to time I go back to a clean slate, and today was unfortunately one of those times! And no, the fix for the al175.c compile problem hasn't reached the development tree yet! Hope this helps, AG -- ---------------------------------------------------------------------- Alfred Ganz alfred-ganz@agci.com AG Consulting, Inc. (203) 624-9667 440 Prospect Street # 11 New Haven, CT 06511 -----...

Arjen, Arnaud, All, Here I propose 2 new status flags for inclusion into NUT: HB - HighBattery TEST - Battery test is running rationale: Eltek AL175 alarm module provides this info, therefore rationale: I dicide to add them. Signed-off-by: Kirill Smelkov <kirr@mns.spb.ru> Index: nut--trunk/docs/new-drivers.txt =================================================================== --- nut--trunk.orig/docs/new-drivers.txt 2007-01-09 12:39:06....

everything is in the title... as a side note to Arjen: I've not had time to consider Kirill update on al175. Any thought on this? Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ -------------- n...

...ot;HB High Battery" NUT flag can mean physically, and if the few existing drivers that use it do so consistently with *some* single definition; I looked at precedents of `git grep -w HB` in the codebase, there are a few `setval()` hits, namely: * adelsystem_cbi.c: "BVAL_HIALRM_I", * al175.c: "BATTERY VOLTAGE STATUS", * asem.c: "charge_percentage >= hb_threshold (default 75)", * generic_modbus.c: "usually ... charging state > 85%", * pijuice.c: "battery_charge_level > HIGH_BATTERY_THRESHOLD (macro 75)" * similarly in hwmon_ina219.c add...

Citeren Arnaud Quette <aquette.dev at gmail.com>: > Author: aquette > Date: Sat Nov 15 21:50:40 2008 > New Revision: 1556 > > Log: > USB "improved maintenance" code. Refer to docs/new-drivers.txt for > more information... > > Added: > trunk/drivers/usb-common.c > trunk/drivers/usb-common.h > trunk/tools/ > trunk/tools/Makefile.am >

Hi, Need to get an answer to the following. I find the naming to be little redundant regarding the 'input.transfer.boost.low - hige'. The same goes for input.transfer.trim.low - high. As I find it, there is only one point where the boost or buck (trim) kicks in. Let's say that the nominal voltage is 230 volt, then we have a input.transfer.boost point on say 220 volt. If the

...to do next, it seams to download some >>> things on my /tmp/nut/ but i don't know what is it. >>> >>> My kernel is Linux 5.4.0-162-generic x86_64 and i don't have >>> huawei-ups2000 driver. >>> >>> I have "/lib/nut$ ls >>> al175 blazer_usb metasys riello_ser >>> apcsmart clone mge-shut riello_usb >>> apcsmart-old clone-outlet mge-utalk safenet >>> apcupsd-ups dummy-ups microdowell solis >>> bcmxcp etapro nutdrv_at...