New Feature Ideas

[Thinkersbluff]

I hope to put out small incremental improvements to this UI, rather than save things up for periodic major release cycles.
Think "Agile" product development life-cycle, incremental build, incremental release.

My challenge is to learn just enough to be able to implement each feature "wisely". (i.e in a manner that is consistent with the software architecture as it is and/or as it should be, for future robustness and maintenance.)

e.g. Adding a button that just calls a gcode macro (like M112) is easy for me now. I am thinking M600 might be handy, on the Change Filament or Printing Tune menu.

To add an extruder esteps calibration function, I would require a bit of help on the python side. I would also expect to be implementing a rotational-distance calibration tool, rather than esteps. Maybe the first release would require manual editing of the printer.cfg file, while upgrades could read/write the values?

Think "Agile" product development life-cycle, incremental build, incremental release.

[henriquevianasilva]

I want to say that you are doing a great job and thanks to it we are giving our lcd a second life and improving the way we use klipper.

I have three ideas I'd like to share.

1. Turn on/off the hotend led light.

2. Keep klipper up to date, dgus version is 4/5 months old.

3. Would it be possible for you to be able to adapt the second dgus approach?

Desuuuu/klipper#74

In the next few days I will test your last version well and give you new feedback.

[henriquevianasilva]

It seems to me that the problem might just be in the initial readme file.

https://github.com/gbkwiatt/klipper/compare/dgus-reloaded...Thinkersbluff:dgus-reloaded_klipper:DGUS-ReloadedForCR6?diff=unified

[Thinkersbluff]

Fwiw, I seem to have successfully updated the modified Klipper on that test branch, in spite of GitHub. I have not yet committed the update to the default branch but kiauh will happily update your Klipper from the other branch, if you point it there. I just verified that I could use it to build Klipper.bin for STM32 boards and the UI still works correctly. Let me know if there is a specific way to verify that the Klipper is now up to date, as of yesterday.

[henriquevianasilva]

can be consulted here:

Klipper/docs/Releases.md

or you can see the modifications when comparing with original fork.

[Thinkersbluff]

Not much different in 0.11.0 that I can test.
Comparing individual files at random is not a robust check, but it does remind me that Desuuuu also marked-up some of those documents, which my update removed. 🤨

I will delete that branch, then, and try to find out how Desuuuu was doing his updates. It looks like I need to learn a bit about yaml...

[Thinkersbluff]

Now that we have posted the klipper.bin files for both the BTT board and the Creality ERA board, we might be able to copy [t5uid1] into the klippy/extras folder of any Klipper installation, to enable this UI. Not looking to leave behind the 4.5.2 board users, but I need a helper from the Community to validate and share the klipper.bin for 4.5.2 boards.

There is also something known as "wheels" that I would appreciate some help looking into, as another possible way to handle the distribution of [t5uid1].

[Thinkersbluff]

At v3.0.2, I added the Nozzle LED On/Off controls to the Miscellaneous Settings menu. (Home->Setup->Miscellaneous Settings)