[repetier host 2.0]Print stopped soon after begin on micromake D1

emprize

error as follow

[img]https://holland.pk/jvqg3y9l[/img]

works perfectly at 1.6.2 but not in 2.0.0

emprize

emprize said:

error as follow



works perfectly at 1.6.2 but not in 2.0.0

sorry for the image

Repetier

Somehow your answers do not come through completely.

Should be

Error:temp. for retraction when heating [C]

as part of the eeprom scan. But that is EPR not error.

What OS is that? Connected via serial connector I assume?

emprize

Repetier said:

Somehow your answers do not come through completely.
Should be
Error:temp. for retraction when heating [C]
as part of the eeprom scan. But that is EPR not error.
What OS is that? Connected via serial connector I assume?

windows 10, repetier 0.92.9, connect via usb, exactly the same config but works at repetier host 1.6.2

Repetier

That is strange since both use same old communication system. New version just has some more answers it understands. But for correct analysis I need the written log to see what is happening. From what I see the serial seems to swallow or replace parts with older communication parts. Have seen that happen under high traffic e.g. echo enabled. In a parallel thread a used with same printer said with ping pong enabled the communication works for him also in 2.0.

Also last question - which board does the printer use and which baud rate is set? If I have that board I could try to reproduce.

emprize

it is chinese custom make board im not sure the detail, baud rate 250000

https://world.taobao.com/item/531683229732.htm?fromSite=main&spm=a312a.7700824.w4004-12199790885.24.99unkc

Lex8xx

Same problem on RAMPS 1.4 with marlin firmware. My printer is Flying bear FB P902

Repetier

No one wanting to share the full log part that explains what is going wrong? Com errors are quite normal and normally get fixed by host/server. The communication has not been changed for a while and is known to normally work, so without more information I have no point to start fixing.

Lex8xx

I try do it tomorrow, need install 2.0.1v again.

How can i share log for you?

Repetier

From dropbox/google drive share link. You can send it as pm if you think public is not good. Or use a site like pastebin to share the data.

Pleaee make sure it is the written log from host not the log in the gui which is incomplete.

Lex8xx

https://1drv.ms/t/s!Arg6_wducENG4Ahu4x5swrTEq5a- https://1drv.ms/t/s!Arg6_wducENG4Ak2I_vI2riqmORy

Lex8xx

Today it wont to start printing. Only heating.

Repetier

Case 1 very strange:

22:13:12.447 : ok T:223.6 /0.0 B:79.4 /0.0 T0:223.6 /0.0 @:0 B@:0

22:13:15.501 : N17 M10517

22:13:15.511 : ok T:220.7 /0.0 B:79.1 /0.0 T0:220.7 /0.0 @:0 B@:0

Then press start and:

22:14:54.997 : Resend: N43 G0 X79.22 Y76.554 Z0.3 F9000*28

22:14:54.997 : Error:Line Number is not Last Line Number+1, Last Line: 37

22:14:54.997 : Resend: 38

You see host has send line 17 and firmware I guess send some text I have never seen and then wants line 37.

Second case

22:18:18.298 : N34 M117 ETE: 2h 11m 12s58

22:18:18.301 : ok

22:18:18.302 : ok

22:18:18.302 : N35 M109 T0 S230*27

22:18:18.921 : ok

22:18:18.921 : N36 M10518

22:18:18.921 : N37 M107*17

22:18:18.925 : Error:No Checksum with line number, Last Line: 33

22:18:18.925 : Resend: 34

22:18:18.932 : ok

22:18:18.932 : Resend: N34 M117 ETE: 2h 11m 12s58

22:18:18.932 : Resend: N35 M109 T0 S230*27

is more clear. Here it seems the M117 command confuses the firmware. I guess it is the same in case 1 also we do not see it but line 37 seems also a M117 command.

So my guess is your firmware can not handle M117 with line number and checksum.

Only solution is in printer settings to deselect "Send ETA to printer display". This disables sending the M117 command coming from host it self. Of course your gcode should also not contain them.

Regular Marlin has no problems with this and it is also correct gcode so it is more a firmware problem as it seems, but with the workaround it should do.

Stevenlgts

I was having the same problem with the error due to retraction and I deselected the "Send to ETA to print display" and it correct my printing problem!