Tevo Tornado prints getting stopped automatically after couple layers

[suvinks]

Hi

Am using Tevo tornado firmware 1.1. I am able to connect and monitor the prints. However, for a print more than couple layers, the print gets paused automatically after 2-3 layers. The printer controls still work if I cancel the print and move the motors. However, due to some reason it will not print.

Any suggestions?

I was printing astrobot keychain file which was sliced in astrocloud. I also printed a very small 2layer print which came out correctly. Anything more than 5 has issues. Am using raspberrry pi 3 bplus for my hardware.

Thanks Suvin

[CoDanny]

Activate serial logs and when this happens again send to us via Settings -> Sofware -> advanced

[suvinks]

I have sent the log over with ticket number 384

[suvinks]

Pasting the part where I hit issues

---

2018-04-04 02:13:40,562 - SERIAL - DEBUG - Enabling serial logging
2018-04-04 02:13:46,134 - SERIAL - DEBUG - Send: M105
2018-04-04 02:13:46,149 - SERIAL - DEBUG - Recv: ok T:39.42 /0.00 B:39.90 /0.00 @:0 B@:0
2018-04-04 02:13:52,157 - SERIAL - DEBUG - Send: M105
2018-04-04 02:13:52,170 - SERIAL - DEBUG - Recv: ok T:39.19 /0.00 B:39.85 /0.00 @:0 B@:0
2018-04-04 02:13:58,184 - SERIAL - DEBUG - Send: M105
2018-04-04 02:13:58,206 - SERIAL - DEBUG - Recv: ok T:38.94 /0.00 B:39.79 /0.00 @:0 B@:0
2018-04-04 02:14:04,214 - SERIAL - DEBUG - Send: M105
2018-04-04 02:14:04,230 - SERIAL - DEBUG - Recv: ok T:38.56 /0.00 B:39.77 /0.00 @:0 B@:0
2018-04-04 02:14:10,238 - SERIAL - DEBUG - Send: M105
2018-04-04 02:14:10,251 - SERIAL - DEBUG - Recv: ok T:38.42 /0.00 B:39.88 /0.00 @:0 B@:0
2018-04-04 02:14:15,120 - SERIAL - DEBUG - Changing monitoring state from 'Operational' to 'Printing'
2018-04-04 02:14:15,123 - SERIAL - DEBUG - Send: N0 M110 N0*125
2018-04-04 02:14:15,139 - SERIAL - DEBUG - Recv: ok
2018-04-04 02:14:15,144 - SERIAL - DEBUG - Send: N1 M140 S60.0*76
2018-04-04 02:14:15,155 - SERIAL - DEBUG - Recv: ok
2018-04-04 02:14:15,157 - SERIAL - DEBUG - Send: N2 M109 S220.0*116
2018-04-04 02:14:15,175 - SERIAL - DEBUG - Recv:  T:38.58 /220.00 B:39.46 /60.00 @:0 B@:0 W:?
2018-04-04 02:14:16,180 - SERIAL - DEBUG - Recv:  T:37.94 /220.00 B:39.96 /60.00 @:127 B@:127 W:?
2018-04-04 02:14:17,196 - SERIAL - DEBUG - Recv: echo:busy: processing
2018-04-04 02:14:17,203 - SERIAL - DEBUG - Recv:  T:38.10 /220.00 B:39.96 /60.00 @:127 B@:127 W:?
2018-04-04 02:14:18,203 - SERIAL - DEBUG - Recv:  T:38.42 /220.00 B:39.92 /60.00 @:127 B@:127 W:?
2018-04-04 02:14:19,213 - SERIAL - DEBUG - Recv: echo:busy: processing
2018-04-04 02:14:19,220 - SERIAL - DEBUG - Recv:  T:39.02 /220.00 B:40.42 /60.00 @:127 B@:127 W:?
2018-04-04 02:14:20,220 - SERIAL - DEBUG - Recv:  T:39.81 /220.00 B:40.61 /60.00 @:127 B@:127 W:?
2018-04-04 02:14:21,235 - SERIAL - DEBUG - Recv:  T:40.92 /220.00 B:41.38 /60.00 @:127 B@:127 W:?
2018-04-04 02:14:21,244 - SERIAL - DEBUG - Recv: echo:busy: processing
2018-04-04 02:14:22,239 - SERIAL - DEBUG - Recv:  T:42.11 /220.00 B:41.60 /60.00 @:127 B@:127 W:?
2018-04-04 02:14:23,250 - SERIAL - DEBUG - Recv:  T:43.22 /220.00 B:42.26 /60.00 @:127 B@:127 W:?
2018-04-04 02:14:23,255 - SERIAL - DEBUG - Recv: echo:busy: processing
....
....
2018-04-04 02:32:10,626 - SERIAL - DEBUG - Send: N10544 G1 F1800 X159.074 Y161.150 E858.59670*13
2018-04-04 02:32:10,652 - SERIAL - DEBUG - Recv: ok
2018-04-04 02:32:10,653 - SERIAL - DEBUG - Send: N10545 G0 F9000 X158.466 Y161.193*71
2018-04-04 02:32:12,657 - SERIAL - DEBUG - Read communication timeout during printing, listen again
2018-04-04 02:32:22,670 - SERIAL - DEBUG - Read communication timeout during printing, listen again
2018-04-04 02:32:32,682 - SERIAL - DEBUG - Read communication timeout during printing, listen again
2018-04-04 02:32:42,695 - SERIAL - DEBUG - Read communication timeout during printing, listen again
2018-04-04 02:32:52,708 - SERIAL - DEBUG - Read communication timeout during printing, listen again
2018-04-04 02:32:54,703 - SERIAL - DEBUG - Send: G28 X0 Y0
2018-04-04 02:32:54,705 - SERIAL - DEBUG - Send: N0 M110 N0*125
2018-04-04 02:32:54,706 - SERIAL - DEBUG - Send: M140 S0.000000
2018-04-04 02:32:54,707 - SERIAL - DEBUG - Send: M104 S0.000000
2018-04-04 02:32:54,707 - SERIAL - DEBUG - Send: M84
2018-04-04 02:32:54,708 - SERIAL - DEBUG - Send: M106 S0
2018-04-04 02:32:54,794 - SERIAL - DEBUG - Changing monitoring state from 'Printing' to 'Operational'
2018-04-04 02:32:56,714 - SERIAL - DEBUG - Send: M105
2018-04-04 02:33:00,720 - SERIAL - DEBUG - Send: M105
2018-04-04 02:33:06,728 - SERIAL - DEBUG - Send: M105
2018-04-04 02:33:12,737 - SERIAL - DEBUG - Send: M105
2018-04-04 02:33:18,751 - SERIAL - DEBUG - Send: M105
2018-04-04 02:33:24,760 - SERIAL - DEBUG - Send: M105
2018-04-04 02:33:30,772 - SERIAL - DEBUG - Send: M105
2018-04-04 02:33:36,783 - SERIAL - DEBUG - Send: M105
2018-04-04 02:33:42,791 - SERIAL - DEBUG - Send: M105
2018-04-04 02:33:44,020 - SERIAL - DEBUG - Changing monitoring state from 'Operational' to 'Closed'
2018-04-04 02:33:44,035 - SERIAL - DEBUG - Changing monitoring state from 'Offline' to 'Opening serial port'
2018-04-04 02:33:44,049 - SERIAL - DEBUG - Connecting to: /dev/ttyUSB0
2018-04-04 02:33:44,056 - SERIAL - DEBUG - Connected to: Serial<id=0x73e47e50, open=True>(port='/dev/ttyUSB0', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=True, rtscts=False, dsrdtr=False), starting monitor
2018-04-04 02:33:44,057 - SERIAL - DEBUG - Changing monitoring state from 'Opening serial port' to 'Connecting'
2018-04-04 02:33:44,058 - SERIAL - DEBUG - Send: M105
2018-04-04 02:33:44,795 - SERIAL - DEBUG - Connection closed, closing down monitor
2018-04-04 02:33:46,061 - SERIAL - DEBUG - Send: M105

