Printing stops without reason

Hi,

I'm having troubles with my printer who stops without reason.
I can print several times the same file, it will never fail at the same spot.
When the print fails, the head stops moving, but still heats.

I did not succed to have more logs.
I have no error message.
What I don't understand from logs :
- Why a "Smoothie" line, on client side ?
- Why is there a M20 command sent ?

Printer : MicroDelta Rework
Drivers are up to date (SD formated, new files freshly downloaded)

My configuration : Repetier Host on windows, linked to Repetier Server on Linux server (chip), linked to the printer by USB.

Attachements :
- 20171217_fromServer.log : logs from Repetier Server
- 20171217_fromClient.log: logs from Repetier Host

Do you have any idea to resolve this mistery ?

Regards,
LeNouveau

PS : Yes, logs have 1 hour shift, server is not well configured.
PS : On server logs, I only cut the middle part, for file size. Begining and end are as is.

Somehow the data on my Controller is getting really messed up causing many weird things to happen. similar to what you are experiencing here.
Seems like when I do an M502 or M501 and a M500 or more simply stated a factory reset the problems go away.

Not saying this will fix yours, just stating this seem to work for mine.

Edited 2 time(s). Last edit at 12/17/2017 01:01PM by Roberts_Clif.

By "Reset Factory", do you mean format the MicroSD and reinstall firmware ? If so, I already tried and it changed nothing.

The printer stoped again, this afternoon.
Forgot to specify that sometimes (not sure it's every time, or I missed it), the printer bips when it stops.
Don't know if it can help.

Still curious why I have a "Smoothie" line in logs. Don't know what it means.

Repetier may not have reset factory settings.

smoothie probably means your printer is running smoothieware firmware.
Send a M115 comand to the printer to get firmware version.

22:41:42.416 : M115
22:41:42.809 : ok

Not very talkative.
Is it the expected return ? According to the M115 documentation, it's not working on Smoothie. So, it's normal ?

(yes, I'm a bit lost, sorry if stupid questions)

Different approach: What's the endstop config you use? Normal Open or Closed? Mechanical? Optical? Magnetic? Sudden and random print stops may occur when the endstop wires get noise from the environment, probably because heating or motor wires are close to them. If the firmware detects an endstop triggered during the print, something is wrong for sure.
Does your firmware log something if an endstop is triggered? I couldn't see anything at a quick glance, but maybe these events don't get logged.
Anyway NC endstop against GND config is usually less sensible because of the wires being pulled down in normal operation, and if it's not too much trouble, you could try to move your endstop wires somewhat away from your motor & heating wires.