Topics created by Dugee

@jay_s_uk I saw that one, but it doesn't automate the trigger heights, but the calibration process.

I did see a thread that included automating the trigger heights,

https://forum.duet3d.com/topic/14280/invitation-to-share-your-conditional-gcode-scripts

but havent yet found any follow up.

I also found this one, which I'll have to read through first!

https://forum.duet3d.com/topic/17872/automatic-bed-leveling-with-conditional-gcode-iterations/40

@Veti I'll add that back in tonight and check PID. I was having problems with my bed heater, and had removed it from the config previously. thanks for spotting.

@Dugee You're getting there!

@Phaedrux it was the daily digest of new topics. It normally hits my inbox at 6pm every day. I look forward to it! Seems to be coming through again now.

@Phaedrux thanks. I understand that better now.

Tbh, now I'm home and getting stuck in I am much happier.

I had a missing decimal point that threw my autocalibration out. 192mm z offset at one of the probe points instead of 0.192mm

My autocalibration figure is coming out at 0.052, which I'm now more than happy with, so I'm hoping not to do the trigger heights again for a while.

I was expecting much more pain than I actually got tonight.

@T3P3Tony. @Dougal1957

17:32:11G32
Calibrated 6 factors using 16 points, deviation before 0.887 after 0.071

1st calibration run after putting the decimal place back in!

Dougal, you are my new hero.

@Dugee said in dimensional accuracy:

I think the auto calibration of delta arm length has given me more problems than solutions.

If you read the wiki page on auto calibrating delta printers, you will see that we recommend using 6 factor calibration, which leaves the arm length alone.

I had done it earlier, but as you say, it is now set to 0.

I'm using the bed switches on a monoprice Mini delta, wired in parallel instead of individually, which is actually giving me me amazing repeatability, Over a sequence of 5 probes, I'm almost always having the last 4 the same to 3 decimal places and the 1st probe +0.02mm greater., all around the +/- 0.5mm mark.

I'm giving up for tonight but tomorrow I'll do the G31 probing again and check I have the correct figure again, and as suggested by @Pheadrux I'll also move to firmware 2.04rc1.

I knew it must be something straightforward as I had a couple of prints last week, but I've been staring too much at it today. Beginning to go fuzzy!

thanks for the help

edited to change wiring of bed switches

Thanks for the confirmation!

@dugee said in Maestro not connecting to DWC or via USB:

@dc42 , I can't see any damage on or around U3, but I've plugged it in again to check connectivity and whilst it is still unresponsive, U10 gets very hot to touch after about 1-2 seconds of USB power. Everything else looks OK and nothing else seems to be reacting strangely.

U10 is the Ethernet interface chip. If it is getting very hot, that indicates it is damaged. My guess is that U3 has failed and subjected it to excess voltage. If your board was still under warranty on 29 July when you reported the problem, please ask your supplier to replace it under warranty.

ok thanks @dc42 I'll fill in the form now, as I purchased direct.

(The only reason to have the switches as normally closed is prevent movement if there is a loose connection. With normally closed switches that would trigger immediately, while normally opened would never trigger. However that may be reason enough to change, IDK.)

@dc42 Thanks for the reminder. I had seen that in the documentation but I'll make a note when I start the install.