??? 03/27/09 15:09 Read: times |
#163912 - Go for KISS Responding to: ???'s previous message |
I think I would ignore looking for bit timing or transfer timing from any response. If the modem has echo on and receives incorrect characters because of incorrect baudrate, you have to figure out how many characters the modem is actually echoing back.
Analyzing the response will give clues that can improve the synchronization speed. But KISS normally wins. Let the poor 8051 fight through the baudrates in a spiral pattern. If n is optimum, then test n, n+1, n-1, n+2, n-2, ... until you either get a lock or runs out of baudrates to test. Then decide if the baudrate is good enough, or if you should move the modem to a better baudrate. If you save your favourite setting in the modem, then the extra synchronization step will only be needed once after a modem change. |
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 |