Hello all,

I thought I'd provide a workflow for those interested in using Fusion 360 for CNC and laser work. Hopefully it's useful.

I'm running RRFW 3.3 on a Duet 3 running 32v for motors and 24v for most everything else. I'll cover how I build a tool library in Fusion 360 and call macros for a manual tool change between operations with a modified post processor for a pwm controlled spindle and a stationary z probe. I've also enabled arcs in this post processor.

First setup your tool library in Fusion 360 including data on spindle speeds and feedrates.

I reserve T1-T2 for defining tools such as spindles and laser engravers in my config files. Using T0 has caused me issues, so I avoid using that. Use T3 and above in Fusion 360 for defining bits. Note: a new tool will default to the lowest available number so make sure you add it to the bottom of the list. Save to the cloud tool library (preferences -> manufacture -> enable cloud libraries).

In my config.g file, I have as many Tx as I have bits in my library.

; Tools
; No tool is selected at startup
M453						                ; Set to CNC mode,
M950 R0 C"out0+out6" Q300 L0:24000          ; Select Spindle On/Off,RPM & Direction (not selected).
M563 P1 S"Laser"					; Create tool 1 Laser
M563 P2 S"Spindle" R0				; Create tool 2 with Spindle

; Create enough tools to cover library of F360 CAM tools and link to R0
M563 P3 S"T3" R0
M563 P4 S"T4" R0	
M563 P5 S"T5" R0	                        
M563 P6 S"T6" R0	
M563 P7 S"T7" R0	
M563 P8 S"T8" R0	
M563 P9 S"T9" R0	
M563 P10 S"T10" R0		

; PWM Laser Enable 1# 2
M950 P1 C"io4.out"                      ; Use C"" for output - Opt Lasers enable input #1
M42 P1 S0				                    ; Ensure P1 is off - enable input #1		

Your CAM will show the tool numbers:

Upload the post processor I have provided. The post processor will call for a tool change if required. It does this by calling on macros I have also provided here. If you want to run a different macro, simply open up the post processor in Visual Studio Code and change the file path at LINE 573, save, and reupload to F360.

For the macros, these were written mostly by @EducatingSavvas for his moot line of CNC machines. I'll provide a workflow here as well as I think it's helpful.

Again, my machine has a fixed z probe button just off the work area. macros 01-04 are for initial setup of the machine. 02 and 04 need to be changed when resurfacing the waste board

01 - Set Probe Location
first sets the location of the probe and permanently stores this info

02 - Set Probe to Waste Board Distance G55
Then stores the difference between the probe and the waste board.

03 - Set X Y Datum In g55
This sets the location of my machine X0 Y0 work coordinates

04 - Set X Y Z Datum in g56 for laser
I have a laser attached next to the spindle (magnetically removable optlaser). I use this macro to set the offset in X, Y, and Z. U simply make a mark with my CNC vbit in g55 at X0 Y0 then jog the laser over to the same spot and then use this macro for setting laser X0 Y0 and Z0 in g56. This means that the spindle and the laser are perfectly aligned.

These next macros are called in the gcode during a tool change:

Move To Probe Location in g55
moves the spindle to the Z probe

Set Tool Height in g55
adjusts new tool to wasteboard Z0

That's all there is to it.

In F360, select the bottom of the stock for your origin point and this will correspond to Z0, the top of your waste board.

I have also include Tpre, Tpost, and probe files for good measure.

I keep getting a parse error when trying to upload files. I will try to post the files in a second thread.

There appears to be a typo in the Duet 3 6XD wiring diagram 1.0 and 0.1. Driver 2 should read D2 STEP-, D2 DIR-, D2 EN-, and D2_ERR not D4.

I switched over to Orca Slicer when it looked like SuperSlicer had be abandoned after no updates since March. But I found a Sept post from the creator that says he is going to work on SS full time starting this month. I hope it's true.

From this post: https://github.com/supermerill/SuperSlicer/discussions/3902

@droftarts, @oliof

Thanks for the info. I will ensure to close all browser windows before doing any more testing.

I am not sure it is related, but my network setup is 2x Asus rt-ax56U routers, one main, one a mesh access point connected on a wifi backbone with the duet via ethernet.

