Adding TCP/IP Ethernet to PIC - how?

[flotulopex]

Thanks a lot Dave.

I'll give that module a go...and see

[mackrackit]

A couple of things about the ConnectOne.
The pins spacings are metric
if you plan to use it as a web page server it only does port 80.

Other than that it is a good part. I have six in use currently.

[dhouston]

A couple of things about the ConnectOne.
The pins spacings are metric
if you plan to use it as a web page server it only does port 80.

Other than that it is a good part. I have six in use currently.

The WIZ110SR is easier to interface as it has a DB9 on one end and an RJ45 on the other and comes with a power supply. But, it requires more coding from the PIC side. I'll leave it to those interested to study the docs to understand the differences.

If you have an existing serial device you want to connect to the network, the WIZ110SR is the best choice. If you are designing a PCB and planning some quantity, ConnectOne (or Tibbo) is the way to go. Tibbo requires a lot of coding but they give you examples and 320K of flash to use with it. Your PIC app would probably be the simplest as the Tibbo could handle all of the heavy lifting network-wise.

One additional point in favor of Tibbo. They have a GA1000 WiFi card (802.11b/g) that connects to the EM500 via SPI. At this point they haven't released EM500 firmware to support it but they indicate it is in their plans. Some of their other modules already support it. I think it's a little cleaner than the way ConnectOne does it - mackrackit may convince you otherwise.

[mackrackit]

mackrackit may convince you otherwise.

Nope, I am not stuck on one brand, from what you tell about Tibbo I will most likely try one for the next project.

[dhouston]

Nope, I am not stuck on one brand, from what you tell about Tibbo I will most likely try one for the next project.

Buy the evaluation board for your first one. Otherwise, you'll need to design a pcb due to the 2x11x0.050inch pinout.

If you refer back to my first mention of them in this thread, you might wonder what changed my mind.

I had 100 boards (designed to use their EM202) partially assembled and placed an order (with Crownhill) for 25 of the Tibbo modules only to learn, after a couple of weeks, that Tibbo would not allow dealers to sell them to the USA. I had earlier bough a handful from another dealer that I had used for prototyping. Shortly thereafter they discontinued it. The marketing gal in Taiwan that I communicated with promised a replacement in a few months. That stretched into about two years. Still, the EM500 has convinced me to forgive (but not forget) - it really is a neat design.

I suspect they ran into patent issues with the earlier design which was in a single package similar to the Lantronix XPort.

[Charles Linquis]

I have you beat. I have over 1900 XPorts and 380 MatchPorts in the field. All connected to PICs.

[Charles Linquis]

Lantronix XPorts aren't the easiest things to use, but if you decide to use them, I can give you a lot of help.

[dhouston]

I have you beat. I have over 1900 XPorts and 380 MatchPorts in the field. All connected to PICs.

My projects are not intended for profit. They are mostly for my own amusement. It probably would not be amusing if I had to support 2280 units.

[Charles Linquis]

My projects are not intended for profit. They are mostly for my own amusement. It probably would not be amusing if I had to support 2280 units.

You are right! Supporting them isn't easy. Fortunately, they are in the hands of only 20-30 customers. That helps a bit.

[flotulopex]

...pins spacings are metric...it only does port 80...

Thanks for the tips although I currently don't understand the importance of the port number

I'm a little confused about which ConnectOne NANO module I need to order. Is it correct to choose part iL-SM2144H-I if I just need a module with pins, no WiFi, a RJ45 socket onboard? But then it is a Nano SocketLAN I want to buy not the Nano LANReach or am I wrong?

One more question about the NANO module; as I will use it to update a server's clock using NTP (or SNTP), will I need an external program running on the server to handle the time information provided by the module or is the module capable to do it all by itself?

According to Dave's post, the WIT110SR module could also be an option (http://www.wiznet.co.kr/Sub_Modules/...te3=0&pid=1040) but, at a first glance, it looks a little more complicated however it is half the price of the Nano (!).

BTW, I just found ConnectOne's LAN modules comparision chart here here.

[mackrackit]

Thanks for the tips although I currently don't understand the importance of the port number

If you have one of these modules behind a router (NAT) and another device is configured for PORT 80, say Apache for a web sever, you will not be able to serve web pages directly from the module because it only listens on PORT 80 and this can not be changed. Same if you have it set as a HTPPS server, PORT 443 is all it will listen to. This all is not a problem on a LAN.

The SERIAL NET function of these modules are not a problem, you can pick your port.

But then it is a Nano SocketLAN I want to buy not the Nano LANReach or am I wrong?

The Nano Socket family are the ones I use, they have pins. The on board antenna on the wifi module is pretty good too.

One more question about the NANO module; as I will use it to update a server's clock using NTP (or SNTP), will I need an external program running on the server to handle the time information provided by the module or is the module capable to do it all by itself?

I am not sure how to answer this one.
The module can be set to check certain time servers, it is a client.
From your other thread I think I know what you want to do. Have your own time server on a LAN that is not connected to a WAN?
If that is correct then I think it is doable...
Where ever you are getting your time from could be sent to the module with a PIC and the module FTP, SERIAL NET, email,,, the data to the server. Then the server has a script to deal with the data... Kind of like I do for temperature data??

