from:"Andrea de Lutti"

[Nut-upsuser] (no subject)

2017-07-05 Thread Andrea de Lutti

2017-07-05 13:32 GMT+02:00 Charles Lepple <clep...@gmail.com>:

> On Jul 5, 2017, at 7:05 AM, Andrea de Lutti <adelu...@gmail.com> wrote:
> >
> > Which are the ups.status I can use with ups in dummy mode?
> > I have seen only OB, LB, OL...
> >
> Those are the ones that upsmon will respond to. The dummy-ups driver
> accepts any string, AFAIK.
>
> Others: http://networkupstools.org/docs/developer-guide.chunked/
> ar01s04.html#_manipulating_the_data
> ___
>

What if I would like to implement a notification for [OL CAL] status
during battery calibration?
___
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

2017-07-05 Thread Andrea de Lutti

Thank you lots! Finally I have everything working!
Which are the ups.status I can use with ups in dummy mode?
I have seen only OB, LB, OL...

thank you
Andrea

2017-07-04 19:55 GMT+02:00 Charles Lepple <clep...@gmail.com>:

> On Jul 3, 2017, at 11:06 AM, Andrea de Lutti <adelu...@gmail.com> wrote:
> >
> > I would like that NOTIFYCMD points to upssched.
> >
> If I understand correctly, Roger is pointing out that your configuration
> is confusing upssched and upssched-script.
>
> Since you are using Ubuntu, upsmon.conf should contain "NOTIFYCMD
> /sbin/upssched". Similarly, upssched.conf should contain "CMDSCRIPT
> /usr/local/bin/upssched-script".
>
> Not sure if those passwords in the script are real, but if they are, you
> will want to change them now.
> ___
> Nut-upsuser mailing list
> Nut-upsuser@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
>
___
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

2017-07-03 Thread Andrea de Lutti

>
>
>
> MONITOR dummy@artu 1 user pass master
>> SHUTDOWNCMD "/sbin/shutdown -h +0"
>> NOTIFYCMD /usr/local/bin/upssched-script
>>
>
> Hi, As far as I can see, what you are getting in syslog corresponds
> correctly to what you have specified.  You have specified that upsmon is to
> call upssched-script _directly_.  This means that the argument to the
> script call will be the NOTIFYMSG value.  But in upssched-script you are
> testing for the notifytype, e.g. ONBATT.
>
> Did you want that, or did you want NOTIFYCMD to point to upssched?
>
> If I may throw away modesty, see chapter 4 in
> http://rogerprice.org/NUT/ConfigExamples.A5.pdf which has a diagram and a
> fully worked example.
>
> Roger
>
>
>> Hi Roger,
thanks for your reply.
My intention is to set my email script when some event occurs (on battery
and so on).
in chapter 4.2 you mention

The NOTIFY events detected by upsmon and flagged as EXEC in upsmon.conf
become events for upssched when NOTIFYCMD points to upssched.

I would like that NOTIFYCMD points to upssched.

Thank you lots,
Andrea


___
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

2017-07-03 Thread Andrea de Lutti

Ok, I am running NUT in dummy mode.
I have added a new ups in ups.conf

[dummy]
driver = dummy-ups
port = upsc.dev
desc = "dummy ups for testing purposes"

upsc.dev has been generated by exporting the Elit configuration.

I have added the monitor line in upsmon.conf and the "exec" flags (all the
events)

MONITOR dummy@artu 1 user pass master
SHUTDOWNCMD "/sbin/shutdown -h +0"
NOTIFYCMD /usr/local/bin/upssched-script
NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC
NOTIFYFLAG FSD SYSLOG+WALL+EXEC
NOTIFYFLAG COMMOK SYSLOG+WALL+EXEC
NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC
NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC
NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC
NOTIFYFLAG NOCOMM SYSLOG+WALL+EXEC
NOTIFYFLAG NOPARENT SYSLOG+WALL+EXEC

The upssched-script is

#! /bin/sh
case "$1" in
"ONBATT")
echo "On batt" | mailx -v -r "adelu...@gmail.com" -s "TEST NUT
object" -S smtp="smtp.gmail.com:587" -S smtp-use-starttls -S
smtp-auth=login -S smtp-auth-user="adelu...@gmail.com" -S
smtp-auth-password="gtmtnqyelhlumyds" -S ssl-verify=ignore
adelutti+ser...@gmail.com
;;
"ONLINE")
echo "On power" | mailx -v -r "adelu...@gmail.com" -s "TEST NUT
object" -S smtp="smtp.gmail.com:587" -S smtp-use-starttls -S
smtp-auth=login -S smtp-auth-user="adelu...@gmail.com" -S
smtp-auth-password="gtmtnqyelhlumyds" -S ssl-verify=ignore
adelutti+ser...@gmail.com
;;
"LOWBATT")
echo "LOWBATT" | mailx -v -r "adelu...@gmail.com" -s "TEST NUT
object" -S smtp="smtp.gmail.com:587" -S smtp-use-starttls -S
smtp-auth=login -S smtp-auth-user="adelu...@gmail.com" -S
smtp-auth-password="gtmtnqyelhlumyds" -S ssl-verify=ignore
adelutti+ser...@gmail.com
;;
*)
logger -t upssched-cmd "Unrecognized command: $1"
;;
esac

while upssched.conf is

# Network UPS Tools - upssched.conf sample file
#
#

CMDSCRIPT /usr/local/bin/upssched-script
PIPEFN /var/run/nut/upssched/upssched.pipe
LOCKFN /var/run/nut/upssched/upssched.lock

AT ONBATT * EXECUTE onbattwarn
AT ONLINE * EXECUTE ups-back-on-power

Running upson in debug mode I can see the change of the status (I have a
cycle of 30 secs for online/batterry/low battery) but the syslog reports

Jul  3 16:17:15 artu upsmon[4685]: UPS dummy@artu on battery
Jul  3 16:17:15 artu upssched-cmd: Unrecognized command: UPS dummy@artu on
battery
Jul  3 16:17:45 artu upsmon[4685]: UPS dummy@artu battery is low
Jul  3 16:17:45 artu upssched-cmd: Unrecognized command: UPS dummy@artu
battery is low
Jul  3 16:18:15 artu upsmon[4685]: UPS dummy@artu on line power
Jul  3 16:18:15 artu upssched-cmd: Unrecognized command: UPS dummy@artu on
line power
Jul  3 16:18:45 artu upsmon[4685]: UPS dummy@artu on battery
Jul  3 16:18:45 artu upssched-cmd: Unrecognized command: UPS dummy@artu on
battery
Jul  3 16:18:57 artu systemd[1]: Started CUPS Scheduler.
Jul  3 16:19:15 artu upsmon[4685]: UPS dummy@artu battery is low
Jul  3 16:19:15 artu upssched-cmd: Unrecognized command: UPS dummy@artu
battery is low

I have tried so many commands, but always the same result...

PS: this evening I will change the battery, I have some standby/cycle
voltage declared by the manufacturer: should I use them?

Thank you,
Regards

Andrea

2017-06-29 14:59 GMT+02:00 Andrea de Lutti <adelu...@gmail.com>:

>
>> Bear in mind that upsmon runs as user "nut" on Ubuntu, as does the
>> NOTIFYCMD script. At one point, you said that the script is in /root, which
>> is not commonly readable by other users. Does the script work if you move
>> it to, say, /usr/local/bin?
>>
>> (With Ubuntu 16.04, there should be some error messages from upsmon in
>> 'journalctl' referencing permissions.)
>>
>> I have tried running from /etc/nut, now moved in /usr/local...will keep
> you informed
>
>
>
>> Under the Bugs heading, the man page says "Instant commands are not yet
>> supported in Dummy Mode..." - one of the use cases was automated developer
>> testing of NUT, and there isn't much use in simulating all of the commands
>> in that case. "load.off" is probably worth implementing at some point for
>> user testing.
>>
>> So for your use case, the timers would probably be the easiest way with
>> the current code.
>
>
> Ok, I am testing it, thank you
>
>
___
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

2017-06-29 Thread Andrea de Lutti

