Menu
A PL2303 serial-over-USB device is configured to receive-only data. There is an explanation of tty vs cu here:
MacOS: what's the difference between /dev/tty.* and /dev/cu.*?
That being said, when configuring data collection software, one has to choose either /dev/tty.usbserial OR /dev/cu.usbserial. I would like to understand the facts and the decision-making thought for selecting tty or cu.
459
In practice, it probably matters for historical things like uucp. For everything that's not a modem or that's not intended to be shared between call-out/call-in processes, you should use the /dev/cu.* as this gives you exclusive access to the device.
Each serial device shows up twice in /dev, once as a tty.* and once as a cu.*. What is the cu.* device? How does it differ from the tty.* device? Show activity on this post. The idea is to supplement software in sharing a line between incoming and outgoing calls. The callin device (typically /dev/tty*) is used for incoming traffic.
A PL2303 serial-over-USB device is configured to receive-only data. There is an explanation of tty vs cu here: MacOS: what's the difference between /dev/tty.* and /dev/cu.*?
Each serial device shows up twice in /dev, once as a tty.* and once as a cu.*. What is the cu.* device? How does it differ from the tty.* device? Show activity on this post.
The distinction only matters when you use a modem that provides the DCD signal and you're interested in sharing the device between two or more processes: one or more that can occasionally call out, and exactly one that wants to answer calls. In practice, it probably matters for historical things like uucp.
For everything that's not a modem or that's not intended to be shared between call-out/call-in processes, you should use the /dev/cu.* as this gives you exclusive access to the device.
89
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
