Mesh bed leveling gone wild!
-
Looks like the firmware thinks that X10 is not reachable by the probe, hence the initial column of zeros. In the config.g file you posted earlier, the X movement limit (M208 S1 X) is -22 and the probe offset (G31 X) is +32, which puts X10 right on the boundary between reachable and not reachable. Try X11:200 in your M558 command instead of X10:200.
-
That seems to work for the left side of the bed. Still does not seem right yet. This is what I just ran M557 X11:200 Y10:200 S40 and this is what I see only points on right hand row.
this is the file RepRapFirmware height map file v1 generated at 2017-04-19 12:41 mean error -0.08 deviation 0.13
xmin xmax ymin ymax radius spacing xnum ynum
11 200 10 200 -1 40 5 5
0 -0.176 -0.151 -0.162 -0.202
0 -0.021 -0.038 -0.076 -0.12
0 0.115 0.067 0.002 -0.073
0 0.14 0.041 -0.062 -0.167
0 0.059 -0.09 -0.255 -0.412It did probe X11
What about the config.json mismatch?
-
I just spotted this in your earlier post:
It also thinks the firmware is 1.17 and I have 1.18.1
If it thinks the firmware is 1.17, chances are that it is. Send command M115 to check. If the upgrade to 1.18.1 failed, you may need to upload the latest iap4e.bin before you upload firmware 1.18.1.
-
4:04:02 PM M115
FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.18.1 ELECTRONICS: Duet WiFi 1.0 FIRMWARE_DATE: 2017-04-09But the config.json says 1.17
{"board":"duetwifi10","firmware":1.17,"compatibility":2,"nvram":false,"geometry":{"type":"cartesian","mins":[0,0,0],"maxes":[200,200,180]},"drives":[{"direction":0,"microstepping":32,"microstepping_interpolation":true,"steps_per_mm":320,"instant_dv":15,"max_speed":6000,"acceleration":500,"current":800,"driver":0,"endstop_type":1,"endstop_location":1},{"direction":0,"microstepping":32,"microstepping_interpolation":true,"steps_per_mm":320,"instant_dv":15,"max_speed":6000,"acceleration":20,"current":800,"driver":1,"endstop_type":1,"endstop_location":1},{"direction":1,"microstepping":32,"microstepping_interpolation":true,"steps_per_mm":10240,"instant_dv":0.2,"max_speed":150,"acceleration":250,"current":800,"driver":2,"endstop_type":3,"endstop_location":1},{"direction":1,"microstepping":32,"microstepping_interpolation":true,"steps_per_mm":420,"instant_dv":2,"max_speed":20,"acceleration":250,"current":800,"driver":3}],"idle":{"used":true,"factor":30,"timeout":30},"homing_speed_fast":"30","homing_speed_slow":"6","travel_speed":100,"z_dive_height":5,"slow_homing":false,"probe":{"type":"unmodulated","trigger_height":2.5,"trigger_value":443,"x_offset":0,"y_offset":0,"speed":2,"deploy":false,"points":[{"x":30,"y":15,"z":0},{"x":30,"y":180,"z":0},{"x":180,"y":180,"z":0},{"x":180,"y":15,"z":0},{"x":100,"y":100,"z":0}]},"num_nozzles":1,"bed_is_nozzle":false,"bed":{"present":true,"heater":0,"use_pid":false,"width":200,"length":200},"chamber":{"present":false},"max_heater_temperature":260,"heaters":[{"scale_factor":100,"series":4700,"thermistor":100000,"beta":4138,"a":0.0005717725,"b":0.0002416626,"c":0,"channel":0},{"scale_factor":100,"series":4700,"thermistor":100000,"beta":4138,"a":0.0005717725,"b":0.0002416626,"c":0,"channel":1}],"toolchange_wait_for_temperatures":true,"generate_t_code":false,"tools":[{"number":0,"extruders":[0],"heaters":[1],"x_offset":0,"y_offset":0,"z_offset":0}],"compensation_x_offset":15,"compensation_y_offset":15,"mesh":{"x_min":30,"x_max":185,"y_min":15,"y_max":185,"spacing":20},"home_first":false,"orthogonal":{"compensation":false},"network":{"enabled":true,"name":"","password":"","dhcp":true},"fans":[{"value":"30","inverted":false,"frequency":500,"thermostatic":false},{"value":"100","inverted":false,"frequency":500,"thermostatic":true,"heaters":[0,1],"trigger_temperature":45},{"value":"100","inverted":false,"frequency":500,"thermostatic":true,"heaters":[1],"trigger_temperature":45}],"custom_settings":""}
-
Also did you see the heightmap pic? Just one row of data show up. Does not appear to be work as it carved out my PEI !
-
I guess that may be an artifact of how DWC responds to the column of zeros. I'll ask chrishamm to check it out.
-
Why am I getting zeros if it is probing X11? What about the rest of the data as well?
-
Your config.json file doesn't agreed with the config.g file you posted earlier. Please post your current config.g file again.
The version number in config.json suggests to me that you created it before you upgraded the firmware.
-
Like I said they don't jive. I did the full firmware again and same thing. Ran m997 no change to config.json
{"board":"duetwifi10","firmware":1.17,"compatibility":2,"nvram":false,"geometry":{"type":"cartesian","mins":[0,0,0],"maxes":[200,200,180]},"drives":[{"direction":0,"microstepping":32,"microstepping_interpolation":true,"steps_per_mm":320,"instant_dv":15,"max_speed":6000,"acceleration":500,"current":800,"driver":0,"endstop_type":1,"endstop_location":1},{"direction":0,"microstepping":32,"microstepping_interpolation":true,"steps_per_mm":320,"instant_dv":15,"max_speed":6000,"acceleration":20,"current":800,"driver":1,"endstop_type":1,"endstop_location":1},{"direction":1,"microstepping":32,"microstepping_interpolation":true,"steps_per_mm":10240,"instant_dv":0.2,"max_speed":150,"acceleration":250,"current":800,"driver":2,"endstop_type":3,"endstop_location":1},{"direction":1,"microstepping":32,"microstepping_interpolation":true,"steps_per_mm":420,"instant_dv":2,"max_speed":20,"acceleration":250,"current":800,"driver":3}],"idle":{"used":true,"factor":30,"timeout":30},"homing_speed_fast":"30","homing_speed_slow":"6","travel_speed":100,"z_dive_height":5,"slow_homing":false,"probe":{"type":"unmodulated","trigger_height":2.5,"trigger_value":443,"x_offset":0,"y_offset":0,"speed":2,"deploy":false,"points":[{"x":30,"y":15,"z":0},{"x":30,"y":180,"z":0},{"x":180,"y":180,"z":0},{"x":180,"y":15,"z":0},{"x":100,"y":100,"z":0}]},"num_nozzles":1,"bed_is_nozzle":false,"bed":{"present":true,"heater":0,"use_pid":false,"width":200,"length":200},"chamber":{"present":false},"max_heater_temperature":260,"heaters":[{"scale_factor":100,"series":4700,"thermistor":100000,"beta":4138,"a":0.0005717725,"b":0.0002416626,"c":0,"channel":0},{"scale_factor":100,"series":4700,"thermistor":100000,"beta":4138,"a":0.0005717725,"b":0.0002416626,"c":0,"channel":1}],"toolchange_wait_for_temperatures":true,"generate_t_code":false,"tools":[{"number":0,"extruders":[0],"heaters":[1],"x_offset":0,"y_offset":0,"z_offset":0}],"compensation_x_offset":15,"compensation_y_offset":15,"mesh":{"x_min":30,"x_max":185,"y_min":15,"y_max":185,"spacing":20},"home_first":false,"orthogonal":{"compensation":false},"network":{"enabled":true,"name":"","password":"","dhcp":true},"fans":[{"value":"30","inverted":false,"frequency":500,"thermostatic":false},{"value":"100","inverted":false,"frequency":500,"thermostatic":true,"heaters":[0,1],"trigger_temperature":45},{"value":"100","inverted":false,"frequency":500,"thermostatic":true,"heaters":[1],"trigger_temperature":45}],"custom_settings":""}
-
So i was having the same issue of 0's in the first column, and only displaying part of the mesh in the mesh visualizer, I had unwittingly made my X start point value for the probe grid below my X offset and the first column was 0'd out for the 16 point grid.
-
I was 2mm inside the the offset and just for giggles changed it 27mm and shazaam! It started working! I guess you can't be close to the edge…..
-
Now to try a test print.
-
Check my Wonky first layer post; https://www.duet3d.com/forum/thread.php?id=1647
