They are quite close in length so they should work very well. Definitely pair the most equal length rods with one another. Deltas function on having the closest match to pairs of perfect right angled triangles formed between the arms, linear guides and effector. So the more perfect each pair of triangles are the better. That being said start this way do some calibration, swap them around see what effect it has.

Ok, I'm finally back and able to work on the printer again. I connected all of the wires as I stated in the previous post of mine. Sadly, I am getting no input to the drive whatsoever.

Things that may be causing an issue:

ENA+ is said to require +5V at the driver instead of the +3V I had previously listed. Possibly improper from my coding of the M584 command. Possible incorrect pinout from my previous post.

@dc42, you have been awesome so far and I feel like I'm getting very close! Any help is appreciated!

Thanks, Sniffle, that's just the information I needed.

Well, I have a microswitch mounted on my X axis printhead and use it for z endstop and for z probe. Its is mounted offset in both X, Y and Z (lifted 5mm) in a way that it can sample 3 points on the printbed, while the nozzle is outside of the printbed. Totally stole the idea from the BCN3D Sigma 🙂

But I am now installing a BLTouch.

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. 😕

@dc42:

@Whitewolf:

@dc42:

Keep the results. A lot of users get that warning since E3D started supplying silicone socks with their hot ends.

Any way to get that message to stop flooding the PanelDue Console?

You should only get it once.

It seems to repost everytime a change to config.h is made that is why I was seeing it over and over again in the PanelDue console

solution is in this forum here -> https://www.duet3d.com/forum/thread.php?pid=14276#p14276

@dc42:

If you have a PanelDue attached then you can use M300 to make it beep.

Not have PanelDue 😞 if use Fan3?

@my67nova:

…............. Never tried deleting the config-overide.g was not sure what it would do.

Well the config-overide.g does "just what it says on the tin". That is to say, the values in it override the same parameters that are set in config.g. So deleting config-overide.g would simply mean that everything reverts to whatever values are in config.g. Personally, I never use a config-overide.g file just because it is too easy to forget that it is there, overriding any changes I might make to config.g. So whenever I tune a heater or alter homing parameters, I always make a note of the new values and edit the config.g file, rather than use M500 to create another file. I always like to annotate the config.g file with notes on the date and time and the reason for the changes, as well as commenting out the old values rather than deleting them. That way, when things don't work the way you expect them to, you don't get lost or confused.

Ok found something.
The config.gcode had M83 in the beginning so the printer was in relative move for extruders while the slicer do it in absolute mode.

Nice, thanks for the follow up.

I must have gotten overwhelmed learning all this gcode 🙂 It works Thank you

@dc42:

It's not implemented yet. Perhaps it should be M226 with a parameter that means "don't run pause.g or resume.g"?

That sounds like it would work perfectly….. right now I have 4 different macros for each point.... trying to make this simple for my kids. A single macro that pauses at each point where they can adjust the leveling screw then hit confirm on the paneldue would be perfect.

@dc42:

Auto tune in 1.18 will always overshoot the target temperature. You need a larger difference between the target temperature you use in M303 and the temperature limit set in M143. You should use the default P1.0 in M303.

Thank you!

I set the temp limit to 400C (the limit of the PT100)

; Heaters M143 S400 ; Set maximum heater temperature to 400C

Then set the target to the highest temp of filament I plan to use

M303 H1 P1.0 S380

This was the console message:

Warning: Heater 1 appears to be over-powered and a fire risk! If left on at full power, its temperature is predicted to reach 609C. Auto tune heater 1 completed in 545 sec

M307 H1 result:

Heater 1 model: gain 589.9, time constant 284.6, dead time 5.0, max PWM 1.00, mode: PID Computed PID parameters for setpoint change: P17.2, I0.061, D60.3 Computed PID parameters for load change: P17.2, I1.100, D60.3

Any Suggestions or is it safe to leave like this? Not sure if the parameters adjust for the over powered message automatically.

It's not uncommon to get a short inside the heater cartridge between the element and the case. This puts the hot end metalwork at 12V or 24V, and if that shorts to the thermistor ground lead then the VSSA fuse blows. If the piezo is also in contact with the hot end metalwork it could also account for your recent issue. So I suggest you check the heater cartridge.

Thanks for the replies. I'll go back to Z0 and then see if I can get a good layer squish from there.

It is remarkable that I went from Z-0.05 to Z-0.2 and with a 125% extra layer width - almost couldn't tell the difference without looking closely. I'd like to get lower first layer calibration eventually, but 0.3 layout height is quite forgiving.

Okay, thank you. That should be enough to figure it out. Much appreciated.

Please share the Gcode file.