I have a little problem. Prusa i3, with arduino mega 2560 and ramps 1.4.

I have a little problem. Prusa i3, with arduino mega 2560 and ramps 1.4.
I always printed small object and dimensions isn’t was relevant. But “Empty Dice” (empty inside dice (K6) by pasqal - Thingiverse) has 30.1x30.2x29.82. Yesterday i printed GyroCube (Parametric Gyro Cube by whosawhatsis - Thingiverse) but instead 100x100x100 my cube has 100.8x100.64x86.7 !?!

Marlin has correct value:
#define DEFAULT_AXIS_STEPS_PER_UNIT {76.19,76.19,4000,850}
Result | Leadscrew pitch | Step angle | Stepping | Gear ratio
4000.00 | 0.8 | 1.8° | 1/16th | 1 : 1

G-code I was created in CURA 14.03 ( http://g.bsd4.pl/pastebin/gyrothecube-flat.gcode ). Seems to be fine when i loaded this into Repetier Host, but strange is when I look inside. The regexp “G1 Z9[2-9]” return 0. That means there no layer above 92mm in Gcode. Cura failed? Am I correct?

Haha. I know it’s not funny, but your prints are much better than what I get on my i3.

You don’t accidentally have a scaling factor set in Cura do you?

@Matt_Harrington i still learning :slight_smile:
@Dale_Dunn of course not. I checked twice.

Is the z axis still level at the end of the print? That would be a dead giveaway that you are losing z steps in hardware not software.

@Matt_Harrington I was wondering the same, but he said the layers are missing from the G code as well.

Hmm. Maybe not. That regexp search could have failed if the Z moves are combined with an X or Y movement. I don’t know if Cura does that. I think another search may be in order to find the last Z move and verify that it was to 86.7 and not 100.

@Dale_Dunn the newest version of Cura has a small Z lift enabled (0.075mm I think) which could possibly mess up the search?

It’s possible, seeing as all that black gunk is on his rods that they’re bound a bit, and the Z could be slipping in the couplers.

Last night i created simple cylinder shape. Dimensions: diameter 50mm, height 100 mm. Cura 14.03, in expert mode new function “Spiralize” (I used “spiralize” for saving filament for this test). Result, everything fine. http://g.bsd4.pl/pastebin/0rgnZ.jpg
I think that my previous printed GyroCube has broken Gcode. Before I generate Gcode i had problem with Python interpreter. It was happened after i installed FreeCAD in 0.14 unstable version.
I haven’t enought filament to print another GryroCube ;).