W5500 재접속 관련문의
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 재접속 관련문의
by Eugeny ·
W5500 does not close socket if sees cable disconnected. The advantage of this behavior is when cable is unplugged for short time and then plugged back, all the connections continue to operate (unless some specific events happen).
You see this behavior. W5500 socket keeps being established after cable reconnection. This is not a bug - it is a feature
The socket will change its state in the following scenario - you unplug the cable, try to send some data to the peer, data will be undeliverable (cable is unplugged) and after time out period W5500 auto-closes the socket with time-out condition. You can turn internal chip auto-keep-alive functionality to regularly probe the network or perform regular probing (‘pinging’ remote device) connection by yourself.
If you are very bothered by the cable reconnections - for example for security reasons when W5500 is not physically secure and anyone can physically put man-in-the-middle device, then as soon as you see cable disconnect, forcefully close all the sockets at W5500 side and start reconnecting.
RE: W5500 재접속 관련문의
by irina WIZnet ·
안녕하세요
답변이 늦었습니다.
@Eugeny 가 말한것과 같이, TCP 동작중 이더넷 케이블을 제거한다고 하더라도, 내부에서 발생하는 Timeout시간보다 짧을 경우 계속 연결된 상태를 유지합니다. 그렇기 때문에 그문제는 버그가 아니라, 정상적인 동작입니다.
만약,TCP로 데이터를 주고 받는 상태에서 이더넷 케이블이 빠진경우
강제 Close명령을 내려서 재접속을 하도록 소스를 변경하시면 됩니다.
PHYCFGR(0x002E)의 bit '0’을 확인해서 Link 가 들어와있는지 여부를 확인해보시면 해당 동작을 실행하면 될것같습니다.

===========================
@Eugeny 가 잘 설명해주고 있네요 고마워요!