https://github.com/andrewdsmith/edxlc
EDXLC is a companion app for the game Elite Dangerous that controls the button lights on your Saitek X52 Pro joystick so that they reflect the current state of your ship in the game.
https://github.com/andrewdsmith/edxlc
elite-dangerous joystick rgb-led x52pro
Last synced: 3 months ago
JSON representation
EDXLC is a companion app for the game Elite Dangerous that controls the button lights on your Saitek X52 Pro joystick so that they reflect the current state of your ship in the game.
- Host: GitHub
- URL: https://github.com/andrewdsmith/edxlc
- Owner: andrewdsmith
- License: other
- Created: 2021-03-27T19:55:53.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2026-03-09T21:20:21.000Z (3 months ago)
- Last Synced: 2026-03-10T03:32:07.696Z (3 months ago)
- Topics: elite-dangerous, joystick, rgb-led, x52pro
- Language: Rust
- Homepage:
- Size: 262 KB
- Stars: 19
- Watchers: 6
- Forks: 6
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- Changelog: Changes.md
- License: COPYING
Awesome Lists containing this project
README
# Elite Dangerous X52 Pro Light Control - EDXLC
**EDXLC** is a companion app for the game **Elite Dangerous** that controls the
button lights on your **Saitek X52 Pro** joystick so that they reflect the
current state of your ship in the game.
Download [the latest zip file][download], unzip, and run `edxlc.exe`. The app
runs in a console window. Exit with `Ctrl`+`C` or just close the console
window.
[download]: https://github.com/andrewdsmith/edxlc/releases/download/v1.12/edxlc_v1.12.zip
On first run the app creates a simple text file called `edxlc.toml`. Edit this
file to change how the app behaves. Restart the app after making any changes to
this file. To reset to defaults delete the file.
The app detects the following:
- Landing gear deployed
- Cargo scoop open
- External lights activated
- Frame shift drive (FSD) charging
- Silent running activated
- Hardpoints deployed
- Night vision activated
Where a game control is bound in game to a button on the joystick, the button
light will indicate the following states:
- Inactive - Green (Off) - Not currently activated but can be activated
- Active - Amber (On) - Currently activated
- Blocked - Red (Off) - Cannot be activated
- Alert - Flashing amber (Flashing) - May need to be activated urgently
An example blocked state is FSD charging while mass-locked or landing gear
deployed. Examples of alert states include heat sinks when overheating and
landing gear when docking permission has been granted.
When hardpoints are deployed, night vision is enabled, or silent running is
activated, then the app switches to an alternative configuration.
The default configurations in `edxlc.toml` are:
```toml
[default]
inactive = ["off", "green"]
active = ["on", "amber"]
blocked = ["off", "red"]
alert = ["flash", "amber-flash"]
[hardpoints-deployed]
inactive = ["off", "red"]
active = ["on", "amber"]
blocked = ["off", "off"]
alert = ["flash", "amber-flash"]
[night-vision]
inactive = ["off", "off"]
active = ["on", "green"]
blocked = ["off", "off"]
alert = ["flash", "green-flash"]
[silent-running]
inactive = ["off", "off"]
active = ["on", "green"]
blocked = ["off", "red"]
alert = ["flash", "green-flash"]
[mfd]
line1 = "EDXLC"
line2 = ""
line3 = ""
```
The `hardpoints-deployed`, `night-vision`, and `silent-running` sections are
optional and will fall back to the values in `default` if missing. The
precendence order is fixed to: `silent-running` > `night-vision` >
`hardpoints-deployed` > `default`
The `[mfd]` section allows you to customize the three lines of text displayed on
the X52 Pro's Multi-Function Display (MFD). If this section is missing, the
first line defaults to `EDXLC`. Each line supports up to 16 characters. Lines
longer than 16 characters will scroll.
For each state you specify the light mode for boolean and red/amber/green
lights. For boolean lights, the supported modes are:
- `off`
- `on`
- `flash`
For red/amber/green lights, the supported modes are:
- `off`
- `red`
- `amber`
- `green`
- `red-flash`
- `red-amber-flash`
- `red-green-flash`
- `amber-flash`
- `amber-green-flash`
- `amber-red-flash`
- `green-flash`
- `green-amber-flash`
- `green-red-flash`
To use an alternative configuration file specify it as a command line argument:
```text
edxlc.exe C:\Path\To\My\config.toml
```
By default the app reads the game control bindings from the `Custom.4.2.binds`
bindings file used by Odyssey. You can use a different bindings file (e.g.
`Custom.3.0.binds` for Horizons) by specifying the full path to the file in the
`bindings` value in the `[files]` section of `config.toml`, e.g.
```toml
[files]
bindings = 'C:\Users\DavidB\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings\Custom.3.0.binds'
```
Important: Due to the way the TOML file format works, you should use single
quote characters around the path (as shown above).
# Contributors
Many thanks to our contributors:
* [andrewdsmith](https://github.com/andrewdsmith)
* [speedyspikes](https://github.com/speedyspikes)
* [midwan](https://github.com/midwan)