Ooznest Workbee Z Touch Plate Support with RRF3.2.2

Phaedrux

I'll try and see where we're at with M585. Thanks for your patience.

dc42

@edwardp, please try the unofficial 3.3beta2+1 build at https://www.dropbox.com/sh/6203euyyobllic5/AABTHIbn7F_maK9p-oy7vq3Ea?dl=0. It's compatible with DWC for 3.3beta2.

edwardp

Thanks guys - @dc42 I'll flash the new firmware this weekend and report back.

edwardp

On uploading and installing Duet2CombinedFirmware.bin from your zip I get the following error:

Error: M997: In-application programming binary "0:/firmware/Duet2_SDiap32_WiFiEth.bin" not found

Do I need this additional file from somewhere, it is not included in the zip above?

E

dc42

You can find that file in the 3.3beta1 and 3.2.2 releases on github.

edwardp

OK - thanks @dc42. I've re-uploaded alongside the WifiEth.bin from the RRF3.2.2Beta2 and confirmed the new firmware looks good:

Board: Duet 2 Ethernet (2Ethernet)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.3beta2+1 (2021-03-19)

The probe test macros, exactly as above, continues to give no error or motion I'm afraid.

One aspect of my set-up I should be clear about is I am running the DWC-CNC-CNC02-3.2.0-RC1 (built from the tagged branch on https://github.com/Duet3D/DWC-CNC) from my local machine and connecting to the Duet2 over ethernet. I'm using this UI to upload the firmware patches and trigger the macro. This is our test machine, so it has been upgraded from RRF2 in quite a few incremental steps now. Could any of these things be a source of this problem?

Can I just also formally confirm that my macro (as posted above) does run on the test rigs you have at your end - I'm not sure we have quite stated that explicitly so thought I should check?

E

scrhall

@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

edwardp

@dc42 perhaps you could post a 'canonical' macro sample showing the commands as you intend them to be used and that you have verified at your end? If there is a typo/mistake in my macro this would help us to flush it out.

The set-up I (and I think many Workbee customers) have is simple and because of Ooznest's documentation: https://learn.ooznest.co.uk/Guide/Assembling+Your+Original+WorkBee+XYZ+Touch+Probe/61they should be configured pretty consistently. At this point I just need to reproduce the simplest Z probe (Step 8 ) under firmware 3.2.2 - which is needed before any CNC toolpath can be run.

The macro needs to drive the tool down in Z until contact with plate is made (wiring as per the link - plate is essentially an NO switch) and set Z0 in the current work-space to be this position, plus the thickness of the plate.

I cannot emphasise enough how core this functionality is. The Duet under RFW3.xx is not, in practical terms, usable as a CNC controller without it. It has been over a month since I raised this problem...

edwardp

(@scrhall thanks for checking this too, by the way, much appreciated)

chimaeragh

@edwardp I had to revert back to firmware 2.0.5 due to this very reason. Though I enjoyed using some of the added functionality in RRF3.2.2 with the DWC-CNC from @Sindarius , the lack of a probing wizard like Ooznest's made me go back to Workbee Control.

Hagrid

@chimaeragh I'm going to stick with RRF 3.??, but I really hope that @Sindarius manages to find the time to develop a plug-in that works in the same way. There must be quite a few of us that are craving this option

Sindarius

@hagrid it is on my list, just been side tracked with some other efforts at the moment.

Kane

Hey I use this code and it works as desired

M400 ; make sure we've finished any other movements

M558 K0 P5 F100 C"!e1stop"
M563 P0 S"ZProbe"
T0 ; set the fake tool
 
M585 Z10 F600 P0 S1 ; probe 'forward' in Z 10mm or until Probe 3 triggers
G10 L20 Z19.5		;Set Tool Offset to 19.5mm thickness of the touch plate

;raise the dirll for 5mm for the second run
G91             	; relative positioning
G1 Z+5 F1000      	; go back a few mm
G90					;absolute positioning

M585 Z10 F100 P0 S1 ; probe 'forward' in Z 10mm or until Probe 3 triggers
G10 L20 Z19.5		;Set Tool Offset to 19.5mm thickness of the touch plate

;raise the dirll for 20mm
G91             	; relative positioning
G1 Z+20.5 F1000     ; go back for 20mm
G90					;absolute positioning

But maybe I discovered a bug. If you leave out the first G10 command, the code behaves confusing. After the first pass, the z-axis run down in the ground for maybe 20mm and then perform the second probing. The raise for 5mm don`t seems to be performed. Maybe someone else can reproduce that.

Hagrid

@sindarius No worries. Good things are worth waiting for

scrhall

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

@kane - that seems to work for me! Many thanks. I simply changed the e1stop for the e0stop on my machine, but apart from that it seems to now run as I originally expected. There are a number of differences between our versions (we have commands in a different order and I use a different probe and dummy tool number, for example). I'll go through them line now and see if I can identify the precise problem with my original macro. I'll also see if I can confirm the other issue you mention.

Thanks again!

E