I have some problem with the printer I am building and I hope that

I have some problem with the printer I am building and I hope that you could give some advice what could be wrong. The printer is an CoreXY with a bowden feed 1.75 mm filament. I have problems in the outer perimeter, there is no blob but the opposite, a small ridge inwards. I have tried many different settings for the retract but I can not seem to get rid of the problem, any that got some thougts?

There’s two things that could be helpful in solving this issue: 1) What slicer are you using, and 2) What speeds are you printing at?

Slic3r V 1.1.7, speed do not make any change of the effect.

Maybe it could be the belt tension, but the tension seems to be equal on the two belts sinc the axis are really 90 degrees when printing an angle with 200 mm sides, also the circles are not oval and from what I knew they should be oval if the tension differs from belt to belt.

slic3r sometimes leaves a tiny part of the top layer, it enrages me also. that groove looks pretty dirt tho. you can randomise starting points but that would probably just move the groves alround the part and look worse as its ment to prevent build up of “blobs” up one edge. Id try a diff version of slic3r and check your hardware for loose things.

belt tension - if it was slipping the other layers wouldnt line up and your object would lean

good luck

Try using a negative number in if a setting for when extrusion should restart after retraction.

@Martin_Bondeus show them those videos you linked me. I couldn’t figure out why it crossed over to the other perimeter quickly then came back. Also I cannot tell from my phone screen if where it does the cross over is where that fold occurred.

The video shows the printing, the strange jump to the other side is for half of the layers, the layers above does not have theese jumps but it does not affect the problem, it is still there as you can see on the photo:
Video: https://drive.google.com/file/d/0B7A1MEUY39HCVnZfZkJsckhxMGM/edit?usp=sharing

Do you get this artefact if you print something in single walled vase mode? If you do, you should be able to say for sure it’s a hardware issue and not something in software/slicing.

It looks like the pause is at the outermost point of the curve, which makes me think it’s to do with your gantry sticking somehow on the direction change. But I could be seeing that wrong since I’m watching on my phone at the moment.

His vase mode results in perfect prints.

Well that’s weird. Really weird.

I now think that jump to the other side pulls the OD with it. One test would be print outside to inside versus inside to outside.

Try a different file

I think slic3r allows you to randomise your start and end point for each layer. You’ll still have the problem, but it won’t be as noticeable.

Will do more tests this evening, yes Slic3r has the option to randomize the start points but then it looks really horrible.

I had same kind issues , I increased z axis speed .

Wow! That is a serious Gcode stumble.
@Eclsnowman slice the file with your S3D. Let him run that. I don’t mind slicing either. This might rule out a start/stop per layer Gcode bug.
Another option, post the Gcode. Some can dissect on here. This is a simple shape so should be noticeable at layer change.
Going to have to shoot down hardware issues on this one.

@Brandon_Satterfield @Martin_Bondeus mind linking the gcode and stl for troubleshooting?

On a side not Martin is doing some cool extruder drive work I hadn’t seen before and his new e3d duct is very cool ( would be even better with a centrifugal fan for smaller profile, though those fans don’t pwm well).

I am starting to suspect my Z axis, i am now using two M5 x0.8 rods, I have TR10x3 trapezoidal spindles but I had not had time to install it yet, seems that there will be some work in the lathe tomorrow and rebuilding of the Z-stage coming up…
Thanks for your fantastic help and support! The extruder is working flawless and has a big Grip, the cad design needs some work thoug, are you interested to help Eric Lien?

@Martin_Bondeus sure.