@jltx said in SZP for bed level in 3.6-RC1:

I don't understand the DWC feedback. I was seeing red Z values for heights above the trigger, like 6mm. And sometimes I see yellow. Right now it is behaving.

Are you sure it was red when that far above the trigger height? That is not normal unless the probe is returning an invalid reading (in which case it will read 99999). The colour will change as you get close to the trigger threshold. Had you actually set the trigger threshold when you saw the DWC reading go red? You can find out what the current trigger height and threshold are by running G31 k<probe number> with no other parameters.

The threshold is set either by using the P parameter to G31, when you do that you are basically saying set the trigger threshold to be <xxxx> (the P parameter value) and that this value will be reported at the Z height set with the Z parameter of G31. The alternate way to set the threshold with a SZP is to set the Z trigger height with G31 and then to use M558.1 to run a calibration pass. This will move to the Z trigger height plus the calibration range set by the M558.1 S parameter and will then move down to the trigger height minus the calibration range, taking a series of readings. This data is then used to calibrate the conversion of readings to actual height above the bed. As part of the process the probe trigger threshold will also be set to match the trigger height.

I am currently trying to get mesh.g to work but it fails every time on the first point with an error that I need to recalibrate the probe, despite the ABL working correctly now. The G29 starts with a high Z value that I cannot seem to control.

What is the full error message you are getting when you try to perform the scan? You probably need to post your updated bed.g and mesh.g files so we can see what it is you are doing.

After running ABL you should rehome Z and probably recalibrate the SZP using M558.1 then run the scan using G29, this scan will move the probe to the trigger height as set by G31 and will then perform the scan. So you need to be sure that that drive current is set to ensure that you have valid readings with the nozzle at the selected trigger height and at all heights above/below this needed to obtain a scan.

@thomasvanderwal said in Duet 2 v1.02 not responding:

Calibration is now the problem. After setting the trigger height and z0 I wanted to Run Delta calibration. This is going well. But the mesh compansation is not going well : Error: G29: Probe was not triggered during probing move
The nozzle even goes besides the bed? I have in config.g : M557 R95 S10. The bed is 20cm in diameter,

As this thread is now well over 100 posts and does not match the description and initial issue, I think you'd have better luck starting a new thread for your delta calibration issue. You're more likely to get some helpful delta users to lend a hand with calibration.

@Phaedrux Ok! Thank you very much! That's work fine now. 👍

I had a problem with my tablet but I found the solution on this post.
I also had an error report with my ZPROBE line in my config.g but after a complete reboot of the printer I no longer had an error.

Please give us more information.

https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help

@dc42 Thank you for your help! We had to fix the jumpers and connect a power supply for the fan pins to work.

Great! I’ll proceed the way you’ve outlined.

Thank you for the detailed response. Extremely helpful!

@konvalm FYI we have an outstanding ussie regarding this situation:

https://github.com/Duet3D/RepRapFirmware/issues/1082

T3P3 created this issue in Duet3D/RepRapFirmware open SAME70 - Firmware update failures #1082

@T3P3Tony said in 4 Z Axis Leadscrews:

Please paste config.g in use the code block (</> icon in the text formatting menu), to format it

I have edited your post to paste in the contents of the file in a code block. this makes it much easier for people to help you.

from the documentation here:
https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_auto_levelling#axis-levelling-using-endstops

When homing, RRF3 will home both axes, and stop each motor when each endstop is triggered. Note that DWC and M119 will only show one endstop per axis, but will show the axis endstop as triggered if either switch is triggered. So you can test them by triggering one at a time.

That is true for the object model as well.

@dc42
@droftarts

Hello guys,

I tried it and got a reply.
So that worked.

After being sure that it is only Eth issue, I added a small switch in between, I remember that once I did a similar work-around at a LAN connection at my friend's house during a LAN party (yes, I am that old).

AND I got a reply from printer! DWC smiled at me.

I works like a charm now.
Interface is there, firmware updated and I am happy as I can be.

I would like to thank you both for your help and assistance.

Kind Regards,

P.S. If any of you two passes through Linz, let me know. I owe you a beer or few.

@Aurimas does the tool also have 4 temperature sensors? What commands in config.g are you using to configure it?

@thooms

It's important to differentiate between G32 - bed leveling (auto or manual) and G29 (mesh compensation - mesh creation - mesh loading)

Both require setting the Z=0 Datum using G30.

G32 (bed leveling) should be followed by G30.

G29 (mesh creation or loading) should be preceded by G30.

On a machine that allows auto bed leveling you will likely use G32 (bed leveling) followed by G30 (setting the Z=0 Datum) then G29 S1 (mesh loading).

In that case the G30 proceeding the G29 satisfies the need to follow G32 by G30.

The reason for G30 after G32 is that the leveling process can change the Z position of Z=0 - doing the G30 resets the Z=0 Datum correctly.

Hope that clarifies rather than confuses.

Frederick

@DoodleCube said in Need help with 5 Bar SCARA configuration:

it seems RRF3 on Duet 2 stopped supporting 5 bar

there are flags in RRF to turn on or off those "exotic" kinematics, so if you're able to compile it yourself, you can turn it on for Duet 2.

Pins.h
'# define SUPPORT_FIVEBARSCARA 0
Set this to 1.

@elmoret
Germany dont remember the retailer it was 2021 or something like that

@droftarts
Solved, firefox had some issues with the site.

@dc42 Thank you, and everyone. I'll put that on the To-Do after this print (took the lazy route and stuck it on an external SD via PanelDue for now).

Will mark as solved.