Adding TCP/IP Ethernet to PIC - how?
Hi All,
After searching a few threads with not quite the answers i'm looking for, i'd like to know what the preferable way is, to add TCP/IP into a PIC project.
I'm looking at using the ENC28J60 Ethernet interface, but not sure if that's the popular choice for a newbie?
From what i (mis)understand, some interfaces are somewhat intelligent and handle all the tcp/ip protocol itself, whereas the smaller cheaper interfaces are nothing more than a physical interface into the pic, and i'd need to code a LOT more low-level tcp-handling routines.....something i don't want to do.
So, trying to keep things as simply as possible, are there preferred interfaces i should go with? is there a 'how to get started/basics' thread hidden somewhere here or elsewhere on the net?
Ultimately, (like most people) i'd like to control my Pic project via the net (or internal network), simply toggling a bit on/off from a Webpage elsewhere would be nice, or serving a webpage telemetry/status indication that i can view anywhere would also be of great use.
Thanx in advance,
Marty.
Some Ethernet communication basics would be highly appreciated
Quote:
Originally Posted by
mackrackit
Hi mackrackit,
Thanks a lot for this example; sure, it'll help a lot for a start ;)
I'd like to ask a few questions here and hope some of you can give a neophyte-style answers. And please, forgive-me if my questions sound stupid, I just have no clue what the answers are!
1.- Assuming I connect a well-configured ConnectOne NANO LANReach module to a network (office or so), is it going to be "pingable" just like if I ping another PC?
2.- What is different between the possible protocols the module supports? Is it only the way the data is organized in the packet?
3.- Is there a difference if the module is directly connected to a PC or the module is connected to a network (i.e. via a switch)?
4.- What makes a module's address unique? The IP address and the port? Or is it the MAC address?
That's enough for now :o