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

configuration creality 3D CR-10S 500 #9386

Closed
boubouexpress opened this issue Jan 29, 2018 · 7 comments
Closed

configuration creality 3D CR-10S 500 #9386

boubouexpress opened this issue Jan 29, 2018 · 7 comments

Comments

@boubouexpress
Copy link

boubouexpress commented Jan 29, 2018

{Configuration.h}

//setting the PID//

#define PIDTEMPBED

//Creality 3D Hotend CR-10S 500
#define DEFAULT_Kp 22.04
#define DEFAULT_Ki 1.52
#define DEFAULT_Kd 79.90

//Creality 3D bed CR-10S 500
#define DEFAULT_bedKp 386.11
#define DEFAULT_bedKi 22.49
#define DEFAULT_bedKd 1657.27

//setting of the original firmware data//

#define DEFAULT_AXIS_STEPS_PER_UNIT { 80, 80, 400, 93 }

#define DEFAULT_MAX_FEEDRATE { 300, 300, 5, 25 }

#define DEFAULT_MAX_ACCELERATION { 500, 300, 100, 5000 }

#define DEFAULT_ACCELERATION 500
#define DEFAULT_RETRACT_ACCELERATION 500
#define DEFAULT_TRAVEL_ACCELERATION 1000

#define DEFAULT_XJERK 5.0
#define DEFAULT_YJERK 5.0
#define DEFAULT_ZJERK 0.4
#define DEFAULT_EJERK 5.0

// The size of the print bed
#define X_BED_SIZE 500
#define Y_BED_SIZE 490

// Travel limits (mm) after homing, corresponding to endstop positions.
#define X_MIN_POS 0
#define Y_MIN_POS 0
#define Z_MIN_POS 0
#define X_MAX_POS 510
#define Y_MAX_POS 490 // (to avoid that the bed taps on the support gear of the axis Y)
#define Z_MAX_POS 510

#define Z_MAX_POS 500

#define Z_SAFE_HOMING_X_POINT (510 / 2) #define Z_SAFE_HOMING_Y_POINT (510 / 2)

//solve the heating problem//

{Configuration_adv.h}

#define WATCH_BED_TEMP_PERIOD 240

//solves the SD drive detection problem//

{pins_RAMPS.h}

#define SD_DETECT_PIN -1

option BLtouch

#define BLTOUCH
#define X_PROBE_OFFSET_FROM_EXTRUDER -41
#define Y_PROBE_OFFSET_FROM_EXTRUDER -11
#define Z_PROBE_OFFSET_FROM_EXTRUDER -1.0

#define MULTIPLE_PROBING 2

#define GRID_MAX_POINTS_X 7

#define LEFT_PROBE_BED_POSITION 40
#define RIGHT_PROBE_BED_POSITION 460
#define FRONT_PROBE_BED_POSITION 40
#define BACK_PROBE_BED_POSITION 460

#define AUTO_BED_LEVELING_BILINEAR

//#define LCD_BED_LEVELING

#define LEVEL_BED_CORNERS

#define Z_SAFE_HOMING

//change position of the park//

#define NOZZLE_PARK_POINT { (X_MIN_POS + 20), (Y_MIN_POS + 20), 20 }

@thinkyhead
Copy link
Member

thinkyhead commented Feb 14, 2018

My hands are in too much pain to convert this information into Configuration files. Would you mind doing it for me? You can start with these:

https://github.com/MarlinFirmware/Marlin/tree/bugfix-1.1.x/Marlin/example_configurations/Creality/CR-10S

@Evgeny-SPB
Copy link
Contributor

Hello!

I've spend a few hours looking at example configuration of Creality CR-10S and source code, that is available online at Creality web site.

CR-10S and CR-10 5S, are two different printers and there should be two example configurations for them.

But Marlin version 1.1.x is closed for development. Should I create configuration file for Marlin 2.x or 1.1.x ?

@thinkyhead
Copy link
Member

Yes, they should be made for bugfix-2.0.x, using the current example configurations as the starting-point, and submitted as a PR to that branch.

@boelle
Copy link
Contributor

boelle commented Feb 20, 2019

@boubouexpress @Evgeny-SPB as thinky said make a PR

and i think we can close this one

@Evgeny-SPB
Copy link
Contributor

@boelle you are correct. Pull request is already merged in bugfix -2.0.x

I also think we can close this issue

@boelle
Copy link
Contributor

boelle commented Feb 27, 2019

only @boubouexpress and @thinkyhead can close

but i think @boubouexpress just created the issue and then left :-(

@thinkyhead will you swing the axe over this one?

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants