https://hackaday.com/2020/06/13/rip-danal-estes-developer-of-multitool-3d-printing-infrastructure

What about just putting an index in front of the fan currently used as tool fan?

I uploaded a short video showing this print:

https://vimeo.com/357503565

An alternative would be to continuously extrude a tiny amount of filament on parked heads…

We (at LOG hackerspace) designed such dual extruder using one motor. It is not driven by a Duet, but it should work.

Here is our design: https://wiki.logre.eu/index.php/DondoLOG based on this one: https://www.thingiverse.com/thing:673816 (we changed a lot of things, leading to a much more simple geometry).

Onshape designs are here: Mine¹: https://cad.onshape.com/documents/ab5e4a91e08de464a68c8fa9/w/d1a6bf327030002f2355aebe/e/4fc76c1855ace35a39166ba3 (using aluminium plates) and a derivated, made by a friend: https://cad.onshape.com/documents/44cc3aa0e2de59f4440a6e4b/w/58c86854d8b2aa8e76983bb9/e/82ef35419fb25e023c2c8b7d (using PMMA 6mm).

Feel free to ask if you want more details. Note that the second design is now working (see https://piwigo.logre.eu/picture.php?/1139, https://piwigo.logre.eu/picture.php?/1239 and https://piwigo.logre.eu/picture.php?/1286); I never tested mine...

¹ my design means to me, as it is my very first usage of Onshape (and first time I ever used a parametric CAD software).

David, could it be possible to change the revision numbering and the way releases are managed?

I suggested in another thread to use a.b.c: 'a' for major release (3, here), 'b' for minor release (0, here), and 'c' for bug fixes.

Currently, installing a new release for bugs fix introduces new features, so potentially new bugs: this is not a good thing. One should be able to dissociate bugs fix and new features...

So, after the current release, which should be named 3.0.0, the next one should be named 3.1.0 (not 3.01). And bugs fix should go into 3.0.x (then in 3.1.x...)

Thanks.

Here is a very simple Python script to implement Ian's idea:

#!/usr/bin/env python
# -*- coding: utf-8 -*-

import sys

for line in sys.stdin:

    # Replace tool changing commands by part changing tags
    if line.startswith('T'):
        num = int(line[1:])
        print "; part %d\n; process %d" % (num, num)

    else:
        args = line.split()

        # Only keep tool 0 temperature commands
        if line.startswith('M104') or line.startswith('M109'):
            args = line.split()
            num = int(args[2][1:])
            if num == 0:
                print line,

        # Default commands
        else:
            print line,

It replaces tool changing commands:

Tn

by:

; part n
; process n

It also remove all temperature commands of tools >= 1.

To use it:

$ ./tool_parser.py <input.gcode >output.gcode

PS: I only checked Slic3r output; Cura output may need additional stuff.

M260 can send data over I²C bus:

https://duet3d.dozuki.com/Wiki/Gcode#Section_M260_i2c_Send_and_or_request_Data

On the I²C slave, just mimic some registers you will write from Duet to take the actions you need.

I recently developped a project using an ATtiny841 as I²C slave (this chip as a hardware I²C slave implementation), working this way. See:

https://framagit.org/fma38/Servo_Node

This is for an hexapod (I will use 6 of them, to control the 4 servos of each leg). But I will certainly use this chip for other projects, like here.

Code in Arduino/ dir is a master example; the real master will be a RPi, running my framework Py4bot: https://framagit.org/fma38/Py4bot

I'm also working on such filament mux, with multiple tools using the same heater, and I didn't have this problem. Could you share your tfree macro, and tell us what commands are skipped?

Hi!

I plan to use 2 fans to cool down the drivers, as my Duetwifi/x5 will be in a box.

Is it possible to create a thermostatic fan, routed to a specific thermistor, without any heater? If not, how should I create a dummy heater for that?

Thanks,

According to E3D guys, the piezo can't handle non uniform pre-tightening, as it may crack the element. That's why they use a central bolt (they use a drilled screw to let the filament pass through).

So, I designed a similar setup for my hotend :

I can screw it on the hotend, and on the mount. This will require to drill/cut a standard hex screw, and CNC the 2 other parts (or have them 3D printed in metal).

I see on their example they mount the PZ Probe perpendicular to the probing direction, so a tork is applied to the probe.

In my case, I planned to mount it on the hotend heat sink:

The problem is I don't have any screw in the center, but 4 on the outside perimeter. And as they give a tightening torque instead of a force applied on the probe, how can I know how to tighten my 4 screws?

Their documentationcould be better, with schematics with the different way to mount it, instead of a single picture of a specific usage...

Thank you very much!

Hi!

I'm wondering if some of you is using a E3D PZ Probe?

I plan to mount one on my modified FLSUN SR, but I didn't find any documentation about the idle pressure I should (not) apply to the piezo element...

Here is my design, with a modified effector, and a custom mount for the extruder (genuine Bondtech GLX Lite) and the hotend (genuine Phaetus Rapido 2 Plus HF):

https://cad.onshape.com/documents/19fff3683d4080f810beb21e/w/e18f2a4ce6a69f33ff95fd56/e/1af0fe0f40b14b4d0efb2e8c

The PZ Probe is sandwished between the plastic mount and the hotend heat sink.

Does it seem correct to you?

Thanks for your feedback.

@droftarts Thanks. I'll ask my cousin to check.
In the meantime, he tested the ISO prostprocessor, which seems to work fine.

Mmm, Blender CAM generates strange G-Code:

G0X0Y0Z10
X3.477Y3.144
G1Z0F500
G0Z10
X3.666Y3.004
G1Z0
G0Z10
X3.868Y2.883
G1Z0
G0Z10
X4.081Y2.782
G1Z0
G0Z10
X4.303Y2.703
G1Z0
G0Z10
X4.531Y2.646
G1Z0
G0Z10
X4.764Y2.611
G1Z0
G0Z10
X4.999Y2.599
G1Z0
G0Z10
X5.235Y2.611

For lines only containing X/Y coords, G-Code simulators use the previous command (G0, here), but RRF does not seem to understand such lines... Do you confirm?

Hi!

My cousin bough a used CNC which is running with a Duet2 board.

As he knows Blender very well, he would like to use Blender CAM, which does not output GCode for RRF. Which machine should he use, from this list:

• Iso
• Mach3
• LinuxCNC
• Fadal
• Heidenhain (530, TNC151)
• Sieg KX1
• Hafco HM-50
• Centroid M40
• Anilam Crusader M
• Gravos
• WinPC-NC
• ShopBot MTC
• Lynx Otter o

Is GRBL ok?

Thanks.

Hi!

As I switched to a Duet3 Mini for my FLSUN SR, I'm selling:

• 1x Duet2 wifi board (wifi module has external antenna): 80€
• 1x Duex5 expansion board: 60€
• 1x PaneldDue Controller + 7" screen and custom enclosure: 50€

(only to Europe).

@droftarts if you look at the Laser filament monitor doc page, the first picture shows a v1.2 PCB

Thanks for the infos and the link to the indirect mod!

I have a v1.2, not a v1.7; is it ok?

Does it work with 3.3V, like recent sensors? I don't have any free input with 5V power supply.

The modified version could be interesting...