UM+Cura 12.11 hangs - what does my error log mean?

[andywalter 7]

Hi, I had problems a while back, UM RepG had been stable from day 1; Cura 12.11 was hanging very frequently. Changing the USB cabling from using front-panel of Win7 PC to using USB on mobo at the back seemed to improve it; but today it's hung twice, once after 15 mins of a run, then about 10 seconds after starting a new run! I got this error-log after the second hang - does it suggest what my problem is please?

Send: M105

Recv: ok T:239.8 /240.0 B:0.0 /0.0 @:42

Send: M105

Recv: ok T:239.8 /240.0 B:0.0 /0.0 @:41

... lots more like this skipped, m/c ok so far ...

Recv: ok T:240.2 /240.0 B:0.0 /0.0 @:36

Send: G92 E0

Send: G1 E2 F120

Recv: ok

Recv: ok

Send: M105

Recv: ok T:239.8 /240.0 B:0.0 /0.0 @:46

Send: M105

Recv: ok T:239.8 /240.0 B:0.0 /0.0 @:46

Send: G92 E0

Send: G1 E2 F120

Recv: ok

Recv: ok

Send: G92 E0

Send: G1 E2 F120

Recv: ok

Recv: ok

Send: G92 E0

Send: G1 E2 F120

Recv: ok

Recv: ok

Send: G92 E0

Send: G1 E2 F120

Recv: ok

Recv: ok

Send: M105

Recv: ok T:240.2 /240.0 B:0.0 /0.0 @:36

... another 12 like this Send:/Recv pair skipped ...

Recv: ok T:239.7 /240.0 B:0.0 /0.0 @:42

Changing monitoring state from 'Operational' to 'Printing'

Send: N0M110*3

Send: N1M92 E865.888000*65

Send: N2M109 S240.000000*98

Send: N3G21*57

Send: N4G90*52

Recv: ok

Send: N4G90*52

Recv: ok

Send: N5M107*0

Send: N6G28 X0 Y0*52

Serial timeout while writing to serial port, trying again.

Recv: T:239.7 E:0 W:3

Recv: T:239.8 E:0 W:2

Recv: T:239.9 E:0 W:1

Recv: T:239.8 E:0 W:0

Recv: ok

Send: M105

Recv: Error:Line Number is not Last Line Number+1, Last Line:4

Recv: Resend:5

Recv: ok

Send: N5M107*0

Recv: ok

Send: N6G28 X0 Y0*52

Recv: ok

Send: N7G28 Z0*126

Recv: echo:Unknown command:"05"

Recv: ok

Send: N8G92 X0 Y0 Z0 E0*36

Recv: ok

Send: N9G1 Z15.0 F180*62

Recv: ok

Send: N10G92 E0*86

Recv: ok

Send: N11G1 F200 E3*58

Communication timeout during printing, forcing a line

Send: M105

Communication timeout during printing, forcing a line

Send: M105

Recv: ok

Send: M105

Recv: ok

Send: N12G92 E0*84

Recv: ok

Send: N13G1 F9000*85

Recv: ok

Send: N14G1 X38.156 Y104.583 Z0.3 F9000.0*40

Recv: ok T:240.7 /240.0 B:0.0 /0.0 @:30

Send: N15G1 X38.245 Y110.679 F1200.0 E0.1954*4

Recv: ok

Send: N16G1 X39.63 Y115.922 E0.3693*73

Recv: ok T:240.7 /240.0 B:0.0 /0.0 @:30

Send: N17G1 X40.822 Y119.868 E0.5014*119

Recv: ok T:240.7 /240.0 B:0.0 /0.0 @:30

Send: N18G1 X43.219 Y125.712 E0.704*71

Recv: ok

Send: N19G1 X44.172 Y127.389 E0.7658*116

Recv: ok

Send: N20G1 X47.069 Y132.374 E0.9507*119

Recv: ok

Send: N21G1 X51.323 Y138.138 E1.1803*124

Recv: ok

Send: N22G1 X57.843 Y144.588 E1.4744*121

Recv: ok

Send: N23G1 X66.62 Y150.857 E1.8202*64

Recv: ok

Send: N24G1 X72.246 Y153.629 E2.0212*120

Recv: ok

Send: N25G1 X78.432 Y156.12 E2.235*120

Recv: ok

Send: N26G1 X83.051 Y157.23 E2.3874*65

Recv: ok

Send: N27G1 X93.395 Y158.52 E2.7215*74

Recv: ok

Send: N28G1 X107.262 Y158.52 E3.1661*112

Recv: ok

Send: N29G1 X115.625 Y157.32 E3.437*76

Recv: ok

Send: N30G1 X120.755 Y156.12 E3.6059*125

Recv: ok

Send: N31G1 X124.511 Y154.834 E3.7332*75

Recv: ok

Send: N32G1 X130.542 Y152.051 E3.9461*73

Recv: ok

Send: N33G1 X138.751 Y147.148 E4.2527*66

Recv: ok

Send: N34G1 X146.668 Y140.566 E4.5828*77

Recv: ok

Send: N35G1 X152.046 Y133.699 E4.8624*75

Recv: ok

Send: M105

Recv: ok

Send: N36G1 X154.394 Y130.201 E4.9975*78

Recv: ok

Send: N37G1 X156.831 Y125.334 E5.172*125

Recv: Error:No Checksum with line number, Last Line:32

Changing monitoring state from 'Printing' to 'Error: No Checksum with lin...'

Recv: Resend:33

Recv: ok

Recv: Error:No Line Number with checksum, Last Line:32

and it's stopped dead, dribbling hot plastic. Any ideas please? What puzzles me is, this m/c was rock-solid using Repg, so has the USB serial comms protocol changed when going to Cura?

Thx, Andy

[Daid 306]

Seems like something goes wrong in the cura code, as this shouldn't happen:

"Changing monitoring state from 'Printing' to 'Error: No Checksum with lin...'"

It seems that the exception for that error state is missing (Sadly enough, the machine reports both critical errors and communication errors as "Error:"