My first 'crappy' prototype system!
Talks IP (TCP and UDP) over Ethernet (10Base-T)
Soon will serve Web pages to the Internet / Intranet!
| Just some uses |
I wish to embed this controller in my MP3 player, so I can play MP3 files directly across my network. A standard household could have one central Windows or Linux file server with a directory full of mp3 files. Then just plug multiple ethernet mp3 players into your network and all access the music from the server. No more hunting and swapping CD's. The kids can listen to their music from the server while you listen to your favorite songs in the lounge room or outside. You could even listen to the same music at once!
With wireless networking when you park your car at night, new MP3 files could be downloading to you car's stereo system ready for that long drive tomorrow.
| Description |
Pinging 192.168.0.45 with 32 bytes of data:
Reply from 192.168.0.45: bytes=32 time=15ms TTL=32
Reply from 192.168.0.45: bytes=32 time=7ms TTL=32
Reply from 192.168.0.45: bytes=32 time=7ms TTL=32
Reply from 192.168.0.45: bytes=32 time=7ms TTL=32
Ping statistics for 192.168.0.45:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 15ms, Average = 9ms
C:\WINDOWS>ping 192.168.0.45
Pinging 192.168.0.45 with 32 bytes of data:
Reply from 192.168.0.45: bytes=32 time=8ms TTL=32
Reply from 192.168.0.45: bytes=32 time=7ms TTL=32
Reply from 192.168.0.45: bytes=32 time=7ms TTL=32
Reply from 192.168.0.45: bytes=32 time=8ms TTL=32
Ping statistics for 192.168.0.45:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 8ms, Average = 7ms
This is a terminal dump of data from the Ethernet Engine's RS232 Port (19200pbs). Every time a valid packet of data comes for the ethernet engine, the processor acknowledges it with 'P'. Then the processor reports the type of packet ie ARP, ICMP (ping) UDP etc. 'W' means the processor wrote data out on the ethernet port.
WAP Embedded Ethernet 2001 Wayne Peacock Rev 1.01 Resetting Realtek RTL8019AS .... ID=Pp Realtek Found! Setting MAC address 00:00:00:12:34:56 Card Initialization Complete Setting IP address 192.168.0.45 PARP request W PPing request WPPing request WPPing request WPPing request
One of my goals is the control equipment using TCP/IP, but first I can control equipment using UDP (User Datagram Protocol).
UDP is a far easier protocol to implement than TCP, so it's a good start place. On the right is a program to send UDP packets over ethernet.
It was whipped up in Borland Builder 5 in a few minutes and simply sends a packet containing the string entered in the top memo box to the IP address entered.
Once the data is sent, 'Data Sent' is displayed in the status box.
Once the packet is received on the Ethernet Engine's side, the data in the packet is displayed on the top line of the LCD panel and sent down the RS232 port.
Already I have a system that can send RS232 commands or messages over a long distance or across the room. Whether the data gets to the server is a concern, but that's what TCP is for.
TCP will make a connection with the other end and then send the data and check that it got there. UDP just sends the packet and you assume it arrived at the other end.
PUDPWelcome! PPUDPWelcome to wayne's ethernet server! PPUDPWelcome to Wayne's super Ethernet server!
Lots more coming to a terminal near you!
| Schematics |
Coming Soon!
| Source Code |
Coming Soon!
| Useful Links |