j2 Developer is an Application Interface that provides a technique to take external code, written in a variety of languages, and interface it directly into a j2 Aircraft Model.
This can lead to:
- Increased productivity – The speed with which existing systems can be integrated means that models can be created in days.
- Saving costs – Being able to re-use existing components means that their value can be retained rather than starting again.
- Improved connectivity and collaboration – Working with common components across an organisation allows a consistent approach to be utilised
- Collection of data for intelligence analytics – Specific components can be written to study project specific features and run across multiple test cases.
- Building new product capabilities - Additional internal systems and simulations can be developed and tested alongside the air vehicle
- Hardware integration – The API can be used to develop middleware that is able to connect simulations and models to real vehicle hardware
- Protection of Legacy Systems – Where the original developers are no longer available, value can still be gained from existing code and ringfenced with further updates superimposed on top.
This powerful interface capability provides the ability to integrate any parts of the aircraft, provide additional mathematical approaches, controls systems, or even the complete aircraft.
Previous examples have included:
- Aerodynamics from Full Flight Simulator for tuning purposes
- High Fidelity Engine Dynamic Simulation
- Landing Gear and Hard Point Modelling
- Integration of Airborne Flight Control Systems for Evaluation and Test
- Bespoke Fuel Management and Engine Control Systems
- Additional Analytical techniques for Flight Matching Test and Evaluation
- Existing Airframe Fortran Code to evaluate new features
The code can be integrated as is with a simple interface layer being added, it can then be compiled into a Windows™ Dynamic Link Library. The code is then “stitched” into the model by providing the details of the variables that are required by the code .
Outputs can then be inserted back onto the model wherever desired.
For more information about the process flow of j2 Developer Items see j2 Developer Process Flow