> > , but when in battery test I have OL CAL status: it would be good to
> have the result.
>
> "OL CAL" or "OB CAL"? If the UPS is powering the load from the battery
> during calibration, it should report "OB CAL". The ONBATT handler in
> NOTIFYCMD can check for CAL at that point.
>
> I don't think we considered the case where CAL is paired with OL.
>
> I confirm it, during battery testing I have OL CAL



> > Anyway I still not receive any email on any test (power cord
> disconnected and/or reconnected for example)
>
> Oh, I misinterpreted "working script" as a script that was sending email,
> rather than work-in-progress. Does that same command work from the command
> line? Can you add something like "logger" before the mailx line to be sure
> that the script is executing properly? Be sure to "chmod a+x" the script.
>

Yep, the script works flawlessy with a command line. It is a "modified"
script from other jobs, and I receive daily all the emails from them

>
> I forget if I mentioned this earlier, but for testing notifications, you
> can use the dummy-ups driver:
>
>http://networkupstools.org/docs/man/dummy-ups.html
>
> The timer example will simulate the OL-OB-LB transition.
>

Maybe I have missing someting. I have exported my configuration to a .dev
file, and then used for dummy ups, configured as dummy. Do i need to make
circular tests (timer configuration) or may I do them manually? Just
beacuse the only command allowed in dummy mode (upscmd -l dummy@artu) is
load.off


