Timeline for Serial XOnXOff handshaking
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 15:10 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jun 11, 2015 at 19:09 | comment | added | Suba Thomas | Yes, that's what I'm planning to do at the moment. Stick with XOn and XOff, and not use any flow control, i.e. set it to None. | |
| Jun 11, 2015 at 18:56 | comment | added | Asmyldof | @SubaThomas Very well, It's not wrong, as you can see, but calling them Xon/Xoff implies buffering and you can't expect your use-case to have them done automatically. I had actually not noticed the duality there, to be honest. If you use Xon/Xoff though, make sure the ports aren't configured for it, or they will be caught. The atmel doesn't have the option, so that's okay, but if you start sending them back and want to parse them yourself, remember to turn off flow control in you com port. | |
| Jun 11, 2015 at 18:50 | vote | accept | Suba Thomas | ||
| Jun 11, 2015 at 18:50 | comment | added | Suba Thomas | Thanks again. I have decided to leave it at DC1/XOn/17 and DC3/XOff/19. | |
| Jun 11, 2015 at 17:59 | comment | added | Asmyldof | @SubaThomas For your use, as I understand it, the special control cases to send from PC to device that don't really fit anything "should" be handled with DC1 through 4. They are "Device Commands" that you can define as meaning anything you like. They should never be sent by generic drivers, but may cause confusion when using Program A with Device B, of course. But, to be honest, I don't see many people using control characters any more, so any pick would be relatively safe. If you want to at least not confuse mouse drivers and such: Use DC1 ~ 4 in both directions for special stuff. | |
| Jun 11, 2015 at 17:56 | comment | added | Asmyldof | @SubaThomas STX and ETX are commonly used for "Here is the message" and "message done", so you would add them to a stream to identify "normal text" between blocks of header or other information. They may be useful at some point. If you need to send different bits of data from different sources you can put a "Record Separator" or "Unit Separator" between them. RS is most common. SOH is often used for "attention, here is data" followed by a header, then STX followed by message, followed by ETX a footer and then EOT, or EOT right after the message. | |
| Jun 11, 2015 at 16:43 | comment | added | Suba Thomas | Thanks, especially for that ASCII table. Please see my update. Do you have an opinion on what is appropriate. Is there some kind of standard for my scenario? I also need to pick a third character as a delimiter for cases when there there multiple inputs and/or outputs. | |
| Jun 11, 2015 at 15:25 | history | edited | Asmyldof | CC BY-SA 3.0 |
added 528 characters in body
|
| Jun 11, 2015 at 15:13 | history | answered | Asmyldof | CC BY-SA 3.0 |