Printer jumps multiple times misplacing object

Get Help
1

What is the problem?
Hi all, I have a GEEETECH E180, no mod, no modifications at all...just a raspberry pi connected usb to control it wirelessly.

When I go to print things it starts normally and then after a few layers it jumps suddently to another position and then start printing again but it will have translated the print to some random location so i have mismatched layers. (and cloned objects)

I tried to slice gcode with CURA and EasyPrint (official printer slicer) with no success (apparently...read down)

I am at a total loss...

What did you already try to solve it?
I used the official slicer and software to control the printer and magically it starts to print correctly!
The same file, same gcode dropped on octoprint jups around the plate (with weird motor noises)

Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)

Recv:  ok
Send: N697 G1 X44.302 Y79.28 E296.8511*111
Recv:  ok
Send: N698 G1 X53.297 Y70.284 E297.5212*94
Recv:  ok
Send: N699 G1 X54.193 Y70.284 E297.5685*85
Recv:  ok
Send: N700 G1 X44.302 Y80.175 E298.3053*89
Recv:  ok
Send: N701 G1 X44.302 Y81.071 E298.3525*88
Recv:  ok
Send: N702 G1 X55.089 Y70.284 E299.156*111
Recv:  ok
Send: N703 G1 X55.985 Y70.284 E299.2032*90
Recv:  ok
Send: N704 G1 X44.302 Y81.967 E300.0735*83
Recv:  ok
Send: N705 G1 X44.302 Y82.863 E300.1208*94
Recv:  ok
Send: N706 G1 X56.881 Y70.284 E301.0578*80
Recv:  ok
Send: N707 G1 X57.777 Y70.284 E301.105*104
Recv:  ok
Send: N708 G1 X44.302 Y83.759 E302.1088*92
Recv:  ok
Send: N709 G1 X44.302 Y84.655 E302.156*100
Recv:  ok
Send: N710 G1 X58.672 Y70.284 E303.2265*80
Recv:  ok
Send: N711 G1 X59.568 Y70.284 E303.2737*90
Recv:  ok
Send: N712 G1 X44.302 Y85.551 E304.4109*80
Recv:  ok
Send: N713 G1 X44.302 Y86.447 E304.4581*80
Recv:  ok
Send: N714 G1 X60.464 Y70.284 E305.6621*92
Recv:  ok
Send: N715 G1 X61.36 Y70.284 E305.7093*97
Recv:  ok
Send: N716 G1 X44.302 Y87.343 E306.98*92
Recv:  ok
Send: N717 G1 X44.302 Y88.238 E307.0273*89
Recv:  ok
Send: N718 G1 X62.256 Y70.284 E308.3647*93
Recv:  ok
Send: N719 G1 X63.152 Y70.284 E308.4119*81
Recv:  ok
Send: N720 G1 X44.302 Y89.134 E309.8161*85
Recv:  ok
Send: N721 M105*35
Recv:  ok  B:0.0 /0.0 T0:210.0 /210.0 T1:0.0 /0.0 T2:85.3 /0.0 F:0 R:100 @:0 B@:0
Send: N722 G1 X44.302 Y90.03 E309.8633*106
Recv:  ok
Send: N723 G1 X64.048 Y70.284 E311.3342*86
Recv:  ok
Send: N724 G1 X64.943 Y70.284 E311.3814*91
Recv:  ok
Send: N725 G1 X44.302 Y90.926 E312.9191*87
Recv:  ok
Send: N726 G1 X44.302 Y91.822 E312.9663*90
Recv:  ok
Send: N727 G1 X65.839 Y70.285 E314.5707*90
Recv:  ok
Send: N728 G1 X66.735 Y70.285 E314.6179*89
Recv:  ok
Send: N729 G1 X44.302 Y92.718 E316.289*109
Recv:  ok
Send: N730 G1 X44.302 Y93.614 E316.3362*94
Recv:  ok
Send: N731 G1 X67.631 Y70.285 E318.0741*82
Recv:  ok
Send: N732 G1 X68.527 Y70.285 E318.1213*89
Recv:  ok
Send: N733 G1 X44.302 Y94.51 E319.9259*97
Recv:  ok
Send: N734 G1 X44.302 Y95.406 E319.9731*90
Recv:  ok
Send: N735 G1 X69.423 Y70.285 E321.8445*92
Recv:  ok
Send: N736 G1 X70.319 Y70.285 E321.8917*83
Recv:  ok
Send: N737 G1 X44.302 Y96.301 E323.8298*84
Recv:  ok
Send: N738 G1 X44.302 Y97.197 E323.877*100
Recv:  ok
Send: N739 G1 X71.214 Y70.285 E325.8818*91
Recv:  ok
Send: N740 G1 X71.499 Y70.896 E325.9173*91
Recv:  ok
Send: N741 G1 X44.302 Y98.093 E327.9434*86
Recv:  ok
Send: N742 G1 X44.302 Y98.989 E327.9905*88
Recv:  ok
Send: N743 G1 X71.503 Y71.787 E330.0169*82
Recv:  ok
Send: N744 G1 X71.508 Y72.679 E330.0639*95
Recv:  ok
Send: N745 G1 X44.302 Y99.885 E332.0905*94
Recv:  ok
Send: N746 G1 X44.302 Y100.781 E332.1377*105
Recv:  ok
Send: N747 G1 X71.536 Y73.547 E334.1665*82
Recv:  ok
Send: N748 G1 X71.724 Y74.255 E334.2051*93
Recv:  ok
Send: N749 G1 X44.302 Y101.677 E336.2479*97
Recv:  ok
Send: N750 G1 X44.302 Y102.573 E336.295*91
Recv:  ok
Send: N751 G1 X72.028 Y74.847 E338.3604*95
Recv:  ok
Send: N752 G1 X72.42 Y75.35 E338.3941*82
Recv:  ok
Send: N753 G1 X44.302 Y103.469 E340.4887*111
Recv:  ok
Send: N754 G1 X44.302 Y104.365 E340.5359*109
Recv:  ok
Send: N755 G1 X72.907 Y75.76 E342.6668*102
Recv:  ok
Send: N756 G1 X73.47 Y76.092 E342.7013*107
Recv:  ok
Send: N757 G1 X44.302 Y105.26 E344.8741*95
Recv:  ok
Send: N758 G1 X44.302 Y106.156 E344.9213*102
Recv:  ok
Send: N759 G1 X74.148 Y76.31 E347.1447*98
Recv:  ok
Send: N760 G1 X74.969 Y76.385 E347.1881*89
Recv:  ok
Send: N761 G1 X44.302 Y107.052 E349.4726*107
Recv:  ok
Send: N762 G1 X44.302 Y107.948 E349.5198*104
Recv:  ok
Send: N763 G1 X75.686 Y76.564 E351.8578*89
Recv:  ok
Send: N764 G1 X75.686 Y77.46 E351.9049*108
Recv:  ok
Send: N765 G1 X44.302 Y108.844 E354.2429*105
Recv:  ok
Send: N766 G1 X44.302 Y109.74 E354.2901*87
Recv:  ok
Send: N767 M105*33
Recv:  ok  B:0.0 /0.0 T0:210.2 /210.0 T1:0.0 /0.0 T2:85.3 /0.0 F:0 R:100 @:0 B@:0
Send: N768 G1 X75.686 Y78.355 E356.6281*80
Recv:  ok
Send: N769 G1 X75.687 Y79.251 E356.6752*95
Recv:  ok
Send: N770 G1 X44.302 Y110.636 E359.0132*111
Recv:  ok
Send: N771 G1 X44.302 Y111.532 E359.0604*106
Recv:  ok
Send: N772 G1 X75.687 Y80.147 E361.3984*83
Recv:  ok
Send: N773 G1 X75.687 Y81.042 E361.4456*82
Recv: JumpToApp0
Recv: JumpToApp1
Recv: ACHINE_TYPE:E180 UUID:180125E18003770 FIRMWARE_NAME:V1.00.16
Recv: PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1
Recv: echo:SD card ok
Recv: echo:Unknown command:
Recv: ok
Send: N774 M105*35
Recv: ok
Send: N775 G1 X44.302 Y112.428 E363.7836*102
Recv: ok
Send: N776 G1 X44.302 Y113.323 E363.8308*97
Recv: ok
Send: N777 G1 X75.687 Y81.938 E366.1688*81
Recv: ok
Send: N778 G1 X75.687 Y82.834 E366.216*98
Recv: ok
Send: N779 G1 X44.302 Y114.219 E368.554*93
Recv: echo:SD card ok
Recv: echo:Unknown command:
Recv: ok
Send: N780 G1 X44.302 Y115.115 E368.6012*100
Recv: ok
Send: N781 G1 X75.688 Y83.729 E370.9393*91
Recv: MACHINE_TYPE:E180 UUID:180125E18003770 FIRMWARE_NAME:V1.00.16
Recv: PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1
Recv: ok B:0.0 / /0.0 T0:0.0 /0.0 T1:0.0 /0.0 T2:0.0 /0.0 F:0 R:100 @:0 B@:0
Send: N782 G1 X75.688 Y84.625 E370.9865*80
Recv: Begin file list
Recv: 424.gcode
Recv: bitonga8.gcode
Recv: End file list
Recv: ok
Send: N783 G1 X44.302 Y116.011 E373.3245*110
Recv: Error0: Line Number is not Last Line Number+1, Last Line: 0
Recv: Resend: 1
Printer requested line 1 but no sufficient history is available, can't resend
Changing monitoring state from "Printing" to "Error: Printer requested line 1 but no sufficient history is available, can't resend"
Changing monitoring state from "Error: Printer requested line 1 but no sufficient history is available, can't resend" to "Offline (Error: Printer requested line 1 but no sufficient history is available, can't resend)"
Connection closed, closing down monitor
Connecting to: /dev/ttyUSB0
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0xb006ae70, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Starting baud rate detection...
Changing monitoring state from "Opening serial port" to "Detecting baudrate"
Trying baudrate: 115200
Send: N0 M110 N0*125
Recv: JumpToApp0
Recv: JumpToApp1
Recv: ACHINE_TYPE:E180 UUID:180125E18003770 FIRMWARE_NAME:V1.00.16
Recv: PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1
Recv: echo:SD card ok
Recv: echo:Unknown command:
Recv: ok
Changing monitoring state from "Detecting baudrate" to "Operational"
Send: N0 M110 N0*125
Recv: ok
Send: M115
Recv: ok
Send: M20
Recv: ok
Recv: ok
Recv: ok
Recv: echo:SD card ok
Recv: echo:Unknown command:
Recv: ok
Recv: ok
Recv: MACHINE_TYPE:E180 UUID:180125E18003770 FIRMWARE_NAME:V1.00.16
Recv: PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1
Recv: ok B:0.0 / /0.0 T0:0.0 /0.0 T1:0.0 /0.0 T2:0.0 /0.0 F:0 R:100 @:0 B@:0
Recv: Begin file list
Recv: 424.gcode
Recv: bitonga8.gcode
Recv: End file list
Recv: ok
Send: M105
Recv:  ok
Recv:  ok
Recv: ACHINE_TYPE:E180 UUID:180125E18003770 FIRMWARE_NAME:V1.00.16
Recv: PROTOCOL_VERSION:V1.0 EXTRUDER_COUNT:1
Recv:  ok
Recv: egin file list
Recv: 424.gcode
Recv: bitonga8.gcode
Recv: End file list
Recv: ok
Recv:  ok
Recv: ok  B:0.0 /0.0 T0:167.2 /0.0 T1:0.0 /0.0 T2:85.2 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:164.0 /0.0 T1:0.0 /0.0 T2:85.2 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:160.1 /0.0 T1:0.0 /0.0 T2:85.2 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:156.6 /0.0 T1:0.0 /0.0 T2:85.2 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:153.2 /0.0 T1:0.0 /0.0 T2:85.2 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:149.9 /0.0 T1:0.0 /0.0 T2:85.2 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:147.1 /0.0 T1:0.0 /0.0 T2:85.2 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:144.2 /0.0 T1:0.0 /0.0 T2:85.3 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:141.5 /0.0 T1:0.0 /0.0 T2:85.3 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:138.9 /0.0 T1:0.0 /0.0 T2:85.2 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:136.4 /0.0 T1:0.0 /0.0 T2:85.3 /0.0 F:0 R:100 @:0 B@:0
Send: G91
Recv:  ok
Send: G28 X0 Y0
Send: G90
Recv: X:0.000
Recv: Y:130.000
Recv:  ok
Recv:  ok
Send: G91
Recv:  ok
Send: G28 Z0
Recv: Z:131.900
Recv:  ok
Send: G90
Recv:  ok
Send: M105
Recv:  ok  B:0.0 /0.0 T0:133.9 /0.0 T1:0.0 /0.0 T2:85.2 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:131.6 /0.0 T1:0.0 /0.0 T2:85.3 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:129.5 /0.0 T1:0.0 /0.0 T2:85.3 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Recv:  ok  B:0.0 /0.0 T0:127.5 /0.0 T1:0.0 /0.0 T2:85.3 /0.0 F:0 R:100 @:0 B@:0
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105
Send: M105
No response from printer after 3 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
Changing monitoring state from "Operational" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
Connection closed, closing down monitor

Here i turned off the printer.

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)

OctoPrint 1.3.10 running on OctoPi 0.16.0 (installed yesterday)
As far as i know, octoprint doesn't edit the raw gcode...but a could be wrong.

esp32_caja_ok.gco (839.5 KB)

IMG_8077
IMG_8077.jpg4032Ă—3024 439 KB

2

Treat this as either:

  • insufficient power to the Pi
  • the serial cable needs to have internal metallic shielding or a ferrite core
3

The cable is the same i used with official control software so i think we can exclude it...
how can i check if power to my old raspberry pi 1 is good?

4

Seriously?

If it were me, I would retire the old Pi, buy a Raspberry Pi 3B, a new 5V 2.5A power adapter for it and try this.

5

Your printer seems to be resetting in the middle of the print. Multiple times. It also prints out something about jumping to apps which I've never seen before and strikes me as very odd. Does that thing have any kind of filament sensors, crash recovery or is your power flaky?

6

no sensors at all....it's very simple beginner printer... https://amzn.to/2CorokQ also i have the original power supply from the box.

7

What happens if you print the same gcode more than once? Does it fail exact same way?
Also, your log shows that you have SD card reader. Disconnect Octoprint and try printing the same gcode file from SD. Check if it makes difference.

1 Like
8

I do have SD card, but i can't use it because the screen is not calibrated and every touch bring me to the same useless menu :disappointed:

