Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PR] Creality Ender 3v2 Extensible_UI support #21328

Closed

Conversation

mriscoc
Copy link
Contributor

@mriscoc mriscoc commented Mar 12, 2021

Description

This Pull request add Creality Ender 3v2 Extensible_UI support to the bugfix-2.0.x branch.

I use dgus, the example file as first templates. This is a preliminary support and rewrite it for have all the defaults menu and items.

Requirements

Requires enable the Extensible UI support in config files, sample configuration files are attached.

Benefits

Enable the use of Extensible UI on the DWIN display of the Creality Ender 3v2. Only single language support is enabled in this release but it uses the language constants of language_en.h file for now.

Configurations

Configuration.zip

@mriscoc mriscoc changed the title Bugfix 2.0.x extensible UI [PR] Creality Ender 3v2 Extensible_UI support Mar 12, 2021
@otioss
Copy link

otioss commented Mar 12, 2021

I've heard ExtUI is not suitable for Ender 3 V2's DWIN display. I think it is preferred to use MarlinUI for this printer.

@thinkyhead
Copy link
Member

Indeed, the ExtUI API is intended as a wrapper for displays that Marlin can't directly control, and which use a light protocol to send values to and from the controller. The Ender 3 V2 display is not suited to an ExtUI wrapper because it is entirely controlled by Marlin through custom code originally provided by Creality3D.

The interface provided by Creality is fine, but very minimal. In order for this display to work fully with Marlin, we need to finish the MarlinUI implementation started at #19371. That project needs help to get screen updates working properly. It would be good to get that completed first.

There is also an alternative UI being created, linked from that PR. There's no reason for them to move over to an ExtUI wrapper either. It is simply not appropriate to the display.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants