Octoprint + Marlin communication issue

The issue I am experiencing is that Octoprint sends Gcodes to RAMPS(Marlin) and RAMPS responses with ok, however, before it actually having moved its motor to the position.
So what actually happens is only few of the Gcode sent by Octoprint being actualized to the machine. Although I made an STL file with star shape, it makes some random shape or even completely ignores XY movement and only raise extruder head every 2 seconds which is insane. The estimated print time is 3hours according to CURA, but RAMPS, which experiences almost instantenous response from RAMPS, estimates its finish time to 10 minutes!

Here is the terminal log from Octoprint :

Send: N6725 G0 F600 X205.675 Y141.513*78
Recv: ok
Send: N6726 G1 F1200 X207.931 Y139.258 E124.31224*57
Recv: ok
Send: N6727 G0 F600 X208.769 Y139.833*77
Recv: ok
Send: N6728 G1 F1200 X207.089 Y141.513 E124.31378*50
Recv: ok
Send: N6729 G0 F600 X208.503 Y141.513*77
Recv: ok
Send: N6730 G1 F1200 X210.027 Y140.696 E124.31480*54
Recv: ok
Send: N6731 G1 X209.918 Y141.513 E124.31533*89

it would have been much more descriptive if I could configure octoprint to print out timestamps, but I can tell you that this much log happened in less than 2 seconds.

Our printer in fact isn't conventional - we are extruding chocolate out of cylinder, so we have some few irregularities on CURA settings. Since we are extruding molten chocolate out of cylinder, we set filament diameter to 42mm and layer thickness to 1mm (both causing warning message), although I don't really think this is the source of error.

Did anyone experience same problem as me when using octoprint + marlin? I would appreciate it if you could share your solution.

Thanks!

Edited 1 time(s). Last edit at 06/12/2015 06:36AM by totorovirus.

First thing I would take OctoPrint out of the picture by sending the G-codes directly from a laptop or another PC.

Because my guess is OctoPrint has nothing to do with your problems. Nor the RAMPS board itself. Probably it's a firmware issue.

Second, I would look into your Marlin Configuration.h (if you need to post it here, please do not post in General, post in the Firmware section, and do not post a Configuration.h file in the post itself, attach it as a separate file).

My guess is about the same with yours. I should move this post to firmware section