reprappro / RepRapFirmware

OO C++ RepRap Firmware
Other
143 stars 120 forks source link

bad moves in Z-Axis #60

Closed RFranta closed 10 years ago

RFranta commented 10 years ago

Hi, my printer is two extruders machine. Extruding, heating and move in x and y axis works fine. but strange thing happens, when I try to print something, when its time for move layer up Z axis doesnt move as it should (just tiny move) and I hear some strange noise, almost beep... When I move with hotend in Z axis in pronterface or do Z homing, Z axis works fine, problem is only when printing, I found that it happen directly after the code "G92 E0" even it doesnt make sense for me, when I deleted all "G92 E0" in gcode file, moving in Z axis was fine,

Here are my sd/sys and my platform files, the only files that I changed on firmware. https://drive.google.com/folderview?id=0B_zsCEMKg3fibmVtaTZ5bXZMT0U&usp=sharing

Thank you for any help!

reprappro commented 10 years ago

Hi

This should be fixed by Version 0.78 in the test branch. Let me know if there's still a problem.

Best wishes

Adrian

Dr Adrian Bowyer Director RepRapPro Ltd http://reprappro.com

On 12/06/14 18:34, RFranta wrote:

Hi, my printer is two extruders machine. Extruding, heating and move in x and y axis works fine. but strange thing happens, when I try to print something, when its time for move layer up Z axis doesnt move as it should (just tiny move) and I hear some strange noise, almost beep... When I move with hotend in Z axis in pronterface or do Z homing, Z axis works fine, problem is only when printing, I found that it happen directly after the code "G92 E0" even it doesnt make sense for me, when I deleted all "G92 E0" in gcode file, moving in Z axis was fine,

Here are my sd/sys and my platform files, the only files that I changed on firmware. https://drive.google.com/#folders/0B_zsCEMKg3fibmVtaTZ5bXZMT0U

Thank you for any help!

— Reply to this email directly or view it on GitHub https://github.com/reprappro/RepRapFirmware/issues/60.

RFranta commented 10 years ago

Thank you very much! Yes, problem was solved in version 0.78 in the test branch.