[time-nuts] OT : different Rx and Tx baud rate on same port

[Paul Alfille]

An alternative to writing your own software is using 'socat' which can
interface between a tcp port and serial port (perhaps using a raspberry pi
or the like as the interface). It apparently has settings for separate
ispeed and ospeed. Its competitor, ser2net, doesn't seem to have that
ability.

This way you can create a virtual serial port with the baud rate details
hidden.

As for whether all this would work on current hardware -- I haven't tested
because I haven't had reason to try, nor the hardware to test it on. I can
tell you, as I noted above, that changing baud rates on the fly works, even
with telnet connections using RFC2217 commands, since I use that with
1-wire work. The only problems were some of the stranger settings, like
6-bit words.

Paul Alfille


On Sat, Dec 7, 2013 at 3:18 PM, Hal Murray <hmurray at megapathdsl.net> wrote:

>
> bg at lysator.liu.se said:
> > Looking at the "stty" unix command. It seems clear that split baud rates
> has
> > been supported at one time.
>
> On Linux, man termios gives lots of API details.
>
> On NetBSD and FreeBSD, that gets an overview.  man tcsetattr gets the API
> details.
>
> If you use stty to change things, the new info is sticky.  So if you have a
> program that is all set to go except that the baud rates aren't right and
> that program doesn't smash the baud rates, you can set them with stty and
> your program should work.  I haven't tried it with split baud rates, but
> the
> normal (non-split) case works.
>
> If your gizmo uses simple ASCII, you can test things with cat /dev/wherever
> and things like this on another terminal
>   echo "blah blah..." > /dev/wherever
>
>
> --
> These are my opinions.  I hate spam.
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>