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

[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

[Phaedrux]

The H value in the M558 command in config.g

[Phaedrux]

@puppet172 did it work?

[Puppet172]

@phaedrux @dc42
Yeah it worked.
And another question. When i re did my G29 to have more points to be more accurate, now when ever i print it is much higher off the print bed like a couple millimeters. Why would this be happening?
Thanks

[Puppet172]

@Phaedrux @dc42

I don't think the bed level is working to well

[Phaedrux]

Yeah that's a bit too high maybe.

Can we get some more details of your printer? Print surface? Slicer settings?firmware version?

[Puppet172]

@phaedrux
Ok So my printer is massive its about 3 ft cubed and has two arms controlling the y and one controlling the x and finally 4 lead screws controlling the z. it is printing onto a piece of aluminum that is screw down to box tube then that screwed into the frame the bed is not level by itself. i have tried my best to get it level on its own but to no avail. On that aluminum sheet is 1 foot squares of PEI i bought off amazon and have pieced together to make a bed surface. i am using Cura 15.04.6 as a slicer, but have been thinking about buying Simplify 3d.

[Puppet172]

@phaedrux
Software Information
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later + DueX5
Firmware Version: 2.01beta1(RTOS) (2018-06-23b1)
WiFi Server Version: 1.21
Web Interface Version: 1.21.2-b1

[Phaedrux]

Alright, from the top, try this.

Redo your trigger height measurements but run these commands first just to eliminate any overlapping height map errors.

M561			; Disable any current bed compensation
G29 S2			; Clear mesh bed compensation perameters
G31 Z0				; Reset zprobe trigger height 

Enter your resulting trigger height into config.g, reboot, and run a G29 and post the resulting height map image.

[Puppet172]

@phaedrux @dc42
Ok before i can do that i have a problem that just started happening. When i turn on the Printer i can connect for about 5 seconds and then it does like a reset and its says HTTP Error and then i cant connect until it does like a reboot and then it happens again over and over. My setting are still the same as before and this just started happening. Is it a bug with the new update?
Thanks,
Bennett

[Phaedrux]

Does it only do a reset when you connect to the DWC?

Can you connect via usb and terminal and do a M122 command and post the results?

When you updated to 2.0 did you get all of the other files as well? DWC etc?