W5100 broadcast TX
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 broadcast TX
by Coccoliso ·
Hi,
), but you may use its model.
there is the DHCP client example [url]http://www.wiznet.co.kr/wp-content/uploads/wiznethome/Chip/W5100/Application%20Note/W5100_Application_Note.zip[/url] where the client sends a broadcast (UDP discover) packet “at all” and the only DHCP server responds.
Clearly you can not use this example “in toto” (as it is used by DHCP
It should be quite easy : all devices listening on a particular port and when receiving a packet (from let’s call master) can send back a response packet on same socket and they are also able to extract IP and MAC of who sent the request
(so can know master end point) .
Please note that the response packet being UDP has in his head MAC, IP and port.
Master side processing incoming packets extracts information about slaves.
RE: W5100 broadcast TX
by gman ·
Thank you Coccoliso, I’ll take a look.
It works, but the broadcast solution would be much better.
I have the whole system working(slave response, extracting MAC…). But I was not able to send the broadcast packet. At the moment I have a very ugly solution, where the master basically sends a ping request to every single IP address(one by one) in the subnet
RE: W5100 broadcast TX
by Coccoliso ·
Hi,
keep in mind that it would be good that the “master” send 1 to nSlaves broadcast query to which responds only the “slave” interrogated (the first byte sent was the “slave” number who must answer … for example).
So you are able to get the list of “slaves” connected (at “master” side) only with a round of requests and all the “slaves” know who is the “master” with only a round.
Broadcast packets occupies a lot of bandwidth and so is the case of using it as little as possible
RE: W5100 broadcast TX
by gman ·
Hi,
I am looking at the example you told me about, I found the broadcast packet, but unfortunately it is for TCP/IP, where it is very easy, just send the packet to 255. Job done.
I am using UDP protocol, do you have any idea how to do that there??
RE: W5100 broadcast TX
by Coccoliso ·
Hi,
look what you’re wrong … you must look DHCP example … and uses UDP, the ports are the 67 recorded for the server and 68 for the client.
Folder :
Source file:
Function:
You find a beautiful call at the socket function :
And it is precisely what you need a beautiful UDP broadcast to all …
Clearly you will need:
with a round of broadcast for nSlave you can find the list of all the “slave” in network.
Remember that IP and MAC of the respondent are not in the TCP registers … are inside the packet header!
See Sn_MR_UDP select case in recvfrom function.
[url]http://www.wiznet.co.kr/wp-content/uploads/wiznethome/Chip/W5100/Software/W5100_Driver_V180(0).zip[/url]
Under folder :
Source file:
Function: