I'm sure there are others, but while (my experienced with) the IR sensor is reliable in the stock form (with the MMU is a different story) there can be false events. In what case would you not want the filament to unload on EOF. The current behavior seems a wrong design to me. Without direct evidence of someone familiar with the printer being there when the event happened, it's hard to jump directly to a firmware/hardware issue (especially with the results of "event 2") when other possibilities exist. it clogged close to the end of the filament, but before the sensor was tripped). If it had been left for a significant amount of time and the nozzle was still hot, then it's likely that it thought it was still printing (e.g. After you press the knob to start the unload process it will then pause the process while it reheats the nozzle. That prompt does not timeout (I've had mine wait about 36 hours (ran out of filament before the new spools arrived)), it simply turns off the nozzle heat if it is idle too long. If it detected a filament runout, it would have prompted for the unload. I assume it was requesting the knob be pushed, but I can't be 100% sure of that. BTW, I was not there when the event 1 was discovered, so I don't really know the state of the display at that time. Posted by: I was not attending the printer at event 1, I must have received the prompt and when no action was taken, the filament did not move out of the hot end and cooked/burned (I assume). Why does it need to be attended? Also, if EOF is the state, why keep the heat on? At the very least it should time out on the prompt and turn off the heat. They said no, but that I could request as such in github. I asked support if an unattended unload was possible when the sensor detected EOF. Since I was not attending the printer at event 1, I must have received the prompt and when no action was taken, the filament did not move out of the hot end and cooked/burned (I assume). In event 2, I was prompted to push the knob to unload the filament. However, the filament did continue to burn on event 1, so it would seem the heat did not turn off. That seems to have not been true per the results of event 2. The fact that the hot end was clogged on event 1 I intrerpreted as EOF not detected, a common event on my mk3s. Event 2 showed that the sensor detected end-of-filament (EOF), paused the job, and set the codes to 0. Event 1, I misinterpreted as the sensor not working. Event 2 demonstrated that the sensor worked perfectly. Event 2 was when I tested the sensor (after clearing the hot end). Event 1 - the unattended job that clogged my hot end. I'm sorry, I did not report the events very clearly. It leaves the heater on initial with the expectation that you are going to change the filament promptly and don't want to have to wait for it to reheat. There is a set timer (not configurable as far as I'm aware) where the hotend heater will turn off if it is idle too long (I want to say either 10 or 30 minutes) and that isn't long enough to cause issues with PLA. Another good test of more real world conditions would be to start a print and once it's been going for awhile, use your flush cutters to snip the filament just above the extruder and watch how it reacts.Īs far as the process goes, when it pauses, it asks you to unload it first (I assume to prevent a false runout from letting your filament wind back and cause a tangle?). Given that you report manual testing works, that would seem to indicate the IR board itself is probably healthy (still could be heat or movement related which you wouldn't see in a static test). Are you 100% sure that the filament passed the steel ball? It could be that the jam came first and the filament simply hadn't advanced far enough into the extruder to trip the sensor? Have your been printing much since the last time you took apart the extruder? Maybe there is some debris that is/was preventing proper operation of the sensor mechanism? If it didn't pause the print, that would indicate that either the filament sensor is disabled (Settings menu) or it for some reason didn't recognize the filament had run out. If it detected the run out and paused the print, the problem could have simply been that there was something about the end of the filament that prevented it from backing out (e.g. These two statements seem to contradict each other.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |