@Nightowl thank you for the reply.

What I want todo is basically set a macro that will take the bit over to the tool length probe location and measure the tool length and set the offset so that Z0 is the top of the spoilboard.
Currently when I probe using the tool length probe it sets an offset between the current Z and the probed.
I am not sure how or where to tell it how far the probe switch is from the top of the spoilboard and I think that’s my issue.
The job setup and stock settings are fine.

@Nightowl thanks for the reply.

I am using a Duet3 Mini+ with version 3.4.5 in SBC mode.

When I run job with the RepRap post in Fusion 360 jobs work okay but I am trying to understand what is happening in Carbide Create 6.52 that is causing the cuts into the material.

@baird1fa said in help with z touch off macro:

G38.2

Do you mind sharing what your final config or setup for this was?

@Nightowl said in Resume on power failure - CNC:

Just out of curiosity, am I correct in thinking the pause.g file is relevant to this process, and that the resume.g file can be used after powering down and restarting the machine, or have I got my wires crissed?

The pause.g and resume.g files are not relevant to resume after power fail. However, any time you pause a print, resurrect.g gets written. This is to allow you to pause the job and then power down, knowing that you can resume it if you have set up resurrect-prologue.g appropriately. This works for 3D printing; I don't know whether it is appropriate for CNC applications.

@Nightowl EXCELLENT!!!

@markz its alive, Thank you for your help and advice.

https://youtube.com/shorts/x23cIedPRH4?feature=share

Jesse

@hackinistrator Ahh right. At this point it depends if you have the time to program a devicenet master onto board with CAN support.

It looks like there is a developer kit here:
https://pyramidsolutions.com/products/netstax/protocol-stack-source-code/dmdk/

@YYCSparks said in Silly homing problem:

it was set wrong causing the Z axis to see the probe as tripped and wouldn’t home.

That'll do it 😁

@paolozampini1973
I think what that means is the memory within the Duet2 doesn't have adequate capacity to store the additional code required.

@baird1fa on tablet/phone, try:

http://cncrouter.local/

Ian

Never mind, I’m sorted ✅

@jay_s_uk
Yeah, I kind of get that. I had a bit of an issue with the manufacturer of my previous machine on this subject, but they believed it was perfectly acceptable to do this. What made matters worse was their machine barrelled forward to the front edge after homing, to prompt for a tool. I thought that was more dangerous.

I probably won’t do this 👍🤔

@phomann the first beta of 3.5b1 has just come out. I expect it to be a while before 3.5 goes stable

@T3P3Tony

The object model was the answer. I ended up having a short on the signal wire and identified it because you helped me locate the "Sensors" "GPIN" correctly.

Thanks!

@sinned6915 Hi, which connections / pins have you used to connect the encoder to the paneldue? Thanks in advance.

There might be a safety issue here, in that keeping the spindle running until it moves to the safe place might prevent the bit from snapping (or worse, damaging the milling motor) if it were to hit the stock.

This is my pause.g file (it includes triggering a LED to show it's in Pause mode and a method of storing the spindle speed on resume*):

; pause.g M42 P8 S0 ; pause/resume LED off set global.PausePress = !global.PausePress ; toggle the value from whatever it was before set global.savedSpindleSpeed = spindles[0].active ; sets the global variable echo "Spindle speed saved at ", {global.savedSpindleSpeed}, "RPM" ; shows saved spindle speed in the Console G1 Z{max(move.axes[2].userPosition+5,move.axes[2].max-5)} F2400 ; move the Z axis to a safe height G0 X273.5 Y560 ; move XY to a safe place M5 ; turn the spindle off

...and the respective resume.g (with a bit of tool confirmation, but some of this might be spurious - but it works!) but note the indents are critical:

; resume.g M42 P8 S1 ; pause/resume LED off set global.PausePress = !global.PausePress ; toggle the value from whatever it was before if state.currentTool =-1 echo "No tool active. Selecting tool zero" T0 ; select tool zero if state.currentTool >= 0 echo "Spindle state on tool ", state.currentTool, " is ", spindles[state.currentTool].state if {state.currentTool >= 0} & {tools[state.currentTool].spindleRpm >= 0} M3 S{global.savedSpindleSpeed} ; resume saved spindle speed G4 S1 ; wait 1 second to allow the spindle to spin up echo "Spindle speed resumed at " ^ {global.savedSpindleSpeed} ^ "RPM" ; this should show that the setting was successful G0 R1 X0 Y0 ; move X and Y back to saved work XY location G1 R1 Z0 F240 ; move Z slowly down to saved work Z location

*I'm happy to provide the configuration lines from the config.g, stop.g and trigger2.g files, if you want to incorporate those features, too?

Once you've moved to the exact X, Y and Z starting point of the cut (depending on how you've set this up in the project software - Vectric, Fusion, etc. - and the thickness of the material), clicking the Set Work XYZ in CNC mode.

Screenshot 2022-12-09 at 08.15.47.png