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

Phaedrux

Couple questions

Are you sure your z steps are 4000?

How did you measure your z offset for the G31 command?

Are you using mesh compensation?

I don't see anywhere in your config where you load the height map.

Can you see the z axis move at all if you move to z=0 and move the head in x and y?

Which guide did you follow?

Puppet172

@phaedrux

they might be a little off but i don't know because i haven't been able to get a solid cube done to measure the height. but i can check now
I put the head in the middle of the bed and the put it down so it barely grabbed my piece of paper. then i did G92 Z0 and then moved the head up ~3 mm and then did G30 S-1 to home z in that point. then i put the number that i got in the z axis as my offset.
Yes, i am using mesh bed compensation.
I don't know how to put that in config so it works in prints or anything, i thought that was automatic.
i don't believe so it would only move if that head started to scrape against the bed because the bed isn't completely flat
6.https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

If you need any other files i can post them
Thanks,
Bennett

dc42

How are you homing Z? Please post your homez.g and homeall.g files.

Puppet172

I am homing with z probe. Also i figured out one problem and it was that my z steps were way off bc they were at 4000 but they were supposed to be at 2000. so that fixed some stuff but i still don't think the compensation is working while printing

0_1530374213194_homez (1).g

0_1530374220925_homeall.g

Phaedrux

@puppet172

https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation

https://duet3d.dozuki.com/Wiki/Gcode#Section_M375_Load_height_map

M375 with no parameters will load the default height map.

Homing files look ok to me I think.

dc42

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

Puppet172

@dc42 @Phaedrux

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)