[Nut-upsdev] Fwd: [networkupstools/nut] Riello IDG400 wrong values & not powering off (#530)

[Charles Lepple]

Elio or others at Riello, can you please check out the following issue on Github?

https://github.com/networkupstools/nut/issues/530

From: latimeria
Subject: [networkupstools/nut] Riello IDG400 wrong values & not powering off (#530)
Date: February 25, 2018 at 12:06:14 PM EST
Hello,
1: it shows battery charge 255% - battery.runtime 3932100 - Runtime (H:M:S): 1092:15:00
is this an hardware problem or something on Nut side?
2: I use a raspberry as nut server to shutdown all lan clients after 180 seconds without main power; the old ups was also powered off after FINALDELAY 5 seconds while the Riello keeps staying on battery; is this something related to the first problem?
Thanks

[Charles Lepple]

Hi Charles,
this type of UPS doesn't support realtime autonomy calculation, instead a fixed countdown must be used.
How we can fix non supported values?

If a value is not supported, the driver should not publish it with the dstate API. Dhould the driver be modified to not return battery.charge if the UPS returns 0xFF? Are there other variables that are affected?

(I don't think the IDG400 is covered in the protocol documentation that the NUT project received a while back.)

For the point number 2, as we know NUT perfomrs the shutdown after battery low signal with a delay of 5 seconds as specified in the FINALDELAY.
Is this correct?

Right, NUT tells the computer to shut down, but it also typically sends a shutdown signal to the UPS. Does the IDG400 also respond to the same shutdown command as others?

[Elio Parisi]

Hi Charles,
attached there is a patch for a new version of riello drivers:

Changes:

- small changes in riello_usb.c and riello_ser that solved problem with UPS that not support realtime autonomy calculation (and also internal temperature);
- the second problem I think is related to the first because the shutdown command that I sent to UPS by NUT monitor works without problems;

Cheers,
Elio Parisi.

-----Messaggio originale-----
Da: Charles Lepple [mailto:***@gmail.com]
Inviato: lunedì 26 febbraio 2018 14:56
A: Elio Parisi <***@riello-ups.com>
Cc: nut-upsdev Nut Developer Mailing List <nut-***@lists.alioth.debian.org>
Oggetto: Re: [networkupstools/nut] Riello IDG400 wrong values & not powering off (#530)

Hi Charles,
this type of UPS doesn't support realtime autonomy calculation, instead a fixed countdown must be used.
How we can fix non supported values?

If a value is not supported, the driver should not publish it with the dstate API. Dhould the driver be modified to not return battery.charge if the UPS returns 0xFF? Are there other variables that are affected?

(I don't think the IDG400 is covered in the protocol documentation that the NUT project received a while back.)

For the point number 2, as we know NUT perfomrs the shutdown after battery low signal with a delay of 5 seconds as specified in the FINALDELAY.
Is this correct?

Right, NUT tells the computer to shut down, but it also typically sends a shutdown signal to the UPS. Does the IDG400 also respond to the same shutdown command as others?

[Charles Lepple]

Post by Elio Parisi
- the second problem I think is related to the first because the shutdown command that I sent to UPS by NUT monitor works without problems;

Can you please weigh in on the discussion on GitHub?

https://github.com/networkupstools/nut/issues/530#issuecomment-370947318