I’ve had a Qidi Q1 Pro for a while now and I really do love it, very minor issues (mostly caused by my tinkering) so far and now I need help from someone that’s a lot smarter than me.
There’s a gesture to auto replace the filament. Problem is, it just does that wherever the head is and makes a mess on the plate. So I had an idea, why not move the head back to the chute and do the filament change there? I added the code for that (including a few wipes on the pad) inside the filament change macros but had to add a home all axies G28 first in order to locate the head and then move it.
That presents 2 problems: 1. When you push go on the screen to change the filament, it heats the nozzle first and then calls the macros. Doing that oozes filament out where it is, still making a mess. 2. I’m trying to experiment with manually changing colors during a print but it calls on that same automatic filament change routine with the homing call which makes it lose its position.
If anyone knows how to change the screen’s firmware and/or knows how to fetch a current position and feed it to the macro (I would add an if statement saying if the location of the head is unknown, home, otherwise proceed) I would be very excited to hear from you!
dual_sport_dork@lemmy.world 3 hours ago
If your Q1 is anything like my previous X-Plus or current X-Max 3, pretty much all of the routines you can run from the touch screen are macros that are defined in your printer.cfg on the machine itself. This is just a text file full of gcode and you can dick with it freely without having to reflash the firmware. The only “fun” part will be figuring out which one of the custom macros it is, since Qidi doesn’t always give them a readable name and they tend to make them random looking numeric strings. I’ll have to take a look at mine when I get home and ensure that the filament load/unload/runout routines are located there, but I’m pretty sure they are.
You can directly edit your printer.cfg through the Mainsail interface within the Qidi Slicer or you can SSH into the machine and get a terminal via which you can mess with things directly (username mks, password makerbase).