Howdy All,

I know a lot of you will say that I should just upgrade my mainboard (and I am thinking of doing that when I am a little further along in the hobby) but for the moment I am happy with the 8-bit stock Creality 3d v1.1.4 mainboard that came with the CR-10 Mini I have.

So onto the reason for my post...I just purchased a Creality genuine CR-Touch and I am working on setting it up. After a bit of blood, sweat and tears, I got the CR-Touch wired into the mainboard (by connecting the Servo pins to the Pin 27 breakout board and the probe endstop connected to the Z-Endstop connector on the mainboard) and now I am starting to run some tests to at least confirm the wiring is okay. Just to mention at this point that the stock Z-endstop has been completely removed so only the CR-Touch is connected to the Z-endstop connector on the mainboard.

After compiling/flashing a custom version of Marlin 2.1.2.1, I am now trying to test the CR-Touch probe. When I turn on the printer, I can see the CR-Touch initialize and go to Ready state (I believe). If I go into the Motion menu and select 'Deploy Probe' the probe does indeed deploy. If I then select 'Stow Probe', the probe does indeed stow so that all seems good to me. If I then select 'Auto Home', I believe the correct things do happen namely:

• 1) The Y axis homes.
• 2) The Z axis goes up to a predetermined height (presumably set somewhere in the firmware configuration).
• 3) The CR-Touch deploys it's probe and then the Z axis starts to descend towards the bed. If I touch the probe, the Z axis stops and repeats the prior step and this step again and then stops.

Here is a video of this in action:

https://photos.app.goo.gl/pBVFNivh1e77tazF7

Now onto where I *think* there might be an issue with my setup. After some extensive research online, I found a post on a forum that suggested I follow the below steps to ensure that the probe is functioning correctly. The steps were written for the BL-Touch but it is my understanding that the CR-Touch and BL-Touch should be considered identical:

Connect BLTouch, power up controller and upload the firmware

Blue LED will be ON if a servo signal is present. Blue LED is faint.

M119 ; should return OPEN. If not check that the BLTouch is enabled in the configuration. If enabled then check wiring and check that the correct pin is being used. Also check that Z_MIN_ENDSTOP_INVERTING and Z_MIN_PROBE_ENDSTOP_INVERTING are both set to "false".

M280 P0 S10 ; should deploy the probe and the orange LED will be OFF.

M119 ; should return OPEN

M280 P0 S90 ; should stow the probe and the orange LED will be ON

M280 P0 S60 ; puts it into the M119 test mode.

The probe should remain stowed and the blue LED should be OFF. If it's ON then the unit needs to be adjusted.

M119 ; should return TRIGGERED

M280 P0 S160 ; returns it to normal operation

M119 ; should return OPEN.

So I went ahead and followed the above sequence of steps and what I found was that M119 reported that z_min is in 'OPEN' state when the probe is deployed (using command 'M280 P0 S10') and 'TRIGGERED' when the probe is stowed (using command 'M280 P0 S90') so now I am trying to figure out if that is correct or if there is something setup incorrectly either in the way I have wired the probe, or the way the factory wired the probe or whether I made a mistake configuring the Marlin v2.1.2.1 firmware prior to compiling?

Here are the pertinent changes which I made in the Marlin v2.1.2.1 source after downloading the release version from GitHub to compile a DEBUG version of the firmware:

1. Took the Marlin v2.1.2.1 release configuration and applied the example CR-10 Mini configuration .h files from this folder -> Configurations-2.1.2.1\config\examples\Creality\CR-10 Mini\CrealityV1

In Configuration.h:

1. Uncommented '#define ENDSTOPPULLUP_ZMIN'
2. Confirmed that both '#define Z_MIN_ENDSTOP_INVERTING' and '#define Z_MIN_PROBE_ENDSTOP_INVERTING' are set to 'false'
3. Uncommented '#define USE_PROBE_FOR_Z_HOMING'
4. Made sure that '#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN' is enabled.
5. Uncommented '#define BLTOUCH'
6. Uncommented '#define AUTO_BED_LEVELING_BILINEAR' and checked to make sure that this was the only Bed Leveling methodology option was enabled.
7. Uncommented '#define Z_SAFE_HOMING'.
8. Uncommented '#define DISABLE_M503' to save PROGMEM space as the 8-bit board is limited.
9. Commented out '#define SDSUPPORT' to save PROGMEM space. SDSUPPORT is not needed in this DEBUG build.
10. Enabled '#define SLIM_LCD_MENUS' to save PROGMEM space.
11. Commented out '#define SPEAKER' as SPEAKER support is no longer needed as Pin 27 has been repurposed for the CR-Touch.

In Configuration_adv.h:

1. Commented out '#define BLTOUCH_SET_5V_MODE' as I believe this is only needed when using a 32-bit mainboard.
2. Uncommented '#define PROBE_OFFSET_WIZARD' to use to confirm correct operation of the CR-Touch with this DEBUG build.
3. Uncommented '#define SDCARD_READONLY' to save PROGMEM space.
4. Commented out '#define ARC_SUPPORT' to disable ARC Support to save PROGMEM space.

I think that covers everything, I would really appreciate anyone's thoughts on how I have approached this and whether I am on the right track (or not). The more I think about it the more I think the probe is working fine as it is deploying and stowing correctly and correctly responding to input when touched during the Auto Home process but would still love confirmation that it is working correctly from those who have more experience than I do with the CR-Touch/BL-Touch when used with an 8-bit board with a Pin 27 adapter board.

Thanks in advance!!!