[BUG] Anycubic P - print stops, target temperatures show 0 #559

New Issue

2024-12-03T16:30:16-06:00

fenugrec commented

2024-12-03 16:30:16 -06:00

(Migrated from github.com)

Hi,
I've installed this firmware hoping it would cure some glitches in the original firmware.

I've had this issue a few times now randomly, not every time. Can happen within 1h.

Print stops at some arbitrary height,
parks the head at the origin (nice)
the temperature targets now display 0 for both E0 and Bed, as if it had given up.
Display is still normal, responsive progress screen. The temperature readings still update, too.

Is there a way to find out what exactly it's waiting for ?

Steps to Reproduce

print anything
cross fingers to make it through the print
it doesn't

Additional Information

Anycubic mega P
this firmare, MEGA_P_DGUS_v1.5.4

[EDIT] happened a second time, at 14% completion (first time was 15%)

Hi, I've installed this firmware hoping it would cure some glitches in the original firmware. I've had this issue a few times now randomly, not every time. Can happen within 1h. - Print stops at some arbitrary height, - parks the head at the origin (nice) - the temperature targets now display 0 for both E0 and Bed, as if it had given up. - Display is still normal, responsive progress screen. The temperature readings still update, too. Is there a way to find out what exactly it's waiting for ? ### Steps to Reproduce 1. print anything 2. cross fingers to make it through the print 3. it doesn't #### Additional Information * Anycubic mega P * this firmare, `MEGA_P_DGUS_v1.5.4` ![printstall](https://github.com/user-attachments/assets/5ef4f38b-8e71-40f6-a6b0-0220ecbcda17) [EDIT] happened a second time, at 14% completion (first time was 15%)

fenugrec commented

2024-12-05 11:41:58 -06:00

(Migrated from github.com)

I looked at the Gcode, and there are

the expected G0, G1 moves
some M205 X Y motion settings
G92 E0 "New extruder position" , a few of these in the early parts to clear filament etc, and one around layer 60, Z=19mm . Unsure what Z height my prints stopped but it seemed quite lower than 19mm.

There is no weird M command in the middle of nowhere, it's all just regular stuff...

I looked at the Gcode, and there are - the expected G0, G1 moves - some M205 X Y motion settings - G92 E0 "New extruder position" , a few of these in the early parts to clear filament etc, and one around layer 60, Z=19mm . Unsure what Z height my prints stopped but it seemed quite lower than 19mm. There is no weird M command in the middle of nowhere, it's all just regular stuff...

fenugrec commented

2024-12-06 08:28:25 -06:00

(Migrated from github.com)

Out of pure irrational optimism I tried the print again today, and after failing to even start a few times in a row, it eventually worked. Not sure what to think of this, but it will not be possible to debug this issue further.

stklcode commented

2024-12-06 10:44:51 -06:00

(Migrated from github.com)

Out of curiosity: printing from SD card or via USB?

I experienced some more or less random filament runout issues (most likely a hardware issue, he sensors are not very reliable) which got better with increased error threshold (since 1.5.3 IIRC) and there was some change around runout pause in 1.5.4, too.

I didn't use the SD card for quite a while, so wondering if it's actually a simple false-positive runout with lack of notification on the display 🤔

(runout detection can be disabled using M412 S0, if that's the issue)

Out of curiosity: printing from SD card or via USB? I experienced some more or less random filament runout issues (most likely a hardware issue, he sensors are not very reliable) which got better with increased error threshold (since 1.5.3 IIRC) and there was some change around runout pause in 1.5.4, too. I didn't use the SD card for quite a while, so wondering if it's actually a simple false-positive runout with lack of notification on the display :thinking: (runout detection can be disabled using `M412 S0`, if that's the issue)

fenugrec commented

2024-12-06 11:12:49 -06:00

(Migrated from github.com)

Out of curiosity: printing from SD card or via USB?

From SD. I tried Cura->USB->print a few times and it failed miserably every time

I experienced some more or less random filament runout issues

Hmm interesting, I'm only aware of the limitswitch that just senses filament absence, but there would be no threshold for that, are you referring to something else ?

Frankly I'm tired of this printer's unreliability. I'm not sure it's entirely the firmware's fault (whether anycubic's or this build), and the lack of error reporting / logging makes it impossible to tell.

> Out of curiosity: printing from SD card or via USB? From SD. I tried Cura->USB->print a few times and it failed miserably every time > I experienced some more or less random filament runout issues Hmm interesting, I'm only aware of the limitswitch that just senses filament absence, but there would be no threshold for that, are you referring to something else ? Frankly I'm tired of this printer's unreliability. I'm not sure it's entirely the firmware's fault (whether anycubic's or this build), and the lack of error reporting / logging makes it impossible to tell.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wp/Marlin-2-0-x-Anycubic-i3-MEGA-S#559