HI,
At some stage, I would like to start interfacing using TCP/IP. Either direct or via internet explorer. I had view assembly codes examples and even purchases from microchip their TCP/IP demo board. (did not go to far with this, assemble is not my thing)
I am in no real hurry for this as I have other jroject on the go, however, at some stage i would like to interface my project onto the PC via TCP/IP.
I would like this to be added to the Wish list, prefer the will happen list Date to be determined.
ANDREW
TCP/IP suport
The answer is yes. The question is, is there enough demand to justify providing this service? I forgot the exact name, but serial modem TCP/IP is one of the many services defined for TCP/IP, and would fit into the TCP/IP services package.It would be great if you could serve small web pages through the serial port. Couldn’t this be done on some old serial based modem protocol or something?
As I think about it, this might be another way to do a quick-and-dirty HMI (see ethernet board post). It could concievably be used in conjunction with an RS-485 network. With RS-485, it would be a lot cleaner if there were a gateway pic, because the serial TCP/IP expects to see a single serial port. It would certainly be easy to do with one PIC communicating over RS-232.
There are some possibilities here....
I think it would be easier and more professional looking if you could configure your project using a web page in internet explorer than having to use HyperTerminal.
And if that interface was provided by a serial cable driving a modem protocol which windows would recognize automatically then it's a much cheaper solution than having to buy an enternet card.
If you then decided to use your project remotely using the internet then you already have your web server built in you just tell it to use the enternet card instead.
As for demand I think most people want a cool web server thing for their application so if there is a way of providing this with out having to shell out for an enternet card which if you are just connecting to one pc is a waste of money it is a good thing.
And if that interface was provided by a serial cable driving a modem protocol which windows would recognize automatically then it's a much cheaper solution than having to buy an enternet card.
If you then decided to use your project remotely using the internet then you already have your web server built in you just tell it to use the enternet card instead.
As for demand I think most people want a cool web server thing for their application so if there is a way of providing this with out having to shell out for an enternet card which if you are just connecting to one pc is a waste of money it is a good thing.
That's a long sentence; some commas would help.As for demand I think most people want a cool web server thing for their application so if there is a way of providing this with out having to shell out for an enternet card which if you are just connecting to one pc is a waste of money it is a good thing.
I agree, I was just trolling for some comments from some of the people who stated earlier that this was what they wanted, such as Steve in Australia.
This, if done right, would probably satisfy pretty much everybodys' needs and wants, for precicely the reasons stated. You could have a quick-and-dirty, and yet somewhat sexy, web interface on the cheap, which could be extended later. And, as I said, with a PIC as a gateway, you could commuinicate with a CAN or RS-485 or 1-wire network with multiple nodes located remotely.
Next question: Can the serial TCP/IP service be made to work through a USB interface? I'm sure this can be done, because there are USB modems. This would be the icing on the cake, because a lot of motherboards don't have comm ports. It would be really, really nice if a USB-enabled PIC could talk to a browser through the TCP/IP stack, and the USB interface.
Sorry for my poor punctuation it’s getting a bit late here and I’m not that great at it at the best of times.
I agree that if you could do with serial you probably could do it with USB also should work for Bluetooth if you wanted to go wireless as that has a modem protocol.
I think it would be the best way for communicating with a pic locally as it’s the way most users are use to doing things now and the added benefit that it would be upgradeable is a real winner.
Lets hope that if it can be done someone can be bothered to do it and that it will be included in the Micro(Pascal, Basic, C?) libraries.
I agree that if you could do with serial you probably could do it with USB also should work for Bluetooth if you wanted to go wireless as that has a modem protocol.
I think it would be the best way for communicating with a pic locally as it’s the way most users are use to doing things now and the added benefit that it would be upgradeable is a real winner.
Lets hope that if it can be done someone can be bothered to do it and that it will be included in the Micro(Pascal, Basic, C?) libraries.
I had a little look on the web for pic web severs and the really small ones seem to use SLIP (serial line ip)
Basically it is a very simple framing protocol that uses two bytes a start of frame byte and an end of frame byte, can’t get much simpler than that.
So would be a piece of piss to implement but then you would have write a tcp stack.
But creating a connection to a slip device seems possible in xp had a little look and there is an option.
I think I will wait till the release of microC and if it doesn’t already have a tcp stack I might look into porting one from somewhere as there is a few written in c that I found.
Basically it is a very simple framing protocol that uses two bytes a start of frame byte and an end of frame byte, can’t get much simpler than that.
So would be a piece of piss to implement but then you would have write a tcp stack.
But creating a connection to a slip device seems possible in xp had a little look and there is an option.
I think I will wait till the release of microC and if it doesn’t already have a tcp stack I might look into porting one from somewhere as there is a few written in c that I found.
1) SLIP was what I was thinking of. I'm not hallucinating.
2) "Piece of piss"? You Englishmen talk funny.
3) Based on statements in the ethernet thead, it is safe to assume that a TCP stack is in the works.
4) In general, the libraries for Pascal, Basic, and C are the same. If the stack is ready in this next release, I would expect it to be in all languages. My understanding is that the .mcl files for the three languages are interchangeable, and that you can "mix and match" libraries between languages. So, anything written in C which can be made into a procedure library will be usable with all three languages.
If these C procedures are GNU or free, they should, in theory, be convertable into libraries for all to use.
2) "Piece of piss"? You Englishmen talk funny.
3) Based on statements in the ethernet thead, it is safe to assume that a TCP stack is in the works.
4) In general, the libraries for Pascal, Basic, and C are the same. If the stack is ready in this next release, I would expect it to be in all languages. My understanding is that the .mcl files for the three languages are interchangeable, and that you can "mix and match" libraries between languages. So, anything written in C which can be made into a procedure library will be usable with all three languages.
If these C procedures are GNU or free, they should, in theory, be convertable into libraries for all to use.
and
I was wondering when someone would do that. The Realtek parallel interface is an unweildy mess. 100 pins! SPI would be much cleaner. The questions I would have are:
1. Is it a complete ethernet solution, or does it need a seperate PHY device?
2. With the history that microchip has had for late delivery, when is it realistic to actually see these?
3. If this is real, will mE support this?
1. Is it a complete ethernet solution, or does it need a seperate PHY device?
2. With the history that microchip has had for late delivery, when is it realistic to actually see these?
3. If this is real, will mE support this?
If you know what you're doing, you're not learning anything.
Oh, the ENC28J60 is there quite a while (however not available yet):Storic wrote:It is not on the microchip website as yet.
http://www.microchip.com/stellent/idcpl ... e=en022889
Or did you mean something different?
I was with a Microchip rep on Monday and was given a demo of the ENC28J60 on their new evaluation board.
The TCP/IP stack code is a free download, and the topic is covered in depth on the Microchip site at:
http://microchip.com/stellent/idcplg?Id ... odeId=1489
As for the chips themselves, I was told that they're sampling imminently - with production chips due to become available in the next 3-4 weeks.
The TCP/IP stack code is a free download, and the topic is covered in depth on the Microchip site at:
http://microchip.com/stellent/idcplg?Id ... odeId=1489
As for the chips themselves, I was told that they're sampling imminently - with production chips due to become available in the next 3-4 weeks.
