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...
> >
> T
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...@gmai
ccurs (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
___
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
A
> > , 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
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, a
ail.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.
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.86
, 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 ha
, 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
&g
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...
>> >
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 va
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 <hyo...@gmail.com>:
> > Starting the driver with d
>
> 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
8299 qx_process_answer: short reply (input.voltage)
3.608313 Device not supported!
3.608319 Device not supported!
It seems I am not so lucky...
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
untime 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
Arnaud Quette aquette.dev at gmail.com writes:
2011/6/13 Angela Williams angierfw at gmail.com
Hi All!
Hi Angela,
Just an update! The snmp driver seems quite happy with an APC AP9618 managment
card in an APC Smart-UPS RT 5000 XL UPS.
thanks for your report.I've just committed
to start UPS drivers!
Maybe i'm doing something wrong during compilation of the sources...
Thanks in advice,
Andrea
2011/3/30 Arjen de Korte nut+us...@de-korte.org:
Citeren Andrea krog...@gmail.com:
Exactly what benefit can i have using the new driver with this hack?
If nothing changes i can
drivers with this ups model feel free to contact me.
Andrea
2011/3/29 Arjen de Korte nut+us...@de-korte.org:
If you're able to build from sources, you can modify line 189 in
drivers/blazer.c from
if (blazer_command(cmd, buf, sizeof(buf)) 47) {
to
if (blazer_command(cmd, buf
detected [ VT12094S].
* Service upsdrv started
What can I do to use the new, still supported and developed blazer driver?
Many thanks
Andrea
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 232
Device Status: 0x0002
(Bus Powered)
Remote Wakeup Enabled
Many thanks!
Andrea
2011/3/28 Arjen de Korte nut+us...@de-korte.org
Citeren Andrea krog...@gmail.com
21 matches
Mail list logo
