@Donpi since I don't have duet 3, I can't use that, although it's the same result I'm looking for.

I am assembling a workbee, as soon as it is assembled I will test your code @Sindarius , thank you very much, you saved me many hours of development.

I use this macro, i found it on the forum. its working for now

; Z Probing macro

M400                                ; wait for current movement to finish

M291 P"Make sure the probe is connected and the Endmill is on top of the probe" R"Warning" S3   ; warning message

G91                                 ; set relative position
G30 S-1
M400
G10 L20 Z19.1                         ; set Z offset to 19.1
G1 Z10

M291 P"Probing complete on the CURRENT WCS. Please remove probe." R"Success" S1    ; screen message```

I use this macro, i found it on the forum. its working for now

; Z Probing macro

M400                                ; wait for current movement to finish

M291 P"Make sure the probe is connected and the Endmill is on top of the probe" R"Warning" S3   ; warning message

G91                                 ; set relative position
G30 S-1
M400
G10 L20 Z19.1                         ; set Z offset to 19.1
G1 Z10

M291 P"Probing complete on the CURRENT WCS. Please remove probe." R"Success" S1    ; screen message```

@edwardp said in Ooznest Workbee Z Touch Plate Support with RRF3.2.2:

OK - machine up and running.

My probe z macros is now as follows:

M563 P0 S"ZProbe" ; Define a 'fake' tool (is this necessary?)
T0 ; set the fake tool

M400 ; make sure we've finished any other movements

M558 K3 P5 C"!e0stop" ; configure probe 3 as switch connected to e0stop
M585 Z10 F600 P3 S1 ; probe 'forward' in Z 10mm or until Probe 3 triggers

; Set the current workplane offset relative to this current position, backed-off 10mm 
; in Z to allow for touch plate thickness

G10 L20 Z10 

I do not appear to have 'deployprobe.g' or 'retractprobe.g' in the system files (or macros) but I did have a 'probe.g', which definitely looks out of date so I have renamed that in case it was problematic.

Macro, as posted, produces no errors, response or movement. For the avoidance of doubt, the machine homes, jogs in all axis, moves under G0/G1 etc. with no apparent issues.

I have the same problems with my workbee

@Sindarius the plugin only works in DWC 3.2? I use the workbee version (i think is based in 2.0.4)

@Donpi since I don't have duet 3, I can't use that, although it's the same result I'm looking for.

I am assembling a workbee, as soon as it is assembled I will test your code @Sindarius , thank you very much, you saved me many hours of development.

I don't know the world of duet too much yet, would this work with duet 2 wifi?

@Sindarius WOW, nice job.
Is the code shared anywhere?

Hi, I'm looking for information in case someone has tried it before.
I'm trying to integrate a gamepad (for example the xbox one), although any gamepad connected to the pc would work, to handle the movement of the axes manually.
My idea is to use the GAMEPAD API (https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API/Using_the_Gamepad_API)
to develop a small code in javascript that converts the keystrokes into GCODE.

Any similar project that has made progress?

I have seen on the forum some related to hardware connections through the screen port, but my intention is that we do not have to use any additional hardware apart from the gamepad itself.