[dhouston]

I bought one of the modules with the itsy-bitsy socket because I wanted to see whether it was practical to incorporate it in by PCB design. I decided against it but the boards themselves were the same so I just added pins in order to use that first one in prototyping. One advantage of adding the pins myself was I could mount it atop or beneath my main PCB. BTW, the support techs at ConnectOne are very sharp and well orgaized - all my questions were answered by the same tech so there was no loss of continuity. (Either they are well organized or they only have one overworked support tech.)

I know there are ways to push the time out to machines on a LAN but, as I've never had the need, I've never explored it. Search Bing (or Google?) using Time Synchronization Network (LAN) for details.

[l_gaminde]

[QUOTE=dhouston;95970]I bought one of the modules with the itsy-bitsy socket because I wanted to see whether it was practical to incorporate it in by PCB design. I decided against it but the boards themselves were the same so I just added pins in order to use that first one in prototyping. One advantage of adding the pins myself was I could mount it atop or beneath my main PCB. BTW, the support techs at ConnectOne are very sharp and well orgaized - all my questions were answered by the same tech so there was no loss of continuity. (Either they are well organized or they only have one overworked support tech.)

only one [email protected]

[dhouston]

Either they are well organized or they only have one overworked support tech.

only one [email protected]

that's the one!

[flotulopex]

From your other thread I think I know what you want to do. Have your own time server on a LAN that is not connected to a WAN?

Yes, correct.

Kind of like I do for temperature data??

No, just accurate time & date from a radio-controlled system (in Europe, it is DCF77 from GERMANY) or GPS module.

...if you are looking at a one-off design, it is ready to go out-of-the-box with no assembly required

Yup, it's a one-shot project. Anyway, I need to design a PCB for the PIC and the DCF77 receiver. But your points are pertinent...and you make me doubt about the best choice I have to go for

Let's do it a feminine way: keep the first impression as beeing the best one = NANO!

[dhouston]

Yup, it's a one-shot project. Anyway, I need to design a PCB for the PIC and the DCF77 receiver.

I'm assuming that you do not need to connect to a Network Time Server using NTP since you'll be getting the time wirelessly. You just need to then share that time with the machines on your LAN. I have no idea whether the nano can act as an NTP server, if it can then it may be the best choice but if you're going to have to write the code to push the time out over the LAN, the WIZ110SR would be my choice based on initial cost and its out-of-the-box readiness.

[flotulopex]

...You just need to then share that time with the machines on your LAN

YES... and NO.

The LAN is dedicated to a security CCTV and access control system. Time has to be "minute" accurate so I prefer to have a good time-base that will adjust the time once or twice a day or so.

NANO does NTP according to its datasheet. Nevertheless, I'll have a deeper look @ WIZ110SR. Actually, I could buy both...and try!

Thanks a lot for your advice... and experience too

[dhouston]

According to Dave's post, the WIT110SR module could also be an option (http://www.wiznet.co.kr/Sub_Modules/...te3=0&pid=1040) but, at a first glance, it looks a little more complicated however it is half the price of the Nano (!).

As I noted above, of the three (ConnectOne, Tibbo, WIZNet), the WIZ110SR will require the most coding on the PIC end but, if you are looking at a one-off design, it is ready to go out-of-the-box with no assembly required.

If you are planning for volume and designing a PCB, I would go with ConnectOne or Tibbo and the choice would probably depend on the application. The Tibbo, with its own program memory offloads nearly all of the network coding but does mean you are working with two different Basic dialects. I think, if you study the docs I've referenced, you'll be most impressed with the Tibbo. I design projects that usually have some DIY elements and the flexibility of the Tibbo and the fact it is programmable in Basic make it attractive in that environment. Plus, users can reprogram as needed if I become totally incapacitated.

BTW, when I bought my ConnectOne modules they had not released the SocketLAN so I added my own pins to the LANReach. I tend to use the latter term to apply to either.

[dhouston]

Here are some additional links.

Charles Linquis PIC code to get network time...http://www.picbasic.co.uk/forum/show...k+time+charles

Tibbo's example code to get network time...http://basic.tibbo.com/resources/web/internet_time.html

You should be able to compare and contrast those and learn a bit that you can then transfer to either the ConnectOne or WIZNet devices.

Here's Tibbo's other examples...http://basic.tibbo.com/resources.html

Once you grasp that Tibbo uses an object oriented Basic dialect, it should be fairly simple to convert the code to a PIC.

I would share my PIC code but the truth is I have none. I use mostly 8-pin PICs for small special single-purpose applications. Most then link serially to a ZBasic chip which I find much easier to work with for complex problems. I'm an old geezer (69) with major health issues who has neither time nor desire to become an ASM wizard like Darrel Taylor (much, much younger) or Bruce Reynolds (also much younger) so I prefer a chip that has two hardware serial ports plus 4 software serial ports all of which are buffered, full-duplex and operate in the background as well as numerous other features of similar power (that would require Darrel or Bruce to duplicate with PBP) for major projects. Plus, my ZBasic code is proprietary.