It may be fixed. Time will tell. I’m on my 3rd print job and at 45% complete it looks good.
- it is not a bad linear module
- it has nothing to do with print speed
- it is not a nozzle not properly seated
- it is not ‘jerk’ or ‘jog’
- it is not the build plate moving
- it is not a curling issue
- it is not an overheated linear module
- it is not a stepper motor overheating
It is most likely a glitch in the matrix. Following a recommendation from Facebook I carried the printer up a flight of stairs and set it on the floor beside my computer and did a direct USB connection followed by doing a factory reset. I then first installed the latest firmware (v1.15.23), followed by deinstalling Luban 4.7.3 from my desktop. Then I performed a file and registry cleanup on my computer and reinstalled Luban 4.7.3. Next, I carried the A350 back downstairs and put it back into the enclosure and did a complete calibration and alignment. Then it was time …
I opened Luban and loaded an stl file that had printed very well in the past but wasn’t working recently (see pictures above). I created a new gcode file and sent it to the printer. As of now I’m on the 3rd different print job and all have been successful. I believe I may have fixed the glitch in the matrix.