The Diamond 5 colour ("FullColor") Hot End



  • For anyone who might be interested, I've just written a post on my blog detailing my findings, thoughts, ideas and other ramblings about using a Diamond 5 colour hot end and some other general mixing hot end related stuff. There isn't much that is specifically relevant to Duet as I've pretty well covered that in other blog posts but for anyone with an interest in mixing hot ends, there may be something worth reading. You can find it here https://somei3deas.wordpress.com/2017/10/04/the-diamond-5-colour-fullcolor-hot-end-and-other-related-stuff/



  • Great right up Ian, very interesting reading.



  • This is a really excellent post, thanks for sharing in such detail.


  • administrators

    Thank you for the great write up,



  • Thanks Ian! Very informative and helpful, especially for us mixing guys!



  • Thanks for the feedback guys. These things take a fair bit of time to put together so a bit of encouragement is always welcome. A quick gander at the stats for my blog shows that 164 people have viewed that post so far today, but with zero comments or "likes" it's hard to tell from stats alone if I'm wasting my time or not.



  • I didn't see comments where activated! I posted an answer on reprap forums; I can re-post it on your blog, if you want.

    BTW, I'm working on the idea of the extruder gantry driven in a smoother way, and for the V-Python simulator I'm writing, I'm looking for a simple G-Code parser… For your Diamond python scripts, are you using a public parser, or is it something you wrote yourself?



  • I'd be interested to see your script for parsing the gcode to swap tools.



  • @fma:

    I didn't see comments where activated! I posted an answer on reprap forums; I can re-post it on your blog, if you want.

    BTW, I'm working on the idea of the extruder gantry driven in a smoother way, and for the V-Python simulator I'm writing, I'm looking for a simple G-Code parser… For your Diamond python scripts, are you using a public parser, or is it something you wrote yourself?

    Don't worry about putting comments on my blog - it's just something else I'd have to do in terms of moderating.

    One advantage of having the extruder gantry precisely following the hot end is that there is no movement in any of the cable connectors so I don't get issues with broken wires like I used to occasionally get. I think the way it is is just fine. If it doesn't precisely follow the hot end, then sooner or later it'll have to be "jerked" (in the physical sense) to catch up. If the frame is rigid enough, then even throwing 4 kgs around like I do, isn't a problem and there are no print artefacts as a result. Personally I think you are trying to fix a problem that deosn't exist but hey, it's your printer.

    I don't even know what a parser is 🙂 I just use Python a sort of semi-automated text editor to post process g-code files. I'm not a writer of code and the only "python" I know is what I've managed to scrape off of internet searches to get done what I want to get done. I know my scripts aren't pretty and a professional writer of code would either laugh or cry if they saw them. That's why I'm reluctant to publish them but they get the job done for me.



  • I understand, but I will do the maths as nice exercice 😉 Don't know yet if I will really use it on my printer.

    BTW, the parser is the part of code which reads the G-Code file, and extracts all informations you need (XYZ coords, speed, extrusion and so), and store them as Python objects (lists, dicts…), so you can process datas. It can be very simple, but to handle all cases (comments, upper/lower case...), it sometimes requires a lot of work.

    I find some libraries, but more CNC-oriented.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.