What do I plug in to get xyz probe working?

JoergS5

@chrishornby yes, the endstops are active for all tools. The tools have XYZ offsets, so they can be at different positions. But corrected by this offest, they are all be defined by the same endstops.

The homing defines where the XYZ movement is at the XYZ endstop (high or low). The printer defines this as the end of the possible movement for most commands. If you try to move behind the endstop, you'll get an error message and the movement is canceled. There are a few commands to ignore the endstops (with the danger to create a crash), but the "normal" movement commands like G0 and G1 behave so.

If you define the Z axis endstop, you can use it to define Z=0. You can use the router as your probe, so you don't need to change from probe to router. This may not be possible because some routers have a peak, this will be in the way, so you may need to define it as tool and change the Z value of the tool properties. The probe is mainly used if you make mash compensation, ie probing multiple points on the bed to correct the 3D print, so the first layer's adhesive is best (unevenness of bed is corrected). This is not needed in CNC IMHO.

chrishornby

Thanks, slowly getting there. Guess I need to understand the G codes and it is a steep learning curve.

JoergS5

@chrishornby this is true. If you want to learn, a good method is to follow the threads and the solutions of config problems.

chrishornby

Looks like I have it, I need to add the HI to any G1 command that is looking for an end stop command to make it trigger.
Like G1 H1 X50

Is that right?

JoergS5

@chrishornby Yes, H1 sets to the M208 limit. I would make X much bigger, because it will be stopped at the endstop anyway and you don't know where you start. Make X bigger than the maximal possible movement.
In most cases there is one fast G1 H1 to the endstop (F high value), than a bit back G1 without H, than second G1 H1 movement slowly for higher precision. Just check some examples in the documentation of printer types.

chrishornby

OK thanks got it
Could you tell me what the parameters in this command refer to:
M585 Z50 E2 L0 F500 S1

According to the wiki
Parameter must be only one of
Xnnn
Y-nnn
Znnn

JoergS5

@chrishornby M585 is for getting the tool's offset by moving against the endstop. You can only run and get value for one axis with a M585, but you can run it three times with the different axes. M585 was the preferred method of the thread I mentioned above.

chrishornby

I guess I just need to mark solved and go away and weep with frustration. I know the answers are there somewhere if you know what question to ask. All I wanted to know was what E0 L0 and S1 refer to in that command. I think I can work out the others.

JoergS5

@chrishornby I would not do that. You talked only to me and opened the thread yesterday. There are CNC specialists out there who may be on their weekend trip and answer you all your questions on monday
Hope you get your open answers. See you!

M585 parameters are explained here:
https://duet3d.dozuki.com/Wiki/Gcode#Section_M585_Probe_Tool
E0 => not supported in RRF3
L0 => not supported in RRF3
S1 => S=1 means go backwards (towards the axis minimum)

chrishornby

@JoergS5 Sorry if I sound frustrated, but I have been doing 3d printers for many years, built a few and got lots of experience with Marlin and smoothie. This is my first experience with CNC and Reprap coding and it is doing my head in. Apologies all round.

JoergS5

@chrishornby CNC is very complex, you've only just begun! Reprap is complicated because the transition from RRF2 to RRF3 and some changed G-Code and their parameters. I am sure you'll manage it when you think a bit about it.

chrishornby

Yes I am sure I will, Thank you so much for all your help. I have decided that I will do my own macro from scratch rather than take the quickie (not!) route by shoe horning someone else's code into the mix.
Thanks so much !

JoergS5

@chrishornby said in What do I plug in to get xyz probe working?:

I have decided that I will do my own macro from scratch

that's a very good decision! So you understand what your macro does to the detail. Good luck!

I like Duet especially because it is possible to test G-Code commands on the fly by putting it in the DWC field and see the result.

chrishornby

DWC Field?? (I struggle with acronyms)
Is that the field in the UI where you can send a G code?

JoergS5

@chrishornby yes, DWC is the browser program, Duet Web Control.

chrishornby

Thanks!!

rzi

I'm having a similar issue. I got a Duet2 up and running on my old machine. And a Duet3 on my new machine and I want to run a similar set up. But I can't for my life get the xyz probe to work. Did you find the answer?

Best regards
Rickard

dc42

@rzi said in What do I plug in to get xyz probe working?:

I'm having a similar issue. I got a Duet2 up and running on my old machine. And a Duet3 on my new machine and I want to run a similar set up. But I can't for my life get the xyz probe to work. Did you find the answer?

Best regards
Rickard

Please start a new thread, post your config.g file, and tell us what probe type you are using.

rzi

@dc42 I decided to use G38.2 and it was straight forward.

onescentpro

@chrishornby I have the Duet3d board and purchased the xyz touch probe you show in your picture. What terminal on the Duet does this plug into?