can-isotp-queue 0.1.0

Queue/actor adapter for split ISO-TP TX/RX endpoints across async runtimes
Documentation 
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

# can-isotp-queue

`can-isotp-queue` provides queue/actor adapters for `can-isotp-interface` async endpoints.

It is intended for designs where a single concrete ISO-TP node/socket must be owned by one task,
while higher layers need split TX and RX handles that implement:

- `IsoTpAsyncEndpoint`
- `IsoTpAsyncEndpointRecvInto`

## Features

- `tokio`: tokio `mpsc`/`oneshot` adapter.
- `embassy-07`: `embassy-sync` 0.7 channel-based adapter for static/no-alloc use.

## Tokio Usage

```rust,ignore
use core::time::Duration;
use can_isotp_queue::{ActorConfig, NoopHooks};
use can_isotp_queue::tokio::{make_endpoints, run_actor};

let (tx_node, rx_node, actor_ports) = make_endpoints::<MyErr>(2048, 8, 8);
let cfg = ActorConfig::new(Duration::from_micros(50), 8, None);
tokio::spawn(run_actor(my_socket_node, actor_ports, cfg, NoopHooks));
```

## Embassy 0.7 Usage

```rust,ignore
use core::time::Duration;
use can_isotp_queue::{ActorConfig, NoopHooks};
use can_isotp_queue::embassy07::{QueueResources, run_actor};
use embassy_sync::blocking_mutex::raw::CriticalSectionRawMutex;

static RES: QueueResources<CriticalSectionRawMutex, MyErr, 1024, 8, 1, 8> = QueueResources::new();

let (tx_node, rx_node) = RES.split_endpoints();
let cfg = ActorConfig::new(Duration::from_micros(50), 8, None);
// Spawn actor task with `run_actor(node, &RES, cfg, NoopHooks)`.
```

## Reply-to Override

Set `ActorConfig::fixed_reply_to` to force received metadata reply-to when a backend cannot
reliably report source address metadata.

## Source Filtering

Set `ActorConfig::allowed_reply_from` (or use `with_allowed_reply_from`) to drop received frames
whose ISO-TP source does not match the expected peer address.