Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simultaneous use of the leop-client and the MCC #2

Open
crespum opened this issue Jan 10, 2015 · 4 comments
Open

Simultaneous use of the leop-client and the MCC #2

crespum opened this issue Jan 10, 2015 · 4 comments
Assignees

Comments

@crespum
Copy link
Member

crespum commented Jan 10, 2015

At this moment, it is not possible to use both the leop-client and the MCC at the same time. The problem is that only one process at a time can read data from the serial port.
One possible solution may include creating a virtual port from the OS and forwarding the received data from the TNC to that port. This forwarding could be done either from the client or from the OS.

@rtubio
Copy link

rtubio commented Jan 12, 2015

Take a look at this application, it permits creating virtual serial ports exactly the way we need them:

http://com0com.sourceforge.net/

@rtubio
Copy link

rtubio commented Jan 13, 2015

In the following README, they explain perfectly what we can do with that application:

http://com0com.cvs.sourceforge.net/viewvc/com0com/com0com/ReadMe.txt?revision=RELEASED

@rtubio
Copy link

rtubio commented Jan 13, 2015

@crespum
Copy link
Member Author

crespum commented Jan 15, 2015

I tried the following command under Debian (ttyACM1 corresponds to the TNC):

sudo socat -d -d /dev/ttyUSB0 pty,link=/dev/ttyS0

Then I opened two minicom terminals but the messages could only be read from one of them at a time. Sometimes they were shown under the terminal reading /dev/ttyS0 and sometimes under the other terminal, for no apparent reason to select one or another.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants