Crazy3DPrinter CZ-300

[DragonSlayerSE]

Motherboard is named "3FD1X ENTINE T1 2018/10/22"

[JamesH1978]

Thankyou for submitting a PR, couple of points before i review, please be aware you need to sign off your PR for the certificate of origin as per point 3 in https://github.com/Klipper3d/klipper/blob/master/docs/CONTRIBUTING.md#what-to-expect-in-a-review and all new config example added need to also pass regression tests as per point 4 in https://github.com/Klipper3d/klipper/blob/master/docs/Example_Configs.md#guidelines

Thanks James

[DragonSlayerSE]

Commit message:

This is a config file for the Crazy3DPrint CZ-300 printer. Sold as a 300x300x400 printer, but with the right glass clamps you can use all the 310x330. Since Klipper3D does not support multi microstepping modes, the A5984 stepper is forced to 32 microsteps via [static_digital_output] There are several unpopulated pinheaders (jst 2.0) on the motherboard, Like (burning, debug, calibrate, e-sensor, led, fan2) English is not my native language, there could be som spelling problems.

Signed-off-by: Kire Dyfvelsten [email protected]

[github-actions[bot]]

Thank you for your contribution to Klipper. Unfortunately, a reviewer has not assigned themselves to this GitHub Pull Request. All Pull Requests are reviewed before merging, and a reviewer will need to volunteer. Further information is available at: https://www.klipper3d.org/CONTRIBUTING.html

There are some steps that you can take now:

1. Perform a self-review of your Pull Request by following the steps at: https://www.klipper3d.org/CONTRIBUTING.html#what-to-expect-in-a-review If you have completed a self-review, be sure to state the results of that self-review explicitly in the Pull Request comments. A reviewer is more likely to participate if the bulk of a review has already been completed.
2. Consider opening a topic on the Klipper Discourse server to discuss this work. The Discourse server is a good place to discuss development ideas and to engage users interested in testing. Reviewers are more likely to prioritize Pull Requests with an active community of users.
3. Consider helping out reviewers by reviewing other Klipper Pull Requests. Taking the time to perform a careful and detailed review of others work is appreciated. Regular contributors are more likely to prioritize the contributions of other regular contributors.

Unfortunately, if a reviewer does not assign themselves to this GitHub Pull Request then it will be automatically closed. If this happens, then it is a good idea to move further discussion to the Klipper Discourse server. Reviewers can reach out on that forum to let you know if they are interested and when they are available.

Best regards, ~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.