support for XK-80 HID device

[ez_aviator]

I have a P.I.Engineering XK-80 input device, normally used with X-Plane 11. It's basically a grid of 80 push buttons which can be programmed.

I ran the HID scanner, and it recognises the device - see attached, so I was wondering if I would be able to use it with FSUIP7 and MSFS2020.
The device is recognised as a mouse!

HidScanner.log

[John Dowson]

7 minutes ago, ez_aviator said:

if I would be able to use it with FSUIP7 and MSFS2020.

I don't know, why don't you try it? The beta license is still valid - until tomorrow!

However, if its recognised as a mouse I don't think so, but see how it is recognised by FSUIPC (especially in the Joyscan.csv file).

[ez_aviator]

I have a full paid up licence copy 🙂

Just been viewing the HidDemo.lua script.
I might just give that a try tomorrow.

 

Will report back

[John Dowson]

You will need lua anyway to handle 80 buttons - if it is recognised, you can only handle the first 32 buttons via regular assignments.

[ez_aviator]

Hello John,

Can I first confirm, that in order to run a lua script with FSUIPC7;

1) I need the script to be in the root folder of FSUIPC7,

2) To have a keypress/joystick button set to activate it?

This seems to work, but I just wanted to see if there were other ways.

 

Plus, I have run the HidDemo script, with the details gleaned from the HidScanner log - see attached, and nothing appears to be seen.
Should I have to have the device visible within FSUIPC7 first.

Sorry - a few too many questions I suspect.
I am used to batch and Lua programming, but not with this interface.

Many thanks

HidScanner.log

Edited November 9, 2020 by ez_aviator

[John Dowson]

2 minutes ago, ez_aviator said:

1) I need the script to be in the root folder of FSUIPC7,

The installation folder, yes.

2 minutes ago, ez_aviator said:

2) To have a keypress/joystick button set to activate it?

Thats one way. Or if you want it to auto-start, you can add it to the [Auto] section of your FSUIPC7.ini (or the same in a profile), like so:

Quote

[Auto]
1=Lua HidDemo

 

4 minutes ago, ez_aviator said:

Plus, I have run the HidDemo script, with the details gleaned from the HidScanner log - see attached, and nothing appears to be seen.
Should I have to have the device visible within FSUIPC7 first.

I've already seen that. As I said, better to run FSUIPC7 and show me your .log, .ini and Jotscan.csv files.
However, if HidScanner thinks its a mouse, I presume so will FSUIPC7 and so you will not see it.

[ez_aviator]

Hi John,

Sorry I repeated the Scanner log.
I just did a hardware reset on the XK80 device, and now it's appearing in the FSUIPC7.ini and Joyscan.csv - both attached.

Is this now a possibility?

Thanks

For some reason the site says I can only upload 0kb of data!

Therefore I have copied and pasted the results.

FSUIPC7.ini:
=============

[Sounds]
Device1=Primary Sound Driver
Device2=Speakers (Realtek High Definition Audio)
Device3=LG FULL HD (NVIDIA High Definition Audio)

[General]
UpdatedByVersion=7000
UseSystemTime=No
JoystickTimeout=20
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
UseProfiles=Yes
WideLuaGlobals=Yes
InvokeFSUIPCOptionsKey=70,12
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
LogOptionProtect=Yes
AutoConnectToSim=Yes
AutoExitWithSim=Yes
TimeForLuaClosing=2
TrafficStallTime=1
InitialStallTime=30
NormalStallTime=1
LuaRerunDelay=66
ComReadLoopTime=20
Window=-1550,105,-725,929
Console=No
ConsoleWindowTopMost=No
ConsoleWindow=130,130,1123,649
ControlsListBuild=999

[JoyNames]
A=Controller (Xbox One For Windows)
A.GUID={BF4D1CD0-1C52-11EB-8001-444553540000}
B=T.16000M
B.GUID={50AFC3C0-19C5-11EB-8005-444553540000}
0=T.16000M
0.GUID={50AFC3C0-19C5-11EB-8005-444553540000}
1=XK-80 HID
1.GUID={DA4B6680-2298-11EB-8002-444553540000}
C=XK-80 HID
C.GUID={DA4B6680-2298-11EB-8002-444553540000}

[JoystickCalibration]
RudderBlendLowest=1
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60

[Axes]
PollInterval=10
RangeRepeatRate=10

[Buttons]
PollInterval=25
ButtonRepeat=20,10
2=UB,2,C65607,0     -{ELEV_TRIM_DN}-
3=UB,3,C65607,0     -{ELEV_TRIM_DN}-
4=PB,4,CL1:R,0     -{Lua HidDemoXK80}-
5=PB,6,CL2:R,0     -{Lua MyDisplay}-
6=PB,9,C1084,0     -{}-
7=PB,13,CL3:R,0     -{Lua display vals}-
8=PB,8,C1084,0     -{}-

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002

[LuaFiles]
1=HidDemoXK80
2=MyDisplay
3=display vals

JOYSCAN.CSV:
=============

Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk?

,,, HIDscanning completed

N, x00, x044F, xB10A, , -1, -1, 0, {NULL}, {NULL}, {50AFC3C0-19C5-11EB-8005-444553540000}, Y, N
N, x00, x05F3, x0443, , -1, -1, 0, {NULL}, {NULL}, {DA4B6680-2298-11EB-8002-444553540000}, Y, N

,,, REGscanning completed

N, x00, x044F, xB10A, T.16000M, -1, 0, 0, {NULL}, {50AFC3C0-19C5-11EB-8005-444553540000}, {50AFC3C0-19C5-11EB-8005-444553540000}, Y, Y
N, x00, x05F3, x0443, XK-80 HID, -1, 1, 1, {NULL}, {DA4B6680-2298-11EB-8002-444553540000}, {DA4B6680-2298-11EB-8002-444553540000}, Y, Y
N, x00, x05F3, x0443, XK-80 HID, -1, -1, 0, {NULL}, {DA4B6680-2298-11EB-8001-444553540000}, {NULL}, N, N

,,, User settings imported

N, x00, x044F, xB10A, T.16000M, 0, 0, 0, {50AFC3C0-19C5-11EB-8005-444553540000}, {50AFC3C0-19C5-11EB-8005-444553540000}, {50AFC3C0-19C5-11EB-8005-444553540000}, Y, Y
N, x00, x05F3, x0443, XK-80 HID, -1, 1, 1, {NULL}, {DA4B6680-2298-11EB-8002-444553540000}, {DA4B6680-2298-11EB-8002-444553540000}, Y, Y
N, x00, x05F3, x0443, XK-80 HID, -1, -1, 0, {NULL}, {DA4B6680-2298-11EB-8001-444553540000}, {NULL}, N, N

,,, Values matched and decided

Y, x1E, x044F, xB10A, T.16000M, 0, 0, 0, {50AFC3C0-19C5-11EB-8005-444553540000}, {50AFC3C0-19C5-11EB-8005-444553540000}, {50AFC3C0-19C5-11EB-8005-444553540000}, Y, Y
Y, x1E, x05F3, x0443, XK-80 HID, 1, 1, 1, {NULL}, {DA4B6680-2298-11EB-8002-444553540000}, {DA4B6680-2298-11EB-8002-444553540000}, Y, Y
N, x11, x05F3, x0443, XK-80 HID, -1, -1, 0, {NULL}, {DA4B6680-2298-11EB-8001-444553540000}, {NULL}, N, N

Cheers

[John Dowson]

52 minutes ago, ez_aviator said:

Is this now a possibility?

No idea, but maybe your device was in a weird state....

So its recognized and you are good to go, no?