Hello, I have an UPS Hunnox HNX-650 (http://www.hunnox.com/), but it's
not quite running yet with NUT. Any hints? Thanks...
Some info:
* lsusb:
Bus 005 Device 003: ID 0001: Fry's Electronics
* usb-devices:
T: Bus=05 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 2.00
b285f61f
>
> It's the solis_debug branch on Github.
>
> Does that help? I'm concerned that it might get out of sync later,
> but I don't want to change too much at once.
I'll give it a shot !!!
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
&
ive: RecPack: (25 bytes) => bb
47 88 ad 02 0a a0 29 02 2b 15 10 0b
62.940701 00 00 00 01 00 09 a1
49 5e 5e 19 fe
64.978509 getupdateinfo: requesting 25 bytes from
ser_get_buf_len()
64.978551 getupdateinfo: received 25 bytes from
ser_get_buf_len()
64.978571 CommReceive: Re
= ^W;
Thanks,
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
UNIX was not designed to stop you from doing stupid things,
because that would also stop you from doing clever things.
On Tue, 25 Aug 2015 21:59:08 -0400
Charles Lepple clep...@gmail.com
On Sun, 23 Aug 2015 11:09:03 -0400
Charles Lepple clep...@gmail.com wrote:
On Aug 21, 2015, at 10:10 AM, Mario Lobo ml...@digiart.art.br wrote:
Not sure what to look for yet. It might be easier to add in the
debug calls to the source code-- can you try building NUT from
source? If you
On Sun, 23 Aug 2015 11:09:03 -0400
Charles Lepple clep...@gmail.com wrote:
On Aug 21, 2015, at 10:10 AM, Mario Lobo ml...@digiart.art.br wrote:
Not sure what to look for yet. It might be easier to add in the
debug calls to the source code-- can you try building NUT from
source? If you
suggestions.
--
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
UNIX was not designed to stop you from doing stupid things,
because that would also stop you from doing clever things.
___
Nut-upsuser mailing
Hello list,
Cannot make Evolution 850 to be recognized, maybe the problem is Warning:
incomplete endpoint descriptor in lsusb? Details are as follows. NUT installed
by download of debian package.
Any ideas/suggestions are highly welcome, thanks in advance!
--ValenteM
= = = =
I am not able to do the test
When I put protocol=zinto I get:
Fatal error: 'protocol' is not a valid variable name for this driver.
I have also tried subdriver=zinto without luck
2012/2/21 Arnaud Quette aquette@gmail.com:
2012/2/16 Mario Giammarco mgiamma...@gmail.com:
Tomorrow I will do
Tomorrow I will do the test!
2012/2/16 Arnaud Quette aquette@gmail.com:
Halo Thomas und Mario ;-)
2012/2/14 Thomas Maisl exp-122...@maisl.com:
attached information was retrieved while UPS was operating _offline_ (doing
a runtime test)
thanks a lot for your test results.
1. lsusb -v
What can I do next?
Thanks,
Mario
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
2012/2/2 Arnaud Quette aquette@gmail.com:
2012/2/1 Mario Giammarco mgiamma...@gmail.com:
Here we go!
This one for 06da:0601:
...
ok, so that one seems almost good.
can you please send also upsc / upscmd / upsrw output?
upsc:
upsc mieionline
Error: Driver not connected
upsd:
upsd
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 32
Device Status: 0x
(Bus Powered)
2012/2/2 Arnaud Quette aquette@gmail.com:
2012/2/1 Mario Giammarco mgiamma...@gmail.com:
And for 06da:0002:
...
this one has a problem.
could you please send back
2012/1/31 Arnaud Quette aquette@gmail.com:
so you should also use sudo, Ie:
$ sudo /path/to/blazer_usb -D -a upsname
Unfortunately I am already root. I have enabled the root account I am
tired to to always use sudo. Even as root the problem persists.
I have searched and killed all processes that I think can use usb, so
I do not know what is happening
2012/2/1 Mario Giammarco mgiamma...@gmail.com:
2012/1/31 Arnaud Quette aquette@gmail.com:
so you should also use sudo, Ie:
$ sudo /path/to/blazer_usb -D -a upsname
Unfortunately
,
Mario
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
send_to_all: SETINFO ups.load 39
33.193844 send: Q1
33.449923 read: (226.3 226.3 226.3 034 50.0 27.4 60.4 1001
33.450027 send_to_all: SETINFO ups.load 34
2012/2/1 Arnaud Quette aquette@gmail.com:
2012/2/1 Mario mgiamma...@gmail.com:
Arnaud Quette aquette.dev at gmail.com
And for 06da:0002:
0.00 send_to_all: SETINFO driver.parameter.port auto
0.000198 send_to_all: SETINFO driver.parameter.subdriver ippon
0.000248 send_to_all: SETINFO driver.parameter.vendorid 06da
0.000332 send_to_all: SETINFO driver.parameter.productid 0002
Arnaud Quette aquette.dev at gmail.com writes:
ppon will probably be needed too.
Then send us back the debug output of the driver, ie (as root):
$ /path/to/blazer_usb -D -a upsname
Let it run for a minute or so, then stop it using Ctrl+C.
Sorry for missing informations:
I have ubuntu
Hello,
I have a Yunto e a Zanto ups connected with usb with id 06da:0002 and 06da:0601.
I have seen that people had some success using megatec driver.
But now megatec is replaced by blazer-usb and I am not able to use my upses
under nut.
Can you help me?
Thanks!
Mario
20 matches
Mail list logo
