Damn, a stupid colon made me feel stupid 
Thanks @dc42 for your continued attention to this and for working with me on getting it resolved so quickly. You guys are awesome in doing what you do. Keep up the great work, it is much appreciated.
I hope someone can benefit from my oops in the config.
I've re-tested all my print modes with the same file and it all behaves as I would expect now.
@dc42 said in IDEX printing U-axis incompatible with G2/G3 arc moves:
I've just compared your X and U videos side by side, and I can see that the X one is printing faster. I will look into this. I no longer think the motion is compute-limited.
If you run the original prints without using ArcWelder, do the X-only and U-only prints run at the same speed?
Yes, without the ArcWelder both run slow and produce the same lower quality prints. You can see the comparison in the photo I included with the videos.
To say it differently, when ArcWelder converted file is used only the X axis prints with the advantage of the G2/G3 which allows for better speed and quality.
Thanks @wilriker! I just upgraded and it is working as I hoped for.
You and all of the folks on the Duet3d project(s) are awesome! The turnaround on this was lightning fast. Much appreciated.
@dc42 said in IDEX printing U-axis incompatible with G2/G3 arc moves:
Thanks, U axis printing alone is probably the most important then, and X axis alone may be a useful comparison.
I'm sorry I haven't been able to include a complete fix in release 3.2.2.
I agree, and no worries! I will be patient 
Thanks!
@dc42 In Ditto mode both axis print with stutter.
Another way to put it, only X axis printing alone prints arcs smoothly. Whenever U axis is part of movement the arcs are not smooth at all.
I uploaded 4 files for you. Three short video clips to see the printing, and one picture to compare quality of the printed parts.
I tried to make the stutter visible on the video (maybe hard to notice) but definitely notice the speed difference between X-axis print and the the other two examples. All printed with exactly the same code source file.
[link removed]
@dc42 Ok, I was able to test the firmware you shared with me. Partial success...
What appears to be working correctly now...
However, the following issues still persist...
Thanks @wilriker. You have summarized things exactly as I assumed. Better explanation than mine.
I also thought that this was for a good reason that I was not thinking about. And you are correct that in my case the previous way is the desired one.
It would be great if there is a setting for that like you suggested. I will look forward to having this option.
Thank you!
I ended up reversing the heater sensor pins and it all works great with my extruder breakout boards.
If I can help with testing or troubleshooting this with you guys, I'd be happy to. I have a dev background and am capable (I'd like to think )
Let me know.
Ok, I've tested all combinations now.
Printing with X only in either direction (M579 X1 or M579 X-1) works perfectly. Smooth and fast.
Printing with U only in either direction (M579 U1 or M579 U-1) prints slow and it stutters like with a "plain" gcode without arc.
Printing with X and U together either Ditto or Mirror results in an unpredictable movement where on the first G3 move X carriage stops and U carriage advances toward it crashing into it.
Here is my code file: guidefilla-1.gcode
Thanks for looking into it!
It appears that the same thing happens when I do a Ditto print. Considering that this happens in both Ditto and Mirror print what could be the problem. I am baffled.
Here is my config: config.g
I have IDEX configured with 4 tools (Left, Right, Ditto, Mirror). I just upgraded from PanelDue firmware 3.2.7 to the latest 3.2.9 and the tools control on the screen is messed up.
The current state...
Tool 0 column activates tool 0 and controls heater 1 values (ok)
Tool 1 column activates tool 1 and controls heater 2 values (ok)
Tool 2 column activates tool 2 and controls heater 1 values (messed up)
Tool 3 column activates tool 2 and controls heater 2 values (messed up)
No screen control for Tool 3 now. It's off the screen (I'm assuming). I hope that is not by design because it worked in 3.2.7 just fine. Please restore that functionality.
This is how it used to be...
Tool 0 column activates tool 0 and control heater 1 values (ok)
Tool 1 column activates tool 1 and control heater 2 values (ok)
Tool 2 column activates tool 2 and control heater 1&2 values (ok)
Tool 3 column activates tool 3 and shows heater 1&2 values (ok)
Duet 2 WiFi / Firmware 3.2 / PanelDue v3 Screen 4.3"
I got my IDEX configured to work with 4 tools (Left, Right, Ditto, and Mirror). When I use the M579 U-1 to scale my U axis in reverse in mirror print my extruders crash into each other. However, that only occurs when I use gcode post-processed with ArcWelder and converted to use G2/G3 moves.
When I mirror print with linear moves it works fine but it stutters like crazy on arcs, also increasing the print time by a lot.
My guess is that reverse scaling does not work with Arc moves. Can y'all confirm that is the case? If so, is there any workaround, or plan to make that work in the future?
Duet 2 Wifi / Firmware 3.2
Thanks!
@Phaedrux thanks for your attention. I isolated the problem to a breakout board that my extruders are using. It appears that the filament wiring is sharing ground with other elements on the board and that is what's triggering the heater fault. When I connect the switch all by itself through a dedicated wire it all works as expected.
I have an IDEX machine, and I am in the process of installing runout sensors (simple switch) to e0stop and e1stop. The sensors show up fine when I run M591 D0 or D1, but when I trigger either switch I get a heater fault/error for the respective extruder and that extruder cooling fan kicks in. It all returns to normal when I put filament back in the sensor.
The switches are wired as normally closed to the two outer pins of the header (GND/STP).
I looked everywhere but cannot find anything with this specific condition.
I am running Duet 2 WiFi with Duex5 and Firmware 3.2.
Any help will be greatly appreciated. Thanks!