📊 Community Feedback: Is this Scale Cockpit Framework interesting?

[Spitfire-developer]

Hi everyone!

To help me decide the future of the SpitFW framework, I would love to hear your thoughts.

Thanks to the new ETHOS 2.0.0 and FW 26.1.2 version, the RAM management issues are now almost resolved—to the point where this framework is very close to being fully usable on real models.

Please leave a quick comment below:
👍 "This is awesome, I find it highly interesting for my models!"
👎 "Not really interested, drop the project."

Any feedback, ideas, or simple words of encouragement are highly appreciated. Let me know if it's worth continuing!

Spitfire -developer

[modelist1]

👍

[Spitfire-developer]

Thank you so much for the support and the thumbs up! It really means a lot to me and gives me the motivation to keep working on this framework.

I would be absolutely thrilled to connect with you for future brainstorming, sharing ideas, and exchanging technical advice as the project evolves. Looking forward to keeping in touch! ✈️🦾
Massimo

[modelist1]

Looking forward to it. Plan to use it for a P47 with a 5 cylinder.

[Spitfire-developer]

Wow, a P-47 with a 5-cylinder engine sounds absolutely amazing! That is the perfect model for a scale cockpit simulation. Is she from CARF? I love Razorback version! While I am troubleshooting the widget, I will try to start looking into the instrumentation layout for the P-47. I will keep you posted! ✈️🇺🇸🔥

[modelist1]

No the carf would not fit in my car. This is a "small" one

[mgsanna]

👍🏻

[Spitfire-developer]

Hi Marco , thank you for your feedback, very very appreciated!.
Grazie .
Massimo

[Spitfire-developer]

Hi everybody,

I finally managed to set up the one-click demo link in the SpitFW repository README.

The link now launches the ETHOS 26.1.2 X20RS EU simulator and automatically loads the compact SpitFW build from the GitHub release.

This makes it possible to try SpitFW directly in the browser without any manual installation.

Any feedback, ideas, or simple words of encouragement are highly appreciated. Let me know if it works fine.

Best regards,
Massimo

https://github.com/Spitfire-developer/spitfw-presentation

[Benno00]

great project

[Spitfire-developer]

Thanks for the follow, Benno00! Stay tuned, as there is plenty more to come.

[Spitfire-developer]

Hi @Benno00, following up on my previous message: since you have great experience with the ETHOS ecosystem and LUA scripting, I’d really value your technical input.
If you have a chance to try the browser demo, please let me know if you see any areas for improvement, architectural changes, or optimization tweaks that could benefit the framework. Also, if you have any questions or need any technical clarifications on how it works, please feel free to ask anytime. I'd love to hear your thoughts!"

[Benno00]

Hi Spifire-developer,
my suggestion for improvement would be a language file to translate the text accordingly.
It’s a really lovely project and runs very well in the online simulator.

[Spitfire-developer]

Hi Benno,

Thank you very much! That’s a really good suggestion, and I’ll definitely keep the language-file idea in mind for a future version.

I’m also very happy to hear that you tried it in the online simulator and that it runs well. If you find SpitFW useful, a GitHub ⭐ would also be greatly appreciated and would help the project get a little more visibility.

Best regards,
Massimo

[Benno00]

Hi Massimo,

You could potentially consolidate the configuration using a panel; that would make it clearer.
For your Instruments

would then look something like this "form.addExpansionPanel"

[modelist1]

Will look into how to install it on my x20 proaw and on my x18 during the weekend.

[Spitfire-developer]

Hi modelist1,

Thank you! 😊 I'm really glad you're going to try SpitFW on your X20 Pro and X18.

The installation is quite simple, but if anything is unclear, just ask me. The project is modular, so there are a few files and folders to put in the correct places.

And please don't hesitate to ask about anything during the installation or testing. I'm especially interested in hearing how it behaves on the real X20 Pro and X18.

Thanks again for taking the time to try it! 👍

Spitfire-developer

[modelist1]

Downloaded the cockpit: bitmaps, models, scripts and radio.bin.

Where do I put these on my x20?

[Spitfire-developer]

Hi! Before copying anything, let's check a few things on your X20 so I can give you the correct instructions for your particular setup.

First of all: Have you ever installed an ETHOS widget on your radio? , .and whats the Radio FW ? we need 26.1.2 version on your Radio..

[Spitfire-developer]

