W5500 as a server deals with communication problems
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 as a server deals with communication problems
by Eugeny ·
You should not just close the hyperterminal. Connection should be terminated properly. If there was connection established between your client and W5500 as server, your client should send disconnect request to W5500 before shutting down the channel.
Solution for your 0x16 problem: always use new source port number. First connection - port number c001, you use server and then properly close the connection, and second time you connect with port number c002. The issue is simple - when you use same source port connecting second time W5500, router or bridge may think that new connection is continuation of previous communication, but as soon as previous communication was already closed, “re-using” same port confuses all devices on the network.