Centroid Community CNC Support Forum

Hello,

Could you try running this version of the file that is attached.

Allin1Chris wrote: ↑Mon Mar 31, 2025 3:38 pm Hello,

Could you try running this version of the file that is attached.

I’m working a 12-12 shift today so I won’t be able to do that until tomorrow but I’m assuming this is just the laser gcode and does not do anything about the y delay in 5.3?

Onawa220 wrote: ↑Mon Mar 31, 2025 4:25 pm I’m working a 12-12 shift today so I won’t be able to do that until tomorrow but I’m assuming this is just the laser gcode and does not do anything about the y delay in 5.3?

Correct i do not think this will do anything to the delay, still looking further into that. Provided G-Code should remove the "long" lines produced by the Y-Axis file however.

Allin1Chris wrote: ↑Mon Mar 31, 2025 4:48 pm

Onawa220 wrote: ↑Mon Mar 31, 2025 4:25 pm I’m working a 12-12 shift today so I won’t be able to do that until tomorrow but I’m assuming this is just the laser gcode and does not do anything about the y delay in 5.3?

Correct i do not think this will do anything to the delay, still looking further into that. Provided G-Code should remove the "long" lines produced by the Y-Axis file however.

Thank you. I will run that first thing tomorrow.

Now we just need to Parameter 42x that adjusts the Y delay

It’s weird it was pretty darn close in 5.2 with no adjustments and in 5.3 it needs then. I do like that I was able to fine tune the X delay more than it was before. Until it’s fixed I went back to 5.2 though.

Onawa220 wrote: ↑Mon Mar 31, 2025 4:55 pm
Thank you. I will run that first thing tomorrow.

Now we just need to Parameter 42x that adjusts the Y delay

After looking into it more, The Change in the Y ZigZag file may correct the issues with the delay for Y-Axis.

Allin1Chris wrote: ↑Tue Apr 01, 2025 11:07 am

Onawa220 wrote: ↑Mon Mar 31, 2025 4:55 pm
Thank you. I will run that first thing tomorrow.

Now we just need to Parameter 42x that adjusts the Y delay

After looking into it more, The Change in the Y ZigZag file may correct the issues with the delay for Y-Axis.

That fixed it! Thank you!

What was in the Y file that would have caused it to ignore the delay fix in P424?

Ran it in 5.2 1st and it looked great. No burn lines from not turning off between firing.



Then swapped back to 5.3 and it looks good too!



I still need to fine tune it. This was at 12ms. I'm assuming I can do 10th and 100th too?

I tried doing 12.X and it doesn't allow that which makes sense since it is already in miliseconds.

I did find that I can get one axis or the other dialed in but not both.

at 14ms my X is dead on



but my Y is not



Again no backlash on either axis so I don't want to artificially fix it using the lash compensation only to have that mess me up with using the router.

Is there a possibility of making each axis tunable independently ?

Onawa220 wrote: ↑Tue Apr 01, 2025 12:02 pm

Allin1Chris wrote: ↑Tue Apr 01, 2025 11:07 am

Onawa220 wrote: ↑Mon Mar 31, 2025 4:55 pm
Thank you. I will run that first thing tomorrow.

Now we just need to Parameter 42x that adjusts the Y delay

After looking into it more, The Change in the Y ZigZag file may correct the issues with the delay for Y-Axis.

That fixed it! Thank you!

What was in the Y file that would have caused it to ignore the delay fix in P424?

Ran it in 5.2 1st and it looked great. No burn lines from not turning off between firing.

Then swapped back to 5.3 and it looks good too!

I still need to fine tune it. This was at 12ms. I'm assuming I can do 10th and 100th too?

Hello,

The Y ZigZag file was updated to alternate between S0 and S1000 rather than S1 and S1000. These were the same commanded speeds from the X ZigZag file, which would explain why you were only running into issues with Y and not X.

P424 currently only applies the delay when alternating between a zero and non-zero spindle speed. This will need to be fixed to avoid issues like this in the future.

Thank you,
Michael