That would be also my expectation.
The moving wires are the heatbed, but this runs over a SSR and I do not think a short circuit would cause this behaviour over the SSR.
I removed also the bed Thermistor (but did not heat then the bed) and still the issue.
So could be the wires running from top to the printhead carrier. I renewed already the connector to the IR probe, as this looked a bit suspicious.
As it looks as I'm the only one having this issue, it mustbe something with my build ?.
I will be next week on vacation and afterwards I replace the Duet 0.8.5 by the Duet Wifi. Lets see if this changes anything in this behaviour.
It is a pitty that the error occours only from time to time, making trouble shooting much harder.
I will report how it goes.
I gave up on the Tunell monitor as I didn't want to risk the electronics on my Duet.
I designed a simpler filament monitor using an optical sensor and a housing to hold the filament in the path of the sensor. You could do the same thing with optical or mechanical endstops. It will get you the filament out detection but not the tangled filament or clogged nozzle detection.
Thanks for the update, Leon.
The only acrylic I have to test the IR sensor against is black acrylic, and the sensor works well with that. The usual issue for the IR sensor with transparent bed surfaces is that the reflection from the back surface interferes with the reflection from the top surface, and this causes the trigger height to depend on the relative strengths of the two reflections. Your acrylic may be opaque enough to avoid that.
I agree on this one, I just did not want to bring it up. If the standard blower was used, it is unlikely that it can cause a drop of 10C. My guess is that either PID settings are wrong for some reason, or, most probably, the Rostock hot end has developed issues. So, going to a more standard hot end such as E3D would solve the problem.
I have seen other complaints about the 10C excursion limit, so perhaps an ability to temporarily override it could be useful, but I agree that fixing problems makes more sense.
Personally I'm a bit puzzled by all of this. I don't want to upset anyone here but aren't we asking for the firmware to be modified to compensate for some defect in the printer design, when in fact we should be looking to rectify the root cause of the problem?
Very sorry for the delay.
I tried to reflash the firmware but the board is not even detected by the software. Tried from another computer on both Windows and Linux, still no sign of life.
EDIT : nevermind, I actually managed to reflash the DuetWifi firmware, also I reflashed the PanelDue's itself with its own firmware via bossac utility.
Everything seems to be functional, will test tomorrow with stepper and heatbed wired.
EDIT 2 : Everything is working as expected. My metamorph 3D printer project can now continue
All the hardware-PWM-capable output pins are assigned to heaters and fans. Currently you can't reassign the heater pins without recompiling the firmware, because the associated PIDs are liable to overwrite anything you write to them. I intend to introduce an M code that would let you specify now many heaters you have, thereby allowing the remaining heater pins to be used as GPIO pins.
The Duet WiFi expansion boards we are working on will also provide additional PWM channels.
I will report on that. It definetly doesn't like nozzle crashing into it.
I upped the temperature with edge filament to 240°C and I am doing a print tonight first layer adhesion is actually better ( I used too low temperatures due to some wrong indication on the e3d sticker spool box and also because I was lacking experience)
I still get a lot of goo around the nozzle which I need to babysit clean every 5-10 layer or so… I wonder what is wrong in my slicer settings. The ngen (colorfab) didn't do that.
problem with the goo is that it detaches and hardens always at the worst place and then you get a nozzle crash...
So, I had the right idea how the axis should work, and after the 7:th combination and switched x & y motor connections I finally found the right settings!
Thank you so much for your patience and great answers to me who´s just starting to understand the in´s & out´s of Duet and reprapfirmware!