Re: [Nut-upsuser] connection pb with blazer_usb with infusec UPS

2016-10-09 Thread hyo...@gmail.com 
Please keep the list CC'd, thanks.

2016-10-07 8:54 GMT+02:00 MATHIEU Clement :
> Hello
> thanks for your answer
> i’ve tried with nutdrv_qx driver
> and i got this result
>
> lsusb :
>
> Bus 001 Device 058: ID 0665:5161 Cypress Semiconductor USB to Serial
> Bus 001 Device 005: ID 13ee:0001 MosArt
> Bus 001 Device 004: ID 0a81:0101 Chesen Electronics Corp. Keyboard
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514
> Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
>
> sudo /lib/nut/nutdrv_qx -a HERO -DDD -u root
>
> Network UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2)
> USB communication driver 0.32
>0.00 debug level is '3'
>0.002329 upsdrv_initups...
>0.003541 Checking device (0665/5161) (001/036)
>0.014412 - VendorID: 0665
>0.014521 - ProductID: 5161
>0.014608 - Manufacturer: INNO TECH
>0.014697 - Product: USB to Serial
>0.014783 - Serial Number: unknown
>0.014875 - Bus: 001
>0.014961 Trying to match device
>0.015172 Device matches
>0.015305 failed to claim USB device: could not claim interface 0: Device
> or resource busy
>0.015942 detached kernel driver from USB device...
>0.017534 send: QGS
>0.152570 read: N
>0.153407 qx_process_answer: short reply (input.voltage)
>0.154812 send: QGS
>0.289577 read: N
>0.290254 qx_process_answer: short reply (input.voltage)
>0.291575 send: QGS
>0.426589 read: N
>0.427286 qx_process_answer: short reply (input.voltage)
>0.428596 send: M
>0.552624 read: P
>0.553499 voltronic_qs_protocol: invalid protocol [P]
>0.554862 send: M
>0.678625 read: P
>0.679343 voltronic_qs_protocol: invalid protocol [P]
>0.680625 send: M
>0.804641 read: P
>0.805347 voltronic_qs_protocol: invalid protocol [P]
>0.806638 send: QS
>2.041443 read: could not claim interface 0: Device or resource busy
>2.042383 qx_process_answer: short reply (input.voltage)
>2.043674 send: QS
>3.277104 read: could not claim interface 0: Device or resource busy
>3.277275 qx_process_answer: short reply (input.voltage)
>3.277954 send: QS
>4.512612 read: could not claim interface 0: Device or resource busy
>4.512787 qx_process_answer: short reply (input.voltage)
>4.513487 send: D
>4.638121 read: N
>4.638259 qx_process_answer: short reply (input.voltage)
>4.638996 send: D
>4.763133 read: N
>4.763241 qx_process_answer: short reply (input.voltage)
>4.764012 send: D
>4.888154 read: N
>4.888259 qx_process_answer: short reply (input.voltage)
>4.889028 send: Q1
>5.019190 read: N
>5.019383 qx_process_answer: short reply (input.voltage)
>5.020180 send: Q1
>5.150184 read: N
>5.150289 qx_process_answer: short reply (input.voltage)
>5.151061 send: Q1
>5.281199 read: N
>5.281306 qx_process_answer: short reply (input.voltage)
>5.282077 send: Q1
>5.412245 read: N
>5.412437 qx_process_answer: short reply (input.voltage)
>5.413234 send: Q1
>5.543247 read: N
>5.544118 qx_process_answer: short reply (input.voltage)
>5.545492 send: Q1
>5.675251 read: N
>5.675956 qx_process_answer: short reply (input.voltage)
>5.677259 send: Q1
>5.807269 read: N
>5.808067 qx_process_answer: short reply (input.voltage)
>5.809396 send: Q1
>5.939284 read: N
>5.939965 qx_process_answer: short reply (input.voltage)
>5.941293 send: Q1
>6.071312 read: N
>6.072170 qx_process_answer: short reply (input.voltage)
>6.073557 send: Q1
>6.203318 read: N
>6.204040 qx_process_answer: short reply (input.voltage)
>6.205327 send: Q1
>6.335336 read: N
>6.336029 qx_process_answer: short reply (input.voltage)
>6.337338 send: Q1
>6.467375 read: N
>6.468330 qx_process_answer: short reply (input.voltage)
>6.469048 Device not supported!
>6.469736 Device not supported!
>
> any idea ?

The reply ('P') to the 'M' query seems to confirm my belief that this
device might be supported by 'nutdrv_qx' driver with
'voltronic-qs-hex' protocol.

>
> how do you install from repository ver 2.7.4. ?

Well, if you want the most recent source, you can either start from
our Git tree, or use the tarball snapshots from our Buildbot (see
http://networkupstools.org/download.html ), then follow our user
manual ( http://networkupstools.org/docs/user-manual.chunked/ar01s05.html
- some steps are not needed if you already have NUT installed, just be
sure to use compatible configure/install options).

>
> i’v also tried with combo  06da/.
> it does not work…
> thanks

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] connection pb with blazer_usb with infusec UPS

2016-10-02 Thread hyo...@gmail.com 
2016-10-01 17:59 GMT+02:00 MATHIEU Clement :
> Hello
>
> i need your help regarding the following issue :
>
> i have a hero touch ups from infosec. it is connected via USB to a raspberry
> pi 3.
> i’ve configure ups.conf file as below
>
> [HERO]
>driver = blazer_usb
>vendorid = 0665
>productid = 5161
>
> either with
>port = auto
> or
>port = /dev/hidraw0
> or
>   port = /dev/ttySo
>
> the connection never works

The 'blazer_usb' driver (like others based on libusb) don't actually
use the 'port' argument, but, since it is still required by NUT, you
should set it to 'auto'.

>
> i get the following log from command line :
> sudo /lib/nut/blazer_usb -a HERO -DDD -u root
> Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
>0.00 debug level is '3'
>0.003947 Checking device (0665/5161) (001/116)
>0.016760 - VendorID: 0665
>0.017245 - ProductID: 5161
>0.017686 - Manufacturer: INNO TECH
>0.018127 - Product: USB to Serial
>0.018598 - Serial Number: unknown
>0.019086 - Bus: 001
>0.019540 Trying to match device
>0.020136 Device matches
>0.020655 failed to claim USB device: could not claim interface 0: Device
> or resource busy
>0.021625 detached kernel driver from USB device...
>0.022676 Trying megatec protocol...
>0.025291 send: Q1
>0.153928 read: N
>0.154751 blazer_status: short reply
>0.155441 Status read 1 failed
>0.156783 send: Q1
>0.286922 read: N
>0.287605 blazer_status: short reply
>0.288335 Status read 2 failed
>0.289796 send: Q1
>0.419969 read: N
>0.420052 blazer_status: short reply
>0.420081 Status read 3 failed
>0.420107 Trying mustek protocol...
>0.420818 send: QS
>1.654899 read: could not claim interface 0: Device or resource busy
>1.655782 blazer_status: short reply
>1.656445 Status read 1 failed
>1.657598 send: QS
>2.891901 read: could not claim interface 0: Device or resource busy
>2.892810 blazer_status: short reply
>2.893497 Status read 2 failed
>2.894755 send: QS
>4.129250 read: could not claim interface 0: Device or resource busy
>4.129411 blazer_status: short reply
>4.129503 Status read 3 failed
>4.129590 Trying megatec/old protocol...
>4.130286 send: D
>4.254420 read: N
>4.254520 blazer_status: short reply
>4.254608 Status read 1 failed
>4.255296 send: D
>4.379452 read: N
>4.379601 blazer_status: short reply
>4.379692 Status read 2 failed
>4.380447 send: D
>4.504477 read: N
>4.504631 blazer_status: short reply
>4.504725 Status read 3 failed
>4.504812 Trying zinto protocol...
>4.505581 send: Q1
>4.635465 read: N
>4.635565 blazer_status: short reply
>4.635654 Status read 1 failed
>4.636344 send: Q1
>4.766481 read: N
>4.766580 blazer_status: short reply
>4.78 Status read 2 failed
>4.767360 send: Q1
>4.897519 read: N
>4.897659 blazer_status: short reply
>4.897749 Status read 3 failed
>4.897835 No supported UPS detected
> any idea ?

