maxb-odessa/x52mfd

This is to control your Saitek x52(pro) joystick. Exec a proggie and communicate with it via STDIN/STDOUT. Read joystick events from proggie's STDOUT and process them. Write joystick events to proggie's STDIN.

x52mfd

This is to control your Saitek x52(pro) joystick

Exec a proggie and communicate with it via STDIN/STDOUT Read joustick events from proggie's STDOUT and process them. Write joystick events to proggie's STDIN.

Built on libx52

LEDS and MFD commands and such

Commands are exactly the same as used by x52cli:

Usage: x52cli <command> [arguments]

Commands:
	led <led-id> <state>
	bri {mfd | led} <brightness level>
	mfd <line> <text in quotes>
	blink { on | off }
	shift { on | off }
	clock {local | gmt} {12hr | 24hr} {ddmmyy | mmddyy | yymmdd}
	offset {2 | 3} <offset from clock 1 in minutes> {12hr | 24hr}
	time <hour> <minute> {12hr | 24hr}
	date <dd> <mm> <yy> {ddmmyy | mmddyy | yymmdd}
	raw <wIndex> <wValue>

WARNING: raw command may damage your device

Exceptions:

* 'raw' command is not supported
* all fields are mandatory

Addition:

* calling proggie must send new command 'update' for prev commands to be applied
* commands and args (except mfd text) are case insensitive
* brightness may be specified by value (0-128) or by percents (0-100%)
* call to 'clock' command will set current time automatically

Examples (bash):

echo "bri mfd 30%"
echo "bri led 30%"
echo update
echo "clock local 24hr ddmmyy"
H=$(date +"%H")
M=$(date +"%M")
echo "time $H $M 24hr"
echo update
echo "mfd 1 \"line one\""
echo "mfd 2 \"line two\""
echo "mfd 3 \"line last!\""
echo update

Led IDs:

* fire
* a
* b
* d
* e
* t1
* t2
* t3
* pov
* clutch
* throttle

Led States:

* off
* on
* red
* amber
* green

BUTTONS and other

x52mfd will send back to called proggie x52pro joystick buttons states. Button name will follow 'on' or 'off' to indicate its state except 'modes' which have 3 states: 1,2 and 3. Axis states are not supported 'cause I see no need in them atm.

Button names could be found in libx52 sources plus I've made some other by myself for HAT, MODE and connection states.

Button names:

* BTN_TRIGGER
* BTN_TRIGGER_2
* BTN_FIRE
* BTN_PINKY
* BTN_A
* BTN_B
* BTN_C
* BTN_D
* BTN_E
* BTN_T1_UP
* BTN_T1_DN
* BTN_T2_UP
* BTN_T2_DN
* BTN_T3_UP
* BTN_T3_DN
* BTN_POV_1_N
* BTN_POV_1_E
* BTN_POV_1_S
* BTN_POV_1_W
* BTN_POV_2_N
* BTN_POV_2_E
* BTN_POV_2_S
* BTN_POV_2_W
* BTN_CLUTCH
* BTN_MOUSE_PRIMARY
* BTN_MOUSE_SECONDARY
* BTN_MOUSE_SCROLL_UP
* BTN_MOUSE_SCROLL_DN
* BTN_FUNCTION
* BTN_START_STOP
* BTN_RESET
* BTN_PG_UP
* BTN_PG_DN
* BTN_UP
* BTN_DN
* BTN_SELECT
* BTN_MODE_1
* BTN_MODE_2
* BTN_MODE_3
* BTN_HAT_N
* BTN_HAT_NE
* BTN_HAT_E
* BTN_HAT_SE
* BTN_HAT_S
* BTN_HAT_SW
* BTN_HAT_W
* BTN_HAT_NW
* MODE
* CONNECTED
* DICONNECTED

Addition:

There are two 'buttons' which could be send to a proggie: 'CONNECTED' and 'DISCONNECTED' indicating current joystick connection status. During disconnection no buttons will be sent and no led or mfd actions will be processed.