[CoDanny]

This log tells me that the printer stopped receiving commands or sending responses. After this:

2018-04-04 02:32:10,652 - SERIAL - DEBUG - Recv: ok
2018-04-04 02:32:10,653 - SERIAL - DEBUG - Send: N10545 G0 F9000 X158.466 Y161.193*71
2018-04-04 02:32:12,657 - SERIAL - DEBUG - Read communication timeout during printing, listen again

There's nothing else coming form the printer. I would guess it's a firmware or board issue.

[suvinks]

I connected the printer directly to my PC and used Ultimaker Cura to print directly. It did so without any issue. If it was a firmware issue the usb communication should have stopped for cura too right? Also my tornado is having Marilin 1.1 firmware. Which one do you suggest?

[CoDanny]

The firmware is fine but the loss of communication I can't explain. We have a Tevo Tarantula that we showing the same problems. Tevo sent us a new board, we're going to be testing it this week

[suvinks]

Thanks. Do let me know how it goes. I did update the firmware to 1.1.6 but still have the communication issue. This one too is printing with Cura without issues. With Astroprint, it stops after 3 layers :( I did try your Astroprint desktop. That one started printing without even heating up the bed or nozzle or even homing. I had to cancel the print. Looks like there is an issue with Gcode creation on that one. I could have tested the usb printing on that if it was working correctly.

Just that you know, the same issue is there for octoprint.

[suvinks]

Any updates?

[suvinks]

Is your Tevo working now without issues?

[CoDanny]

We haven't had time to test yet

[DanielJoyce]

Your raspberry pi needs a good powersupply and your printer and pi need to share a ground, like plug them both into the same outlet or power strip. This smells like brownout issues, especially if it worked from a laptop.