Oddly, the board no longer appears in the list of clients even though I can connect to DWC. It seems to be causing issues on my network. Unclear to me what is going in. I may redo my network and see if there is any improvement.

Hello,

I built a CNC machine recently using these components and a duet2. I had issues with the PWM converter you linked to. I would recommend this one instead. Both, however, say limit 30V, not 32V.

I use two of those PWM converters, one on E0heat to enable spindle on as my VFD requires a 10V signal input to do so, and one on E1heat for spindle speed. The Duet uses the difference between Vin and E0- or E1- for the PWM signal. That means E0- and E1- start at Vin (no PWM) and goes down to 0 (diff = Vin = max PWM).

The PWM converter board you linked to cannot handle this. It only works if both Vin and E0- or E1- start at 0V/PWM, and E0- or E1- goes to Vin. You can enable this using !E0heat in RRF3, but I would not do this. There is a dangerous issue with this setup. Let's say you have a problem and you hit the emergency stop button to reset the board. There is a brief moment, maybe before the !E0heat in the config takes over, that E1 and E0heat briefly pulses to Vin. The board you linked to sees this as max PWM and Spindle On basically turning the emergency stop into a temporary spindle on at max speed button. This isn't a problem starting up the machine since the VFD takes longer to come online. But any reset where the VFD is ready to go and you E-Stop, boom.

I would suggest NO prox sensors rather than NC for redundancy and I am also using an 8 channel relay to isolate between prox sensors and z-probe from the duet.

@selva_tvi

Hi selva, I'm working on this today. I just deleted another post trying to find out how to change the error pin pull up/down. Turns out there is a a spot to bridge it on the board itself. I will let you know how it goes. I am pretty close to finishing if this works.

@dc42

Ok yeah, I didn’t see the version before. It’s v0.1.

Some things were not disclosed until I drove out to meet an hr+ away. Win some, lose some. I’ll grab a new board if it bothers me enough.

I recently picked up a voron 2.4 from a guy who turned out to have had worked at E3D and it was a low-use test machine. I have 2 CNC machines running duet, but this is my first printer so a little new that side of things.

He mentioned that the machine had some early test boards. It has a revo roto, a duet roto toolboard and a revo PZ probe. The PZ probe has no mounting holes, for example, so is likely pre-production.

I am not sure this is the reason for my issues. I am getting an initialization error when I try to do input shaping. I can see it with M122 B1.

I am running the most recent RC though I am getting a warning of incompatible versions. Not sure why.

Duet 3 Mini 5+ 3.6.0-rc.3
Duet 3 Expansion TOOL1RR 3.6.0-rc.3
Duet WiFi Server n/a 2.2.1
Duet Web Control 3.6.0-rc.3

My config file has this, which seems to be in order

; Accelerometer
M955 P1.0 I01 

I also tried

; Accelerometer
M955 P1.0 I01 S1600 R8  

M122 B1 says: INT1 error only after running input shaper, otherwise 00. Not sure how to get it to initialize.

m122 b1
Diagnostics for board 1:
Duet TOOL1RR firmware version 3.6.0-rc.3 (2025-04-29 14:50:37)
Bootloader ID: SAME5x bootloader version 2.9 (2023-10-06)
All averaging filters OK
Never used RAM 170600, free system stack 200 words
Tasks: Move(3,nWait 7,0.0%,176) TMC(2,delaying,1.3%,51) HEAT(2,nWait 6,0.1%,112) CanAsync(5,nWait 4,0.0%,70) CanRecv(3,nWait 1,0.0%,73) CanClock(5,nWait 1,0.0%,63) ACCEL(3,nWait 6,0.0%,47) MAIN(1,running,97.9%,320) IDLE(0,ready,0.0%,29) AIN(2,nWait 2,0.7%,255), total 100.0%
Owned mutexes:
Last reset 00:08:58 ago, cause: power up
Last software reset at 2023-10-25 10:23, reason: deliberate HardFault zeroDiv, available RAM 165012, slot 1
Software reset code 0x8060 HFSR 0x40000000 CFSR 0x02000000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x200023a0 Task MAIN Freestk 782 ok
Stack: 00000001 00000000 20001168 00000004 00000001 00010ee7 00012394 41000000 a5a5a5a5 a5a5a5a5 a5a5a5a5 0001ce53 00000000 00000000 20002dc8 a5a5a5a5 00000000 11af7900 00000040 0300eb65 200032f8 0002fa86 200032f8 0002fa86 000000ce 00010c15 41200000
Moves scheduled 0, hiccups 0 (0.00/0.00ms), segs 0, step errors 0 (types 0x0), maxLate 0 maxPrep 0, ebfmin 0.00 max 0.00
Sync err accum 65, peak jitter -4/4, peak Rx delay 180, resyncs 0/0, no timer interrupt scheduled, next step interrupt due in 3890958943 ticks, disabled
VIN voltage: min 24.2, current 24.2, max 24.2
MCU temperature: min 16.9C, current 27.9C, max 27.9C
Driver 0: pos 0, 2682.0 steps/mm, standstill, SG min 0, temp 31.4C, read errors 0, write errors 0, ifcnt 13, reads 43930, writes 0, timeouts 0, DMA errors 0
Last sensors broadcast 0x00000002 found 1 181 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 4426, send timeouts 0, received 1923, lost 0, ignored 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, rxMotionDelay 0
Accelerometer: LIS2DW, status: 00, INT1 error!
Inductive sensor: never activated
Integrated filament monitor not present
I2C bus errors 0, naks 0, contentions 0, other errors 0

M122 for good measure

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-rc.3 (2025-04-30 14:42:33) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: DVFNG-3096U-D65J0-40KMW-LK03Z-RXN4D
Used output buffers: 4 of 40 (21 max)
=== RTOS ===
Static ram: 94764
Dynamic ram: 94324 of which 0 recycled
Never used RAM 52236, free system stack 142 words
Tasks: NETWORK(1,ready,16.9%,201) HEAT(3,nWait 6,0.0%,325) Move(4,nWait 6,0.0%,264) TMC(4,nWait 6,1.5%,65) CanReceiv(6,nWait 1,0.0%,766) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,346) MAIN(1,running,80.5%,655) IDLE(0,ready,0.2%,29) USBD(3,blocked,0.0%,147) AIN(4,delaying,0.8%,255), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:15 ago, cause: software
Last software reset at 2025-05-15 16:28, reason: User, Gcodes spinning, available RAM 52196, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 21.2, current 23.4, max 24.9
Supply voltage: min 24.0, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/28/8, gc cycles 0
Events: 1 queued, 1 completed
Date/time: 2025-05-15 16:33:10
Slowest loop: 34.50ms; fastest: 0.16ms
=== Storage ===
Free file entries: 20
SD card 0 detected, requested/actual speed: 25.0/24.0MBytes/sec
SD card longest read time 3.6ms, write time 2.1ms, max retries 0
=== Move ===
Segments created 6, maxWait 107441ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 29680.00/29680/0.00 5680.00/5680/0.00 1996.00/1996/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 0, r/w errs 0/1, ifcnt 21, reads/writes 23150/10, timeouts 0, DMA errs 0, CC errs 0
Driver 1: standstill, SG min 0, r/w errs 0/1, ifcnt 37, reads/writes 23143/17, timeouts 0, DMA errs 0, CC errs 0
Driver 2: standstill, SG min 0, r/w errs 0/1, ifcnt 38, reads/writes 23143/17, timeouts 0, DMA errs 0, CC errs 0
Driver 3: standstill, SG min 2, r/w errs 0/1, ifcnt 65, reads/writes 23129/31, timeouts 0, DMA errs 0, CC errs 0
Driver 4: standstill, SG min 0, r/w errs 0/1, ifcnt 64, reads/writes 23130/30, timeouts 0, DMA errs 0, CC errs 0
Driver 5: standstill, SG min 0, r/w errs 0/1, ifcnt 37, reads/writes 23143/17, timeouts 0, DMA errs 0, CC errs 0
Driver 6: standstill, SG min 0, r/w errs 0/1, ifcnt 37, reads/writes 23143/17, timeouts 0, DMA errs 0, CC errs 0
=== DDARing 0 ===
Scheduled moves 18, completed 18, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000803, drives owned 0x00000803
Code queue is empty
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
=== CAN ===
Messages queued 2247, received 5136, lost 0, ignored 0, errs 1, boc 0
Longest wait 5ms for reply type 4014, peak Tx sync delay 228, free buffers 26 (min 25), ts 1209/1208/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 11.21ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Power up, Vcc 3.34, flash size 2097152, free heap 39340
MAC address f0:08:d1:03:80:3b
IP address 192.168.1.94
Signal strength -91dBm, channel 7, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-rc.3 (2025-04-30 14:42:33) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: DVFNG-3096U-D65J0-40KMW-LK03Z-RXN4D
Used output buffers: 18 of 40 (33 max)
=== RTOS ===
Static ram: 94764
Dynamic ram: 94324 of which 0 recycled
Never used RAM 52236, free system stack 142 words
Tasks: NETWORK(1,ready,16.5%,201) HEAT(3,nWait 6,0.0%,325) Move(4,nWait 6,0.0%,264) TMC(4,nWait 6,1.5%,65) CanReceiv(6,nWait 1,0.0%,766) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,346) MAIN(1,running,81.0%,655) IDLE(0,ready,0.1%,29) USBD(3,blocked,0.0%,147) AIN(4,delaying,0.8%,255), total 99.9%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:15 ago, cause: software
Last software reset at 2025-05-15 16:28, reason: User, Gcodes spinning, available RAM 52196, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 23.1, current 23.4, max 23.4
Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/28/8, gc cycles 0
Events: 1 queued, 1 completed
Date/time: 2025-05-15 16:33:11
Slowest loop: 4.88ms; fastest: 0.16ms
=== Storage ===
Free file entries: 20
SD card 0 detected, requested/actual speed: 25.0/24.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 6, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 29680.00/29680/0.00 5680.00/5680/0.00 1996.00/1996/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 0, r/w errs 0/0, ifcnt 21, reads/writes 63/0, timeouts 0, DMA errs 0, CC errs 0
Driver 1: standstill, SG min 0, r/w errs 0/0, ifcnt 37, reads/writes 63/0, timeouts 0, DMA errs 0, CC errs 0
Driver 2: standstill, SG min 2, r/w errs 0/0, ifcnt 38, reads/writes 62/0, timeouts 0, DMA errs 0, CC errs 0
Driver 3: standstill, SG min 2, r/w errs 0/0, ifcnt 65, reads/writes 62/0, timeouts 0, DMA errs 0, CC errs 0
Driver 4: standstill, SG min 2, r/w errs 0/0, ifcnt 64, reads/writes 63/0, timeouts 0, DMA errs 0, CC errs 0
Driver 5: standstill, SG min 0, r/w errs 0/0, ifcnt 37, reads/writes 63/0, timeouts 0, DMA errs 0, CC errs 0
Driver 6: standstill, SG min 2, r/w errs 0/0, ifcnt 37, reads/writes 62/0, timeouts 0, DMA errs 0, CC errs 0
=== DDARing 0 ===
Scheduled moves 18, completed 18, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000803, drives owned 0x00000803
Code queue is empty
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000
Code queue is empty
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
=== CAN ===
Messages queued 5, received 10, lost 0, ignored 0, errs 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 3, free buffers 26 (min 26), ts 3/3/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 19.52ms; fastest: 0.09ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.1
Module reset reason: Power up, Vcc 3.34, flash size 2097152, free heap 39340
MAC address f0:08:d1:03:80:3b
IP address 192.168.1.94
Signal strength -93dBm, channel 7, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

@droftarts, @oliof

Thanks for the info. I will ensure to close all browser windows before doing any more testing.

I am not sure it is related, but my network setup is 2x Asus rt-ax56U routers, one main, one a mesh access point connected on a wifi backbone with the duet via ethernet.

Oddly, the board no longer appears in the list of clients even though I can connect to DWC. It seems to be causing issues on my network. Unclear to me what is going in. I may redo my network and see if there is any improvement.

@SDJ I found a post saying to increase the number of max AJAX communication to 5 from 2 under the machine-specific tab of DWC. This fixed the issue. I still don't understand why I am having these comm issues with the new firmware, especially considering that this is on an ethernet connection.

Hello all,

I updated from 3.4.5 to 3.5.3 and instantly had HTTP dropouts every 20-40 sec.

Running a 6XD on ethernet, so not used to having dropout issues.

I downloaded the firmware from github and updated via the web interface, had issues, then downloaded the DuetWebControl-SD and also updated, still the same issues.

Also cleared browser cache in desperation.

shows as updated

Not sure what to do next.

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6XD version 3.5.3 (2024-09-18 11:27:56) running on Duet 3 MB6XD v1.0 (standalone mode)
Board ID: 08DLM-956DA-M2NS4-6J1FD-3S06Q-9A26S
Used output buffers: 1 of 40 (36 max)
=== RTOS ===
Static ram: 153760
Dynamic ram: 135120 of which 0 recycled
Never used RAM 54256, free system stack 198 words
Tasks: NETWORK(1,ready,35.0%,172) ETHERNET(5,nWait 7,0.2%,316) HEAT(3,nWait 6,0.0%,355) Move(4,nWait 6,0.0%,335) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,339) MAIN(1,running,64.5%,128) IDLE(0,ready,0.2%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:22:18 ago, cause: power up
Last software reset at 2024-10-26 10:29, reason: User, Gcodes spinning, available RAM 57424, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU temperature: min 25.0, current 32.8, max 33.4
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 12.1, max 14.8, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/352/352, gc cycles 0
Events: 4 queued, 4 completed
Driver 0: ok
Driver 1: ok
Driver 2: ok
Driver 3: ok
Driver 4: ok
Driver 5: ok
Date/time: 2024-10-26 11:18:25
Slowest loop: 850.08ms; fastest: 0.07ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 150.0ms, write time 136.4ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 6692, received 0, lost 0, errs 6318399, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 6692/0/0
Tx timeouts 0,0,6691,0,0,0 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 137.33ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

Anyone having this issue? It is quite debilitating.

Oh I get it. This is screwing and unscrewing the collet nut. Crazy. I noticed you are using an air cooled spindle. I'm not sure I can run my spindle that slow without pissing off the VFD. It's a very short span of time I guess? I would have to lower my programmed limits to try this.

"Tu fait quoi papa"

"Un truc"

Lol. Genial.

Oooh this looks great. I would like to try this out on my next machine. Thanks for sharing.

What are you using reverse for? I don't really see why you would require this for tool changes.

I switched over to Orca Slicer when it looked like SuperSlicer had be abandoned after no updates since March. But I found a Sept post from the creator that says he is going to work on SS full time starting this month. I hope it's true.

From this post: https://github.com/supermerill/SuperSlicer/discussions/3902

Hello digital elf,

In general it is best to used normally closed (NC) sensors. That way if there is an issue with the sensor the machine will refuse to home. I think the sensors you are using are normally open.

Should still work fine, but I would suggest something like this: LJ12A3-4-Z/AX on this amazon page.

Either way, the wiring should be nearly the same. Might have to switch the relay from high to low. Just test to see what works. Hold up something iron to the sensor and you should get the relay to switch on to off or opposite depending on how you wired it up.

Hope that helps.

Hello there,

I have seen this question in the forums for other boards, but not the Duet 3 6xd with external drivers. This feels like one of those easy electronics questions that baffles people like me.

I have a Duet 3 6XD (on 3.4.5) running closed loop drivers (Lichuan LCDA257S) which is similar to a CL57T from stepperonline which has ALM+ and ALM-. I am confused on how to wire this up to the duet.

Duet 3 has a gnd pin and an Error pin (Dx_ERR) for each driver. The error pin meters 4.8v or so. I will check again tonight but I swear the pin is 4.8v regardless of the pull up/pull down selector.

If it is grounded or goes to 5V, it triggers the driver error. Not sure why it is both. The error pin also has a physical selector for pull up/pull down on the board. I tried wiring up to ALM+ and ALM- in just about every configuration I could try and it would never trigger the error. Nothing worked. I tried 5V to ALM+ and ALM- to dx_ERR pin, dx_ERR to ALM+ and ALM- to gnd, etc. I thought this was a simple optocoupler that would close the contact. In normal state the ALM+ and ALM- reads 16 mOhms, in alarm state, this goes to 0. Why can't I trigger the error on the duet??

Currently, my workaround is 24V to ALM+, ALM- to a separate 4 channel relay which closes a contact to ground out the dx_ERR pin. This works fine. I am ok with this workaround but it adds complexity.

Am I missing a resistor somewhere to be able to hook straight up to the duet? Perhaps the separate channel relay is safer anyway by putting an optocoupler in the way.

For clarity, this is the drive pins:

The duet

And the selector