I have an IR probe.

How do I delete all calibration settings and start from scratch?

cancel.g of course!

Thank you.

…..

@longshot:

Run G32 without homing
Run G29

A nice graph pops up with this.

https://ibb.co/cFaNuv

So here's the problem:

https://ibb.co/bOSrnF

What in the world is going on. Its like I never calibrated . . .
I can't be that far off the mark.

When I run G29 I get an error about no valid grid defined for G29. I am guessing you have a G29 grid defined too?
I'd love to see a graph…

Anyway, now I cannot print anything. Need to start all over but am lost as to what to delete and where to start.

Have you made any progress?

@DC42, you said disable bed compensation before calibrating? How do you do this and how long does the setting last? I see an option for this under the "Auto Delta Calibration" button, but it never changes to Enable bed compensation.

For a Delta, which is better Auto Delta Calibration (G30 P0 - P<whatever>) or Grid (G29?)

How do I start over? delete all offsets, calibration, and start fresh with Z height and ensure there is no fragments from previous releases or betas that remain?

Thanks!</whatever>

Sorry for the incredibly late reply. I haven't been able to work on it for a while. I ran the test and took a video of what happened. That video is linked here.

In short one of the extruder steppers moves as expected while the other does not want to turn.

I now found the time to test it and by now it seems to be working. Startet 4 -5 times and it always started at X41 as you said it should. and didnt go back to -30 like before.

Thanks for your help.

To be honest, I gave up as I was way too busy with the Nimble.
So have not looked at getting it sorted out.
But I think the problem was more on my side than the hardware side.

I was also thinking if it would be viable to divide the temperature curve (R:T) into ranges and have the software adjust the temperatures reported by DWC in the lower range to better reflect actual temperatures (while relying on actual readings in detecting faults). Not exactly necessary but there's something about those incorrect readings on my all-powerful control interface that rub me the wrong way.

I prefer to keep my slicer configuration as standard as possible and do parking, heating and unparking in free#.g and post#.g so it's easier to use different slicers.

PID provides better temperature control. It is essential for the hot end, and recommended for most bed heaters.

You are supposed to use M226 from with the gcode file itself, but in recent firmware versions M25 works too.

Slicer failed first time with M82, Head didn't move and extruder spun endlessly.
Slic3r does work with M83….

Now printing a very fine escher lizard......

At those prices I'd say that you aren't using genuine parts as supplied by from RepRap.me and with genuine E3D heat sinks. TBH and without wishing to cause any offence, that may be why you have problems. If you are interested, I did a bit of write up on my blog on how I assemble Diamonds hot ends. I don't seem to get the blockages or leaks that most people complain about so you might find something useful in what I have written - https://somei3deas.wordpress.com/2017/05/28/how-i-assemble-diamond-hot-ends/

Print looks much better .. still not perfect but closer, do a few more calcs and adjusts.. will up the current to 1000 in M906 and increase the extruder steps for the titan and the 0.9 motor .and keep trying . Thanks again all ..

Actually it's only necessary to put M82 in the slicer start gcode to use absolute extrusion.

Absolute extrusion is a huge pain in the butt from a firmware development perspective. It bears no direct relation to the amount of movement made by the extruder stepper except in the simple case of a machine with only one extruder drive, the extrusion factor set to 1.0, and no G92 E0 received since starting to extrude. So all the calculations have to be done after converting to relative extrusion anyway. OTOH the firmware code for pause/restore, resume after power fail and filament change procedures all needs to have unnecessary complications added to handle incoming gcode with absolute extruder coordinates.

It looks like Cura will support relative extruder coordinates in the near future, at which point the advice and documentation can be just to set your extruder to use relative extruder coordinates.

Yes if you build the firmware yourself. Do you have an issue with the current value?

Well first principles would suggest:
-If it's grinding then the idler isn't tight enough. You fixed that.
-if it is stalling the motor once the pinch wheel is tight enough (or skipping some steps) which results in the incomplete extrusion you've seen, then either:
-the e motor current is too low or
-there is some sort of physical restriction/obstruction preventing filament from flowing normally. Could be a blockage or something causing friction.

Try setting fairly high temperature for the filament you're using, and pushing it through by hand does it flow easily? Is your hotend as hot as you think it is? Try an atomic pull, see if it clears it.

That SOLVED IT!!!!!!!!!!!!!!!!

Thank You so much!!! I am now Printing and its great can I buy you a beer or 6 @DC42?

@Eddiie:

@DjDemonD:

If you're using ungeared its worth using 1/32 microstepping to reduce pulsing artefacts at low extrusion rates.

I am getting artifacts on some edges. Retraction does not seem to help.

I can also go 128 micro stepping..?

M350 X16 Y16 Z16 E16:16:16 I1

To make it 32,
M350 X16 Y16 Z16 E32:32:32 I1

Then adjust M92 settings for extruders to be double the old?

If you set the steps/mm with M92 assuming x16 microstepping before the M350 command, then the steps/mm will be adjusted automatically by the M350 command.

welcome back ~Russ… Thanks ~Russ!

OK i have been doing the life things but I'm back. ill update charts with the new data real soon...

for now I'm getting back on working on my OSDhttp://rwgresearch.com/open-projects/3d-printing-research/oversize-delta-3d-printer/. time to update the firmware. I'm sure I'm a few revisions behind!

~Russ