Struct serial2::SerialPort
source · pub struct SerialPort { /* private fields */ }Expand description
A serial port.
Implementations§
source§impl SerialPort
impl SerialPort
sourcepub fn open(name: impl AsRef<Path>, settings: impl IntoSettings) -> Result<Self>
pub fn open(name: impl AsRef<Path>, settings: impl IntoSettings) -> Result<Self>
Open and configure a serial port by path or name.
On Unix systems, the name parameter must be a path to a TTY device.
On Windows, it must be the name of a COM device, such as COM1, COM2, etc.
The second argument is used to configure the serial port.
For simple cases, you pass a u32 for the baud rate.
See IntoSettings for more information.
The library automatically uses the win32 device namespace on Windows, so COM ports above COM9 are supported out of the box.
Example
SerialPort::open("/dev/ttyUSB0", 115200)?;Examples found in repository?
6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
fn do_main() -> Result<(), ()> {
let args: Vec<_> = std::env::args().collect();
if args.len() != 3 {
let prog_name = args[0].rsplit_once('/').map(|(_parent, name)| name).unwrap_or(&args[0]);
eprintln!("Usage: {} PORT BAUD", prog_name);
return Err(());
}
let port_name = &args[1];
let baud_rate: u32 = args[2]
.parse()
.map_err(|_| eprintln!("Error: invalid baud rate: {}", args[2]))?;
let port = SerialPort::open(port_name, baud_rate)
.map_err(|e| eprintln!("Error: Failed to open {}: {}", port_name, e))?;
let port = Arc::new(port);
// Spawn a thread to read from stdin and write to the serial port.
std::thread::spawn({
let port = port.clone();
let port_name = port_name.to_owned();
move || {
if let Err(()) = read_stdin_loop(port, &port_name) {
std::process::exit(1);
}
}
});
// Read from serial port and write to stdout in main thread.
read_serial_loop(port, port_name)?;
Ok(())
}sourcepub fn available_ports() -> Result<Vec<PathBuf>>
pub fn available_ports() -> Result<Vec<PathBuf>>
Get a list of available serial ports.
Not currently supported on all platforms. On unsupported platforms, this function always returns an error.
Examples found in repository?
1 2 3 4 5 6 7 8 9 10 11 12 13 14
fn main() {
match serial2::SerialPort::available_ports() {
Err(e) => {
eprintln!("Failed to enumerate serial ports: {}", e);
std::process::exit(1);
},
Ok(ports) => {
eprintln!("Found {} ports", ports.len());
for port in ports {
println!("{}", port.display())
}
},
}
}sourcepub fn set_configuration(&mut self, settings: &Settings) -> Result<()>
pub fn set_configuration(&mut self, settings: &Settings) -> Result<()>
Configure (or reconfigure) the serial port.
sourcepub fn get_configuration(&self) -> Result<Settings>
pub fn get_configuration(&self) -> Result<Settings>
Get the current configuration of the serial port.
This function can fail if the underlying syscall fails,
or if the serial port configuration can’t be reported using Settings.
sourcepub fn read(&self, buf: &mut [u8]) -> Result<usize>
pub fn read(&self, buf: &mut [u8]) -> Result<usize>
Read bytes from the serial port.
This is identical to std::io::Read::read(), except that this function takes a const reference &self.
This allows you to use the serial port concurrently from multiple threads.
Note that there are no guarantees on which thread receives what data when multiple threads are reading from the serial port. You should normally limit yourself to a single reading thread and a single writing thread.
Examples found in repository?
57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74
fn read_serial_loop(port: Arc<SerialPort>, port_name: &str) -> Result<(), ()> {
let mut buffer = [0; 512];
loop {
match port.read(&mut buffer) {
Ok(0) => return Ok(()),
Ok(n) => {
std::io::stdout()
.write_all(&buffer[..n])
.map_err(|e| eprintln!("Error: Failed to write to stdout: {}", e))?;
},
Err(ref e) if e.kind() == std::io::ErrorKind::TimedOut => continue,
Err(e) => {
eprintln!("Error: Failed to read from {}: {}", port_name, e);
return Err(());
},
}
}
}sourcepub fn read_vectored(&self, buf: &mut [IoSliceMut<'_>]) -> Result<usize>
pub fn read_vectored(&self, buf: &mut [IoSliceMut<'_>]) -> Result<usize>
Read bytes from the serial port into a slice of buffers.
This is identical to std::io::Read::read_vectored(), except that this function takes a const reference &self.
This allows you to use the serial port concurrently from multiple threads.
Note that there are no guarantees on which thread receives what data when multiple threads are reading from the serial port. You should normally limit yourself to a single reading thread and a single writing thread.
sourcepub fn is_read_vectored(&self) -> bool
pub fn is_read_vectored(&self) -> bool
Check if the implementation supports vectored reads.
If this returns false, then Self::read_vectored() will only use the first buffer of the given slice.
All platforms except for Windows support vectored reads.
sourcepub fn write(&self, buf: &[u8]) -> Result<usize>
pub fn write(&self, buf: &[u8]) -> Result<usize>
Write bytes to the serial port.
This is identical to std::io::Write::write(), except that this function takes a const reference &self.
This allows you to use the serial port concurrently from multiple threads.
Note that data written to the same serial port from multiple threads may end up interleaved at the receiving side. You should normally limit yourself to a single reading thread and a single writing thread.
Examples found in repository?
40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55
fn read_stdin_loop(port: Arc<SerialPort>, port_name: &str) -> Result<(), ()> {
let stdin = std::io::stdin();
let mut stdin = stdin.lock();
let mut buffer = [0; 512];
loop {
let read = stdin
.read(&mut buffer)
.map_err(|e| eprintln!("Error: Failed to read from stdin: {}", e))?;
if read == 0 {
return Ok(());
} else {
port.write(&buffer[..read])
.map_err(|e| eprintln!("Error: Failed to write to {}: {}", port_name, e))?;
}
}
}sourcepub fn write_all(&self, buf: &[u8]) -> Result<()>
pub fn write_all(&self, buf: &[u8]) -> Result<()>
Write all bytes to the serial port.
This will continue to call Self::write() until the entire buffer has been written,
or an I/O error occurs.
This is identical to std::io::Write::write_all(), except that this function takes a const reference &self.
This allows you to use the serial port concurrently from multiple threads.
Note that data written to the same serial port from multiple threads may end up interleaved at the receiving side. You should normally limit yourself to a single reading thread and a single writing thread.
sourcepub fn write_vectored(&self, buf: &[IoSlice<'_>]) -> Result<usize>
pub fn write_vectored(&self, buf: &[IoSlice<'_>]) -> Result<usize>
Write bytes to the serial port from a slice of buffers.
This is identical to std::io::Write::write_vectored(), except that this function takes a const reference &self.
This allows you to use the serial port concurrently from multiple threads.
Note that data written to the same serial port from multiple threads may end up interleaved at the receiving side. You should normally limit yourself to a single reading thread and a single writing thread.
sourcepub fn is_write_vectored(&self) -> bool
pub fn is_write_vectored(&self) -> bool
Check if the implementation supports vectored writes.
If this returns false, then Self::write_vectored() will only use the first buffer of the given slice.
All platforms except for Windows support vectored writes.
sourcepub fn flush(&self) -> Result<()>
pub fn flush(&self) -> Result<()>
Flush all data queued to be written.
This will block until the OS buffer has been fully transmitted.
This is identical to std::io::Write::flush(), except that this function takes a const reference &self.
sourcepub fn set_read_timeout(&mut self, timeout: Duration) -> Result<()>
pub fn set_read_timeout(&mut self, timeout: Duration) -> Result<()>
Set the read timeout for the serial port.
The timeout set by this function is an upper bound on individual calls to std::io::Read::read().
Other platform specific time-outs may trigger before this timeout does.
sourcepub fn get_read_timeout(&self) -> Result<Duration>
pub fn get_read_timeout(&self) -> Result<Duration>
Get the read timeout of the serial port.
sourcepub fn set_write_timeout(&mut self, timeout: Duration) -> Result<()>
pub fn set_write_timeout(&mut self, timeout: Duration) -> Result<()>
Set the write timeout for the serial port.
The timeout set by this function is an upper bound on individual calls to std::io::Write::write().
Other platform specific time-outs may trigger before this timeout does.
sourcepub fn get_write_timeout(&self) -> Result<Duration>
pub fn get_write_timeout(&self) -> Result<Duration>
Get the write timeout of the serial port.
sourcepub fn get_windows_timeouts(&self) -> Result<CommTimeouts>
Available on crate feature windows only.
pub fn get_windows_timeouts(&self) -> Result<CommTimeouts>
windows only.Get the platform specific timeouts of a serial port on Windows.
This allows for full control over the platform specifics timeouts, but it is only available on Windows.
Also note that changing the read timeouts can easily lead to the serial port timing out on every read unless you are very careful. Please read the whole article about serial port timeouts on MSDN before using this, including all remarks: https://learn.microsoft.com/en-us/windows/win32/api/winbase/ns-winbase-commtimeouts
You are strongly suggested to use Self::get_read_timeout() and Self::get_write_timeout() instead.
sourcepub fn set_windows_timeouts(&self, timeouts: &CommTimeouts) -> Result<()>
Available on crate feature windows only.
pub fn set_windows_timeouts(&self, timeouts: &CommTimeouts) -> Result<()>
windows only.Set the platform specific timeouts of a serial port on Windows.
This allows for full control over the platform specifics timeouts, but it is only available on Windows.
Also note that changing the read timeouts can easily lead to the serial port timing out on every read unless you are very careful. Please read the whole article about serial port timeouts on MSDN before using this, including all remarks: https://learn.microsoft.com/en-us/windows/win32/api/winbase/ns-winbase-commtimeouts
You are strongly suggested to use Self::set_read_timeout() and Self::set_write_timeout() instead.
sourcepub fn discard_buffers(&self) -> Result<()>
pub fn discard_buffers(&self) -> Result<()>
Discard the kernel input and output buffers for the serial port.
When you write to a serial port, the data may be put in a buffer by the OS to be transmitted by the actual device later. Similarly, data received on the device can be put in a buffer by the OS untill you read it. This function clears both buffers: any untransmitted data and received but unread data is discarded by the OS.
sourcepub fn discard_input_buffer(&self) -> Result<()>
pub fn discard_input_buffer(&self) -> Result<()>
Discard the kernel input buffers for the serial port.
Data received on the device can be put in a buffer by the OS untill you read it. This function clears that buffer: received but unread data is discarded by the OS.
This is particularly useful when communicating with a device that only responds to commands that you send to it. If you discard the input buffer before sending the command, you discard any noise that may have been received after the last command.
sourcepub fn discard_output_buffer(&self) -> Result<()>
pub fn discard_output_buffer(&self) -> Result<()>
Discard the kernel output buffers for the serial port.
When you write to a serial port, the data is generally put in a buffer by the OS to be transmitted by the actual device later. This function clears that buffer: any untransmitted data is discarded by the OS.
sourcepub fn set_rts(&self, state: bool) -> Result<()>
pub fn set_rts(&self, state: bool) -> Result<()>
Set the state of the Ready To Send line.
If hardware flow control is enabled on the serial port, it is platform specific what will happen. The function may fail with an error or it may silently be ignored. It may even succeed and interfere with the flow control.
sourcepub fn read_cts(&self) -> Result<bool>
pub fn read_cts(&self) -> Result<bool>
Read the state of the Clear To Send line.
If hardware flow control is enabled on the serial port, it is platform specific what will happen. The function may fail with an error, it may return a bogus value, or it may return the actual state of the CTS line.
sourcepub fn set_dtr(&self, state: bool) -> Result<()>
pub fn set_dtr(&self, state: bool) -> Result<()>
Set the state of the Data Terminal Ready line.
If hardware flow control is enabled on the serial port, it is platform specific what will happen. The function may fail with an error or it may silently be ignored.
sourcepub fn read_dsr(&self) -> Result<bool>
pub fn read_dsr(&self) -> Result<bool>
Read the state of the Data Set Ready line.
If hardware flow control is enabled on the serial port, it is platform specific what will happen. The function may fail with an error, it may return a bogus value, or it may return the actual state of the DSR line.
Trait Implementations§
source§impl AsFd for SerialPort
impl AsFd for SerialPort
source§fn as_fd(&self) -> BorrowedFd<'_>
fn as_fd(&self) -> BorrowedFd<'_>
source§impl AsRawFd for SerialPort
impl AsRawFd for SerialPort
source§impl From<OwnedFd> for SerialPort
impl From<OwnedFd> for SerialPort
source§impl From<SerialPort> for OwnedFd
impl From<SerialPort> for OwnedFd
source§fn from(value: SerialPort) -> Self
fn from(value: SerialPort) -> Self
source§impl FromRawFd for SerialPort
impl FromRawFd for SerialPort
source§unsafe fn from_raw_fd(fd: RawFd) -> Self
unsafe fn from_raw_fd(fd: RawFd) -> Self
Self from the given raw file
descriptor. Read moresource§impl IntoRawFd for SerialPort
impl IntoRawFd for SerialPort
source§fn into_raw_fd(self) -> RawFd
fn into_raw_fd(self) -> RawFd
source§impl Read for SerialPort
impl Read for SerialPort
source§fn read(&mut self, buf: &mut [u8]) -> Result<usize>
fn read(&mut self, buf: &mut [u8]) -> Result<usize>
source§fn read_vectored(&mut self, buf: &mut [IoSliceMut<'_>]) -> Result<usize>
fn read_vectored(&mut self, buf: &mut [IoSliceMut<'_>]) -> Result<usize>
read, except that it reads into a slice of buffers. Read moresource§fn is_read_vectored(&self) -> bool
fn is_read_vectored(&self) -> bool
can_vector)1.0.0 · source§fn read_to_end(&mut self, buf: &mut Vec<u8>) -> Result<usize, Error>
fn read_to_end(&mut self, buf: &mut Vec<u8>) -> Result<usize, Error>
buf. Read more1.0.0 · source§fn read_to_string(&mut self, buf: &mut String) -> Result<usize, Error>
fn read_to_string(&mut self, buf: &mut String) -> Result<usize, Error>
buf. Read more1.6.0 · source§fn read_exact(&mut self, buf: &mut [u8]) -> Result<(), Error>
fn read_exact(&mut self, buf: &mut [u8]) -> Result<(), Error>
buf. Read moresource§fn read_buf(&mut self, buf: BorrowedCursor<'_>) -> Result<(), Error>
fn read_buf(&mut self, buf: BorrowedCursor<'_>) -> Result<(), Error>
read_buf)source§fn read_buf_exact(&mut self, cursor: BorrowedCursor<'_>) -> Result<(), Error>
fn read_buf_exact(&mut self, cursor: BorrowedCursor<'_>) -> Result<(), Error>
read_buf)cursor. Read more1.0.0 · source§fn by_ref(&mut self) -> &mut Selfwhere
Self: Sized,
fn by_ref(&mut self) -> &mut Selfwhere
Self: Sized,
Read. Read moresource§impl Write for SerialPort
impl Write for SerialPort
source§fn write(&mut self, buf: &[u8]) -> Result<usize>
fn write(&mut self, buf: &[u8]) -> Result<usize>
source§fn flush(&mut self) -> Result<()>
fn flush(&mut self) -> Result<()>
source§fn is_write_vectored(&self) -> bool
fn is_write_vectored(&self) -> bool
can_vector)1.0.0 · source§fn write_all(&mut self, buf: &[u8]) -> Result<(), Error>
fn write_all(&mut self, buf: &[u8]) -> Result<(), Error>
source§fn write_all_vectored(&mut self, bufs: &mut [IoSlice<'_>]) -> Result<(), Error>
fn write_all_vectored(&mut self, bufs: &mut [IoSlice<'_>]) -> Result<(), Error>
write_all_vectored)