Welcome to Discussions of DGUS-reloaded(ForKlipper)_CR6Community Edition #3
Thinkersbluff
announced in
Announcements
Replies: 2 comments 21 replies
-
oh wow can i have a few questions. since this repo is another repo from dgus. Is it up to date with the klipper firmware? |
Beta Was this translation helpful? Give feedback.
0 replies
-
The DWIN component and Klipper component each reside in their own repo, for now. Your question is answered in the Klipper repo Readme. Now that we have uploaded the precompiled Klipper.bin files, there is no need to keep updating the modified Klipper. It is best to let Moonraker keep Klipper up to date, and just copy t5uid1 into klippy/extras. |
Beta Was this translation helpful? Give feedback.
21 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Welcome!
This repo is one of two, at the moment, which jointly host the two parts of the CR6Community Edition of DGUS-Reloaded.
The goal of this project is to restore some functionality to the stock DWIN screen, after converting your CR6-series 3D printer to run on Klipper.
The first versions of this DWIN_SET UI were achieved by refactoring the landscape mode T5UID1 DGUS-Reloaded DWIN App by Desuuuu. This allowed me to learn the architecture of the two parts and confirm that I would be able to generate a CR6-compatible version with a reasonable amount of functionality.
At version 0.3 and subs, the look and feel of this UI is inspired by the Marlin-based CR6 Community Firmware [UI]. Some Klipper functionality is different from Marlin, so the UI will not be 100% identical, but ;the workflow and user-experience concepts baked into the CF6.1 UI are very evident in this UI, as of v0.3.
The deliberate alignment/overlap between the two UI projects is intended to keep the learning curve shallow for CR6 Community members who decide to switch from CF6.1 to Klipper on their CR6 printer(s).
The Klipper portion of this solution is a fork of a fork of the Klipper3D master.
Hopefully, the long-term version of the CR6 Community Edition will NOT always depend upon maintaining a unique fork of Klipper.
At this time, however, I do not know of any viable alternative approach. Perhaps you, dear Community Member, have some specialized knowledge/experience which enables you to be of some assistance, in that regard? If so, PLEASE start a Discussion on that topic & let's get ourselves back onto the mainstream Klipper repo.
-->
Beta Was this translation helpful? Give feedback.
All reactions