How fail-safe is nr as stop bytes?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







8












$begingroup$


In my UART communication I need to know the start byte and the stop byte of the message sent. The start byte is easy but the stop byte, not so much. I have implemented two stop bytes at the end of my message, that is n and r (10 and 13 decimal). UART only works on bytes 0-255 values so how fail-safe is this? I can imagine, though low probability, that my message might contain the values "10 and 13" after each other when they are not the stop bytes.



Is there a better way to implement this?










share|improve this question











$endgroup$








  • 7




    $begingroup$
    To send arbitrary data you either have to go to using packets or byte stuffing. In your case the probability of the pattern appearing in a certain location is 1/65536. Which gets to 1 if you have a long enough random data stream.
    $endgroup$
    – Oldfart
    Apr 18 at 10:36






  • 4




    $begingroup$
    Can you provide context please. Stop bits are part of UART communication but stop bytes? This sounds like a pure software issue and depends what has been agreed by the sender and receiver.
    $endgroup$
    – Warren Hill
    Apr 18 at 10:39






  • 2




    $begingroup$
    @MariusGulbrandsen if your data is truly arbitrary and not strictly text (think ASCII) then null termination will not work; you will have to implement a packet.
    $endgroup$
    – RamblinRose
    Apr 18 at 10:47






  • 4




    $begingroup$
    BTW: That common practice is to put the carriage return before the line feed: "x0Dx0A".
    $endgroup$
    – Adrian McCarthy
    Apr 18 at 21:16






  • 3




    $begingroup$
    @AdrianMcCarthy I think the point of reversing it is to minimize the odds of it being a valid sequence. That said, two Windows line-endings in a row would give you rnrn which contains the nr sequence in the middle...
    $endgroup$
    – Mike Caron
    Apr 19 at 16:05


















8












$begingroup$


In my UART communication I need to know the start byte and the stop byte of the message sent. The start byte is easy but the stop byte, not so much. I have implemented two stop bytes at the end of my message, that is n and r (10 and 13 decimal). UART only works on bytes 0-255 values so how fail-safe is this? I can imagine, though low probability, that my message might contain the values "10 and 13" after each other when they are not the stop bytes.



Is there a better way to implement this?










share|improve this question











$endgroup$








  • 7




    $begingroup$
    To send arbitrary data you either have to go to using packets or byte stuffing. In your case the probability of the pattern appearing in a certain location is 1/65536. Which gets to 1 if you have a long enough random data stream.
    $endgroup$
    – Oldfart
    Apr 18 at 10:36






  • 4




    $begingroup$
    Can you provide context please. Stop bits are part of UART communication but stop bytes? This sounds like a pure software issue and depends what has been agreed by the sender and receiver.
    $endgroup$
    – Warren Hill
    Apr 18 at 10:39






  • 2




    $begingroup$
    @MariusGulbrandsen if your data is truly arbitrary and not strictly text (think ASCII) then null termination will not work; you will have to implement a packet.
    $endgroup$
    – RamblinRose
    Apr 18 at 10:47






  • 4




    $begingroup$
    BTW: That common practice is to put the carriage return before the line feed: "x0Dx0A".
    $endgroup$
    – Adrian McCarthy
    Apr 18 at 21:16






  • 3




    $begingroup$
    @AdrianMcCarthy I think the point of reversing it is to minimize the odds of it being a valid sequence. That said, two Windows line-endings in a row would give you rnrn which contains the nr sequence in the middle...
    $endgroup$
    – Mike Caron
    Apr 19 at 16:05














8












8








8


2



$begingroup$


In my UART communication I need to know the start byte and the stop byte of the message sent. The start byte is easy but the stop byte, not so much. I have implemented two stop bytes at the end of my message, that is n and r (10 and 13 decimal). UART only works on bytes 0-255 values so how fail-safe is this? I can imagine, though low probability, that my message might contain the values "10 and 13" after each other when they are not the stop bytes.



Is there a better way to implement this?










share|improve this question











$endgroup$




In my UART communication I need to know the start byte and the stop byte of the message sent. The start byte is easy but the stop byte, not so much. I have implemented two stop bytes at the end of my message, that is n and r (10 and 13 decimal). UART only works on bytes 0-255 values so how fail-safe is this? I can imagine, though low probability, that my message might contain the values "10 and 13" after each other when they are not the stop bytes.



Is there a better way to implement this?







uart communication protocol






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 19 at 21:07









Nick Alexeev

32.7k1066167




32.7k1066167










asked Apr 18 at 10:33









Marius GulbrandsenMarius Gulbrandsen

169113




169113








  • 7




    $begingroup$
    To send arbitrary data you either have to go to using packets or byte stuffing. In your case the probability of the pattern appearing in a certain location is 1/65536. Which gets to 1 if you have a long enough random data stream.
    $endgroup$
    – Oldfart
    Apr 18 at 10:36






  • 4




    $begingroup$
    Can you provide context please. Stop bits are part of UART communication but stop bytes? This sounds like a pure software issue and depends what has been agreed by the sender and receiver.
    $endgroup$
    – Warren Hill
    Apr 18 at 10:39






  • 2




    $begingroup$
    @MariusGulbrandsen if your data is truly arbitrary and not strictly text (think ASCII) then null termination will not work; you will have to implement a packet.
    $endgroup$
    – RamblinRose
    Apr 18 at 10:47






  • 4




    $begingroup$
    BTW: That common practice is to put the carriage return before the line feed: "x0Dx0A".
    $endgroup$
    – Adrian McCarthy
    Apr 18 at 21:16






  • 3




    $begingroup$
    @AdrianMcCarthy I think the point of reversing it is to minimize the odds of it being a valid sequence. That said, two Windows line-endings in a row would give you rnrn which contains the nr sequence in the middle...
    $endgroup$
    – Mike Caron
    Apr 19 at 16:05














  • 7




    $begingroup$
    To send arbitrary data you either have to go to using packets or byte stuffing. In your case the probability of the pattern appearing in a certain location is 1/65536. Which gets to 1 if you have a long enough random data stream.
    $endgroup$
    – Oldfart
    Apr 18 at 10:36






  • 4




    $begingroup$
    Can you provide context please. Stop bits are part of UART communication but stop bytes? This sounds like a pure software issue and depends what has been agreed by the sender and receiver.
    $endgroup$
    – Warren Hill
    Apr 18 at 10:39






  • 2




    $begingroup$
    @MariusGulbrandsen if your data is truly arbitrary and not strictly text (think ASCII) then null termination will not work; you will have to implement a packet.
    $endgroup$
    – RamblinRose
    Apr 18 at 10:47






  • 4




    $begingroup$
    BTW: That common practice is to put the carriage return before the line feed: "x0Dx0A".
    $endgroup$
    – Adrian McCarthy
    Apr 18 at 21:16






  • 3




    $begingroup$
    @AdrianMcCarthy I think the point of reversing it is to minimize the odds of it being a valid sequence. That said, two Windows line-endings in a row would give you rnrn which contains the nr sequence in the middle...
    $endgroup$
    – Mike Caron
    Apr 19 at 16:05








7




7




$begingroup$
To send arbitrary data you either have to go to using packets or byte stuffing. In your case the probability of the pattern appearing in a certain location is 1/65536. Which gets to 1 if you have a long enough random data stream.
$endgroup$
– Oldfart
Apr 18 at 10:36




$begingroup$
To send arbitrary data you either have to go to using packets or byte stuffing. In your case the probability of the pattern appearing in a certain location is 1/65536. Which gets to 1 if you have a long enough random data stream.
$endgroup$
– Oldfart
Apr 18 at 10:36




4




4




$begingroup$
Can you provide context please. Stop bits are part of UART communication but stop bytes? This sounds like a pure software issue and depends what has been agreed by the sender and receiver.
$endgroup$
– Warren Hill
Apr 18 at 10:39




$begingroup$
Can you provide context please. Stop bits are part of UART communication but stop bytes? This sounds like a pure software issue and depends what has been agreed by the sender and receiver.
$endgroup$
– Warren Hill
Apr 18 at 10:39




2




2




$begingroup$
@MariusGulbrandsen if your data is truly arbitrary and not strictly text (think ASCII) then null termination will not work; you will have to implement a packet.
$endgroup$
– RamblinRose
Apr 18 at 10:47




$begingroup$
@MariusGulbrandsen if your data is truly arbitrary and not strictly text (think ASCII) then null termination will not work; you will have to implement a packet.
$endgroup$
– RamblinRose
Apr 18 at 10:47




4




4




$begingroup$
BTW: That common practice is to put the carriage return before the line feed: "x0Dx0A".
$endgroup$
– Adrian McCarthy
Apr 18 at 21:16




$begingroup$
BTW: That common practice is to put the carriage return before the line feed: "x0Dx0A".
$endgroup$
– Adrian McCarthy
Apr 18 at 21:16




3




3




$begingroup$
@AdrianMcCarthy I think the point of reversing it is to minimize the odds of it being a valid sequence. That said, two Windows line-endings in a row would give you rnrn which contains the nr sequence in the middle...
$endgroup$
– Mike Caron
Apr 19 at 16:05




$begingroup$
@AdrianMcCarthy I think the point of reversing it is to minimize the odds of it being a valid sequence. That said, two Windows line-endings in a row would give you rnrn which contains the nr sequence in the middle...
$endgroup$
– Mike Caron
Apr 19 at 16:05










5 Answers
5






active

oldest

votes


















14












$begingroup$

There are different ways to prevent this:




  • Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes). E.g. to send 20 21 22 23 24 25:



