pub struct FdTimingBoundaries {Show 16 fields
pub nom_prescaler_min: u16,
pub nom_prescaler_max: u16,
pub nom_sjw_min: u8,
pub nom_sjw_max: u8,
pub nom_tseg1_min: u16,
pub nom_tseg1_max: u16,
pub nom_tseg2_min: u8,
pub nom_tseg2_max: u8,
pub data_prescaler_min: u16,
pub data_prescaler_max: u16,
pub data_sjw_min: u8,
pub data_sjw_max: u8,
pub data_tseg1_min: u8,
pub data_tseg1_max: u8,
pub data_tseg2_min: u8,
pub data_tseg2_max: u8,
}Expand description
Hardware-specific timing parameter boundaries for CAN FD bit timing.
These boundaries define the valid ranges for CAN FD bit timing parameters and are hardware-specific to PEAK-System CAN FD devices. CAN FD supports dual bit rates: a nominal (arbitration) bit rate and a faster data bit rate, each with their own timing parameters.
§Timing Parameters
§Nominal (Arbitration) Phase
Used during arbitration and control fields:
- nom_prescaler: Nominal phase clock prescaler
- nom_sjw: Nominal phase synchronization jump width
- nom_tseg1: Nominal phase time segment 1
- nom_tseg2: Nominal phase time segment 2
§Data Phase
Used during the data field for higher throughput:
- data_prescaler: Data phase clock prescaler
- data_sjw: Data phase synchronization jump width
- data_tseg1: Data phase time segment 1
- data_tseg2: Data phase time segment 2
§Usage
These boundaries are used internally by CanFdBitTiming::new() to validate timing
parameters. Users should reference CANFD_TIMING_BOUNDARIES to ensure their custom
CAN FD timing configurations fall within acceptable ranges for PEAK hardware.
§Note
The data phase bit rate must be equal to or higher than the nominal bit rate. Typical configurations use 500 kbit/s for nominal and 2-8 Mbit/s for data phases.
Fields§
§nom_prescaler_min: u16§nom_prescaler_max: u16§nom_sjw_min: u8§nom_sjw_max: u8§nom_tseg1_min: u16§nom_tseg1_max: u16§nom_tseg2_min: u8§nom_tseg2_max: u8§data_prescaler_min: u16§data_prescaler_max: u16§data_sjw_min: u8§data_sjw_max: u8§data_tseg1_min: u8§data_tseg1_max: u8§data_tseg2_min: u8§data_tseg2_max: u8