Duet 3 6HC with Openbuilds XYZ Probe

Yveske

@Phaedrux
Took me some time, but got the Duet to work, the touch probe doesn't however...
Something I could try next ?

Thanks in advance
Yveske

Phaedrux

I'm not sure. It's quite odd. You can see the green LED flash on the X probing, and on the Y it certainly lights up, but isn't being respected.

Maybe related to the dual Y axis?

Yveske

@Phaedrux
Thanks I will try this today and let you know.

Yveske

@Phaedrux
Not sure how I can probe on Y with only one motor running without breaking the gantry and without disassembling...

I did however simulate M675 by manually using M38.2 and M38.4 commands on all axis (X, Y and Z) and this works like a charm.

Is it possible in a macro to access the coordinates after each command and use that to calculate the center of the cavity myself ?

Phaedrux

@Yveske said in Duet 3 6HC with Openbuilds XYZ Probe:

Not sure how I can probe on Y with only one motor running without breaking the gantry and without disassembling...

Yeah that's not something you can easily test

Yveske

Is there anyone out there who can try M675 in both X and Y axis please ?

Thanks,
Yveske

Yveske

No takers ?
Any chance this will be fixed (if need be) in the next release ?

dc42

Does M38.2 work properly now, and it is just M675 that doesn't?

What M675 command are you sending? Have you used the P parameter to specify that you are using a Z probe, and which one?

Yveske

@dc42 Yes m38.2 does work, but I would like to have a tool diameter agnostic homing using the hole in the XYZ probe.

dc42

And what M675 commands are you trying to use?

Yveske

@dc42
This is my probe macro

; Touch probe.g
; called to find workpiece bottom left corner via G38.2
;

; Display message without time-out and allow to position the bit
M291 T-1 S3 X1 Y1 Z1 P"Make sure the bit is positioned in the hole of the touch probe well beneath the top surface" R"Touch probe"

; Find center of cavity
M675 X R8 F100 P0                 ; Find center in X axis
M675 Y R8 F100 P0                 ; Find center in Y axis

; Set bit above center of probe
G0 Z15                            ; rapid move Z axis 15 mm
G0 X27 Y27                        ; rapid move X and Y axis to middle of probe

; Probe Z component
G38.2 Z-15 F100                   ; seek until the probe circuit is closed Z-axis -15 mm

; Return bit to center of hole
G0 Z15                            ; rapid move Z axis 15 mm
G0 X-27 Y-27                      ; rapid move X and Y axis to center of cavity
G0 Z-15                           ; rapid move Z axis -15 mm

G10 P0 L20 X0 Y0 Z10              ; store relative probe offset for coordinates system 0

dc42

Thanks. From your video, it looked as though the M675 X command worked but the M675 Y command did not stop when it should. Is that correct?

Can you confirm that you are running firmware 3.2.2 now?

Yveske

@dc42 Yes indeed. I haven't invested much time in it since, but it seems M675 in X does work and fails in Y. I'm running 3.2.2 now.

dc42

If you comment out the M675 X command in the macro, does the M675 Y command then work?

dc42

One more question: do you have deployprobe.g and retractprobe.g files, or not? I think I see a problem with the implementation of M575 when these files are present.

Yveske

@dc42

I don't have those present (see below).
I will try to reconnect everything this afternoon to answer your second question. I'm trying to build an enclosure...

H:\gcodes
H:\macros
H:\sys
H:\www
H:\System Volume Information\WPSettings.dat
H:\System Volume Information\IndexerVolumeGuid
H:\macros\Touch probe.g
H:\sys\bed.g
H:\sys\config.g
H:\sys\Duet3Firmware_MB6HC.bin
H:\sys\homeall.g
H:\sys\homex.g
H:\sys\homey.g
H:\sys\homez.g
H:\sys\pause.g
H:\sys\resume.g
H:\sys\sleep.g
H:\sys\stop.g
H:\sys\tfree0.g
H:\sys\Touch probe.g
H:\sys\tpost0.g
H:\sys\tpre0.g
H:\sys\config.g.bak
H:\sys\dwc-settings.json
H:\www\Duet2CombinedFirmware.bin
H:\www\Duet2Firmware_SBC.bin
H:\www\Duet2_SDiap32_Maestro.bin
H:\www\Duet2_SDiap32_WiFiEth.bin
H:\www\Duet3Firmware_EXP1XD.bin
H:\www\Duet3Firmware_EXP3HC.bin
H:\www\Duet3Firmware_MB6HC.bin
H:\www\Duet3Firmware_Mini5plus.uf2
H:\www\Duet3Firmware_TOOL1LC.bin
H:\www\Duet3_SDiap32_MB6HC.bin
H:\www\Duet3_SDiap32_Mini5plus.bin
H:\www\Duet3_SDiap_Mini5plus.bin
H:\www\DuetMaestroFirmware.bin
H:\www\DuetWiFiServer.bin
H:\www\favicon.ico.gz
H:\www\index.html.gz
H:\www\manifest.json.gz
H:\www\precache-manifest.08b4c61242ac3cb9e1bd2a96bd3aacb2.js.gz
H:\www\service-worker.js.gz
H:\www\css
H:\www\fonts
H:\www\img
H:\www\js
H:\www\precache-manifest.a1d0ef5757696b3d6a44992f8c30488d.js.gz
H:\www\css\app.54d98193.css.gz
H:\www\css\GCodeViewer.68d05d8a.css.gz
H:\www\css\HeightMap.389e8521.css.gz
H:\www\css\ObjectModelBrowser.c5e13b42.css.gz
H:\www\css\OnScreenKeyboard.578a974b.css.gz
H:\www\css\GCodeViewer.18c47076.css.gz
H:\www\css\HeightMap.5a0c6c12.css.gz
H:\www\css\ObjectModelBrowser.7385f747.css.gz
H:\www\css\OnScreenKeyboard.a9b1a06d.css.gz
H:\www\css\TouchJog.9db4823c.css.gz
H:\www\css\app.9ef74274.css.gz
H:\www\fonts\materialdesignicons-webfont.3d1f8fa2.eot.gz
H:\www\fonts\materialdesignicons-webfont.3e722fd5.ttf.gz
H:\www\fonts\materialdesignicons-webfont.4187121a.woff2
H:\www\fonts\materialdesignicons-webfont.4187121a.woff2.gz
H:\www\fonts\materialdesignicons-webfont.fec1b66a.woff
H:\www\fonts\materialdesignicons-webfont.fec1b66a.woff.gz
H:\www\img\icons
H:\www\img\icons\android-chrome-192x192.png.gz
H:\www\img\icons\android-chrome-512x512.png.gz
H:\www\img\icons\android-chrome-maskable-192x192.png.gz
H:\www\img\icons\android-chrome-maskable-512x512.png.gz
H:\www\img\icons\apple-touch-icon-120x120.png.gz
H:\www\img\icons\apple-touch-icon-152x152.png.gz
H:\www\img\icons\apple-touch-icon-180x180.png.gz
H:\www\img\icons\apple-touch-icon-60x60.png.gz
H:\www\img\icons\apple-touch-icon-76x76.png.gz
H:\www\img\icons\apple-touch-icon.png.gz
H:\www\img\icons\favicon-16x16.png.gz
H:\www\img\icons\favicon-32x32.png.gz
H:\www\img\icons\msapplication-icon-144x144.png.gz
H:\www\img\icons\mstile-150x150.png.gz
H:\www\img\icons\safari-pinned-tab.svg.gz
H:\www\js\app.f43f66da.js.gz
H:\www\js\app.f43f66da.js.map.gz
H:\www\js\GCodeViewer.928ca6b9.js.gz
H:\www\js\GCodeViewer.928ca6b9.js.map.gz
H:\www\js\HeightMap.7361cf24.js.gz
H:\www\js\HeightMap.7361cf24.js.map.gz
H:\www\js\ObjectModelBrowser.f722b29d.js.gz
H:\www\js\ObjectModelBrowser.f722b29d.js.map.gz
H:\www\js\OnScreenKeyboard.1f9c0f92.js.gz
H:\www\js\OnScreenKeyboard.1f9c0f92.js.map.gz
H:\www\js\TouchJog.a2011aaa.js.gz
H:\www\js\DRO.f8d0c566.js.gz
H:\www\js\ObjectModelBrowser.62b4acaf.js.map.gz
H:\www\js\ObjectModelBrowser.62b4acaf.js.gz
H:\www\js\OnScreenKeyboard.be1a1000.js.gz
H:\www\js\DRO.f8d0c566.js.map.gz
H:\www\js\OnScreenKeyboard.be1a1000.js.map.gz
H:\www\js\HeightMap.79dc5595.js.gz
H:\www\js\TouchJog.a2011aaa.js.map.gz
H:\www\js\GCodeViewer.32f07c79.js.gz
H:\www\js\HeightMap.79dc5595.js.map.gz
H:\www\js\GCodeViewer.32f07c79.js.map.gz
H:\www\js\app.bbd01205.js.gz
H:\www\js\app.bbd01205.js.map.gz

dc42

Thanks, I will also try to reproduce this issue.

dc42

I confirm that M675 does not work properly in any recent RRF3 firmware version. I am currently fixing it, in time for firmware 3.3beta3.

Yveske

@dc42 Thanks !
In my test both X and Y axis performs the same.
Both go in positive direction first, don't stop immediately but move the probe half a centimeter, change direction to never stop again...

I'm running with the new CNC interface. I installed it with the duet decoupled and didn't check. Now homing always goes in the wrong direction for Z. I changed M574 Z2 into Z1 and back

; Drives
M569 P0.0 S0                                ; physical drive 0.0 direction (0 = backwards, 1 = forwards (default 1))
M569 P0.1 S0                                ; physical drive 0.1 direction (0 = backwards, 1 = forwards (default 1))
M569 P0.2 S0                                ; physical drive 0.2 direction (0 = backwards, 1 = forwards (default 1))
M569 P0.3 S1                                ; physical drive 0.3 direction (0 = backwards, 1 = forwards (default 1))

; Endstops
M574 X1 S1 P"!io0.in"                       ; configure active-high endstop for low  end on X via pin io0.in
M574 Y1 S1 P"!io1.in+!io2.in"               ; configure active-high endstop for low  end on Y via pin io1.in
M574 Z2 S1 P"!io3.in"                       ; configure active-high endstop for high end on Z via pin io3.in

dc42

Please create a separate thread for the homing problem.