> > Does the runtime calibration test alter the values of ups.conf? Or do I
> have to change it manually? Which would be the right procedure for changing
> the battery for calibrating NUT (over the manufacturer's suggestions)?
>
> The automatic calibration/battery test invoked by upscmd (or the UPS front
> panel button, if any) is for the UPS low battery warning.
>
> The manual calibration ups.conf parameters are necessary (and need to be
> maintained separately) because Qx-based protocols do not all report the
> state-of-charge as calculated by the UPS.
>
> I would recommend both forms of calibration after replacing the battery.
>
> Ok, thanks. I will replace the battery and test it
___
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

2017-06-27 Thread Andrea de Lutti

Sorry, I didn't received it...
I don't have any REPLBATT message, but when in battery test I have OL CAL
status: it would be good to have the result.
Anyway I still not receive any email on any test (power cord disconnected
and/or reconnected for example)

Does the runtime calibration test alter the values of ups.conf? Or do I
have to change it manually? Which would be the right procedure for changing
the battery for calibrating NUT (over the manufacturer's suggestions)?

Thank you lots,
Andrea

2017-06-27 14:50 GMT+02:00 Charles Lepple <clep...@gmail.com>:

> On Jun 26, 2017, at 7:03 AM, Andrea de Lutti <adelu...@gmail.com> wrote:
> >
> > Are there no warnings for battery test?
>
> not sure if you saw my reply on 2016-06-17:
>
> Do you mean a notification that a test is in progress, or something for
> the results?
>
> There is the REPLBATT message in upsmon when the battery test fails, but I
> don't think the generic Qx protocol supports the RB status flag.
>
> You could possibly trigger on the OB status and look for the CAL flag in
> ups.status as well, but I haven't tried to automate that.
>
> ^^^ If you run "upsc $UPSNAME ups.status", do you see CAL in the status
> string during a battery test? If not, your UPS is not reporting this the
> way that the driver expects.
___
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

2017-06-26 Thread Andrea de Lutti

Good morning again,
I have finished some tests and the driver works perfectly for shutting down
the server and a client, both Ubuntu 16.04.
I have to change the battery, I am unable to test with 100% load and now I
have 5 minutes of battery power with a load of 18%.

I am still unable to send email notifications, I have enabled all the
warnings in upsmon.conf:

 NOTIFYFLAG ONLINESYSLOG+WALL+EXEC
 NOTIFYFLAG ONBATTSYSLOG+WALL+EXEC
 NOTIFYFLAG LOWBATTSYSLOG+WALL+EXEC
 NOTIFYFLAG FSDSYSLOG+WALL+EXEC
 NOTIFYFLAG COMMOKSYSLOG+WALL+EXEC
 NOTIFYFLAG COMMBADSYSLOG+WALL+EXEC
 NOTIFYFLAG SHUTDOWNSYSLOG+WALL+EXEC
 NOTIFYFLAG REPLBATTSYSLOG+WALL+EXEC
 NOTIFYFLAG NOCOMMSYSLOG+WALL+EXEC
 NOTIFYFLAG NOPARENTSYSLOG+WALL+EXEC

and enabled my email script:

NOTIFYCMD /root/mailnotify.sh

This is my working script:

#!/bin/sh

echo "$UPSNAME in is $NOTIFYTYPE state" | mailx -v -r "adelu...@gmail.com"
-s "$NOTIFYTYPE" -S smtp="smtp.gmail.com:587" -S smtp-use-starttls -S
smtp-auth=login -S smtp-auth-user="adelu...@gmail.com" -S
smtp-auth-password="mypassword" -S ssl-verify=ignore
adelutti+ser...@gmail.com;

Are there no warnings for battery test?

Thank you,
Andrea






2017-06-16 15:19 GMT+02:00 Andrea de Lutti <adelu...@gmail.com>:

> 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 <clep...@gmail.com>:
>
>> On Jun 16, 2017, at 2:20 AM, Andrea de Lutti <adelu...@gmail.com> 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

2017-06-16 Thread 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 <clep...@gmail.com>:

> On Jun 16, 2017, at 2:20 AM, Andrea de Lutti <adelu...@gmail.com> 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

2017-06-16 Thread 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 <wo...@nobugconsulting.ro>:

> 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

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

2017-06-14 Thread 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 hel
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 17:34 GMT+02:00 Andrea de Lutti <adelu...@gmail.com>:

> Thanks a lot, I will do it and keep you informed.
> Best regards
>
> Andrea
>
> 2017-06-12 12:34 GMT+02:00 Manuel Wolfshant <wo...@nobugconsulting.ro>:
>
>> 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

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

2017-06-12 Thread Andrea de Lutti

Thanks a lot, I will do it and keep you informed.
Best regards

Andrea

2017-06-12 12:34 GMT+02:00 Manuel Wolfshant <wo...@nobugconsulting.ro>:

> 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

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

2017-06-12 Thread Andrea de Lutti

>
> > root@artu:~# upsc Elit@artu
> > Init SSL without certificate database
> > battery.voltage: 13.90
> > battery.voltage.high: -1.08
> > battery.voltage.low: -0.87
> > device.type: ups
> > driver.name: blazer_usb
> > driver.parameter.pollinterval: 2
> > driver.parameter.port: auto
> > driver.version: 2.7.2
> > driver.version.internal: 0.11
> > input.frequency: 50.0
> > input.voltage: 228.7
> > input.voltage.fault: 140.0
> > output.voltage: 226.5
> > ups.beeper.status: enabled
> > ups.delay.shutdown: 30
> > ups.delay.start: 180
> > ups.load: 16
> > ups.productid: 
> > ups.status: OL
> > ups.temperature: 30.0
> > ups.type: offline / line interactive
> > ups.vendorid: 
>
> Glad it works.
>

Yep! :)

>
>
> > 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?

TY

Andrea
___
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

2017-06-11 Thread Andrea de Lutti

Soseems so better...

Each time I rebbot, I miss the /var/run/nut folder...

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)
Can't chdir to /var/run/nut: No such file or directory
Driver failed to start (exit status=1)

root@artu:~# upsd
Network UPS Tools upsd 2.7.2
fopen /var/run/nut/upsd.pid: No such file or directory
listening on 192.168.1.1 port 3493
listening on 127.0.0.1 port 3493
Can't chdir to /var/run/nut: No such file or directory

Once manually created ad giving permission to nut group, I can start the
driver and the daemon:

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

root@artu:~# upsd -c reload
Network UPS Tools upsd 2.7.2
.08)!
Battery runtime will not be calculated (runtimecal not set)


root@artu:~# upsc Elit@artu
Init SSL without certificate database
battery.voltage: 13.90
battery.voltage.high: -1.08
battery.voltage.low: -0.87
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.7.2
driver.version.internal: 0.11
input.frequency: 50.0
input.voltage: 228.7
input.voltage.fault: 140.0
output.voltage: 226.5
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 16
ups.productid: 
ups.status: OL
ups.temperature: 30.0
ups.type: offline / line interactive
ups.vendorid: 

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

