Topics created by Deltasquare

very strange.

I notice you're using probe type P1 for the piezo, which is intended for analog probes with feedback.

I believe it's more common to use P8 for digital mode for the piezo. Perhaps there is erroneous analogue feedback/interference at those points causing it to slow down as it approaches.

Can you test with P8?

How is your piezos mounted? What type?

This is a probe with an analog output connected to the Z probe connector. The probe output must rise as it gets closer to the bed, unless you use parameter I1 in the M558 command to indicate that the probe output falls as it gets closer to the bed (the I1 parameter is supported in firmware 1.16 and later). The control signal is driven HIGH.

P1 specifies an unmodulated or smart IR probe, or any other probe type that emulates one (probe output is an analog signal that rises with decreasing nozzle height above the bed). If there is a control signal to the probe, it is driven high when the probe type is P1.

@Deltasquare said in Tool Changing - Storing and retrieving z-offsets:

Thank you!

This helps with displaying the offset, but should the offset displayed not switch around depending on the chosen tool?

Both methods require a tool# be issued
You can probably get what you want with something like (assuming you want Z offset)

if state.currentTool != -1 M117 {"Z offset of " ^ tools[(state.currentTool)].name ^ " is " ^ tools[state.currentTool].offsets[2]} else M117 {"No tool selected"}

But if the printer was just warming up and I do a G28, than probe again another 100x it shouldnt do the same drift again, or am I mistaken?

@Deltasquare said in Attaching 5V device:

dc42 said I can simply plug the RasPi into the output of the paneldue, which is a 4-pin plug where I populated the 5V pin on the far right as well as the ground left of it. Before plugging the Raspberry into that I checked the voltage and there is nothing....

You should get 5V between the pins as shown here https://d17kynu4zpq5hy.cloudfront.net/igi/duet3d/4k56ZjaaAHrTJI6Z.huge. The pins are on the far right or the far left depending on which way up you have the Duet.

It's already mentioned at https://duet3d.dozuki.com/Wiki/Duex_wiring_diagrams#Section_Warnings_and_Cautions.

@Deltasquare said in Did I kill my DuetWiFi?:

So I have a new board now. Just to make sure this time:

If I run a 24V System, I can only set the voltage to 12V on the DueX.

By "I can only set the voltage to 12V on the DueX", do you mean you can set the Fan voltage to 12V on the DueX but not on the Duet? If so, that is correct.

For this purpose we have the jumper on the Duex. If I set it I can power Fans as well as LEDs from Duex

Correct, if you connect the LEDs to spare fan outputs.

however, the Duex does not act as a constant power source for the LEDs.

Do you mean that you want some "Always-on" LEDs? The most recent DueX5 revision has a 12V always-on output (when the 12V Enable jumper is in place). For other DueX5 revisions, with the fan voltage selection jumper set to 12V you can connect a 12V always-on fan or LED between the VFAN pin of any fan output and the ground VIN connection.

@bearer said in Forum: Name not found:

( you should be able to see all your posts on your user profile as well for future reference, or does it not work?
https://forum.duet3d.com/user/deltasquare )

This works well, thank you! I was just surprised that the search function would not show my latest post:

Search does not show latest post.

It is not that this is a showstopper, however other forum admins like to be made aware.

I will find my way around now. Thank you again.

M558
Recovery time at 1 does not change a thing.
Speed at F100 does neither improves nor detriotates measurements

Can anybody help me?

If the problem occurs only while the fan is powered (not when it is spinning down), you could try setting Z probe type P9 in your M558 command, as if you were using a bltouch. That will cause the firmware to run deployprobe.g and retractprobe.g for each individual probe move. You could turn the fan off in deployprobe.g and on again in retractprobe.g.

The Smart Effector only "hijacks the fan power" to power the illumination LEDs.