w5500 can not connect to server after running a couple of hours
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Share projects and connect with makers.
Joined before the site update? first.
New to WIZnet Makers?
We sent a verification link to your address. Open it to activate your account, then log in.
Accounts from this email provider are reviewed by an administrator after verification. Approval usually takes one business day.
Already have an account?
Enter your email address. If it belongs to an account, we'll send a link to set a new password. Members who joined before the site update use this to set their password.
If an account uses that address, we sent a link to set a new password. The link works once and expires in 30 minutes.
Know your password?
Need an account?
RE: w5500 can not connect to server after running a couple of hours
by Eugeny ·
[quote=“peter1104, post:1, topic:3190”]
4) but it can not connect to server after correctly running a couple of hours, when I check the log, I found the socket established [opened?] well, and after issuing a connect command, the snsr was always syncsent status,[/quote]
This needs further troubleshooting:
You mean W5500 is stuck in SYNSENT state, you power cycle W5500, and after it initializes it still can not connect to the server? If yes, then what do you do to make it cinnecting again?
So you unplug cable from the W5500 and plug into PC, that PC using this cable and this port of the switch cable is connected to can connect to the server?
RE: RE: w5500 can not connect to server after running a couple of hours
by peter1104 ·
thanks for your reply.
#1 I am not familiar with wireshark, but I will try.
#2 I will try to dump all.
#3 even power w5500 off and on for a couple of times, w5500 can not connect to the server. but if I tried, for example, 20 times, there might be one successful connection, or if I ping the w5500 ip(when it is in synsent status), w5500 can connect server immediately.
#4 yes, PC can use the same cable and port to connect server, so it is not problem with cable and port of switch.
By the way, before connecting to server, w5500 can get ip assigned from dhcp server (I copied the official reference codes about how to parse dhcp) successfully. In my codes, w5000 get ip assigned from dhcp server and connect to application server immediately, shall I need to wait for some time before connecting and after getting ip assigned?
Peter Fu
RE: w5500 can not connect to server after running a couple of hours
by Eugeny ·
Sounds like there’s an issue with ARP cache, and not only at W5500 side.
Let’s make a quick check:
RE: w5500 can not connect to server after running a couple of hours
by peter1104 ·
@@1. codes below is to get register set from response of dhcp, also, I copied the mac of my wifi module (wihch driving w5500 through spi, the mac is officially assigned, and wifi module won’t connect any wifi route or switch), so it won’t be a locally admined or multicast, by the way, when first plugging in the cable, it works for a couple of hours with the same mac)
@@2. yes, I can find the log in order:
@@3. yes, you can find the any_port++
RE: RE: w5500 can not connect to server after running a couple of hours
by becky ·
Hello,
It would be better to check the packets with wireshark. Connect w5500 and PC to Dummy Hub and check on PC. You can download wireshark at Wireshark · Download and it is simple to use.
By clicking below, you can see all the packets sent and received on the network.
To see only packets that communicate with your server, write the server ip in the blank. (ip.addr = xxx.xxx.xxx.xxx)
For the connection to be successful, there should be a syn - syn, ack - ack packet. Only the syn packet will exist in the present situation. Check this out.
It is also recommended to try the connection process again after issuing the close command.
To check the ARP cache, check the ARP cache table in the server to see if the W5500 ip is set up properly.