Topics created by RGN01

Oh, OK, thanks for clarifying.

I'm very happy with where this ended up - when the printer starts up it displays a message telling me to run the Delta_Start macro.

This sets the trigger (M581), checks which Smart Effector is installed, then homes the printer, runs delta config and then disables the trigger condition.

It works great and I won't get caught out with the Volcano installed and think I have the shorter v6!

Thanks for your help.

Richard

@Hergonoway I wasn't able to find your file on thingiverse, mind linking it?

Firmware 1.21RC3 runs file start.g first when you start to print a SD card file. You could do homing and auto calibration in that file.

I got this sorted - see https://www.duet3d.com/forum/thread.php?pid=40025#p40025

Richard

To get accurate homing, make sure that the XY position at which you home Z coincides with one of the points in the mesh. This isn't as easy as it sounds, because when you execute G30 to home Z, probing is done at the current location; whereas when you use G29 to generate a height map, the nozzle position is adjusted to allow for the offset of the probe. So in homez.g and homeall.g, choose the XY location that you send the nozzle to before you execute G30 so that it is at the location of a probe point close to the centre of the bed minus the Z probe XY offset that you specified in the G31 command.

It's this one

Fixed "listen failed" error after repeated use of FTP

@biscuitlad:

The zesty nimbles seem to have some supply issues currently, so I'll have to go ahead get it set up without them. So looking forward to quiet stepper motors!

It's a good idea not to change too many components in one go anyway, it makes troubleshooting easier.

Fantastic, David, thank you! That worked. Not sure how I managed that and I can't believe how many hours of confusion that cost me - and you.

Thanks again.

(edited to add) The support you provide is awesome. Thank you!)

Richard

Thanks, David. That makes sense and your comments about axis limits etc. have probably saved me asking another question on here!

Richard

@Stoop:

WHY don't you wanna use G92 after G30?

The firmware needs to know the Z probe trigger height anyway for other bed probing purposes. There is no point in putting the same information in two different places, you will just confuse yourself if/when that value changes.

Thanks, David. I'll experiment with this - the gz extension was throwing me.

Richard

I am in the process of updating the filament monitor support, and I decided to add support for pulse-type filament monitors at the same time. How many pulses per mm of filament does your sensor produce?

I've been asked to send this one back and a replacement will be in the mail this afternoon, I understand. Great service, thanks.

Richard

run the script at http://www.escher3d.com/pages/wizards/wizardbed.php using the params for your bed and it will generate a BED.G For you but edit the supplied file replacing the S6 at the end of the last G30 line with S8 so that it adjust for tilt as well.

Doug

Thanks, David, that works perfectly.