@CrazyCreator
For anyone who has the same problem after me, here's how to connect or insert the ribbon cable.
You have to flip the small black bracket upwards, then insert the cable, and then flip the bracket back down. This secures the cable.
Of course, you should have known beforehand that there is a bracket on these mini jacks.

IMG_0786.jpeg

@dc42 said in Set Z height Max For clay Delta printer:

@JetClay one option may be to use G30 S-1 to do manual probing without setting the Z height to zero. Then run this:

G10 L2 Z{sensors.probes[0].lastStopHeight}

This will set the Z offset of the workplace to that height. Or you could use:

G10 L2 Z{move.axes[2].userPosition}

since the current Z position will be the same. Or even:

G10 L20 Z0

You can include

G10 L2 Z0

in your homedelta.g file to reset the offset to zero when you home the printer again.

Thank you very much for your response we finally made it work! we used this code

; SetZHeight.g - Manual Z height calibration & M665 H update
M291 P"Ensure the nozzle is clean. Press OK to continue." R"Z-Height Calibration" S3

G28 ; Home all axes completely before probing
M665 ; Print current M665 values for reference

; Ensure previous height offsets are cleared
G10 L2 Z0

M291 P"Move the nozzle down until it just touches the bed. Press OK when done." R"Manual Adjustment" S3 S2

G30 S-1 ; Perform manual probing without setting Z=0

M291 P"Extracting new height offset..." R"Processing" S1

; Ensure latest calibration data is loaded before changing M665 H
M501 ; Load saved config-override.g (M665 H value)

; Capture the last probe height and set Z offset
G10 L2 Z{sensors.probes[0].lastStopHeight}

; Update M665 H dynamically based on last saved value
M665 H{move.kinematics.homedHeight - sensors.probes[0].lastStopHeight}

; Save new M665 H for persistence
M500 ; Save parameters to config-override.g

M291 P"Calibration complete! The new Z height and M665 H value have been saved." R"Success" S1
M501 ; override config file
G28 ; Home axes

Hope it works for maore people!

@Inlinebrother said in Duet 3 mini 5+/FYSETC Big Dipper on FFCP/Flashforge Creator Pro:

I installed the bltouch and it's working perfectly fine. Though I was concerned that it is glowing red and not violet

My genuine BLTouch has a red LED on all the time. I think there's a blue one, but it is very dull. I think the red one goes off when the probe is triggered, so you see the blue one, but that happens very quickly, so hard to spot. So I think that's normal.

Ian

@gloomyandy
Thank you!

@Proschi78 I can't see any reason for it to be an issue👌

@Proschi78 May want to start a new thread with your specific question.

@oliof said in Fysetc StrideMax Dual - CAN-FD Expansion Board:

@Exerqtor seems your wish has been fulfilled

87d9956f-a184-48d0-aa61-acc25e5e0d2a-image.png

Oh wow! They managed to let the typo follow all the way to production though! The label on the product box i got mine in say Daul 😆

@dc42 it works know
6f85142d-73f4-4d61-9d87-2724c2f64ddd-image.png

Thanks for your support

@Phaedrux I have extended the way thank you

@jay_s_uk ok, ja da haben sie recht. Mal sehen, werde mal darüber nachdenken. Vielen Dank für die Infos und Anregungen. Liebe Grüße Wolfgang

@dc42 Thanks for the help I managed to do it

If your windows / arduino can generate HTTP you can use https://github.com/Duet3D/RepRapFirmware/wiki/HTTP-requests. This is quite a straightforward interface, e.g. a GET of http://11.22.33.44/rr_gcode?gcode=G28 will execute G28 (ie home all) on the duet machine at 11.22.33.44. It has file operations (upload, download, list, delete etc.), execute arbitarray gcode, and let you get any part of the object model (which lets you check almost every element of the state or status of the machine).

If you install curl you can do this from pretty much any scripting language (even .bat files).

If you have a Pi connected to the duet device there's also the DSF: https://github.com/Duet3D/DuetSoftwareFramework This will let you do anything the duet can do, but requires more detailed and particular programming knowledge.

@jay_s_uk said in RFF 3.42 extruder change:

@paolozampini1973 you have more than 1 tool defined though. you don't need to have a physical toolchange to have different tools

So what do you think I should do delete them?

@tecno said in Suddenly extrusion buttons Extrude/Retract are grey!:

M563 P1 H1 F0

You don't have a motor assigned to the tool. You need a D value.

EDIT: I see Gloomyandy got you there first.

@selva_tvi T1 just pauses so if you want to do more than that you'll have to use a different trigger and create a trigger file accordingly.
See here about setting up power resume https://docs.duet3d.com/en/User_manual/Tuning/Resume

@jay_s_uk

Thanks for the help...I actually got it working now. This time I only commented the M558 line out

@selva_tvi We got the solution. Pin assignment in config.g has to be changed.

;Filament Runout sensor
M591 D0 P1 C"e1stop" S1
M591 D1 P1 C"e2stop" S1

Accordingly it has to be connected to the board as per the given diagram

Octopus Pro Endstop Pins.JPG

We can consider this as solved and we can close this case. Thanks for the support

@jay_s_uk
Thank you
An issue has been solved

If you want to use your endstop as a emergency stop you can re-purpose them at the end of the homing file to act as an estop. Just be sure to set them as endstops again at the start of homing.

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m581-configure-external-trigger

@phaedrux Ah yes thank you very much, adding g29 s1 to the cura start code seems to have solved the issue!