MaikStohn / UP3D

UP 3D Printer Tools
GNU General Public License v2.0
80 stars 32 forks source link

Layer Positioning Issue #28

Closed adrianbear closed 8 years ago

adrianbear commented 8 years ago

Hi @MaikStohn, @kscheff, Testing version "UP3DTOOLS_WIN_20160508_v0.6.2" with my UPBox, there is an issue with the layer positioning. The error can be seen both in a real print and when converting back to gcode. This is the original preview image

After converting to up code and then back to gcode, the preview looks like this image

I considered this may just be an issue with the preview only from converting back and forth so I printed it anyway, but the real print has the layers off too. wp_20160510_005 wp_20160510_004

Adrian

The files might help :), I couldn't zip everything so I excluded the upcode and the converted back to gcode files (as I figured you could reproduce them with your tools anyway) LayerPositioningIssue.zip

MaikStohn commented 8 years ago

Thanks for the files.

Will have a look at them. The problem seems to be very very small segments (time wise), This only seems to happen when your speed is very slow.

adrianbear commented 8 years ago

The print shown here was done at 3600 mm/min which is only a bit slower then the UPBox turbo speed on a 0.4 mm layer height (5020 mm/min). I also originally tried the print at 4800 mm/min but got the same result.

MaikStohn commented 8 years ago

I will have a look as soon as I find some time for it.

MaikStohn commented 8 years ago

Hi,

this was a tricky one. Actually everything was working perfect except a small thing. The absolute Z-move for layer change was not synchronized with the normal movement buffer, which was caused by a skip (ultra small timing segment). So I was looking at wrong place for some time.

New version contains a fix for it. Please check and close the issue if it's solved.

Maik

EDIT: Looks like the build is a bit slow today. Please wait and check for v0.6.4 to download.

adrianbear commented 8 years ago

Yeah, the windows build is taking a while

MaikStohn commented 8 years ago

Finally the build was getting through. v0.6.4 is ready now.

adrianbear commented 8 years ago

This appears to be resolved in version 0.6.4. Closing the issue :) Adrian