@phaedrux Thanks a lot. I will do that.

@phaedrux yeah it is dynamic IP.
No I do not have a reservation set however, I can see from my router software which IP address it gave to each printer.

After 20 minutes or so, the IP address changes on the router software so probably there is a communication issue somewhere and with the new IP address I can connect to the printer.

However, the problem occurs on one of the duets and always the same one.

@didiz just for info, after 20 minutes or so routers changes the IP and it is possible to connect. Each time it is the same.

Hello,

I have 4 Duet 2 wifi and 3 of them connect to Wi fi without problem by the time I turn on the printers. One of them seems to be connected from the routers application but when I try to connect to web interface by putting the IP on the browser, it just does not connect saying this site can't be reached because it doesn't send any date.

I rebooted the router and other ones connect with no issue.

I had over voltage problem on the same duet before very randomly in the middle of a long print which did not repeat itself.

@dc42 Just for the information,

I restarted the printer that gave over voltage error, secured the piece on the bed and continued printing. It's been 13 hours and still printing. Most of the time I printed in between 105% to 110% and no errors what so ever.

Result of actual M122 :
Supply voltage: min 24.0, current 24.1, max 24.4, under voltage events: 0, over voltage events: 1, power good: yes

So it is very hard to find the source of these kind of errors that don't persist and are very random.

Is there anything that comes into your mind ?

Thank you so much.

@dc42 Thank you so much,

I will prepare an e mail.

Concerning the over voltage event, this happened to me twice. I couldn't find a documentation with the possible reasons. I can provide you with any information that you need. Is there any known reason to have that very rarely like this?
Supply voltage: min 23.9, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes

Here is the M122 result :

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NW4SS-6JKD0-3S86J-1BZVL
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75448 of which 332 recycled
Never used RAM 11904, free system stack 104 words
Tasks: NETWORK(ready,65.8%,233) HEAT(delaying,0.6%,330) Move(notifyWait,6.8%,303) MAIN(running,24.6%,445) IDLE(ready,2.2%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 12:05:10 ago, cause: power up
Last software reset at 2022-02-13 20:09, reason: User, GCodes spinning, available RAM 11904, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 39.4, current 41.1, max 60.6
Supply voltage: min 24.0, current 24.2, max 30.5, under voltage events: 0, over voltage events: 1, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/28/28, gc cycles 0
Driver 0: position 27090, standstill, SG min/max 0/353
Driver 1: position 31041, standstill, SG min/max 0/696
Driver 2: position 25032, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max 0/1023
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2022-02-15 08:24:18
Cache data hit count 4294967295
Slowest loop: 128.19ms; fastest: 0.11ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 5.0ms, write time 2.7ms, max retries 0
=== Move ===
DMs created 83, maxWait 375409ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 466598, completed moves 466598, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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, chamberHeaters = -1 -1 -1 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Filament sensors ===
Extruder 0 sensor: ok
=== Network ===
Slowest loop: 140.00ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address f4:cf:a2:e2:1b:3e
WiFi Vcc 3.37, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25200
WiFi IP address 192.168.1.110
WiFi signal strength -74dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

@dc42 Hello,

The driver is not particularly hotter than the rest of the board. I used stock creality cables which was probably not a good idea since I make them work over long periods in an enclosure.

Could the reason be the cabling for these kind of problems?

I also had an over voltage error "Warning: VIN over-voltage event (30.5V)
" on another printer during the night. It cancelled printing. I get these errors very randomly and rarely. However since I have been doing very long prints over and over again with 1 - 2 hours cooling time in between it is hard to understand the problem and very annoying to constantly need to find a solution to save the print.

Hello @dc42

Thanks for your answer.
M913
Motor current % of normal - X:100, Y:100, Z:100, E:100
M906
Motor current (mA) - X:850, Y:850, Z:700, E:850, idle factor 30%

This is the return for the commands.

Duet is brand new, I bought it 1 month ago and the second board that I have installed is 2 months old.

I don't know how to check the driver temperature, the MCU temperature is around 45 degrees. I have used the stock cable and cut the duet side connector and crimped the connectors supplied with the board. I have connected them in series (there are 2 slots for Z motors and 2 motors)

Z motors are the stock creality motors
Brand: Creality 3D
Item name: RepRap 42 Stepper Motor
Item number: 42-34
Step angle: 1.8 degrees
Nominal Voltage: 4.83V
Current Rating: 1.5 (A)
Rated speed: 1-1000 (rpm)
Rated torque: 0.4 (NM)
Ambient Temperatuar: -20℃~+50℃
Length: 34mm

Hello,

I am having an issue with a CR10 MAX with Duet2 wifi and a volcano installed on it. There are in total of 3 printers with the same configuration in an enclosure passively heated by the heated bed and the ambient temperature is in between 30 and 35 degrees C.

So one of the printers gave this error and z motors stopped turning ended up in a big mess. I cleaned all, changed the motherboard with another printer that works fine, added another fan so now I have 1 blowing on the back of pcb and other from the side so there is an air flow and the MCU temp stays around 44 45 degrees C even for long prints. Z motor current is 0.7A however the motors get hot. The hottest of all with lowest current.

I really don't see any reason why this problem persist on the same printer. Can it be caused by cabling in that case the cables of the Z motors I suppose or can it be caused by a motor malfunction ? Please help me in this manner because I am a bit lost...

For info, I am printing big pieces from PETG taking 20 hours more or less with 28mm3/s with 1mm nozzle so the printers work hard at the moment.

Thank you so much for your help.