Hi @Benno00

The project is now in good shape, and the new configuration structure is working well. I'm preparing a cleaner presentation of the project, including the new tile-based interface and touch controls.

I haven't put the new version online yet because I want to finish the presentation and the online simulator package properly first.

But I thought I'd give you a preview of how SpitFW is looking now.

I've attached a few screenshots — the interface is still in Italian for now, but I think the structure and icons make it much more intuitive and cleaner than the previous version.

So… stay tuned. 😉

[modelist1]

Yes i have several on my x20proaw none on my x18. And yes I am on 26.1.2 on both of them.

[Spitfire-developer]

Hi @modelist1, here is how to correctly place the files on your X20:
First, do not use the radio.bin file. Please use your own existing radio.bin on your radio's root directory, as using mine could overwrite your personal radio configurations.
Here is where to put the actual framework files on your SD card root:
• scripts/ (CRITICAL): Copy the entire contents of this folder into the scripts/ directory on your radio. It contains 17 folders in total. Most of them hold the instrument images, while the others contain the core engine that runs the framework.
• models/ (Optional): This contains my test model configuration (prova-spit.bin). If you want to use it, copy it into the models/ folder on your radio.
• bitmaps/ (Optional): Inside this folder, you will find a subfolder named models/ containing the Spitfire image (spit.bmp). If you want the model picture to show up on your radio, copy this .bmp file into your radio's bitmaps/models/ directory.
Let me know if everything loads correctly or if you need any help setting it up!

[Spitfire-developer]

I hope this explanation is clear enough. If you run into any issues, let me know and we will figure out how to solve them.

[modelist1]

I installed it on my x18 and installation was easy and straightforward. Everything worked and I think I can work out the meaning of the italian texts. Only problem I already expected it did not really displayed correctly on the small x18 screen. This evening and tomorrow I thus going to install it on my x20proaw and try linking it to the telemetry for now using a flightline spit. If that works going for my P47. The other example with the touch switches I tried in the sim and worked fine and is nice but I do not see me using it except for demo of what the frsky can do.

[Spitfire-developer]

Thanks a lot!

I'm really glad to hear that the installation on the X18 was easy and that everything is working.

Yes, the X18 screen is unfortunately a bit too small for the current SpitFW cockpit layout. The X20/X20 Pro is really where it was designed to fit properly.

I'm very interested to hear how it behaves on your X20 Pro AW with the Flightline Spit and telemetry. And if that works, the P-47 sounds like a great next test! 😄

Thanks again for taking the time to test it and give feedback.

About the touch controls, I understand your point.

My idea is not to replace the physical switches. I see the touchscreen more as an additional, easily visible control panel right in front of you.

For example, with something like IGNITION, I can immediately see whether it is ON or OFF, without having to remember which physical switch is assigned to it. And if I need to change it, I can simply touch the corresponding button on the screen.

So for me it is mainly about visibility and convenience: the information and the control are in the same place, directly in front of your eyes.

Of course, the physical switch remains available when you prefer to use it.

I simply see it as one more possibility offered by this great radio and by the ETHOS software. 😄

Have fun!
Massimo / Spitfire-developer

[modelist1]

Hi Massimo, Used to have a spectrum ix20 but never regretted switching. Spectrum is nice and easy to program but overpriced for outdated hard and software. I see you point for an easy to check screen for switches. Never thought about that option but now I want it. Instead of checking each switch individually i see them at once. Very useful for my big planes with many options like P47 and me turbines! Just installed on my x20 and it looks great. Now the next step is binding to the telemetry etc. Great job (also what I missed on my Spectrum the active community)

[Spitfire-developer]

Thanks a lot! 😄

And yes — that is exactly what I was hoping for with the touch controls: not replacing the physical switches, but giving you a clear overview of the important functions directly on the screen.

Especially on a big model like a P-47 or a turbine aircraft with many functions, being able to see immediately what is ON or OFF can be really useful.

I'm very happy that you installed it on your X20 and that you like how it looks!

Now I'm really curious to see how it works once you connect it to telemetry and start using it with your models. 😄

And yes… the active community is probably one of the best things about ETHOS!

Thanks again for testing it and for the great feedback! 👍 (please , if you really like multitoggles a star is useful for visibility ;-) )

Massimo / Spitfire-developer

[modelist1]

One star is given! Cannot wait for the new version you just described in the group but for now its amazing. Just working on the spitfire and got a couple of dials working such as voltage and I REALLY like it. Highest compliments for such an amazing performance!

[Spitfire-developer]

Thank you so much! 😄
This really means a lot to me, especially because you are actually installing it and testing it on your Spitfire.

I'm very happy that the instruments are already working for you and that you like the result. And believe me… the new version is getting even more interesting. 😉

Thanks again for the star and for the fantastic feedback! 🍻

Stay tuned! 😄

[modelist1]

Hi, I am working with your cockpit dials. I have some remarks. 1: in the artificial horizon you need to have some possibility for offsets. My receiver is not fully mounted flat and also sideways. My ah is thus totally of 2: if I understand the fuel cauge decreases depending on the throttle position. However I have a sensor in my spitfire that measures current and have a variable that calculates remaining capacity (and a variable based on a switch that specifies basr capacity of the lipo). Which is more accurate than throttle position. The same applies for my turbines which delivers amount per min and amount consumed. It would thus be advantageous to use any of these. Regards, Ferdie

[Spitfire-developer]

Hi Ferdie! 😊

Thanks again for your feedback! Let me explain the thinking behind the current AFG fuel gauge.

The AFG was originally designed mainly for combustion-powered models, using petrol or methanol, where a dedicated fuel sensor is not always available.

In the AFG configuration, you can set the estimated fuel consumption at idle and at full throttle. By entering realistic values for these two limits and checking the actual fuel remaining after each flight, you can progressively fine-tune the settings over several flights.

The aim is to obtain a reasonably accurate estimate of the remaining fuel. However, I would always recommend treating the displayed remaining quantity conservatively: in other words, it is better for the gauge to underestimate the fuel remaining than to overestimate it.

This approach is intended to be more useful than a simple timer set to a fixed number of minutes, because the estimate takes the intermediate throttle positions into account rather than assuming a constant flight duration or consumption rate.

Of course, an estimate based on throttle position cannot replace a real measurement.

Your suggestion of using actual telemetry data is therefore very interesting. Unfortunately, I don't currently have a dedicated fuel-flow sensor or ECU telemetry setup that I could use to develop and test this functionality myself.

Perhaps someone in the community with experience in this area could suggest which ETHOS telemetry value would be most suitable. For example, it might be a remaining-fuel value, actual fuel consumption, or a fuel-flow measurement from a sensor or turbine ECU.

If we can identify a suitable telemetry source and understand its units and behaviour, I can investigate how to make it available as an alternative input for AFG, while retaining the existing estimation method for models without dedicated sensors.

Regarding the AH6A, the existing reset function can be activated by touching the instrument: "Usa tocco sullo strumento per il reset" must be enable in configuration AH6A. Alternatively, if touch reset is not enabled, you can use the dedicated "Interruttore Bolla (Reset)" switch configured for that purpose.

Have you tried the existing reset function? I'd be interested to know whether it corrects the initial attitude sufficiently with your receiver mounting, or whether additional sensor alignment adjustments are needed.

Thanks again for testing SpitFW and helping me improve it!

Best regards,
Massimo

[Benno00]

[Spitfire-developer]

"Haha, classic email notification loop! 😂
By the way, following up on your previous feedback: I am currently refactoring the configuration menus to make them much more readable and I'm implementing full English language support right now.
Thanks again for the great tips, I'll keep you posted on the progress!"

[Spitfire-developer]

What do you think about that?

[modelist1]

Like it, a lot.

[modelist1]

As to the fuel I have a some of the sensors and can help with the names. But the easiest is to let the user select a telemetry value and let the user select 0 and 100 as min and max and warning value. The needle just displays the selected telemetry value. For example i use the frsky current sensors when flying electric. From these it is easy to develop a percentage. Thus the needle start at 100 (% or liter to make the display nice and rge calculated value drops when flying and when at 30 (my selected value) it gives a warning. This works with most of my lipo’s as the percentage remaining is calculated based on a switch. So top position is a lipo of 6000, middle 5200 and low 4500. So whatever i placed in the plane as long as the switch is in correct postion (confirmed by audio outputting the capacity) half used is always 50% and the needle should be in the middle. Thus using throttle without a sensor your formula, selecting a calculated parameter needle is equal to parameter.

[Spitfire-developer]

Hi Ferdie! 😊

Thank you! This is a very useful and concrete suggestion.

I think the best approach would be to retain the existing AFG estimation method for combustion-powered models without dedicated fuel sensors, while adding an alternative telemetry mode.

In this new mode, the user could select a telemetry source, configure the minimum and maximum values for the gauge, and set a warning threshold. The needle would then display the selected value directly.

Your battery example is particularly interesting. If the remaining capacity percentage is already calculated from the current sensor and the selected battery capacity, AFG would not need to calculate it again. It could simply use that value as its input.

The same principle could work with a suitable remaining-fuel value from a turbine ECU or another telemetry sensor.

I would like to make this as generic as possible, so that users can select the source that best suits their model.

Could you share the exact names of the telemetry sources or calculated variables you use? It would also be useful to know which values are available from your current sensors and turbine ECU, and what units they use.

That would help me design the new mode around real examples rather than assumptions.

Thanks again for helping me improve SpitFW!

Best regards,
Massimo

[modelist1]

Will send you some shots tomorrow.

[modelist1]

This is how I solved it for the current sensor from frsky Telemetry sensors Sensors in detail Switch defines which at which consumption the lipo is at 30% thus which lipo I placed And example of one placed lipo if switch is changed Message if remaing capacity is 30%

[Spitfire-developer]

Hi Ferdie! 😊

Thank you for sharing this. I'm re-posting your images here so they stay visible in this thread.

""
This is how I solved it for the current sensor from frsky

Telemetry sensors

Sensors in detail

Switch defines which at which consumption the lipo is at 30% thus which lipo I placed

And example of one placed lipo if switch is changed

Message if remaing capacity is 30%

"

[Spitfire-developer]

Hi Ferdie,

I have now added a telemetry mode to the AFG instrument in SpitFW,
while keeping the original throttle-based estimation mode.

I have documented the configuration here:
AFG Configuration

In telemetry mode, the instrument can read a selected source,
such as a cumulative consumption sensor configured in ETHOS,
and use the configured capacity and reserve threshold to drive
the gauge and warning indication.

I have tested the basic operation using a stick as a test source.
The next step is to test it with a real cumulative consumption
sensor.

Your setup could be a useful real-world test case.

I am currently organizing the documentation and discussing the
next steps for the project before preparing another simulator
package.

I will keep you updated.

[modelist1]

Just let me know once i can download a new version to do some real world testing.

[Spitfire-developer]

Hi Ferdie,

The new SpitFW release is now available:

It includes the new AFG telemetry mode alongside the original
throttle-based estimation mode.

[Spitfire-developer]

@Benno00 @modelist1

Hi Benno00 and modelist1,

I have finally created a new release for the updated version of SpitFW!
You can find the link here: v0.3.0-preview

As you know, on the main spitfw-presentation repository, I added the "Try SpitFW now in your browser" link, which should point to this new release so you can try it directly in the web simulator.

Thanks a lot for your help and let me know if you like this new version!

Massimo
Spitfie-developer

[Spitfire-developer]

Hi Ferdie and Benno00,

I have some really exciting news to share! 🚀

I have just published a complete, brand-new User Manual for SpitFW. It’s a comprehensive 8-chapter guide designed to make the widget accessible to everyone, from first-time users to advanced pilots.

The manual covers:

Installation & Setup: How to get SpitFW running on your radio.

Multiple Instances: The golden rules for setting up different windows (Engine, Flight, etc.) on the same model.

Configuration: A walkthrough of the tile-based menu and X/Y positioning.

Instrument Guide: A detailed breakdown of all 15+ instruments, including a special focus on the new AFG Telemetry mode (which was heavily inspired by your input, Ferdie!).

Troubleshooting & FAQ: Solutions to common issues and advanced tips (like how to customize the PNG graphics).

You can read the introduction and navigate through the whole manual here:
👉 SpitFW User Manual

(The full manual is also linked in the main README, right under the "Try SpitFW in your browser" link).

I wrote this to make it as easy as possible for new users to understand the power of SpitFW without having to dig through the code.

I would love to hear your thoughts! If you have a moment to read through it, please let me know if anything is unclear, or if you think I missed something important. Your feedback is always incredibly valuable.

Thanks again for your continuous support and for testing the early versions!

Best regards,
Massimo \ Spitfire-developer

[modelist1]

Coming weekend I will do a real life test with my flightline spit before transferring to my large P47. Will keep you informed.