Should i remove it when using octoprint?

9

I replaced my old rpi1 with a new raspberry 3 + wifi... and happened again!
Now i have made a video... as you can see the extruder is working... but the positions jumps everywhere...

video
video2

ps: the file is still the same gcode generated from official slicer (which works good via usb with official software)

1 Like
10

What are these regular clonky noises? Sounds like it's skipping steps.

Can you please pay attention to the terminal tab when it happens? I'd like to know if there's this "JumpToApp" stuff happens coincides with the shift. Also please share a full octoprint.log.

11

I zipped all logs so you watch entire history.
The noise seems to came from the extruder i zoomed in the video with pulls the filament, and the retracts it... it does this noise only when operated with octoprint

logs.zip (9.9 KB)

12

So before we go any further here, first get rid of your undervoltage situation:

2019-11-07 17:47:58,851 - octoprint.plugins.pi_support - WARNING - This Raspberry Pi is reporting problems that might lead to bad performance or errors caused by overheating or insufficient power.
!!! UNDERVOLTAGE REPORTED !!! Make sure that the power supply and power cable are capable of supplying enough voltage and current to your Pi.

Once that is fixed, see if the issue persists and if so we can take it up from there.

1 Like
13
14

I'm using a 2.4A iPad Tablet power supply... how is possible the under voltage alert?

