iFSim.Ready V2.3.0 Feature Deep Dive: Full Hardware Integration with JeeHell FMGS A320
Communication between a hardware cockpit and flight simulation software is, at its core, a signal-mapping problem between two independent systems — on one side, the discrete and analog signals from physical hardware; on the other, the internal variables and command sets of the simulation software. Different software platforms expose their interfaces in very different ways, which is exactly why "supporting ToLiss" and "supporting JeeHell" represent two completely different engineering efforts for the same hardware.
This time, we're taking a closer look at the JeeHell FMGS A320 integration newly added in iFSim.Ready V2.3.0.
JeeHell's Interface Landscape
JeeHell exposes its interface through two distinct paths. FSUIPC is the primary open interface, aimed at professional and DIY users: JeeHell officially maintains a complete FSUIPC offset reference table, allowing users to read and write these offsets directly to map hardware signals. A large number of home cockpit builders in the community build their own interface solutions on top of this offset table — it's highly open and fully customizable. SDKPRO, on the other hand, is aimed at full-cockpit vendors, provided officially as an interface solution for commercial hardware manufacturers.
Dual-Channel Handling Approach
While mapping the hardware FLAP handle signal to FMGS, we discovered that SDKPRO has no API for absolute FLAP position at all — it only exposes two discrete events, "increment" and "decrement," which cannot accept a continuous analog input. After reviewing the JeeHell FMGS FSUIPC offset documentation, we found that FSUIPC does expose discrete signals for FLAP positions 1 through 5.
This class of signal ended up being handled by writing the absolute detent position directly through the corresponding FSUIPC offset.
This also established our overall channel-selection principle: prioritize SDKPRO, with FSUIPC used only as a fallback. This is primarily a matter of coverage — signals like absolute FLAP position simply have no equivalent API in SDKPRO, so FSUIPC is the only way to fill that gap. As a result, any signal that SDKPRO can handle is routed through the SDKPRO API by default; FSUIPC is only brought in when SDKPRO lacks a suitable interface.
Support Matrix After This Integration
CNFSimulator hardware components now support four major platforms: ToLiss on the X-Plane side, Fenix on MSFS, and ProSim and JeeHell on the P3D side. Regardless of platform or preferred systems-simulation approach, users should be able to find a matching software solution to pair with the same hardware.
Download iFSim.Ready V2.3.0
https://en.cntech.com/blogs/download/ifsim-ready-version-v2-3-0-release-note