??? 03/28/09 00:13 Read: times |
#163914 - Timing Responding to: ???'s previous message |
If you know how long a character is supposed to take at the baud rate at which you're operating, then, having sent an AT, which should produce an OK, you can time the length of the string.
Starting with the baud rates in the order of your own preference is not a bad idea, i.e. send AT and listen for OK. It's only if that doesn't work that you have to do something more involved, like sending your AT command and then "listening" for the start bit and timing out how long the response is. It's likely to complain in some way, typically with "ERROR" or some such. If you know what the modem is supposed to say when there's a framing error, you should be able to tell from the length of the predetermined response, what, approximately, the baud rate is. Async comm's are not that precise. They're usually happy with ~2-3 percent. If you "try" the baud rates in the order of your own preference, you'll likely end up with one you like. RE |
Topic | Author | Date |
Autobaud - the other end... | 01/01/70 00:00 | |
Doh | 01/01/70 00:00 | |
Eh? | 01/01/70 00:00 | |
Homing in | 01/01/70 00:00 | |
Considerations | 01/01/70 00:00 | |
How does it respond to AT? | 01/01/70 00:00 | |
The proper response to "AT" is "OK" | 01/01/70 00:00 | |
no absolutely perfect solution | 01/01/70 00:00 | |
Character time | 01/01/70 00:00 | |
Go for KISS | 01/01/70 00:00 | |
only be needed once after a modem change. | 01/01/70 00:00 | |
Some ARM7's have Autobaud detect | 01/01/70 00:00 | |
No - the *other* end! | 01/01/70 00:00 | |
Fall back and forward | 01/01/70 00:00 | |
Only interested in local DTE-DCE speed | 01/01/70 00:00 | |
You were clear | 01/01/70 00:00 | |
Start slow, or start fast...? | 01/01/70 00:00 | |
Unnecessarily high? | 01/01/70 00:00 | |
High baudrate = bursty | 01/01/70 00:00 | |
Throughtput | 01/01/70 00:00 | |
Keep Up? | 01/01/70 00:00 | |
Keeping up always hard at high baudrates | 01/01/70 00:00 | |
KISS? | 01/01/70 00:00 | |
A Cunning Plan... | 01/01/70 00:00 | |
Timing | 01/01/70 00:00 |