Posts made by zruncho

@o_lampe

Amazing work on that! I hadn't really understood it from skimming the thread, but I watched your video:
https://www.youtube.com/watch?v=Lo-ymCO0Ekw

... and the great animations made it clear. How did you do them?!?!?

Anyway, I'm personally not too worried about mesh leveling, as all my printers either use a MIC6 bed or glass plate and none require mesh leveling, just bed tramming. A little variance in the first layer is probably OK anyway, especially if using textured beds, with parts that have first-layer chamfers.

re: parking outside - that's an option w/a Dual Gantry too. You can do that with the world's simplest T0/T1 gcodes to move to a parking position:

https://github.com/zruncho3d/DuelingZero/blob/main/Diagrams/workspace_dual_corners.png

@dc42 said in Beta testers for multiple motion system support:

https://reprap.org/wiki/G-code#M597:_Collision_avoidance

If I understand the G-code description, though, this seems like more of a "collision detect & then abort" than proactive avoidance?

"If this is not the case, the job will be aborted prior to starting the first move that would cause the conflict."

Still useful though! If I had this it would have avoided a few head crashes.

BTW, have you seen any other Dual Gantry machines printing? The Links section at the bottom of the README links to every bit of prior art I could find - mostly gantry renders for post (here), or one commercial model, the Essentium HD 280i.

https://github.com/zruncho3d/DuelingZero#links

@dc42

I don't have the modern Duet boards to make use of this code, but it's still exciting to hear that this is coming along.

Today I released a complete open-source Dual-Gantry CoreXY printer called Dueling Zero, w/configs, STLs, videos, CAD, docs, diagrams, the whole nine yards. The GitHub repo includes a sample RRF config for XY motion, which "just worked"... it was nice.

https://github.com/zruncho3d/DuelingZero/

Curious what you (and others on this thread) think. In particular, the section on collision detection and avoidance in a shared workspace is general for any firmware.

https://github.com/zruncho3d/DuelingZero/blob/main/SOFTWARE.md

@droftarts

On v3.4, I was able to get everything working without issue, from your suggestions. Thanks!

It was all pretty straightforward - define a CoreXYUV, map the axes and endstops, and verify it all as a CoreXYUV, first. Then set up to the tools, where the second one maps (U, V) to (X, Y), and ensure they work as expected with T0 and T1, where each of these parks the toolhead.

Seems all good... with no pain, surprisingly, so far. I know the XY offset calibration to come will be the bigger pain.

@breed

I'll share it all on GitHub once I've addressed a few minor items, just like all my other printer mods:

https://github.com/zruncho3d/

As a teaser, imagine two BoxZero gantries, with one rotated 180 degrees, plus all-custom XY joints so that both gantries can have shared rails.

@breed

On my Hybrid-CoreXY IDEX ("Double Dragon"), I enlarged the toolhead mount holes slightly, then tapped one toolhead into position, using a shared nozzle endstop to precisely measure the Z height difference. Took < 5 m to get < 0.01mm alignment.

https://github.com/zruncho3d/double-dragon

https://www.youtube.com/watch?v=GY29F2O1unw

Gonna do the same thing on the IDG printer, since I know it works...

@droftarts

Interesting. I really don't see how that would be useful without a way to sync Z motion between the two streams. What's the driving use case for that functionality?

@zruncho

I got a different message in this thread about the possibility of making a dual gantry work; what missing feature would be needed in RRF 3.5 to enable this?

Thanks.

Also, are you aware of any public references to a machine like this? I'll put mine on GitHub soon enough, but curious to see any others. Dual Gantry is a lotta work, but it's definitely an interesting setup if your goal is to learn.

@droftarts

Thanks... that does seem to cover most of what I'd need for config.

Should the g-code that the slicer generates then include T0 and T1 commands to trigger the 'tfree*.g'? That's the bit I'm missing here, and maybe it's just that.

Looks like no g-code postprocessor will be needed here to make use of the second gantry, which is pretty cool. Seems like Duet's been designed for this or something...

Probably relevant, it's a dual CoreXY setup.

Re: independant dual gantry corexy

I've recently built an independent dual gantry printer. This is not an IDEX; the toolheads are on independent gantries.

I'm looking for any examples of how to configure it so that, like an IDEX, the toolheads can both share in a single print, by taking turns.

Any ideas out there, especially @dc42 ?

There was this thread:
https://forum.duet3d.com/topic/24258/independant-dual-gantry-corexy/10

... but it seemed to die long ago, and the forum encouraged me to create a new thread vs rekindling the old.

Thanks! I've got a Duet2 WiFi all upgraded to the latest code now, and I'd love to know if/how this is possible.