Problem with networking and DWC
-
Just to be sure you could download this one and place it in /sys and give it one more try.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2CombinedFirmware.bin
And just in case, grab these two iap files and place them in /sys as well, over write what you have in there already.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.03/iap4e.bin
https://github.com/Duet3D/RepRapFirmware/releases/download/2.03/iap4s.bin
What device is .134?
-
@bjackson said in Problem with networking and DWC:
I have emailed Filastruder and asked for an RMA, starting with the little ethernet daughter board. I feel like I really need to try to do something to prove or eliminate hardware failure as a possibility.
If we can't get it figured out, yes we will get it exchanged. It's just very rare for an ethernet to fail to connect for hardware reasons, though not impossible.
Could you provide some close up photos of the module and board area?
-
I obtained those three files and put them in the /sys folder, overwriting whatever I might have had with the same names. It still comes back from M115 reporting no change in the firmware version. After it recovered from the supposed firmware update, I checked, then I powered down the board, re-energized it again, and checked again. Still no change.
BTW, at this time, I don't have the printer power supply on. The board is being powered via USB. I presume that's enough power available to run the ethernet too?
As for device .134, I can only guess. I did not create those testlog files, but I assume somebody did who was doing final QC on the equipment before releasing it for distribution. I would assume it was a computer they used to test network connectivity to the board. It seems to say that it worked at one time.
I have attached a couple of photos. I even got one that actually caught the green activity light on the ethernet jack on for a quick flash. You can barely make out the orange glow from the link light on the other side of the plug retainer.
)
-
@bjackson said in Problem with networking and DWC:
The board is being powered via USB. I presume that's enough power available to run the ethernet too?
Normally it would be. Perhaps your supply can't keep up? Have you tried applying VIN yet?
@bjackson said in Problem with networking and DWC:
I assume somebody did who was doing final QC on the equipment before releasing it for distribution.
Yes, of course. I was being dense.
-
It was also suggested to me by someone far more on the ball than me that there might be an issue with auto negotiation, so see if your router/switch has the option of forcing the link to 100 full duplex.
-
Have you tried applying VIN yet?
Yes, I did try that. That doesn't change the behavior I'm seeing. The computer who's USB port is powering the board for these tests is a very standard Dell Optiplex 755 desktop machine.
I left things up over night and looked again at the packets that Wireshark had captured. All I'm seeing is IPv4 and IPv6 packets coming from the computer, and nothing coming from the Duet.
The auto-negotiation issue was considered. Right now, I'm using the super simple test environment of the computer connected to the Duet board with an ethernet cable. The router is not involved currently.
I went into the speed/duplex settings for the network card on the computer and experimentally set it to 100 half, and 100 full. Those choices did not work, but in fact made the error messages seen when trying the ping command to be more severe
I put it back to Auto. -
@bjackson Can you try the Duet again directly connected to your PC? Assuming the PC isn't connected to any other network, you only need to set the ethernet adaptor's IP address and subnet mask, and the Duets IP address and subnet mask. If the PC is connected to another network through another adaptor (WiFi or wired), you just need to make the Duet/PC network sufficiently different. See https://duet3d.dozuki.com/Wiki/Setting_up_networking_on_Duet#Section_Wired_direct_connection for full details.
Are you actually editing the config.g with the new settings, or typing them in through a serial console (eg YAT) over USB? The settings you used in your original post come from the standard SD card contents: https://github.com/T3P3/Duet/blob/master/Duet2/SD Card Contents/sys/config.g
I can't remember if changing network settings take immediate effect, or if it's better to disable the network, change the settings, then enable network. But it may be worth trying in this order.
Finally, check the SD card has a www folder, which should contain the files for the Duet Web Console (DWC). See here for the folder structure and contents: https://duet3d.dozuki.com/Wiki/SD_Card#Section_Creating_the_file_structure
Ian
-
@bjackson reading down from the top it looks like you have had the Duet Ethernet connect directly to you laptop by a network cable and both configured with 192.158.1.x IP addresses?
If you then connect in YAT and send:
M552 S0 (to disable the network)
then
M552 P192.168.1.14 S1 (to enable the network and set a fixed IP)The you should be able to pin 192.168.1.14 from your PC
If that does not work then please use this thread as a warranty replacement authorisation.
-
it looks like you have had the Duet Ethernet connect directly to you laptop by a network cable and both configured with 192.168.1.x IP addresses?
I've tested both ways, i.e. single cable between the computer and board, and also both of them connected to LAN ports on a router. No difference in behavior seen.
When I power up the board and send commands M552, M553, and M554, it tells me these things:
Network is enabled, IP address is 192.168.1.14
Subnet mask is 255.255.255.0, Gateway is 192.168.1.254
That just upon powered up the board. It has those settings because of lines in config.g Ping does not work.M552 S0 (to disable the network)
then
M552 P192.168.1.14 S1 (to enable the network and set a fixed IP)OK, I followed those steps exactly, still no response to ping even though the network status lights next to the RJ45 network connection jacks both on the computer and on the board look as they should.
If that does not work then please use this thread as a warranty replacement authorisation.
At this point, do you think I should be attempting to RMA the whole thing, or just the ethernet daughter board. If networking was the only issue, I'd perhaps lean towards just the daughter board, but I also have the firmware upgrade issue.
As for that, due to the fact I'm new to this device, I leave more room for sure that I'm just not doing something right. Some very helpful folks here did point me with explicit links to the files needed, and reviewed the command to be given, but it always comes back reporting firmware as 2.03, not 2.05.1 as hoped.
Of course, I'd really like to get all the way to the latest current stable release of firmware. Is there any way that I could lay my hands on a board that's already in that state? If not, I'll keep trying to get there.
-
@bjackson said in Problem with networking and DWC:
I leave more room for sure that I'm just not doing something right.
if you're up for using something teamviewer, anydesk, chrome remote desktop, vnc etc to your computer that is both online and directly connected to the duet with ethernet and usb I'm sure myself or someone else could take a quick look to rule out that
-
@bjackson - Tim here, from Filastruder. You've been through enough troubleshooting - send the board to the address on our website's contact page, along with your original order number, and we'll troubleshoot it and either upgrade it and send it back to you, or replace it (with updated firmware) as needed.
-
I'd be happy to try that first. If we don't prevail, then I will send the board to Tim Elmore at Filastruder, as he offers.
We can use any sort of remote desktop assistance tool that you like. The machine in question has Windows 10 Pro installed, so that means "Quick Assist" (which I believe is Microsoft's own replacement for what used to be called "Remote Assistance") is built in, and I have used that a few times. Then of course there are things like Team Viewer, realVNC, and so on. Honestly, it's whatever tool you prefer that I will use.
I will just quickly restore the setup to one where the router is involved so everything has Internet access.
I am in Oklahoma, thus on central daylight time. What sort of time and day did you have in mind?
-
@bjackson I'm sorry I missed this earlier; and I'm affraid I won't be near a computer before Monday. Sounds like Tim will sort you out if no-one else can help you though. Best of luck!
-
If you are still willing to take a look at the issue, I will make myself available on Monday whenever you would like. If we don't manage to figure it out pretty quickly, then of course I will send the boards back to Tim for review.
Do you have any idea of what time of the day would probably be most convenient for you. I can shuffle things around as needed. Your profile suggests that you are about 7 hours ahead of my time zone.
-
@bjackson said in Problem with networking and DWC:
Put the card back, powered up, ran M997 S0:1
Try just M997 without any parameters.
-
I did just try M997 with no paramaters, but the result was the same. Like before, it reports the USB interface will be shut down for the upgrade. When I connect back to the board later, it's still at 2.03.
-
I think at this point it's best to just take Tim up on his offer and ship it back to Filastruder for some testing and possible replacement.
-
Closing the loop on this: Board received, managed to update the firmware via bossac, but the board drops USB connection when trying to do network commands like M552 S0/S1. Warranty exchange in progress.
-
@elmoret Thanks!
-
This has been great support from Tim and Filastruder. When I get a board back here, I will restart this project and move closer to the goal of having a FolgerTech FT-5, R2 running with Duet controls.
I still may have a question or two down the line as I'm still pretty new to 3D printing, and the building of customized hardware configurations for such printers.
