you ask, "What good does it do to have a fantastic piece of equipment if it can not communicate with what it is supposes to communicate with such as a PC?"

to which I reply, What good is a piece of async comm gear that can't do anything but communicate async? The processing isn't always the only thing it has to do. It isn't even always the most important thing it has to do. If its most important task is communicating, it probably shouldnt be wasting bandwidth on async protocol. Of course, in the auto industry they don't care about efficiency, do they?

BTW, it's clearly not a typo ... the word you keep misspelling is "babbling," not "babbeling."

Now, there's what it could be, but can't because it's talking to things too dumb to do it right, and there's what it should be. So long as you are aware of both, it's fine. Things seldom end up as they ought.

If you use mode-0 with a somewhat faster than 12 MHz one-clocker, you can stuff your data into that T1 frame. That's something you'll NEVER be able to do with async gear unless you put a different piece of equipment between you and the DSU/CSU. Clearly you're using a stat-mux of some sort if you're talking async.

You probably could talk directly in sync with a T1 frame, possibly even a T3 frame, with a 1-clock MCU as fast as the ones you're using, but not in async protocol. (That's one thing mode-0 might do for you.)

RE