Cant get my nozzle close to bed at all when trying to print

dc42

I agree, homing files look ok. G29 S1 also loads the height map. Which firmware version are you using?

Puppet172

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0 + DueX5
Firmware Version: 1.19.2 (2017-09-01)
WiFi Server Version: 1.19.2
Web Interface Version: 1.19.3

dc42

With older firmware versions there is a known issue if the height map has a nonzero height offset at the XY point at which you do Z homing, and you home Z when a height map is loaded. Workarounds are to clear the height map before Z homing, or to upgrade to version 2.0 firmware.

Puppet172

@dc42 @Phaedrux
Just updated the firmware and now having homing problems like endstops hitting but not stopping the axis's

Puppet172

@dc42 @Phaedrux
Fixed that but now it says insufficient axis's homed How can i stop this from happening becuase it say i need to home x and y first before homing z but i can home x because it says
G28 X
Error: G0/G1: insufficient axes homed

whosrdaddy

Reading the firmware upgrade notes would have prevented this question
In recent firmwares you cannot move axes before they are homed, so you must add S2 to G1 moves for non homed axes...
Anyway, you can add M564 H0 to your config.g file to have the old behavior back...

Puppet172

@dc42
How can i control my fans in the new server version because i only see control for Fan 0 and i have mine on 1&2

Puppet172

@puppet172
Nvm

Puppet172

@dc42
Still not using the mesh bed compensation during print. Even after i updated. Any idea why?

Phaedrux

@puppet172 Did you add the M375 or G29 S1 command to load the height map to your config.g?

Puppet172

@phaedrux
no where would i add that
0_1530485751276_config (3).g

Phaedrux

Just add M375 anywhere in config.g.

I put mine in the section where I configure the mesh size and z probe.

Puppet172

@phaedrux
That should fix it then?

Phaedrux

That will load the height map if you've run a successful compensation probing. That will adjust the nozzle height based on the probe data to keep it at the specified height from the bed at all times.

Hopefully that will resolve your issue.

Puppet172

@phaedrux
if i change me trigger height should i run another mesh bed compensation( G29)

Phaedrux

I'm not sure about that. As long as the probe is triggering consistently when you make the map the new trigger height should be applied after homing z and it should follow the height map correctly, but I could be wrong in my thinking there.

Regardless, I like to follow this order for bed leveling just to make sure.

Mechanically level your bed as well as you can first.

Measure your trigger height at least 10 times and take the average (or mode if it looks like a single value repeats most often).

Then run a compensation probing routine knowing that the results should be as accurate as possible.

Then you can varify that the height compensation is applied by moving to z=0.5 and jogging the head over the bed and see if the z axis is engaging to keep the distance the same as it moves.

Puppet172

@phaedrux @dc42

When im doing a mesh bed compensation It keeps getting to a point where the bed is a little higher there and it triggers the probe before it probes there. so i get this
Error: Z probe already triggered before probing move started
Is there anyway to get around this because all my axis's are level the bed just isnt
Thanks

Phaedrux

You can try increasing your dive height a millimeter or two.

Puppet172

@phaedrux
Where is that?

Puppet172

@puppet172 @Phaedrux
Nvm found it