@selva_tvi

Hi selva, I'm working on this today. I just deleted another post trying to find out how to change the error pin pull up/down. Turns out there is a a spot to bridge it on the board itself. I will let you know how it goes. I am pretty close to finishing if this works.

Screenshot 2023-02-12 at 16.07.45.png

@jmorganmkm I found this item in the bug fix list in version 3.4.0 at https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-340 (search for CNC to find it):

In CNC and laser mode it is permitted to omit G0/G1 at the start of a line of GCode and just provide parameters, provided that the previous command was G0 or G1. However, only parameter letters that were present in that previous G0/G1 command were recognised.

So this is a bug in 3.3 which is fixed in 3.4.

@Jack_kelley I know this is a bit old, but did you ever find a solution for the random Sxxxx Gcode?

Or are you using another way to control your CNC now?

--
Lars

@Stef64Fr good luck to find the reason. I hope you'not damaged your board, you can make M122 to check the driver status with steppers where you know they work. I've no other idea what you can check.

@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 👍🤔