BL-touch was working
-
@downshift64 said in BL-touch was working:
@phaedrux those 2 files there config.g and home all i dont see that anything is wrong
G29 S0
Warning: Skipping grid point X=-20.0, Y=25.0 because Z probe cannot reach it
Warning: Skipping grid point X=0.0, Y=25.0 because Z probe cannot reach it
just noticed this warning
should that first probe point be the same as M557 define meshIt will skip points that the probe physically can't get to. You can either just ignore that warning, or alter the M557 command to keep the probe within bounds.
-
@phaedrux that is within bonds that is where it was before i think but if it isnt its still on the bed close to where it was
do i need to change the Y25 because it goes to X-20 it just goes past the Y off the bed into the neg towards me
what i dont understand is if i just home it probes the bed at x15 Y25just looked at my heightmap from yesterday and its X-20 Y25
should it have S20:20 or is S20 ok; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Wed Jul 06 2022 10:08:28 GMT-0500 (Central Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X15 Y28 F6000 ; go to first probe point
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
@downshift64 said in BL-touch was working:
G1 X15 Y28 F6000 ; go to first probe point
G30 ; home Z by probing the bedIt homes Z with the probe where you tell it to in homeall.g and homez.g
That is unrelated to where it probes for a mesh compensation routine.
-
@phaedrux that is the spot i told it to probe for the mesh yesterday but today it wont i dont understand does it save anything in memory maybe that might need to be cleared
-
I'm really not sure what you mean. Can you illustrate the problem you're seeing?
-
@phaedrux maybe this can explain better than i can i hope
https://www.youtube.com/watch?v=a4e_qhzWl1E -
Ok, I see what you mean now with the video. I think what needs to happen is that the M208 min and max be adjusted such that the nozzle is positioned accurately on the bed, and the G31 XY offsets for the probe accurately measured as well. Then you can tweak the M557 range a bit to ensure the probe is always within the safe range.
To get the M208 correct the easiest way is to manually move the nozzle to the front left corner of the bed where you want 0,0 to bed. Once there, send G92 X0 Y0. Now send M564 S0 to allow movement outside of bounds. Now jog the axis towards the endstops until they just trigger. Check your position with M114. The position it reports for that axis will be your new M208 minima for that axis. This value may be slightly negative. Now when the endstop is triggered, it will correctly set the 0,0 point to be where you want it on the bed. Do this for both X and Y.
Once the minima is set, you can now measure the maxima by manually jogging towards the far end of the axis stopping when you either hit the physical extent, or as long as the nozzle is still on the bed. Check position again with M114 and use that as the M208 maxima for that axis.
For the G31 XY offsets for the probe follow this method to measure it accurately.
This lets the firmware know exactly where the probe is in relation to the nozzle tip. This is important so that it will keep the probe within bounds when doing a mesh.
Now that you have the min and max positions of the axis and the probe offsets correct you can set the M557 range. One option is to just take your min and max values, add a bit of buffer on the edges, and leave it at that. Or if you want to maximize the probed area you can physically jog the nozzle to each extend and see where the probe is actually able to reach and adjust the M557 range so that only areas it can reach will be probed.
-
@downshift64 how can u make sure your using the heightmap mine doesnt look like it is being compensated
-
You can send M122 for a diagnostic report. One of the lines will say
Compensation: MeshorCompensation: none -
@phaedrux thank you i feel like i need to pay you i have learned a lot upgrading this printer
-
@downshift64 === Move ===
DMs created 83, segments created 11, maxWait 135054ms, bed compensation in use: mesh, comp offset 0.000
got some real high spots and some to low and it says i am using the mesh is that how a probed bed is supposed to be like this,, i think i can do this without a bltouch -
Can you share a screen shot of the heightmap viewer in DWC?
Did you go through and make all the changes I had mentioned in that longer post?
-
-
@downshift64 i done some of the changes and just wanted to try it since my bed has been heating for about 1 hour but working on all of them now
got my redone my Z0
i haven't been doing the probe offset right i just jogged the nozzle or X around and whatever the location was on the web status was i put that as the offset i didn't realize that one side u had to put positive or neg that's helped a lot -
Yeah that will make a big difference because it depends on the offset to tell it where the probe is in relation to the nozzle. So the heightmap will be shifted by whatever the error is in the offset from probe to nozzle.
-
@phaedrux i taped a piece of paper down to the bed touched it with the nozzle then marked that spot it took 30mm of y and 37mm of x to line the probe up with the mark my probe is to the right of the nozzle and in front of it so that would be y is -30 and X is +37
G31 P500 X37 Y-30 Z2.67 ; set Z probe trigger value, offset and trigger height
M557 X-23:277 Y30:294 S20 ; define mesh grid
what am i doing wrong now it wont probe in the spots i tell it -
That sounds correct for the measurement of the offset.
For the mesh grid I would try
M557 X40:277 Y40:290I'm not sure what your X and Y maxima are, so I left them at 277 and 290, but I would take whatever you've measured for the M208 maxima and bring it in 40mm from the edge. That should at least get you safely within the bed bounds. Then you can try and increase the range a bit, keeping in mind that you don't want it to move the probe off the bed surface, and that it will skip any points it can't physically reach with the probe.
-
@phaedrux should the printer home at 0:0 with a probe first before it moves to the center of the bed right now i have it moving to center
; Axis Limits
M208 X-24 Y-29 Z-3.0 S1 ; set axis minima
M208 X305 Y295 Z295 S0 ; set axis maxima
G31 P500 X37 Y-30 Z2.67 ; set Z probe trigger value, offset and trigger height
M557 X-23:277 Y30:294 S20 ; define mesh grid
this is with M557 X40:277 Y40:290
M557 X-23:277 Y30:290 S20 this is what i get with this M557 the x location is where it should be but Y isnt it should be closer to the front or me by about 30+ mm
M98 P"0:/macros/PROBE BED GRID"
Warning: Skipping grid point X=-23.0, Y=30.0 because Z probe cannot reach it
Warning: Skipping grid point X=-3.0, Y=30.0 because Z probe cannot reach it
-
@downshift64 said in BL-touch was working:
should the printer home at 0:0 with a probe first before it moves to the center of the bed right now i have it moving to center
I'm not sure what you mean by that. Homing is done in homeall.g and the other homing macros. Normally it's recommended to home the Z axis with the probe at the center of the bed.
@downshift64 said in BL-touch was working:
M557 X-23:277 Y30:290 S20 this is what i get with this M557 the x location is where it should be but Y isnt it should be closer to the front or me by about 30+ mm
Then Change Y30:290 to Y5. Maybe Y0 if you think it's safely going to touch the bed at each point along the edge.
@downshift64 said in BL-touch was working:
Warning: Skipping grid point X=-23.0, Y=30.0 because Z probe cannot reach it
Warning: Skipping grid point X=-3.0, Y=30.0 because Z probe cannot reach itYour probe physically can't reach those points because it's on the right side of the print head. That's why I suggested starting with X40
-
@phaedrux what i am not understanding is why do you have to measure the probes offset to the nozzle when it doesnt use that or i am not understanding something here
