I doubt that this level of control (includes fiddling with control signals like RTS (Request to Send), CLS (Clear to Send), etc is needed. I think all that is needed here is binary data send/receive (not low level access to the flow control signals).
A modern computer can keep up easily with the port, even at "high" baud rate settings.
Also many of the computers nowadays have very limited RS-232 support and all of the flow control signals may not be even available! xon/xoff flow control is the way to go (if possible and needed) - however even no flow control at all is often fine!
The serial port chip or emulator will have at least 16 bytes of buffer. If this is a simple request/response protocol (no asynchronous messages being used), the programming should be fairly straight-forward.
RS-232 serial port communication is going the way of the dodo bird although it will "live" and be useful for a very long time.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.