@dc42
that sounds very promising!
I use the Duet3D ecosystem in my printer as well in some prototypes for special machines which have nothing to do with CNC or 3D printing.
I did a quick google but didn't find a current readmap. I am very interested in what else is planned 
You guy are doing a great job!
@jay_s_uk
I have already spent several hours printing with the toolboard.
Connected to the Toolboard are:
Extruder motor
Axis Endstop
Heater Cartridge
PT1000 sensor
Duet3D Filament Monitor: Rotating Magnet Version
Everything works fine except the accelerometer.
@jay_s_uk
I ordered the toolboards from Filafarm on 10.01.22
https://www.filafarm.de/products/duet-3-toolboard-1lc
The link refers to PCB version 1.1, but I received version 1.2 from Filafarm.
@jay_s_uk
I have already spent several hours printing with the toolboard.
Connected to the Toolboard are:
Extruder motor
Axis Endstop
Heater Cartridge
PT1000 sensor
Duet3D Filament Monitor: Rotating Magnet Version
Everything works fine except the accelerometer.
i already had on release 3.4.0 beta 7 with the same problem. I had of course also upgraded the toolboard to the current firmware.
I have downgraded again to 3.3 due to other reconfiguration efforts.
The board is a PCB version toolboard v1.2
Hi,
on my toolbard it does not recognize the accelerometer. I have also tried the latest beta firmware without success.
M122 B21
Diagnostics for board 21:
Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 3040, free system stack 2762 words
Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.2%,115) CanAsync(notifyWait,0.0%,57) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) TMC(notifyWait,2.9%,57) MAIN(running,92.0%,352) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:06:23 ago, cause: software
Last software reset data not available
Driver 0: position 0, 400.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 24, reads 60773, writes 11, timeouts 0, DMA errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 0/5, peak Rx sync delay 218, resyncs 0/0, no step interrupt scheduled
VIN: 26.1V
MCU temperature: min 33.3C, current 36.8C, max 36.8C
Ticks since heat task active 247, ADC conversions started 382218, completed 382217, timed out 0, errs 0
Last sensors broadcast 0x00000004 found 1 2 ticks ago, loop time 0
CAN messages queued 4844, send timeouts 0, received 3478, lost 0, free buffers 37, min 37, error reg 110000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer detected: no
I2C bus errors 0, naks 3, other errors 0
=== Filament sensors ===
Interrupt 4 to 8us, poll 8 to 714us
Driver 0: pos 0.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
M955 P21.0
Error: M955: Accelerometer 21.0 not present
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TN-6J1D2-3SD6J-9BBYT
Used output buffers: 3 of 40 (23 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 92676 of which 320 recycled
Never used RAM 107436, free system stack 152 words
Tasks: NETWORK(ready,30.4%,206) ETHERNET(notifyWait,0.1%,117) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,266) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.7%,59) MAIN(running,61.6%,924) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:09:54 ago, cause: software
Last software reset at 2022-01-26 10:05, reason: User, GCodes spinning, available RAM 110644, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 137
MCU temperature: min 32.6, current 37.6, max 37.8
Supply voltage: min 25.8, current 25.9, max 26.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/16/16, gc cycles 0
Driver 0: position 0, standstill, reads 16974, writes 19 timeouts 0, SG min/max 0/181
Driver 1: position 0, standstill, reads 16974, writes 19 timeouts 0, SG min/max 0/236
Driver 2: position 60000, standstill, reads 16974, writes 19 timeouts 0, SG min/max 0/206
Driver 3: position 119680, standstill, reads 16975, writes 19 timeouts 0, SG min/max 0/238
Driver 4: position 0, standstill, reads 16971, writes 23 timeouts 0, SG min/max 0/910
Driver 5: position 0, standstill, reads 16980, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2022-01-26 10:15:50
Slowest loop: 132.34ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.2ms, write time 39.8ms, max retries 0
=== Move ===
DMs created 125, maxWait 71427ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 21, completed moves 21, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.9
Heater 2 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by 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
Code queue is empty.
=== Filament sensors ===
Extruder 1: no data received
=== CAN ===
Messages queued 5381, received 7494, lost 0, longest wait 4ms for reply type 6024, peak Tx sync delay 325, free buffers 49 (min 48), ts 2971/2970/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 185.17ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 2 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
@dc42
that sounds very promising!
I use the Duet3D ecosystem in my printer as well in some prototypes for special machines which have nothing to do with CNC or 3D printing.
I did a quick google but didn't find a current readmap. I am very interested in what else is planned
You guy are doing a great job!
Is it possible to move one axis asynchronously to another?
What exactly do I want to do:
Assume I have two axes Z and X.
I want to move Z. Let's say G01 Z100 F100.
Independently I want to move X with G01 X200 F500
Both axes should start at the same time but move independently.
Is this possible somehow?
That sounds really great. I just got rid of the proprietary electronics on my Craftbot3 printer and installed a Duet3 6HC board instead.
The previous display was also a 3.5 inch display.
So I am very interested in a latest generation RepPanel.
If you need someone to test it, I hereby announce my willingness
Greetings from Heidelberg