Hi Mario,
first, please keep the traffic on the list.
2012/2/28 Mario Giammarco mgiamma...@gmail.com:
Here it is:
[mieionline]
driver = blazer_usb
protocol = zinto
port = auto
desc = yunto q700
# subdriver = zinto
vendorid = 06da
productid = 0601
But please note that I have done:
2012/2/27 Mario Giammarco mgiamma...@gmail.com:
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
could you please send back your ups.conf.
cheers,
Arno
2012/2/27 Thomas Maisl exp-122...@maisl.com:
Hello,
schrieb Arnaud Quette, Am 16.02.2012 18:48:
Can you please counter check, and report back upsc/upsrw/upscmd
upsc:
# upsc YQ450
battery.voltage: 13.40
beeper.status: disabled
device.type: ups
driver.name: blazer_usb
Hello,
schrieb Arnaud Quette, Am 16.02.2012 18:48:
Can you please counter check, and report back upsc/upsrw/upscmd
upsc:
# upsc YQ450
battery.voltage: 13.40
beeper.status: disabled
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
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
2012/2/16 Mario Giammarco mgiamma...@gmail.com:
Tomorrow I will do the test!
Marco, Thomas,
before I switched to something else, I'd like to complete this case.
have you been able to do some testing on your side?
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.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 -d06dA:0002
2-6. blazer_usb using subdriver cypress|phoenix|ippon|krauler
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
attached information was retrieved while UPS was operating _offline_ (doing
a runtime test)
1. lsusb -v -d06dA:0002
2-6. blazer_usb using subdriver cypress|phoenix|ippon|krauler
with and w/o protocol zinto
IMO cypress with zinto produced the best result, ippon and krauler didn't work
2012/2/4 Mario Giammarco mgiamma...@gmail.com:
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
schrieb Arnaud Quette, Am 13.02.2012 18:28:
for the 2nd, as per its USB IDs (06DA/0002), the driver should be bcmxcp_usb.
can you please try it in debug more and also send back the output?
A few minutes ago I managed to connect to a Yunto YQ450 using USB connection.
[YQ450]
driver =
Hi Thomas,
2012/2/13 Thomas Maisl exp-122...@maisl.com:
schrieb Arnaud Quette, Am 13.02.2012 18:28:
for the 2nd, as per its USB IDs (06DA/0002), the driver should be bcmxcp_usb.
can you please try it in debug more and also send back the output?
A few minutes ago I managed to connect to a
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
Bus 002 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd UPS
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0
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?
...
0.478318 Ratings read in 1 tries
0.480405 send: I
0.622185 read: I
this command seems
2012/2/1 Mario Giammarco mgiamma...@gmail.com:
And for 06da:0002:
...
this one has a problem.
could you please send back the following output (as root):
$ lsusb -v -d 06da:0002
it may turn out to be a HID device more than a megatec / Q1.
as for the other unit, you may also try other
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
Arnaud Quette aquette.dev at gmail.com writes:
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 have also
tried to kill processes that may lock usb but with no luck.
What can I do?
Thanks,
Here we go!
This one for 06da:0601:
0.00 send_to_all: SETINFO driver.parameter.port auto
0.000117 send_to_all: SETINFO driver.parameter.subdriver ippon
0.000179 send_to_all: SETINFO driver.parameter.vendorid 06da
0.000230 send_to_all: SETINFO
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
2012/1/31 Charles Lepple clep...@gmail.com:
On Jan 30, 2012, at 3:15 PM, Mario wrote:
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
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
25 matches
Mail list logo
