Many disconnects - Duet Ethernet
-
logging a session with wireshark might help shed some light on the issue, but i'd be very temped to rule out wifi of the equation.
-
randomly searched for a post of dc42 recommending grounding and this was the first post; suddenly seemed very relevant.
-
I need to check how the frame and motors are grounded. I have some electronics background and I would prefer not to have a reference between the high voltage side and the low voltage side. Any noise/static should affect both V+ and V- and cancel each other out. I need to borrow a scope
@bearer
Logging network traffic could be done. Not exactly sure what I would be looking for.As an update I get just as many disconnects while no heater or motor is running. Well the motors were holding so some current is passing through. I'm just to start a new print so I'll have to verify tomorrow.
-
@bearer said in Many disconnects - Duet Ethernet:
but i'd be very temped to rule out wifi of the equation.
@strips I agree with the above, that you need to try it without the ASUS media bridge. I'd guess wireshark would show up if this was the problem, though.
Ian
-
@strips said in Many disconnects - Duet Ethernet:
Logging network traffic could be done. Not exactly sure what I would be looking for.
me neither, but if you upload the file I'll take a look tomorrow. preferably without a capture filter
-
Ok,
I still need to eliminate the media bridge and analyse the traffic. I could just make a long TP-cable running down the stairs. My wife would freak out but it would only be temporary
Update:
I'm getting the issue with nothing turned on. I just tried to upload a file and i got a disconnect. Then I did a M999 to reboot. The first command after opening a new browser window 3 minutes after was M122. I got the output printet in console then a disconnect immediately after.08/04/2020, 10:53:01 Connection established 08/04/2020, 10:52:59 Failed to upload dwc2settings.json Could not complete action because the connection has been terminated 08/04/2020, 10:52:59 Connection interrupted, attempting to reconnect... Network error 08/04/2020, 10:52:57 M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC6 running on Duet Ethernet 1.02 or later Board ID: 08DGM-9T6BU-FG3SN-6J9FA-3SJ6P-1BWRG Used output buffers: 1 of 24 (9 max) === RTOS === Static ram: 28052 Dynamic ram: 93492 of which 44 recycled Exception stack ram used: 240 Never used ram: 9244 Tasks: NETWORK(ready,184) HEAT(blocked,1244) MAIN(running,1840) IDLE(ready,80) Owned mutexes: === Platform === Last reset 00:01:52 ago, cause: software Last software reset at 2020-04-08 10:51, reason: User, spinning module GCodes, available RAM 8788 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: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.6ms, max retries 0 MCU temperature: min 36.7, current 37.0, max 37.6 Supply voltage: min 24.0, current 24.1, max 24.1, 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: 2020-04-08 10:52:56 Cache data hit count 229791096 Slowest loop: 8.67ms; fastest: 0.12ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 150.20ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 Interface state active, link 100Mbps full duplex 08/04/2020, 10:52:29 Connected to 10.10.100.40 -
@strips Unfortunately, I can't see anything obviously wrong in that M122 report because the reset has cleared any errors. Is it possible to connect a PC/laptop/RPi to the USB port and log the debug information? If you can, send
M111 P1 S1to log network debug info, andM111 P2 S1to log webserver debug info to the USB port.If you can run a long cable to it, it would remove one possible failure point.
Ian
-
I just bought a RPI 4 and Pi-cam to use on the printer. I'll let the RPI be the wifi-bridge. Then I can have a closed network between RPI and Duet. It gives me the best way to analyse the traffic as well.
Just bear with me a few days and I'll report back when I got everything running. Depending on my wife I could have it fixed by tonight...
-
haha, with respect to the other issues is usually easier to get acceptance* if you present a worse alternative; i.e either there is a cable running downstairs, or the printer comes upstairs. Suddenly the cable looks like good option.
*) but you'll still "pay" for it I guess..
-
@bearer said in Many disconnects - Duet Ethernet:
if you present a worse alternative
Better still, don't present it, when she says no cable simply start to carry the printer upstairs. When she SEES the alternative she'll insist you run the cable.