akbl icon indicating copy to clipboard operation
akbl copied to clipboard

Add support to the Alienware 17 R5 computer

Open seirios opened this issue 6 years ago • 2 comments

After running akbl --block-testing this is what I get under Arch Linux 4.18.9-arch1-1. After clicking connect, I get the following:

device loaded:
DEVICE ID 187c:0550 on Bus 001 Address 004 =================
 bLength                :   0x12 (18 bytes)
 bDescriptorType        :    0x1 Device
 bcdUSB                 :  0x200 USB 2.0
 bDeviceClass           :    0x0 Specified at interface
 bDeviceSubClass        :    0x0
 bDeviceProtocol        :    0x0
 bMaxPacketSize0        :   0x40 (64 bytes)
 idVendor               : 0x187c
 idProduct              : 0x0550
 bcdDevice              :  0x200 Device 2.0
 iManufacturer          :    0x1 Alienware
 iProduct               :    0x2 AW-ELC
 iSerialNumber          :    0x3 00.01
 bNumConfigurations     :    0x1
  CONFIGURATION 1: 0 mA ====================================
   bLength              :    0x9 (9 bytes)
   bDescriptorType      :    0x2 Configuration
   wTotalLength         :   0x29 (41 bytes)
   bNumInterfaces       :    0x1
   bConfigurationValue  :    0x1
   iConfiguration       :    0x0 
   bmAttributes         :   0xe0 Self Powered, Remote Wakeup
   bMaxPower            :    0x0 (0 mA)
    INTERFACE 0: Human Interface Device ====================
     bLength            :    0x9 (9 bytes)
     bDescriptorType    :    0x4 Interface
     bInterfaceNumber   :    0x0
     bAlternateSetting  :    0x0
     bNumEndpoints      :    0x2
     bInterfaceClass    :    0x3 Human Interface Device
     bInterfaceSubClass :    0x0
     bInterfaceProtocol :    0x0
     iInterface         :    0x0 
      ENDPOINT 0x81: Interrupt IN ==========================
       bLength          :    0x7 (7 bytes)
       bDescriptorType  :    0x5 Endpoint
       bEndpointAddress :   0x81 IN
       bmAttributes     :    0x3 Interrupt
       wMaxPacketSize   :   0x21 (33 bytes)
       bInterval        :    0xa
      ENDPOINT 0x1: Interrupt OUT ==========================
       bLength          :    0x7 (7 bytes)
       bDescriptorType  :    0x5 Endpoint
       bEndpointAddress :    0x1 OUT
       bmAttributes     :    0x3 Interrupt
       wMaxPacketSize   :   0x21 (33 bytes)
       bInterval        :   0x64

When clicking TEST BLOCK I get an endless stream of:

DEBUG from `/usr/lib/python3.7/AKBL/Engine/Core/Driver.py` on method `write_constructor`:
packet=[  2|  6|  0|  0|  0|  0|  0|  0|  0]	 legend=set_get_status


DEBUG from `/usr/lib/python3.7/AKBL/Engine/Core/Driver.py` on method `read_device`:
msg=array('B', [2, 6, 0, 0, 0, 0, 0, 0, 0])


DEBUG from `/usr/lib/python3.7/AKBL/Engine/Core/Driver.py` on method `write_constructor`:
packet=[  2|  6|  0|  0|  0|  0|  0|  0|  0]	 legend=set_get_status
packet=[  2|  7|  3|  0|  0|  0|  0|  0|  0]	 legend=reset, command=RESET_ALL_LIGHTS_OFF

and I have to kill the process.

Hope you can guide me to get this working. I can do USB capture from Windows if needed.

seirios avatar Oct 03 '18 02:10 seirios

Hi @seirios , it is always nice of having feedbacks of new computers. Saddly I'm currently kinda busy developing some features for the software. I'll come back when I finish them!

Regards, rsm

rsm-gh avatar Oct 17 '18 17:10 rsm-gh

Hello @seirios ,

It makes long time. I still having no real solution for this but have you tried to update the variable DATA_LENGTH to 12? It seems to fix many problems in some computers.

Regards

rsm-gh avatar Jul 01 '19 12:07 rsm-gh