So, to save you the trouble, I figured out what was going on with my acceleration settings. I’ve had the “Emit Limits to G-Code” box checked under the advanced motion ability controls for your printer in Orca, which hadnt done a thing all up until I updated the firmware. After the update it started actually adhering to that setting in the slicer, instead of the firmware settings overriding the slicer settings like it had done in the past, So I unchecked that box/made sure the speed setting for my machine were set in Orca to match what I want them to be in the firmware. This allowed me to print at least, but its still not quite dialed in. Even with my bed level variance as close to perfect as onew can get realistically, or at least that I can achieve realistically, I’m still having trouble printing along the right side of the print bed for some reason. Everything else looks immaculate just running the new expanded bed level mesh that you added, Z offset included. But that right side screws it all up and I have to lower the Z offset to print on that side and deal with the little bit of drag it causes on the rest of the bed, or baby sit it and kinda dial it back and forth a bit during the intial layer, then its fine the rest of the way up. Or at least the very short print I did was fine the rest of the way up. I’ll try something that runs a little higher up the Z axis next and let you guys know if I have any additional problems similar to @stguitar or anything of that nature.
If you’d be so kind as to share the speed/acceleration/jerk settings you’re running on your machine @Iroh3d, I’d be very appreciative. Or anyone for that matter. I’d like to see how far I can push it and still have successful prints, but I’m still in the learning/iteration phase I guess, so some guidance from you guy’s experience would be much appreciated.
I still havent quite figured out how to solve the filament runout sensor problem, but I havent looked further into it. I scrolled up and noticed that I may be missing some of the nessecary code in the “Before Print Starts” G-Code section on Octoprint, that sort of thing. It seems the string of G-Code I added was an earlier iteration, but supposedly that iteration functioned, but the GUI gave people problems and was updated as a result. So I’m not sure why it would be successfully pinging the sensor, yet not functioning despite supposedly functioning G-code prefaces or whatever. But it very well could be that it worked on an earlier iteration of the firmware and not on the newest update or something and I need to change said G-code prefaces to fix it. So far, I couldnt use it without printing a filament guide to take some of the tension out of the filament at a certain point just prior the the sensor itself, so I gave it up till I can get that printed. Not as pressing I figure, I’ll worry about it later. Still, if you have any thoughts about what I seem to be missing here, Idn appreciate them greatly.
Thanks in advance guys!
Live long and prosper🖖