W5100 ping but no response
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: W5100 ping but no response
by Edward ·
Hi.
I’m checking to your configuration.
First, you checking to ping ?
If you can ping
It is not ethernet shield problem.
otherwise checking RJ-45 LAN LED(yellow and green)?
one more checking to your code.
Thank you
RE: W5100 ping but no response
by Coccoliso ·
hi,
the module does not have an http server “native” to do this then I hope that you put on the embedded side the software to response for incoming http request of index.html
RE: W5100 ping but no response
by I14R10 ·
Hi, sorry for not responding.
So, this happens. Of course, I have a software library included in my project. W5100 works for about 10-15 minutes normally and after that I can’t reach it over the browser, only from console by pinging it’s IP address. Is it overheating maybe?
RE: W5100 ping but no response
by Coccoliso ·
Hi,
you should understand if is reception part that goof after a number of bytes received or simply spent time a lot of time…
if you think it’s the heat, you should have the same result by leaving the chip power also limiting the reception.
But if instead it happens after a constant number of received bytes then it probably are rx pointers vs data readed num not coherent (and hangs receiving logic).
Check the logical at buffer-overflow time sending bytes for a number sufficient to fill the receive buffer as soon as possible and if everything hangs before 15 minutes are pointers