@DreadPotato
@sopuli.xyz[SOLVED] Turns out I'm just a bigger moron than I thought. The MAC address of my server had accidentally been flagged in my router for black listing.
As the title says, my proxmox host is apparently not able to reach the internet anymore, not sure for how long this has been an issue, I rarely work on the host itself. It can ping other devices on my network just fine, and other devices can ping it. I can also SSH in to it and access the web interface. My VMs are connected to the internet without any issues. I don't need to access the host remotely/outside my home network, this is just for updating it etc.
I can't see the host under active devices in my router though.
I have been trying to figure why, but so far without any luck.
I've been contemplating switching the rods that my X and Y axis travel on to linear rails instead. The current hardware is double SS rods with SG15 bearings, with an eccentric nut to adjust tension on the rods.
Unfortunately these rods are not evenly spaced on my Y-axis. They're closer together at the back than at the front, deviating with 0.5mm. So the rollers are either too tight at the front, or too loose at the back, meaning the bed wobbles a bit when using the front of the bed, or skips layers due to higher resistance on the rollers when using the back of the bed. I could lower the movement speed, but I would rather fix the actual cause of the issue.
I have some suspicion that the rollers are also not rolling smoothly on the rods and sometimes slip/skip on them instead.
And then I came across the Voron switchwire and Ender3-to-switchwire conversions. Now I'm not really willing to fully rebuild the printer as a switchwire, but changing to linear rails on Y and X axes is not a massive rebuild and considerably cheaper. I would keep the existing threaded rods for the Z-axis.
I would use the hardware I have now (motors, pulleys, belts, bed-mount, belt tensioners) with minor modifications to accommodate the rails instead of the rods currently used.
Are there any caveats to be aware of when using linear rails?
I've been trying to print some things in TPU, using a fairly soft 85A TPU, and I keep having under extrusion.
I've already reduced speeds to max 25mm/s, and reduced retraction. My printer uses a direct drive extruder, and as far as I can tell, it's grabbing the filament just fine. I'm printing at 240°C, using my default 0.4mm volcano CHT brass nozzle.
I'm looking to expand my printer lineup, and have been looking at kits from magic phoenix for both the Voron Trident and the v2.4R2.
Is there any real benefit to one over the other, or is it more a preference thing?
Edit: if anyone know of other kits, preferably available in the EU, I would also like to take a look at those.
I tried printing with PETG yesterday, and I noticed that it intermittently stops moving during the print for a few seconds. It doesn't throw an error or anything, just stops and then after a few seconds resumes as if nothing happened. But this creates huge blobs where it stops. It only happens when printing PETG, not PLA. Could this be caused by a filament setting in my slicer? I'm using prusa slicer. I inspected the gcode and there are no stops, pauses or color changes etc. in it. The behaviour happens both when printing from octoprint and directly from SD card.
Edit: these random intermittent stops are 10-20 seconds long, causing massive blobs from oozing filament.
Edit 2: so it seems to not actually be a PETG specific issue, but rather a model size/speed issue. I can get it running without stops if I just reduce print speed. When I crank speed to 100% I start getting these weird 10-20 second long stops.
So I'm overloading the controller with a lot of gcode commands in rapid succession? I'm running at slightly lower than manufacturer default Max.
SOLVED: the gcode resolution was set too fine, I increased it from 0.0125mm to 0.5mm as described here and the stuttering disappeared.
Why are 3D printers still stuck on stepper motors? Why haven't we transitioned to servo motors with encoder feedback for positioning?
Is it just too cost prohibitive for the consumer-level? We would be able to print a lot faster and more accurately if we had position feedback on the axes. Instead we just rely blindly on the stepper not skipping any steps when we tell it to move, hoping for the best.
I have run in to a strange issue where the X and Y axes don't move to the specified coordinate beyond a certain range.
The steps/unit are calibrated, when i tell an axis to move to position 100mm (using G0 or G1 command manually), it moves to position 100mm, this goes for both X and Y axis...but it seems like it hits a software-stop when i tell it to move beyond 225mm on both of them, which is weird since build plate is 230mmx230mm, and nozzle wipe-pad and Z-offset calibration are located at Y position 240mm-245mm.
The stepper just stops at 225mm even if i tell it to move beyond this point, and if i tell it to move back to 0mm, it positions itself correctly at the starting point. It doesn't sound like any skipping on the belt or the stepper itself is happening, it's completely silent but just stops. I can easily move the bed and print-head beyond this point by hand, and i can't feel any noticeable increased resistance in the movement.
The odd thing is, that this worked just fine a week ago, i haven't changed anything on the config of the printer. It's an anycubic Kobra 2 bedslinger.
EDIT: i can trick it to move beyond the 225mm point by changing the steps/unit, but that messes with the general print size accuracy.
EDIT 2: It seems a FW update enabled SW end-stops, a simple "M211 S0" command from the terminal disabled them again and now it works just fine.