Losing steps

[Edendale]

[Edendale]

Hi Doddy, I might be wrong about it starting again at the same place it’s hard to tell,

[Doddy]

Hi, could you post the g-code as a text-file attachment? (you might need to rename the extension to .txt) The point was to go back to your opening post on this thread to understand if the increasing offset is somehow in the g-code. For that, I/we'd need to look at the first layer and successive layer (differentiated by the plunge-depth on Z) to understand if the resulting displacements in Y were being applied in the g-code... so clearly we need substantial parts of g-code to realise that. Plus, the data reduction that is required is far easier in a macro-supported text editor (or even Excel!), certainly not using an image from a screen shot. HOWEVER, what pushed me to ask for that was your statement that I interpreted as the starting XY on each layer was correct, but the resulting error in Y existed at the end of the layer - as your original analysis concludes that's only really feasible back at the computer/controller/g-code end. But, you've cast doubt on that.

BUT... you could do the donkey work yourself - use an online g-code viewer to confirm that your G-Code is correct (not introducing the Y offsets). If you can confirm that it's largely takes the uncertainty around you situation away, and I'd be more convinced that you're losing steps in the electronics/machine than in the controller. That would NOT be the case if the start-position was correctly recovered on each layer (if the error is in the machine or electronics the offer is cumulative... only recovering if the error cancels itself out).

Every thought I have is to simplify the problem - and for that I'd ask if you've tried to revert to cutting a simple repeatable shape - cut a rectangle 0.5mm deep in a bit of scrap a thoasand times - the thousandth pass should cut the same path as the first. That tells you if the machine is losing steps. ... or the other advice from others earlier in the thread - all good.

[Edendale]

thankyou Doddy for your time on my problem, i have run the program again and it reverts back to the starting point, i will try and send you the code, regards mike.3D Roughing pike.txt