CR10 V2 Configuration

[marlinfirmware]

CR10 V2 Configuration

[thinkyhead]

If you find one out there in your searches, please let us know. We don't yet have this on the radar. Maybe ask TinyMachines3D about it.

[NathanCrainJr]

I have done some digging around and found these files in Creality's dropbox linked here https://www.dropbox.com/sh/dt38tetxsxowg7b/AAD_kCsmkdlgafImo9e_gKKia?dl=0
It is clearly an old version of Marlin with the CR-10 V2 applicable settings. Would this help anyone who could update the configuration.h and configuration_adv.h to the current Marlin version?

[NathanCrainJr]

Update: I have recently found this Cheetah 5.0 firmware that have specific settings for CR-10 V2. I am going to see which parameters they have used for the machine and try to use those in vanilla Marlin.
https://kay3d.com/pages/kay3d-cheetah-5-firmware
There is a facebook group specifically for the CR-10 V2, but they only share a .Hex file. I do not know how to reverse engineer this file to extract settings. It runs perfectly on my machine though.

[thinkyhead]

I also have the Creality3D source in hand, partially ported to the latest code. I'll take a look at the french guy version.

[kiss81]

@fran6p
@thinkyhead

I finalized a version that works on the CR-10 v2 stock setup:
https://github.com/kiss81/cr10v2
in the "marlin" folder.

The main issue I struggled with where some RAM issues and inverted END stops in the Z direction... That caused several issues of course 🙂
I am trying to do some prints now to see how it goes.

[APajonk]

I´m also currently searching for a way to update my new CR-10 v2 to current Marlin firmware. Did not found any existing HowTo or any description about this. TH3D is the only one I found which has specifically CR-10 V2 configuration parameters. Unfortunately, there are also hints the comments that features like Linear Advance will not work with this model :(

[WartyTowel]

I have a similar problem with the CR-10 Pro V2. I think that the config should be very close. So I would be very interested in progress here. ;)

[zigomatichub]

I guy on a forum which have a CR10V2 gave me his Configuration.h , Configuration_adv.h, _Bootscreen.h and _Statusscreen.h. All modifications done for Marlin V2 and CR10V2.
I don't have look yet but his build is working fine on his printer (with BL Touch). I don't know how I can share those files here. If I found some time next week... I will look on it

the basis is https://github.com/InsanityAutomation/Marlin/tree/CrealityDwin_2.0
with config start from CR10SV2

Cheetah is also a good starting point.

[NathanCrainJr]

You linked the tinymachines3d firmware. It works pretty darn good. Unfortunately, the config and config_adv files are special tailored to the way they modified the marlin firmware.

[swilkens]

This website:
https://www.creality3dofficial.com/pages/firmware-download

Has CR-10 V2 Firmware + BL Touch - that link also includes an archive with the sources, including the configuration files.

[thinkyhead]

Has CR-10 V2 Firmware + BL Touch

I will have to compare it to the sources provided to me. I am in the process of bringing it up to date with bugfix-2.0.x so that all the kinks are worked out. The starting date of their sources is from a very brief period where the platformio.ini file was using inheritance to be hierarchical.

[mdmartini]

I also just purchased a CR10 V2, and would like to update to the lastest version of vanilla Marlin to get the new features (mostly the thermal runaway), but I seem to be having issues with errors, and I think it is because I have to either select 'CR10S' or CR10. I have gotten a CR10S config to upload once, however it now shows 'CR10S' on the info screen, and i am not completely sure it is the correct set up. Is it possible that a new version of Marlin will have a config specifically for the CR10 V2?

[zigomatichub]

There is a french guy that he did a marlin for cr10 V2 based on 2.0.5.3 Marlin.
Here the reference with all details to redo the same.

https://www.lesimprimantes3d.fr/forum/topic/29980-cr10-v2-carte-originelle-252-marlin-2053/?tab=comments#comment-348341

[kiss81]

Any update on this? It would be nice to have this work on a CR-10 v2.
edit: translating the French website helped a bit. Would be nice if his configuration files could be added to the example configurations directory. I will give it a run to see if it compiles.

[thinkyhead]

Just added this… 9209d64

[kiss81]

