Adding a DIY Firmware Configurator; thoughts?

[classicrocker883]

Introductory

If you dont know, but over at mriscoc/Special_Configurations you will find

- Creating your own custom configuration

Which basically generates a sort of "Firmware Selector" (using Python)

---

Key Points

After with the help of @Mik-S-UMS for the Firmware Selector idea, I did some thinking. @yrabbit gave me an idea...
because he uses JD / JUNCTION_DEVIATION instead of CLASSIC_JERK, and also a different Thermistor type.
so what I propose is what if I make something similar to mriscoc's Professional Firmware Configurator;
where one could select different Options/Features and it will either spit out the right Configuration.h|Configuration_adv.h files.
or it will somehow compile and spit out a firmware.bin file on it's own.

Reasons

So already each build release has hundreds of options to choose from. Basically, if I were to also add JUNCTION_DEVIATION as an option instead - it would literally double the firmware files. I mean it is a totally valid option dont get me wrong, but I'm not sure such a great idea because of the sheer amount of files, so im looking if there is a way around.

First before I begin, I have already done something similar using:
configurations_Define_Configuration_adv.h|.h
configurations_Undef_Configuration_adv.h|.h.

I'm not sure if I wrote up a Wiki about it, but I should anyway, simple use instructions can be found here:

• Marlin\src\inc\MarlinConfigPre-1-axes.h
• • //#include "../../../configurations/_Undef_Configuration.h" // **EXPERIMENTAL** Uncomment to use
//#include "../../../configurations/_Define_Configuration.h" // **EXPERIMENTAL** Uncomment to use
• Marlin\src\inc\MarlinConfigPre-4-adv.h
• • //#include "../../../configurations/_Undef_Configuration_adv.h" // **EXPERIMENTAL** Uncomment to use
//#include "../../../configurations/_Define_Configuration_adv.h" // **EXPERIMENTAL** Uncomment to use

Let's get down to business

Here is the point I am trying to make, and here comes the hard part... (To see if it's worth my time DOING).

I propose I write up something similar, except perhaps use my HTML page where the Firmware Selector is.

(Just let me know if this is something I should pursue or not)

Let's say I write up an html page that works either like a simple user interface like Professional Firmware Configurator (pictured above), or the _Define|_Undef_Configuration_adv|.h (probably better suited for the more advanced user - idk, its just a list of all the options).

Then what will happen is this will either create a Codespace or it will ask a user to create a fork of the repo and use Github Actions to make their very own Release which will upload with their edited firmware.bin file.

just looking for thoughts.

I'm just curious if it is even possible for me to add such an endeavor to a webpage, or should I just make/edit a Wiki with the other thing I mention (_Define|_Undef ...)

[yrabbit]

A monumental task:)

Personally, it would be convenient for me to click a button and download the compiled bin in accordance with my config - I would be sure that the sources are the latest version, that the platformIO used is the right version, not to mention that I would not need to run a virtual machine with Linux to compile myself. I don't know how you can organize such on-demand compilation....

Well and with the first part (generation) is also not very simple: at each generation I don't want to start selecting options from scratch, so you have to import the config, but you can't make UI for all options - let's say thermistors can be listed, but my extruder has 565.42 steps or bed 230x220, not standard.

The task is grandiose:)

[yrabbit]

Well I can tell you that the square became square (don't look for this in the photo, it's just an example of how I checked the deviations on millimetre paper).

But through the printer menu it would be an absolute nightmare and there are other considerations:

• yes such precision is needed because you need to compensate for very small deviations on large sizes;

• if the distortions are large, you need to disassemble the printer and reassemble the frame in a normal way;

• the correction is set once and there is no need to enter it again via UI.
  

[classicrocker883]

I calculated your skew factor, and got -0.0025575447569071725 or you could probably say -0.0026, perhaps it doesn't need to be that precise? I know the stock values do calculate to 0.0.

so technically what I can do is instead of you entering those values, you just enter the calculated XZ_SKEW_FACTOR and YZ_SKEW_FACTOR (with skew correction for z enabled).
so if it doesnt need to be so precise that just might work out having it editable in the menu.

[yrabbit]

😆 it never occurred to me to calculate that coefficient. 😄

[classicrocker883]

i tried asking chatgpt using the same calculations, got something different every time, so made a python script to help out
skewfactor.zip

[yrabbit]

Yeah, AI can't count at all - having recently received such an answer, where E = 5 although 6 edges are listed in brackets, I decided that it's not worth messing with these things for now - it will take more time to find errors than if I had figured it out myself from the beginning 😄

[yrabbit]

How about the current Firmware Selector download the conchiguration files at the same time.
Let me explain:
My Aquila is many years old (it is the original version) and the display unit is starting to wear out in the area of the rotor contacts and the display itself. I can't buy display modules from them anymore, I can buy from Ender3, but in all probability I will get TJC. Tested by experience:)

My attempt to naively change the config:

-#define DWIN_LCD_PROUI          // Pro UI by MRiscoC
+//#define DWIN_LCD_PROUI          // Pro UI by MRiscoC
 //#define DACAI_DISPLAY
-//#define TJC_DISPLAY
+#define TJC_DISPLAY

 #if ENABLED(DWIN_LCD_PROUI)

ended badly:

So I would like to have a look at the actual configuration files of the TJC variant :)

[classicrocker883]

DWIN_LCD_PROUI should be enabled for TJC display, its basically a subset of DWIN.. LCD_BACKLIGHT_TIMEOUT_MINS is only for certain displays as well, basically without DWIN_LCD_PROUI, you dont have any displays enabled.

[yrabbit]

Ah, I see now:)

[classicrocker883]

i should probably move that under #if ENABLED(DWIN_LCD_PROUI)

[elfl0rd]

It's a great idea in some form))) I really liked the firmware in general (especially after the stock one), now want more and more. :)

For example, a toolbar from EX-UI, but without advanced settings.

[classicrocker883]

firmware configurator will take a bit, I'm thinking of adding a custom box to enter your own, or perhaps a list of all available options/features. we'll see.

im not quite sure how you mean a toolbar from EX-UI without advanced settings

[elfl0rd]

im not quite sure how you mean a toolbar from EX-UI without advanced settings

At EX-UI firmware, we have additional options after standart 4 tiles on the main screen. It's pretty convenient, quick warm up, cooling, access to table alignment... But at the same time I don't need advanced options from EX-UI personally - table size adjustment for example.
Which are in the menu, not on the main screen (I may not have expressed myself correctly)

[classicrocker883]

I suppose some options can be disabled to make room for other things. however in order to keep the toolbar, the -EX must be enabled. and those others things come with it.

you can use firmware without -EX and advanced settings but the toolbar is gone. I don't think I have UBL Firmware on HC32 without it enabled. I can always make that available if that is what you want but you can disable whatever you like to compile your own firmware. I made it kind of simple using configurations/_Define_Configuration.h|_adv.h.

[elfl0rd]

Thanks! I'll definitely give it a try :)