info@mpsdevelopment.com

On-Board Systems

2D and 3D views of on-board systems are used in Computer Based Trainings (CBT) and in Instructor Operating Stations (IOS) to show current device control positions. In case of CBT this controls are interactable and user can use mouse or touch screen to press this controls. In case of IOS this controls are read-only for visualization purposes only. Note that same codebase is used in both cases. Also this controls are one of On-Board system views. Due to our pluggable architecture (and Model-View-Controller architecture pattern) different viewpoints can be attached to OnBoard Systems model – like this 2D or 3D views or hardware in-cockpit controls.

Our qualified subject matter experts and electrotechnical engineers can investigate technical manuals and electrotechnical on-board system schemes and model work and cooperation of on-board devices during simulation. The approach is to model inner work of some real aircraft’s On-Board systems (like engines, hydraulic, electric, warning, pneumatic systems etc.) as much as possible based on manuals and schemes of the aircraft.

We develop both-way interactions between simulator and hardware cockpit devices. We also develop displaying of the current state of the devices at instructor operating stations and a mechanism of introducing device malfunctions for teaching crew to operate an aircraft in critical conditions.

One of the most important cases when this can be used is to model logic of the on-board systems of a simulated unit for teaching board engineers such complex procedures as turning an aircraft on or off, taking off and landing, on-board systems management, different maintenance tasks, aircraft flight preparations etc.

Work of on-board systems on Computer Based Training

At the time of flight the onboard systems that we developed interact with a flight module. Flight control actions are processed by our code and affect the flight of a simulated aircraft. Sensors and gauges get information from the flight module and environment to show the actual state of aircraft flight on different instrument panels. Maximal realism is modelled, even icing effect affects on-board systems simulation.

This window displays states of Hydraulic and AI-9 Engine on-board systems at Instructor Operating Station. Also using this window instructor can introduce on-board systems malfunctions

We also develop modules that control hardware for in-cockpit realism. For example, we manage in-cockpit sounds and illumination playbacks  depending on the in-cockpit events and the level of force on control elements.

Here you can see helicopter flight with on-board systems. Due to our pluggable architecture helicopter can be operate both from in-cockpit controls or joystick / game controls.

We develop on-boards systems with a good level of abstraction and the model is fully distinguished from the view layer. An on-board systems model are shared through HLA between hardware devices and an instructor operating station. Two-way interaction allows synchronizing the states of controls both at the instructor operating station and inside the cockpit, and allows an instructor to introduce device malfunctions. Any new view to this model can also be introduced independently without changing the skeleton. For example, we can add some 3D cockpit views with actual visualization and reaction with on-board system controls.

Here is modelling of sounds effects in case of on board systems failure. Same lights and sounds can be reproduced inside a cockpit

We also develop On-Board systems testing framework for effective testing of on-board systems. QA Engineer (Tester) can test devices and modules of on-board systems independently in the same way as the whole simulator testing with using pre-configured On-Board system states. This technology allows us to increase quality of On-Board Systems and drastically decrease time and expenses on On-Board Systems testing process.

Here testing of AI-9 engine module is demonstrated. Using set of input variables and with changing them in real-time, QA engineer can see if Output signals (in the right) and correspondent device goggles (in the top) works correct.

You can read in more detail about On-Board systems testing framework in On-Board systems testing framework section.

Top
Have a question? Write us!Send message