Open minameismud opened 2 years ago
Don't have any comments related to your probe errors. However about your thermal runaway, it could be that your heat sensor in the hot end is damage (Granted you have the stock Aquila thermistor) there has been a reported issue that the thermistor has been torqued a little bit too much from the factory and has led to damaged leads to the sensor. I would double check that your thermistor wires are not damaged and/or the screw is not crazy torqued down. If so replace it. Also I would run a PID tune on your hotend to see and do another print to narrow down your variables of whats causing this. Cheers.
I was running the 1.3.5 ManualMesh-3x3-N32.bin firmware through OctoPrint on an RPi4b for months with zero issues. No shutdowns, no runaways, no errors of any kind that weren't my fault for bad slicing or inconsistent leveling. Just installed a BLTouch (genuine) a few days ago and the 1.3.5 BLTouch-4x4-N32.bin firmware. Immediately following the first print, I got an M112 during the Unload Filament procedure (initiated directly on the printer) while the hotend was heating. Shut off the printer, turned it back on, hit Unload Filament, another M112. Repeated a third time, third M112. Shut it off, turned it back on, and manually performed unloading (manual hotend temp set, waited, disabled steppers, cranked the extruder backwards by hand). Since then, Unload Filament has worked fine the dozen or so times I've tried it since. Then I started getting Probing errors during print startup. My startup gcode in Cura:
Just had an emergency stop during printing due to thermal runaway. As stated above, I've never had thermal runaway before. I'm printing PLA at 200/67, and neither temperature as reported on the screen looked any different from that. Restarted the printer, restarted the print, and I got another probing error during startup. This BLTouch-specific firmware is super buggy for me. I've not customized anything in the header files - the only printer settings I've changed have been through the screen.
As a fellow software dev, I get that this isn't a super helpful ticket (consistent repro steps, etc). Maybe the BLTouch 4x4 just needs a recompile? I'm going to try the BLTouch 3x3 to see if that's any better.