My J1s has been having a problem where the left extruder stops working after an hour or so of printing. I am running with DLMCW’s firmware, v0.0.06, but had to disable runout detection because of too many spurious “Filament runout” errors. With runout detection off, printing will usually be OK, but there are times when the Left extruder just stops advancing the filament. Have have replaced the reverse Boden tubes, but it has not fixed the problem.
When the extruder stops working, it will no longer react to the “Load Filament” command from the front panel control. It appears to respond, and goes to the “Stop Extruding” screen, but the extruder motor does not turn. There is no physical clog, as I can push the filament in, and it extrudes as it should. I have to power cycle the printer to get the Left extruder working again.
I believe this was happening with the standard firmware, as well, but I don’t recall that specifically. I have tried a variety of connection issues, such as re-seating the FFC cable where it attaches to the board inside the enclosure, which seems to help for a while, but the problem recurs.
Other questions… Sounds like your sure the motor is even turning. Has yours always done this intermittently, or is it a thing that’s getting worse? And on which hotends?
If it’s developed over time, I wonder if the FFC’s have gotten fatigued.
I did start getting the spurious runout errors and I also disabled runout prevention until I can find time to troubleshoot that issue. I have looked over every change to the code and I cannot see anything that would cause that, so my next step will be to fine tune the sensitivity of the sensors. Something has to be causing more interference.
Anyway, I have not experienced the other issue in question. That sounds like a hardware issue.
The fact that restarting the printer fixes the problem makes me think it’s a firmware problem. The fact that everything works fine for the first hour or so makes me think it’s a hardware problem. Perhaps some hardware issue triggers a condition in the firmware, that can’t be reset without power cycling?
While fixing various issues, I have twice disconnected the FFC cable from the circuit board. Both times, I had to guess which way the connector latch has to move to release the cable. Both times, I guessed wrong, and the tiny piece of black plastic came off completely. Both times, after careful examination of the part, I was able to get the latch back in place, and doing its job of holding the end of the FFC cable in place. But, it still makes me wonder if that connector is the problem.
It does seem to be getting worse over time, and it is only the left extruder.
The replacement FFC cables have just arrived….and….they are the wrong side! I accidentally ordered 2 cables for the R extruder. So, another week (or two) of waiting for the L cables to arrive.
In the meantime, I re-flashed the standard firmware (2.7.x), and the problem persists.
Now, I’m getting a brand new error: MAXTEMP triggered, Heater_ID:0. I have not seen this one before, and it has now happened several times.
As I have 2 replacement FFC cables for the R extruder, which is working fine, I’m wondering if I can re-fold one so that it is suitable for use on the Left? I was thinking of warming it in some hot water, then trying to fold it the other way. I have a set of cables for the left on order, but I want to monkey around a bit while waiting for delivery.
I’m now a little over an hour into a 4 hour print, with a new FFC cable. So far, so good. It turns out that you CAN re-fold a R FFC cable for use on the L side. They actually fold and un-fold pretty easily. I did not have to warm it up or anything fancy like that. The new fold does have to be fairly accurate so that it fits into the channel in the extruder assembly, but it’s not that hard.
Once this print finishes, I will re-flash DLMCW’s firmware, and try filament runout detection again. The frequent erroneous triggers may have been from the failing cable.
Success! A 4.5 hr print just finished without any problems. I have re-installed DLMCW’s firmware, v0.0.06, and enabled “Filament Runout Detection” for both print heads. New (overnight) print starting.
No go for Filament Runout Detection. I started a new print, of over 500 layers, and by layer 6 had a false Filament Runout trigger. So we are now printing with DLMCW’s firmware, but FRD disabled.
