Struct ecu_diagnostics::hardware::passthru::PtCombiChannel

pub struct PtCombiChannel { /* private fields */ }

Passthru combination channel for software emulation of ISO-TP channel over CAN channel

Why?

According to the J2534 API, a CAN and ISO-TP cannot be opened at the same time, as they both require physical access to the same hardware communication layer of the VCI.

To overcome this, we instead up open a dedicated CAN channel and run the ISO-TP communication via software. This allows for both CAN and ISO-TP to coexist at the same time.

IMPORTANT NOTE

This mode is technically a violation of the J2534 API, whilst tested devices work fine with this some cheap ‘clone’ J2534 adapters may struggle with the high throughput CAN Channel that is requied for this to work.

Implementations

impl PtCombiChannel

pub fn new(dev: PassthruDevice) -> HardwareResult<Self>

Creates a new combi channel using a given passthru device

Trait Implementations

impl CanChannel for PtCombiChannel

fn set_can_cfg(&mut self, baud: u32, use_extended: bool) -> ChannelResult<()>

Sets the CAN network configuration

impl Drop for PtCombiChannel

fn drop(&mut self)

Executes the destructor for this type.

impl IsoTPChannel for PtCombiChannel

fn set_iso_tp_cfg(&mut self, cfg: IsoTPSettings) -> ChannelResult<()>

Sets the ISO-TP specific configuration for the Channel

impl PacketChannel<CanFrame> for PtCombiChannel

fn open(&mut self) -> ChannelResult<()>

Opens the channel, from this point forward, the network filter will be applied to be fully open so data has to be polled rapidly to avoid a driver’s internal buffer from filling up rapidly

fn close(&mut self) -> ChannelResult<()>

Closes the channel. Once closed, no more traffic can be polled or written to the channel.

fn write_packets( &mut self, packets: Vec<CanFrame>, timeout_ms: u32 ) -> ChannelResult<()>

Writes a list of packets to the raw interface

fn read_packets( &mut self, max: usize, timeout_ms: u32 ) -> ChannelResult<Vec<CanFrame>>

Reads a list of packets from the raw interface

fn clear_rx_buffer(&mut self) -> ChannelResult<()>

Tells the channel to clear its Rx buffer. This means all pending messages to be read should be wiped from the devices queue, such that PayloadChannel::read_bytes does not read them

fn clear_tx_buffer(&mut self) -> ChannelResult<()>

Tells the channel to clear its Tx buffer. This means all messages that are queued to be sent to the ECU should be wiped.

impl PayloadChannel for PtCombiChannel

fn open(&mut self) -> ChannelResult<()>

This function opens the interface. It is ONLY called after set_ids and any other configuration function

fn close(&mut self) -> ChannelResult<()>

Closes and destroys the channel

fn set_ids(&mut self, send: u32, recv: u32) -> ChannelResult<()>

Configures the diagnostic channel with specific IDs for configuring the diagnostic server

fn read_bytes(&mut self, timeout_ms: u32) -> ChannelResult<Vec<u8>>

Attempts to read bytes from the channel.

fn write_bytes( &mut self, addr: u32, ext_id: Option<u8>, buffer: &[u8], timeout_ms: u32 ) -> ChannelResult<()>

Attempts to write bytes to the channel.

fn clear_rx_buffer(&mut self) -> ChannelResult<()>

Tells the channel to clear its Rx buffer. This means all pending messages to be read should be wiped from the devices queue, such that PayloadChannel::read_bytes does not read them

fn clear_tx_buffer(&mut self) -> ChannelResult<()>

Tells the channel to clear its Tx buffer. This means all messages that are queued to be sent to the ECU should be wiped.

fn read_write_bytes( &mut self, addr: u32, ext_id: Option<u8>, buffer: &[u8], write_timeout_ms: u32, read_timeout_ms: u32 ) -> ChannelResult<Vec<u8>>

Attempts to write bytes to the channel, then listen for the channels response

impl Send for PtCombiChannel

impl Sync for PtCombiChannel