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

[FR] Creality Ender 7 #602

Closed
mattrayner opened this issue Oct 29, 2021 · 15 comments
Closed

[FR] Creality Ender 7 #602

mattrayner opened this issue Oct 29, 2021 · 15 comments

Comments

@mattrayner
Copy link

Description

I have an Ender 7 running the Creality 4.2.7 motherboard, it is missing some basic features, along with some very strange defaults for things like ABL. I would love to be able to compile my own firmware for it as I do with my Ender 3.

I have reached out to Creality via the [email protected] email address (is there a better way?) to request the files, but wasn't sure if there is an alternative way to set this up?

Configuration Details

  • Manufacturer: Creality
  • Model: Ender 7
  • Motherboard: Creality 4.2.7

Additional Information

https://www.creality.com/goods-detail/creality-ender-7-3d-printer

@ellensp
Copy link
Contributor

ellensp commented Oct 29, 2021

It has the same touch screen as the cr-6 se which is not yet supported in standard Marlin.

@ellensp
Copy link
Contributor

ellensp commented Oct 29, 2021

you should do a M503 to dump basic settings

@InsanityAutomation
Copy link
Contributor

I've got one here and its mostly working, a few more oddities with the touchscreen to sort out. The mainboard for it is a unique board though, not a 4.2.7. I submitted the board already though.

@mattrayner
Copy link
Author

@InsanityAutomation Amazing, do you need any help at all? I'm happy to provide assistance :)

@ellensp
Copy link
Contributor

ellensp commented Oct 31, 2021

@InsanityAutomation I wish you would add it to real Marlin, not your fork...

@InsanityAutomation
Copy link
Contributor

@ellensp maybe eventually, but that discussion is better had on discord etc not here. It is however a pure ExtUI module. Drop its folder in, enable ExtUI and you're done. Its built to utilize absolutely nothing outside the API following the original intent of the system.

There is an issue with the dgus software, every time i build the displays, at least a couple screens have been getting messed up, and idk why yet... Random and different screens every time i make a change, not even consistent. Once I figure that out we should be in good shape, Everything else is working on both the Sermoon D1 and Ender 7 that use this display.

@mattrayner
Copy link
Author

@InsanityAutomation do you have a guide to get this setup with your forks?

@InsanityAutomation
Copy link
Contributor

Missed the last comment here @mattrayner however the flashing process is the same as any other DGUS display, and mainboard is just drop the bin file on an sd card and power on. - https://www.youtube.com/watch?v=SBX30GmM3Qo for flashing the LCD - https://github.com/InsanityAutomation/Marlin/tree/CrealityDwin_2.0 for the working code

@umsmin
Copy link

umsmin commented Dec 29, 2021

@InsanityAutomation you make a great work! Thank you for that. on which point are we for the Configuration.h Configuration_adv.h? Maybe similar to the Ender 6?

@InsanityAutomation
Copy link
Contributor

@umsmin Theyre blended together, if you search the MachineEnder7 tag in the configuration.h file youll see all the options that are set specifically for it.

@umsmin
Copy link

umsmin commented Dec 30, 2021

@InsanityAutomation Ah, now I get it. It works for the first test. Only the Infoscreen is shown directly over the buttons from config screen. not in a separately screen. Thanks for all

@slashnot
Copy link

slashnot commented Jan 16, 2022

@InsanityAutomation Thanks for your work. Your configuration is working good. I just selected Ender 7 BLT zm in platform.io and I got a working firmware. I also played a bit with the display firmware and I get some parts to work properly.

@thinkyhead
Copy link
Member

Duplicate of #649

@thinkyhead thinkyhead marked this as a duplicate of #649 Jan 26, 2022
@fellnerse
Copy link

@InsanityAutomation did you have any time/luck investigating the issue and merging this back?

@InsanityAutomation
Copy link
Contributor

@InsanityAutomation did you have any time/luck investigating the issue and merging this back?

The touchscreen code is maintained in a separate repo as its still actively evolving. You can simply drop the folder into the current bugfix, and enable extensible_ui if youd like, though my code base doesnt often diverge far from bugfix.

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

No branches or pull requests

7 participants