Geeetech

I am supposing the same. Or a problem related to the wrong management of long / integers during compilation, wrong casting or similar. Now I am doing a counter-test:

Set the slicer feed rates to almost absurd values, like 1 and 2 Then the result in the generated gcode is between acceptable ranges. If this work, I will try to modify the firmware feedrate calculation simplifying the formula and splitting it in more parts.

As I have finished the test cycles I will post an update anyway.

Enrico

Mark,

Now setting these low values the printer moves. Not fine because the values are too low in some cases but the problem on the z-axis occurs only when there is normal feedrates set in the slic3r with the Repetier host (take in account that I have saved the various kind of slic3r settings.

Exploring the firmware Medel_main.cpp it seems that for some strange reason the feedrate forumla
does not do the float division correctly. And this has not so much sense for me.

Hope you can suggest something else...

Thank you. Enrico

sorry don't quite familiar with the firmware and formula...guess the mainboard is faulty somewhere...