15 questions · All topics
01Do I need programming skills?
No. You do not need programming skills to use Cockpit Suite and configure supported modules. Custom hardware may require you to adapt some code.
02Can I program my hardware with the Arduino IDE?
Yes. We provide example code for communication with Cockpit Suite, device identification and receiving data. Use it as a starting point for your Arduino or microcontroller and add the functions for your switches, LEDs or displays.
03Can I use ready-made controller boards?
Yes. Supported ready-made boards make getting started easier. Boards designed for this purpose let you connect the power supply, LEDs and toggle switches without developing your own firmware. Check the board’s compatibility, connections and specifications before buying.
04Does Cockpit Suite work with DIY hardware?
Yes, if your controller uses a compatible interface and data format. Our example code shows how to identify the device and receive Cockpit Suite data. You can adapt it to your hardware without developing the entire communication from scratch.
05Can I combine ready-made boards and DIY hardware?
Yes, provided the devices are supported or connected through a compatible interface. For example, use ready-made boards for switches and your own controllers for special displays.
06Which simulators can I use with Cockpit Suite?
BMS and DCS F-16C are available as final modules with hardware support. War Thunder, ETS2 and ATS are beta modules with hardware support. LS25 remains in development, awaiting approval from the manufacturer.
07What is the difference between Live Hub and Client?
Live Hub connects to the simulator and manages profiles, data and permissions. The Client receives shared displays on another PC in your network.
08Do I need several PCs for my cockpit?
No. Additional PCs are optional. A Client is useful when you want to distribute displays across other computers.
09Can I save separate settings for each simulator?
Yes. Simulator profiles keep settings and assignments separate, so you can configure your cockpit for different simulators.
10How do I assign simulator data to my controllers?
Use profiles and the Controller Workshop to select supported data, configure data chains and assign them to your devices.
11Can I test my configuration without real hardware?
The Controller Simulator helps you check data chains and transmitted values. You still need to test the final setup on your actual hardware.
12Can I put instrument displays on several monitors?
Supported displays can be detached into separate windows and placed on your monitors. Available displays depend on the simulator module.
13Can I start with a small cockpit?
Yes. A small piece of wood or plywood with holes for a few toggle switches, some LEDs or a display is enough to get started. It does not have to be perfect. Once your first functions work, you can expand and refine your cockpit step by step. A complete replica is not required.
14Do I have to register Cockpit Suite?
No. Basic functions can be used without registration. Planned: hardware buyers receive a registration number that unlocks additional functions in supported modules. The corresponding Live Hub menu items appear after registration is confirmed. This feature unlock has not been implemented yet.
15Will the standalone MFD Viewers remain free?
Yes. The standalone DX9, DX11 and GDI MFD Viewers remain free and do not require a serial number. They are separate applications alongside Cockpit Suite Live Hub and Client.
No matching question found. Try another search term or choose “All questions”.
Still have a question?
Tell us what you want to build and which simulator you use.