DaHai8

It started out OK. I'll try reducing it by 10% until it either stop extruding or prints properly. I just don't understand why its doing it...humpf

This is really P***ing me off! :angry: I found my "Tune" menu. It only appears when the printer is actively processing a gcode file. In it are "Flow" and "Flow 0" setting. I tried both. Neither do a Damn thing - no matter what value I set it too. There's no documentation I could find on either as well. Argh. Side Note: My Tune menu also has a "Change Filament" option. So I tried that. Big Mistake! The print-head raised off the object and then moved to home, but totally ignored the 0-stop switch and proceeded to grind the motor until I quickly powered it off. More Argh. So, I redid my Perl Code for the 2.65x E rate multiplier and truncated the values to 5 decimal places. And that worked!!! Sort of... The first couple of layers printed fine, but then I noticed it was overflowing - badly (see attached pic). Checking the values, they are all 2.65 times greater than your gcode file - even to the end: Original: G1 X160.916 Y67.960 E62.02322 G1 X159.924 Y68.193 E62.02960 G1 X158.909 Y68.348 E62.03604 G1 X157.896 Y68.427 E62.04241 G0 F11400.00000 X157.869 Y67.626 M107 M104 S0 ;extruder heater off Modified: G1 X160.916 Y67.960 E164.36231 G1 X159.924 Y68.193 E164.37922 G1 X158.909 Y68.348 E164.39629 G1 X157.896 Y68.427 E164.41317 G0 F11400.00000 X157.869 Y67.626 M107 M104 S0 ;extruder heater off So I'm still scratching my head on what's going wrong... :( P.S. Just so you know I'm noting wasting both our times with a crappy printer. Mine is pretty nice and prints well at .1mm. Here's an example at .1mm and 7cm tall:

I shall try again!

Well, here's where I get to show how smart (or stupid) I am. Generated your object at .1mm and compare my gcode to yours. Of course, the coordinates are not the same, but at least the relative offsets and distances would be, right? Nope. How about the relative Extrusion rates per 1 unit distance? Those should be constant, right? Nope. How about relative differences between Extrusion rates per 1 unit distance between your gcode and mine? Should be consistant? Nope. Argh. Nothing is making sense. This appears to be un-testable by me. Sorry. I've included the spreadsheet along with my gcode if you want to have a go at it, but I understand if you want to move on and find another, more qualified tester. http://bitman.org/AA3_Test.gcode http://bitman.org/Comparison.ods

Here some things to check (if it were me): Is it a true solid? Check it in Meshmixer or Sketchup's Solid Inspector. How thick are the walls? Are they as thin or thinner that your print head nozzle? If you turn on X-Ray mode in Cura, do you see any Red areas? These indicate issues with your model. Do you have another slicer to try? That might help narrow down the issue. Hope this helps.

Not sure what firmware I'm running. The display only says "Mendel Ready" and none of the other screens say anything about the firmware type or version. I'll go back the to seller and see if they know. It is a .4mm nozzle. And I have it set to that in Cura, along with 1.75mm filament. I got no "Flow" menu item either. Nothing in the "Prepare" or "Control" menus have any kinda of flow setting. On the Main screen I have "Fr", but setting that just makes the print head move faster (same as with Gx Fnnn.nnnn gcode). I think the M211 S293 didn't do anything because the flow rate of the filament out of the nozzle was unchanged, ie: near to nothing. I agree with your math. I checked that earlier. I've printed a few items between trying your gcode files and everything is working fine. No clogs. I did change the temps in your files from the start to match my regular print temps: 55c bed and 215c nozzle. Post the STL of your test cylinder and I'll load into Cura and generate at .1mm res gcode file like yours. Then I'll compare my generated E rates against your's and see what multiplier is being used. Then I can update my Perl script to adjust the Extrusion rate to what my printer requires. Thanks!