20 21 22 23 24 25 10 13





  • Escape 10 and 13 (or all non ASCII characters with an escape character e.g. . So to send 20 21 10 13 25 26 send: (see comment of/credits for: DanW)



20 21 1b 10 1b 13 25 26





  • Define a packet when sending messages. E.g. if you want to send message 20 21 22 23 24 25 than instead add the number of bytes to sent, so the package is:



< nr_of_data_bytes > < data >




If your messages are max 256 bytes send:




06 20 21 22 23 24 25




So you know after receiving 6 data bytes that is the end; you don't have to send a 10 13 afterwards. And you can send 10 13 inside a message. If your messages can be longer, you can use 2 bytes for the data size.



Update 1: Another way of defining packets



Another alternative is to send commands which have a specific length and can have many variances, e.g.




10 20 30 (Command 10 which always has 2 data bytes)



11 30 40 50 (Command 11 which always has 3 data bytes)



12 06 10 11 12 13 14 15 (Command 12 + 1 byte for the number of data bytes that follow)



13 01 02 01 02 03 ... (Command 13 + 2 bytes (01 02 for 256 + 2 = 258 data bytes that follow)



14 80 90 10 13 (Command 14 that is followed by an ASCII string ending with 10 13)




Update 2: Bad connection/byte losses



All of the above only work when the UART line is sending bytes correctly. If you want to use more reliable ways of sending, there are also many possibilities. Below are a few:




  1. Sending a checksum within the package (check google for CRC: Cyclic Redundancy Check). If the CRC is ok, the receiver knows the message has been sent ok (with high probability).

  2. If you need a message to be resent, than an acknowledgement (ACK/reply) mechanism needs to be used (e.g. sender sends something, receiver receives corrupt data, sends a NACK (not acknowledged), sender can than send again.

  3. Timeout: In case the receiver does not get an ACK or NACK in time, a message needs to be resend.


Note that all above mechanism can be simple or as complicated as you want (or need) to be. In case of resending message, also a mechanism for identifying messages is needed (e.g. adding a sequence number into the package).






share|improve this answer











$endgroup$









  • 1




    $begingroup$
    "Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes)." – you've not said how to send data which does include a 10/13 combination – you need to escape it. So "20 10 13 23 10 13" might be sent as "20 1b 10 1b 13 23" with 1b as your escape character.
    $endgroup$
    – Dan W
    Apr 18 at 18:33








  • 1




    $begingroup$
    Note that using a length field as proposed, you’ll get in trouble when your serial link is bad and loses a single byte. Everything will go out of sync.
    $endgroup$
    – Jonas Schäfer
    Apr 18 at 19:55










  • $begingroup$
    @DanW If you use the first one or 2 bytes as the number of data bytes, it does not matter if 10 or 13 are part of those data... So 20 10 13 23 10 13 can be send as 06 20 10 13 23 10 13 where 06 is the number of data bytes that follow.
    $endgroup$
    – Michel Keijzers
    Apr 18 at 22:08










  • $begingroup$
    @MichelKeijzers - yes, but that’s the second solution you mention. Your first solution is missing an explanation of escape sequences to prevent the stop bytes being transmitted.
    $endgroup$
    – Dan W
    Apr 18 at 22:25










  • $begingroup$
    Both approaches work, and are commonly used, but they have different advantages and disadvantages, which you could add if wanted, though it’s beyond what the OP asked for.
    $endgroup$
    – Dan W
    Apr 18 at 22:27



















13












$begingroup$


How fail-safe is nr as stop bytes?




If you send send arbitrary data -> probably not fail-safe enough.



A common solution is to use escaping:



Let's define that the characters 0x02 (STX - frame start) and 0x03 (ETX - frame end) need to be unique within the transmitted data stream. This way the start and the end of a message can be safely detected.



If one of these characters should be send within the message frame, it is replaced by prefixing an escape character (ESC = 0x1b) and adding 0x20 to the original character.



Original character replaced by



0x02 -> 0x1b 0x22  
0x03 -> 0x1b 0x23
0x1b -> 0x1b 0x3b


The receiver reverses this process: Anytime he receives an escape character, this character is dropped and the next character is subtracted by 0x20.



This only adds some processing overhead but is 100% reliable (assuming no transmission errors occur, which you could/should verify by additionally implementing a checksum mechanism).






share|improve this answer









$endgroup$









  • 1




    $begingroup$
    Nice answer. The common escape character used for ASCII protocols was 'x10' DLE (Data Link Escape). Some of the Wikipedia pages suggest that DLE was often used in the opposite way: to say that the next byte was a control character rather than a data byte. In my experience, that's generally the opposite meaning for an escape.
    $endgroup$
    – Adrian McCarthy
    Apr 18 at 21:23






  • 2




    $begingroup$
    One thing to watch our for here is that your worst case buffer size doubles. If memory is really tight that might not be the best solution.
    $endgroup$
    – TechnoSam
    Apr 18 at 21:23






  • 1




    $begingroup$
    @Rev What's the rationale for adding 0x20 to the original character? Wouldn't the escaping scheme work without that just as well?
    $endgroup$
    – Nick Alexeev
    Apr 19 at 21:02












  • $begingroup$
    @NickAlexeev: It is easier/faster to identify the actual frame boundaries if you remove any other occurrence of the reserved chars from the stream. That way, you can seperate frame reception and frame parsing (including the un-escaping). This may be especially relevant, if you have a very slow controller without FIFO and/or high data rates. So you can just copy the incoming bytes (between STX/ETX) into the frame buffer as they arrive, mark the frame as complete and do the processing with lower priority.
    $endgroup$
    – Rev1.0
    Apr 21 at 18:08










  • $begingroup$
    @TechnoSam: Good point.
    $endgroup$
    – Rev1.0
    Apr 21 at 18:08



















5












$begingroup$

You know, ASCII already has bytes for these functions.




  • 0x01 : start of heading -- start byte

  • 0x02 : start of text -- end headers, begin payload

  • 0x03 : end of text -- end payload

  • 0x04 : end of transmission -- stop byte

  • 0x17 : end of transmission block -- message continues in next block


It also has codes for various uses inside the payload.




  • 0x1b : escape (escape the next character -- use in payload to indicate next character is not one of the structure describing codes used in your protocol)

  • 0x1c, 0x1d, 0x1e, 0x1f : file, group, record, and unit separator, respectively -- used as simultaneous stop and start byte for parts of hierarchical data


Your protocol should specify the finest granularity of ACK (0x06) and NAK (0x15), so that negative acknowledged data can be retransmitted. Down to this finest granularity, it is wise to have a length field immediately after any (unescaped) start indicator and (as explained in other answer(s)) it is wise to follow any (unescaped) stop indicator with a CRC.






share|improve this answer









$endgroup$













  • $begingroup$
    I will be sending arbitrary data, I guess it might have been confusing to use "nr" in my question when I'm not sending ASCII data. Even though, I like this answer, it's very informative on sending ASCII over UART
    $endgroup$
    – Marius Gulbrandsen
    Apr 19 at 21:50










  • $begingroup$
    @MariusGulbrandsen : As long as your protocol establishes where payload is and which codes must be escaped in each payload section, you can send anything, not just text-ish data.
    $endgroup$
    – Eric Towers
    Apr 19 at 22:57



















4












$begingroup$

UART is not fail-safe by its very nature - we are talking about 1960s technology here.



The root of the problem being that UART only syncs once per 10 bits, allowing a lot of gibberish to pass between those sync periods. Unlike for example CAN which samples every individual bit multiple times.



Any double bit error occurring inside the data will corrupt an UART frame and pass undetected. Bit errors in start/stop bits may or may not get detected in the form of overrun errors.



Therefore, no matter if you use raw data or packets, there is always a probability that bit flips caused by EMI result in unexpected data.



There exist numerous ways of "traditional UART quackery" to improve the situation ever so slightly. You can add sync bytes, sync bits, parity, double stop bits. You could add checksums that count the sum of all bytes (and then invert it - because why not) or you could count the number of binary ones as a checksum. All of this is widely used, wildly unscientific and with a high probability of missing errors. But this was what people did from 1960s to 1990s and lots of weird things like these lives on today.



The most professional way to deal with safe transmission over UART is to have a 16 bit CRC checksum at the end of the packet. Everything else isn't very safe and has a high probability of missing errors.



Then on the hardware level you can use differential RS-422/RS-485 to drastically improve ruggedness of the transmission. This is a must for safe transmission over longer distances. TTL level UART should only be used for on-board communication. RS-232 should not be used for any other purpose but backwards compatibility with old stuff.



Overall, the closer to the hardware your error detection mechanism is, the more effective it is. In terms of effectiveness, differential signals add the most, followed by checking for framing/overrun etc errors. CRC16 adds some, and then "traditional UART quackery" adds a little bit.






share|improve this answer











$endgroup$









  • 7




    $begingroup$
    This advice is fairly tangential - you haven't actually addressed the question asked. In particular, your proposed solutions may solve other problems, but they do not solve the basic problem of the question on this page, which is confusion between framing byes and payload byes. At most, your proposal would reject valid data embedding a framing byte due to CRC or similar failure, with no way to communicate such.
    $endgroup$
    – Chris Stratton
    Apr 18 at 14:28








  • 3




    $begingroup$
    In fact, this answer makes it worse. The original had just data bytes and stop bytes. This adds a third category, CRC bytes. And as presented here, those can take on any value, including {10,13}.
    $endgroup$
    – MSalters
    Apr 18 at 15:53






  • 1




    $begingroup$
    @MSalters: The CRC can be ASCII encoded hex to prevent this issue. Another trick that I've seen on RS485 is to set bit 7 on the start / address byte.
    $endgroup$
    – Transistor
    Apr 18 at 16:03










  • $begingroup$
    Re "CAN which samples every individual bit multiple times.": The actual sampling of the bit value is only once per bit. What are you referring to here? Some kind of error checking, like by the sender? Clock synchronisation?
    $endgroup$
    – Peter Mortensen
    Apr 19 at 12:33












  • $begingroup$
    The inverting of the checksum was done so that summing the entire block of data would result in a zero, which is a bit easier to code and a bit faster to execute. Also, CRC is much better than you make it out to be, look it up in the Wikipedia.
    $endgroup$
    – toolforger
    Apr 19 at 22:04



















0












$begingroup$


... I can imagine, though low probability, that my message might contain the values "10 and 13" after each other when they are not the stop bytes.




A situation when a portion of data is equal to terminating sequence should be considered when designing the format of a serial data packet. Another thing to consider is that any character can get corrupted or lost during transmission. A start character, a stop character, a data payload byte, a checksum or CRC byte, a forward error correction byte aren't immune to corruption. The framing mechanism has to be able to detect when a packet has corrupt data.



There a several ways to approach all this.



I'm making the working assumption that packets are framed only with the serial bytes. Handshake lines aren't used for framing. Time delays aren't used for framing.



Send packet length



Send the length of the packet in the beginning, instead of [or in addition to] the terminating character at the end.



pros: Payload is sent in a efficient binary format.



cons: Need to know the packet length at the start of the transmission.



Escape the special characters



Escape the special characters when sending the payload data. This is already explained in a an earlier answer.



pros: Sender doesn't need to know the length of the packet at the beginning of the transmission.



cons: Slightly less efficient, depending on how many payload bytes need to be escaped.



Payload data encoded such that it can't contain start and stop characters



The payload of the packet is encoded such that it can't contain the start or stop characters. Usually, this is done by sending numbers as their ASCII or Hex-ASCII representation.



pros: Human-readable with common terminal programs. No need for code to handle escaping. No need to know the length of the packet at the start of the transmission



cons: Lower efficiency. For one byte of payload data, several bytes are sent.






share|improve this answer











$endgroup$














    Your Answer






    StackExchange.ifUsing("editor", function () {
    return StackExchange.using("schematics", function () {
    StackExchange.schematics.init();
    });
    }, "cicuitlab");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "135"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f433202%2fhow-fail-safe-is-n-r-as-stop-bytes%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    5 Answers
    5






    active

    oldest

    votes








    5 Answers
    5






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    14












    $begingroup$

    There are different ways to prevent this:




    • Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes). E.g. to send 20 21 22 23 24 25:



    20 21 22 23 24 25 10 13





    • Escape 10 and 13 (or all non ASCII characters with an escape character e.g. . So to send 20 21 10 13 25 26 send: (see comment of/credits for: DanW)



    20 21 1b 10 1b 13 25 26





    • Define a packet when sending messages. E.g. if you want to send message 20 21 22 23 24 25 than instead add the number of bytes to sent, so the package is:



    < nr_of_data_bytes > < data >




    If your messages are max 256 bytes send:




    06 20 21 22 23 24 25




    So you know after receiving 6 data bytes that is the end; you don't have to send a 10 13 afterwards. And you can send 10 13 inside a message. If your messages can be longer, you can use 2 bytes for the data size.



    Update 1: Another way of defining packets



    Another alternative is to send commands which have a specific length and can have many variances, e.g.




    10 20 30 (Command 10 which always has 2 data bytes)



    11 30 40 50 (Command 11 which always has 3 data bytes)



    12 06 10 11 12 13 14 15 (Command 12 + 1 byte for the number of data bytes that follow)



    13 01 02 01 02 03 ... (Command 13 + 2 bytes (01 02 for 256 + 2 = 258 data bytes that follow)



    14 80 90 10 13 (Command 14 that is followed by an ASCII string ending with 10 13)




    Update 2: Bad connection/byte losses



    All of the above only work when the UART line is sending bytes correctly. If you want to use more reliable ways of sending, there are also many possibilities. Below are a few:




    1. Sending a checksum within the package (check google for CRC: Cyclic Redundancy Check). If the CRC is ok, the receiver knows the message has been sent ok (with high probability).

    2. If you need a message to be resent, than an acknowledgement (ACK/reply) mechanism needs to be used (e.g. sender sends something, receiver receives corrupt data, sends a NACK (not acknowledged), sender can than send again.

    3. Timeout: In case the receiver does not get an ACK or NACK in time, a message needs to be resend.


    Note that all above mechanism can be simple or as complicated as you want (or need) to be. In case of resending message, also a mechanism for identifying messages is needed (e.g. adding a sequence number into the package).






    share|improve this answer











    $endgroup$









    • 1




      $begingroup$
      "Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes)." – you've not said how to send data which does include a 10/13 combination – you need to escape it. So "20 10 13 23 10 13" might be sent as "20 1b 10 1b 13 23" with 1b as your escape character.
      $endgroup$
      – Dan W
      Apr 18 at 18:33








    • 1




      $begingroup$
      Note that using a length field as proposed, you’ll get in trouble when your serial link is bad and loses a single byte. Everything will go out of sync.
      $endgroup$
      – Jonas Schäfer
      Apr 18 at 19:55










    • $begingroup$
      @DanW If you use the first one or 2 bytes as the number of data bytes, it does not matter if 10 or 13 are part of those data... So 20 10 13 23 10 13 can be send as 06 20 10 13 23 10 13 where 06 is the number of data bytes that follow.
      $endgroup$
      – Michel Keijzers
      Apr 18 at 22:08










    • $begingroup$
      @MichelKeijzers - yes, but that’s the second solution you mention. Your first solution is missing an explanation of escape sequences to prevent the stop bytes being transmitted.
      $endgroup$
      – Dan W
      Apr 18 at 22:25










    • $begingroup$
      Both approaches work, and are commonly used, but they have different advantages and disadvantages, which you could add if wanted, though it’s beyond what the OP asked for.
      $endgroup$
      – Dan W
      Apr 18 at 22:27
















    14












    $begingroup$

    There are different ways to prevent this:




    • Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes). E.g. to send 20 21 22 23 24 25:



    20 21 22 23 24 25 10 13





    • Escape 10 and 13 (or all non ASCII characters with an escape character e.g. . So to send 20 21 10 13 25 26 send: (see comment of/credits for: DanW)



    20 21 1b 10 1b 13 25 26





    • Define a packet when sending messages. E.g. if you want to send message 20 21 22 23 24 25 than instead add the number of bytes to sent, so the package is:



    < nr_of_data_bytes > < data >




    If your messages are max 256 bytes send:




    06 20 21 22 23 24 25




    So you know after receiving 6 data bytes that is the end; you don't have to send a 10 13 afterwards. And you can send 10 13 inside a message. If your messages can be longer, you can use 2 bytes for the data size.



    Update 1: Another way of defining packets



    Another alternative is to send commands which have a specific length and can have many variances, e.g.




    10 20 30 (Command 10 which always has 2 data bytes)



    11 30 40 50 (Command 11 which always has 3 data bytes)



    12 06 10 11 12 13 14 15 (Command 12 + 1 byte for the number of data bytes that follow)



    13 01 02 01 02 03 ... (Command 13 + 2 bytes (01 02 for 256 + 2 = 258 data bytes that follow)



    14 80 90 10 13 (Command 14 that is followed by an ASCII string ending with 10 13)




    Update 2: Bad connection/byte losses



    All of the above only work when the UART line is sending bytes correctly. If you want to use more reliable ways of sending, there are also many possibilities. Below are a few:




    1. Sending a checksum within the package (check google for CRC: Cyclic Redundancy Check). If the CRC is ok, the receiver knows the message has been sent ok (with high probability).

    2. If you need a message to be resent, than an acknowledgement (ACK/reply) mechanism needs to be used (e.g. sender sends something, receiver receives corrupt data, sends a NACK (not acknowledged), sender can than send again.

    3. Timeout: In case the receiver does not get an ACK or NACK in time, a message needs to be resend.


    Note that all above mechanism can be simple or as complicated as you want (or need) to be. In case of resending message, also a mechanism for identifying messages is needed (e.g. adding a sequence number into the package).






    share|improve this answer











    $endgroup$









    • 1




      $begingroup$
      "Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes)." – you've not said how to send data which does include a 10/13 combination – you need to escape it. So "20 10 13 23 10 13" might be sent as "20 1b 10 1b 13 23" with 1b as your escape character.
      $endgroup$
      – Dan W
      Apr 18 at 18:33








    • 1




      $begingroup$
      Note that using a length field as proposed, you’ll get in trouble when your serial link is bad and loses a single byte. Everything will go out of sync.
      $endgroup$
      – Jonas Schäfer
      Apr 18 at 19:55










    • $begingroup$
      @DanW If you use the first one or 2 bytes as the number of data bytes, it does not matter if 10 or 13 are part of those data... So 20 10 13 23 10 13 can be send as 06 20 10 13 23 10 13 where 06 is the number of data bytes that follow.
      $endgroup$
      – Michel Keijzers
      Apr 18 at 22:08










    • $begingroup$
      @MichelKeijzers - yes, but that’s the second solution you mention. Your first solution is missing an explanation of escape sequences to prevent the stop bytes being transmitted.
      $endgroup$
      – Dan W
      Apr 18 at 22:25










    • $begingroup$
      Both approaches work, and are commonly used, but they have different advantages and disadvantages, which you could add if wanted, though it’s beyond what the OP asked for.
      $endgroup$
      – Dan W
      Apr 18 at 22:27














    14












    14








    14





    $begingroup$

    There are different ways to prevent this:




    • Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes). E.g. to send 20 21 22 23 24 25:



    20 21 22 23 24 25 10 13





    • Escape 10 and 13 (or all non ASCII characters with an escape character e.g. . So to send 20 21 10 13 25 26 send: (see comment of/credits for: DanW)



    20 21 1b 10 1b 13 25 26





    • Define a packet when sending messages. E.g. if you want to send message 20 21 22 23 24 25 than instead add the number of bytes to sent, so the package is:



    < nr_of_data_bytes > < data >




    If your messages are max 256 bytes send:




    06 20 21 22 23 24 25




    So you know after receiving 6 data bytes that is the end; you don't have to send a 10 13 afterwards. And you can send 10 13 inside a message. If your messages can be longer, you can use 2 bytes for the data size.



    Update 1: Another way of defining packets



    Another alternative is to send commands which have a specific length and can have many variances, e.g.




    10 20 30 (Command 10 which always has 2 data bytes)



    11 30 40 50 (Command 11 which always has 3 data bytes)



    12 06 10 11 12 13 14 15 (Command 12 + 1 byte for the number of data bytes that follow)



    13 01 02 01 02 03 ... (Command 13 + 2 bytes (01 02 for 256 + 2 = 258 data bytes that follow)



    14 80 90 10 13 (Command 14 that is followed by an ASCII string ending with 10 13)




    Update 2: Bad connection/byte losses



    All of the above only work when the UART line is sending bytes correctly. If you want to use more reliable ways of sending, there are also many possibilities. Below are a few:




    1. Sending a checksum within the package (check google for CRC: Cyclic Redundancy Check). If the CRC is ok, the receiver knows the message has been sent ok (with high probability).

    2. If you need a message to be resent, than an acknowledgement (ACK/reply) mechanism needs to be used (e.g. sender sends something, receiver receives corrupt data, sends a NACK (not acknowledged), sender can than send again.

    3. Timeout: In case the receiver does not get an ACK or NACK in time, a message needs to be resend.


    Note that all above mechanism can be simple or as complicated as you want (or need) to be. In case of resending message, also a mechanism for identifying messages is needed (e.g. adding a sequence number into the package).






    share|improve this answer











    $endgroup$



    There are different ways to prevent this:




    • Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes). E.g. to send 20 21 22 23 24 25:



    20 21 22 23 24 25 10 13





    • Escape 10 and 13 (or all non ASCII characters with an escape character e.g. . So to send 20 21 10 13 25 26 send: (see comment of/credits for: DanW)



    20 21 1b 10 1b 13 25 26





    • Define a packet when sending messages. E.g. if you want to send message 20 21 22 23 24 25 than instead add the number of bytes to sent, so the package is:



    < nr_of_data_bytes > < data >




    If your messages are max 256 bytes send:




    06 20 21 22 23 24 25




    So you know after receiving 6 data bytes that is the end; you don't have to send a 10 13 afterwards. And you can send 10 13 inside a message. If your messages can be longer, you can use 2 bytes for the data size.



    Update 1: Another way of defining packets



    Another alternative is to send commands which have a specific length and can have many variances, e.g.




    10 20 30 (Command 10 which always has 2 data bytes)



    11 30 40 50 (Command 11 which always has 3 data bytes)



    12 06 10 11 12 13 14 15 (Command 12 + 1 byte for the number of data bytes that follow)



    13 01 02 01 02 03 ... (Command 13 + 2 bytes (01 02 for 256 + 2 = 258 data bytes that follow)



    14 80 90 10 13 (Command 14 that is followed by an ASCII string ending with 10 13)




    Update 2: Bad connection/byte losses



    All of the above only work when the UART line is sending bytes correctly. If you want to use more reliable ways of sending, there are also many possibilities. Below are a few:




    1. Sending a checksum within the package (check google for CRC: Cyclic Redundancy Check). If the CRC is ok, the receiver knows the message has been sent ok (with high probability).

    2. If you need a message to be resent, than an acknowledgement (ACK/reply) mechanism needs to be used (e.g. sender sends something, receiver receives corrupt data, sends a NACK (not acknowledged), sender can than send again.

    3. Timeout: In case the receiver does not get an ACK or NACK in time, a message needs to be resend.


    Note that all above mechanism can be simple or as complicated as you want (or need) to be. In case of resending message, also a mechanism for identifying messages is needed (e.g. adding a sequence number into the package).







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 18 at 22:42

























    answered Apr 18 at 10:59









    Michel KeijzersMichel Keijzers

    7,20293173




    7,20293173








    • 1




      $begingroup$
      "Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes)." – you've not said how to send data which does include a 10/13 combination – you need to escape it. So "20 10 13 23 10 13" might be sent as "20 1b 10 1b 13 23" with 1b as your escape character.
      $endgroup$
      – Dan W
      Apr 18 at 18:33








    • 1




      $begingroup$
      Note that using a length field as proposed, you’ll get in trouble when your serial link is bad and loses a single byte. Everything will go out of sync.
      $endgroup$
      – Jonas Schäfer
      Apr 18 at 19:55










    • $begingroup$
      @DanW If you use the first one or 2 bytes as the number of data bytes, it does not matter if 10 or 13 are part of those data... So 20 10 13 23 10 13 can be send as 06 20 10 13 23 10 13 where 06 is the number of data bytes that follow.
      $endgroup$
      – Michel Keijzers
      Apr 18 at 22:08










    • $begingroup$
      @MichelKeijzers - yes, but that’s the second solution you mention. Your first solution is missing an explanation of escape sequences to prevent the stop bytes being transmitted.
      $endgroup$
      – Dan W
      Apr 18 at 22:25










    • $begingroup$
      Both approaches work, and are commonly used, but they have different advantages and disadvantages, which you could add if wanted, though it’s beyond what the OP asked for.
      $endgroup$
      – Dan W
      Apr 18 at 22:27














    • 1




      $begingroup$
      "Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes)." – you've not said how to send data which does include a 10/13 combination – you need to escape it. So "20 10 13 23 10 13" might be sent as "20 1b 10 1b 13 23" with 1b as your escape character.
      $endgroup$
      – Dan W
      Apr 18 at 18:33








    • 1




      $begingroup$
      Note that using a length field as proposed, you’ll get in trouble when your serial link is bad and loses a single byte. Everything will go out of sync.
      $endgroup$
      – Jonas Schäfer
      Apr 18 at 19:55










    • $begingroup$
      @DanW If you use the first one or 2 bytes as the number of data bytes, it does not matter if 10 or 13 are part of those data... So 20 10 13 23 10 13 can be send as 06 20 10 13 23 10 13 where 06 is the number of data bytes that follow.
      $endgroup$
      – Michel Keijzers
      Apr 18 at 22:08










    • $begingroup$
      @MichelKeijzers - yes, but that’s the second solution you mention. Your first solution is missing an explanation of escape sequences to prevent the stop bytes being transmitted.
      $endgroup$
      – Dan W
      Apr 18 at 22:25










    • $begingroup$
      Both approaches work, and are commonly used, but they have different advantages and disadvantages, which you could add if wanted, though it’s beyond what the OP asked for.
      $endgroup$
      – Dan W
      Apr 18 at 22:27








    1




    1




    $begingroup$
    "Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes)." – you've not said how to send data which does include a 10/13 combination – you need to escape it. So "20 10 13 23 10 13" might be sent as "20 1b 10 1b 13 23" with 1b as your escape character.
    $endgroup$
    – Dan W
    Apr 18 at 18:33






    $begingroup$
    "Make sure you never send a 10/13 combination in your regular messages (so only as stop bytes)." – you've not said how to send data which does include a 10/13 combination – you need to escape it. So "20 10 13 23 10 13" might be sent as "20 1b 10 1b 13 23" with 1b as your escape character.
    $endgroup$
    – Dan W
    Apr 18 at 18:33






    1




    1




    $begingroup$
    Note that using a length field as proposed, you’ll get in trouble when your serial link is bad and loses a single byte. Everything will go out of sync.
    $endgroup$
    – Jonas Schäfer
    Apr 18 at 19:55




    $begingroup$
    Note that using a length field as proposed, you’ll get in trouble when your serial link is bad and loses a single byte. Everything will go out of sync.
    $endgroup$
    – Jonas Schäfer
    Apr 18 at 19:55












    $begingroup$
    @DanW If you use the first one or 2 bytes as the number of data bytes, it does not matter if 10 or 13 are part of those data... So 20 10 13 23 10 13 can be send as 06 20 10 13 23 10 13 where 06 is the number of data bytes that follow.
    $endgroup$
    – Michel Keijzers
    Apr 18 at 22:08




    $begingroup$
    @DanW If you use the first one or 2 bytes as the number of data bytes, it does not matter if 10 or 13 are part of those data... So 20 10 13 23 10 13 can be send as 06 20 10 13 23 10 13 where 06 is the number of data bytes that follow.
    $endgroup$
    – Michel Keijzers
    Apr 18 at 22:08












    $begingroup$
    @MichelKeijzers - yes, but that’s the second solution you mention. Your first solution is missing an explanation of escape sequences to prevent the stop bytes being transmitted.
    $endgroup$
    – Dan W
    Apr 18 at 22:25




    $begingroup$
    @MichelKeijzers - yes, but that’s the second solution you mention. Your first solution is missing an explanation of escape sequences to prevent the stop bytes being transmitted.
    $endgroup$
    – Dan W
    Apr 18 at 22:25












    $begingroup$
    Both approaches work, and are commonly used, but they have different advantages and disadvantages, which you could add if wanted, though it’s beyond what the OP asked for.
    $endgroup$
    – Dan W
    Apr 18 at 22:27




    $begingroup$
    Both approaches work, and are commonly used, but they have different advantages and disadvantages, which you could add if wanted, though it’s beyond what the OP asked for.
    $endgroup$
    – Dan W
    Apr 18 at 22:27













    13












    $begingroup$


    How fail-safe is nr as stop bytes?




    If you send send arbitrary data -> probably not fail-safe enough.



    A common solution is to use escaping:



    Let's define that the characters 0x02 (STX - frame start) and 0x03 (ETX - frame end) need to be unique within the transmitted data stream. This way the start and the end of a message can be safely detected.



    If one of these characters should be send within the message frame, it is replaced by prefixing an escape character (ESC = 0x1b) and adding 0x20 to the original character.



    Original character replaced by



    0x02 -> 0x1b 0x22  
    0x03 -> 0x1b 0x23
    0x1b -> 0x1b 0x3b


    The receiver reverses this process: Anytime he receives an escape character, this character is dropped and the next character is subtracted by 0x20.



    This only adds some processing overhead but is 100% reliable (assuming no transmission errors occur, which you could/should verify by additionally implementing a checksum mechanism).






    share|improve this answer









    $endgroup$









    • 1




      $begingroup$
      Nice answer. The common escape character used for ASCII protocols was 'x10' DLE (Data Link Escape). Some of the Wikipedia pages suggest that DLE was often used in the opposite way: to say that the next byte was a control character rather than a data byte. In my experience, that's generally the opposite meaning for an escape.
      $endgroup$
      – Adrian McCarthy
      Apr 18 at 21:23






    • 2




      $begingroup$
      One thing to watch our for here is that your worst case buffer size doubles. If memory is really tight that might not be the best solution.
      $endgroup$
      – TechnoSam
      Apr 18 at 21:23






    • 1




      $begingroup$
      @Rev What's the rationale for adding 0x20 to the original character? Wouldn't the escaping scheme work without that just as well?
      $endgroup$
      – Nick Alexeev
      Apr 19 at 21:02












    • $begingroup$
      @NickAlexeev: It is easier/faster to identify the actual frame boundaries if you remove any other occurrence of the reserved chars from the stream. That way, you can seperate frame reception and frame parsing (including the un-escaping). This may be especially relevant, if you have a very slow controller without FIFO and/or high data rates. So you can just copy the incoming bytes (between STX/ETX) into the frame buffer as they arrive, mark the frame as complete and do the processing with lower priority.
      $endgroup$
      – Rev1.0
      Apr 21 at 18:08










    • $begingroup$
      @TechnoSam: Good point.
      $endgroup$
      – Rev1.0
      Apr 21 at 18:08
















    13












    $begingroup$


    How fail-safe is nr as stop bytes?




    If you send send arbitrary data -> probably not fail-safe enough.



    A common solution is to use escaping:



    Let's define that the characters 0x02 (STX - frame start) and 0x03 (ETX - frame end) need to be unique within the transmitted data stream. This way the start and the end of a message can be safely detected.



    If one of these characters should be send within the message frame, it is replaced by prefixing an escape character (ESC = 0x1b) and adding 0x20 to the original character.



    Original character replaced by



    0x02 -> 0x1b 0x22  
    0x03 -> 0x1b 0x23
    0x1b -> 0x1b 0x3b


    The receiver reverses this process: Anytime he receives an escape character, this character is dropped and the next character is subtracted by 0x20.



    This only adds some processing overhead but is 100% reliable (assuming no transmission errors occur, which you could/should verify by additionally implementing a checksum mechanism).






    share|improve this answer









    $endgroup$









    • 1




      $begingroup$
      Nice answer. The common escape character used for ASCII protocols was 'x10' DLE (Data Link Escape). Some of the Wikipedia pages suggest that DLE was often used in the opposite way: to say that the next byte was a control character rather than a data byte. In my experience, that's generally the opposite meaning for an escape.
      $endgroup$
      – Adrian McCarthy
      Apr 18 at 21:23






    • 2




      $begingroup$
      One thing to watch our for here is that your worst case buffer size doubles. If memory is really tight that might not be the best solution.
      $endgroup$
      – TechnoSam
      Apr 18 at 21:23






    • 1




      $begingroup$
      @Rev What's the rationale for adding 0x20 to the original character? Wouldn't the escaping scheme work without that just as well?
      $endgroup$
      – Nick Alexeev
      Apr 19 at 21:02












    • $begingroup$
      @NickAlexeev: It is easier/faster to identify the actual frame boundaries if you remove any other occurrence of the reserved chars from the stream. That way, you can seperate frame reception and frame parsing (including the un-escaping). This may be especially relevant, if you have a very slow controller without FIFO and/or high data rates. So you can just copy the incoming bytes (between STX/ETX) into the frame buffer as they arrive, mark the frame as complete and do the processing with lower priority.
      $endgroup$
      – Rev1.0
      Apr 21 at 18:08










    • $begingroup$
      @TechnoSam: Good point.
      $endgroup$
      – Rev1.0
      Apr 21 at 18:08














    13












    13








    13





    $begingroup$


    How fail-safe is nr as stop bytes?




    If you send send arbitrary data -> probably not fail-safe enough.



    A common solution is to use escaping:



    Let's define that the characters 0x02 (STX - frame start) and 0x03 (ETX - frame end) need to be unique within the transmitted data stream. This way the start and the end of a message can be safely detected.



    If one of these characters should be send within the message frame, it is replaced by prefixing an escape character (ESC = 0x1b) and adding 0x20 to the original character.



    Original character replaced by



    0x02 -> 0x1b 0x22  
    0x03 -> 0x1b 0x23
    0x1b -> 0x1b 0x3b


    The receiver reverses this process: Anytime he receives an escape character, this character is dropped and the next character is subtracted by 0x20.



    This only adds some processing overhead but is 100% reliable (assuming no transmission errors occur, which you could/should verify by additionally implementing a checksum mechanism).






    share|improve this answer









    $endgroup$




    How fail-safe is nr as stop bytes?




    If you send send arbitrary data -> probably not fail-safe enough.



    A common solution is to use escaping:



    Let's define that the characters 0x02 (STX - frame start) and 0x03 (ETX - frame end) need to be unique within the transmitted data stream. This way the start and the end of a message can be safely detected.



    If one of these characters should be send within the message frame, it is replaced by prefixing an escape character (ESC = 0x1b) and adding 0x20 to the original character.



    Original character replaced by



    0x02 -> 0x1b 0x22  
    0x03 -> 0x1b 0x23
    0x1b -> 0x1b 0x3b


    The receiver reverses this process: Anytime he receives an escape character, this character is dropped and the next character is subtracted by 0x20.



    This only adds some processing overhead but is 100% reliable (assuming no transmission errors occur, which you could/should verify by additionally implementing a checksum mechanism).







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Apr 18 at 11:05









    Rev1.0Rev1.0

    7,72043369




    7,72043369








    • 1




      $begingroup$
      Nice answer. The common escape character used for ASCII protocols was 'x10' DLE (Data Link Escape). Some of the Wikipedia pages suggest that DLE was often used in the opposite way: to say that the next byte was a control character rather than a data byte. In my experience, that's generally the opposite meaning for an escape.
      $endgroup$
      – Adrian McCarthy
      Apr 18 at 21:23






    • 2




      $begingroup$
      One thing to watch our for here is that your worst case buffer size doubles. If memory is really tight that might not be the best solution.
      $endgroup$
      – TechnoSam
      Apr 18 at 21:23






    • 1




      $begingroup$
      @Rev What's the rationale for adding 0x20 to the original character? Wouldn't the escaping scheme work without that just as well?
      $endgroup$
      – Nick Alexeev
      Apr 19 at 21:02












    • $begingroup$
      @NickAlexeev: It is easier/faster to identify the actual frame boundaries if you remove any other occurrence of the reserved chars from the stream. That way, you can seperate frame reception and frame parsing (including the un-escaping). This may be especially relevant, if you have a very slow controller without FIFO and/or high data rates. So you can just copy the incoming bytes (between STX/ETX) into the frame buffer as they arrive, mark the frame as complete and do the processing with lower priority.
      $endgroup$
      – Rev1.0
      Apr 21 at 18:08










    • $begingroup$
      @TechnoSam: Good point.
      $endgroup$
      – Rev1.0
      Apr 21 at 18:08














    • 1




      $begingroup$
      Nice answer. The common escape character used for ASCII protocols was 'x10' DLE (Data Link Escape). Some of the Wikipedia pages suggest that DLE was often used in the opposite way: to say that the next byte was a control character rather than a data byte. In my experience, that's generally the opposite meaning for an escape.
      $endgroup$
      – Adrian McCarthy
      Apr 18 at 21:23






    • 2




      $begingroup$
      One thing to watch our for here is that your worst case buffer size doubles. If memory is really tight that might not be the best solution.
      $endgroup$
      – TechnoSam
      Apr 18 at 21:23






    • 1




      $begingroup$
      @Rev What's the rationale for adding 0x20 to the original character? Wouldn't the escaping scheme work without that just as well?
      $endgroup$
      – Nick Alexeev
      Apr 19 at 21:02












    • $begingroup$
      @NickAlexeev: It is easier/faster to identify the actual frame boundaries if you remove any other occurrence of the reserved chars from the stream. That way, you can seperate frame reception and frame parsing (including the un-escaping). This may be especially relevant, if you have a very slow controller without FIFO and/or high data rates. So you can just copy the incoming bytes (between STX/ETX) into the frame buffer as they arrive, mark the frame as complete and do the processing with lower priority.
      $endgroup$
      – Rev1.0
      Apr 21 at 18:08










    • $begingroup$
      @TechnoSam: Good point.
      $endgroup$
      – Rev1.0
      Apr 21 at 18:08








    1




    1




    $begingroup$
    Nice answer. The common escape character used for ASCII protocols was 'x10' DLE (Data Link Escape). Some of the Wikipedia pages suggest that DLE was often used in the opposite way: to say that the next byte was a control character rather than a data byte. In my experience, that's generally the opposite meaning for an escape.
    $endgroup$
    – Adrian McCarthy
    Apr 18 at 21:23




    $begingroup$
    Nice answer. The common escape character used for ASCII protocols was 'x10' DLE (Data Link Escape). Some of the Wikipedia pages suggest that DLE was often used in the opposite way: to say that the next byte was a control character rather than a data byte. In my experience, that's generally the opposite meaning for an escape.
    $endgroup$
    – Adrian McCarthy
    Apr 18 at 21:23




    2




    2




    $begingroup$
    One thing to watch our for here is that your worst case buffer size doubles. If memory is really tight that might not be the best solution.
    $endgroup$
    – TechnoSam
    Apr 18 at 21:23




    $begingroup$
    One thing to watch our for here is that your worst case buffer size doubles. If memory is really tight that might not be the best solution.
    $endgroup$
    – TechnoSam
    Apr 18 at 21:23




    1




    1




    $begingroup$
    @Rev What's the rationale for adding 0x20 to the original character? Wouldn't the escaping scheme work without that just as well?
    $endgroup$
    – Nick Alexeev
    Apr 19 at 21:02






    $begingroup$
    @Rev What's the rationale for adding 0x20 to the original character? Wouldn't the escaping scheme work without that just as well?
    $endgroup$
    – Nick Alexeev
    Apr 19 at 21:02














    $begingroup$
    @NickAlexeev: It is easier/faster to identify the actual frame boundaries if you remove any other occurrence of the reserved chars from the stream. That way, you can seperate frame reception and frame parsing (including the un-escaping). This may be especially relevant, if you have a very slow controller without FIFO and/or high data rates. So you can just copy the incoming bytes (between STX/ETX) into the frame buffer as they arrive, mark the frame as complete and do the processing with lower priority.
    $endgroup$
    – Rev1.0
    Apr 21 at 18:08




    $begingroup$
    @NickAlexeev: It is easier/faster to identify the actual frame boundaries if you remove any other occurrence of the reserved chars from the stream. That way, you can seperate frame reception and frame parsing (including the un-escaping). This may be especially relevant, if you have a very slow controller without FIFO and/or high data rates. So you can just copy the incoming bytes (between STX/ETX) into the frame buffer as they arrive, mark the frame as complete and do the processing with lower priority.
    $endgroup$
    – Rev1.0
    Apr 21 at 18:08












    $begingroup$
    @TechnoSam: Good point.
    $endgroup$
    – Rev1.0
    Apr 21 at 18:08




    $begingroup$
    @TechnoSam: Good point.
    $endgroup$
    – Rev1.0
    Apr 21 at 18:08











    5












    $begingroup$

    You know, ASCII already has bytes for these functions.




    • 0x01 : start of heading -- start byte

    • 0x02 : start of text -- end headers, begin payload

    • 0x03 : end of text -- end payload

    • 0x04 : end of transmission -- stop byte

    • 0x17 : end of transmission block -- message continues in next block


    It also has codes for various uses inside the payload.




    • 0x1b : escape (escape the next character -- use in payload to indicate next character is not one of the structure describing codes used in your protocol)

    • 0x1c, 0x1d, 0x1e, 0x1f : file, group, record, and unit separator, respectively -- used as simultaneous stop and start byte for parts of hierarchical data


    Your protocol should specify the finest granularity of ACK (0x06) and NAK (0x15), so that negative acknowledged data can be retransmitted. Down to this finest granularity, it is wise to have a length field immediately after any (unescaped) start indicator and (as explained in other answer(s)) it is wise to follow any (unescaped) stop indicator with a CRC.






    share|improve this answer









    $endgroup$













    • $begingroup$
      I will be sending arbitrary data, I guess it might have been confusing to use "nr" in my question when I'm not sending ASCII data. Even though, I like this answer, it's very informative on sending ASCII over UART
      $endgroup$
      – Marius Gulbrandsen
      Apr 19 at 21:50










    • $begingroup$
      @MariusGulbrandsen : As long as your protocol establishes where payload is and which codes must be escaped in each payload section, you can send anything, not just text-ish data.
      $endgroup$
      – Eric Towers
      Apr 19 at 22:57
















    5












    $begingroup$

    You know, ASCII already has bytes for these functions.




    • 0x01 : start of heading -- start byte

    • 0x02 : start of text -- end headers, begin payload

    • 0x03 : end of text -- end payload

    • 0x04 : end of transmission -- stop byte

    • 0x17 : end of transmission block -- message continues in next block


    It also has codes for various uses inside the payload.




    • 0x1b : escape (escape the next character -- use in payload to indicate next character is not one of the structure describing codes used in your protocol)

    • 0x1c, 0x1d, 0x1e, 0x1f : file, group, record, and unit separator, respectively -- used as simultaneous stop and start byte for parts of hierarchical data


    Your protocol should specify the finest granularity of ACK (0x06) and NAK (0x15), so that negative acknowledged data can be retransmitted. Down to this finest granularity, it is wise to have a length field immediately after any (unescaped) start indicator and (as explained in other answer(s)) it is wise to follow any (unescaped) stop indicator with a CRC.






    share|improve this answer









    $endgroup$













    • $begingroup$
      I will be sending arbitrary data, I guess it might have been confusing to use "nr" in my question when I'm not sending ASCII data. Even though, I like this answer, it's very informative on sending ASCII over UART
      $endgroup$
      – Marius Gulbrandsen
      Apr 19 at 21:50










    • $begingroup$
      @MariusGulbrandsen : As long as your protocol establishes where payload is and which codes must be escaped in each payload section, you can send anything, not just text-ish data.
      $endgroup$
      – Eric Towers
      Apr 19 at 22:57














    5












    5








    5





    $begingroup$

    You know, ASCII already has bytes for these functions.




    • 0x01 : start of heading -- start byte

    • 0x02 : start of text -- end headers, begin payload

    • 0x03 : end of text -- end payload

    • 0x04 : end of transmission -- stop byte

    • 0x17 : end of transmission block -- message continues in next block


    It also has codes for various uses inside the payload.




    • 0x1b : escape (escape the next character -- use in payload to indicate next character is not one of the structure describing codes used in your protocol)

    • 0x1c, 0x1d, 0x1e, 0x1f : file, group, record, and unit separator, respectively -- used as simultaneous stop and start byte for parts of hierarchical data


    Your protocol should specify the finest granularity of ACK (0x06) and NAK (0x15), so that negative acknowledged data can be retransmitted. Down to this finest granularity, it is wise to have a length field immediately after any (unescaped) start indicator and (as explained in other answer(s)) it is wise to follow any (unescaped) stop indicator with a CRC.






    share|improve this answer









    $endgroup$



    You know, ASCII already has bytes for these functions.




    • 0x01 : start of heading -- start byte

    • 0x02 : start of text -- end headers, begin payload

    • 0x03 : end of text -- end payload

    • 0x04 : end of transmission -- stop byte

    • 0x17 : end of transmission block -- message continues in next block


    It also has codes for various uses inside the payload.




    • 0x1b : escape (escape the next character -- use in payload to indicate next character is not one of the structure describing codes used in your protocol)

    • 0x1c, 0x1d, 0x1e, 0x1f : file, group, record, and unit separator, respectively -- used as simultaneous stop and start byte for parts of hierarchical data


    Your protocol should specify the finest granularity of ACK (0x06) and NAK (0x15), so that negative acknowledged data can be retransmitted. Down to this finest granularity, it is wise to have a length field immediately after any (unescaped) start indicator and (as explained in other answer(s)) it is wise to follow any (unescaped) stop indicator with a CRC.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Apr 18 at 15:55









    Eric TowersEric Towers

    20912




    20912












    • $begingroup$
      I will be sending arbitrary data, I guess it might have been confusing to use "nr" in my question when I'm not sending ASCII data. Even though, I like this answer, it's very informative on sending ASCII over UART
      $endgroup$
      – Marius Gulbrandsen
      Apr 19 at 21:50










    • $begingroup$
      @MariusGulbrandsen : As long as your protocol establishes where payload is and which codes must be escaped in each payload section, you can send anything, not just text-ish data.
      $endgroup$
      – Eric Towers
      Apr 19 at 22:57


















    • $begingroup$
      I will be sending arbitrary data, I guess it might have been confusing to use "nr" in my question when I'm not sending ASCII data. Even though, I like this answer, it's very informative on sending ASCII over UART
      $endgroup$
      – Marius Gulbrandsen
      Apr 19 at 21:50










    • $begingroup$
      @MariusGulbrandsen : As long as your protocol establishes where payload is and which codes must be escaped in each payload section, you can send anything, not just text-ish data.
      $endgroup$
      – Eric Towers
      Apr 19 at 22:57
















    $begingroup$
    I will be sending arbitrary data, I guess it might have been confusing to use "nr" in my question when I'm not sending ASCII data. Even though, I like this answer, it's very informative on sending ASCII over UART
    $endgroup$
    – Marius Gulbrandsen
    Apr 19 at 21:50




    $begingroup$
    I will be sending arbitrary data, I guess it might have been confusing to use "nr" in my question when I'm not sending ASCII data. Even though, I like this answer, it's very informative on sending ASCII over UART
    $endgroup$
    – Marius Gulbrandsen
    Apr 19 at 21:50












    $begingroup$
    @MariusGulbrandsen : As long as your protocol establishes where payload is and which codes must be escaped in each payload section, you can send anything, not just text-ish data.
    $endgroup$
    – Eric Towers
    Apr 19 at 22:57




    $begingroup$
    @MariusGulbrandsen : As long as your protocol establishes where payload is and which codes must be escaped in each payload section, you can send anything, not just text-ish data.
    $endgroup$
    – Eric Towers
    Apr 19 at 22:57











    4












    $begingroup$

    UART is not fail-safe by its very nature - we are talking about 1960s technology here.



    The root of the problem being that UART only syncs once per 10 bits, allowing a lot of gibberish to pass between those sync periods. Unlike for example CAN which samples every individual bit multiple times.



    Any double bit error occurring inside the data will corrupt an UART frame and pass undetected. Bit errors in start/stop bits may or may not get detected in the form of overrun errors.



    Therefore, no matter if you use raw data or packets, there is always a probability that bit flips caused by EMI result in unexpected data.



    There exist numerous ways of "traditional UART quackery" to improve the situation ever so slightly. You can add sync bytes, sync bits, parity, double stop bits. You could add checksums that count the sum of all bytes (and then invert it - because why not) or you could count the number of binary ones as a checksum. All of this is widely used, wildly unscientific and with a high probability of missing errors. But this was what people did from 1960s to 1990s and lots of weird things like these lives on today.



    The most professional way to deal with safe transmission over UART is to have a 16 bit CRC checksum at the end of the packet. Everything else isn't very safe and has a high probability of missing errors.



    Then on the hardware level you can use differential RS-422/RS-485 to drastically improve ruggedness of the transmission. This is a must for safe transmission over longer distances. TTL level UART should only be used for on-board communication. RS-232 should not be used for any other purpose but backwards compatibility with old stuff.



    Overall, the closer to the hardware your error detection mechanism is, the more effective it is. In terms of effectiveness, differential signals add the most, followed by checking for framing/overrun etc errors. CRC16 adds some, and then "traditional UART quackery" adds a little bit.






    share|improve this answer











    $endgroup$









    • 7




      $begingroup$
      This advice is fairly tangential - you haven't actually addressed the question asked. In particular, your proposed solutions may solve other problems, but they do not solve the basic problem of the question on this page, which is confusion between framing byes and payload byes. At most, your proposal would reject valid data embedding a framing byte due to CRC or similar failure, with no way to communicate such.
      $endgroup$
      – Chris Stratton
      Apr 18 at 14:28








    • 3




      $begingroup$
      In fact, this answer makes it worse. The original had just data bytes and stop bytes. This adds a third category, CRC bytes. And as presented here, those can take on any value, including {10,13}.
      $endgroup$
      – MSalters
      Apr 18 at 15:53






    • 1




      $begingroup$
      @MSalters: The CRC can be ASCII encoded hex to prevent this issue. Another trick that I've seen on RS485 is to set bit 7 on the start / address byte.
      $endgroup$
      – Transistor
      Apr 18 at 16:03










    • $begingroup$
      Re "CAN which samples every individual bit multiple times.": The actual sampling of the bit value is only once per bit. What are you referring to here? Some kind of error checking, like by the sender? Clock synchronisation?
      $endgroup$
      – Peter Mortensen
      Apr 19 at 12:33












    • $begingroup$
      The inverting of the checksum was done so that summing the entire block of data would result in a zero, which is a bit easier to code and a bit faster to execute. Also, CRC is much better than you make it out to be, look it up in the Wikipedia.
      $endgroup$
      – toolforger
      Apr 19 at 22:04
















    4












    $begingroup$

    UART is not fail-safe by its very nature - we are talking about 1960s technology here.



    The root of the problem being that UART only syncs once per 10 bits, allowing a lot of gibberish to pass between those sync periods. Unlike for example CAN which samples every individual bit multiple times.



    Any double bit error occurring inside the data will corrupt an UART frame and pass undetected. Bit errors in start/stop bits may or may not get detected in the form of overrun errors.



    Therefore, no matter if you use raw data or packets, there is always a probability that bit flips caused by EMI result in unexpected data.



    There exist numerous ways of "traditional UART quackery" to improve the situation ever so slightly. You can add sync bytes, sync bits, parity, double stop bits. You could add checksums that count the sum of all bytes (and then invert it - because why not) or you could count the number of binary ones as a checksum. All of this is widely used, wildly unscientific and with a high probability of missing errors. But this was what people did from 1960s to 1990s and lots of weird things like these lives on today.



    The most professional way to deal with safe transmission over UART is to have a 16 bit CRC checksum at the end of the packet. Everything else isn't very safe and has a high probability of missing errors.



    Then on the hardware level you can use differential RS-422/RS-485 to drastically improve ruggedness of the transmission. This is a must for safe transmission over longer distances. TTL level UART should only be used for on-board communication. RS-232 should not be used for any other purpose but backwards compatibility with old stuff.



    Overall, the closer to the hardware your error detection mechanism is, the more effective it is. In terms of effectiveness, differential signals add the most, followed by checking for framing/overrun etc errors. CRC16 adds some, and then "traditional UART quackery" adds a little bit.






    share|improve this answer











    $endgroup$









    • 7




      $begingroup$
      This advice is fairly tangential - you haven't actually addressed the question asked. In particular, your proposed solutions may solve other problems, but they do not solve the basic problem of the question on this page, which is confusion between framing byes and payload byes. At most, your proposal would reject valid data embedding a framing byte due to CRC or similar failure, with no way to communicate such.
      $endgroup$
      – Chris Stratton
      Apr 18 at 14:28








    • 3




      $begingroup$
      In fact, this answer makes it worse. The original had just data bytes and stop bytes. This adds a third category, CRC bytes. And as presented here, those can take on any value, including {10,13}.
      $endgroup$
      – MSalters
      Apr 18 at 15:53






    • 1




      $begingroup$
      @MSalters: The CRC can be ASCII encoded hex to prevent this issue. Another trick that I've seen on RS485 is to set bit 7 on the start / address byte.
      $endgroup$
      – Transistor
      Apr 18 at 16:03










    • $begingroup$
      Re "CAN which samples every individual bit multiple times.": The actual sampling of the bit value is only once per bit. What are you referring to here? Some kind of error checking, like by the sender? Clock synchronisation?
      $endgroup$
      – Peter Mortensen
      Apr 19 at 12:33












    • $begingroup$
      The inverting of the checksum was done so that summing the entire block of data would result in a zero, which is a bit easier to code and a bit faster to execute. Also, CRC is much better than you make it out to be, look it up in the Wikipedia.
      $endgroup$
      – toolforger
      Apr 19 at 22:04














    4












    4








    4





    $begingroup$

    UART is not fail-safe by its very nature - we are talking about 1960s technology here.



    The root of the problem being that UART only syncs once per 10 bits, allowing a lot of gibberish to pass between those sync periods. Unlike for example CAN which samples every individual bit multiple times.



    Any double bit error occurring inside the data will corrupt an UART frame and pass undetected. Bit errors in start/stop bits may or may not get detected in the form of overrun errors.



    Therefore, no matter if you use raw data or packets, there is always a probability that bit flips caused by EMI result in unexpected data.



    There exist numerous ways of "traditional UART quackery" to improve the situation ever so slightly. You can add sync bytes, sync bits, parity, double stop bits. You could add checksums that count the sum of all bytes (and then invert it - because why not) or you could count the number of binary ones as a checksum. All of this is widely used, wildly unscientific and with a high probability of missing errors. But this was what people did from 1960s to 1990s and lots of weird things like these lives on today.



    The most professional way to deal with safe transmission over UART is to have a 16 bit CRC checksum at the end of the packet. Everything else isn't very safe and has a high probability of missing errors.



    Then on the hardware level you can use differential RS-422/RS-485 to drastically improve ruggedness of the transmission. This is a must for safe transmission over longer distances. TTL level UART should only be used for on-board communication. RS-232 should not be used for any other purpose but backwards compatibility with old stuff.



    Overall, the closer to the hardware your error detection mechanism is, the more effective it is. In terms of effectiveness, differential signals add the most, followed by checking for framing/overrun etc errors. CRC16 adds some, and then "traditional UART quackery" adds a little bit.






    share|improve this answer











    $endgroup$



    UART is not fail-safe by its very nature - we are talking about 1960s technology here.



    The root of the problem being that UART only syncs once per 10 bits, allowing a lot of gibberish to pass between those sync periods. Unlike for example CAN which samples every individual bit multiple times.



    Any double bit error occurring inside the data will corrupt an UART frame and pass undetected. Bit errors in start/stop bits may or may not get detected in the form of overrun errors.



    Therefore, no matter if you use raw data or packets, there is always a probability that bit flips caused by EMI result in unexpected data.



    There exist numerous ways of "traditional UART quackery" to improve the situation ever so slightly. You can add sync bytes, sync bits, parity, double stop bits. You could add checksums that count the sum of all bytes (and then invert it - because why not) or you could count the number of binary ones as a checksum. All of this is widely used, wildly unscientific and with a high probability of missing errors. But this was what people did from 1960s to 1990s and lots of weird things like these lives on today.



    The most professional way to deal with safe transmission over UART is to have a 16 bit CRC checksum at the end of the packet. Everything else isn't very safe and has a high probability of missing errors.



    Then on the hardware level you can use differential RS-422/RS-485 to drastically improve ruggedness of the transmission. This is a must for safe transmission over longer distances. TTL level UART should only be used for on-board communication. RS-232 should not be used for any other purpose but backwards compatibility with old stuff.



    Overall, the closer to the hardware your error detection mechanism is, the more effective it is. In terms of effectiveness, differential signals add the most, followed by checking for framing/overrun etc errors. CRC16 adds some, and then "traditional UART quackery" adds a little bit.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 18 at 11:38

























    answered Apr 18 at 11:27









    LundinLundin

    4,5291131




    4,5291131








    • 7




      $begingroup$
      This advice is fairly tangential - you haven't actually addressed the question asked. In particular, your proposed solutions may solve other problems, but they do not solve the basic problem of the question on this page, which is confusion between framing byes and payload byes. At most, your proposal would reject valid data embedding a framing byte due to CRC or similar failure, with no way to communicate such.
      $endgroup$
      – Chris Stratton
      Apr 18 at 14:28








    • 3




      $begingroup$
      In fact, this answer makes it worse. The original had just data bytes and stop bytes. This adds a third category, CRC bytes. And as presented here, those can take on any value, including {10,13}.
      $endgroup$
      – MSalters
      Apr 18 at 15:53






    • 1




      $begingroup$
      @MSalters: The CRC can be ASCII encoded hex to prevent this issue. Another trick that I've seen on RS485 is to set bit 7 on the start / address byte.
      $endgroup$
      – Transistor
      Apr 18 at 16:03










    • $begingroup$
      Re "CAN which samples every individual bit multiple times.": The actual sampling of the bit value is only once per bit. What are you referring to here? Some kind of error checking, like by the sender? Clock synchronisation?
      $endgroup$
      – Peter Mortensen
      Apr 19 at 12:33












    • $begingroup$
      The inverting of the checksum was done so that summing the entire block of data would result in a zero, which is a bit easier to code and a bit faster to execute. Also, CRC is much better than you make it out to be, look it up in the Wikipedia.
      $endgroup$
      – toolforger
      Apr 19 at 22:04














    • 7




      $begingroup$
      This advice is fairly tangential - you haven't actually addressed the question asked. In particular, your proposed solutions may solve other problems, but they do not solve the basic problem of the question on this page, which is confusion between framing byes and payload byes. At most, your proposal would reject valid data embedding a framing byte due to CRC or similar failure, with no way to communicate such.
      $endgroup$
      – Chris Stratton
      Apr 18 at 14:28








    • 3




      $begingroup$
      In fact, this answer makes it worse. The original had just data bytes and stop bytes. This adds a third category, CRC bytes. And as presented here, those can take on any value, including {10,13}.
      $endgroup$
      – MSalters
      Apr 18 at 15:53






    • 1




      $begingroup$
      @MSalters: The CRC can be ASCII encoded hex to prevent this issue. Another trick that I've seen on RS485 is to set bit 7 on the start / address byte.
      $endgroup$
      – Transistor
      Apr 18 at 16:03










    • $begingroup$
      Re "CAN which samples every individual bit multiple times.": The actual sampling of the bit value is only once per bit. What are you referring to here? Some kind of error checking, like by the sender? Clock synchronisation?
      $endgroup$
      – Peter Mortensen
      Apr 19 at 12:33












    • $begingroup$
      The inverting of the checksum was done so that summing the entire block of data would result in a zero, which is a bit easier to code and a bit faster to execute. Also, CRC is much better than you make it out to be, look it up in the Wikipedia.
      $endgroup$
      – toolforger
      Apr 19 at 22:04








    7




    7




    $begingroup$
    This advice is fairly tangential - you haven't actually addressed the question asked. In particular, your proposed solutions may solve other problems, but they do not solve the basic problem of the question on this page, which is confusion between framing byes and payload byes. At most, your proposal would reject valid data embedding a framing byte due to CRC or similar failure, with no way to communicate such.
    $endgroup$
    – Chris Stratton
    Apr 18 at 14:28






    $begingroup$
    This advice is fairly tangential - you haven't actually addressed the question asked. In particular, your proposed solutions may solve other problems, but they do not solve the basic problem of the question on this page, which is confusion between framing byes and payload byes. At most, your proposal would reject valid data embedding a framing byte due to CRC or similar failure, with no way to communicate such.
    $endgroup$
    – Chris Stratton
    Apr 18 at 14:28






    3




    3




    $begingroup$
    In fact, this answer makes it worse. The original had just data bytes and stop bytes. This adds a third category, CRC bytes. And as presented here, those can take on any value, including {10,13}.
    $endgroup$
    – MSalters
    Apr 18 at 15:53




    $begingroup$
    In fact, this answer makes it worse. The original had just data bytes and stop bytes. This adds a third category, CRC bytes. And as presented here, those can take on any value, including {10,13}.
    $endgroup$
    – MSalters
    Apr 18 at 15:53




    1




    1




    $begingroup$
    @MSalters: The CRC can be ASCII encoded hex to prevent this issue. Another trick that I've seen on RS485 is to set bit 7 on the start / address byte.
    $endgroup$
    – Transistor
    Apr 18 at 16:03




    $begingroup$
    @MSalters: The CRC can be ASCII encoded hex to prevent this issue. Another trick that I've seen on RS485 is to set bit 7 on the start / address byte.
    $endgroup$
    – Transistor
    Apr 18 at 16:03












    $begingroup$
    Re "CAN which samples every individual bit multiple times.": The actual sampling of the bit value is only once per bit. What are you referring to here? Some kind of error checking, like by the sender? Clock synchronisation?
    $endgroup$
    – Peter Mortensen
    Apr 19 at 12:33






    $begingroup$
    Re "CAN which samples every individual bit multiple times.": The actual sampling of the bit value is only once per bit. What are you referring to here? Some kind of error checking, like by the sender? Clock synchronisation?
    $endgroup$
    – Peter Mortensen
    Apr 19 at 12:33














    $begingroup$
    The inverting of the checksum was done so that summing the entire block of data would result in a zero, which is a bit easier to code and a bit faster to execute. Also, CRC is much better than you make it out to be, look it up in the Wikipedia.
    $endgroup$
    – toolforger
    Apr 19 at 22:04




    $begingroup$
    The inverting of the checksum was done so that summing the entire block of data would result in a zero, which is a bit easier to code and a bit faster to execute. Also, CRC is much better than you make it out to be, look it up in the Wikipedia.
    $endgroup$
    – toolforger
    Apr 19 at 22:04











    0












    $begingroup$


    ... I can imagine, though low probability, that my message might contain the values "10 and 13" after each other when they are not the stop bytes.




    A situation when a portion of data is equal to terminating sequence should be considered when designing the format of a serial data packet. Another thing to consider is that any character can get corrupted or lost during transmission. A start character, a stop character, a data payload byte, a checksum or CRC byte, a forward error correction byte aren't immune to corruption. The framing mechanism has to be able to detect when a packet has corrupt data.



    There a several ways to approach all this.



    I'm making the working assumption that packets are framed only with the serial bytes. Handshake lines aren't used for framing. Time delays aren't used for framing.



    Send packet length



    Send the length of the packet in the beginning, instead of [or in addition to] the terminating character at the end.



    pros: Payload is sent in a efficient binary format.



    cons: Need to know the packet length at the start of the transmission.



    Escape the special characters



    Escape the special characters when sending the payload data. This is already explained in a an earlier answer.



    pros: Sender doesn't need to know the length of the packet at the beginning of the transmission.



    cons: Slightly less efficient, depending on how many payload bytes need to be escaped.



    Payload data encoded such that it can't contain start and stop characters



    The payload of the packet is encoded such that it can't contain the start or stop characters. Usually, this is done by sending numbers as their ASCII or Hex-ASCII representation.



    pros: Human-readable with common terminal programs. No need for code to handle escaping. No need to know the length of the packet at the start of the transmission



    cons: Lower efficiency. For one byte of payload data, several bytes are sent.






    share|improve this answer











    $endgroup$


















      0












      $begingroup$


      ... I can imagine, though low probability, that my message might contain the values "10 and 13" after each other when they are not the stop bytes.




      A situation when a portion of data is equal to terminating sequence should be considered when designing the format of a serial data packet. Another thing to consider is that any character can get corrupted or lost during transmission. A start character, a stop character, a data payload byte, a checksum or CRC byte, a forward error correction byte aren't immune to corruption. The framing mechanism has to be able to detect when a packet has corrupt data.



      There a several ways to approach all this.



      I'm making the working assumption that packets are framed only with the serial bytes. Handshake lines aren't used for framing. Time delays aren't used for framing.



      Send packet length



      Send the length of the packet in the beginning, instead of [or in addition to] the terminating character at the end.



      pros: Payload is sent in a efficient binary format.



      cons: Need to know the packet length at the start of the transmission.



      Escape the special characters



      Escape the special characters when sending the payload data. This is already explained in a an earlier answer.



      pros: Sender doesn't need to know the length of the packet at the beginning of the transmission.



      cons: Slightly less efficient, depending on how many payload bytes need to be escaped.



      Payload data encoded such that it can't contain start and stop characters



      The payload of the packet is encoded such that it can't contain the start or stop characters. Usually, this is done by sending numbers as their ASCII or Hex-ASCII representation.



      pros: Human-readable with common terminal programs. No need for code to handle escaping. No need to know the length of the packet at the start of the transmission



      cons: Lower efficiency. For one byte of payload data, several bytes are sent.






      share|improve this answer











      $endgroup$
















        0












        0








        0





        $begingroup$


        ... I can imagine, though low probability, that my message might contain the values "10 and 13" after each other when they are not the stop bytes.




        A situation when a portion of data is equal to terminating sequence should be considered when designing the format of a serial data packet. Another thing to consider is that any character can get corrupted or lost during transmission. A start character, a stop character, a data payload byte, a checksum or CRC byte, a forward error correction byte aren't immune to corruption. The framing mechanism has to be able to detect when a packet has corrupt data.



        There a several ways to approach all this.



        I'm making the working assumption that packets are framed only with the serial bytes. Handshake lines aren't used for framing. Time delays aren't used for framing.



        Send packet length



        Send the length of the packet in the beginning, instead of [or in addition to] the terminating character at the end.



        pros: Payload is sent in a efficient binary format.



        cons: Need to know the packet length at the start of the transmission.



        Escape the special characters



        Escape the special characters when sending the payload data. This is already explained in a an earlier answer.



        pros: Sender doesn't need to know the length of the packet at the beginning of the transmission.



        cons: Slightly less efficient, depending on how many payload bytes need to be escaped.



        Payload data encoded such that it can't contain start and stop characters



        The payload of the packet is encoded such that it can't contain the start or stop characters. Usually, this is done by sending numbers as their ASCII or Hex-ASCII representation.



        pros: Human-readable with common terminal programs. No need for code to handle escaping. No need to know the length of the packet at the start of the transmission



        cons: Lower efficiency. For one byte of payload data, several bytes are sent.






        share|improve this answer











        $endgroup$




        ... I can imagine, though low probability, that my message might contain the values "10 and 13" after each other when they are not the stop bytes.




        A situation when a portion of data is equal to terminating sequence should be considered when designing the format of a serial data packet. Another thing to consider is that any character can get corrupted or lost during transmission. A start character, a stop character, a data payload byte, a checksum or CRC byte, a forward error correction byte aren't immune to corruption. The framing mechanism has to be able to detect when a packet has corrupt data.



        There a several ways to approach all this.



        I'm making the working assumption that packets are framed only with the serial bytes. Handshake lines aren't used for framing. Time delays aren't used for framing.



        Send packet length



        Send the length of the packet in the beginning, instead of [or in addition to] the terminating character at the end.



        pros: Payload is sent in a efficient binary format.



        cons: Need to know the packet length at the start of the transmission.



        Escape the special characters



        Escape the special characters when sending the payload data. This is already explained in a an earlier answer.



        pros: Sender doesn't need to know the length of the packet at the beginning of the transmission.



        cons: Slightly less efficient, depending on how many payload bytes need to be escaped.



        Payload data encoded such that it can't contain start and stop characters



        The payload of the packet is encoded such that it can't contain the start or stop characters. Usually, this is done by sending numbers as their ASCII or Hex-ASCII representation.



        pros: Human-readable with common terminal programs. No need for code to handle escaping. No need to know the length of the packet at the start of the transmission



        cons: Lower efficiency. For one byte of payload data, several bytes are sent.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Apr 19 at 21:28

























        answered Apr 19 at 21:07









        Nick AlexeevNick Alexeev

        32.7k1066167




        32.7k1066167






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Electrical Engineering Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            Use MathJax to format equations. MathJax reference.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2felectronics.stackexchange.com%2fquestions%2f433202%2fhow-fail-safe-is-n-r-as-stop-bytes%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Færeyskur hestur Heimild | Tengill | Tilvísanir | LeiðsagnarvalRossið - síða um færeyska hrossið á færeyskuGott ár hjá færeyska hestinum

            He _____ here since 1970 . Answer needed [closed]What does “since he was so high” mean?Meaning of “catch birds for”?How do I ensure “since” takes the meaning I want?“Who cares here” meaningWhat does “right round toward” mean?the time tense (had now been detected)What does the phrase “ring around the roses” mean here?Correct usage of “visited upon”Meaning of “foiled rail sabotage bid”It was the third time I had gone to Rome or It is the third time I had been to Rome

            Slayer Innehåll Historia | Stil, komposition och lyrik | Bandets betydelse och framgångar | Sidoprojekt och samarbeten | Kontroverser | Medlemmar | Utmärkelser och nomineringar | Turnéer och festivaler | Diskografi | Referenser | Externa länkar | Navigeringsmenywww.slayer.net”Metal Massacre vol. 1””Metal Massacre vol. 3””Metal Massacre Volume III””Show No Mercy””Haunting the Chapel””Live Undead””Hell Awaits””Reign in Blood””Reign in Blood””Gold & Platinum – Reign in Blood””Golden Gods Awards Winners”originalet”Kerrang! Hall Of Fame””Slayer Looks Back On 37-Year Career In New Video Series: Part Two””South of Heaven””Gold & Platinum – South of Heaven””Seasons in the Abyss””Gold & Platinum - Seasons in the Abyss””Divine Intervention””Divine Intervention - Release group by Slayer””Gold & Platinum - Divine Intervention””Live Intrusion””Undisputed Attitude””Abolish Government/Superficial Love””Release “Slatanic Slaughter: A Tribute to Slayer” by Various Artists””Diabolus in Musica””Soundtrack to the Apocalypse””God Hates Us All””Systematic - Relationships””War at the Warfield””Gold & Platinum - War at the Warfield””Soundtrack to the Apocalypse””Gold & Platinum - Still Reigning””Metallica, Slayer, Iron Mauden Among Winners At Metal Hammer Awards””Eternal Pyre””Eternal Pyre - Slayer release group””Eternal Pyre””Metal Storm Awards 2006””Kerrang! Hall Of Fame””Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Bullet-For My Valentine booed at Metal Hammer Golden Gods Awards””Unholy Aliance””The End Of Slayer?””Slayer: We Could Thrash Out Two More Albums If We're Fast Enough...””'The Unholy Alliance: Chapter III' UK Dates Added”originalet”Megadeth And Slayer To Co-Headline 'Canadian Carnage' Trek”originalet”World Painted Blood””Release “World Painted Blood” by Slayer””Metallica Heading To Cinemas””Slayer, Megadeth To Join Forces For 'European Carnage' Tour - Dec. 18, 2010”originalet”Slayer's Hanneman Contracts Acute Infection; Band To Bring In Guest Guitarist””Cannibal Corpse's Pat O'Brien Will Step In As Slayer's Guest Guitarist”originalet”Slayer’s Jeff Hanneman Dead at 49””Dave Lombardo Says He Made Only $67,000 In 2011 While Touring With Slayer””Slayer: We Do Not Agree With Dave Lombardo's Substance Or Timeline Of Events””Slayer Welcomes Drummer Paul Bostaph Back To The Fold””Slayer Hope to Unveil Never-Before-Heard Jeff Hanneman Material on Next Album””Slayer Debut New Song 'Implode' During Surprise Golden Gods Appearance””Release group Repentless by Slayer””Repentless - Slayer - Credits””Slayer””Metal Storm Awards 2015””Slayer - to release comic book "Repentless #1"””Slayer To Release 'Repentless' 6.66" Vinyl Box Set””BREAKING NEWS: Slayer Announce Farewell Tour””Slayer Recruit Lamb of God, Anthrax, Behemoth + Testament for Final Tour””Slayer lägger ner efter 37 år””Slayer Announces Second North American Leg Of 'Final' Tour””Final World Tour””Slayer Announces Final European Tour With Lamb of God, Anthrax And Obituary””Slayer To Tour Europe With Lamb of God, Anthrax And Obituary””Slayer To Play 'Last French Show Ever' At Next Year's Hellfst””Slayer's Final World Tour Will Extend Into 2019””Death Angel's Rob Cavestany On Slayer's 'Farewell' Tour: 'Some Of Us Could See This Coming'””Testament Has No Plans To Retire Anytime Soon, Says Chuck Billy””Anthrax's Scott Ian On Slayer's 'Farewell' Tour Plans: 'I Was Surprised And I Wasn't Surprised'””Slayer””Slayer's Morbid Schlock””Review/Rock; For Slayer, the Mania Is the Message””Slayer - Biography””Slayer - Reign In Blood”originalet”Dave Lombardo””An exclusive oral history of Slayer”originalet”Exclusive! Interview With Slayer Guitarist Jeff Hanneman”originalet”Thinking Out Loud: Slayer's Kerry King on hair metal, Satan and being polite””Slayer Lyrics””Slayer - Biography””Most influential artists for extreme metal music””Slayer - Reign in Blood””Slayer guitarist Jeff Hanneman dies aged 49””Slatanic Slaughter: A Tribute to Slayer””Gateway to Hell: A Tribute to Slayer””Covered In Blood””Slayer: The Origins of Thrash in San Francisco, CA.””Why They Rule - #6 Slayer”originalet”Guitar World's 100 Greatest Heavy Metal Guitarists Of All Time”originalet”The fans have spoken: Slayer comes out on top in readers' polls”originalet”Tribute to Jeff Hanneman (1964-2013)””Lamb Of God Frontman: We Sound Like A Slayer Rip-Off””BEHEMOTH Frontman Pays Tribute To SLAYER's JEFF HANNEMAN””Slayer, Hatebreed Doing Double Duty On This Year's Ozzfest””System of a Down””Lacuna Coil’s Andrea Ferro Talks Influences, Skateboarding, Band Origins + More””Slayer - Reign in Blood””Into The Lungs of Hell””Slayer rules - en utställning om fans””Slayer and Their Fans Slashed Through a No-Holds-Barred Night at Gas Monkey””Home””Slayer””Gold & Platinum - The Big 4 Live from Sofia, Bulgaria””Exclusive! Interview With Slayer Guitarist Kerry King””2008-02-23: Wiltern, Los Angeles, CA, USA””Slayer's Kerry King To Perform With Megadeth Tonight! - Oct. 21, 2010”originalet”Dave Lombardo - Biography”Slayer Case DismissedArkiveradUltimate Classic Rock: Slayer guitarist Jeff Hanneman dead at 49.”Slayer: "We could never do any thing like Some Kind Of Monster..."””Cannibal Corpse'S Pat O'Brien Will Step In As Slayer'S Guest Guitarist | The Official Slayer Site”originalet”Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Kerrang! Awards 2006 Blog: Kerrang! Hall Of Fame””Kerrang! Awards 2013: Kerrang! Legend”originalet”Metallica, Slayer, Iron Maien Among Winners At Metal Hammer Awards””Metal Hammer Golden Gods Awards””Bullet For My Valentine Booed At Metal Hammer Golden Gods Awards””Metal Storm Awards 2006””Metal Storm Awards 2015””Slayer's Concert History””Slayer - Relationships””Slayer - Releases”Slayers officiella webbplatsSlayer på MusicBrainzOfficiell webbplatsSlayerSlayerr1373445760000 0001 1540 47353068615-5086262726cb13906545x(data)6033143kn20030215029