Posts made by myschetzky

Ah of course. Lower temperature while probing.

I wonder what s3d will do if I set a low temp in the starting script before the bedleveling routine.

I’ll experiment a little and return.

Hello,

How do you guys avoid making a bed full of dots and spider web when probing?
No matter how much I retract before probing I end up with a mess when probing is done.

/Niklas

It did! Yay! Almost an 1.02 board now. Hehe

Great. Then hopefully This Will work
https://drive.google.com/open?id=0B55_VkyZJuz0cGV3X3puZ1RXQUE

Ah but even if I turn the multimeter up to 2000K ohm's it doesn't register anything.
Oh well, I ordered a few spares which will arrive tomorrow. Thanks to the efficient Farnell!

Ordered this:
MF-MSMF014-2 MULTIFUSE, SMD, 0.14A
http://dk.farnell.com/bourns/mf-msmf014-2/multifuse-smd-0-14a/dp/9350284?CMP=i-ddd7-00001003

So I will add a self resetting fuse as per your instructions.

Connect the fuse between the E0 thermistor VSSA pin and the E1 endstop ground pin.

Will this fix all thermistors? Or do I need to add one for E1 and bed temp also?

Here is a video of it ..
Sorry about the upside down. It was difficult to probe and hold the phone at the same time!
https://www.youtube.com/watch?v=p4fdPfm9vks

Well if I set my multimeter to 200 ohm, it can register down to 0.1 ohm.

But when I put the probes on the VSSA and ground it still displays 1 on the display. As it does when the probes are not touching anything.

Oh now I found this
https://duet3d.com/wiki/Connector_and_spare_part_numbers#VSSA_fuse

haha always one step ahead huh Dave
But isn't it odd that I can't measure any resistance at all?

Hello,

Both hotend and bed are showing 2000c. So from what I can read in other posts the VSSA fuse is most likely blown.
But when I try to measure the resistance from an end stop ground pin to the VSSA pin on the back, it shows no resistance at all.

Could you provide a diagnostic and repair guide for dummies?

Kind regards, Niklas

Oh thank you!

Important! If you use an IR Z probe or some other type that does not need to be deployed, delete the files sys/deployprobe and sys/retractprobe.g if they exist, because they are now called automatically. You can do this in the System Files Editor of the web interface.

Hello,

I just upgraded my delta's firmware from 1.18 to 1.19. And as part of the calibration, I do a G32.
And it does probe the bed at the defined points, but between every one it goes to the far left corner, moves down a bit, then to the back of the bed where it does a sliding movement, before it continues to the next probe point.

See a video of it here:
https://app.frame.io/f/rQmQHdCz

Why is that?!

Thank you in advance for any help

Kind regards, Niklas

Check if the plug is properly seated on the board.

So I did the above, and then started a print, but first I commented the S29 out in bed.g to try only with the G32.

This resulted in a print starting 2 mm above the plate. So apparently the M500 created an override file with a wrong height.

But also I could see a quite active up/down compensation going on. Several mm up and down over a few cm travel. Which I guess is odd considering I didn't do a G29. And I disabled the load of the old height map.

I'm so confused.

I re-mounted my fiber plate, upside down to protect my PEI from further damage. (Scraped a bit in earlier auto level tests)
Then I went through the https://duet3d.com/wiki/Calibrating_a_delta_printer page again, measuring trigger height. Checking repeatability and then running G32 a few times until it settled. And then finally a M500 to save.

I didn't change my bed.g since I just uploaded it here for review.

Don't you think these results looks fine and consistent enough?

Here is my bed.g

[[language]]
M561						; clear any bed transform, otherwise homing may be at the wrong height
G31 X0 Y0					; don't want any probe offset for this
G28						; home the printer

; Probe the bed and do 6- or 7-factor auto calibration
G30 P0 X0.00 Y88.97 Z-99999 H0
G30 P1 X83.80 Y48.38 Z-99999 H0
G30 P2 X95.26 Y-55.00 Z-99999 H0
G30 P3 X0.00 Y-110.00 Z-99999 H0
G30 P4 X-95.26 Y-55.00 Z-99999 H0
G30 P5 X-83.80 Y48.38 Z-99999 H0
G30 P6 X0.00 Y37.35 Z-99999 H0
G30 P7 X47.63 Y-27.50 Z-99999 H0
G30 P8 X-47.63 Y-27.50 Z-99999 H0
G30 P9 X0 Y0 Z-99999 S7

G1 X0 Y0 Z150 F9000			; get the head out of the way of the bed

G29 S1

Hi David,

Thank You for your reply. Much appreciated!

Yes, but the slant measured by the probe matched the result on the print. So that suggests that the probe data isn't being used. I have G32 in my start script. And I deleted the the override. I don't think there is anything overwriting it.
I have a G29 S-1 in the end of bed.g

I lowered the nozzle until it gripped a piece of paper, then did a G92 Z0 followed by G1 Z5, and then a G31 S-1. Then I moved to another YX pos and did the same thing. Hmm or did I actually reset Z between new XY pos?! I'll have to retry that tomorrow to confirm. (At the pillow now)

Ah okay. My glass bed is clear with the heat thing glued underneath. So that explains the unreliable probes on the glass. Back to my PEI slate then.

Which means that I have to check if anything overwrites after G32. And check if I checked the Z trigger height correctly. If I didn't, could the slant be effector tilt?
I checked my rods and paired them in as equal pairs as I could. There isn't much more than 0.2mm in difference from shortest to longest rod.

And then because I wanted to see if it could be reflections or something about the glass, I did a G29 on a piece of paper.
Which resulted in this bonkers result

Next G29 try, also on glass bed

And console

From my console on the last probes on my glass bed

Hello,

I've upgraded my Kossel build from Ramps to Duet Wifi, but I can't get my bed to autolevel. I'm using the IR sensor.
I feel like I've tried everything. It probes fine. The Z trigger height is consistent at 8 different places when testing.

But what made me write this post is that I can't understand my latest issue.

When I do a G32 and then a G29 on my regular build plate. A fiber slate with PEI, the height map shows a consistent slant going up towards the back side. Quite a bit actually. But its very consistent with the test print failures I've been doing. However it didn't seem to compensate for it even tho the height map made sense..

So I removed the fiber slate, and tried with the glass plate I had underneath. But then my height map went crazy. It looks like a hedgehog.
And of course the print is even worse since the adhesion is far from as good as PEI when the level is off.

So why is it probing so bad on my glass bed?
And why isn't it using the probe data I was getting on my fiber slate?

And last but not least - If my Trigger height is consistent all over the plate when testing manually, does that mean that I shouldn't worry about effector tilt?

Thank you for any advice!

/Niklas