That's clearly not true, as both ethernet and USB are serial. What you tend to need is a link layer implementation (which can be software) to packetise and multiplex messages. (Ethernet also allows multiplexing with multiple physical line drivers, which requires a master station which knows who is on the link, collision detection or some sort of discovery protocol.)
There are standards for multiplexing over asynchronous serial connections. Some, like SLIP, are very simple. One could also have application specific ones, although there would be problems getting everyone to agree on the same one. (SLIP is really a packetisation protocol, it needs a multiplexing one, which can be IP, but can be simply prefixing with a channel number.) Apologies for pronouns preceding nouns, but that is list policy! Ken Nicely wrote: > > One of the main problems with the serial communication is that only one > software application or device can connect at a time, so we end up with -- David Woolley "we do not overly restrict the subject matter on the list, and we encourage postings on a wide range of amateur radio related topics" List Guidelines <http://www.elecraft.com/elecraft_list_guidelines.htm> ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
