Yesterday I visited the Duet3D booth and had the pleasure to meet the team and have a chat with David and Christian.

It made me realize just how much is going on behind the curtains and how much work and passion those guys are pouring into the development of new features and constant improvement of the overall system.

I am super excited about what's to come.
I hope you guys have a great last day at Formnext!

Max

Good morning!

I know that this has been discussed several times already. I started this thread to collect the available closed loop options for the Duet3.

I have two custom large format printers in the making. One with a build volume of 1000x1000x1000mm for printing architecture models and one with 500x500x1000mm for printing speaker enclosures. With a Build volume this large speed and reliability are essential. Therefore, a closed-loop motion system is a "must have" for my clients.

For the Duet3 I have found the following options:

1. Duet3 + Duet3 Expansion 1XD + external closed loop stepper drivers that accept step/dir signals

2. @dc42 I am aware that there is a closed-loop extension board in the making for the Duet3. Is there already a rough estimate on the release date or beta test?

3. Is there an alternative "of the shelve" closed loop solution available that support the CAN FD protocol?

Cheers,
Max

I would like to use the constant surface speed feature on my Duet based CNC-Lathe.

I am using a generic Haas turning post Processor with some minor adjustments that I have tested with Fusion360 or Solidworks+HSMWorks.

the constant surface speed GCode (G96) is defined on the Haascnc G-Code dictionary as follows:

"G96 commands the control to maintain a constant cutting speed at the tip of the tool. The spindle RPM is based on the diameter of the part where the cut is taking place, and the commanded S value (RPM=3.82xSFM/DIA). This means the spindle speed increases as the tool gets closer to X0. When Setting 9 is set to INCH, the S value specifies Surface Feet Per Minute. When Setting 9 is set to MM, the S value specifies Surface Meters Per Minute.

WARNING: It is safest to specify a maximum spindle speed for the Constant Surface Speed feature. Use G50 to set a maximum spindle RPM. Not setting a limit allows the spindle speed to increase as the tool reaches the center of the part. The excessive speed can throw parts and damage tooling."

Cheers Max

@T3P3Tony

Indeed, I wrote a simple macro that sets the height of the dust shoe to the height of the spindle collet+ the current tool length. This macro is called after a toolchange or if one of the macros for mist cooling or dust extraction is called. Maybe I will add a demon later that updates the height of the dust shoe regularly during a job. But for now this will do.

I made a short video while running a tool change. Not having to fiddle with the dust shoe during toolchanges is already so much more convenient.

And with this start Gcode for PrusaSlicer the correct heightmap is loaded according to the temperature of the printbed.

{if first_layer_bed_temperature[0] <=40}
G29 S1 P"heightmap_roomtemp.csv"
{elsif first_layer_bed_temperature[0] <=70}
G29 S1 P"heightmap_60°.csv"
{elsif first_layer_bed_temperature[0] <=90}
G29 S1 P"heightmap_80°.csv"
{elsif first_layer_bed_temperature[0] <=110}
G29 S1 P"heightmap_100°.csv"
{endif}

Thanks everyone for your ideas and feedback. This is by far more elegant than my original idea.

@bearer @Phaedrux

I have solved the issue by installing the unstable version (DSF Version: 2.1.3) of Duet Software Framework on Raspberry Pi. and also reverting back to RC11

The guide links to the stable version of the DSF and latest version of the reprap firmware which, at least in my case is not compatible and will lead to the "DCS is unavailable" Error.

cheers Max

With the release of the new Duet 3 Roto Toolboard I am not sure if a new smart effector is really needed. for me the main advantage of the smart effector was nozzle probing. But with the new Scanning Z-Probe Nozzle probing is already obsolete in my opinion. Of course you woul need to set the probe offset manually with a Scanning Z-Probe. To do this I use either a separate button style probe or I adjust the z height manually with baby stepping and run a simple macro to adjust the probe offset by the baby stepping amount and save the new probe offset in config-override.g.

I would still be interested in buying multiple smart effectors if they support the following points. some of them are obvious but for the sake of completeness...

• Scanning Z-Probe
• onboard accelerometer
• onboard motor driver
• Io input for filament monitor
• VZ style hotend mounting holes for Hotends like the Phaetus Rapido, VZ-Revo or Mellow Goliath Hotends.
• Enough space for direct drive extruders.

And lastly not necessarily a must but it is nice to have options.

• A hotend mosfest that can handle <100 W (Mellow Goliath Hotend)

Since I use CPAP style part cooling and watercooling for the hotend I do not require fanports on the tool board. But I recon This would be a no-go for most users.

Hey @bruce

Thank you so much for developing and sharing your post processor! I use it with the HSM-Works plugin directly in SolidWorks for my duet based CNC Mill.

Any chance to also include a profile for turning as well? I am in the process of converting a Lathe to CNC using a Duet3 6HC board. With lathe support, it would really be the "one post processor to rule them all"

Cheers Max

@comediantf2

Just installed your UDL, thank you so much for your work!
-Max

@martin7404 said in IDEX motor jitter:

@maxgyver stil.I would like to see your belt arrangment, please
Thank you

I am working from home right now. I will gladly provide you with some CAD-Screenshots of my belt arrangement later this week.

@fcwilt said in IDEX motor jitter:

But why does just the inactive axis vibrate? You mentioned that you can print with one axis without problem - correct?
Have you experimented with changing belt tension?
Frederick

Yes, I have tried every tension from loose to guitar string high.