I have also successfully tested the battery...

 upscmd -uadmin -pups Elit@artu test.battery.start.quick

Thank you lots,
Andrea


2017-06-11 5:31 GMT+02:00 Daniele Pezzini :

> > Starting the driver with debug level 5 seems happier, but continue to
> cycle
>
> It is meant to 'cycle', it's working correctly.
> When you run the driver normally (i.e. not in debug mode), you don't
> see all that output (plus, after having established a connection with
> the device, the driver goes into the background), but it's doing
> exactly the same thing.
>
> > nutdrv_qx
> >
> > rroot@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)
> > Can't chdir to /var/run/nut: No such file or directory
> > Driver failed to start (exit status=1)
> >
> > but with blazer_usb seems better
> >
> > 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)!
> > Battery runtime will not be calculated (runtimecal not set)
> >
> > but
> >
> > root@artu:~# upsc Elit@artu
> > Error: Connection failure: Connection refused
>
> Also, remember that, if you launch upsd and then you change the
> content of ups.conf (for example, changing the driver of your UPS from
> 'nutdrv_qx' to 'blazer_usb'), you need to reload its configuration
> (upsd -c reload) or restart it (mandatory, if it's running in debug
> mode).
>
> So, let's try this:
> 1. stop all NUT-related services,
> 2. make sure to have the right things in your ups.conf (i.e. your UPS
> configured for driver 'blazer_usb'),
> 3. launch upsd,
> 4. launch the driver,
> 5. now check the values with upsc: what happens?
>
___
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

2017-06-10 Thread Andrea de Lutti

>
> hmm, apparently the UPS doesn't close the replies to our queries with
> the expected CR and we (I) did not consider that case in nutdrv_qx --
> noted:
> https://github.com/networkupstools/nut/issues/441
>
> But blazer_usb, being less strict on the terminating CR of Q1 replies,
> should work with your device.
>
> > root@artu:~# upsc Elit@artu
> > Init SSL without certificate database
> > Error: Driver not connected
>
> aehm, was the blazer_usb driver running?
>

This was tested with 

nutdrv_qx

rroot@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)
Can't chdir to /var/run/nut: No such file or directory
Driver failed to start (exit status=1)

but with blazer_usb seems better

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)!
Battery runtime will not be calculated (runtimecal not set)

but

root@artu:~# upsc Elit@artu
Error: Connection failure: Connection refused

Starting the driver with debug level 5 seems happier, but continue to cycle

