Results 1 to 9 of 9
Thread: G29 probes only in 1 location
-
06-26-2015, 03:52 PM #1
- Join Date
- Dec 2014
- Posts
- 8
G29 probes only in 1 location
I moved this to a new thread
Roxy directed me to this forum and the Beckdac fork from issue#2040 about the ABL bugs.
I've uploaded the Beckdac to my Ramps 1.4 on a Mendel90, the Y endstop is at Y max and the X endstop is at X max (back right of the bed)
When I send a G28, homing takes place at the back right and then when I send G29, there is no movement in X or Y and the same point is probed each time. I've tried switching the origin from front left to back right with no change. EEPROM and chitchat are disabled.
I also tried a M48 L 10 which Roxy suggested elsewhere and there was no movement in X and Y.
Even with safe Z homing enabled, homing and probing is at back right.
I able to manually jog X and Y but they both stop a bit short of the bed edges.
I've attached a link to my configuration.h and Marlin_main.h and will be grateful for any assistance in fixing this.
configuration.h http://pastebin.com/T6u1Gghk
marlin_main.cpp http://pastebin.com/NbATys7k
-
06-26-2015, 04:22 PM #2
Your home limit switches are at the Max side of the bed for X & Y ???? And when you say it only probes one point, does it probe that same point multiple times?
I'm not positive this is the problem, but you have:
Code:#define min_software_endstops true // If true, axis won't move to coordinates less than HOME_POS. #define max_software_endstops true // If true, axis won't move to coordinates greater than the defined lengths below
Code:#define MANUAL_X_HOME_POS 195 #define MANUAL_Y_HOME_POS 195 #define MANUAL_Z_HOME_POS 0
Update: I just noticed this:
Code:// set the rectangle in which to probe #define LEFT_PROBE_BED_POSITION 7 #define RIGHT_PROBE_BED_POSITION 140 #define FRONT_PROBE_BED_POSITION 13 #define BACK_PROBE_BED_POSITION 181 ... // these are the offsets to the probe relative to the extruder tip (Hotend - Probe) #define X_PROBE_OFFSET_FROM_EXTRUDER -38 // Probe on: -left +right #define Y_PROBE_OFFSET_FROM_EXTRUDER -8 // Probe on: -front +behind #define Z_PROBE_OFFSET_FROM_EXTRUDER -1.11 // -below (always!)
Code:#define LEFT_PROBE_BED_POSITION 50 #define RIGHT_PROBE_BED_POSITION 125 #define FRONT_PROBE_BED_POSITION 50 #define BACK_PROBE_BED_POSITION 125
Last edited by Roxy; 06-26-2015 at 04:41 PM.
-
06-26-2015, 07:04 PM #3
- Join Date
- Dec 2014
- Posts
- 8
Your home limit switches are at the Max side of the bed for X & Y
does it probe that same point multiple times?
I also turned off software endstops and changed the probe points as you suggested but it's made no difference. I'm sending plain G29 without topology report.
-
06-27-2015, 08:42 AM #4
It would also be helpful to see the output of the G29 with a high verbose level: G29 T V 4 We should be able to see if it is looping through all the points it is supposed to.
-
06-27-2015, 09:19 AM #5
- Join Date
- Dec 2014
- Posts
- 8
Here's the log, probing took place in one location only (back right)
Code:15:16:45.706 : N538 G28 *61 15:16:49.653 : ok 15:17:00.698 : N544 G29 T V4 *33 15:17:00.698 : Roxy's Enhanced G29 Auto_Bed_Leveling Code V1.81: 15:17:00.713 : Full support at http://3dprintboard.com 15:17:06.002 : Bed x: 50.00 y: 50.00 z: 1.12 15:17:12.039 : Bed x: 87.00 y: 50.00 z: 1.11 15:17:18.061 : Bed x: 124.00 y: 50.00 z: 1.12 15:17:24.098 : Bed x: 50.00 y: 87.00 z: 1.11 15:17:30.135 : Bed x: 87.00 y: 87.00 z: 1.11 15:17:36.172 : Bed x: 124.00 y: 87.00 z: 1.11 15:17:42.210 : Bed x: 50.00 y: 124.00 z: 1.11 15:17:48.262 : Bed x: 87.00 y: 124.00 z: 1.11 15:17:54.300 : Bed x: 124.00 y: 124.00 z: 1.12 15:17:54.300 : Eqn coefficients: a: 0.00 b: -0.00 d: 1.12 15:17:54.315 : Mean of sampled points: 1.112673 15:17:54.315 : 15:17:54.315 : Bed Height Topography: 15:17:54.315 : --0.00392 --0.00580 +0.00233 15:17:54.315 : +0.00045 --0.00049 --0.00017 15:17:54.315 : +0.00326 +0.00201 +0.00233 15:17:54.315 : 15:17:54.315 : planeNormal x: -0.00 y: 0.00 z: 1.00 15:17:54.315 : 15:17:54.331 : Bed Level Correction Matrix: 15:17:54.331 : 1.000000 0.000000 0.000021 15:17:54.331 : 0.000000 1.000000 -0.000068 15:17:54.331 : -0.000021 0.000068 1.000000 15:17:56.031 : ok 15:17:56.031 : echo:endstops hit: X:125.00 Y:108.00 Z:1.12
-
06-27-2015, 10:32 AM #6
The output should look like:
Bed Level Correction Matrix:
1.000000 0.000000 -0.000449
0.000000 1.000000 0.000548
0.000449 -0.000548 1.000000
echo:endstops hit: Z:4.72
It should say the Z endstop was hit... But not the X & Y. I think that is the explanation for why it is refusing to move the X & Y.
I don't know what your end stop configuration is... But switching one of these might make it go:
const bool X_MIN_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
const bool Y_MIN_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
or maybe...
const bool Y_MAX_ENDSTOP_INVERTING = true; // set to true to invert the logic of the endstop.
const bool Z_MAX_ENDSTOP_INVERTING = true; // set to true to invert the logic of the endstop
PS. Make sure you have a finger on the reset button when you tell it to home! Like I say, I don't know how your end stops are wired. But it would be unusual to have some one way and others a different way. My guess is flipping the true and false on either the Min or the Max might make it go.Last edited by Roxy; 06-27-2015 at 11:14 AM.
-
06-27-2015, 12:03 PM #7
- Join Date
- Dec 2014
- Posts
- 8
Thanks, that helped. I got myself into a bit of muddle with the min/max and direction of the Y axis
-
06-27-2015, 12:09 PM #8
-
06-27-2015, 06:07 PM #9
- Join Date
- Dec 2014
- Posts
- 8
yes, it's working. thanks for your help!
Printer will print perfect...
06-14-2024, 10:44 AM in Tips, Tricks and Tech Help