can-isotp-interface 0.1.0

ISO-TP transport traits shared across user-space and kernel backends
Documentation
  • Coverage
  • 100%
    44 out of 44 items documented0 out of 22 items with examples
  • Size
  • Source code size: 13.01 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 2.8 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 17s Average build duration of successful builds.
  • all releases: 17s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • conroy-cheers/can-isotp-interface
    0 0 0
  • crates.io
  • Dependencies
    • —
  • Versions
  • Owners
  • conroy-cheers

can-isotp-interface

can-isotp-interface defines dependency-light Rust traits for addressed ISO-TP transports used by UDS-style communication.

The crate provides shared sync and async endpoint traits for sending payloads to a peer address, sending functional requests, and receiving payloads together with reply metadata. It also includes the common status and error types needed around those operations, plus an optional trait for backends that support runtime receive-side flow-control configuration.

It is intended as a small interface crate that can be implemented by different backends while presenting the same transport surface to higher-level diagnostic code. The crate is no_std and is designed to work as the common boundary between user-space and kernel-backed ISO-TP implementations.