[Nut-upsuser] Riello Dialog Plus UPS

[Arjen de Korte]

Massimiliano Giorgi wrote:

> when genericups start it write
> 
> "parse_output_signals: SD overriden with ST"
> 
> so I suppose that this setting was in use but (you  are right) probably
> is inefective

The above line was executed in the wrong place. We never get there when
commanding the UPS to shutdown. :-)

[...]

> this morning I have test the UPS running "upsmon -c fsd"... the system
> goes down but the UPS remain online (with and without the main present)..
> I have look at the source (the trunk) of genericups.c: in the
> upsdrv_shutdown function there is a
> 
> tcsendbreak(upsfd, 4901)
> 
> why 4901?

The only thing I can tell, is historic reasons. The duration for the
break is implementation dependent, so there is no way to tell how long
it will be.

> (PS: anyway the version of nut I have does not execute this line)

I warned you for that, didn't I? ;-)

> I have written some line of C to send a break to the ups...
> using a delay of 4901 has no effect (with and without main);
> the man page of tcsendbreak on my system tells that " If duration is not
> zero, it sends zero-valued bits for some implementation-defined length
> of time."; on my system the duration seems to be the delay in
> milliseconds; I have tried 20000... nothing... but with 25000:
> 
> with the main present... nothing...

This is not uncommon, most contact closure type UPS'es will ignore the
shutdown command when not on battery.

> without the main... the UPS has been killed immediatly (well, after a
> delay of ~20 seconds after the execution of the tcsendbreak)...

We should probably make this value configurable. What works for you now,
might break on other systems. So the best I can offer here, is to create
a way to override the build in default value.

> if the
> main return the UPS go up and power all the output (I does not know what
> happens if the main return and the battery is low... I hope the ups wait
> until the battery is partially charged prior to power the output)

Don't count on that. :-(

We have some words about situations like this in the FAQ and documentation.

Best regards, Arjen