offset y layer consistent & repeatable

[stewart]

I have a simple model that I've tried to print a couple of times. On the 4th layer, the y axis shifts as if it's missing a move. The gcode is correct, so it's clearly something in the way the printer is interpreting it (or dropping instructions). Has anyone had a similar experience or found a workaround?

[Tinkerer]

In the first picture I can see a shift in layer 7.

If that always happens at the same height, with the same amount of offset, that might be a mechanical thing.


What I know from my own experience with the N2:
- the stepper motor drivers can be causing shifts/lost steps
- the mechanical construction of the N2 is prone to misalignments and consequent errors
- the support will always assume it is a nozzle hit;-)

[stewart]

It hasn't happened in any other models. Just this one. So it's not mechanical at that Z offset. It's likely a software skip. Thus the sample file that someone else should be able to repeat (support?) on their N2 ...

[Tinkerer]

My N2 would not be a good reference here, since it is buggy as hell...

[Michael.P@Raise3D]

Hi Stewart,

If it is on the same model every time you print but not on any other models then it might just be a software hiccup. Try reslicing the model, I tend to give the part an angle of 15* in x/y to change the pattern of the slice. In the past this helped remove the hiccup in the slice.

@Tinkerer, come on man, we dont always assume it is a nozzle hit on the supports!

[Tinkerer]

Michael,
I apologize for my grim sense of humor;-)

[stewart]

Hi Stewart,

If it is on the same model every time you print but not on any other models then it might just be a software hiccup. Try reslicing the model, I tend to give the part an angle of 15* in x/y to change the pattern of the slice. In the past this helped remove the hiccup in the slice.

@Tinkerer, come on man, we dont always assume it is a nozzle hit on the supports!

Yes, it is a software bug *in the printer*. I've resliced it with different settings and it works. The gcode generated both times was fine.

[Michael.P@Raise3D]

All good Stewart, lets keep the good prints rolling. If you find anything else along those lines that can shed some more light on the issue from before please update us.

[stewart]

All good Stewart, lets keep the good prints rolling. If you find anything else along those lines that can shed some more light on the issue from before please update us.

I would like it if you tried this on one of your printers. It should fail early in the print (per the pics). Then your dev team would have a bug that's easily reproducible.

[Michael.P@Raise3D]

Sounds good, toss me a file at me email michael.p@raise3d.com

[stewart]

Sounds good, toss me a file at me email michael.p@raise3d.com

It's attached to my first post