@ar300 here is a link to some of our papers. The videos are awesome. We have a few more papers lined up for the next few months.. https://www.sciencedirect.com/science/article/pii/S1359645417308170

Yes, that is right. With 51200 steps/rotation and 200000 steps per second it takes 0.256sec for a single rotation (or 3.90625 rotations / second). And 200kHz is the limit as min duration for the on period is 2.5usec and off period too 2.5usec so 5usec for a period == 200kHz. What can I suggest reeeeeeaaaaly depends on your use case.. It is for start question why you need 51200 steps? If you are trying to get resolution out of it, forget it, you are not getting any better resolution with 1/51200 then you get from 1/16, even worse, as those 51200 steps are not evenly distributed troughout move of a single step but are rather grouped around somepoints, and repeatability does not exist (you are like 5000 steps +- there for repeatability) .. on the other hand, if you have issues moving heavy load, get longer motors that can deliver more torque, don't rely on microstepping Anyhow, for the "cheap mid current drivers" I love the leadshine closed loop ones .. for e.g. I have some experience with 6A HBS57, I don't have enough but so far I love it, on the other thread there's HBS86H, an 8A closed loop driver ... both are iirc 200kHz too but are closed loop so you can expect some precision and some repeatability .. As for high speed high current high microstepping drivers, I can't suggest none, not my price range

Drew up a first concept for the 4th axis extruder mount:

@dc42 about: Pullup resistors are no longer enabled on endstop inputs used to connect filament monitors when they are configured using M591. This change feels like it is a severe breaking change that requires hardware (!) changes to a previously working printer. I'm not sure, but I think there has been no similar case in the past (or at least non that I remember) where a firmware update required hardware changes. Changing my config and adapting macros after upgrading a firmware is fine - but having to change hardware feels like a very invasive software update. Is is possible to only disable the pullup-resistor based on the selected filament monitor? Or have it available as a new parameter to M591.

@timothyz This is the first line of code made with S3d: G1 E-1.8000 F3900 ; feature skirt ; tool H0.320 W0.720 G1 Z0.320 F1200 G1 X214.920 Y212.896 F8400 G1 E1.8000 F3900 G1 X217.896 Y209.920 E0.4031 F2520 G1 X232.104 Y209.920 E1.3610 G1 X235.080 Y212.896 E0.4031 G1 X235.080 Y227.104 E1.3610 G1 X232.104 Y230.080 E0.4031 G1 X217.896 Y230.080 E1.3610 G1 X214.920 Y227.104 E0.4031 G1 X214.920 Y212.896 E1.3610 G1 E-1.8000 F3900 G1 Z0.640 F1200 G1 X215.640 Y213.194 F8400 G1 Z0.320 F1200 G1 E1.8000 F3900 G1 X218.194 Y210.640 E0.3460 F2520 G1 X231.806 Y210.640 E1.3039 G1 X234.360 Y213.194 E0.3460 G1 X234.360 Y226.806 E1.3039 G1 X231.806 Y229.360 E0.3460 G1 X218.194 Y229.360 E1.3039 G1 X215.640 Y226.806 E0.3460 G1 X215.640 Y213.194 E1.3039 I can't really find anything strange here..

I'm printing for 10+ years and I never had the idea to put 0,0 to the center of the bed ... it makes so much sense when someone opens your eyes .. thanks!!

@tcmoore87 said in Firmware retraction for single tool in multitool setup?: So that being said I cannot "uncouple" the extruders from the tool while mixing for the purpose of retraction and would need to use each extruder as a separate tool and thus would change my mind about this setup and may go back to the 4 separate nozzle I had before. @deckingman Thank you for your help so if I confused you with what i was asking. Read my post above because I might have an answer. But "normal" slicer retraction should only retract one filament (although it's a long time since I used it).

@Phaedrux said in Mesh Compensation Undercompensating: It would help to know what firmware version you're using. 2.03RC5. I tried updating to the final version a while back, but had problems and downgraded. I don't remember why. I've figured out the most of my issue with it was mechanical, but even after fixing that it still doesn't seem to compensate enough. I don't have time to mess with it right now though, so I'll have to use manual leveling until I can fully diagnose it. Thanks!

Hi, I've been giving this some thought. I don't think config.g is the best place for T0. You really should find the place that will always execute the T0 command at the start of a print. Otherwise, if by chance you deselect tool 0, you will get the error again. Frederick

Configuring pressure advance should eliminate the need for wipe anyway.

Thanks, please keep me informed. If I don't get any other bug reports for 2.04RC4 then I'll turn that 2.04RC4+1 into 2.04 final release.

What firmware version are you using?

What type of bed is it?

I'm always astonished at how much dust builds up in my simple dust filter.

Not having the computer near would be an issue yeah, although i would attach it to the Raspberry Pi. With respect to RRF3, conditional g-code and variables

@nhof said in remember password: You can just set the password to "" and it will log in automatically with no password to enter. /me embarrassed that I have not tried it thanks!

@Mike Thanks for the reply. I will be going with the youprintin3d.de version, as it should be arriving tomorrow

Thanks for your report - it's on my list to investigate.