What is the problem?
Printer just stops without error and creates a blob on the current position.
Terminal shows "Recv: echo:busy: paused for user"
What did you already try to solve it?
- Changed thermistor because at first I got thermal runaway errors with old firmware
- Checked all cables
- Changed power supplies
- Changed power outlet
- Changed firmware from 1.1.2 to 2.1.2.5
- Changed positions of equipment
- Changed USB cable many times
- Added ferrit cores to the USB cable that is working
- Did PID tuning, because the temperature of the hot end varies +/- 5°C
Have you tried running in safe mode?
No
Did running in safe mode solve the problem?
/
Systeminfo Bundle
You can download this in OctoPrint's System Information dialog ... no bundle, no support!)
octoprint-systeminfo-20241212234920.zip (99.4 KB)
Additional information about your setup
OctoPrint Version 1.10.3
OctoPi 2024.11.05.092907 with "webcamd", based on OctoPi 1.0.0, running on Raspberry Pi 4 Model B Rev 1.1
FLSUN Cube, no filament sensor
Marlin 2.1.2.5
PrusaSlicer 2.9.0
G-Code
Start G-Code
G90 ; use absolute coordinates
M83 ; extruder relative mode
M104 S{is_nil(idle_temperature[0]) ? 150 : idle_temperature[0]} ; set temporary nozzle temp to prevent oozing during homing and auto bed leveling
M140 S{first_layer_bed_temperature[0]} ; set final bed temp
M190 S{first_layer_bed_temperature[0]} ; wait for bed temp to stabilize
G28 ; home all axis
G29 ; auto bed levelling
G1 Z50 F240
G1 X2.0 Y10 F3000
M104 S{first_layer_temperature[0]} ; set final nozzle temp
M109 S{first_layer_temperature[0]} ; wait for nozzle temp to stabilize
G1 Z0.28 F240
G92 E0
G1 X2.0 Y140 E10 F1500 ; prime the nozzle
G1 X2.3 Y140 F5000
G92 E0
G1 X2.3 Y10 E10 F1200 ; prime the nozzle
G92 E0
End G-Code
{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+2, max_print_height)} F600{endif} ; Move print bed down
G1 X50 Y50 F{travel_speed*60} ; move print head out of the way
M140 S0 ; turn off heatbed
M104 S0 ; turn off temperature
M107 ; turn off fan
M84 X Y E ; disable motors
Hello @l1z4rd89 !
This message
is generated by the firmware of the printer.
Unfortunately, this message does not appear in the octoprint.log.
Usually this massage can be confirmed by clicking Resume on the OctoPrint GUI.
PS:
Please do not use a(nother) file server. Upload your files here. Ur use a link:
https://reprap.org/wiki/G-code#D20:_Generate_an_offline_crash_dump
Also: For you use a FLSUN printer, D20 won't work. It is Prusa only.
1 Like
Hey @Ewald_Ikemann
thank you for your answer 
-
Resume on the OctoPrint GUI
Does not show for me, should I check the LCD the next time?
My printer is on another floor, that's why I did not check it and just used OctoPrint to cancel and reconnect after the error.
-
When the error does not show up in octoprint.log does that mean that it could be another error but it just shows Recv: echo:busy: paused for user ? Is there some way for me to pinpoint the error?
-
Could this error be caused by EMI? There are fluorescent tubes in this room.
Or: Low voltage on the drivers?
Or: Could this also be caused by a faulty mainboard? (it is old, 2017)
Or: The temperature fluctuates too much?
-
I used WeTransfer because the file was bigger than 4mb, sry.
-
D20 is misleading, sorry again. The *.stl file I used was called like that. The gcode is for a screw and nut.
I appreciate the help Have a nice day.
This it not an error. It is a notification. And when you get this on the OctoPrint GUI, it should appear in the log.
Unlikely.
You may check the gcode file if there is a hint (filament change etc.)
What you can do is activate the serial.log and post a new systeminfo bundle after the message occurred again.
1 Like
Hey @Ewald_Ikemann
oh, I added serial.log. I deleted some logs and uploaded the wrong one. Here is the serial.log added
octoprint-systeminfo-20241212234920.zip (1009.2 KB)
serial.log:
The print starts at 2024-12-12 21:50:16,008
The notification appears at 2024-12-12 23:13:16,486
Then I try to unpause / pause with the OctoPrint buttons on the left. There was no extra button for resume.
Then I cancel the print job at 2024-12-12 23:15:50,329
I did not find any filament change commands or pause commands in the gcode.
There is nothing extraordinary going on before this message.
...
2024-12-12 23:13:14,211 - Recv: ok
2024-12-12 23:13:14,215 - Send: G1 E-4.2 F2100
2024-12-12 23:13:14,238 - Recv: ok
2024-12-12 23:13:14,243 - Send: G1 F6240
2024-12-12 23:13:14,244 - Recv: ok
2024-12-12 23:13:14,246 - Send: G1 X135.753 Y116.767 E-.26519
2024-12-12 23:13:14,275 - Recv: ok
2024-12-12 23:13:14,278 - Send: G1 X136.017 Y116.983 E-.10905
2024-12-12 23:13:14,370 - Recv: ok
2024-12-12 23:13:14,373 - Send: G1 X136.281 Y117.2 E-.10926
2024-12-12 23:13:14,426 - Recv: ok
2024-12-12 23:13:14,428 - Send: G1 X136.739 Y117.541 E-.18256
2024-12-12 23:13:14,467 - Recv: ok
2024-12-12 23:13:14,471 - Send: G1 X136.794 Y117.578 E-.02119
2024-12-12 23:13:14,485 - Recv: ok
2024-12-12 23:13:14,489 - Send: G1 E-1.11275 F2100
2024-12-12 23:13:16,486 - Recv: echo:busy: paused for user
2024-12-12 23:13:18,486 - Recv: echo:busy: paused for user
2024-12-12 23:13:20,486 - Recv: echo:busy: paused for user
...
I really can't tell why the printer firmware is doing this.
1 Like
Hey @Ewald_Ikemann
so what I did:
- Adjusted the voltage of my printer power unit
- Added ferrit cores to the power cables
- Using short names for *.gcode files
- Added these settings in
configuration.h and configuration_adv.h of marlin because I wanted to update my LCD as well but then realized my LCD does need another configuration file and other menu pictures:
EEPROM_SETTINGS (in Configuration.h)
BABYSTEPPING (in Configuration_adv.h)
AUTO_REPORT_TEMPERATURES (in Configuration_adv.h)
AUTO_REPORT_POSITION (in Configuration_adv.h)
EXTENDED_CAPABILITIES_REPORT (in Configuration_adv.h)
M115_GEOMETRY_REPORT (in Configuration_adv.h)
M114_DETAIL (in Configuration_adv.h)
REPORT_FAN_CHANGE (in Configuration_adv.h)
SDSUPPORT (in Configuration.h)
LONG_FILENAME_HOST_SUPPORT (in Configuration_adv.h)
AUTO_REPORT_SD_STATUS (in Configuration_adv.h)
SDCARD_CONNECTION ONBOARD (in Configuration_adv.h)
EMERGENCY_PARSER (in Configuration_adv.h)
SERIAL_FLOAT_PRECISION 4 (in Configuration_adv.h)
HOST_ACTION_COMMANDS (in Configuration_adv.h)
HOST_PROMPT_SUPPORT (in Configuration_adv.h)
HOST_STATUS_NOTIFICATIONS (in Configuration_adv.h)
Options to support dialog with host (as pre requisite)
SET_PROGRESS_MANUALLY (in Configuration_adv.h)
M73_REPORT (in Configuration_adv.h)
ADVANCED_OK (in Configuration_adv.h)
NOZZLE_PARK_FEATURE (in Configuration.h)
ADVANCED_PAUSE_FEATURE (in Configuration_adv.h)
PARK_HEAD_ON_PAUSE (in Configuration_adv.h)
FILAMENT_LOAD_UNLOAD_GCODES (in Configuration_adv.h)
Z_MIN_PROBE_REPEATABILITY_TEST (in Configuration.h)
G26_MESH_VALIDATION (in Configuration.h)
Z_STEPPER_AUTO_ALIGN (in Configuration_adv.h)
- Currently have my LCD disconnected
Until now it seems to be working. Have printed 1hour, 4hours and now 3 hours without a pause / error/ etc.
1 Like
