[Nut-upsdev] No answer from upsrw <ups name> command

[Charles Lepple]

copying the list for reference.

> On Feb 4, 2018, at 10:57 AM, Vitālijs Hodiko <hodiko.v at inbox.lv> wrote:
> 
> Thank you very much for a quick response. I tested nutdrv_qx driver and it's working just fine.
> 
> SETINFO battery.voltage "13.50"
> SETINFO device.type "ups"
> SETINFO driver.name "nutdrv_qx"
> SETINFO driver.parameter.pollfreq "30"
> SETINFO driver.parameter.pollinterval "2"
> SETINFO driver.parameter.port "auto"
> SETINFO driver.version "2.7.2"
> SETINFO driver.version.data "Q1 0.02"
> SETINFO driver.version.internal "0.06"
> SETINFO input.frequency "49.9"
> SETINFO input.voltage "224.1"
> SETINFO input.voltage.fault "223.6"
> SETINFO output.voltage "223.6"
> SETINFO ups.beeper.status "enabled"
> SETINFO ups.delay.shutdown "30"
> + ADDRANGE ups.delay.shutdown 12 600
> + SETFLAGS ups.delay.shutdown RW
> SETINFO ups.delay.start "180"
> + ADDRANGE ups.delay.start 0 599940
> + SETFLAGS ups.delay.start RW
> SETINFO ups.load "3"
> SETINFO ups.productid "0003"
> SETINFO ups.status "OL"
> SETINFO ups.temperature "25.0"
> SETINFO ups.type "offline / line interactive"
> SETINFO ups.vendorid "06da"
> ADDCMD beeper.toggle
> ADDCMD load.off
> ADDCMD load.on
> ADDCMD shutdown.return
> ADDCMD shutdown.stayoff
> ADDCMD shutdown.stop
> ADDCMD test.battery.start
> ADDCMD test.battery.start.deep
> ADDCMD test.battery.start.quick
> ADDCMD test.battery.stop
> DATAOK
> DUMPDONE
> 
> It even reports some RW variables, but as i understand from driver debug message they are built in into driver:
> > 2536.209109    setvar(ups.delay.start, 100)
> > 2536.209134    setvar: setting server side variable ups.delay.start
> > 2536.209149    setvar: SUCCEED
> > 2536.859612    upsdrv_updateinfo...
> > 2536.859626    Full update...
>  
> Best wishes,
> Vitaly
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20180204/e8aad8e3/attachment.html>