> I wanted to replace existing RS485 communication method to Ethernet
> base communication on my embedded device.
>
> Which are the protocols normally used for inter embedded device
> communication on Ethernet?
TCP is good for host pc to device communications, it has a concept of
sessions (though of course you can open and close them for each
operation, as HTTP tends to)
For simply replacing RS485 in a more peer-to-peer environment though,
UDP would be the most directly translatable in that you talk whenever
your feel like it and wait for an application level reply. You can
either take the content you would put in RS485 messages (in whatever
addressed formating you had been using) and put it instead in UDP
packets addressed to the intended device, or you can actually just
encapsulate each entire RS485 message in a UDP packet to the host (or
even sent to broadcast)
I've been looking at a device that has a legacy system of RS485
transmittable message packets, that for its ethernet option then sends
those through a TCP session. That I don't like. I'd rather open a TCP
session and converse, or send each message as a UDP packet.
Reply by ●September 8, 20062006-09-08
sorry I mean peer-to-peer only
ashu38@rediffmail.com wrote:
> Hi,
>
> I wanted to replace existing RS485 communication method to Ethernet
> base communication on my embedded device.
>
> Requirement is
> 1. To communicate with our own similar devices.
> 2. Communicate with 3rd party devices on same standard protocol.
> 3. Want to use same Ethernet port for TCP/IP web connection.
>
>
> Which are the protocols normally used for inter embedded device
> communication on Ethernet?
> Any link which does comparison of different Ethernet base protocols
> like Ethernet IP, TCP Modbus., etc?
>
> As I want Interdevice communication so I would like to have pear to
> pear communication.
>
> Regards,
> Ashu
Reply by CBFalconer●September 8, 20062006-09-08
sameer wrote:
>
> HEy can u plz send me website to get full book on RTOS in embedde
> systems....
HEy can u plz send me website to get full book on RTOS in embedde
systems....
ashu38@rediffmail.com wrote:
> Hi,
>
> I wanted to replace existing RS485 communication method to Ethernet
> base communication on my embedded device.
>
> Requirement is
> 1. To communicate with our own similar devices.
> 2. Communicate with 3rd party devices on same standard protocol.
> 3. Want to use same Ethernet port for TCP/IP web connection.
>
>
> Which are the protocols normally used for inter embedded device
> communication on Ethernet?
> Any link which does comparison of different Ethernet base protocols
> like Ethernet IP, TCP Modbus., etc?
>
> As I want Interdevice communication so I would like to have pear to
> pear communication.
>
> Regards,
> Ashu
Reply by Mark McDougall●September 7, 20062006-09-07
ashu38@rediffmail.com wrote:
> As I want Interdevice communication so I would like to have pear to
> pear communication.
I was going to suggest AppleTalk, but you need "pear-to-pear"(sic) ;)
Regards,
--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, <http://www.vl.com.au>
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266
Reply by Mike Silva●September 7, 20062006-09-07
ashu38@rediffmail.com wrote:
>...
> 2. Communicate with 3rd party devices on same standard protocol.
>...
This would seem to be a controlling factor. What protocols do these
devices understand?
Reply by Steve at fivetrees●September 7, 20062006-09-07
<ashu38@rediffmail.com> wrote in message
news:1157656975.622988.43090@p79g2000cwp.googlegroups.com...
> Hi,
>
> I wanted to replace existing RS485 communication method to Ethernet
> base communication on my embedded device.
>
> Requirement is
> 1. To communicate with our own similar devices.
> 2. Communicate with 3rd party devices on same standard protocol.
> 3. Want to use same Ethernet port for TCP/IP web connection.
>
> Which are the protocols normally used for inter embedded device
> communication on Ethernet?
> Any link which does comparison of different Ethernet base protocols
> like Ethernet IP, TCP Modbus., etc?
You need to do some reading.
> 1. To communicate with our own similar devices.
Whatever you like. I'd suggest using a header that at least says what the
body size is, and a body that encapsulates the protocol you use now. In both
directions.
> 2. Communicate with 3rd party devices on same standard protocol.
No such thing, unless you're talking http. Or unless you're using a standard
TCP/IP service, like mail, or telnet, or... etc.
> 3. Want to use same Ethernet port for TCP/IP web connection.
Then you do need to talk http. It's a client-server affair, stateless. Do
some reading. Clue: port 80.
> As I want Interdevice communication so I would like to have pear to
> pear communication.
Could be worse. Could be apples to oranges.
I suspect you mean peer-to-peer, in which case look into sockets. Define
your own packet-based protocol. Use a TCP socket pair (not pear) to exchange
packets in a well-defined format.
There are some big conceptual differences between RS-485 and
Ethernet/TCP/IP. Read up on TCP/IP. It's kinda like the OSI N-layer model,
but simpler.
Steve
http://www.fivetrees.com
Reply by Tadeu●September 7, 20062006-09-07
Maybe you could take a look at the book:
TCP-IP Lean--Web Servers for Embedded Systems
Jeremy Bentham
it is a 2002 dated book from CMP books
Grant Edwards escreveu:
> On 2006-09-07, ashu38@rediffmail.com <ashu38@rediffmail.com> wrote:
> > Hi,
> >
> > I wanted to replace existing RS485 communication method to Ethernet
> > base communication on my embedded device.
> >
> > Requirement is
> > 1. To communicate with our own similar devices.
> > 2. Communicate with 3rd party devices on same standard protocol.
> > 3. Want to use same Ethernet port for TCP/IP web connection.
> >
> >
> > Which are the protocols normally used for inter embedded device
> > communication on Ethernet?
>
> UDP, TCP, or a custom protocol.
>
> UDP is low overhead but you have to handle retries and whatnot
> in the application. TCP handles the reliability stuff for you.
> A custom protocol can have very very low overhead, but it's a
> bit of a pain when you want to do host-based programs.
>
> --
> Grant Edwards grante Yow! I once decorated my
> at apartment entirely in ten
> visi.com foot salad forks!!
Reply by Grant Edwards●September 7, 20062006-09-07
On 2006-09-07, ashu38@rediffmail.com <ashu38@rediffmail.com> wrote:
> Hi,
>
> I wanted to replace existing RS485 communication method to Ethernet
> base communication on my embedded device.
>
> Requirement is
> 1. To communicate with our own similar devices.
> 2. Communicate with 3rd party devices on same standard protocol.
> 3. Want to use same Ethernet port for TCP/IP web connection.
>
>
> Which are the protocols normally used for inter embedded device
> communication on Ethernet?
UDP, TCP, or a custom protocol.
UDP is low overhead but you have to handle retries and whatnot
in the application. TCP handles the reliability stuff for you.
A custom protocol can have very very low overhead, but it's a
bit of a pain when you want to do host-based programs.
--
Grant Edwards grante Yow! I once decorated my
at apartment entirely in ten
visi.com foot salad forks!!
Reply by ●September 7, 20062006-09-07
Hi,
I wanted to replace existing RS485 communication method to Ethernet
base communication on my embedded device.
Requirement is
1. To communicate with our own similar devices.
2. Communicate with 3rd party devices on same standard protocol.
3. Want to use same Ethernet port for TCP/IP web connection.
Which are the protocols normally used for inter embedded device
communication on Ethernet?
Any link which does comparison of different Ethernet base protocols
like Ethernet IP, TCP Modbus., etc?
As I want Interdevice communication so I would like to have pear to
pear communication.
Regards,
Ashu