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

#576 in Asynchronous

Download history 878/week @ 2024-12-01 841/week @ 2024-12-08 982/week @ 2024-12-15 145/week @ 2024-12-22 231/week @ 2024-12-29 690/week @ 2025-01-05 667/week @ 2025-01-12 531/week @ 2025-01-19 541/week @ 2025-01-26 664/week @ 2025-02-02 558/week @ 2025-02-09 601/week @ 2025-02-16 914/week @ 2025-02-23 665/week @ 2025-03-02 782/week @ 2025-03-09 538/week @ 2025-03-16

2,931 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–18MB
~181K SLoC