@zapta
Is there an alternative for the ACS70331EOLCTR-2P5B3 that can be used? They are not really available at the moment and if only extremely overpriced

I have the same problem since 3.4.0beta7+7 and 3.4.0RC1.
Whenever the fan speed changes, the algorithm doesn't seem to take it into account. I always print my bridges very slowly and therefore reduce my fan speed slightly during this time, the target temperature is always overridden by approx. 5 Kelvin to the target value, even if the change is very short (e.g. 3mm bridge).

So that the prototype housing of the AWD Stepper Motor Analyzer fits quite well, just adjust a few small things.

@zapta
Unfortunately only provisionally because I don't have my 5V transformer an Arduino Uno yet

The final case is finally ready. I also installed a FlowMeter. Everything fits in and the lid even closes.
If you like, you can download the STEP file

https://a360.co/3sl2Kge

@phaedrux
Thanks for the 1st layer test, it worked wonderfully.

Here is some more information
I used a Fritzbox 7290

M122 befor crash

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJMSS-6J9DG-3SS6K-KBGBB
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 96384 of which 24 recycled
Never used RAM 103264, free system stack 200 words
Tasks: NETWORK(ready,25.6%,251) ETHERNET(notifyWait,0.2%,168) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.9%,92) MAIN(running,66.3%,925) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:07:44 ago, cause: software
Last software reset at 2022-04-03 22:26, reason: User, GCodes spinning, available RAM 103264, 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
Step timer max interval 129
MCU temperature: min 29.3, current 29.5, max 36.9
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.3, max 12.4, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 35490, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 35490, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 35490, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 35490, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 35490, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 35491, writes 14 timeouts 0
Date/time: 2022-04-03 22:33:56
Slowest loop: 7.31ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 0.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 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, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.1
=== 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
=== CAN ===
Messages queued 4182, received 3723, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 314, free buffers 50 (min 49), ts 2325/2324/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 2.49ms; 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: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0

m122 b1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.4.0 (2022-03-15 08:59:40)
Bootloader ID: SAME5x bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 158948, free system stack 200 words
Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,108) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.5%,99) MAIN(running,91.1%,442) IDLE(ready,0.0%,39) AIN(delaying,1.3%,263), total 100.0%
Last reset 00:08:45 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 55769, writes 11 timeouts 0, steps req 0 done 0
Driver 1: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 55770, writes 11 timeouts 0, steps req 0 done 0
Driver 2: pos 0, 420.0 steps/mm,standstill, SG min 0, mspos 8, reads 55766, writes 16 timeouts 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 -7/6, peak Rx sync delay 179, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.2, current 24.3, max 24.3
V12 voltage: min 12.1, current 12.1, max 12.1
MCU temperature: min 25.9C, current 26.1C, max 31.0C
Last sensors broadcast 0x00000000 found 0 68 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 4231, send timeouts 0, received 4733, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

This is an M122 via USB that I did when I couldn't connect to the 6HC anymore

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJMSS-6J9DG-3SS6K-KBGBB
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 96384 of which 20 recycled
Never used RAM 103268, free system stack 190 words
Tasks: NETWORK(ready,25.9%,227) ETHERNET(notifyWait,0.1%,168) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.9%,92) MAIN(running,66.1%,925) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:17:05 ago, cause: power up
Last software reset at 2022-04-03 22:26, reason: User, GCodes spinning, available RAM 103264, 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
Step timer max interval 131
MCU temperature: min 30.0, current 39.9, max 40.1
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.3, max 12.4, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 10937, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 10937, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 10937, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 10937, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 10937, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 10937, writes 14 timeouts 0
Date/time: 2022-04-03 23:14:12
Slowest loop: 9.23ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 1.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 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, chamber heaters -1 -1 -1 -1, ordering errs 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 ready with „m122“ 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
=== CAN ===
Messages queued 9230, received 8213, lost 0, boc 0
Longest wait 1ms for reply type 6042, peak Tx sync delay 6, free buffers 50 (min 49), ts 5130/5129/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 10.83ms; 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: 0 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 2 2 2 2 2 0 0 0
ok

M552
Ethernet is enabled, configured IP address: 0.0.0.0, actual IP address: 192.168.178.41

After that I made an M111 P1 S1.
But I still couldn't connect to the Duet. It only worked again when I restarted it.

M111 P1 S1
Debugging enabled for modules:
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15) SbcInterface(16) CAN(17)
Debugging enabled for modules: Network(1 - 0xffffffff)
Debugging disabled for modules: Platform(0) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15) SbcInterface(16) CAN(17)

