Great! Thanks! I'm looking at moving to a mesh system as well (Netgear Orbi). My current Asus router allows separate naming of the 2.4 and 5, which I've taken advantage of to date.
@plasticmetal You could also throw the Prometheus system into the mix.
Purging can be done a number of ways. I use 3 different techniques with my Diamond mixing hot end depending on the model I'm printing. If the colour change occurs on layer change, then you can often get away with no purge simply but printing inner perimeters before outer ones. If it's a small model or the colour change happens within the same layer, then it is necessary to extrude some filament. Most systems print a sacrificial tower of some sort but this is often wasteful as the tower has to be printer on every layer change, even if there is no colour change. I prefer to move the head outside the bed and simply extrude into a "bucket" which is less wasteful (in terms of time as well as filament). details here https://somei3deas.wordpress.com/2017/12/06/5-colour-printing-with-a-purge-bucket/
The final approach I use is to advance the tool change point with the gcode file so effectively the filament is changed before it is needed. The easiest way to explain that is to point you to this part of my blog https://somei3deas.wordpress.com/2017/01/06/multi-colour-printing-without-wipe-or-prime-towers/
Thanks. I think ultimately the issue was related to my nozzle being damaged/worn. I replaced it with a micro-swiss hardened steel and also dialed up the grip in the extruder. Between the two, that resolved the problem.
Ahh, that could very possibly be it. I've got a tablet and a PC that I jump back and forth between on a regular basis, and then a laptop shows up from time to time when I'm upstairs checking on a print.
Thanks, anyway to fail the start of the upload if the name is too long? The first time the upload success msg stayed and the error message flashed by and then the file wasn't shown on site. I had to do it 2 other times, once to read the message, and the next to capture the msg.
Yes, see M591 in the GCode wiki. The firmware currently supports simple switch-type filament sensors and the prototype Duet3D rotating magnet filament monitors. I also have a build that supports the prototype Duet3D laser filament monitors.
Ahh. I've been trying to do everything through the config tool, and I've left those settings in there. I seem to remember a fragment somewhere that said those could be deleted after initial set up.
I'll drop those from my config files going forward.
