I can't think of any reason why you would need to wait for 30 seconds.

Swapped it out today and the new board works fine. Thank you.

@deckingman:

That's all fine. I was just replying to the title of your post which is that two TOOLS are active at the same time. I guess heaters need to be active on order to maintain standby temperature even if the tool itself isn't active.

I do appreciate you pointing out the underlining of the tool. It helps to make clear that only one TOOL was active/selected while both HEATERS were active. That's one of the differences with the duet (and RRF, I guess) that I haven't quite become used to: "has a" relationships instead of "is a."

Yep that works. Tested in my tfree0 and 1 and works as i expected. At end of a tool usage it waits for the active tool to cool a bit so stops oozing out my volcano, wipes and switches tool. This will prevent alot of random oozed filament from being dragged about and falling off randomly.

THanks!

Oh I did search on grabcad but didn't find it. Thank you :D.

HIWIN Servo drive Model number D2-0123-S-A0-G

Thanks!

Yep- that's it! The Z-probe display also shows numeric values with the paper test. Now to make a new mount…

Thanks!

I have a feeling that this behaviour was deliberately changed in firmware 1.20 because several users complained that babystepping wasn't remembered from one print to the next.

I suggest you use a multimeter to check the voltage between ENA+ and ENA- on your external drivers. It should be 0 when you start the Duet, changing to almost 3.3V when you first command the X motor to move.

Similarly, measure the voltage between DIR+ and DIR-. It should switch between 0V and 3.3V depending on which way you try to move the X motor. For example, if you send G91 first, then G1 S2 X10 will set it one way and G1 S2 X-10 will set it the other way.

If those are both working, then although most external drivers work OK with the 3.3V signals provided by the Duet, it's possible that your drivers need a full 5V.

Agreed. It's one complex challenge. One posible way to workaround is employing the same technique as when using dual extruders. Setup a small priming pillar and when a speed/temp change is executed (the Mxxx command is present in the start script), the head retracts/moves to the priming pillar and waits for the temperature to reach the desired level. Then performs
unretract->prime->nozzle wipe->retract->Z-hop>moveX/Y and continues print where it left off.

Cura uses a variation of this method to prevent curling/warping when the layer time goes below the preset time,allowing the filament to cool a bit before continuing printing the next layer. The downside is that print time will increase and possible visible banding.

See the description of M591 in the GCode wiki.

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.

If it happens again, please try to isolate the file that causes the problem.

@burtoogle:

I think you should be posting this on the Cura forum (https://community.ultimaker.com/), not here, as the problem is more likely to be a slicer setting rather than a problem with the Duet config.

Sorry, you're right. I'm gonna post there.

Here's my build https://openbuilds.com/builds/zidex.5259/

Stephen

@dc42:

I found this https://www.shapeways.com/product/E628BXAJW/bi-v2-5-effector-for-chimera-with-ir but it's not cheap and I don't know whether the rod spacing is suitable for a Mini Kossel. There is at least one thread on using a Chimera/Cyclops on a delta on the reprap forum, but that forum seems to be down at present.

Unfortunately, that looks like it won't fit, but still thanks!

… I have two boot partitions on my router; so I selected the other partition, which still contains Linksys default firmware.. and it is working brilliantly. DD-WRT is no more... Thank you for your help!

@dc42:

First choose the head reference point. … Now define the M208 axis limits, the tool XY offsets (G10) and the Z probe XY offsets (G31) relative to the head reference point.

Okay, I found my problem. I was mentally using my right tool (T1) as my reference point, but when I configured things I set the offset on T1 (instead of on T0.) After moving the offset to T0, everything works.

Thank you
Gary