Hey guys. About a month ago i was finally able to get my printer to a good working state - or so i thought. I started printing smaller things without issue, now I’m beginning to push the boundaries a bit and print bigger. The issue is, I’m starting to get later shifting. The shifts always occur in the Y axis, where I’m using a Nema 23 geared down with a 3:1 reduction, which drives a shaft and two g2 belts to slide a gantry (I can post photos if needed).
At first, I thought this was a mechanical issue. My print head sits very close to the build plate (only a couple mm higher than the lowest tip of the nozzle), so I thought some portion may be catching, but the Nema 23 is pretty tough, and I have to apply quite a bit of force to cause the gantry to shift (and even when I do that, the belts slip before the motor skips).
Most recently, I’ve decided that maybe the motor is getting too hot and is not behaving optimally, but I can’t imagine it’s getting that hot without causing any damage or permanent flex to the ABS mount it’s bolted to. Plus, I’m only running it at 1000 - 1200 mA (the motor is rated for 2 or 3 amp max, I believe). I would increase the current, but as I’ve said already, the belts slip before the motor stalls, so I don’t think adding MORE torque would really do anything.
Does anyone have any ideas? I’m lost and it’s starting to get frustrating because all I want to do is print big! Haha.
Thank you in advanced for any and all help (and I apologize for the super long write up)
Best posts made by wcj97
-
Nema 23 problems
-
RE: Difference between DuetWifi and Duet2Wifi?
Got it! My machine is now running 3.0. I had to revert back to 1.19, but the second time around I was able to successfully update everything. Time to update my config file and start playing around. Love the new WebControl design, btw!
Thank you everyone for your help!
Latest posts made by wcj97
-
RE: Supporting multiple configurations on a single Duet
@dc42 was looking at this thread and was curious if this feature got carried into the newest versions of RRF, most notably version 3.0 and on. I'm testing out the possibility of wiring 2 printers to a single board (mostly for testing purposes), and I've found that it was easy to just create a macro to change certain portions of the config while the secondary printer is being run, but things like homing files and the like aren't so easy. The separate directory as you've stated would make this much easier to implement.
-
RE: Terminate Move after commanded retraction reached
@dc42 Could the new conditionals be used to accomplish this? I've just started to add them to my macros and things this evening. Would it be possible to say something along the lines of:
while sensors.filamentMonitors[0].distanceMoved <= 300 G1 F600 E-25
I'm still learning the syntax and what all of the implemented object models are, but is there a way I could make that happen?
-
RE: Terminate Move after commanded retraction reached
@dc42 It's fairly reliable as I've tested it so far, but there is always a chance that the filament will drag a bit when being pulled from the extruder and won't retract the full distance, or there may be a bit of extra friction or resistance here and there that may cause the secondary extruder to slip a bit. If I can ensure that the exact amount of filament is retracted then not only can I prevent massive purge blocks, but I can make sure my filament swapper works on a closed loop and is reliable and repeatable. The swapper will cut the filament, but if there is still a meter of filament in the bowden tube on a switch, it has no way of knowing that it has to purge that much material from the nozzle before moving on with a color change.
In short, I just want to ensure that it works perfectly every time without any major changes in consistency. I could find other ways around the problem, but they require either additional hardware, or a bit of manual entry.
-
Terminate Move after commanded retraction reached
Hey guys, I just installed a filament sensor on my bowden line between my printhead and a filament switching system I've got set up (similar to Prusa's MMU2.0). I'd like to use the filament monitor during prints to check for filament out and clogs and whatnot, but I'd also like to use it when I swap filaments as a sort of endstop.
There is about 1 meter of bowden line running between my filament swticher (Proteus) and my printhead. I have a secondary extruder at Proteus, as well as a primary direct-drive extruder at my print head. When I swap filaments, I need to ensure that the filament retracts a fairly specific distance so that the filament swapper doesn't get caught up on the filament, but also so the filament doesn't retract so far that the secondary extruder doesn't pull the filament passed the drive gear, which would prevent it from being automatically loaded again. I thought I could use the H parameter in a G1 command to tell terminate the move when the right amount of filament is retracted, but that doesn't seem to work without an actual switch. Is there a way I can tell the printer to, say, retract the filament until the filament sensor tracks that 600mm of filament has been moved?
Thank you in advanced!
-
RE: Extrusion Control on Web Console
I'm having the same issue since I updated from RRF 3.0 to 3.01-RC6 and to Web Control 2.1.0
-
RE: Z Babystepping reverting after ~2 sec
@Phaedrux That's it! I did some more testing today and found that the babystepping works fine for a few steps, but starts undoing itself after the values become a bit more extreme (~200-300 microns). I didn't realize that the axis minimum still affected babystepping values. Thanks again for helping me diagnose!
-
RE: Z Babystepping reverting after ~2 sec
@Phaedrux DWC using the built in buttons. I don't have a PanelDue unfortunately.
-
RE: Z Babystepping reverting after ~2 sec
@Phaedrux Nope still doing it
-
RE: Z Babystepping reverting after ~2 sec
@Phaedrux RRF 3.0, and all webserver related things were updated to the most recent version just a couple weeks ago.
-
Z Babystepping reverting after ~2 sec
I've been trying to run a large print of head straps for some of the new PPE that's been going around the 3D printing community, and because they're taking up the entirety of my almost 500mm x 500mm bed, I've found my bed probing to be a little less accurate than I'd like. Usually this wouldn't be a big deal, but my Z babystepping doesn't seem to be working (or holding I should say). During the print, if I send a babystep command, I can see my ballscrews rotate to compensate, but after about 2 sec, they rotate back by the same amount. I thought maybe I was just seeing the printer adjust for a change in the height map, but it is clearly doing this after any babystep command I send. If I send 4 babystepping commands, one after the other, I can watch as about 2 seconds later my Z axis hits ctrl+Z and undoes whatever adjustment I made. I thought maybe my motor idle time was set too low, and the motors were adjusting a step and then losing it due to a loss of power, but my idle time is set to 30 seconds, and even right after the controller reverts from the babystep I applied, I can see my ballscrews rotating ever so slightly due to mesh bed, so it can't be the motors going idle.
Is anyone else having this problem? Is there some other line in my config that may be affecting this?
Thank you in advanced!