Topics created by Kiwi3D

@Kiwi3D said in BL Touch . CR Touch:

M280 P0 S1000
M950 S0 C"121.io0.out" ; 121 is my toolboard CAN ID
M558 P9 C"121.io0.in" H5 F120 T6000

You can't use M280 (set servo position) before you define the pin with M950. For the proper sequence of GCodes, please refer to the Configuration section of the document Connecting a Z probe - BLTouch (which covers the CR Touch, too).

@jay_s_uk

M669 K2 X1:0:1 Y0:1:0 Z1:0:-1

Machine is a Voron Switchwire

@Kiwi3D im core XY , , you are core Xz
but you should still be able to use my home x , you need to modify it for your core XZ

something like this

; homex.g echo "home the X axis" M400 ; make sure everything has stopped before we make changes G91 ; relative positioning M915 P0.0 S5 H200 F0 R0 ; Configure Stall Detection M906 X550 ; set homing motor current G1 F8000 G1 H1 X-350 ; Home X-Axis independently M906 X1000 ; set homing motor current M915 P0.0 S35 H500 F0 R1 ; Configure Stall Detection M400 ; make sure everything has stopped before we make changes G90 ; absolute positioning G1 F12000 X152.5

@Kiwi3D your steps per mm for z should be the same as X I would expect

@droftarts

Thank you for confirmation. PID in progress now

@jay_s_uk

Awesome - case closed 🙂

What firmware version is on your Duet and PanelDue?
Is that the SD card in the Duet or PanelDue?

@Kiwi3D said in Lead Screw Calibration:

So what am I doing wrong here tea. Yes I understand P0 (left most probe position ) and P1 (right most probe position)

Driving me potty to be honest

I have attached my config.g and lead-screw macro.....welcome any feedback please

Screen Shot 2020-06-28 at 6.12.51 PM.png

config (6).g calibrate_leadscrews (1).g

I would say your probing in the wrong order swap the P0 and P1 parameters round but leave the X Y Co-ords where they are also the second set should be P2 and P3 even tho they just repeat the probes (Don't think you really need those mind and they may just confuse the issue.

So try

M561 ;G30 P1 X10 Y100 Z-99999 ; probe near a leadscrew ;G30 P0 X210 Y100 Z-99999 S2; probe near a leadscrew G30 P0 X10 Y100 Z-99999 ; probe near a leadscrew G30 P1 X210 Y100 Z-99999 S2; probe near a leadscrew G1 Z10 ;M561 ;G30 P0 X10 Y100 Z-99999 ; probe near a leadscrew ;G30 P1 X210 Y100 Z-99999 S2; probe near a leadscrew ;G30 P0 X10 Y100 Z-99999 ; probe near a leadscrew ;G30 P1 X210 Y100 Z-99999 S2; probe near a leadscrew ;G1 Z10

HTH

Doug

@Kiwi3D said in Maestro - dead - Blue LED Flashing:

Would you believe it ended up being a corrupt SD Card.

which blue led were you talking about? are there more than one blue led perhaps?

Thank you....very confusing.....

Perhaps you saw this?

https://forum.duet3d.com/topic/13970/dueui-release-3-0-1-beta2-available

Or more likely it was a Duet 3 connected to an touch screen display running the full web interface in a browser window on a Pi?

I think this warning message shows up because rr_gcode returns that there is no more buffer space available (buf:0). You seem to issue a lot of codes from DWC2 and most of them haven't finished when this message pops up.

I would guess you have a problem with the supply that last shorter than the update intervall DWC has for displaying Vin. Check your wiring or get a meter that will measure fast enoigh or have a usable min/max function?

Does your homeall/homez file use a G30 command to probe the bed or is it configured to use a G1 H1 Z move to seek an endstop?

Also see: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

@Kiwi3D There was this thread recently about noisy LDO Prusa motors: https://forum.duet3d.com/topic/15121/is-it-normal-for-motors-to-vibrate-and-hiss-at-standstill

Ian

Thank you 😃