Duet 6 HC restart is taking more than 70 seconds
-
@Phaedrux yes, when applying the changes to config and restart the mainboard it takes 70secs or more to restart DWC
-
@selva_tvi that's not normal. Next time you reboot the Duet, please watch the red STATUS LED and see whether it starts flashing at 1Hz almost immediately, or whether it takes most of the 70 seconds before it does.
-
@selva_tvi standalone or SBC?
-
@oliof Standalone only
-
-
@selva_tvi I've taken a look at your config.g file. There is one line in it that is clearly incorrect:
M568 P2 S1 ; turn on mixing for tool 2
M568 hasn't been used to control mixing for many years and now serves a different function. Please remove that line from config.g. However, I don't think it has anything to do with the slow startup.
As the LED starts blinking almost immediately after reset, I suspect that the Duet is starting up quickly but the network connection is taking some time to be established. What sort of network equipment are you using?
Please try connecting a PC or laptop running a terminal emulator to the USB port. As soon as you command the reset, command the terminal emulator to connect. Then send M552 at intervals to check the network state. Also watch for any messages sent to the terminal emulator by the Duet.
One other test you can do it to command M98 P"config.g" when the machine is already connected, to see whether there is any appreciable delay before the command completes.
-
@dc42 Thanks for the support.
We are using 'Reliance Jio Router' having speed upto 300MBps.
Case 1:
I connected Duet with another router. It is Netgear.
It connected immediately. The network is established within 5-8 seconds.
So, the board and the cable is not the problem.Case 2:
I connected back to the old router. I changed the cables and changed the ports in the Router also.
Still, it is taking 65secs or more.The same router was used for Duet 3 Mini 5+ and for Duet 6 XD boards. We didn't face any issues.
Only with Duet 6 HC, we are facing this issue. (But with another router, it is not having any issues).
Are any network-related settings to be changed?
-
@selva_tvi you could try setting a static IP address in the M552 command, in case the issue is that the DHCP server in the router is taking a long time to respond.
The 6HC and 6XD use the same Ethernet interface, so I can't think of any reason why the behaviour should differ.
-
@dc42 Thanks.
We tried all the possible ways. Given Dynamic IP and tried Static IP also. But it is taking 65 secs to restart DWC.
-
@selva_tvi please use Wireshark to get a trace of trace of the traffic to/from the Duet during this 65 second period.
Here are some more tests you could do:
- Which browser are you using? Does it make a difference if you use a different browser?
- During that 65-second period, does the Duet respond if you ping it from the PC?
- Are you addressing the Duet in the browser by its IP address, or are you using its MDNS name? If you are using its MDNS name, try using its IP address.
-
@selva_tvi Does the same problem show up on multiple client devices? Is it possible to ping the board while DWC is unavailable?
-
- I tried with Chrome, Opera and Brave. All same.
- If we connect with YAT, then it responds immediately.
- Trying with IP address only.
-
@chrishamm
Yes. Almost in any phone or laptop or in any browser (Chrome, Brave or Opera)
Yes, if I connect with YAT, then at the time of restart , if I ping with YAT, it is communicating. Movements are happening.
Only DWC is taking time to reload -
@selva_tvi That sounds very odd, as if some kind of firewall was blocking your traffic for a limited time. Is there any way you could try to connect the 6HC directly to a computer and then check if the problem persists? You'd have to assign static IP addresses to both devices first, though.
-
@chrishamm Yes it is really odd. I tried with Static IP, the same.
When I use another router, it starts immediately.
As I mentioned, I am using Reliance Jio Router. (But the same router connected immediately with 6XD and Duet 3 mini boards)
-
@selva_tvi I am quite sure this is caused by your router then. You could try to assign a different MAC address to the affected board via M540 and check if that makes a difference - maybe there is still an odd rule somewhere in your router's firewall.
If it doesn't work, I'd consider a factory reset of that router although I understand that's easier said than done.