3DTouch deploys too soon after probe May 31, 2019 08:42AM |
Registered: 7 years ago Posts: 46 |
Re: 3DTouch deploys too soon after probe May 31, 2019 06:39PM |
Registered: 8 years ago Posts: 752 |
Re: 3DTouch deploys too soon after probe May 31, 2019 07:42PM |
Registered: 7 years ago Posts: 46 |
Re: 3DTouch deploys too soon after probe June 01, 2019 09:45AM |
Admin Registered: 10 years ago Posts: 3,096 |
Re: 3DTouch deploys too soon after probe June 02, 2019 02:43AM |
Registered: 7 years ago Posts: 46 |
Re: 3DTouch deploys too soon after probe June 05, 2019 05:39AM |
Registered: 8 years ago Posts: 752 |
#define BLTOUCH_DELAY 375Did you try this? I'm not sure what it does exactly but might be worth a shot. The code should look like this:
#define BLTOUCH #if ENABLED(BLTOUCH) #define BLTOUCH_DELAY 375 // (ms) Enable and increase if needed #endif
#define Z_CLEARANCE_DEPLOY_PROBE 10 // Z Clearance for Deploy/Stow #define Z_CLEARANCE_BETWEEN_PROBES 5 // Z Clearance between probe points #define Z_CLEARANCE_MULTI_PROBE 5 // Z Clearance between multiple probesDid you try increasing the clearance?