Duet 3 6HC with Openbuilds XYZ Probe

Yveske

@Phaedrux
Tried several times now, but M98 doesn't display much...

Phaedrux

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

@Phaedrux
Tried several times now, but M98 doesn't display much...

That's ok, it doesn't always. Any messages or errors that would be generated by the gcode in config.g normally get lost at bootup, so sending the command to load it as a macro will let any of those message be displayed. So no messages is a good thing.

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

Maybe interesting to note:
I'm using a Raspberry Pi 3B+ to run DWC with voltage supplied by the Duet, with normal PC monitor, keyboard and mouse connected to the Pi.

That's a risky proposition. It certainly wouldn't work well that way with a Pi4 due to its increased power draw. And even with the Pi3 I would be reluctant to run it with that many USB peripherals powered by the Pi USB ports. It may be prudent to power the Pi separately.

See this section and the one below it on electronics power consumption.
https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Hardware_Overview#Section_5V

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

RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)

It would be a good idea to update your firmware to 3.2 now that it's available. Lots of fixes for the SBC version. You should be able to update by running Sudo apt update followed by sudo apt upgrade.

https://github.com/Duet3D/RepRapFirmware/releases/tag/3.2

After that see if behaviour has changed. Other than that I'm not sure. I've moved this to the CNC forum as well for better visibility by someone more informed.

Yveske

@Phaedrux thanks for pointing me to the update

After the update it is a little bit better, but definitely not reliable yet.
See Duet3D XYZ Touch.mp4

It sometimes (like in the video) starts off in -X like it should, sometimes it starts going directly to +X. Sometimes it doesn't stop in X, but always fails in Y. Either way I have to hit the emergency stop to prevent it from killing yet another end stop.

Yveske

@Phaedrux

It also makes no difference powering the Pi or not.
It's a Pi 4 2 GB I'm using, the 3B+ resides in another project of mine.

Phaedrux

At this point I would ask if you could test in standalone mode without the Pi. This will help identify if it's an issue with RRF or DSF.

https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Running_in_standalone_mode

You can download the contents of your system tab and macros and use a separate SD card. That SD card will need the DWC files in the /www folder as well. Disconnect the Pi, connect network to the duet, put the SD card into the duet. More details in link above.

Yveske

@Phaedrux
Couldn't get it to work yet, didn't have much time today, will try again tomorrow

chrishamm

I doubt it will make a difference to run the Duet in standalone mode in this case.

Is it right that your touch probe is configured as the Z probe? If yes, you should be able to check if the Z probe value in DWC goes from 0 to 1000 whenever it lights up. If it doesn't, I suspect you have a bad contact somewhere.

Yveske

@chrishamm
The touch probe does respond to being activated, it lights up and the value on the screen goes to 1000. In the video you can see that probing even works (but not always) on the X-axis, it does always fail on the Y-axis though...

Will try to get my Duet to boot in standalone mode today. Due to circumstances, my Duet was left boxed for over a year and a half, so I don't have the dual boot SD card. I also don't have the PanelDue, so I can't see what it does or doesn't do on boot... That's why I went with the Pi to connect monitor, mouse and keyboard.

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?