#socket-can #tokio #sockets #stream-ext

tokio-socketcan

Asynchronous Linux SocketCAN sockets with tokio

7 releases

0.3.1 Nov 17, 2021
0.3.0 Feb 10, 2021
0.2.0 Nov 12, 2020
0.1.3 Feb 23, 2019
0.1.1 Jan 10, 2019

#539 in Hardware support

Download history 904/week @ 2024-12-17 82/week @ 2024-12-24 351/week @ 2024-12-31 666/week @ 2025-01-07 741/week @ 2025-01-14 422/week @ 2025-01-21 572/week @ 2025-01-28 613/week @ 2025-02-04 565/week @ 2025-02-11 729/week @ 2025-02-18 824/week @ 2025-02-25 748/week @ 2025-03-04 671/week @ 2025-03-11 552/week @ 2025-03-18 529/week @ 2025-03-25 409/week @ 2025-04-01

2,344 downloads per month
Used in 4 crates

MIT license

14KB
201 lines

crates.io badge documentation Continuous integration

tokio-socketcan

SocketCAN support for tokio based on the socketcan crate.

Example echo server

use futures_util::stream::StreamExt;
use tokio_socketcan::{CANSocket, Error};

#[tokio::main]
async fn main() -> Result<(), Error> {
    let mut socket_rx = CANSocket::open("vcan0")?;
    let socket_tx = CANSocket::open("vcan0")?;
    while let Some(Ok(frame)) = socket_rx.next().await {
        socket_tx.write_frame(frame)?.await?;
    }
    Ok(())
}

Testing

Integrating the test into a CI system is non-trivial as it relies on a vcan0 virtual can device existing. Adding one to most linux systems is pretty easy with root access but attaching a vcan device to a container for CI seems difficult to find support for.

To run the tests locally, though, setup should be simple:

sudo modprobe vcan
sudo ip link add vcan0 type vcan
sudo ip link set vcan0 up
cargo test

Dependencies

~6–15MB
~177K SLoC