PS - I have one PanelDue board fitted with a SAM4S8BA chip that I could be persuaded to part with for not very much. It won't run the standard firmware, but you are going to change the firmware anyway, and I can tell you what changes you need to make to support the 4S8BA because I already did that.

I rather think that it would be easier to have the slicer slice one object, and let DWC and firmware handle the multiple objects feature on the fly. That would make skipping an object a lot easier I guess.

@CaLviNx:

Nah not a fan of automatic updates… how to piss people off in one easy lesson, just look at Microshaft

I'm not talking about FULLY automatic updates, I just say that two simple buttons like "check for updates" and "install update" will be very useful for people.

Ah, sorry. I thought when you said you were testing at 1,000mm /sec you were actually testing under real printing conditions.

By the way, you still don't understand how instantaneous speed change (what has become known as Jerk) works in 3d printers but hey, it's easy enough to set it to zero to test your theory that you can do away with it. Looking forward to seeing a video of your 1,000mm/sec 5g (or as you say in your case 20g) accelerations.

Yes sorry, it's drive numbers not tools that are the issue with DWC. You rightly say that tools are numbered correctly so I have tools 0 to 4 which use extruders 0 to 4 but drives are numbered 1 to 5. So to extrude filament from say tool 0 which uses extruder 0, I have to select extruder drive 1 which is inconsistent and can be confusing. Having said, I still haven't changed from DWC 1.17+2 to 1.19RC? so the behaviour may be different in the latest version.

I believe this is fixed in firmware version 1.19RC6.

This doesnt answer your question but you should check out clearpath SDSK servos it will save you a bunch of headache and yes they are compatible with the Duet or any other board for that matter

No worries, these things are quite versatile. The tuning window (the usable range if you prefer) will be narrow but they can work just bonded to the side of any part that flexes on nozzle contact.

Is there a way to do exactly what you said but for all three axis and all at once and the it auto updates your configuration file. Or would that be a lot of programming. I guess this isn't really a much desired question because not many people change parts on their printer on a daily basis.

My printer is printing absolutely awesome though right now. My next questing is to use a filament thickness sensor that updates your filament thickness live while its printing.

Yep, will give it a go this evening. Also excited to start testing bed levelling using multiple independent Z motors. Hope you have solved your controller issues Tom and can start testing your printer!

The failing ssr is exacly the thing I am after here.

When the ssr fails it will most likely have absolutely nothing to do with the cpu so I guess this will add a safety net that of course is not perfect, but will decrease the possibility of a fatal issue by quite a bit, so I guess the feature is not a complete waste of effort.

Besides this it could also be possible to automagically power down the printer after a print (I guess the ATX function is for that, but the power supplies sold for 12/24 V usually do not have an input for switching them on/off by software).

That's also something that would be nice to have.

I have a mini IR probe, but it has been giving me issues which is why I have mesh bed compensation off and am currently only using it to home. It very well could be the reason for the continuous need to babystep but I have other priorities at the moment.

Here is a similar design that uses a carbon fiber belt.

https://www.kickstarter.com/projects/814534542/blackbelt-3d-printer

I'm looking to support Ian's colour change advance in the firmware some time in the future. When I implement that, it shouldn't be difficult to implement tool preheat too.

It would be good if someone can code support for RRF gcode flavour in Cura including using G10 and relative extrusion, and submit a pull request.

There is a GSoC project for 3MF support for Slic3r

The M557 command should normally be put in config.g not in bed.g. If you put in in bed.g then the grid won't be defined until you run G32.

Firmware 1.19 will include manual delta calibration and mesh bed compensation facilities, supported by new features in DWC and PanelDue.