The big drawback with CORE XY, H-Belt, Markforged e.t.c is that you create a kinematic system where multiple axis are codependent. Meaning that every little tolerance, vibration and over swing, will translate into the other axis. From what I have learned until now, the reduced moving mass is not worth having much longer belts.

@dc42

I just tested 3.6.0-alpha.5+1 on our 5meter printer. The "homing jolt" on our CAN-connected Servo Drives is strong enough to make the servo drives go into fault mode Reducing the homing speed by 50% did help, but it still produces a loud "clonk"

Everything else is working as expected
Setup: Duet MB6HC+ 3xEXP1XD+ EXP3HC

My small printer is flawlessly printing since an on our under 3.6.0-alpha.5+1
Setup: Duet MB6HC+ 3xEXP1HCL+TOOL1RR

four screw bed tramming and mesh probing with the SZP seems to be working as expected, I only had to reduce the pressure advance value by 50%.
I have noticed some short movement pauses during printing, these were also present in RRF 3.5.2, maybe increasing the movement queue length can help here?

Since setting up a "Continuous rotational axis" is not yet supported by RRF, I thought about a workaround to get a continuous rotational axis that won't interfere with the rest of the movement system...

To recap:
I use a stepper motor peristaltic pump on my CNC-Router to control the coolant flow while milling aluminum parts. My original Idea was to set up an extra Axis on the duet to control the stepper motor of the peristaltic pump. Right now this doesn't work since there is no option to run an axis continuously and progressing the axis in a loop would block other movements.

Here is my Idea:
So I need a stepper motor that can basically be controlled like a Fan in DWC. So why not use one of the duet's PWM outputs to generate the step pulses for an external Stepper motor Driver?

@phildoyle

Please check the following on the software side:

• The correct steps/mm are set for your ballscrews pitch in config.g
• If you had backlash compensation enabled for your old leadscrews, disable it for now. Ballscrews should have relatively low backlash.
• You have set the correct tool diameter in your program
• Confirm the diameter of the physical tool

Since the holes are spaced correctly, it is unlikely that you are loosing steps. But you can check the following to make sure it is not a mechanical issue:

• See if the ballscrews are securely coupled to the motors

• See if the ballscrew bearings have any play or are loose

• Reduce your cutting feed and reduce your depth of cut to see if high feed speeds are bending your machine

• Check if your motors are loosing steps: Position the spindle at a point outside your working area. Get something to mark this position. A dial indicator would be optimal. Mount the dial indicator so that it is stationary on your machine. Set the spindle against the dial indicator in die direction of the X or Y-Axis. Zero the dial indicator and note down the machine position. Then run your Program. When the Program is finished, move the spindle to the previously noted position. If the dial indicator is still close to zero, there should be no lost steps.

@droftarts said in [3.5.0-rc3+] M108 (cancel heating) is not working.:

If you run M109 et al in a macro, cancel it by sending M108 from the console in DWC; I think that shouldn’t be blocked.

Yes, that works. Thank you very much for clearing that up!

@droftarts

Okay now I am confused...
From the M108 description I understood that the purpose of this command is to break out of an M109, M116, M190 or M191 wait-for-temperature loop.

When I send an M190 S60 over the console followed by an M108, the input channel is blocked until the bed reaches its set temperature of 60°.

The same goes for macros:

;M108 test
echo "setting bed temp!"
M140 S60 ; set bed temp
G4 S1
echo "sending M108"
M108

Max

I just noticed that the M108 command is not working... at least it does not work in RRF 3.5.0-rc3+. Unfortunately, I have no system running a stable version for testing if the problem is limited to the beta.

@dc42

Thank you very much for your feedback! Just to be on the side of caution. The Roto Toolboard should be ok with the 115W nominal power of the pheatus rapido?

According to the docs the current limit on the high current output of the Revo toolboard is 3.4A (80W @ 24V).
While this is totally fine for the intended use of the Roto tool board with the E3D Revo system (max 60W), most high flow hotends are well above 80W or even around 115W.
Since the full output current is only drawn during the first few seconds during heatup, I was wondering if the revo toolboard might be capable of handling currents higher than 80W for a short amount of time without damaging the high current mosfet?

I found this table for the phaetus rapido @24V. It illustrates the drop in current at different temperatures quite well:

Thank you all for your feedback! In conclusion, we all agree that for heavier machines, hardware limit switches are a must-have or are even mandatory for machines that are used in professional/business environment.

@dc42
@T3P3Tony
Are the X and Y moves considered probing or travel moves in G30 Pnnn?
I assumed that moves in X and Y are travel moves that position the head above the next probing point, and only the following move in Z is the actual probing move. Therefore, the limits in X and Y should be respected like for any other travel move. This would avoid raising faults or adjusting the bed.g macro.

@infiniteloop said in [3.5.0-rc.3] G30 probe point does not respect axis limits:

During the setup process, this safety cannot exist - else, you would not be able to probe the limits. The same applies to tool changes: you will have to recalibrate your Z-height (which is inherently unsafe). [...]

In therms of referencing the machine at startup, I absolutely agree with you. But everything after that should happen within these machine (soft) limits or not? I can't think of a reason to command the machine outside these limits, since it can't physically move there. Maybe we need something like machine-limits and work-limits? Just like we have machine and work coordinates in CNC. The machine limits are set after referencing (aka. homing) and are not exceeded. By defining work-limits the head movement can be limited to a specified boundary like for example the printing area.