Firmware 01.07.00.00 installed over the weekend. Coincidentially, my A1 has started randomly report “The Cutter Is Stuck”, pause the print, and purge filament. Occationally it will also run the head on the X-axis over to the cutter push bar on the right, start to cut the filament, decide to not go all the way, run the x-axis back to the purge spot on the left and purge more filament. There is no pattern to this. Sometimes it will go dozens of layers with no issue, or report the stuck cutter three time in one layer.
I have replace the cutter with a new one I had laying around to no effect. Both blades cut just fine. Is anyone else seeing this problem? What could I do to solve this? Maybe rollback the firmware?
Roll back to the previous version you know worked, and see if that fixes the issue. Don’t forget to do a recalibration after rolling back…just to be safe. Hope it sorts itself out.
I’ll give that a shot, but I’m in the middle of an 18-hour print that i don’t want to cancel. I am having to hit Resume quite often to keep it going, so it’s probably going to error out 10 minutes after I go to bed. I caught it’s latest tantrum on video so you can all share in my pain. Video of Error
I just had it happen again, and this time I noticed the Cutter is Stuck error was preceeded by the printer thinking the AMS has run out of filament. This got me thinking that the Filament Run Out Sensor was malfunctioning (which it never has before, so I’m still looking at you, Firmware Update 01.07.00.00) and that’s a Hall Effect Sensor (I think) with a magnet in it. So I took a small magment and stuck it on the outside next to the Run Out Sensor to “help” the little magnet inside. It’s working… For now. I will remort back on the progress.
Strange that it’s trying to cut in what looks like a single material print. Aside from runout to next spool I’m not even sure what would trigger such an action.
This is getting stranger. I rolled back the firmware to 01.06, recalibrated, and got a good print from it, but it did give me one cutter stuck error at layer 3. So I sent another print, and this one gave me two errors, the first one also at layer 3 and the second at about 95% complete. So I sent another print and this one printed perfectly, no errors. No I sent another print and this one COMPLETELY CRAPPED OUT worse than when I had firmware 01.07 installed. So I did a complete factory reset, took apart the part where the filament detection sensor is, inspected the cutter again, and tried to calibrate. Calibration failed. I tried to run a diagnostic through Handy - that failed. It’s constantly being interrupted with cutter errors and cannot do anything.
This error:
HMS_0700-4500-0002-0003
Which according to this Wiki page:
I only applicable to the P1 and X1 series, not the A series as the A series does not have a cutter sensor!
I have a trouble ticket in, but I don’t expect to hear back for a few days, and 3D printing is supposed to be a DIY hobby, so her I am continuing to attempt to do it myself.
Anyone have any other ideas other than my mainboard has suddenly and mysteriously decided to think it’s a P1 and has a cutter sensor?
Are there loose fragments of filament stuck in the cutter area?
Is it worth trying to blow the dust and debris out or at least brushing it?
If you have the option…do everything on the PC rather than the app (apart from the calibration…do that on the touchscreen). I’d reinstall the firmware that works again, power off for a minute, then recalibrate through the touchscreen. All seems odd but worth a try…maybe even a very small drop of lubricant on the cutter lever pivot point., although the spring is pretty strong. Check you have the cutter aligned and going into the right spot.
Hope you get it sorted soon.
After upgrading my printer to FW 1.7, I have the problem that the display can no longer be woken from standby mode. This means the display stays black, even when starting a new print job. Only a restart of the printer brings the display back to life. Even when the display is black, all printer functions work. Can anyone confirm this experience?