Constant Pause and Parking #907
-
|
Ender 3 V2 - Stock Screen - BLTouch, No End Stop Switch BTT SKR Mini E3 V3 Ender3 V2/S1 Professional Firmware 20230312 I am really clueless at this point and could use some help and\or guidance. I just upgraded by mainboard after the previous one stopped working and for the life of me I cannot get it to work correctly. Any print I start, from Octoprint or Manually, immediately pauses and parks. The Endstop diagnostic screen shows that Z_Min is staying in the TRIGGERED state instead of OPEN. I thought this meant the BLTouch was wired wrong, but Z-Homing and Leveling\Mesh Creation all work without an issue which implies the BLTouch is working normally. Further, I have no other Z Endstop plugged in to trigger it. The BLTouch is currently using the 5Pin JST connector on the board. Any Thoughts on what this could be or anything else that I can check? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 11 replies
-
Check your filament runout sensor (filament settings menu).
No, BLTouch has his own connector, Z_MIN refers to the Z_MIN end stop switch and it is not used when the firmware was set to use a BLTouch. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, Should of mentioned that. The filament sensor was one of the first things I checked and I have verified it is working as desired. The same behavior is seen with it disabled as well So just to confirm for my own knowledge, does it matter if the z_min is in the triggered state? I knew it was not used, it just struck me as odd to see it triggered when nothing was plugged into that port. Is there anything else I can do to confirm what is causing the pause and park behavior? What other items could be causing it if it is not the Filament sensor or the z_min? |
Beta Was this translation helpful? Give feedback.
-
|
The Octoprint terminal should give you the reason of the pause. |
Beta Was this translation helpful? Give feedback.
-
|
I am not seeing one looking through the terminal results, but maybe I am just missing something. I disabled the Filament sensor to be sure, then replicated the issue twice. |
Beta Was this translation helpful? Give feedback.
-
|
Looking at that log it's pausing because your nozzle temperature is reporting its only at 125C which is below the minimum extrusion temperature and resumes at 180C (which is probably what the minimum extrusion temp is set at in the firmware) |
Beta Was this translation helpful? Give feedback.
-
|
Was hoping it was going to be that simple. Upped the set point to 200\60, preheated, verified Filament sensor was disabled and then started a print. Same behavior, It homes to Z Axis correctly, then goes to the start position. As soon as it does that it pauses and moves to the Park position with a LCD Message prompting for PurgeMore or Continue. As far as the normal state of the z-stop, it should be OPEN as well from what I understand. I just do not know why it shows otherwise when the port is empty. That is why I kept thinking it was the problem. But if the firmware ignores that state when a BLTouch is configured, then it does not sound like that is the issue. Any other idea on what I can test or rule out? Will be trying the BTT Firmware tonight just to rule a hardware issue out. Not sure if I want that to fix it or not as I really don't want to use that firmware. |
Beta Was this translation helpful? Give feedback.
-
|
Not having the SKR board in my collection i dont know what may be wrong, however i would check all the connections to the board just to make sure the right component is plugged into the correct socket. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @Crazy-Charles for the confirmation about Z_MIN. |
Beta Was this translation helpful? Give feedback.
-
|
@mriscoc Same behavior from Octoprint and the SD Card. Thought about compiling my own, but still can't point at one thing that is causing the behavior that it would fix. |
Beta Was this translation helpful? Give feedback.
-
|
Please, post a picture of the end-stop diagnostic tool. |
Beta Was this translation helpful? Give feedback.
-
|
So, this is interesting. The M412 disable command made no difference but I realized as I was testing that I had only attempted to print my leveling print this entire time, which has worked before. Changing the print to a small item and it started to print without issues. I had to update the Z-Offset value as the print was way to high, but it was working. I have inspected the GCode of the leveling print and nowhere in there does it have anything that should trigger this behavior. The only large difference is that the leveling code runs a straight line around the edge of the bed while the small print is all in the center. The printer is now working with a few minor leveling issues. At this point I can confirm that the filament sensor was completely unrelated, so the purge message it was triggering was really confusing. @mriscoc @Crazy-Charles Thank you both very much for the help. Still confused as to the the root cause, Maybe the offset? But you got me pointed in the right direction, which was more than I was getting myself. |
Beta Was this translation helpful? Give feedback.
So, this is interesting. The M412 disable command made no difference but I realized as I was testing that I had only attempted to print my leveling print this entire time, which has worked before. Changing the print to a small item and it started to print without issues. I had to update the Z-Offset value as the print was way to high, but it was working. I have inspected the GCode of the leveling print and nowhere in there does it have anything that should trigger this behavior. The only large difference is that the leveling code runs a straight line around the edge of the bed while the small print is all in the center. The printer is now working with a few minor leveling issues.
At this …