1 2 3 4 5 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 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217
// socketcan/src/lib.rs
//
// The main lib file for the Rust SocketCAN library.
//
// This file is part of the Rust 'socketcan-rs' library.
//
// Licensed under the MIT license:
// <LICENSE or http://opensource.org/licenses/MIT>
// This file may not be copied, modified, or distributed except according
// to those terms.
//! SocketCAN support.
//!
//! The Linux kernel supports using CAN-devices through a network-like API
//! (see <https://www.kernel.org/doc/Documentation/networking/can.txt>). This
//! crate allows easy access to this functionality without having to wrestle
//! libc calls.
//!
//! # An introduction to CAN
//!
//! The CAN bus was originally designed to allow microcontrollers inside a
//! vehicle to communicate over a single shared bus. Messages called
//! *frames* are multicast to all devices on the bus.
//!
//! Every frame consists of an ID and a payload of up to 8 bytes. If two
//! devices attempt to send a frame at the same time, the device with the
//! higher ID will notice the conflict, stop sending and reattempt to sent its
//! frame in the next time slot. This means that the lower the ID, the higher
//! the priority. Since most devices have a limited buffer for outgoing frames,
//! a single device with a high priority (== low ID) can block communication
//! on that bus by sending messages too fast.
//!
//! The Linux socketcan subsystem makes the CAN bus available as a regular
//! networking device. Opening an network interface allows receiving all CAN
//! messages received on it. A device CAN be opened multiple times, every
//! client will receive all CAN frames simultaneously.
//!
//! Similarly, CAN frames can be sent to the bus by multiple client
//! simultaneously as well.
//!
//! # Hardware and more information
//!
//! More information on CAN [can be found on Wikipedia](). When not running on
//! an embedded platform with already integrated CAN components,
//! [Thomas Fischl's USBtin](http://www.fischl.de/usbtin/) (see
//! [section 2.4](http://www.fischl.de/usbtin/#socketcan)) is one of many ways
//! to get started.
//!
//! # RawFd
//!
//! Raw access to the underlying file descriptor and construction through
//! is available through the `AsRawFd`, `IntoRawFd` and `FromRawFd`
//! implementations.
//!
//! # Crate Features
//!
//! ### Default
//!
//! * **netlink** -
//! Whether to include programmable CAN interface configuration capabilities
//! based on netlink kernel communications. This brings in the
//! [neli](https://docs.rs/neli/latest/neli/) library and its dependencies.
//!
//! * **dump** -
//! Whether to include candump parsing capabilities.
//!
//! ### Non-default
//!
//! * **utils** -
//! Whether to build command-line utilities. This brings in additional
//! dependencies like [anyhow](https://docs.rs/anyhow/latest/anyhow/) and
//! [clap](https://docs.rs/clap/latest/clap/)
//!
//! * **tokio** -
//! Include support for async/await using [tokio](https://crates.io/crates/tokio).
//!
//! * **async-io** -
//! Include support for async/await using [async-io](https://crates.io/crates/async-io)
//! This will work with any runtime that uses _async_io_, including
//! [async-std](https://crates.io/crates/async-std) and [smol](https://crates.io/crates/smol).
//!
//! * **async-std** -
//! Include support for async/await using [async-io](https://crates.io/crates/async-io)
//! with a submodule aliased for [async-std](https://crates.io/crates/async-std) and examples
//! for that runtime.
//!
//! * **smol** -
//! Include support for async/await using [async-io](https://crates.io/crates/async-io)
//! with a submodule aliased for [smol](https://crates.io/crates/smol) and examples
//! for that runtime.
//!
// clippy: do not warn about things like "SocketCAN" inside the docs
#![allow(clippy::doc_markdown)]
// Some lints
#![deny(
missing_docs,
missing_copy_implementations,
missing_debug_implementations,
unstable_features,
unused_import_braces,
unused_qualifications,
unsafe_op_in_unsafe_fn
)]
use std::io::ErrorKind;
// Re-export the embedded_can crate so that applications can rely on
// finding the same version we use.
pub use embedded_can::{
self, blocking::Can as BlockingCan, nb::Can as NonBlockingCan, ExtendedId,
Frame as EmbeddedFrame, Id, StandardId,
};
pub mod errors;
pub use errors::{CanError, CanErrorDecodingFailure, ConstructionError, Error, Result};
pub mod frame;
pub use frame::{
CanAnyFrame, CanDataFrame, CanErrorFrame, CanFdFrame, CanFrame, CanRemoteFrame, Frame,
};
#[cfg(feature = "dump")]
pub mod dump;
pub mod socket;
pub use socket::{CanAddr, CanFdSocket, CanFilter, CanSocket, ShouldRetry, Socket, SocketOptions};
#[cfg(feature = "netlink")]
pub mod nl;
#[cfg(feature = "netlink")]
pub use nl::{CanCtrlMode, CanInterface};
/// Optional tokio support
#[cfg(feature = "tokio")]
pub mod tokio;
/// Optional support for async-io-based async runtimes, like async-std and smol.
#[cfg(any(feature = "async-io", feature = "async-std", feature = "smol"))]
pub mod async_io;
/// Using the specific definition for 'smol', just re-export the async_io module.
#[cfg(feature = "smol")]
pub mod smol {
pub use crate::async_io::*;
}
/// Using the specific definition for 'async_std', just re-export the async_io module.
#[cfg(feature = "async-std")]
pub mod async_std {
pub use crate::async_io::*;
}
// ===== embedded_can I/O traits =====
impl embedded_can::blocking::Can for CanSocket {
type Frame = CanFrame;
type Error = Error;
/// Blocking call to receive the next frame from the bus.
///
/// This block and wait for the next frame to be received from the bus.
/// If an error frame is received, it will be converted to a `CanError`
/// and returned as an error.
fn receive(&mut self) -> Result<Self::Frame> {
use CanFrame::*;
match self.read_frame() {
Ok(Error(frame)) => Err(frame.into_error().into()),
Ok(frame) => Ok(frame),
Err(e) => Err(e.into()),
}
}
/// Blocking transmit of a frame to the bus.
fn transmit(&mut self, frame: &Self::Frame) -> Result<()> {
self.write_frame_insist(frame).map_err(|err| err.into())
}
}
impl embedded_can::nb::Can for CanSocket {
type Frame = CanFrame;
type Error = Error;
/// Non-blocking call to receive the next frame from the bus.
///
/// If an error frame is received, it will be converted to a `CanError`
/// and returned as an error.
/// If no frame is available, it returns a `WouldBlck` error.
fn receive(&mut self) -> nb::Result<Self::Frame, Self::Error> {
use CanFrame::*;
match self.read_frame() {
Ok(Data(frame)) => Ok(Data(frame)),
Ok(Remote(frame)) => Ok(Remote(frame)),
Ok(Error(frame)) => Err(crate::Error::from(frame.into_error()).into()),
Err(err) => Err(match err.kind() {
ErrorKind::WouldBlock => nb::Error::WouldBlock,
_ => crate::Error::from(err).into(),
}),
}
}
/// Non-blocking transmit of a frame to the bus.
fn transmit(&mut self, frame: &Self::Frame) -> nb::Result<Option<Self::Frame>, Self::Error> {
match self.write_frame(frame) {
Ok(_) => Ok(None),
Err(err) => {
match err.kind() {
ErrorKind::WouldBlock => Err(nb::Error::WouldBlock),
// TODO: How to indicate buffer is full?
// ErrorKind::StorageFull => Ok(frame),
_ => Err(crate::Error::from(err).into()),
}
}
}
}
}