Just added this… 9209d64

I checked the source and compared it to the French guy version. The changes you made make sense, so I used your version.

for the latest stable build you will still need to define these in the Configuration_adv.h:
#define X_HOME_BUMP_MM 5
#define Y_HOME_BUMP_MM 5
#define Z_HOME_BUMP_MM 2

If someone is interested this is the configuration if you don't have a bltouch installed.
https://github.com/kiss81/cr10v2/tree/master/marlin

My machine is still busy with a print, but will give an update here when I installed the new firmware and if things went well (or not). :)

[kiss81]

Update: the build succeeded, but after uploading I only see the blue LCD lights turning on and nothing seems to be running unfortunately. The bootloader was still ok, so I could upload the stock firmware and everything was fine. Anyone got a clue?
I tried the hex file from fran6p (the French guy) but still a blank LCD.
Do I need to update the bootloader maybe?

[thinkyhead]

You wouldn't be able to flash any firmware if the board didn't have a bootloader.

This configuration is indeed untested, and has simply been ported over from fran6p. I suggest you ask him to try the latest Marlin firmware with these configs, and he'll probably figure out what is missing or incorrect pretty quickly, at least to the point of starting up.

I only converted the configuration files. I didn't see any other firmware changes described in his postings.

[kiss81]

I compared the new configuration with the original stock version, but couldn't find anything that should block it from booting. I tested some changes without luck. I will contact fran6p

[thinkyhead]

I'll download yours and compare with https://www.lesimprimantes3d.fr/forum/messenger/8107/?tab=comments#comment-67039 and merge the final result soon.

[kiss81]

I'll download yours and compare with https://www.lesimprimantes3d.fr/forum/messenger/8107/?tab=comments#comment-67039 and merge the final result soon.

The latest version I just uploaded is working well now. There are some changes which are personal preference, but the z clearances as they are now are at least really safe to work with.

[thinkyhead]

Some minor differences between the two versions…
May I assume the newer one is correct in all cases?

For example, the newer one has all Z endstop inverting set to true and the older one has them set to false. The newer one has E steps-per-mm set to 93 and the old one has 97 (more slippage).

[fran6p]

Hi Scott, Without ABL (Bltouch), the logic is «false» for : Z_MIN_ENDSTOP_INVERTING Z_MIN_PROBE_ENDSTOP_INVERTING With ABL the two are «true» :-) Le dim. 21 juin 2020 à 02:28, Scott Lahteine <[email protected]> a écrit :

…

Some minor differences between the two versions… May I assume the newer one is correct in all cases? (For example, the newer one has all Z endstop inverting set to false and the older one has them set to true.) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH3BQOVIWDDV7XMY7X6KH33RXVH2DANCNFSM4KLLTDBA> .

[kiss81]

Exactly. Make sure not to use interrupts for the end stops as that will not always work...

[thinkyhead]

Please review the currently published version for any needed corrections.

[kiss81]

I don't have bltouch, so can't test it, but the changes seems legit for a working version. The default extruder steps are wrong though. They are wrong in every firmware I've seen so far. It should be ~97. (after calibration my unit is even at 98.8, but it depends a bit per unit)

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

[fran6p]

I have reviewed the files. All seems Ok for me BUT my configuration is for a CR10-V2 with BLTouch (and not the standard extruder). I have tested it and it works for me and some other french users of this forum (lesimprimantes3d.fr). @kiss81 you're right with the steps for the extruder, it should be 95 and the user should do a calibration to find the steps for his own printer. On my CR10-V2, before I added BLTouch and change my extruder with the same one found on CR10S Pro (a pseudo BMG without reduction whose steps are near 140) after calibration my extruder's steps where between 94-95 (I don't remember exactly… Maybe I'm becoming too old ;-) . @scott I have to thank you for all the work you (and others) do for the Marlin software. :-) Le lun. 22 juin 2020 à 00:28, Scott Lahteine <[email protected]> a écrit :

…

Please review the currently published version for any needed corrections. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH3BQORS6AMVREQARV2ICMDRX2CPNANCNFSM4KLLTDBA> .

[DavBfr]

@fran6p Is it possible to add some conditions to set the right settings depending on the presence of the BLTOUCH?
like:

