@foesi said in BL-Touch M402 and M280 P0 S90 do not retract pin:

@Phaedrux I tried to position the screw in a position where the test at power on just gets the pin back up in retracted position.
I can´t get the screw in the position as mentioned in the antclabs documentation - because then the pin would not get back up.
And I also used magnets to get the pin magnetised.🤷

This makes it sound like there is something wrong with the BLtouch.

@wurth51 if you get a short between Vssa and a higher voltage then you should get a message on the DWC console warning you of the short.

@sindarius Just tested and working well - many thanks!

@krohm-koala - Thank you for your reply. I was just trying to point out that you should value your own time, even a day developing your own and you are basically valuing your time at very little per hour after material costs. Thats why we made them available for others. Take care.

@dc42 said in Duet smart effector directive drive on E3d titan aero:

@garyd9 said in Duet smart effector directive drive on E3d titan aero:

The only reason I recalibrate on power loss is because RRF (for some reason) can't use the M665/M666 settings to determine how to re-apply mesh compensation. (It's been explained to me at least once, but I never understood it.)

Can you link to a thread about that? I can't remember the reason either, and it might be good to fix it.

I can't quickly find any of the older threads, so I just created a new one here:

https://forum.duet3d.com/topic/23172/delta-mesh-comp-without-g30

Thank you
Gary

Forgot the bltouch wire cover.
bltouch-wirecover.STL

*The front and back parts require threaded inserts.

@Hesus29 said in CoreXY layer shift but only in one direction:

Idk what caused this thing

Friction is the enemy of mechanical freedom.

@dc42 any way we can actually inform the firmware or DWC about the estimated finish time? something like, read data from M73 and send it to firmware? (if firmware is not supporting M73 on it's own)

Aaaaah!! Thank you very much, now it works with RRF3!
Thanks for the support!!

@dc42 wow, thats a good thing to know. As I understand when I open the valve, I can just after few second use same comand with half of power just to keep everything open. Amazing 🙂

@WilcoE

Hi,

I set my steps/mm by "jogging" the head from DWC and insuring that, say, a 100 mm move actually moves the nozzle tip a 100 mm, easily measured with a mm scale.

Then I print my calibration cubes and adjust the size, if needed, via M579.

Frederick

sorry i just realized how the setup is one.

are the switches NO or NC?

i would try to wire them in parallel and use M558 P5

they will need to be connected to the z probe port.

but a construct would allow the printhead to move. this would not be beneficial for the print quality.

@veti Yep that was the reason! Thanks a lot!

@maerkler said in Duet 2 Wifi connection Problems:

; Bed probe section (not needed if you use a bed.g file)
;*** Adjust the XY coordinates in the following M557 commands to suit your build and the position of your Z probe
M557 P0 X60 Y0 ; Four...
M557 P1 X60 Y165 ; ...probe points...
M557 P2 X200 Y165 ; ...for bed...
M557 P3 X200 Y0 ; ...levelling
;M557 P4 X141 Y82.5 ; 5th probe point for levelling (un-comment this to get a 5th point at the centre of the bed)

You're not using M557 correctly at all. See here:

https://duet3d.dozuki.com/Wiki/Gcode#Section_M557_Set_Z_probe_point_or_define_probing_grid

https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation

Parameters to define G32 probe points (Cartesian/CoreXY printers only, deprecated and not supported in firmware 1.18 and later)

Pnnn Probe point number
Xnnn X coordinate
Ynnn Y coordinate
Example

M557 P1 X30 Y40.5

You have some other problems. Twice there is the sequence:

es after '''S''', expected 3
Done!
Response while disconnected:

The first line is probably part of an error message from the Duet, but Repetier has chopped off the first part. I've no idea about "Done!" but I think that's from Repetier, not the Duet. After that, Repetier seems to think it shouldn't be connected and is surprised to see a response.

and thank you who read this topic 400 people i hope you learn from this topic

Look at https://github.com/dc42/PanelDueFirmware/releases . It starts with "Choosing the correct firmware binary" .

@dc42 woah that's an awesome feature! Thanks

Glad it's working.

@darnz said in External Drivers for Nema 34 Steppers:

Could I make use of expansion plug pins for my XY and Z?

So useE2 for my X
Use E3 for my Y
And use E4 for my Z.

Yes, use the M584 command in config.g to specify which drivers your axis motors use.

Do you think I may have a problem with one pin feeding signal to upto4 drivers?

You might be able to drive 4 drivers from one expansion breakout board output. Or you could use E4 and E5 to drive 2 Z drivers each.