Displaying 6 results from an estimated 6 matches for "my_up".
Did you mean:
my_ip
2014 Jul 29
0
Simple UpsTray client for Windows
...o: UpsTray ups at localhost:3493
UPS name: ups
server: local Windows machine
port: 3493 (default)
UpsTray.exe my_nut_server
Equivalent to: UpsTray ups at my_nut_server:3493
UPS name: ups
server: my_nut_server
port: 3493 (default)
UpsTray.exe my_ups at 192.168.0.111
Equivalent to: UpsTray my_ups at 192.168.0.111:3493
UPS name: my_ups
server: 192.168.0.111
port: 3493 (default)
UpsTray.exe my_ups at my_nut_server:1234
Equivalent to: UpsTray my_ups at my_nut_server:1234
UPS name: my_ups
server: my_...
2015 Apr 04
2
nutdrv_qx hangs after send: QS
...dorid = 0665
productid = 5161
The problem I'm experiencing is that after a random amount of time, usually
a few mins, the driver stops providing data and the and the application
complains the data is "stale".
More extensive debugging by running the driver sudo ./nutdrv_qx -u root -a
MY_UPS -DDDDDD indicates the driver works normally then will randomly stop
working at stop "send: QS". The debug logs show values successfully
retrieved repeatedly until something like:
....
Quick update...
send: QS
read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001001
update_status: OL
update_s...
2015 Apr 04
0
nutdrv_qx hangs after send: QS
On Apr 4, 2015, at 7:19 PM, Richard Flint <richard.flint at gmail.com> wrote:
> More extensive debugging by running the driver sudo ./nutdrv_qx -u root -a MY_UPS -DDDDDD indicates the driver works normally then will randomly stop working at stop "send: QS". The debug logs show values successfully retrieved repeatedly until something like:
> ....
> Quick update...
> send: QS
> read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001001
> u...
2012 Mar 16
4
tcp-wrapper not found
Hi, all!
Actually I have two questions for a same reason: I want to share my NUT to my LAN, or read UPS from remote device.
/**************** firstly *****************/
I downloaded tcp-wrapper, but NUT could not detected it.
Previously I successfully configured and make NUT into my embedded system. It worked and UPS is recognized.
I downloaded tcp-wrapper (Ver 7.6, most files in the package
2015 Apr 05
2
nutdrv_qx hangs after send: QS
...the debug level.
Regards,
Richard
On Sun, Apr 5, 2015 at 12:44 AM Charles Lepple <clepple at gmail.com> wrote:
> On Apr 4, 2015, at 7:19 PM, Richard Flint <richard.flint at gmail.com> wrote:
>
> More extensive debugging by running the driver sudo ./nutdrv_qx -u root -a
> MY_UPS -DDDDDD indicates the driver works normally then will randomly stop
> working at stop "send: QS". The debug logs show values successfully
> retrieved repeatedly until something like:
> ....
> Quick update...
> send: QS
> read: (247.9 239.1 248.0 005 50.0 27.5 --.- 00001...
2015 Apr 05
0
nutdrv_qx hangs after send: QS
...t;
> On Sun, Apr 5, 2015 at 12:44 AM Charles Lepple <clepple at gmail.com> wrote:
>
>> On Apr 4, 2015, at 7:19 PM, Richard Flint <richard.flint at gmail.com>
>> wrote:
>>
>> More extensive debugging by running the driver sudo ./nutdrv_qx -u root
>> -a MY_UPS -DDDDDD indicates the driver works normally then will randomly
>> stop working at stop "send: QS". The debug logs show values successfully
>> retrieved repeatedly until something like:
>> ....
>> Quick update...
>> send: QS
>> read: (247.9 239.1 248.0...