Are you running a recent version of Repetier 0.92? I had a similar issue that was fixed a while back in the firmware which would cause exactly this issue when running an additional extrusion cooling fan powered by the stock fan connector.
Then it's probably safe to say that you have a broken wire somewhere.
I'll bust out the voltmeter and start testing connections. If anyone else has experienced this problem please feel free to share your experience. I've had nothing but bad luck with this machine. First 2 broken bearing mounts, then filament Cartridge not registering on the da Vinci software, my glass bed is not perfecly flat, and I still can't get perfect circle prints. This is just the icing on the cake.
I upgraded to .92 last week. When printing off of the sd card I kept getting the same problem. Small prints would be ok, but longer prints the heaters would shut off. The last few prints I printed from pc. Then the heaters stayed on. I had .91 installed for a month with no problems and made no recent hardware changes.
I was also printing off the sd card. And my print was large in comparison to everything else I've printed. That could have been my problem. Once I get my machine back up and running I'll see if that works. Thanks for sharing Chris
I have made several more prints and still get the def error. I've made several 4 to 6 hour prints that worked. A print can fail and I retry with success.
When a print fails I usually usually power cycle the machine in less than a minute. I only touch the power and the display shows the correct temperatures. I checked the connections and they are all tight. Possibly a short, but everything still work a minute later?
A month ago I had the connector for the extruder heater fail. As a temporary fix I used wago quick connects and wrapped with tape. I double checked and they were still secure. When it failed there was no error, just temperature didn't change.
Looking at the machine the connector for the temperature sensor looks cheaper. Has anyone had a problem with it failing?
Trying to figure out if this is a hardware or firmware problem. It first happened after my upgrade from .91 to .92. I like the menu layout of .92 so prefer not to downgrade.
0.91 based does not have decoupled feature that is why never happen before.
any way last week I imported in 0.92 several changes for decoupled feature and temperature reading, and a compilation define has been created to enable/disable decoupled feature
it may help
I had 3 def errors today. The first 2 were between 1 to 2 hours before error.
Trying to narrow down the problem I decided to start with the bed heater. I started the print then disabled the bed heater. I had a def error halfway through the first layer. Restarted and now over an hour without error.
I have been running at 270c but some times turn it down to 260 and still get the error. Would the temp of the extruder cause problems with the temp sensor?
The disable decouple feature seems like it would bypass the error. Would it override a safety? Earlier when unplugging the machine from repeater host I caught it not stopping at temperature and climbing. If there is a real problem with communication in the machine I would rather it stop a print before destroy the machine.
So far with some upgrades it turning into a good machine. Several corners were cut to make it an affordable starter machine. There have been several failures of the extruder heater coupler. Are there any other parts of the wiring harness that are weak links?
the few times I got decoupled errors was when my connector was loose or fan was not working properly.
yes disabling feature bring less safety but put same level as 0.91.
additionnaly 0.92 has watchdog so if printer is unresponsive it will reset which is better than 0.91 for safety.
also if you add the usb patch, this will avoid to lock printer if usb connection is lost, so temperature should be always under control.
That said 270 is pretty for davinci from temperature and power supply point of view which could affect the temperature stability and generate defect sensor issue.
I've upgraded to using octopi for printing. There is watchdog does that work with .92 firmware? If that means safe I'll upgrade and disable. Just don't want to override the machine saying there is a problem if it really is.
A few times I did get a jam I unplugged the main extruder harness and pulled out the extruder. Recently I noticed def error. Before I could unplug, fix error, plug back in, then print.
I've been using "premium filament" from ebay that split and tore apart at 240. I read for that kind of filament 270 and up worked better. Recent prints have no splits. Not ruling my error out but so far hotter is better. Also Covered top opening handle with some clean socks to stop heat loss. The sides of the printer seem warmer. Maybe combination helped make prints work.
I've the same problem ("DEF" on LCD screen and loss of heaters) with .92 on a 1.0 fairly early in long SD card prints with PLA twice recently. I'm using an extra fax blowing at the nozzle with all doors open, and with the extruder set at 220, the measured temp was varying between 211 and 217. I've been playing with the extruder temp settings, and did not have this problem with severe successful but relatively small PLA prints. Am I getting the error because the measured temp drops too low? I've never had the error with long ABS prints and the extra fan off.
I too am getting the "def" error on .91, but I have recently switched to an E3D V6. Did I possibly wire something up wrong or break something? I can see temps in Repetier host, but the Extruder temp is saying -20 ambient. (Haven't changed the Thermistor Tables)
Yes bad air flow control can generate the error - especially if your extra fan is blowing on nozzle/extruder instead of filament/ extruder/model
yes if your thermistor detect -20 it generate sensor error as under -10 it is considered a problem at ambient temperature - you have a connection issue or you changed the thermistor by a one which need a new table
How do I change the thermistor table, as I can't find it in repetier host. Or is the option somewhere else?
In FW - several threads talk about this