duet 3 triple z/motor problem

bzad

@fcwilt thanks yea will do

fcwilt

In your bed.g file after you try to level the bed with the G30 commands you are calling G29 to create the height map for mesh bed compensation.

Do you really want to do both of these together?

I keep them separate as I level the bed when homing but only probe the bed to create the height map manually using a macro.

In your homeall.g file if you wish to level the bed during homing you should use a G32 command to invoke bed.g rather than the three G30 Px commands - no point in having those commands duplicated in different files.

The video is a bit hard to follow when it comes to determining what moves are associated with what commands.

Frederick

bzad

@fcwilt I’ll try your way see what happens as for the video

Home all is done
Moves to
G30 P0 X35 Y30 Z-99999
Done and moves on to
G30 P1 X187 Y410 Z-99999
Done but the stuffer or whatever u call that happens and won’t move to
G30 P2 X405 Y30 Z-99999 S3

fcwilt

@bzad

In your config.g file you specify that the Z probe is 36 mm to the right of the nozzle - is that correct?

Frederick

bzad

@fcwilt yes

bzad

@fcwilt thx for your help i removed all g30's and isolated it in a macro and played around with numbers based on what was happening my understanding is that in my config g i set my build area as 400 or wahat ever and based on probe offset even though the probe had space it was trying to probe 2 far outside of the build volume and it was confusing the system so i just had to add 15 to config file for volume making it 415 even though my print area is only 375 ish

Phaedrux

@bzad said in duet 3 triple z/motor problem:

i just had to add 15 to config file for volume making it 415 even though my print area is only 375 ish

Telling it that it can move to 415 when it can only physically move 375 will likely lead to a crash.

Your points to probe need to be within the safe travel volume and allow for the probe offset.

fcwilt

@bzad said in duet 3 triple z/motor problem:

@fcwilt thx for your help i removed all g30's and isolated it in a macro

The firmware, version 3.3 at least, has already established the use of bed.g which is invoked by G32 and mesh.g which is invoked by G29.

Everything needed to perform leveling can be put in bed.g.

Everything needed to create the height for mesh compensation can be put in mesh.g.

When I say "everything" I mean that I put all of the commands needed so bed.g or mesh.g can be called at anytime and they will work as expected.

it was trying to probe 2 far outside of the build volume and it was confusing the system so i just had to add 15 to config file for volume making it 415 even though my print area is only 375 ish

That is one way to do it.

My axis min/max values are always set to the actual printing volume.

To deal with Z probe offset I either temporarily lift the min/max limits using M564 or pick probe points that are reachable despite the probe offsets.

Frederick

bzad

@phaedrux yup thought of that and found m564 in gcode commands and adde s0 and s1 before and after and put actual area to what is intended thanks

bzad

@fcwilt yup id like to do z level at start of a print so when i turn on printer or a job i know at least thats right (since the bed is a bit heavy it may roll down a bit just to be safe) and since bed g calls home all it will do that anyway and i also skimmed and found the m564 command added it and just saw your msg thanks for the recommendations and help

Phaedrux

@bzad said in duet 3 triple z/motor problem:

@phaedrux yup thought of that and found m564 in gcode commands and adde s0 and s1 before and after and put actual area to what is intended thanks

Yes that's fine as long as it's safe to travel that far.