Displaying 20 results from an estimated 34 matches for "dataok".
2011 Oct 24
2
2.6.0 bcmxcp_usb recovery question
...my server and my PW5115 UPS is removed, bcmxcp_usb reports DATASTALE (as it should) and continues to respond to PING (as it should). When the USB cable is reattached, bcmxcp_usb continues to report DATASTALE in response to DUMPALL even though lsusb indicates that the PW5115 is indeed connected and DATAOK is never reported in response to DUMPALL. If I restart the bcmxcp_usb driver with upsdrvctl then it recovers the connection to the UPS.
The bcmxcp_usb 2.4.1 would not respond to even a PING while the USB cable to the UPS was disconnected, but when the USB cable was reconnected then it would begin...
2014 Jun 26
1
The dreaded Tripp Lite SMART500RT1U and NUT
...9;P')
10.615820 send_cmd: sending 3a 50 af 0d 00 00 00 00 '.P......'
10.717503 send_cmd: received 50 30 30 35 30 30 58 0d 'P00500X.' (OK)
10.717838 send_to_all: SETINFO ups.debug.P "30 30 35 30 30 58 0d
'00500X.'"
10.718023 send_to_all: DATAOK
10.718606 dstate_init: sock /var/run/nut/tripplite_usb-SMART500RT1U
open on fd 5
10.719616 send_to_all: SETINFO driver.parameter.pollinterval "2"
10.720403 send_to_all: SETINFO device.mfr "Tripp Lite"
10.721489 send_to_all: SETINFO device.model "SMAR...
2008 Jun 17
2
R error using Survr function with gcmrec
Would someone be able to help with this question? I'm using the
Gcmrec, Survrec, and Design packages to do a power analysis on
simulated data. I'm receiving an error after using the Survr function
that all data must have a censoring time even after using the gcmrec
function: newdata<-addCenTime(olddata). My program is below. I'd
greatly appreciate any help!
2017 Jan 19
1
PowerWalker VFI 2000 RT LCD
...usbhid-ups"
0.062446 upsdrv_initinfo...
0.062450 send_to_all: SETINFO driver.version.data "EXPLORE HID 0.1"
0.062458 upsdrv_updateinfo...
0.062461 Not using interrupt pipe...
0.062465 Quick update...
0.062469 send_to_all: SETINFO ups.status "OB"
0.062472 send_to_all: DATAOK
0.062497 dstate_init: sock /var/run/nut/usbhid-ups-ups open on fd 5
0.062501 send_to_all: SETINFO driver.parameter.pollinterval "2"
0.062505 send_to_all: SETINFO device.mfr "PPC"
0.062509 send_to_all: SETINFO device.model "USB UPS "
0.062513 upsdrv_updateinfo......
2013 Jun 26
0
smsbrasil-0.0.2 driver
...timeout (2 seconds)
801.445806 Communications with UPS lost: upsdrv_updateinfo: UPS at port /dev/ttyUSB0 is returning by timeout...
804.446713 smsBR_RecAnswer: Started
804.446755 smsBR_RecAnswer: Finished
804.446775 send_to_all: SETINFO output.voltage "115.0"
804.446804 send_to_all: DATAOK
809.451780 smsBR_RecAnswer: Started
809.451858 smsBR_RecAnswer: Finished
809.451895 send_to_all: SETINFO input.voltage "230.0"
814.456905 smsBR_RecAnswer: Started
814.456979 smsBR_RecAnswer: Finished
814.457020 send_to_all: SETINFO output.voltage "114.0"
814.457069 send_t...
2013 Jun 26
3
smsbrasil-0.0.2 driver
Hello again!
Sorry for not being able to test this before.
Ulisses, please apply the patch to fix typo in my e-mail address.
I've compiled it against nut-2.6.5 about 10 hours ago. It was everything
fine until now. I'm seeing CHRG but the ups led wasn't blinking at all.
Vendor software was strangely showing charging also. I am assuming this is
expected behavior.
I've set the
2011 May 01
2
nut problem on boot/restart
...ttery.start.deep? ?3.760142 send_to_all: ADDCMD test.battery.start.quick? ?3.760148 send_to_all: ADDCMD test.battery.stop? ?3.760938 send: Q1? ?4.115391 read: (230.7 231.1 230.7 019 50.1 13.5 25.0 00001001? ?4.115423 send_to_all: SETINFO input.voltage.fault "231.1"? ?4.115446 send_to_all: DATAOK? ?4.115503 dstate_init: sock /var/run/nut/blazer_usb-soyntec open on fd 5? ?4.115515 send_to_all: SETINFO driver.parameter.pollinterval "2"? ?4.116204 send: Q1? ?4.467429 read: (230.7 231.1 231.1 019 50.1 13.5 25.0 00001001? ?4.467466 send_to_all: SETINFO output.voltage "231.1"?...
2011 Mar 26
1
Help with Aiptek PowerWalker VFI 1000 LCD and Konig CMP1200
....124617 send_to_all: SETINFO input.voltage "226.3"
1.124665 send_to_all: SETINFO output.voltage "227.3"
1.124688 send_to_all: SETINFO ups.load "14"
1.124713 send_to_all: SETINFO battery.voltage "41.04"
1.124767 send_to_all: DATAOK
1.124843 dstate_init: sock /var/run/nut/blazer_usb-powerwalker
open on fd 5
1.124867 send_to_all: SETINFO driver.parameter.pollinterval "2"
1.124888 send_to_all: SETINFO device.mfr ""
1.124910 send_to_all: SETINFO device.model "HV 1K"...
2018 Feb 04
0
No answer from upsrw <ups name> command
...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 setva...
2007 Jan 29
1
"no longer stale" when disconnected with 2.0.5
[...]
> I think this output doesn't help very much.
This is very helpful. The problem is not in the connection to the driver,
upd->data_ok switches between 0 and 1. Only the driver can change this
value by repetitively switching between DATASTALE and DATAOK. There is
nothing upsd can do about this, this is a driver problem. This is
consistent with the observation that all people reporting similar problems
are using the newhidups (or usbhid-ups) drivers. I can't reproduce this
with the 'safenet' driver either (different UPS though). Could y...
2006 Jan 27
0
Suspend-to-disk & NUT (solved!)
I finally nailed down the problem with upsd declaring data stale when
resuming from suspend. The problem is two fold (not surprisingly):
1) The dstate_dataok() and dstate_datastale() routines in
'drivers/dstate.c' will only 'broadcast' *changes* in the driver state.
Since the driver has no notion of time, it won't notice at all that it was
suspended. Therefor, after resuming it is business as usual for the driver
and it won't bro...
2014 Nov 05
1
blazer_usb disconnects
...1.076838 send_to_all: ADDCMD test.battery.stop
1.077876 send: Q1
1.331815 read: (229.4 229.4 230.0 024 50.3 13.6 25.0 00001001
1.331926 send_to_all: SETINFO ups.load "24"
1.331986 send_to_all: SETINFO battery.charge "100"
1.332046 send_to_all: DATAOK
1.332212 dstate_init: sock /var/run/nut/blazer_usb-nasups open on fd 5
1.332290 send_to_all: SETINFO driver.parameter.pollinterval "2"
1.333860 send: Q1
1.587784 read: (229.4 229.4 229.4 017 50.3 13.6 25.0 00001001
1.587887 send_to_all: SETINFO output.voltage...
2012 May 10
3
battery.charge and other fixes needed for X-Power Tigra 1kVA
...53144 send_to_all: SETINFO input.frequency "50.0"
1.453144 send_to_all: SETINFO ups.temperature "34.0"
1.453144 send_to_all: SETINFO battery.charge "-24.8"
1.453144 send_to_all: SETINFO ups.status "OL"
1.453144 send_to_all: DATAOK
3.437544 w32_serial_read : ulen 64, vmin_ 1, vtime_ 0, hEvent
000007A8
3.437544 w32_serial_read : Reading 47 characters
3.437544 w32_serial_read : total characters read = 47
My questions are:
1) Any ideas on why battery.charge is set to -24.8 (note also the
negative sig...
2013 May 01
1
Powercom BNT-1500AP serial config
...06289 input.voltage: 99.8
0.306303 output.voltage (raw data): [raw: 62]
0.306324 send_to_all: SETINFO output.voltage "1785735.0"
0.306339 output.voltage: 1785735.0
0.306359 send_to_all: SETINFO ups.status "OB TEST"
0.306375 STATUS: OB TEST
0.306390 send_to_all: DATAOK
0.306492 dstate_init: sock /var/run/nut/powercom-ups4 open on fd 5
0.306514 send_to_all: SETINFO driver.parameter.pollinterval "2"
0.306533 send_to_all: SETINFO device.mfr "PowerCom"
0.306551 send_to_all: SETINFO device.model "KIN-1500AP"
0.306570 send_t...
2011 Apr 28
1
Problem with blazer_ser/megatec when upgrading to 2.6.0 from 2.4
...t
0.634776 send_to_all: ADDCMD test.battery.start.deep
0.634785 send_to_all: ADDCMD test.battery.start.quick
0.634793 send_to_all: ADDCMD test.battery.stop
0.634864 send: Q1
0.862632 read: (246.0 140.0 246.0 004 50.0 54.0 25.0 00001000
0.862677 send_to_all: DATAOK
0.862793 dstate_init: sock /var/lib/nut/blazer_ser-munja open on fd 5
0.862808 send_to_all: SETINFO driver.parameter.pollinterval "10"
0.862818 send_to_all: SETINFO device.mfr ""
0.862827 send_to_all: SETINFO device.model ""
0.862900...
2011 Dec 21
1
APC BZ1200-BR
...9675 send_to_all: SETINFO driver.name "genericups"
0.009690 send_to_all: SETINFO ups.mfr "APC"
0.009705 send_to_all: SETINFO ups.model "Back-UPS"
0.010579 send_to_all: SETINFO ups.status "LB OL"
0.010604 ups.status: OL BL
0.010630 send_to_all: DATAOK
0.010685 dstate_init: sock /var/run/nut/genericups-ups open on fd 5
0.010701 send_to_all: SETINFO driver.parameter.pollinterval "2"
0.010718 send_to_all: SETINFO device.mfr "APC"
0.010731 send_to_all: SETINFO device.model "Back-UPS"
0.011577 ups.status:...
2018 Jan 07
2
No answer from upsrw <ups name> command
2011 Sep 28
0
[BUG] nut 2.4.3+: UPS EP-1K: Firmware fault: USB-Interface crashes with nut.org monitoring if driver polling time <15 sec
...0.951532 send: QS
1.207958 read: (231.2 231.2 231.2 027 50.1 27.4 --.- 00001001
1.208145 blazer_status: non numerical value [--.-]
1.208176 send_to_all: SETINFO battery.charge "100"
1.208205 send_to_all: SETINFO battery.runtime "7653"
1.208220 send_to_all: DATAOK
1.208789 dstate_init: sock /var/state/ups/blazer_usb-ups open on fd 5
1.208824 send_to_all: SETINFO driver.parameter.pollinterval "15"
1.209837 send: QS
1.462236 read: (231.2 231.2 231.2 028 50.1 27.4 --.- 00001001
1.462441 send_to_all: SETINFO ups.load "28"...
2014 Jun 27
3
The dreaded Tripp Lite SMART500RT1U and NUT
...9.370565 send_cmd: sending 3a 53 ac 0d 00 00 00 00 '.S......'
> > 9.472418 send_cmd: received 53 01 04 00 00 64 00 0d 'S....d..' (OK)
That would make sense to what I am seeing. If I leave this to run, it
will keep looping, stopping for a split second on "DATAOK".
> Ah, what we should be seeing here is that "01 04" status in ASCII. I
> think the 3004 protocol also encodes it in binary.
>
> > 9.472712 send_to_all: SETINFO ups.mfr "Tripp Lite"
> > 9.472899 send_cmd(msg_len=2, type='P')
>...
2015 Nov 23
2
Cannot access Patriot Pro II from new system
Hi list,
on my previous (lenny or squeeze) machine, I had it up and running, but
that machine and configs are gone - and on my new jessie machine (see
device and config details below) I cannot start the driver:
# /lib/nut/bestups -DDDDD -a Patriot_Pro_II_750
0.000000 debug level is '5'
0.000806 send_to_all: SETINFO device.type "ups"
0.000842 send_to_all: