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
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 to use my upses > under nut. > > Can you help me?Some additional information would be useful: http://www.networkupstools.org/support.html#_request_help
2012/1/31 Charles Lepple <clepple at 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 to use my upses >> under nut. >> >> Can you help me? > > Some additional information would be useful: > > http://www.networkupstools.org/support.html#_request_helpseconded. we need more info to be able to help you! side comment: the only USB ID related to 0x06da that is known by blazer_usb is 0x06da:0x0003 this means that you must provide "vendorid" and "productid" params to the driver, either by using "-x" or by mentioning these in ups.conf: [mydev] driver = blazer_usb port = auto vendorid = 06da productid = 0601 "subdriver = ippon" will probably be needed too. Then send us back the debug output of the driver, ie (as root): $ /path/to/blazer_usb -DDDDD -a <upsname> Let it run for a minute or so, then stop it using Ctrl+C. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/
2012/1/31 Arnaud Quette <aquette.dev at gmail.com>:> so you should also use "sudo", Ie: > ?$ sudo /path/to/blazer_usb -DDDDD -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 <mgiammarco at gmail.com>:> 2012/1/31 Arnaud Quette <aquette.dev at gmail.com>: > >> so you should also use "sudo", Ie: >> ?$ sudo /path/to/blazer_usb -DDDDD -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.
Arnaud Quette <aquette.dev <at> gmail.com> writes:> so you should also use "sudo", Ie: > $ sudo /path/to/blazer_usb -DDDDD -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, Mario
2012/2/1 Mario <mgiammarco at gmail.com>:> Arnaud Quette <aquette.dev <at> gmail.com> writes: > >> so you should also use "sudo", Ie: >> ? $ sudo /path/to/blazer_usb -DDDDD -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?I forgot a point: since your USB IDs are not yet known, udev rules are not there. So try running as root using: $ /path/to/blazer_usb -u root -DDDDD -a <upsname> $ upsd -u root and you should be done. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/
Bus 002 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd UPS
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x06da Phoenixtec Power Co., Ltd
idProduct 0x0002 UPS
bcdDevice 0.02
iManufacturer 1 ONLINE
iProduct 2 YUNTO
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 4 Sample HID
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 31
Report Descriptor: (length is 31)
Item(Global): Usage Page, data= [ 0x01 ] 1
Generic Desktop Controls
Item(Local ): Usage, data= [ 0x05 ] 5
Gamepad
Item(Main ): Collection, data= [ 0x01 ] 1
Application
Item(Local ): Usage, data= [ 0x06 ] 6
Keyboard
Item(Local ): Usage Minimum, data= [ 0x01 ] 1
Pointer
Item(Local ): Usage Maximum, data= [ 0xf0 ] 240
(null)
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x01 ] 1
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x08 ] 8
Item(Main ): Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position
Non_Volatile Bitfield
Item(Local ): Usage, data= [ 0x07 ] 7
Keypad
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x10 ] 16
Item(Main ): Output, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position
Non_Volatile Bitfield
Item(Main ): End Collection, data=none
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 32
Device Status: 0x0000
(Bus Powered)
2012/2/2 Arnaud Quette <aquette.dev at gmail.com>:> 2012/2/1 Mario Giammarco <mgiammarco at 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 subdrivers...
>
> cheers,
> Arnaud
> --
> Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
> Debian Developer - http://www.debian.org
> Free Software Developer - http://arnaud.quette.free.fr/
Hi Mario, first, please keep the traffic on the list. 2012/2/28 Mario Giammarco <mgiammarco at 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: "man blazer_usb" and I see no > protocol option. I am using the ubuntu 11.10 version 2.6.1-2ubuntu2everything is fine in your ups.conf, and with your setup. I've even tested it with the same setup (ubuntu and nut 2.6.1-2ubuntu2): $ sudo upsdrvctl start blazer Network UPS Tools - UPS driver controller 2.6.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.2) Duplicate driver instance detected! Terminating other driver! Supported UPS detected with zinto protocol Vendor information unavailable Battery runtime will not be calculated (runtimecal not set) so it's either an old version that was still running, or another obscure error. can you please try again, ensuring that you're using the right binaries? cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/> 2012/2/28 Arnaud Quette <aquette.dev at gmail.com>: >> 2012/2/27 Mario Giammarco <mgiammarco at 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