RS232 protocol
-
I'm looking at a new project where the customer wants to use RS232 serial comms to exchange information between 2 embedded systems. (They need the new system to support legacy boxes, they can change the protocol on the old boxes but will not chnage the hardware. At the momment each box has is own way.) I'm having trouble locating an industry standard for the protocol. I've found ISO 1745 which looks like it should do the job but its dated 1975 and that just feels wrong. Does anyone know of a more recent industry standard that defines point to point data exchange over RS232? Thanks Alec
-
I'm looking at a new project where the customer wants to use RS232 serial comms to exchange information between 2 embedded systems. (They need the new system to support legacy boxes, they can change the protocol on the old boxes but will not chnage the hardware. At the momment each box has is own way.) I'm having trouble locating an industry standard for the protocol. I've found ISO 1745 which looks like it should do the job but its dated 1975 and that just feels wrong. Does anyone know of a more recent industry standard that defines point to point data exchange over RS232? Thanks Alec
-
I'm looking at a new project where the customer wants to use RS232 serial comms to exchange information between 2 embedded systems. (They need the new system to support legacy boxes, they can change the protocol on the old boxes but will not chnage the hardware. At the momment each box has is own way.) I'm having trouble locating an industry standard for the protocol. I've found ISO 1745 which looks like it should do the job but its dated 1975 and that just feels wrong. Does anyone know of a more recent industry standard that defines point to point data exchange over RS232? Thanks Alec
Hi, you can use any protocol you like, or come up with your own; I often have. It all depends on your needs (throughput, reliability, recovery, multi-drop, etc). One not so simple example is SLIP. If you roll your own, first decision is binary versus text (compactness versus ease of communication, getting all characters through the driver/modem/...). Whatever you choose, make sure you know to locate the end of each message: either prefix the length, or set a unique terminator (CR and/or LF on text). :)
Luc Pattyn [Forum Guidelines] [My Articles]
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem.