Declimer: its not quite Question / need for help topic. Mostly its for sharing info

Im in the middle of conversion of my cnc into ATC cnc,
and probing is one of the feature I start the ATC at the first place

Im using "JINNI Post for RepRap w/Tool Change & Backlash Compensator" post processor from https://github.com/BruceRoyce/UltimateRepRapPost as a start point, and modify it to my need

In additional to some general changes, like:

• start script
• end script
• tool config script

Im currently working on probing.
Idea is the following: use a "standard" RENISHAW gcoding / post processor parts and than workaround it through custom Gcodes + scripts

https://quagmirerepair.com/files/mazak/Spindle_Probe_Manual.pdf

example:

F360 probing-z
would be converted to

G54
G0 X0 Y0
G0 Z25
G17
;CYCLETYPE PROBING-Z
;CYCLETYPE PROBING-Z A1 NEGATIVEA2 NEGATIVE PC 4
G65 P9810 C3 Z1.5 F300
G65 P9811 A3 Z-2.5 Q10 S1
G80
G0 X0 Y0 Z25

Then, I'll create
g65.g custom gcode, which would recognize
P9810 as a safe move (something like /macros/probing/p9810.g)
and
P9811 as a signle surface probing

With that approach hopfully we would be able to reuse all /macros/probing/p*

Current points I have to keep in mind:

• speed of executing macros from macros (i find some unpredicted delays 1-2 seconds from time to time)
• needs of m400 if I want to use object model position reading
• no array (hopefully till 3.5) to store all the tool data. workarounded by stored_on_flash_array

Any ideas/thoughts would be appriciated

To anyone like me stacked with SBC and 3.5
my way of resotoring stable version (after changing /etc/apt. ... to stable)

sudo apt install duetcontrolserver/stable duetpimanagementplugin/stable duetpluginservice/stable duetsd/stable duetsoftwareframework/stable duettools/stable duetwebcontrol/stable duetwebserver/stable reprapfirmware/stable duetruntime/stable

If it still relevant,
m92 e{move.extruders[0].stepsPerMm}:1333 works in 3.xx

@dc42 set it to preorder somethere %-) willing to put some buks there

@dc42 thanks for the reply
May i signed for alpha/beta for 6xd
I have all the experience with d2/d3 and really wanna try it. Willing to test only recommended cl drivers
Dont want put 4x1hcl and waist all internal ports

My current WIP project
printer: east3d gecko
board: duet
extruder: nimble

suppose to work with 4-6 heads (at least I hope it will)

videos
unload
load

Currently its all printed (ABS/PETG)
waiting for a steel locations pins
and after finish all the beta - will cnc both plates

After that - duet per tool config offset

Currently its kind of loosy, BUT, because of that and the magnets - it fit exact the same position every time %-)

To anyone like me stacked with SBC and 3.5
my way of resotoring stable version (after changing /etc/apt. ... to stable)

sudo apt install duetcontrolserver/stable duetpimanagementplugin/stable duetpluginservice/stable duetsd/stable duetsoftwareframework/stable duettools/stable duetwebcontrol/stable duetwebserver/stable reprapfirmware/stable duetruntime/stable

@dc42
I have multiple Y axis, leveled by multiple end-stops
but Z is single axis

It's a CNC mode

@dc42
#1 - I had multiple lines like
if exists(param.X)
set var.dirX = param.X
and they works before 3.5b1

in 3.5b1 I have to switch to
if {exists(param.X)}
set var.dirX = param.X

I remeber that it was mentioned somethere, but it was not emphisized (ASFAIK) as breaking changes in 3.5b1

Few issues on CNC / d3-6xd / SBC
Switched back to 3.4.5 after a broken bit (

1. it starts enforcing {} rules in IF condition (I know that its in doc somethere)

2. 38.2 38.3 return non zero result quite often. Wich may lead to broken probe. (Im using same probing script for few months on 3.4.5 without any false positive. Only overprotective movement saved me that time)

3. M291 S2 in a programm does not continue by M292 P0/M292/pressing OK. After the widown closed it still in processing state with no window/reaction to M292. M292 P0/M292/pressing OK works fine with M291 S3.

4. Unknown movement issue. On a test milling it hangs on some Z, one time it just hangs there, one times it hangs on Z-3.708 (I see that number in GUI/object model (pendant) ) and continue to press downards with slow pace (probably with the same of the last command) without any update to GUI/object model, nor getting next command in line (gcode attached). Was stopped by pause button (GUI).

Last one is the most disturbing

Gcode: VertAluDrill.cnc.gcode

Create a separate ticket. Movement issue + some minors

Declimer: its not quite Question / need for help topic. Mostly its for sharing info

Im in the middle of conversion of my cnc into ATC cnc,
and probing is one of the feature I start the ATC at the first place

Im using "JINNI Post for RepRap w/Tool Change & Backlash Compensator" post processor from https://github.com/BruceRoyce/UltimateRepRapPost as a start point, and modify it to my need

In additional to some general changes, like:

• start script
• end script
• tool config script

Im currently working on probing.
Idea is the following: use a "standard" RENISHAW gcoding / post processor parts and than workaround it through custom Gcodes + scripts

https://quagmirerepair.com/files/mazak/Spindle_Probe_Manual.pdf

example:

F360 probing-z
would be converted to

G54
G0 X0 Y0
G0 Z25
G17
;CYCLETYPE PROBING-Z
;CYCLETYPE PROBING-Z A1 NEGATIVEA2 NEGATIVE PC 4
G65 P9810 C3 Z1.5 F300
G65 P9811 A3 Z-2.5 Q10 S1
G80
G0 X0 Y0 Z25

Then, I'll create
g65.g custom gcode, which would recognize
P9810 as a safe move (something like /macros/probing/p9810.g)
and
P9811 as a signle surface probing

With that approach hopfully we would be able to reuse all /macros/probing/p*

Current points I have to keep in mind:

• speed of executing macros from macros (i find some unpredicted delays 1-2 seconds from time to time)
• needs of m400 if I want to use object model position reading
• no array (hopefully till 3.5) to store all the tool data. workarounded by stored_on_flash_array

Any ideas/thoughts would be appriciated

@Jengland I do have it
I use the following method:

1. I set the machine zero with setter and spindle without the tool / collet / nut
2. I install the tool
3. I test the tool and set tool height

If I change the tool, I just redo p2 and p3

It does require additional step on the machine enable (p1), but It happend that my setter is +- 0.01, and Z endstop about +- 0.1-0.3

My script

M208 Z8 S1

G53 G90 G0 X321.0 Y0.0

if !exists(global.MGlobalsLoaded)
	M98 P"/macros/Measuring/globals.g"
	
;M558 P1 C"io7.in" H23.258 F{global.MSpeedFast,global.MSpeedLow}	

M558 F{global.MSpeedFast} K1

M300 S300 P1000
if state.currentTool = -1
    M291 S0 T5 P"Probing the spindle zero height"
else
	if global.HSpindle <= -9999
		abort S"Please set the spindle zero first"
	M291 S0 T5 P"Probing the tool " ^ state.currentTool ^" offset"


M558 F{global.MSpeedFast} K1

G30 S-1 K1
G53 G1 Z{move.axes[2].machinePosition+2} H4

M558 F{global.MSpeedLow} K1
G30 S-1 K1


if state.currentTool = -1
  G92 Z{sensors.probes[1].diveHeight}  
  set global.HSpindle = sensors.probes[1].diveHeight
  set global.MResultZ = sensors.probes[1].diveHeight
  M208 Z30 S1
else
	M400
	echo "Probe triggered at Z:" ^ move.axes[2].machinePosition ^" Sensor height: " ^ sensors.probes[1].diveHeight
	var ToolLen = move.axes[2].machinePosition - sensors.probes[1].diveHeight
	set global.MResultZ = - var.ToolLen
	M98 P"/sys/tool_set.g" T{state.currentTool} O{global.MResultZ}
	
	; Set soft limit to 0 plane
	M208 Z{var.ToolLen} S1
	


M558 F{global.MSpeedFast} K1
G53 G1 Z{move.axes[2].max - 10} H4

Hi,
I have a complex (CNC) wiring with multiple layers of E-Stops
And I have a question, does duet3 (6xd, 3hc) can be set up as an NC relay in E-Stop line
I thought of opto out, but not sure if Im in a right direction

I have not seen any issue with a printer (and ASFAIK it utilizes g2/3 at some points)
but as you can see from the pictures with CNC it looks different

It may be still post processor issue, but g2/g3 code looks ok-ish

@3dpmicro Hi, not shure I follow
I attached c-inner_failed (which is with arc, g2/g3) and c-inner (which is g0/g1 only)