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

Ender 5 Pro now shipping with v4.2.2 mainboard #355

Closed
dougbalish1 opened this issue Sep 10, 2020 · 14 comments
Closed

Ender 5 Pro now shipping with v4.2.2 mainboard #355

dougbalish1 opened this issue Sep 10, 2020 · 14 comments

Comments

@dougbalish1
Copy link

Dont believe this has been addressed, if it has, please link me to where:

The default ender 5 pro config now no longer completely works for (what i assume to be) most ender 5's shipping. I, and a few people ive been in contact with, have received ender 5's with creality v4.2.2 mainboards, and while creality has a .bin that works with both the stock version and bltouch (i have a bltouch) version on their site, they refuse to share the (marlin v2 based) source.

I would think at least a warning in the config for ender 5 pros is in order to prevent wasted time, as well as possibly an ender 5 pro v1.5 type addition to the configs.

I would love to help contribute, but i am new to github and open source (competent enough c programmer/debugger though) so if anyone wants to point me in the right direction to help, i would be glad.

Some additional info in case it helps anyone: I have tried building the ender 5 pro config but using the STM32F103RET6//Creality board V4 settings transplanted into the ender 5 pro config, and i can get this to work with some tweaks, but not the bltouch. This indicates (to me at least) that the pinout is different. If anyone would like me to help debug also, i have access to a cheap oscope and multimeter, fpga, logic analyzer, etc.

@SlackHacky
Copy link

SlackHacky commented Sep 10, 2020

because there are to date 3 ways to connect a BLTouch on to a v4.2.2 (or v4.2.7) board

  1. All five pins into the Bltouch port

  2. 3 pins in BlTouch port and 2 in Z stop port

  3. Creality's err way (to use up old v1/v2 SKU kits) is 2 pins into z stop port and connect a adaptor board into the screen display port...

so its all about which port you pick and how you define the configuration.h file

@dougbalish1
Copy link
Author

because there are to date 3 ways to connect a BLTouch on to a v4.2.2 (or v4.2.7) board

  1. All five pins into the Bltouch port
  2. 3 pins in BlTouch port and 2 in Z stop port
  3. Creality's err way (to use up old v1/v2 SKU kits) is 2 pins into z stop port and connect a adaptor board into the screen display port...

so its all about which port you pick and how you define the configuration.h file

Thanks for the reply, i was wondering what the Bl_T header on the mainboard was for since they shipped me the adapter board, makes sense now though.

To clarify: What you are saying is that marlin currently defines the bltouch to be connected through option 1 or 2 (but option 1 is the default that would not require any pin redef?) for 4.2.2 mainboards, but since i currently have option 3, which is not the officially supported way, my best bet is to rewire it to the bltouch port/zstop, because otherwise i would have to trace the pin for signal and the z endstop and redefine bltouch_probe as signal pin, and bltouch_in/out as the endstop pins (either in pins.h or override it in the config)?

@SlackHacky
Copy link

I use option 1 when I self compile, this is not a BUG as such, more no clear documentation for a User that did not know these configurations.

@sjasonsmith
Copy link
Contributor

@thisiskeithb what do you think about this one? Has this been addressed? Do we need to tweak examples to help with this?

@sjasonsmith sjasonsmith transferred this issue from MarlinFirmware/Marlin Dec 2, 2020
@ellensp
Copy link
Contributor

ellensp commented Dec 2, 2020

Anyone know the pinout with option 3, never seen it. Otherwise is fairly easy to setup 3 options and force the user to choose one of them when bltouch is enabled

@thisiskeithb
Copy link
Member

Anyone know the pinout with option 3, never seen it. Otherwise is fairly easy to setup 3 options and force the user to choose one of them when bltouch is enabled

I think they are referring to a "Pin 27 board" that was used on the 1.x boards to break out PIN 27 for the BLTouch or filament runout sensor (depending on config): https://www.amazon.com/Creality-BLTouch-Filament-Print3d-LLC/dp/B07L2Q2SSD

