https://github.com/landre-cerp/wctrldcsbiosbridge
Bridge between Winctrl CDUs , Frontpanels and DCS using DCSBios
https://github.com/landre-cerp/wctrldcsbiosbridge
cdu dcs efis fcu mcdu pdc3n pfp3n pfp4 pfp7 winctrl winwing
Last synced: 19 days ago
JSON representation
Bridge between Winctrl CDUs , Frontpanels and DCS using DCSBios
- Host: GitHub
- URL: https://github.com/landre-cerp/wctrldcsbiosbridge
- Owner: landre-cerp
- License: mit
- Created: 2025-08-08T17:40:12.000Z (11 months ago)
- Default Branch: main
- Last Pushed: 2026-06-04T21:26:39.000Z (23 days ago)
- Last Synced: 2026-06-04T21:37:41.037Z (23 days ago)
- Topics: cdu, dcs, efis, fcu, mcdu, pdc3n, pfp3n, pfp4, pfp7, winctrl, winwing
- Language: C#
- Homepage:
- Size: 1.11 MB
- Stars: 23
- Watchers: 2
- Forks: 5
- Open Issues: 10
-
Metadata Files:
- Readme: README.md
- Contributing: docs/CONTRIBUTING.md
- Funding: .github/FUNDING.yml
- License: LICENSE.txt
Awesome Lists containing this project
README
[![Release][release-shield]][release-url]
[![Discord][discord-shield]][discord-invite-url]
![Build Status][build-shield]
[![Pre-Release][pre-release-shield]][pre-release-url]
# WctrlDcsBiosBridge
This console application bridges DCS World with some of the WinCtrl hardware, enabling real-time data exchange between the simulator and the physical device.
**Data Flow:** DCS <-> DCS-BIOS <-> This App <-> WinCtrl CDUs (and FCU)
## Quick Start
1. **Install DCS-BIOS** (see detailed instructions below)
2. **Download and extract** this application to your preferred folder
5. **Connect** your WinCtrl CDU ( before starting bridge )
6. **run** the application
7. **Launch DCS** and select your aircraft from the CDU menu
## Requirements
- DCS World
- DCS-BIOS [v0.11.0](https://github.com/DCS-Skunkworks/dcs-bios/releases/tag/v0.11.0) or later (0.11.4 recommended as it updates the ch47 cdu pages)
- .NET 8.0 runtime
At least one of these devices.
- WinCtrl CDU hardware (MCDU / PFP3N / PFP7 / PFP4)
- WinCtrl FCU and EFIS ( tested with Left Efis )
- WinCtrl PAP3 (or PAP3Mag )
## Supported Aircraft
| Aircraft | Support Level | Features |
|----------|---------------|----------|
| **A10C** | Full | Complete CDU functionality, LED indicators, brightness control , FCU display (VS , Alt, Speed, HDG , Qnh on Efis ) |
| **AH-64D** | Basic | UFD information, keyboard display |
| **FA-18C** | Basic | UFC fields display |
| **CH-47F** | Basic | Pilot or CoPilot CDU (requires DCS-BIOS nightly build) |
| **OH-58D** | Basic | MPD/TGT/TRQ/CMWS CDU display support |
| **F15E** | Basic | UFC Lines 1-6 by smreki |
| **M2K** | Basic | see documentation in docs/ |
### LED Mappings (A10C)
| MCDU LED | DCS Indicator |
|----------|---------------|
| Fail | Master Caution |
| FM1 | Gun Ready |
| IND | NWS Indicator |
| FM2 | Cockpit Indicator |
### LED Mappings other aircraft
| MCDU LED | DCS Indicator |
|----------|---------------|
| CDU LED | DCS Indicator |
| Fail | Master Caution |
## Installation
### DCS-BIOS Setup
1. **Download** the latest DCS-BIOS release (min v0.11.0):
- Standard: https://github.com/DCS-Skunkworks/dcs-bios/releases
2. **Extract** the DCS-BIOS folder to your DCS saved games Scripts directory:
```
%USERPROFILE%\Saved Games\DCS\Scripts\DCS-BIOS\
```
3. **Configure Export.lua** in your Scripts folder:
```lua
dofile(lfs.writedir() .. [[Scripts\DCS-BIOS\BIOS.lua]])
```
⚠️ **Important:** If you already have an Export.lua file, add the line above instead of overwriting it.
### Application Setup
1. **Extract** the application files to your chosen directory
2. **Run** `WctrlDcsBiosBridge.exe`
if no config.json is found, it will create a default one and show you a dialog box to edit it.
3. Select the **File locations** at `DCS-BIOS` JSON folder. It should be located inside the `Scripts/DCS-BIOS/doc/json` folder.
* Example (as default in your Saved Games): `Saved Games/DCS/Scripts/DCS-BIOS/doc/json`
⚠️ **Important:** When updating the application, do not overwrite your existing `config.json` file.
## Usage
### Controls
- **CDU Keys:** Map them in DCS.
- **Aircraft Selection:** Use line select keys on startup screen
## Troubleshooting
### Common Issues
**"PLT_CDU_LINE1" does not exist (CH-47 Chinook)**
- Wrong dcsbios version installed.
- You need version 0.11.0 or later
**"Connection failed" or CDU not responding**
- Ensure your WinCtrl CDU is properly connected
- Try unplugging and reconnecting the device
- Check that no other applications are using the CDU
**"No data appearing on CDU"**
- Start your aircraft in DCS (data appears after aircraft systems are powered)
- Check that DCS-BIOS is working (look for network traffic) - you can use Bort tools from DCSSkunkworks to verify DCS-BIOS is sending data
- Verify Export.lua is configured correctly
**Aircraft change not working**
- Restart the application when switching aircraft
- Each aircraft requires a separate application instance
**Start bridge is greyed**
- You probably launched the app before plugging your devices.
- Exit application, plug all the cdus you plan to use and launch the app again
### Brightness Issues
- **Mismatched brightness:** Use the aircraft's brightness controls first, then adjust MCDU
- **A10C:** MCDU brightness is linked to the console rotary control (right pedestal)
- **CH-47F:** Check the [specific documentation](docs/CH-47F.md)
- In case of flickering with SimAppPro running, check the
### Logs
All application activity is logged to `log.txt` in the same folder as the executable. Check this file for detailed error information.
Report issues [here](https://github.com/landre-cerp/WWCduDcsBiosBridge/issues), or reach out on Discord [![Discord][discord-shield]][discord-invite-url].
## Known Limitations
- **Aircraft switching:** Requires application restart
- **Cursor behavior:** May appear erratic during waypoint entry (reflects DCS-BIOS data)
- **CH-47F support:** Requires DCS-BIOS nightly build (0.11.0 or later)
- **Brightness sync:** May not perfectly match aircraft state
## Development
This project is written in C# and targets .NET 8.0. It uses:
- **DCS-BIOS** for DCS communication
- **ww-devices-dotnet** for WinCtrl hardware interface
- **NLog** for logging
- **System.CommandLine** for command-line parsing
## Contributing
see `docs/CONTRIBUTING.md` for contribution guidelines. [link](docs/CONTRIBUTING.md)
## License
See `LICENSE.txt` and `thirdparty-licences.txt` for licensing information.
## Support
For issues and questions, please check the logs first and review the troubleshooting section above.
and if you want, no need, you can [Buy Me a Coffee](https://www.buymeacoffee.com/cerppo)
[release-url]: https://github.com/landre-cerp/WWCduDcsBiosBridge/releases
[release-shield]: https://img.shields.io/github/release/landre-cerp/WWCduDcsBiosBridge.svg
[discord-shield]: https://img.shields.io/discord/231115945047883778
[discord-invite-url]: https://discord.gg/Td2cGvMhVC
[dcs-forum-discussion]: https://forum.dcs.world/topic/368056-winwing-mcdu-can-it-be-used-in-dcs-for-other-aircraft/page/4/
[build-shield]: https://img.shields.io/github/actions/workflow/status/landre-cerp/WWCduDcsBiosBridge/build-on-tag.yml
[pre-release-shield]: https://img.shields.io/github/v/release/landre-cerp/WWCduDcsBiosBridge?include_prereleases&sort=semver
[pre-release-url]: https://github.com/landre-cerp/WWCduDcsBiosBridge/releases