after job start i lose the connection
I have a problem with two duet2 ethernets of around 20 installed.
When I start a print job, it loses the connection to the webcontrol shortly thereafter and can only be found again after the job.
sometimes only when the printer has been reset.
ping does not come, even though the display shows an IP.
I then updated to the new firmware and still have the same problem.
I ask for help.
Sounds like electrical interference. What troubleshooting have you already done? Changed/swapped/moved ethernet cables? Are all machines identical, and config.g the same? If so, if you swap one of the problem Duets to another printer, does the problem follow the board or stay with the printer? If you can run M122 after reconnection (or immediately after reset), and post the response here, that may help.
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet Ethernet 1.02 or later
Board ID: 08DGM-917DA-G4MS8-6JKDL-3S46Q-TVT3B
Used output buffers: 3 of 24 (6 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 92856 of which 0 recycled
Exception stack ram used: 320
Never used ram: 12184
Tasks: NETWORK(ready,764) HEAT(blocked,1232) MAIN(running,3816) IDLE(ready,160)
=== Platform ===
Last reset 04:08:33 ago, cause: software
Last software reset at 2019-12-18 07:46, reason: User, spinning module GCodes, available RAM 12032 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 21.5, current 22.8, max 23.1
Supply voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-12-18 11:55:39
Cache data hit count 4294967295
Slowest loop: 4.53ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 4.97ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex
=== Filament sensors ===
Extruder 0 sensor: ok
I have already switched from 1.22.6 to 2.04.
I produce printers and always have the same config and firmware on them.
Lan cable is certainly not a problem since I have tested it on other printers and there are no problems.
If this is a guarantee case, I will be happy to discuss this with roland.