#if ENABLED(BLTOUCH)
  #define Z_MIN_ENDSTOP_INVERTING true
  #define Z_MAX_ENDSTOP_INVERTING true
  #define Z_MIN_PROBE_ENDSTOP_INVERTING true
#else
  #define Z_MIN_ENDSTOP_INVERTING false
  #define Z_MAX_ENDSTOP_INVERTING false
  #define Z_MIN_PROBE_ENDSTOP_INVERTING false
#endif

This way it's easier to build the correct version.

[kiss81]

@fran6p Is it possible to add some conditions to set the right settings depending on the presence of the BLTOUCH?
like:

#if ENABLED(BLTOUCH)
  #define Z_MIN_ENDSTOP_INVERTING true
  #define Z_MAX_ENDSTOP_INVERTING true
  #define Z_MIN_PROBE_ENDSTOP_INVERTING true
#else
  #define Z_MIN_ENDSTOP_INVERTING false
  #define Z_MAX_ENDSTOP_INVERTING false
  #define Z_MIN_PROBE_ENDSTOP_INVERTING false
#endif

This way it's easier to build the correct version.

I agree, such improvements makes things so much easier. If needed I can make a commit on this that you can compare.

[fran6p]

Hi, Good suggestion @david PHAM-VAN I have tested it with :

// Mechanical endstop with COM to ground and NC to Signal uses "false" here (most common setup). #define X_MIN_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop. #define Y_MIN_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop. //#define Z_MIN_ENDSTOP_INVERTING true // Set to true to invert the logic of the endstop. //Test #define X_MAX_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop. #define Y_MAX_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop. //#define Z_MAX_ENDSTOP_INVERTING true // Set to true to invert the logic of the endstop. //Test //#define Z_MIN_PROBE_ENDSTOP_INVERTING true // Set to true to invert the logic of the probe. //Test // Test suggestion David PHAM-VAN #if ENABLED(BLTOUCH) #define Z_MIN_ENDSTOP_INVERTING true #define Z_MAX_ENDSTOP_INVERTING true #define Z_MIN_PROBE_ENDSTOP_INVERTING true #else #define Z_MIN_ENDSTOP_INVERTING false #define Z_MAX_ENDSTOP_INVERTING false #define Z_MIN_PROBE_ENDSTOP_INVERTING false #endif

The compilation with VSC is OK even though these lines (near lines 654) are before the #define BLTOUCH (line 987 on my configuration.h), I'm not a coding professional ;-) So if you want @kiss81 you can make a commit as I don't know how to do it and have no time now to learn as I just began to use Github (now on my CR10-V2 I test / use Klipper but I'm on Marlin with my CR10 (old one)). Cordially Francis Poulizac Le dim. 28 juin 2020 à 21:35, kiss81 <[email protected]> a écrit :

…

@fran6p <https://github.com/fran6p> Is it possible to add some conditions to set the right settings depending on the presence of the BLTOUCH? like: #if ENABLED(BLTOUCH) #define Z_MIN_ENDSTOP_INVERTING true #define Z_MAX_ENDSTOP_INVERTING true #define Z_MIN_PROBE_ENDSTOP_INVERTING true #else #define Z_MIN_ENDSTOP_INVERTING false #define Z_MAX_ENDSTOP_INVERTING false #define Z_MIN_PROBE_ENDSTOP_INVERTING false #endif This way it's easier to build the correct version. I agree, such improvements makes things so much easier. If needed I can make a commit on this that you can compare. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH3BQOWKRQPX2BB7KVQ2CUDRY6LRHANCNFSM4KLLTDBA> .

[alittlec]

Hi,
This doesn't build with the latest 2.0.7.2 release:

buildroot/share/PlatformIO/scripts/../../../../Marlin/src/inc/../../Configuration_adv.h:1054:19: error: #if with no expression

[wirecuttr]

Hi there, Looking at the latest Configuration.h in the bugfix branch. I'm seeing:
#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN

Did you guys bypass the z-endstop switch and wire the BLTOUCH to the Z_MIN?

** Nevermind. installed the FW. It's using the BLTOUCh probe for Z home and bypassin the Z limit switch. No rewiring needed.**