This seems like something that might be supported by 'nutdrv_qx'
driver with 'voltronic-qs-hex' protocol, an early version of which is
part of the 2.7.3 release, while an improved version with support for
more devices is available in 2.7.4. If possible, give it a try.

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] connection pb with blazer_usb with infusec UPS

2016-10-01 Thread MATHIEU Clement 
Hello

i need your help regarding the following issue :

i have a hero touch ups from infosec. it is connected via USB to a raspberry pi 
3.
i’ve configure ups.conf file as below

[HERO]
   driver = blazer_usb
   vendorid = 0665
   productid = 5161

either with
   port = auto
or 
   port = /dev/hidraw0
or
  port = /dev/ttySo
   
the connection never works

i get the following log from command line :
sudo /lib/nut/blazer_usb -a HERO -DDD -u root
Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
   0.00 debug level is '3'
   0.003947 Checking device (0665/5161) (001/116)
   0.016760 - VendorID: 0665
   0.017245 - ProductID: 5161
   0.017686 - Manufacturer: INNO TECH
   0.018127 - Product: USB to Serial
   0.018598 - Serial Number: unknown
   0.019086 - Bus: 001
   0.019540 Trying to match device
   0.020136 Device matches
   0.020655 failed to claim USB device: could not claim interface 0: Device 
or resource busy
   0.021625 detached kernel driver from USB device...
   0.022676 Trying megatec protocol...
   0.025291 send: Q1
   0.153928 read: N
   0.154751 blazer_status: short reply
   0.155441 Status read 1 failed
   0.156783 send: Q1
   0.286922 read: N
   0.287605 blazer_status: short reply
   0.288335 Status read 2 failed
   0.289796 send: Q1
   0.419969 read: N
   0.420052 blazer_status: short reply
   0.420081 Status read 3 failed
   0.420107 Trying mustek protocol...
   0.420818 send: QS
   1.654899 read: could not claim interface 0: Device or resource busy
   1.655782 blazer_status: short reply
   1.656445 Status read 1 failed
   1.657598 send: QS
   2.891901 read: could not claim interface 0: Device or resource busy
   2.892810 blazer_status: short reply
   2.893497 Status read 2 failed
   2.894755 send: QS
   4.129250 read: could not claim interface 0: Device or resource busy
   4.129411 blazer_status: short reply
   4.129503 Status read 3 failed
   4.129590 Trying megatec/old protocol...
   4.130286 send: D
   4.254420 read: N
   4.254520 blazer_status: short reply
   4.254608 Status read 1 failed
   4.255296 send: D
   4.379452 read: N
   4.379601 blazer_status: short reply
   4.379692 Status read 2 failed
   4.380447 send: D
   4.504477 read: N
   4.504631 blazer_status: short reply
   4.504725 Status read 3 failed
   4.504812 Trying zinto protocol...
   4.505581 send: Q1
   4.635465 read: N
   4.635565 blazer_status: short reply
   4.635654 Status read 1 failed
   4.636344 send: Q1
   4.766481 read: N
   4.766580 blazer_status: short reply
   4.78 Status read 2 failed
   4.767360 send: Q1
   4.897519 read: N
   4.897659 blazer_status: short reply
   4.897749 Status read 3 failed
   4.897835 No supported UPS detected
any idea ?
thanks a lot

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser