[Nut-upsdev] Re: [nut-commits] svn commit r801 - in
branches/megatec-usb: . drivers
Jon Gough
jon.gough at eclipsesystems.com.au
Thu Feb 8 19:06:35 CET 2007
Peter,
I am still trying to get more information from the manufacturers,
but they did send this through to me. I am not going to have time to
look into it before Tuesday next week. But I thought I should post it
anyway. My VendorID is -1 rather than 1, but....................
Regards
Jon
HID Device
*******************************************************************************
VendorID =1
ProductID=0
Use API function
*******************************************************************************
SetFeature ()
GetFeature ()
Tx Data (use SetFeature function)
*******************************************************************************
[5][0][len][ask.......] -response data
ask: [Q][1][D13]
[I][D13]
[F][D13]
ex: Ask
TxData=>
[5][0][3][Q][1][D13][0][0]............. ( Feature Report Byte Length )
"Q1"
[5][2][len][ask.......] -don't response data =>
Control or Command
ask: [T][D13]
........
ex: Ask
TxData=>
[5][2][2][T][D13][0][0]................ ( Feature Report Byte Length )
"T"
Rx Data (use GetFeature function)
*******************************************************************************
ex: after Tx "Q1"
RxData=> [(][2][0][8][.][4][
][1][4][0].......... ( Feature Report Byte Length )
"(208.4 140.0 208.4 034 59.9 2.05
35.0 00110000"
steps
*******************************************************************************
1.Get HID Device ( VendorID =1,ProductID=0).
2.use setfeature function to Tx Data.
3.use getfeature function to get data.
%% Information consult => MegaTec Communication Protocols for UPS
%% D:decimal
At 03:42 9/02/2007, Peter Selinger wrote:
>Hi Alexander,
>
>thanks for your good work on the megatec_usb driver. I have made a few
>more (cosmetic) changes.
>
>Is the driver now working stably for your device? In particular, do
>the instant commands (and particularly "upsdrvctl -k") work properly?
>In this case, we could hopefully mark the device as "supported" and
>merge the driver to the main branch.
>
>There is still the question of whether to keep separate code for
>Ablerex and Krauler. From what I understand, each of these subdrivers
>works for each of the devices. But the Krauler driver is now more
>advanced (with the retry feature), so we could remove the Ablerex
>subdriver (provided Jon tests the Krauler one to make sure it still
>works for the Ablerex device).
>
>If I understand correctly, the only change needed would be to change
>
> {0xffff, 0x0000, get_data_ablerex, set_data_ablerex},
>
>to
>
> {0xffff, 0x0000, get_data_krauler, set_data_krauler},
>
>is that correct? -- Peter
---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 000712-1, 08/02/2007
Tested on: 9/02/2007 5:06:38 AM
avast! is copyright (c) 2000-2007 ALWIL Software.
http://www.avast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070209/bdb240d4/attachment.html
More information about the Nut-upsdev
mailing list