We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I have a question about what to do if the ethernet link goes down (eg someone pulled the cable out) while TCPnet is running.
It mostly seems to be fine in that the ethernet traffic resumes if the same cable is replaced. However, my understanding is that if DHCP has been used to obtain an IP address, then the DHCP should be used to renew the lease when the link comes back up, which TCPnet does not do.
TCPnet seems to assume the old IP address is still OK. It *probably* will be if it is reconnected to the same network, but almost certainly won't be if it is connected to a different network.
I can't find a way of forcing the correct behaviour through the API.
Comments?
Christopher Hicks ==
"However, it doesn't apply if the device is reconnected to a different network."
To do that, you'd first have to detect that the link was down. Probably easiest to check the appropriate PHY register. Then you'd have to give the DHCP client a kick. Unfortunately I think you're right - I cannot see any such facility in TCPnet.
Now if Keil had a sensible pricing structure to gain access to the TCPnet source ...