@sjasonsmith
Copy link
Contributor

It makes me sad that Creality put any customer in the position where optiobn #1 is not the correct answer.
It is clearly the "correct" way to do it for these boards. I wonder how many people it impacts if we just left that as the one and only example.

@ellensp
Copy link
Contributor

ellensp commented Dec 2, 2020

how about this in Configuration.h

#ifdef BLTOUCH
  //#define BLTOUCH_FULLY_ON_PROBE_PLUG 
  //#define BLTOUCH_ON_Z_ENDSTOP_PLUG
  //#define BLTOUCH_ON_PIN_27_BOARD
  #if NONE(BLTOUCH_FULLY_ON_PROBE_PLUG, BLTOUCH_ON_Z_ENDSTOP_PLUG, BLTOUCH_ON_PIN_27_BOARD)
    #error "You must select how your BLTOUCH is connected to the controller. Choices are BLTOUCH_FULLY_ON_PROBE_PLUG, BLTOUCH_ON_Z_ENDSTOP_PLUG or BLTOUCH_ON_PIN_27_BOARD."
  #endif
#endif

With appropriate changes elsewhere so it functions as expected.

@mgrrx
Copy link

mgrrx commented Dec 4, 2020

I'm about to mount a BLTouch on my new Ender 5 Pro v 4.2.2 Mainboard. @SlackHacky you mentioned that you chose option 1 and self compiled the firmware, right? Which config did you use?

@Skiddz
Copy link
Contributor

Skiddz commented Jan 28, 2021

I use option 1 when I self compile, this is not a BUG as such, more no clear documentation for a User that did not know these configurations.

I just got my SKR E3 Mini V2 working in my CR-10 Mini, but had to use the Z-stop port for my BL Touch 3.1. I think I know what I need to change in configuration.h to be able to use all 5 wires in the probe port, but can I get a sanity check before I compile and pull it all apart again? This is my 1st foray into Marlin so I'm still learning.

Comment out #define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
Uncomment //#define USE_PROBE_FOR_Z_HOMING
Uncomment //#define Z_MIN_PROBE_PIN 32 (I assume Pin 32 is the Zmin pin in the probe header?)

@zaped212
Copy link

zaped212 commented Aug 4, 2021

For reference I just received a new ender5 pro yesterday with the upgraded 4.2.2 motherboard
I was able to use the configuration files found here:
https://github.com/MarlinFirmware/Configurations/tree/bugfix-2.0.x/config/examples/Creality/Ender-5%20Pro/CrealityV422

but I did need to modify:
#define Z_MIN_PROBE_PIN PB1
to use the 5 pin connector for my BLTOUCH. Finding the correct port was the longest part of building the firmware myself.

It would be nice if we had that as a default in the code atleast with a comment block explaining when to turn it on.

@ellensp
Copy link
Contributor

ellensp commented Aug 4, 2021

default is to use zmin pin ie in the Configuration.h is #define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN.

If you want to use the probe port you disable #define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
and enable #define USE_PROBE_FOR_Z_HOMING

and it use the probe port automatically.
from file Marlin/src/pins/stm32f1/pins_CREALITY_V4.h

#ifndef Z_MIN_PROBE_PIN
  #define Z_MIN_PROBE_PIN                   PB1   // BLTouch IN
#endif

@ellensp
Copy link
Contributor

ellensp commented Aug 4, 2021

Also if you have the pin 27 board, which plugs the servo into the lcd connector pin, you add #define HAS_PIN_27_BOARD to your Config file. (only for boards V4.2.2. V4.2.7)

@ellensp ellensp closed this as completed Aug 4, 2021
@zaped212
Copy link

zaped212 commented Aug 4, 2021

@ellensp thanks for the info, I will adjust my configuration to that.

I initially had both Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN and USE_PROBE_FOR_Z_HOMING defined, and looked like it was trying to use the probe for homing but was expecting it to be on the wrong pin.

I never did try without the Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN, except for when I changed Z_MIN_PROBE_PIN. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants