Re: [Nut-upsuser] Help with Elite 800VA usb UPS

[Andrea de Lutti]

Thanks mates,
as suggested I have added

runtimecal = 240,100,720,50
default.battery.voltage.low = 10.4
default.battery.voltage.high = 13.8 (the actual charging voltage)

In ups.conf

I have also added the startup procedure in rc.local file, everything is
fine...
I have only to make a deep test.

Is there a way to add a NOTIFYMSG value for the battery test?

Thank you lots

Andrea

2017-06-16 14:50 GMT+02:00 Charles Lepple :

> On Jun 16, 2017, at 2:20 AM, Andrea de Lutti  wrote:
> > Using 'guestimation' (low: -0.87, high: -1.08)!
> > Initial battery charge undetermined
> > Driver failed to start (exit status=1)
>
> The "low" and "high" voltages should correspond to the battery voltage
> when it is discharged (LB) and charged, respectively. For a 12V (nominal)
> battery, they should not be less than zero :-)
>
> There is a check for whether the nominal battery voltage is 1, but it
> should be looking for -1. (This has been fixed in nutdrv_qx, but was not
> backported to blazer*)
>
> As Manuel suggested, you can use the "defaults.battery.voltage.low" and
> "defaults.battery.voltage.high" options in ups.conf - there is a bit of a
> chicken-and-egg problem here, but you can still put in approximate values
> (say, 10.4 and 13.0) in order to run the calibration, and then adjust them
> to the actual reported values.
>
>
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Help with Elite 800VA usb UPS (/var/run/nut on Ubuntu 16.04)

[Charles Lepple]

On Jun 11, 2017, at 8:10 AM, Andrea de Lutti  wrote:
> 
> What's the right procedure for loading driver/daemon at boot?
> I have read a lot about /var/run/nut missing, but haven't find any 
> solution

Your copy of /etc/init.d/nut-server should have the following lines:

# Check if /var/run/nut exists and has the correct perms
check_var_directory() {
  [ ! -d ${pid_dir} ] && mkdir -p ${pid_dir} \
&& chown root:nut ${pid_dir} \
&& chmod 770 ${pid_dir} \
&& [ -x /sbin/restorecon ] && /sbin/restorecon ${pid_dir}
}

This works on my Ubuntu 16.04 test system. I am using a PPA with some 
libusb-1.0 changes, but this particular file does not seem to have changed 
since Ubuntu 14.04 (looks like there is some systemd emulation of SysV-style 
init scripts for NUT on 16.04). Are you using systemd or upstart?
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

[Charles Lepple]

On Jun 16, 2017, at 2:20 AM, Andrea de Lutti  wrote:
> Using 'guestimation' (low: -0.87, high: -1.08)!
> Initial battery charge undetermined
> Driver failed to start (exit status=1)

The "low" and "high" voltages should correspond to the battery voltage when it 
is discharged (LB) and charged, respectively. For a 12V (nominal) battery, they 
should not be less than zero :-)

There is a check for whether the nominal battery voltage is 1, but it should be 
looking for -1. (This has been fixed in nutdrv_qx, but was not backported to 
blazer*)

As Manuel suggested, you can use the "defaults.battery.voltage.low" and 
"defaults.battery.voltage.high" options in ups.conf - there is a bit of a 
chicken-and-egg problem here, but you can still put in approximate values (say, 
10.4 and 13.0) in order to run the calibration, and then adjust them to the 
actual reported values.



___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Unable to use nut-2.7.4 with Eaton 5E1500I USB

[Manuel Wolfshant]

On 06/15/2017 04:32 PM, Arnaud Quette wrote:

Hello



 still no reply from them ...

is the guy you contacted Paul Henri?


I wrote to a generic alias ( Ro-PQSupport ). Got a reply from a fellow 
Romanian who also CC:ed something looking like a list 
(List-EGPQCO-BUCRO-PQ ). I replied to both of them 5 days ago, received 
nothing since.






Would you also be able to test some github code?
We have the libusb-1.0 branch that provides both libusb 1.0
support (interesting to test to see if the problem still
happens) along with few other improvements (though these should
not help for your issue):
https://github.com/networkupstools/nut/tree/libusb-1.0





argh, no improvement, but still with libusb 0.1.
do you have libusb 1.0 -devel package installed? With that libusb1.0 
nut branch, if both 1.0 and 0.1 are available, 1.0 will take precedence.
I just tried using libusb-1.0 instead of 0.1 (the only change I did was 
to replace libusb 0.1-devel with libusb 1.0-devel in the buildroot ) but 
it did not fly. I'll try to see what was missing and fix:


libtool: link: gcc -I../include -I/usr/include/libusb-1.0 
-DNETSNMP_ENABLE_IPV6 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 
-mtune=generic -D_RPM_4_4_COMPAT -Ulinux -Dlinux=linux 
-I/usr/include/rpm -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe 
-fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -I/usr/lib64/perl5/CORE -I/usr/include 
-I/usr/include/neon -I/usr/include/modbus -O2 -g -pipe -Wall 
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
--param=ssp-buffer-size=4 -m64 -mtune=generic -Wl,-z -Wl,now -Wl,-z 
-Wl,relro -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions 
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -o 
snmp-ups snmp-ups.o apc-mib.o baytech-mib.o compaq-mib.o eaton-mib.o 
ietf-mib.o mge-mib.o netvision-mib.o powerware-mib.o raritan-pdu-mib.o 
bestpower-mib.o cyberpower-mib.o delta_ups-mib.o xppc-mib.o huawei-mib.o 
eaton-ats16-mib.o apc-ats-mib.o raritan-px2-mib.o eaton-ats30-mib.o 
apc-pdu-mib.o main.o dstate.o -Wl,-z -Wl,relro -Wl,-z -Wl,now  
../common/.libs/libcommon.a ../common/.libs/libparseconf.a -L/usr/lib64 
-lnetsnmp -lpthread

nutdrv_qx-nutdrv_qx.o: In function `ippon_command':
/builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:679: undefined 
reference to `libusb_strerror'
/builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:692: undefined 
reference to `libusb_strerror'

nutdrv_qx-nutdrv_qx.o: In function `fabula_command':
/builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:907: undefined 
reference to `libusb_strerror'

nutdrv_qx-nutdrv_qx.o: In function `krauler_command':
/builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:770: undefined 
reference to `libusb_strerror'

nutdrv_qx-nutdrv_qx.o: In function `sgs_command':
/builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:542: undefined 
reference to `libusb_strerror'
nutdrv_qx-nutdrv_qx.o:/builddir/build/BUILD/nut-libusb-1.0/drivers/nutdrv_qx.c:568: 
more undefined references to `libusb_strerror' follow

collect2: ld returned 1 exit status
make[1]: *** [nutdrv_qx] Error 1
[...]


libtool: link: gcc -I../include -I/usr/include/libusb-1.0 
-DNETSNMP_ENABLE_IPV6 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
-fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 
-mtune=generic -D_RPM_4_4_COMPAT -Ulinux -Dlinux=linux 
-I/usr/include/rpm -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe 
-fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -I/usr/lib64/perl5/CORE -I/usr/include 
-I/usr/include/neon -I/usr/include/modbus -O2 -g -pipe -Wall 
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
--param=ssp-buffer-size=4 -m64 -mtune=generic -Wl,-z -Wl,now -Wl,-z 
-Wl,relro -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions 
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -o 
bcmxcp_usb bcmxcp_usb.o bcmxcp.o usb-common.o main.o dstate.o 
../common/.libs/libcommon.a ../common/.libs/libparseconf.a -lusb-1.0 -lm 
-lpthread

bcmxcp_usb.o: In function `nutusb_open':
/builddir/build/BUILD/nut-libusb-1.0/drivers/bcmxcp_usb.c:515: undefined 
reference to `libusb_strerror'
/builddir/build/BUILD/nut-libusb-1.0/drivers/bcmxcp_usb.c:504: undefined 
reference to `libusb_strerror'

collect2: ld returned 1 exit status
make[1]: *** [bcmxcp_usb] Error 1
libusb1.o: In function `nut_libusb_strerror':
/builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:484: undefined 
reference to `libusb_strerror'
/builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:469: undefined 
reference to `libusb_strerror'
/builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:479: undefined 
reference to `libusb_strerror'

libusb1.o: In function `nut_libusb_open':
/builddir/build/BUILD/nut-libusb-1.0/drivers/libusb1.c:181: 

Re: [Nut-upsuser] Help with Elite 800VA usb UPS

[Andrea de Lutti]

Hi, it's me again.
I haven't yet tested my UPS with full load, but I have tried to insert some
values in ups.conf, I have kept the example on the blazer_usb driver help
page:

runtimecal = 240,100,720,50


When I try to start the driver, I receive

root@artu:~# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.2
Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
Supported UPS detected with megatec protocol
Rating information unavailable
Vendor information unavailable
No values provided for battery high/low voltages in ups.conf

Using 'guestimation' (low: -0.87, high: -1.08)!
Initial battery charge undetermined
Driver failed to start (exit status=1)

What should I do?
Thanks again,

Andrea

2017-06-12 12:34 GMT+02:00 Manuel Wolfshant :

> On 06/12/2017 12:56 PM, Andrea de Lutti wrote:
>
>
>
>> > I have also successfully tested the battery...
>> >
>> >  upscmd -uadmin -pups Elit@artu test.battery.start.quick
>>
>> I would also recommend testing the shutdown procedure and making sure
>> that everything works as expected on power failures.
>> Please, let us know the results of these tests, so that we can add a
>> more informed report about your device to our library
>> (http://networkupstools.org/ddl/).
>>
>
> ​Nice, I would like to test it, but if I don't have battery runtime value
> and / or battery charge, how may I test it correctly?
> I have seen also some strange values for battery.voltage.high and
> battery.voltage.loware they correct?
>
> run with a test load   ( at least twice, for 50% and 100% load for
> instance ) and write down the periods between full charge and shutdown.
> Then you can use runtimecal in ups.conf to obtain guestimations during
> normal usage
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser