Bondtech DDX Creality Firmware, with Touchscreen support

This branch has been developed in collaboration with Bondtech and Tiny Machines 3D. It is intended to offer preconfigured Bondtech DDX configurations for the most common Creality machines and includes support for the following machines :

• CR10S Pro
• CR10S Pro V2
• CR10 Max
• Ender 5 Plus
• CR10 V2/V3
• Ender 3 / Pro 4.2.2 and 4.2.7
• Ender 3 V2
• Ender 5 / Pro 4.2.2 and 4.2.7
• Ender 6

Screen files are archived with 7-Zip simply because it came out 1/5 the file size of a zip file. That added up fast!

There is a limitation with Windows systems and path depth so the file names need to be shorter than we would prefer. If you get an error compiling due to the path limit, move the folder to the root of your hard drive. Here is a legend to help decode the files:

• BLT = BLTouch
• EZABL = TH3D EZABL or other Normally Open 18mm Sensor
• 12mm = TH3D 12mm EZABL or other Normally Open 18mm Sensor
• Slnt = Creality Silent Board (For Ender 5 Plus assumes Dual Z)
• 422 = Creality STM32F1 based Motherboard 4.2.2
• 427 = Creality STM32F1 based Motherboard 4.2.7
• ET = E3D or Slice Engineering 300C Thermistor
• ST = Slice Engineering 450C Thermistor
• PT = Slice Engineering PT1000 Temperature Sensor
• 50W - PID settings for 50 watt Slice Engineering heater cartridge
• ZM = BLTouch connected to ZMin port instead of Probe pin 5 connector harness

Support

This firmware is provided to the public as-is with no warranty or guarantee. It's based on a large open source project and there is no entitlement to support. That said, Tiny Machines 3D customers may obtain support through their normal support queue. I will provide support to Patreons as I am able. If you require more immediate support and are not a Tiny Machines 3D customer, you may contact them at support@tinymachines3d.com about purchasing support hours. Aside from this, we are active on many Facebook groups as well as several discord channels and typically help anyone we can when we come across them.

3D Printing Discord - https://discord.gg/MZrsgVU Marlin Discord - https://discord.gg/n5NJ59y

Primary Notes for DW7.4

• Added Screen Calibration Options -- Standby Brightness -- Volume -- Both now saved in EEPROM -- Screen configuration code based loosely on the work from the CR6 community modified for this screen model -- Automatic Screen rotation for the Ender 6 (Default is upside-down)
• Manual Mesh Controls for no Probe machines -- CRX and Ender 6 with no Probe can now use all mesh controls -- All machines now use the same screen files except for Ender 3 V2 Rotary Dial machines and CR6
• Home button added to 5 point adjustment screen
• Tap mesh values to manually type in a new value - allows for manual adjustment of mesh values
• Additional functions, messaging on pause / filament runout -- No will no longer cancel print -- Depending on state, if only option is continue (eg Reheat, Load filament) Any response continues -- On final Confirm Continue, No will purge more filament and Yes will resume
• Most places temperatures are shown, can now tap them to type in a value to set the temerature
• Updated to Marlin 2.0.9 Base
• CR6 Branches merged in -- Support for this machine is primarily based on the fork by the CR6 Community

Primary notes for DW7.3

• File browser rewritten to support paging as well as subdirectories -- New file browser has a limit of a 66 character directory depth. This can be expanded at the cost of more RAM if users find this more limiting. -- Due to the above, the current recommendation is to try and limit folder depth to 3 subdirectories and keep names short if possible.
• Base bumped to Marlin Bugfix as of 20210418

The default build button is now a batch Build All! If you want to build a custom stock 2560 environment, use the env:megaatmega2560 environment. For SKR 1.3/1.4 boards use the LPC1768/9 environments as usual. For SKR Mini or Creality STM32F1 boards use the standard STM32 environments per vendor.

About Our Branches

The firmware branches maintained here are made possible by the support of Tiny Machines 3D as well as our customer base through our 3D printing Services. Maintaining and developing these branches takes a significant investment, made up of time and machines. To support continued development, please consider your next 3D Printer related purchase from Tiny Machines 3D and thank them for supporting open source development. Or, consider us for printing services outside of your machine’s capabilities. Print service requests can be sent to d.menzel@insanityautomation.com and we will respond typically within 1 working day. If you do not need anything printed or a 3D Printer but still want to contribute, you can support us through Patreon.

Setup

All configuration options intended to be adjusted by end users have been placed in the top section of Configuration.h and have been documented there. There is typically a break line to segregate the standard configuration below. Anything aside from the upper options is intended for advanced users only. Please keep in mind when flashing the Creality 32 bit boards with the binary files (.bin) that occasionally they will not accept particular filenames. This is most common with reflashing after an aborted flash. The machine stores the filename it was last flashed with, so renaming the file to something such as firmware.bin or firmware1.bin (anything different than what it is now) will typically resolve any issue with file names.

Known Issues

• While auto leveling (measuring) is in progress pressing other buttons on the screen can abort portions of the script depending where it is
• • The process includes heating the bed before probing, probing then heating the nozzle before moving to Z0.

Future Goals

For this branch, we still have some active goals open that we plan to continue working on provided there is continued interest in the project.

• Volume and leveling state EEPROM storage
• Brightness control
• Develop internal Marlin state structure for better reporting of pause / block conditions
• Add PID tune status screens as upstream blocks UI updates while processing
• CRX Non ABL Manual mesh interface to bring screens into parity with ABL versions

Creality Firmware Branches

• Most Creality machines CrealityDwin_2.0
• CR6 modified from CR-6 Community - Creality CR6

Formbot / Vivedino Firmware Branches

• Raptor 1/2 Firmware Raptor_2.0.X
• Trex 2+/3 Firmware TM_Trex2+_2.0.x

Mamorubot / HieHa Firmware Branches

• SX4/SX2 Firmware TM_SX4_2.0

Other Firmware

• Raise 3D N2+ (Dual) 2.0 Raise3D-N2+-Dual
• Evnovo Artillery Sidewinder X1 2.0 Evnovo X1
• Anet E16
• Lulzbot with Universal Tools options Lulzbot
• Funmat HT with Graphical Display Funmat HT
• Modix Big60
• Tronxy Chithu Machines Tronxy

Marlin Commit History

Marlin

This is just one of many forks of Marlin. We don't try to bury that behind fancy marketting or anything else. As you can see from the links above, most of the work done here is submitted back to the mainstream Marlin branches. The end goal of every project is to get it to the point where it is merged and maintained there. See marlin resources, including how to contribute to the Marlin Project as well, down below.

Building Marlin 2.0

To build Marlin 2.0 you'll need PlatformIO. We've posted detailed instructions on Building Marlin with PlatformIO for ReArm (which applies well to other 32-bit boards).

The current Marlin dev team consists of:

• Scott Lahteine [@thinkyhead] - USA  
• Roxanne Neufeld [@Roxy-3D] - USA
• Bob Kuhn [@Bob-the-Kuhn] - USA
• Chris Pepper [@p3p] - UK
• João Brazio [@jbrazio] - Portugal
• Erik van der Zalm [@ErikZalm] - Netherlands  

License

Marlin is published under the GPL license because we believe in open development. The GPL comes with both rights and obligations. Whether you use Marlin firmware as the driver for your open or closed-source product, you must keep Marlin open, and you must provide your compatible Marlin source code to end users upon request. The most straightforward way to comply with the Marlin license is to make a fork of Marlin on Github, perform your modifications, and direct users to your modified fork.

While we can't prevent the use of this code in products (3D printers, CNC, etc.) that are closed source or crippled by a patent, we would prefer that you choose another firmware or, better yet, make your own.