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

On Feb 26, 2018, at 4:58 AM, Elio Parisi <e.parisi at riello-ups.com>
wrote:
> 
> 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?

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:clepple at gmail.com] 
Inviato: luned? 26 febbraio 2018 14:56
A: Elio Parisi <E.Parisi at riello-ups.com>
Cc: nut-upsdev Nut Developer Mailing List <nut-upsdev at
lists.alioth.debian.org>
Oggetto: Re: [networkupstools/nut] Riello IDG400 wrong values & not powering
off (#530)

On Feb 26, 2018, at 4:58 AM, Elio Parisi <e.parisi at riello-ups.com>
wrote:
> 
> 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?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: riello.diff.gz
Type: application/x-gzip
Size: 593 bytes
Desc: riello.diff.gz
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20180226/fb06b665/attachment.bin>

On Feb 26, 2018, at 12:06 PM, Elio Parisi <e.parisi at riello-ups.com>
wrote:
> 	-	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