root@artu:~# /lib/nut/blazer_usb -a Elit -u nut -D
Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
   0.00 debug level is '5'
   0.415024 Checking device (1D6B/0001) (006/001)
   0.478033 - VendorID: 1d6b
   0.478074 - ProductID: 0001
   0.478081 - Manufacturer: unknown
   0.478089 - Product: unknown
   0.478096 - Serial Number: unknown
   0.478103 - Bus: 006
   0.478109 Trying to match device
   0.478120 Device does not match - skipping
   0.478193 Checking device (1D6B/0001) (005/001)
   0.541928 - VendorID: 1d6b
   0.542215 - ProductID: 0001
   0.542370 - Manufacturer: unknown
   0.542525 - Product: unknown
   0.542673 - Serial Number: unknown
   0.542818 - Bus: 005
   0.542959 Trying to match device
   0.543981 Device does not match - skipping
   0.544060 Checking device (/) (004/004)
   0.560313 - VendorID: 
   0.560574 - ProductID: 
   0.560700 - Manufacturer:
   0.560833 - Product: 010937
   0.560958 - Serial Number:
   0.561081 - Bus: 004
   0.561205 Trying to match device
   0.561332 Device matches
   0.793308 send_to_all: SETINFO ups.vendorid ""
   0.793568 send_to_all: SETINFO ups.productid ""
   0.793711 send_to_all: SETINFO device.type "ups"
   0.793897 send_to_all: SETINFO driver.version "2.7.2"
   0.794035 send_to_all: SETINFO driver.version.internal "0.11"
   0.794164 send_to_all: SETINFO driver.name "blazer_usb"
   0.794289 Trying megatec protocol...
   0.794402 send: Q1
   1.027417 received 46 (40)
   1.027475 read: (221.8 140.0 220.6 015 50.0 13.8 30.0 1001
   1.027758 send_to_all: SETINFO input.voltage "221.8"
   1.027796 send_to_all: SETINFO input.voltage.fault "140.0"
   1.027839 send_to_all: SETINFO output.voltage "220.6"
   1.027903 send_to_all: SETINFO ups.load "15"
   1.027944 send_to_all: SETINFO input.frequency "50.0"
   1.027970 send_to_all: SETINFO battery.voltage "13.80"
   1.027990 send_to_all: SETINFO ups.temperature "30.0"
   1.028011 send_to_all: SETINFO ups.beeper.status "enabled"
   1.028031 send_to_all: SETINFO ups.type "offline / line interactive"
   1.028049 send_to_all: SETINFO ups.status "OL"
   1.028058 Status read in 1 tries
   1.028067 Supported UPS detected with megatec protocol
   1.028077 send: F
   1.150426 received 21 (35)
   1.150482 read: #220.0 000 012.0 50.0
   1.150492 blazer_rating: short reply
   1.150510 Rating read 1 failed
   1.150520 send: F
   1.273356 received 21 (35)
   1.273397 read: #220.0 000 012.0 50.0
   1.273402 blazer_rating: short reply
   1.273407 Rating read 2 failed
   1.273418 send: F
   1.396336 received 21 (35)
   1.396380 read: #220.0 000 012.0 50.0
   1.396386 blazer_rating: short reply
   1.396392 Rating read 3 failed
   1.396403 Rating information unavailable
   1.396411 send: I
   1.591274 received 38 (35)
   1.591622 read: #   TR00094S
   1.591816 blazer_vendor: short reply
   1.591925 Vendor information read 1 failed
   1.591938 send: I
   1.785267 received 38 (35)
   1.785641 read: #   TR00094S
   1.785879 blazer_vendor: short reply
   1.786077 Vendor information read 2 failed
   1.786275 send: I
   1.980336 received 38 (35)
   1.980814 read: #   TR00094S
   1.981136 blazer_vendor: short reply
   1.981417 Vendor information read 3

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

2017-06-09 Thread Andrea de Lutti

Use the name from ups.conf in front of "@localhost".

The result is quite different ;)

root@artu:~# upsc Elit@artu
Init SSL without certificate database
Error: Driver not connected



> What if you try nutdrv_qx without specifying megatec? (It should
> autodetect.)
>

Here is the result:


 root@artu:~# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.2
Network UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2)
USB communication driver 0.32
Device not supported!
Device not supported!
Driver failed to start (exit status=1)


> If that doesn't work, please try to get some logs - they will look like
> this:
>
>http://lists.alioth.debian.org/pipermail/nut-upsuser/
> 2017-March/010555.html
>
> The author of the driver recommends a debug level of 5: "-D"
>
> (Note that we are not looking for the debug output for upsdrvctl, but
> rather for nutdrv_qx. If you pass "-D" flags to upsdrvctl, it should tell
> you how to start the driver in debug mode instead.)


Here is the output of debug level 5:


root@artu:~# /lib/nut/nutdrv_qx -a Elit -u nut -D
Network UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2)
USB communication driver 0.32
   0.00 debug level is '5'
   0.001187 upsdrv_initups...
   0.414464 Checking device (1D6B/0001) (006/001)
   0.477567 - VendorID: 1d6b
   0.477611 - ProductID: 0001
   0.477619 - Manufacturer: unknown
   0.477627 - Product: unknown
   0.477634 - Serial Number: unknown
   0.477648 - Bus: 006
   0.477656 Trying to match device
   0.477668 Device does not match - skipping
   0.477784 Checking device (1D6B/0001) (005/001)
   0.541404 - VendorID: 1d6b
   0.541733 - ProductID: 0001
   0.541933 - Manufacturer: unknown
   0.542124 - Product: unknown
   0.543843 - Serial Number: unknown
   0.543897 - Bus: 005
   0.543935 Trying to match device
   0.543978 Device does not match - skipping
   0.544122 Checking device (/) (004/004)
   0.561393 - VendorID: 
   0.561428 - ProductID: 
   0.561438 - Manufacturer:
   0.561443 - Product: 010937
   0.561457 - Serial Number:
   0.561461 - Bus: 004
   0.561466 Trying to match device
   0.561473 Device matches
   0.565355 send_to_all: SETINFO ups.vendorid ""
   0.565815 send_to_all: SETINFO ups.productid ""
   0.566137 send: QGS
   0.566421 read: QGS
   0.566708 qx_process_answer: short reply (input.voltage)
   0.567007 send: QGS
   0.567377 read: QGS
   0.567668 qx_process_answer: short reply (input.voltage)
   0.567965 send: QGS
   0.568256 read: QGS
   0.568609 qx_process_answer: short reply (input.voltage)
   0.568952 send: M
   0.569310 read: M
   0.569498 voltronic_qs_protocol: invalid protocol [M]
   0.569678 ups_infoval_set: failed to preprocess value
[ups.firmware.aux: M]
   0.569866 send: M
   0.570071 read: M
   0.570262 voltronic_qs_protocol: invalid protocol [M]
   0.570460 ups_infoval_set: failed to preprocess value
[ups.firmware.aux: M]
   0.570653 send: M
   0.570834 read: M
   0.571024 voltronic_qs_protocol: invalid protocol [M]
   0.571213 ups_infoval_set: failed to preprocess value
[ups.firmware.aux: M]
   0.571405 send: QS
   0.571587 read: QS
   0.571781 qx_process_answer: short reply (input.voltage)
   0.571973 send: QS
   0.572155 read: QS
   0.572343 qx_process_answer: short reply (input.voltage)
   0.572532 send: QS
   0.572716 read: QS
   0.572903 qx_process_answer: short reply (input.voltage)
   0.573093 send: D
   0.573288 read: D
   0.573481 qx_process_answer: short reply (input.voltage)
   0.573673 send: D
   0.573853 read: D
   0.574041 qx_process_answer: short reply (input.voltage)
   0.574236 send: D
   0.574414 read: D
   0.574600 qx_process_answer: short reply (input.voltage)
   0.574759 send: Q1
   0.807418 received 46 (40)
   0.807475 read: (225.3 140.0 222.6 015 49.9 13.8 30.0 1001
   0.807516 qx_process_answer: short reply (input.voltage)
   0.807548 send: Q1
   1.041418 received 46 (40)
   1.041472 read: (225.3 140.0 224.5 015 49.9 13.9 30.0 1001
   1.041487 qx_process_answer: short reply (input.voltage)
   1.041508 send: Q1
   1.275423 received 46 (40)
   1.275476 read: (225.3 140.0 222.6 015 49.9 13.9 30.0 1001
   1.275489 qx_process_answer: short reply (input.voltage)
   1.275511 send: Q1
   1.509410 received 46 (40)
   1.509463 read: (225.3 140.0 222.6 015 49.9 13.9 30.0 1001
   1.509501 qx_process_answer: short reply (input.voltage)
   1.509566 send: Q1
   1.743299 received 46 (40)
   1.743344 read: (225.3 140.0 222.6 015 49.9 13.9 30.0 1001
   1.743353 qx_process_answer: short reply (input.voltage)
   1.743365 send: Q1
   1.976367 received 46 (40)
   1.976428

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

2017-06-07 Thread Andrea de Lutti

Hi, I have tried several drivers for make my Elite UPS working.
With blazer_usb I can contact it, but I have no informations. This is the
best result.

OS: Ubuntu Xenial 16.04.2 LTS
NUT Version: Nut 2.7.2-4Ubuntu1 (Installed from Ubuntu Software Center)
Device name: Elite UPS 800VA (http://www.elit-ups.com/ita/pro_ups.html,
discontinued) I can provider their *not working* linux monitoring tool

Here is the result from starting upsdrvctl

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)!
Battery runtime will not be calculated (runtimecal not set)

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

[Nut-upsuser] (no subject)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

16 matches

Site Navigation

Mail list logo

Footer information