Clearly, I don't know what I'm doing. This, from you gcode had no effect: M221 S293 Perhaps my printer doesn't allow values greater than 100%. So did a quick search/replace of all the G1/G0 F values to numbers 2.93 times more. That resulted in some hilarity as the print head raced around the print bed. It was then I realized its the E values that need changing. So I wrote a Perl script to multiply all the G1/G0 E values to 2.93 x greater. It fed a bit more filament, but still no enough to stick or even make a line. I dunno. Like I said, clearly I don't know what I'm doing. Would it be possible to send me the Cura Engine? Would I be able to replace my 2.1.2 Cura engine with it in the folder? I really want this to work. I HATE those Frankenstein Zipper lines!

Ok, tried it but can't print it. The main problem is the feed rates in your gcode are about half of what my printer requires. So only a small amount of filament comes out and nothing sticks. I think your using 3mm dia filament. I'm using 1.75mm Also, you X location is right at the edge of my printer's printable area (~175mm). Perhaps if you moved the item more to the center of the bed? Thanks.

Nothing to talk about until you try it!

Results like these take days, not hours. Please be patient. We have lives too. I too hate perimeter seams and would love to minimize them. I for one will try this out if possible and get back to you, but within days...not hours.

If you created your model in Sketchup, you can download the Solid Inspector extension. It will tell you if you have holes in your mesh, stray edges or internal surfaces - any of which could cause this issue.

I have a 5yr old Asus Zenbook and Cura 2.x is only slightly slower on it than 15.x The slicing is much better and the screen updates and menu load up just as fast. STL files load in just as fast and the screen refreshes are only slightly slower (even in 'Layers' mode) than 15.x. As as result, I use Cura 2.x almost exclusively now. So, no, I don't find it to be completely unusable at all. I think its very responsive, powerful and easy to use. I'm afraid I don't know much about Macs, but I would suggest looking at your video drivers to ensure that are up-to-date. Is there a memory issue? Do you have multiple apps running? Can you free up more RAM? I wish I could help more.

Try running Cura as Administrator: Right click on the Cura icon and select "Run as Administrator" If that works, you may not have had Administrator privileges when you installed Cura. You can either uninstall Cura and then re-install as an Admin or change Cura to always start as Administrator: Right-click on Cura icon and select Properties, under the Compatibility tab check the box "Run this program as an Administrator". Then click "Ok" Hope this helps.

Randino: Do you not see the irony of your argument?

Many of the settings are saved at the end of the gcode. Also, you can edit the file name in Cura 2.1.x, just click on it.

Have you tried Cura 2.1.2? I have both installed and find that Cura 2.1.2 is better at Combing and Traveling.

Have you tried Cura 2.1.2? I have both installed and find that Cura 2.1.2 is better at Combing and traveling.

There should be a similar .json file on the Mac, but I don't know where it would be. But IRoberti says its set on the printer, so even changing it in Cura probably isn't going to help.

The Material Diameter on the Ultimaker2 is disabled by default in the .json profile. To enable it, so you can change it: Run WordPad as Administrator Open: c:\Program Files\Cura 2.1\resouces\machines\ultimaker2.json Scroll to the bottom and change "material_diameter": { "enabled": "True" }, Save and then restart Cura. You'll then be able to set the diameter to 1.75 Cheers.

Ok, I'm not seeing anything in the gcode that looks like a offset jump or otherwise. If you print using the same gcode file multiple times, does it always jump? And exactly the same way? 'Cause you said it happens nearly all the time. Does it always happen on the same axis? X or Y? It kinds sounds like a loose wire on either your X or Y motor. Or a motor is going bad.

Have you looked at the gcode to see if there is a reset of the origin or x/y positions being offset on that second layer? P.S. Layer numbering starts at 0, so the second layer would be ;LAYER:1

Do you have other options in the "Save to Removable Drive" drop down list? Click on the down arrow next to that button.

Its best to make a copy of the file, rename it, give it a new "id" and "name", perhaps even "manufacturer". Then make you mods and copy it back into the machines folder. When you restart Cura, you'll see it in the "Add Printer" dialog. Then when you download a Cura software update, you don't loose your changes.

Looks like your ATI/AMD/Radeon video driver is crashing. Have you tried updating the video drivers?

Na, I was just using the 2.1.2 release. I'll dig into the nightly builds - wasn't sure if I should go there. Thanks!