conecting and maping my x52 pro
25 posts
• Page 2 of 3 • 1, 2, 3
Re: conecting and maping my x52 pro
phillow wrote:as i was too impatient to wait for a guide, i wrote one myself.
Please feel free to comment, give tips or just read it for no purpose
https://phillow-at.medium.com/x52-hotas ... f9a9c4b3e3
Do I need to change anything to make this work with PS4?
-
Aos_Si - Sergeant
- Posts: 6
- Joined: Mon Dec 07, 2020 2:09 pm
Re: conecting and maping my x52 pro
Aos_Si wrote:phillow wrote:as i was too impatient to wait for a guide, i wrote one myself.
Please feel free to comment, give tips or just read it for no purpose
https://phillow-at.medium.com/x52-hotas ... f9a9c4b3e3
Do I need to change anything to make this work with PS4?
Hi there,
well i guess you have. Input mappings and my scripts probably need some adaption.
But the good thing: you don´t need to do all of it from scratch but use my docs as a template how to walk through
-
phillow - Master Sergeant
- Posts: 27
- Joined: Wed Oct 28, 2020 4:39 pm
Re: conecting and maping my x52 pro
Hi guys
I've been using an X52 standard on Xbox via a Titan Two for over two years now and have just invested in a X52 Pro (the Standard is getting some drift which the deadzone settings can't accomodate anymore).
Anyway - I was kind of hoping the input mapping between the X52 Standard and the Xbox controller would be the same for the X52 Pro - but clearly I've got that wrong. For example, the Clutch (i) button is not being recognosied on the PRO but is recognised on the Standard. Is there a custom HID file that I need to load on the SD card that will enable a few more of the buttons on the X52 Pro?
I have uploaded my Input Translater file and GPC files for Xbox and PC (I play Elite Dangerous on both platforms and the Titan Two allows me to use the X52 on Xbox and PC with identiocal mappings which is awesome). There are about 2 years of refinement in these scripts - so hopefully they will be of use to others.
If there is a custom HID file for the X52 Pro I would be greatly appreciative if some one could post it please.
I've been using an X52 standard on Xbox via a Titan Two for over two years now and have just invested in a X52 Pro (the Standard is getting some drift which the deadzone settings can't accomodate anymore).
Anyway - I was kind of hoping the input mapping between the X52 Standard and the Xbox controller would be the same for the X52 Pro - but clearly I've got that wrong. For example, the Clutch (i) button is not being recognosied on the PRO but is recognised on the Standard. Is there a custom HID file that I need to load on the SD card that will enable a few more of the buttons on the X52 Pro?
I have uploaded my Input Translater file and GPC files for Xbox and PC (I play Elite Dangerous on both platforms and the Titan Two allows me to use the X52 on Xbox and PC with identiocal mappings which is awesome). There are about 2 years of refinement in these scripts - so hopefully they will be of use to others.
If there is a custom HID file for the X52 Pro I would be greatly appreciative if some one could post it please.
- Attachments
-
- X52_HOTAS_mapped_PC_v1.80.gpc
- PC GPC file
- (6.04 KiB) Downloaded 120 times
-
- X52_HOTAS_mapped_Xbox_One_v1.80.gpc
- Xbox GPC file
- (6.04 KiB) Downloaded 118 times
-
- X52_All_1.0.git
- Input Translator
- (62 Bytes) Downloaded 122 times
-
thomo127 - Master Sergeant
- Posts: 32
- Joined: Wed Jan 09, 2019 9:31 am
Re: conecting and maping my x52 pro
Please capture and post here the USB descriptors of your X52 Pro so I can check the compatibility with the Titan Two.
On Gtuner IV, with the Titan Two connected to computer, go to top menu Tools -> "Fetch Descriptors ...". Now plug the X52 Pro to any port on the Titan Two. The descriptors will show in the window, click on the button "Copy Descriptors" and post here or send me via PM.
Thanks.
On Gtuner IV, with the Titan Two connected to computer, go to top menu Tools -> "Fetch Descriptors ...". Now plug the X52 Pro to any port on the Titan Two. The descriptors will show in the window, click on the button "Copy Descriptors" and post here or send me via PM.
Thanks.
ConsoleTuner Support Team
-
J2Kbr - General of the Army
- Posts: 20323
- Joined: Tue Mar 18, 2014 1:39 pm
Re: conecting and maping my x52 pro
Thanks as always for the prompt reply J2Kbr
I really appreciate the continue support that you are providing for the Titan Two
USB Descriptors for the X52 PRO are below:
Also, I have noticed that the lights on the buttons on the throttle are not working on the X52 PRO, but do work on the X52 standard. I'm not sure if that has anything to do with some of the buttons not being active on the throttle - but I thought I should mention it (all lights work and buttons work when the X52 PRO is plugged into a pc).
Please let me know if you need anything else.
Cheers
Ian
[USB DESCRIPTOR]
12 01 00 02 00 00 00 08 A3 06 62 07 00 20 01 02 00 01 09 02 22 00 01 01 00 80 73 09 04 00 00 01 03 00 00 00 09 21 11 01 00 01 22 7D 00 07 05 81 03 10 00 0A
[STRING 1 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 01 04 09 00 12
12 03 4C 00 6F 00 67 00 69 00 74 00 65 00 63 00 68 00
[STRING 2 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 02 04 09 00 38
38 03 58 00 35 00 32 00 20 00 50 00 72 00 6F 00 66 00 65 00 73 00 73 00 69 00 6F 00 6E 00 61 00 6C 00 20 00 48 00 2E 00 4F 00 2E 00 54 00 2E 00 41 00 2E 00 53 00 2E 00
[INTERFACE 0 HID DESCRIPTOR]
00 00 00 02 00 00 02 01 81 06 22 00 00 00 00 7D
05 01 09 04 A1 01 09 01 A1 00 09 30 09 31 15 00 26 FF 03 75 0A 95 02 81 02 75 02 95 01 81 01 09 35 15 00 26 FF 03 75 0A 95 01 81 02 09 32 09 33 09 34 09 36 15 00 26 FF 00 75 08 95 04 81 02 05 09 19 01 29 27 15 00 25 01 95 27 75 01 81 02 75 05 95 01 81 01 05 01 09 39 15 01 25 08 35 00 46 3B 01 66 14 00 75 04 95 01 81 42 05 05 09 24 09 26 15 00 25 0F 75 04 95 02 81 02 C0 C0
I really appreciate the continue support that you are providing for the Titan Two
USB Descriptors for the X52 PRO are below:
Also, I have noticed that the lights on the buttons on the throttle are not working on the X52 PRO, but do work on the X52 standard. I'm not sure if that has anything to do with some of the buttons not being active on the throttle - but I thought I should mention it (all lights work and buttons work when the X52 PRO is plugged into a pc).
Please let me know if you need anything else.
Cheers
Ian
[USB DESCRIPTOR]
12 01 00 02 00 00 00 08 A3 06 62 07 00 20 01 02 00 01 09 02 22 00 01 01 00 80 73 09 04 00 00 01 03 00 00 00 09 21 11 01 00 01 22 7D 00 07 05 81 03 10 00 0A
[STRING 1 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 01 04 09 00 12
12 03 4C 00 6F 00 67 00 69 00 74 00 65 00 63 00 68 00
[STRING 2 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 02 04 09 00 38
38 03 58 00 35 00 32 00 20 00 50 00 72 00 6F 00 66 00 65 00 73 00 73 00 69 00 6F 00 6E 00 61 00 6C 00 20 00 48 00 2E 00 4F 00 2E 00 54 00 2E 00 41 00 2E 00 53 00 2E 00
[INTERFACE 0 HID DESCRIPTOR]
00 00 00 02 00 00 02 01 81 06 22 00 00 00 00 7D
05 01 09 04 A1 01 09 01 A1 00 09 30 09 31 15 00 26 FF 03 75 0A 95 02 81 02 75 02 95 01 81 01 09 35 15 00 26 FF 03 75 0A 95 01 81 02 09 32 09 33 09 34 09 36 15 00 26 FF 00 75 08 95 04 81 02 05 09 19 01 29 27 15 00 25 01 95 27 75 01 81 02 75 05 95 01 81 01 05 01 09 39 15 01 25 08 35 00 46 3B 01 66 14 00 75 04 95 01 81 42 05 05 09 24 09 26 15 00 25 0F 75 04 95 02 81 02 C0 C0
-
thomo127 - Master Sergeant
- Posts: 32
- Joined: Wed Jan 09, 2019 9:31 am
Re: conecting and maping my x52 pro
Thank you. Here is the descriptors decoded for future reference:
I will be adding the dedicated HID configuration file for this controller on the very next Gtuner IV update. With that is expected all buttons and inputs to be accessible via the Titan Two. thanks.
- Code: Select all
[USB DESCRIPTOR]
12 bLength: 18
01 bDescriptorType: 1 DEVICE
00 02 bcdUSB: 2.00
00 bDeviceClass: 0
00 bDeviceSubClass: 0
00 bDeviceProtocol: 0
08 bMaxPacketSize0: 8
A3 06 idVendor: 06A3 Saitek PLC
62 07 idProduct: 0762 Saitek X52 Pro Flight Control System
00 20 bcdDevice: 20.00
01 iManufacturer: 1
02 iProduct: 2
00 iSerialNumber: 0
01 bNumConfigurations: 1
09 bLength: 9
02 bDescriptorType: 2 CONFIGURATION
22 00 wTotalLength: 34
01 bNumInterfaces: 1
01 bConfigurationValue: 1
00 iConfiguration: 0
80 bmAttributes: 128 Bus Powered
73 MaxPower: 230mA
09 bLength: 9
04 bDescriptorType: 4 INTERFACE
00 bInterfaceNumber: 0
00 bAlternateSetting: 0
01 bNumEndpoints: 1
03 bInterfaceClass: 3 Human Interface Device
00 bInterfaceSubClass: 0
00 bInterfaceProtocol: 0
00 iInterface: 0
09 bLength: 9
21 bDescriptorType: 33 HID
11 01 bcdHID: 1.11
00 bCountryCode: 0
01 bNumDescriptors: 1
22 bDescriptorType: 34
7D 00 wDescriptorLength: 125
07 bLength: 7
05 bDescriptorType: 5 ENDPOINT
81 bEndpointAddress: 1 IN
03 bmAttributes: 3 Interrupt, None, Data
10 00 wMaxPacketSize: 16
0A bInterval: 10
[STRING 1 DESCRIPTOR]
Logitech
[STRING 2 DESCRIPTOR]
X52 Professional H.O.T.A.S.
[INTERFACE 0 HID DESCRIPTOR]
05 01 (GLOBAL) USAGE_PAGE 0x0001 Generic Desktop Page
09 04 (LOCAL) USAGE 0x00010004 Joystick (CA=Application Collection)
A1 01 (MAIN) COLLECTION 0x01 Application (Usage=0x00010004: Page=Generic Desktop Page, Usage=Joystick, Type=CA)
09 01 (LOCAL) USAGE 0x00010001 Pointer (CP=Physical Collection)
A1 00 (MAIN) COLLECTION 0x00 Physical (Usage=0x00010001: Page=Generic Desktop Page, Usage=Pointer, Type=CP)
09 30 (LOCAL) USAGE 0x00010030 X (DV=Dynamic Value)
09 31 (LOCAL) USAGE 0x00010031 Y (DV=Dynamic Value)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
26 FF03 (GLOBAL) LOGICAL_MAXIMUM 0x03FF (1023)
75 0A (GLOBAL) REPORT_SIZE 0x0A (10) Number of bits per field
95 02 (GLOBAL) REPORT_COUNT 0x02 (2) Number of fields
81 02 (MAIN) INPUT 0x00000002 (2 fields x 10 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
75 02 (GLOBAL) REPORT_SIZE 0x02 (2) Number of bits per field
95 01 (GLOBAL) REPORT_COUNT 0x01 (1) Number of fields
81 01 (MAIN) INPUT 0x00000001 (1 field x 2 bits) 1=Constant 0=Array 0=Absolute 0=Ignored 0=Ignored 0=PrefState 0=NoNull
09 35 (LOCAL) USAGE 0x00010035 Rz (DV=Dynamic Value)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
26 FF03 (GLOBAL) LOGICAL_MAXIMUM 0x03FF (1023)
75 0A (GLOBAL) REPORT_SIZE 0x0A (10) Number of bits per field
95 01 (GLOBAL) REPORT_COUNT 0x01 (1) Number of fields
81 02 (MAIN) INPUT 0x00000002 (1 field x 10 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
09 32 (LOCAL) USAGE 0x00010032 Z (DV=Dynamic Value)
09 33 (LOCAL) USAGE 0x00010033 Rx (DV=Dynamic Value)
09 34 (LOCAL) USAGE 0x00010034 Ry (DV=Dynamic Value)
09 36 (LOCAL) USAGE 0x00010036 Slider (DV=Dynamic Value)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
26 FF00 (GLOBAL) LOGICAL_MAXIMUM 0x00FF (255)
75 08 (GLOBAL) REPORT_SIZE 0x08 (8) Number of bits per field
95 04 (GLOBAL) REPORT_COUNT 0x04 (4) Number of fields
81 02 (MAIN) INPUT 0x00000002 (4 fields x 8 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
05 09 (GLOBAL) USAGE_PAGE 0x0009 Button Page
19 01 (LOCAL) USAGE_MINIMUM 0x00090001 Button 1 Primary/trigger (MULTI=Selector, On/Off, Momentary, or One Shot)
29 27 (LOCAL) USAGE_MAXIMUM 0x00090027 Button 39 (MULTI=Selector, On/Off, Momentary, or One Shot)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
25 01 (GLOBAL) LOGICAL_MAXIMUM 0x01 (1)
95 27 (GLOBAL) REPORT_COUNT 0x27 (39) Number of fields
75 01 (GLOBAL) REPORT_SIZE 0x01 (1) Number of bits per field
81 02 (MAIN) INPUT 0x00000002 (39 fields x 1 bit) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
75 05 (GLOBAL) REPORT_SIZE 0x05 (5) Number of bits per field
95 01 (GLOBAL) REPORT_COUNT 0x01 (1) Number of fields
81 01 (MAIN) INPUT 0x00000001 (1 field x 5 bits) 1=Constant 0=Array 0=Absolute 0=Ignored 0=Ignored 0=PrefState 0=NoNull
05 01 (GLOBAL) USAGE_PAGE 0x0001 Generic Desktop Page
09 39 (LOCAL) USAGE 0x00010039 Hat switch (DV=Dynamic Value)
15 01 (GLOBAL) LOGICAL_MINIMUM 0x01 (1)
25 08 (GLOBAL) LOGICAL_MAXIMUM 0x08 (8)
35 00 (GLOBAL) PHYSICAL_MINIMUM 0x00 (0)
46 3B01 (GLOBAL) PHYSICAL_MAXIMUM 0x013B (315)
66 1400 (GLOBAL) UNIT 0x00000014 Rotation in degrees [1° units] (4=System=English Rotation, 1=Rotation=Degrees)
75 04 (GLOBAL) REPORT_SIZE 0x04 (4) Number of bits per field
95 01 (GLOBAL) REPORT_COUNT 0x01 (1) Number of fields
81 42 (MAIN) INPUT 0x00000042 (1 field x 4 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 1=Null 0=NonVolatile 0=Bitmap
05 05 (GLOBAL) USAGE_PAGE 0x0005 Game Controls Page
09 24 (LOCAL) USAGE 0x00050024 Move Right/Left (DV=Dynamic Value)
09 26 (LOCAL) USAGE 0x00050026 Move Up/Down (DV=Dynamic Value)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
25 0F (GLOBAL) LOGICAL_MAXIMUM 0x0F (15)
75 04 (GLOBAL) REPORT_SIZE 0x04 (4) Number of bits per field
95 02 (GLOBAL) REPORT_COUNT 0x02 (2) Number of fields
81 02 (MAIN) INPUT 0x00000002 (2 fields x 4 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
C0 (MAIN) END_COLLECTION Physical
C0 (MAIN) END_COLLECTION Application
I will be adding the dedicated HID configuration file for this controller on the very next Gtuner IV update. With that is expected all buttons and inputs to be accessible via the Titan Two. thanks.
ConsoleTuner Support Team
-
J2Kbr - General of the Army
- Posts: 20323
- Joined: Tue Mar 18, 2014 1:39 pm
Re: conecting and maping my x52 pro
Thanks J2Kbr
You guys absolutely rock.
I've just convinced an Elite Dangerous colleague to purchase a Titan Two, that will be the third person I've convinced to get one to use for Elite Dangerous - so I really appreciate all your support as it helps me to support those users.
Cheers
Ian
You guys absolutely rock.
I've just convinced an Elite Dangerous colleague to purchase a Titan Two, that will be the third person I've convinced to get one to use for Elite Dangerous - so I really appreciate all your support as it helps me to support those users.
Cheers
Ian
-
thomo127 - Master Sergeant
- Posts: 32
- Joined: Wed Jan 09, 2019 9:31 am
Re: conecting and maping my x52 pro
Hey J2Kbr
Is there a specific Community Forum channel that I should monitor for forthcoming Firmware updates?
I'm interested in fidning out when the next Titan Two Firmware update is likely to land.
Cheers
Ian
Is there a specific Community Forum channel that I should monitor for forthcoming Firmware updates?
I'm interested in fidning out when the next Titan Two Firmware update is likely to land.
Cheers
Ian
-
thomo127 - Master Sergeant
- Posts: 32
- Joined: Wed Jan 09, 2019 9:31 am
Re: conecting and maping my x52 pro
Normally we announce new firmwares (as well beta releases) as global announcement on the forums.
If you regularly uses Gtuner IV, you will receive a notification on the Output Panel as soon as new update is available.
If you regularly uses Gtuner IV, you will receive a notification on the Output Panel as soon as new update is available.
ConsoleTuner Support Team
-
J2Kbr - General of the Army
- Posts: 20323
- Joined: Tue Mar 18, 2014 1:39 pm
Re: conecting and maping my x52 pro
Hi Console Tuner Team
I noticed that my Titan Two had a firmware update on 4/02/2021 to 1.10.3.4.
Should that firmware update have included the HID file for the X52 Pro please?
Cheers
Ian
I noticed that my Titan Two had a firmware update on 4/02/2021 to 1.10.3.4.
Should that firmware update have included the HID file for the X52 Pro please?
Cheers
Ian
-
thomo127 - Master Sergeant
- Posts: 32
- Joined: Wed Jan 09, 2019 9:31 am
25 posts
• Page 2 of 3 • 1, 2, 3
Who is online
Users browsing this forum: No registered users and 161 guests