SOLVED noDataReceived error?
On my first test print (of a Benchy) from a SecKit SK-Go2 that I've built with a Duet 2 WiFi, I received the following error two or three times on the first layer:
Extruder 0 reported 'noDataReceived'
I was able to resume printing and it would work again for a few more seconds, but after this happened a few times on just the first two layers, I canceled the print.
Eventually, on a subsequent attempt with a fresh slice of the model from a different slicer, I got a heater fault and noticed that one of the very thin wires to the PT1000 temperature probe I'm using had detached from the PT1000 probe. Obviously, this is a bummer, since I've now got to get a new PT1000 probe. (I may have a spare thermistor I can use in the meantime, but I'm not sure it's worth the effort to wire it up for just a few days.)
I'm assuming that the "noDataReceived" error was related to the eventual total hardware failure -- that the connection was weak and so I was getting sporadic failures that didn't quite trip the full-on heater fault. Does this assumption seem correct, or is there some other probable cause of the "noDataReceived" error that I should be investigating?
I'm not certain about your error message but it does seem likely. DC42 would know for sure. Would help to know what other hardware you have and your firmware info. Post the results of M122 and your config.g.
The "no data received" message is generated when a laser or magnetic filament monitor has been configured using M591 but not connected.
@dc42, the configuration does have an M591 line for a filament runout sensor that I hadn't actually plugged in at that point, so that's likely the cause. I've now hooked up a spare thermistor in place of my PT1000 probe, but I haven't yet had time to do anything else with the printer. I'll be sure to either comment out the M591 line or hook up the filament runout sensor before my next attempt. Thanks for the tip; but as a suggestion: If possible, it might be good to make the error message point a little more unambiguously at the cause.
FWIW, I've now done a test print with the filament runout sensor properly configured and connected, and my temporary thermistor installed. It all worked fine this time. I've still got to fine-tune the printer in various ways, but that's another matter....