Octoprint wont start my prints

[Ewalk02]

I've been trying to get my M2 to work with Octoprint recently and have only had partial success. Up to this point I can monitor the printer via the webcam, heat the extruder and bed, move the extruder and bed, read the SD card....basically I can do everything except get Octoprint to start a print. When I upload a file and tell it to start the print it will heat the extruder/bed but then it never starts the print. All the temps will hold at the correct values but the printer will just sit there idle all night. Has anyone else experienced this? I'm using Simplify3D to generate my gcode and running Octoprint on a Raspberry Pi 2 Model B. Any help or insight would be appreciated.

[jsc]

What does it say in the Terminal tab when it's sitting there hanging? Anything?

[Ewalk02]

Octoprint acts just like it is printing, it runs through the gcode but the machine never moves....below is typical of what I get in the terminal viewer:

Send: M23 /redabs~1.gco
Recv: File opened:redabs~1.gco Size:17976176
Recv: File selected
Recv: ok
Changing monitoring state from 'Operational' to 'Printing from SD'
Send: N0 M110 N0*125
Send: N1 M108 S255*106
Recv: ok
Send: N2 G28*17
Recv: ok
Send: N3 G1 Y50 Z0.3 F9600*105
Recv: ok
Send: N4 G1 X205 Z10*24
Recv: ok
Send: N5 G1 Z0.4*125
Recv: ok
Send: N6 G92 E0*65
Recv: ok
Send: N7 G1 E25 F225*30
Recv: ok
Send: N8 G92 E0*79
Recv: ok

[jsc]

Try turning off checksums (Settings, Features). There was a Marlin bug from a year ago that may be affecting you: https://github.com/MarlinFirmware/Marlin/pull/1017

[Ewalk02]

Unfortunately the checksums option was already turned off.....still no luck

[jsc]

That's pretty odd. From your terminal trace, it looks like octoprint is sending the g-code and the RAMBo is getting them. And this works using another host program (Simplify3D?)

[jsc]

Oh, the checksums are not turned off, by the way, that's what those *[number] things are.

[Ewalk02]

I'll check into the check sums again, thanks for the help

[PcS]

I had this problem and it ended up being a bad flash. I would suggest reflashing the pi.

[Ewalk02]

I'll try a re-flash this weekend, this is getting frustrating.