MATLAB Vehicle Network Communication
Prerequisites
- MATLAB R2021a or later
- Vehicle Network Toolbox installed (
ver('vnt') to verify)
- For physical hardware: vendor-specific drivers installed (Vector CANlib, Kvaser CANlib, NI-XNET, PEAK PCAN driver)
- For testing without hardware: MathWorks Virtual channels are always available
Overview
Guide Claude through helping users establish vehicle network communication using MATLAB Vehicle Network Toolbox. This skill covers the full workflow from hardware discovery to message exchange across all supported protocols and vendors.
Implemented protocols:
- CAN / CAN FD — fully documented
Planned protocols (architecture ready, not yet documented):
- J1939 — parameter groups, transport protocol, address claiming
- XCP — measurement, calibration, A2L file handling
- Additional protocols as VNT adds support
When to Use
- User wants to send/receive messages on a vehicle network bus in MATLAB
- User is setting up a communication test bench or loopback verification
- User asks about Vehicle Network Toolbox channel configuration
- User encounters channel errors (initialization access, bus speed, no acknowledgment)
- User wants to filter, decode, or analyze vehicle network messages
- User asks which hardware works on their platform
- User wants passive bus monitoring without affecting traffic
- User needs to encode/decode signal data from messages
When NOT to Use
- User wants to log/replay BLF files without live communication — use a BLF logging skill
- User is building Simulink vehicle network blocks — use Simulink-specific skills
- User needs CAN database file (DBC/LDF/A2L) creation or editing — this skill covers using existing files only
- User is working with a protocol not yet documented in this skill (check protocol sections below)
Protocol Router
Use this decision tree to identify which protocol the user needs:
| User's Goal |
Protocol |
Reference Section |
| Send/receive CAN or CAN FD messages |
CAN/CAN FD |
references/can/ |
| Work with SAE J1939 parameter groups |
J1939 |
Not yet documented |
| ECU measurement or calibration via XCP/CCP |
XCP |
Not yet documented |
| General hardware discovery (any protocol) |
Shared |
references/shared/ |
If the user asks about a protocol not yet documented, inform them which protocols are currently covered and offer to help with those.
Shared Concepts (All Protocols)
Hardware Discovery
t = canChannelList; % CAN/CAN FD/J1939 devices
All VNT protocols share the same hardware discovery mechanism. See references/shared/hardware-discovery.md.
Channel Lifecycle
All protocols follow the same lifecycle pattern:
Create Channel → Configure → Start → Operate → Stop/Cleanup
Key rules:
- Configuration (bus speed, filters) must happen BEFORE
start
clear ch releases the channel (equivalent to stop + destroy)
- Use
onCleanup(@() stop(ch)) for error-safe cleanup
- Running channels hold InitializationAccess — blocking new channel creation
See references/shared/channel-lifecycle.md.
Vendor / Platform Matrix
| Vendor |
Windows |
Linux |
Notes |
| Vector |
Yes |
No |
Virtual channels if driver installed |
| NI |
Yes |
No |
No channel index in constructor |
| Kvaser |
Yes |
Yes |
Restart MATLAB after connecting hardware |
| PEAK-System |
Yes |
Yes |
10-arg clock-based configBusSpeed |
| SocketCAN |
No |
Yes |
Configure speed at OS level via ip link |
| MathWorks Virtual |
Yes |
Yes |
Always available, no driver needed |
CAN / CAN FD
Troubleshooting Gate
If the user reports a CAN/CAN FD problem — "not working", "trouble", "error", "can't connect", "no messages", hardware not detected, or any communication failure — you MUST do one of the following:
Domain-knowledge question ("why does X cause Y", "what's the maximum stub length for CAN FD", "explain bit rate switching") — answer from references/can/troubleshooting/l1-domain-knowledge.md without running diagnostics.
Actionable problem requiring diagnosis — Load references/can/troubleshooting/diagnostic-workflow.md BEFORE responding. Follow its Entry-Point Routing to select the correct starting step. Do NOT diagnose from this file. The tables, pitfalls, and patterns below are reference material for healthy operation — they are NOT a diagnostic procedure. Improvising from them produces wall-of-text responses with multiple guesses instead of structured one-question-at-a-time triage.
Core Workflow
digraph can_workflow {
rankdir=TB;
node [shape=box];
discover [label="1. Discover Hardware\ncanChannelList"];
decide [label="CAN Classic or CAN FD?" shape=diamond];
create_classic [label="2a. Create Channel\ncanChannel(vendor, device, ch)"];
create_fd [label="2b. Create FD Channel\ncanChannel(..., ProtocolMode='CAN FD')\nor canFDChannel(...)"];
config [label="3. Configure Bus Speed\nconfigBusSpeed (vendor-specific syntax)"];
start [label="4. Start Channel\nstart(ch)"];
operate [label="5. Transmit / Receive\ntransmit, receive\ntransmitPeriodic, transmitEvent, replay"];
cleanup [label="6. Cleanup\nstop(ch) or clear ch"];
discover -> decide;
decide -> create_classic [label="Classic"];
decide -> create_fd [label="CAN FD"];
create_classic -> config;
create_fd -> config;
config -> start;
start -> operate;
operate -> cleanup;
}
Post-Transmit Verification (MANDATORY)
After ANY transmit, verify the bus accepted the frame before reporting success:
pause(0.5);
fprintf('TEC=%d REC=%d BusStatus=%s\n', ch.TransmitErrorCount, ch.ReceiveErrorCount, ch.BusStatus);
| Result |
Action |
| TEC=0, REC=0, ErrorActive |
Healthy — report success |
| TEC>0 OR REC>0 OR not ErrorActive |
Unhealthy — report counters to user, route to diagnostic workflow Step 0.5. Follow diagnostic Interaction Rules (one question at a time). |
Never claim "sent successfully" from transmit returning without error. It is non-blocking and returns immediately regardless of bus state. When routing to diagnostics, do NOT list multiple possible causes — let Step 0.5 identify the root cause and ask one targeted question.
CAN Classic vs CAN FD Decision
| Aspect |
CAN Classic |
CAN FD |
| Max payload |
8 bytes |
64 bytes |
| Message constructor |
canMessage(id, ext, dlc) |
canFDMessage(id, ext, dlc) or canMessage(..., ProtocolMode="CAN FD") |
| Channel creation |
canChannel(vendor, device, ch) |
Add 'ProtocolMode', 'CAN FD' or use canFDChannel |
| Bus speed config |
Single speed |
Arbitration + Data phase (vendor-specific syntax) |
receive output |
Objects or timetable |
Always timetable |
| Valid DLCs |
0–8 |
0, 8, 12, 16, 20, 24, 32, 48, 64 |
Critical Patterns (Non-Obvious API Behavior)
These patterns are where the API behaves differently than expected. Follow these exactly.
attachDatabase operates on MESSAGES, not channels
% WRONG — will error
attachDatabase(ch, db);
ch.Database = db; % only valid for name-based filterAllowOnly
% CORRECT — attach to received message object
rxMsg = receive(ch, 1);
attachDatabase(rxMsg, db);
speed = rxMsg.Signals.EngineSpeed;
transmitPeriodic + pack for live signal updates
% WRONG — manual loop blocks MATLAB, timing is inaccurate
while running
pack(msg, newValue, 0, 16, 'LittleEndian');
transmit(ch, msg);
pause(0.1);
end
% CORRECT — hardware-timed, non-blocking
transmitPeriodic(ch, msg, 'On', 0.1);
start(ch);
pack(msg, newValue, 0, 16, 'LittleEndian'); % next cycle sends updated data
filterAllowOnly REQUIRES type argument for numeric IDs
% WRONG — errors with "Expected NAME to be one of these types: char, cell"
filterAllowOnly(ch, [0x180 0x181]);
% CORRECT — must specify 'Standard' or 'Extended'
filterAllowOnly(ch, [0x180 0x181], 'Standard');
filterAllowOnly(ch, [0x18FEF100], 'Extended');
CAN FD configBusSpeed is vendor-specific
% MathWorks Virtual / NI — simple 3-arg form works
configBusSpeed(ch, 500000, 2000000);
% Vector / Kvaser — REQUIRES 9-arg advanced timing form
configBusSpeed(ch, 500000, 2, 6, 3, 2000000, 2, 6, 3);
% PEAK-System — REQUIRES 10-arg clock-based form
configBusSpeed(ch, 20, 5, 1, 2, 1, 2, 1, 3, 1);
CAN FD receive ALWAYS returns timetable
% CAN FD channels ignore OutputFormat — always timetable
msgs = receive(fdCh, Inf); % returns timetable
msgs.ID % numeric vector of IDs
msgs.Data{1} % uint8 vector for first message
% WRONG: msgs(1).Data, msgs.Data(1) — these error on timetable
transmitEvent fires on ANY .Data write (including pack)
transmitEvent(ch, msg, 'On');
start(ch);
pack(msg, value, 0, 16, 'LittleEndian'); % this auto-transmits!
% No explicit transmit() call needed — pack triggers it
Common Pitfalls
| Pitfall |
Symptom |
Fix |
| Stale channel object |
"lacks initialization access" |
clear the variable or stop prior channel |
canMessage for FD payload |
"DATALENGTH must be <= 8" |
Use canFDMessage or add ProtocolMode="CAN FD" |
| No acknowledging node |
Transmit retries continuously |
Ensure another node/channel is started on the bus |
| Claiming success without checking counters |
User believes data sent; bus is ErrorPassive |
ALWAYS check TEC/REC/BusStatus after transmit |
| Bus speed mismatch |
Transmit succeeds, receive empty |
All nodes must share same speed |
configBusSpeed after start |
Error |
Must configure while channel is offline |
| Reusing variable |
Error on creation |
clear variable before creating new channel |
configBusSpeed on SocketCAN |
Not supported |
Configure speed at OS level via ip link |
| CAN FD on PEAK-System Linux |
Self-receive not supported |
Use SocketCAN as workaround |
unpack on timetable |
"Incorrect number or types of inputs" |
CAN FD always returns timetable; use typecast(data(1:2), 'int16') on raw bytes |
CAN References
Detailed API documentation (load on demand):
- references/can/channel-creation.md —
canChannel, canFDChannel, vendor-specific syntax
- references/can/bus-speed-config.md —
configBusSpeed, vendor-specific argument counts
- references/can/message-creation.md —
canMessage, canFDMessage, valid FD DLCs
- references/can/transmit.md —
transmit, transmitPeriodic, transmitEvent, replay
- references/can/receive.md —
receive, SilentMode, timetable output, FIFO behavior
- references/can/filters.md —
filterAllowOnly, filterBlockAll, filterAllowAll
- references/can/database.md —
canDatabase, attachDatabase, signal-level decode/encode
- references/can/pack-unpack.md —
pack, unpack, signal extraction, byte-order
- references/can/message-extraction.md —
extractAll, extractRecent, extractTime, discard
CAN Troubleshooting
See Troubleshooting Gate at the top of this section. Also route to diagnostics when the agent observes unhealthy bus state (TEC/REC > 0, BusStatus not ErrorActive) during any operation — including after transmit verification.
- references/can/troubleshooting/diagnostic-workflow.md — Full diagnostic procedure (Phase 0 automation, L1 physical, L2 traffic analysis)
- references/can/troubleshooting/script-interfaces.md — Function signatures, arguments, and outputs for all diagnostic/analysis scripts
Shared References
- references/shared/hardware-discovery.md —
canChannelList, platform constraints
- references/shared/channel-lifecycle.md —
start, stop, onCleanup, channel release
- references/shared/limitations.md — Vendor/platform-specific constraints
Copyright 2026 The MathWorks, Inc.
1---2name: matlab-use-vehicle-network3description: Use when setting up vehicle network communication in MATLAB using Vehicle Network Toolbox. Covers CAN/CAN FD (fully implemented), with architecture for J1939, XCP, and future protocols. Handles hardware discovery, channel creation, bus configuration, message exchange, signal encoding/decoding, and analysis across all supported vendors. (Vector, Kvaser, PEAK-System, NI, SocketCAN, MathWorks Virtual).4license: https://www.mathworks.com/content/dam/mathworks/license/pmrl/license.md5metadata:6 source: https://skillmd.com/skills/gabrielmoreira/matlab-use-vehicle-network7 author: MathWorks8 version: "2.1"9---1011# MATLAB Vehicle Network Communication1213## Prerequisites1415- MATLAB R2021a or later16- Vehicle Network Toolbox installed (`ver('vnt')` to verify)17- For physical hardware: vendor-specific drivers installed (Vector CANlib, Kvaser CANlib, NI-XNET, PEAK PCAN driver)18- For testing without hardware: MathWorks Virtual channels are always available1920## Overview2122Guide Claude through helping users establish vehicle network communication using MATLAB Vehicle Network Toolbox. This skill covers the full workflow from hardware discovery to message exchange across all supported protocols and vendors.2324**Implemented protocols:**25- CAN / CAN FD — fully documented2627**Planned protocols (architecture ready, not yet documented):**28- J1939 — parameter groups, transport protocol, address claiming29- XCP — measurement, calibration, A2L file handling30- Additional protocols as VNT adds support3132## When to Use3334- User wants to send/receive messages on a vehicle network bus in MATLAB35- User is setting up a communication test bench or loopback verification36- User asks about Vehicle Network Toolbox channel configuration37- User encounters channel errors (initialization access, bus speed, no acknowledgment)38- User wants to filter, decode, or analyze vehicle network messages39- User asks which hardware works on their platform40- User wants passive bus monitoring without affecting traffic41- User needs to encode/decode signal data from messages4243## When NOT to Use4445- User wants to log/replay BLF files without live communication — use a BLF logging skill46- User is building Simulink vehicle network blocks — use Simulink-specific skills47- User needs CAN database file (DBC/LDF/A2L) creation or editing — this skill covers using existing files only48- User is working with a protocol not yet documented in this skill (check protocol sections below)4950## Protocol Router5152Use this decision tree to identify which protocol the user needs:5354| User's Goal | Protocol | Reference Section |55|-------------|----------|-------------------|56| Send/receive CAN or CAN FD messages | CAN/CAN FD | `references/can/` |57| Work with SAE J1939 parameter groups | J1939 | *Not yet documented* |58| ECU measurement or calibration via XCP/CCP | XCP | *Not yet documented* |59| General hardware discovery (any protocol) | Shared | `references/shared/` |6061If the user asks about a protocol not yet documented, inform them which protocols are currently covered and offer to help with those.6263## Shared Concepts (All Protocols)6465### Hardware Discovery6667```matlab68t = canChannelList; % CAN/CAN FD/J1939 devices69```7071All VNT protocols share the same hardware discovery mechanism. See [references/shared/hardware-discovery.md](references/shared/hardware-discovery.md).7273### Channel Lifecycle7475All protocols follow the same lifecycle pattern:7677```78Create Channel → Configure → Start → Operate → Stop/Cleanup79```8081Key rules:82- Configuration (bus speed, filters) must happen BEFORE `start`83- `clear ch` releases the channel (equivalent to stop + destroy)84- Use `onCleanup(@() stop(ch))` for error-safe cleanup85- Running channels hold InitializationAccess — blocking new channel creation8687See [references/shared/channel-lifecycle.md](references/shared/channel-lifecycle.md).8889### Vendor / Platform Matrix9091| Vendor | Windows | Linux | Notes |92|--------|:-------:|:-----:|-------|93| Vector | Yes | No | Virtual channels if driver installed |94| NI | Yes | No | No channel index in constructor |95| Kvaser | Yes | Yes | Restart MATLAB after connecting hardware |96| PEAK-System | Yes | Yes | 10-arg clock-based configBusSpeed |97| SocketCAN | No | Yes | Configure speed at OS level via `ip link` |98| MathWorks Virtual | Yes | Yes | Always available, no driver needed |99100---101102## CAN / CAN FD103104### Troubleshooting Gate105106**If the user reports a CAN/CAN FD problem** — "not working", "trouble", "error", "can't connect", "no messages", hardware not detected, or any communication failure — you MUST do one of the following:1071081. **Domain-knowledge question** ("why does X cause Y", "what's the maximum stub length for CAN FD", "explain bit rate switching") — answer from [references/can/troubleshooting/l1-domain-knowledge.md](references/can/troubleshooting/l1-domain-knowledge.md) without running diagnostics.1091102. **Actionable problem requiring diagnosis** — **Load** [references/can/troubleshooting/diagnostic-workflow.md](references/can/troubleshooting/diagnostic-workflow.md) BEFORE responding. **Follow** its Entry-Point Routing to select the correct starting step. **Do NOT diagnose from this file.** The tables, pitfalls, and patterns below are reference material for healthy operation — they are NOT a diagnostic procedure. Improvising from them produces wall-of-text responses with multiple guesses instead of structured one-question-at-a-time triage.111112### Core Workflow113114```dot115digraph can_workflow {116 rankdir=TB;117 node [shape=box];118119 discover [label="1. Discover Hardware\ncanChannelList"];120 decide [label="CAN Classic or CAN FD?" shape=diamond];121 create_classic [label="2a. Create Channel\ncanChannel(vendor, device, ch)"];122 create_fd [label="2b. Create FD Channel\ncanChannel(..., ProtocolMode='CAN FD')\nor canFDChannel(...)"];123 config [label="3. Configure Bus Speed\nconfigBusSpeed (vendor-specific syntax)"];124 start [label="4. Start Channel\nstart(ch)"];125 operate [label="5. Transmit / Receive\ntransmit, receive\ntransmitPeriodic, transmitEvent, replay"];126 cleanup [label="6. Cleanup\nstop(ch) or clear ch"];127128 discover -> decide;129 decide -> create_classic [label="Classic"];130 decide -> create_fd [label="CAN FD"];131 create_classic -> config;132 create_fd -> config;133 config -> start;134 start -> operate;135 operate -> cleanup;136}137```138139### Post-Transmit Verification (MANDATORY)140141After ANY transmit, verify the bus accepted the frame before reporting success:142143```matlab144pause(0.5);145fprintf('TEC=%d REC=%d BusStatus=%s\n', ch.TransmitErrorCount, ch.ReceiveErrorCount, ch.BusStatus);146```147148| Result | Action |149|--------|--------|150| TEC=0, REC=0, ErrorActive | Healthy — report success |151| TEC>0 OR REC>0 OR not ErrorActive | Unhealthy — report counters to user, route to [diagnostic workflow Step 0.5](references/can/troubleshooting/diagnostic-workflow.md). Follow diagnostic Interaction Rules (one question at a time). |152153**Never claim "sent successfully" from `transmit` returning without error.** It is non-blocking and returns immediately regardless of bus state. When routing to diagnostics, do NOT list multiple possible causes — let Step 0.5 identify the root cause and ask one targeted question.154155### CAN Classic vs CAN FD Decision156157| Aspect | CAN Classic | CAN FD |158|--------|-------------|--------|159| Max payload | 8 bytes | 64 bytes |160| Message constructor | `canMessage(id, ext, dlc)` | `canFDMessage(id, ext, dlc)` or `canMessage(..., ProtocolMode="CAN FD")` |161| Channel creation | `canChannel(vendor, device, ch)` | Add `'ProtocolMode', 'CAN FD'` or use `canFDChannel` |162| Bus speed config | Single speed | Arbitration + Data phase (vendor-specific syntax) |163| `receive` output | Objects or timetable | Always timetable |164| Valid DLCs | 0–8 | 0, 8, 12, 16, 20, 24, 32, 48, 64 |165166### Critical Patterns (Non-Obvious API Behavior)167168These patterns are where the API behaves differently than expected. Follow these exactly.169170#### attachDatabase operates on MESSAGES, not channels171172```matlab173% WRONG — will error174attachDatabase(ch, db);175ch.Database = db; % only valid for name-based filterAllowOnly176177% CORRECT — attach to received message object178rxMsg = receive(ch, 1);179attachDatabase(rxMsg, db);180speed = rxMsg.Signals.EngineSpeed;181```182183#### transmitPeriodic + pack for live signal updates184185```matlab186% WRONG — manual loop blocks MATLAB, timing is inaccurate187while running188 pack(msg, newValue, 0, 16, 'LittleEndian');189 transmit(ch, msg);190 pause(0.1);191end192193% CORRECT — hardware-timed, non-blocking194transmitPeriodic(ch, msg, 'On', 0.1);195start(ch);196pack(msg, newValue, 0, 16, 'LittleEndian'); % next cycle sends updated data197```198199#### filterAllowOnly REQUIRES type argument for numeric IDs200201```matlab202% WRONG — errors with "Expected NAME to be one of these types: char, cell"203filterAllowOnly(ch, [0x180 0x181]);204205% CORRECT — must specify 'Standard' or 'Extended'206filterAllowOnly(ch, [0x180 0x181], 'Standard');207filterAllowOnly(ch, [0x18FEF100], 'Extended');208```209210#### CAN FD configBusSpeed is vendor-specific211212```matlab213% MathWorks Virtual / NI — simple 3-arg form works214configBusSpeed(ch, 500000, 2000000);215216% Vector / Kvaser — REQUIRES 9-arg advanced timing form217configBusSpeed(ch, 500000, 2, 6, 3, 2000000, 2, 6, 3);218219% PEAK-System — REQUIRES 10-arg clock-based form220configBusSpeed(ch, 20, 5, 1, 2, 1, 2, 1, 3, 1);221```222223#### CAN FD receive ALWAYS returns timetable224225```matlab226% CAN FD channels ignore OutputFormat — always timetable227msgs = receive(fdCh, Inf); % returns timetable228msgs.ID % numeric vector of IDs229msgs.Data{1} % uint8 vector for first message230% WRONG: msgs(1).Data, msgs.Data(1) — these error on timetable231```232233#### transmitEvent fires on ANY .Data write (including pack)234235```matlab236transmitEvent(ch, msg, 'On');237start(ch);238pack(msg, value, 0, 16, 'LittleEndian'); % this auto-transmits!239% No explicit transmit() call needed — pack triggers it240```241242### Common Pitfalls243244| Pitfall | Symptom | Fix |245|---------|---------|-----|246| Stale channel object | "lacks initialization access" | `clear` the variable or `stop` prior channel |247| `canMessage` for FD payload | "DATALENGTH must be <= 8" | Use `canFDMessage` or add `ProtocolMode="CAN FD"` |248| No acknowledging node | Transmit retries continuously | Ensure another node/channel is started on the bus |249| Claiming success without checking counters | User believes data sent; bus is ErrorPassive | ALWAYS check TEC/REC/BusStatus after transmit |250| Bus speed mismatch | Transmit succeeds, receive empty | All nodes must share same speed |251| `configBusSpeed` after `start` | Error | Must configure while channel is offline |252| Reusing variable | Error on creation | `clear` variable before creating new channel |253| `configBusSpeed` on SocketCAN | Not supported | Configure speed at OS level via `ip link` |254| CAN FD on PEAK-System Linux | Self-receive not supported | Use SocketCAN as workaround |255| `unpack` on timetable | "Incorrect number or types of inputs" | CAN FD always returns timetable; use `typecast(data(1:2), 'int16')` on raw bytes |256257### CAN References258259Detailed API documentation (load on demand):260- [references/can/channel-creation.md](references/can/channel-creation.md) — `canChannel`, `canFDChannel`, vendor-specific syntax261- [references/can/bus-speed-config.md](references/can/bus-speed-config.md) — `configBusSpeed`, vendor-specific argument counts262- [references/can/message-creation.md](references/can/message-creation.md) — `canMessage`, `canFDMessage`, valid FD DLCs263- [references/can/transmit.md](references/can/transmit.md) — `transmit`, `transmitPeriodic`, `transmitEvent`, `replay`264- [references/can/receive.md](references/can/receive.md) — `receive`, `SilentMode`, timetable output, FIFO behavior265- [references/can/filters.md](references/can/filters.md) — `filterAllowOnly`, `filterBlockAll`, `filterAllowAll`266- [references/can/database.md](references/can/database.md) — `canDatabase`, `attachDatabase`, signal-level decode/encode267- [references/can/pack-unpack.md](references/can/pack-unpack.md) — `pack`, `unpack`, signal extraction, byte-order268- [references/can/message-extraction.md](references/can/message-extraction.md) — `extractAll`, `extractRecent`, `extractTime`, `discard`269270### CAN Troubleshooting271272See **Troubleshooting Gate** at the top of this section. Also route to diagnostics when the agent observes unhealthy bus state (TEC/REC > 0, BusStatus not ErrorActive) during any operation — including after transmit verification.273- [references/can/troubleshooting/diagnostic-workflow.md](references/can/troubleshooting/diagnostic-workflow.md) — Full diagnostic procedure (Phase 0 automation, L1 physical, L2 traffic analysis)274- [references/can/troubleshooting/script-interfaces.md](references/can/troubleshooting/script-interfaces.md) — Function signatures, arguments, and outputs for all diagnostic/analysis scripts275276---277278## Shared References279280- [references/shared/hardware-discovery.md](references/shared/hardware-discovery.md) — `canChannelList`, platform constraints281- [references/shared/channel-lifecycle.md](references/shared/channel-lifecycle.md) — `start`, `stop`, `onCleanup`, channel release282- [references/shared/limitations.md](references/shared/limitations.md) — Vendor/platform-specific constraints283284----285286Copyright 2026 The MathWorks, Inc.287288----