I did notice the bolts holding the faceplate onto the main mount are a bit loose. I’ll need to remove the extruder so I can tighten the bolts back down. I’ll probably add some blue loctite to help hold things together.
Ryan has the Plus 4 and I have 2 Q1 Pros. Both of mine have been serious work horses. I haven’t seen any complaints out of Ryan with his Plus4 either. And with the Qidi printers you can still do skew correction if you want and you don’t have to do the cloud stuff to send prints wirelessly. I am really wanting to pick up a Plus4 as well, I am just waiting to let them come out with the AMS for it and hopefully pick it up as a package deal.
It’s his posts about the plus4 that made me look at them. Cheaper than what I built the mp3dpv4 for and all the same features. Slightly less build volume, but only in the Z direction. Although it doesn’t do the auto-bed levelling. I saw one review that talked about pushing the bed all the way to the bottom to level it before printing. Not sure how much of an issue that really is.
It does look pretty interesting. I hope their AMS is reliable. The Bambu one has seemed to get really good reviews.
My Q1’s didn’t do it from the factory, but the z_tilt settings were already in the config so all I had to do was add it to the print_start macro and they do it every time now. They claim it isn’t needed, and it probably isn’t, but I like having it on lol. They also do auto Z offset and so far my first layers have always been spot on.
Yeah no complaints. You can have it do a 2 stepper tilt, but so far it has not been needed. Very accurate for me out of the box.
I think I am going to get rid of my 6 V4’s, someone locally is sure to want a print farm for a good price and build one more V5 (already have all the parts) and buy another PLus4.
If for some reason their AMS is not good, there are a few other option these days, like the box turtle. I only need one for empty spools.
I ordered some more GT2 belt. What I’ve discovered is that one of the core belts isn’t quite long enough to get a good grip behind the aluminum endplates I designed. I’m going to cut new belts with a little extra that I can pull on to help snug up the belts before I use the bolts on the front to fine-tune. I also recut the end plates to help facilitate this.
I’ve finished up a few outstanding projects in the shop, so I’ve spent the last few weeks cleaning and organizing.
At the end of all that work, I finally got around to installing the new belts into the printer. I also made some more modifications to the two clamping pieces I use to hold the belts in. The belts are much more secure on the core now, so them slipping out should be minimized.
I also took the time to change how the X end stop wires connect to the switch. I soldered on a lead to the switch and put a locking connector on it. I kept having issues with the little baby spades popping off of the end stop.
I did some test ‘homes’ and everything looked good so I started doing some quick wire management and discovered that at some point I broke the wires going to the thermistor on the hot end. New ones on order, but testing the printer will be delayed until Tuesday now.
It’s for the better, I need to redesign the to cover for the new aluminum core so I can attach some zip ties to it for wire management. I didn’t even think about the fact the new core doesn’t have the same mounting holes as the last iteration.
Just to re-iterate. The printer printed great with the 3d printed PETG core that was originally designed for it. My only issue and the whole reason I went down this rabbit hole is because printing ASA was causing the PETG core to soften and cause issues with the huge 120v heated bed I have on the machine.
Unrelated to the core changes, but I think I finally got my Octoprint to stop freezing too. It’s a combination of installing the klipper sonar on the raspberry pi and disabling ipv6 on the wifi devices.
Something to do with ipv6 and dhcpcd service was causing the service to crash when renewing the dhcp release. This caused the entire network stack to hang on the device and make the web UI unalive. Eventually the service would restart. I only saw this because I happen to watching the logs for something else when it happened this morning.