Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnect
-
Yes it's a small module that can be removed.
Perhaps as part of the exploration could you grab some close up shots of it? Perhaps there is a solder point that is suspect.
-
@phaedrux Sure, once it shows up I will pull the board from the machine and see what I can see. I was just looking at the image of it in the getting started guide and saw it was plugged into headers so 2 solder joints for every connection.
Just wish mine would act up on a regular basis.. Trobinson seems to be having issues constantly. I will email MatterHackers and see if my original has made it back home. -
@Phaedrux Duet has mailed the module .. will travel across the pond so I guess it will take a while to arrive..
-
Module arrived today, will try and replace this weekend. I have had a total of 3 network failures since replacing the the board so not real often..
-
@Phaedrux I have installed the new Network Module. This second board has only failed 3 times that I know of making it very hard to diagnose. I did take photos of the solder joints of the header to board on both the old and new module as well as the top and bottom of the main board. I also looked a the surface mounted components on the module .. none of the joints look like they were cold or had large amounts of inclusions.. The photos are here.
Photos of Solder joints magnified
Now the waiting .. -
@Phaedrux Connection dropped once after replacement.. does not look like that fixed it.. Workaround using usb to disable/enable networking did work. I give up!
Will just live with it unless it starts happening much more frequently. Can't trouble shoot if it can not be reproduced on demand.. -
@Phaedrux Connection dropped again (2 times today) This time I check the monitor all was well, pulled out the print bead, Knocked off the print job with the spatula, looked at the monitor no issue. Went to fit the part, then back to the PC in the other room and now we are disconnected. Logon to octoprint and disable/enable network via usb and back in business. Seem like new module is worse than the original or it has nothing to do with the module. Well keep trying to find a way to make it fail on demand. Any of those solder joints look like an issue to you? (see previous post)
-
I didn't see any glaring issues on the photos of the soldering.
If it's happening with the new module as well I'm not sure what else to say. We've replaced the entire board and the module itself. Logically it would seem to be an issue inherent to the local network or the printer setup. Did you happen to break a mirror in the last 7 years?
-
@trobison said in Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnect:
I open up a new Enterprise HP Switch as a test. There are only two ports in use on this 24 port switch. While working on tpre0.g the network dropped and cleared all contents in the file.
Does the switch have some kind of power saving that puts it in to standby until it sees traffic??
Or, if the only other thing connected is your computer, does that have power saving enabled on the Ethernet port?
I know some machines do shut down ports when idle and the wake-up time can cause lost packets - which in theory are automatically re-sent, but that relies on a normal network driver stack..
If you are only using two ports on the switch, can't you use a direct cable & omit the switch, at least for testing?
Also, you say you are "pulling the bed out" - does that cause any motor(s) to rotate??
If it does, that could be affecting or even damaging the Duet board, as the back EMF from an externally turned motor [acting as a generator] feeds back in via the driver electronics.Robert J.
Printers: Overlord pro, Kossel XL+ with Duet 6HC and "Frankentron", TronXY X5SA Pro converted to E3D toolchange with Duet 6HC and 1LC toolboards.
-
@rjenkinsgb Wow moving the motors damage the board??? That was never an issue with the 8bit Rambo.. why in gods name would 10 year newer tech not be able to do what the old did?
This has happened with the old board in the middle of a print job. That board failed more often. Also wanted to mention again, this board and the first board were only a couple numbers different in serial number assuming that is the order they were built on the line. Frist one was w09221 and the replacement is w09219 (actually 2 units prior to the first one if they are built in sequential order)The switch is a dumb switch, not much I can do. The original board failed plugged directly into the router.
I am not sure what to say about the moving of the bed, I do that very often and have done so since 2018 and will be very difficult to stop doing. If I had known I can not do this, I don't think I would have changed boards.
I will change the end script to move the Y all thay out so I do not have to move the bed to see if that eliminates the network drop.
-
@airscapes said in Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnect:
I am not sure what to say about the moving of the bed, I do that very often and have done so since 2018 and will be very difficult to stop doing. If I had known I can not do this, I don't think I would have changed boards.
You'd have to move the bed quite quickly by hand to cause damage, and it would likely damage the driver. Sliding it out gently to remove the part shouldn't be an issue. Changing the end gcode to present the part for removal would be the best way to go, though I don't think it's the issue here.
-
@phaedrux said in Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnect:
@airscapes said in Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnect:
I am not sure what to say about the moving of the bed, I do that very often and have done so since 2018 and will be very difficult to stop doing. If I had known I can not do this, I don't think I would have changed boards.
You'd have to move the bed quite quickly by hand to cause damage, and it would likely damage the driver. Sliding it out gently to remove the part shouldn't be an issue. Changing the end gcode to present the part for removal would be the best way to go, though I don't think it's the issue here.
Oh that is good to know! It will be interesting to see if the keep happening. Have only done 4 prints jobs today with no issue.. and yes bed as been moved but am updating the end script as I go forward. Should have done that years ago, but back then did not know how..
-
@rjenkinsgb I tried several switches and a direct cable. I have then moved to a different PC when the fault happens and still have this issue. There is no power saving on any nics here. The only fix is cycling the Duet in my case. I hope to replace the Network port on the duet this weekend.
-
@trobison
I replaced the Ethernet module, and the issue returns. I upgraded to 3.4 hoping this could help, but the issue returns randomly. Cycling the Duet and I am good. The i7 screen is the only way to interact with the printer at this time. I replace the cable with a new cable during the fault. That did not fix it. Different cable and switches, I am not sure what to do next. -
@trobison said in Duet 2 Ethernet WC 3.3.0 crashes, have to reset to reconnect:
I am not sure what to do next.
I guess at this point a wireshark capture may help, but if the duet isn't even reachable by ping I'm not sure that would be fruitful.
-
@phaedrux
Ok, I have left the browser open to the Duet web page when the printer is in an idle state. It seems ok. I seem to lose connection during prints. After this print job completed, network connectivity returns.
While in a faulted state (I was losing connectivity during a print) I connected directly to a laptop (no switch). I had the same issue. After the print, connection returns.
If you are changing a file on the duet during a network dropout, it removes all content in the file, 0 bytes. That does bite when that happens. -
It sounds like maybe an interference problem? Do you have the frame, motors, etc grounded?
-
@phaedrux I believe everything is grounded. It's an E3D ToolChanger - built to their spec in the instructions. The frame is grounded, the bed is grounded, X Y Z motors are grounded. I am not sure if the extruders are grounded. The extruders are held via printed parts. Do I need to ground these? I am not sure how I can do this with the ToolChanger.
I am getting fine prints now, but the disconnections are disconcerting.
Where would you start? Any suggestions?
Regards.
-
@trobison I grounded the tool heads and verified that they are grounded. All four tool tools checked with a multimeter and they are now grounded with an extra wire in the harness.
I still have the same issue.20/03/2022, 14:43:29 Connection established 20/03/2022, 14:43:28 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 20/03/2022, 14:42:45 Connection established 20/03/2022, 14:42:45 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 20/03/2022, 14:40:54 Connection established 20/03/2022, 14:40:54 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 20/03/2022, 14:39:41 Connection established 20/03/2022, 14:39:40 Connection interrupted, attempting to reconnect... Operation failed (Reason: Service Unavailable) 20/03/2022, 14:38:18 Connection establishedI can't see anything else to ground. What else could cause interference?
-
@trobison It was a long shot. I'm really not sure what the source of the connection drops could be at this point. There's no problem with the config and we've replaced the module. Reason would say it's a network issue, but where or how is hard to determine. It's not impossible that the new module couldn't have the same issue as the old one, but we're not sure what the mechanism of failure could be.
