On Thursday 25 September 2008 17:56:43 Daniel O'Connor wrote:
> > you might want to have libusb debug trace also, to see more low level
> > things. use "export USB_DEBUG=3" before launching usbhid-ups.
> > you might also have a look at your kernel output for ugen to see if
> > there is a problem he
As I haven't found a suitable pin-out that seems to work with this UPS
I'll have to abandon this project until some information forthcoming!
My main issue is that until I can communicate with the UPS its pointless
trying to debug software! (as I don't believe that NUT is at fault!)
although an int
Citeren Jordi Moreno :
> I'm attaching usbsnoop.log.tgz. I've tried to keep the log as little
> as possible, only logging Winpower agent's start.
>
> I hope it will help...
It does. This looks like a Q1/megatec protocol UPS, unlike what I
expected based on earlier megatec logs:
out: 46 0d 4d
Hi all,
I'm attaching usbsnoop.log.tgz. I've tried to keep the log as little as
possible, only logging Winpower agent's start.
I hope it will help...
Thank you for all!
---
Un saludo,
Jordi Moreno
CIM Internet, S.L.
jmor...@cim.es
Alexander I. Gordeev escribió:
Hi Jordi,
Hi Jordi,
On Mon, Jan 26, 2009 at 11:55:42AM +0100, Jordi Moreno wrote:
> I've tried usbsnoop on a Windows machine, connected to the UPS. Software
> bundled with the UPS is WinPower, and it seems to work fine. The problem
> is that I don't know what to look for at the usbsnoop log, since there's
Arjen de Korte escribió:
> Citeren Jordi Moreno :
>
>> Asking for UPS status [Q1]...
>> get_data_agiler: raw dump: (0 bytes) =>
>> get_data_agiler: raw dump: (8 bytes) => 30 30 31 30 30 30 0d 00
>> Q1 => FAILED [short read]
>> Q1 detail: (6 bytes) => 30 30 31 30 30 30
>
> [...]
>
>> Megatec prot
6 matches
Mail list logo