Hi there i have a strange problem.
when i load DWC in Safari the connecting dialog stays openned and doesn't allow me to interact with the interface.
and if i had no connection and turn the printer off and on again i can access the DWC.
But if I then close the browser and TAP and reopen them again, I can't access via DWC again. Only again if I switch the printer off and on again and used a new tap beforehand.
Even if I have a connection to the PC and want to access the duet with my cell phone at the same time, the PC loses the connection and the cell phone cannot access it either.

The firmware on the 6HC, 3HC and the DWC are flashed to 3.4.0.
Does anyone have an idea why I have these problems

And the same i said here
https://forum.duet3d.com/post/270688

I'm trying to do this on my printer right now, but somehow I can't get S3D to output the min/max XY for the file to be printed.
Anyone have a tip on how to do this with S3D?

IMG_5123.mp4

I have the same problem since 3.4.0beta7+7 and 3.4.0RC1.
Whenever the fan speed changes, the algorithm doesn't seem to take it into account. I always print my bridges very slowly and therefore reduce my fan speed slightly during this time, the target temperature is always overridden by approx. 5 Kelvin to the target value, even if the change is very short (e.g. 3mm bridge).

I'm desperate, I just can't get the accelerometer on my Duet 3 6HC (3.4.0beta7+7) + Duet 3HC (3.4.0beta7+4) to work.
The accelerometer is connected on the daughterboard.
In the meantime I get a connection, but now I always get the message -> M956: Failed to start accelerometer data collection: INT1 error

I currently have

• the 3.3V + GND taken separately from the x.io
• the CS separately in a shielded cable
• the SDO (MISO) with a 470 Ohm resistor in series
• the remaining 4 contacts in another shielded cable

Now I have no idea what else I can do.

The M122 after error

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta7+7 (2022-01-14 08:57:59) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TN-6J1DL-3SD6P-99BAT
Used output buffers: 3 of 40 (14 max)
=== RTOS ===
Static ram: 150968
Dynamic ram: 97132 of which 92 recycled
Never used RAM 102408, free system stack 190 words
Tasks: NETWORK(ready,26.6%,233) ETHERNET(notifyWait,0.1%,173) ACCEL(notifyWait,0.0%,236) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,259) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.8%,58) MAIN(running,65.4%,925) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:12:55 ago, cause: software
Last software reset at 2022-01-23 18:38, reason: User, GCodes spinning, available RAM 102528, 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
Step timer max interval 167
MCU temperature: min 39.8, current 43.9, max 44.3
Supply voltage: min 23.8, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: pos 8000, standstill, SG min 0, mspos 8, reads 7175, writes 19 timeouts 0
Driver 1: pos 8000, standstill, SG min 0, mspos 8, reads 7175, writes 19 timeouts 0
Driver 2: pos 0, standstill, SG min 0, mspos 8, reads 7175, writes 19 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 8, reads 7175, writes 19 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 8, reads 7183, writes 11 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 8, reads 7182, writes 13 timeouts 0
Date/time: 2022-01-23 18:51:04
Slowest loop: 18.91ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.3ms, write time 2.8ms, max retries 0
=== Move ===
DMs created 125, segments created 3, maxWait 45231ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 2, completed 2, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 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, chamber heaters 2 -1 -1 -1, ordering errs 0
Heater 1 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
=== CAN ===
Messages queued 6995, received 9323, lost 0, boc 0
Longest wait 1ms for reply type 6018, peak Tx sync delay 382, free buffers 50 (min 49), ts 3880/3879/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 3.23ms; 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: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0

@gixxerfast
My setup is 1x Duet 3 6HC (3.4.0beta7+7) standalone mode and a Duet 3HC (3.4.0beta7+4) somehow doesn't give a beta7+7 version for it.

Since the update to 3.4.0beta7+7 I have several problems.

1. If I made a change in config.g, save and then confirm that I want to restart, the Duet crashes during the execution of the first command (e.g. G32 or a macro). Then it only helps if I completely de-energize the Duet.
   I can work around the problem if, after making a change and restarting the board, I first press the emergency stop symbol at the top right.
   Then the board no longer crashes after the first command.

2. When I have an accelerometer connected to the daughterboard that also has a PT100 connected, the DWC shows a sensor error and the value N/A.
   This always happens when I restart the board after making a change in config.g. If I immediately press the EMERGENCY OFF symbol again, the error no longer occurs.

3. The Duet crashes when I run the measurement with this command "G1 X-50 G4 S2 M956 P0 S1000 A0 G4 P10 G1 X50 F20000".
   A csv file is created, but this cannot be opened because the board reports it as faulty.

@phaedrux
Thanks for the 1st layer test, it worked wonderfully.