Topics created by Puppet172

I'm sorry it has taken me so long to look at this. Does your printer still have this problem?

If so, then I can think of a these possible explanations:

The Z motor is consistently skipping steps when moving in one direction, but not when moving in the other direction. To test this, home the printer, position the nozzle at a known height above the bed, then send these commands:

G91 ; relative mode
G1 Z15 F100
G1 Z-15 F100
G1 Z15 F100
G1 Z-15 F100
... (repeat that pair of commands several times)
G90 ; back to absolute

Then check whether the nozzle height above the bed is the same as when you started.

The print head is crashing into the bed before the Z probe triggers, causing missed steps at that point.

The sudden stop that occurs during bed probing is causing the missed steps. To check this, position the head over the bed but above the trigger height and send these two commands repeatedly:

G30 S-1
G1 Z10
G30 S-1
G1 Z10
...

The trigger height reported by the G30 S-1 command should remain the same to within about 0.02mm. Does it?

HTH David

@t3p3tony said in An extruder to turn a spool:

@deckingman nice write up. With 5 extrucers you are always coming up against stuff that most other people don't have to worry about (like changing the middle spool of 3!)

Thanks Tony. And exactly so. For most people changing a reel of filament is relatively quick and painless job. Changing the middle spool of 3 is one thing but when I swap from say a Diamond 3 colour to a Diamond 5 colour, I have to unload 3 spools, then load up 5 spools so it's a bit of major operation. Less painful than it used to be now though.....

I think you should give firmware 2.01 a go to see if one of the recent bug fixes for mesh leveling solves your issue.

When you do, clear your Heights map, rerun the trigger height measuring, and redo g29. Then make sure your new height map is being loaded before a print with g29 s1.

@puppet172 yes, please contact who you bought the board from and reference this thread.

The G31 command it after the M558 command. So are there any other possibilities of why it wouldn't be changing?
Also i don't have a override file so that can't be it

If the problem is only when going up, that suggests that you have too little motor current set to overcome the load, or you have the Z acceleration set too high.

@puppet172 said in Z probe Detects bed but doesn't stop:

This is my Z probe
https://www.amazon.com/gp/product/B00S50O152/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1

Which mode do you think will be best?
I am thinking 1 or 2 but I don't know

The answer is in the wiki page that I linked to.

I answered the first question in your other post a few minutes ago. Regarding the second question, see https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_NPN_output_normally_open_inductive_or_capacitive_sensor.

See https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#main for advice on connecting various types of Z probe. If the V_FAN jumper is set to the VIN position then the easiest place to get VIN is from one of the always-on fan connectors.

@puppet172 said in Z axis not stopping at Endstop:

; Endstops
M574 X2 Y1 S1 ; Set active low endstops
M574 Z0 S1

Where you have that, try this:

M574 X2 Y1 Z1 S0

That's assuming you have the X end stop at the high end of travel and the Y and Z end stop at the low end of travel. S0 sets them to active low switches which should work with those makerbot switches.

Modify your homez.g to reverse the direction.

If you want post the file content here and we can help.

Is the DueX5 definitely getting VIN power?

Does the Settings General page of DWC mention the DueX5?

Does M122 list the status of 10 drives, or only 5?

The order of the commands in your config.g is a problem, see https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Main_configuration_file.