15

An iPad tablet "power supply" isn't a power adapter. It's technically a charger. A power adapter—if you saw the output on an oscilloscope—would be a nice flat 5V. A charger—again on the oscilloscope—would be pulsating voltage whose "root mean square" is 5V.

16

@OutsourcedGuru i'am about to order this one... it says "power supply" certified for raspberry... do you think it's good?

17

In theory, it's a good one. I don't love that it has two outlets; it encourages users to plug two Raspis into it (and there's no guarantee that it will continue to supply the expected power to both). Feel free to try it but you might just want to stick with the official version.

Without switch
With switch

18

These models are not available in my country, so i will order that and put tape on a usb port to not tempted to plug another raspberry! ahahah

Anyway... in your opinion if the raspberry doesn't reboot how can low power amperage disturb octoprint?

19

Another thing i noticed is when the octoprint connects by serial first time the print makes a reset beep... i cannot ear that sound during good or wrong printing... does octoprint quinckly reconnect making the nozzle jumping around??

20

Professor-mode engaged...

Electronics of all kinds depend upon the correct VCC (or main input voltage). The ones and zeroes of digital circuits need some in-between amount as a threshold: above this is true (one), below this is false (zero).

So the Raspberry Pi has an arbitrary 4.64VDC lower limit on incoming voltage (where it wants to see 5.0V). If your incoming voltage drops to that 4.64VDC level then the Raspberry understands that bad things can and will happen:

  • the Ethernet and wifi devices at this level become problematic and the Pi may even turn them off
  • the microSD reader/writer at this level becomes problematic and may fail
  • serial communication at this level becomes problematic and likely leads to communication errors
  • communication to an attached thumbdrive at this level becomes problematic and may lead to corruption
  • the ability to swap RAM to the swapfile at this level becomes problematic and may lead to a kernel crash

Think of it as a financial crisis akin to the conditions before a company goes out of business.

2 Likes