I've been chasing the same error since a while, I had the same issues with stock firmware and also Repetier host. It turns out that the reason was a loose contact on the hardware.

Please refer to my other post here in this forum for more details: http://www.soliforum.com/post/118358/#p118358

Take care!

Long-standing issue in the 0.92 davinci port, see https://github.com/luc-github/Repetier- … /issues/38 for some possible tips to help.

The 0.92.6 Repetier code has fix for this on Due boards, and luc is syncing his tree in a new branch, but it apparently isn't ready yet.

I am willing to try this and report back.

1. I have not found a hard/fast solution with explanation of why this occurs, though I am about to read into issue 38 above.

It sounds like we ran into the exact same problem, by the way. My only fix was reflashing to stock firmware, at which point I never experienced this error again, ruling out any hardware faults-- unless there's some kind of weird, atypical interaction between the printer's electronics and Repetier that the firmware can't figure out.

After being satisfied that my printer can indeed print (and enjoying some ~95 hours of printing trouble free) I'm again interested in working with Repetier.

I'm going to try 0.92.6 and will report back after this weekend

The 0.92.6 Repetier code has fix for this on Due boards, and luc is syncing his tree in a new branch, but it apparently isn't ready yet.

Coin wrote:

3- I am not sure if I can upload a file in here. Send me your email in private message and I will send you a gcode.

4- https://www.simplify3d.com/support/prin … e-of-print

5- mpoffo could have pointed a good check. The extension, the plug, possible interference, the card... I use a cheap eBay extension myself and it works good.

Okay, thank you. I will PM my email.

In other news, I reflashed Repetier. I made it about 2 hours into a 2h40m long print and it froze again.

This time, the last unknown command was M106 S137.

Might try reflashing with Arduino 1.6.5 and see if that has any effect. About to swap my SD tomorrow as well.

If it is the motherboard overheating, I'm not sure how to check for that. I honestly need a weekend free to troubleshoot it entirely, in the meantime bumping for any new random suggestions

Get a fan and set it so it blows straight on the motherboard... If the prints gets further then it is a heat problem and you should consider installing one or more fans around/over the mainboard.

3- I am not sure if I can upload a file in here. Send me your email in private message and I will send you a gcode.

4- https://www.simplify3d.com/support/prin … e-of-print

5- mpoffo could have pointed a good check. The extension, the plug, possible interference, the card... I use a cheap eBay extension myself and it works good.

Okay, thank you. I will PM my email.

In other news, I reflashed Repetier. I made it about 2 hours into a 2h40m long print and it froze again.

This time, the last unknown command was M106 S137.

Might try reflashing with Arduino 1.6.5 and see if that has any effect. About to swap my SD tomorrow as well.

If it is the motherboard overheating, I'm not sure how to check for that. I honestly need a weekend free to troubleshoot it entirely, in the meantime bumping for any new random suggestions

4- https://www.simplify3d.com/support/prin … e-of-print

5- mpoffo could have pointed a good check. The extension, the plug, possible interference, the card... I use a cheap eBay extension myself and it works good.

1- Have you tried to completely unplug the USB cable ?
2- Does the problem occur on different gcode / models ?
3- I could compile you a gcode using Simplify3D if you'd like to try.

1- yes, having the USB totally unplugged does not help.

2- Yes, it occurs on any/ every model. It could be a problem with my Slic3r settings

3- That would be awesome, if you have anything that's like roughly a ~1 hour job and compiled it, that would be perfect.

Discovered last night that running the print job directly through the USB cable (not uploading to the SD) seems somewhat more reliable, but the problem still exists.

Just reran an SD print that failed in the past, it failed again. I checked temps and tension in the wiring here again immediately after print failure, but all seems well.

Reinstalled Repetier Host.

Only error logged from Gcode:
"Unknown command:M106   S237"

Trying one directly through my laptop's USB to see if that completes without errors, seeing as I've only used the SD print option.

I only ran about a minute and a half of a calibration print before I bought it (used) to made sure it ran. Then, I immediately upgraded to sort of immerse myself in the technical details of 3D printing, but in retrospect I should've definitely gotten a baseline on the stock firmware.

I haven't, no, that's a good idea. I actually just picked up an IR temperature sensor, when I get home from campus I'm going to check the operating temps of the motors, the PS, the extruder and the bed.

Will do, I've been monitoring the G-code and haven't been getting any glaring errors (outside of the printer not recognizing extruder fan commands) but I'll start logging.

Okay, thanks.

Will update later today or tomorrow.

Have you made sure the power supply is getting plenty of cooling as well?  They can also overheat.

I'm not sure if Repetier host can show the G-codes being executed, but Octoprint does by default.

Check to see what command is trying to be executed when it freezes.  (Keep a log) Post what you discover, even if there appears to be no pattern in the last G-code executed. 

Additionally, you can manually edit in @info and/or @pause commands (Bottom of page) to your g-code to try things like pausing every dozen layers or so to see if some cooling time prevents the issue.  (These wouldn't be fixes, but they will provide info on what is causing the issues.)