SLLSEQ7E December   2015  – December 2019 TCAN330 , TCAN330G , TCAN332 , TCAN332G , TCAN334 , TCAN334G , TCAN337 , TCAN337G

PRODUCTION DATA.  

  1. Features
  2. Applications
  3. Description
    1.     Block Diagram
  4. Revision History
  5. Description (continued)
  6. Device Options
  7. Pin Configuration and Functions
    1.     Pin Functions
  8. Specifications
    1. 8.1 Absolute Maximum Ratings
    2. 8.2 ESD Ratings
    3. 8.3 Recommended Operating Conditions
    4. 8.4 Thermal Information
    5. 8.5 Electrical Characteristics
    6. 8.6 Switching Characteristics
    7. 8.7 Typical Characteristics
    8. 8.8 Typical Characteristics, TCAN330 Receiver
    9. 8.9 Typical Characteristics, TCAN330 Driver
  9. Parameter Measurement Information
  10. 10Detailed Description
    1. 10.1 Overview
    2. 10.2 Functional Block Diagram
    3. 10.3 Feature Description
      1. 10.3.1 TXD Dominant Timeout (TXD DTO)
      2. 10.3.2 RXD Dominant Timeout (RXD DTO)
      3. 10.3.3 Thermal Shutdown
      4. 10.3.4 Undervoltage Lockout and Unpowered Device
      5. 10.3.5 Fault Pin (TCAN337)
      6. 10.3.6 Floating Pins
      7. 10.3.7 CAN Bus Short Circuit Current Limiting
      8. 10.3.8 ESD Protection
      9. 10.3.9 Digital Inputs and Outputs
    4. 10.4 Device Functional Modes
      1. 10.4.1 CAN Bus States
      2. 10.4.2 Normal Mode
      3. 10.4.3 Silent Mode
      4. 10.4.4 Standby Mode with Wake
      5. 10.4.5 Bus Wake via RXD Request (BWRR) in Standby Mode
      6. 10.4.6 Shutdown Mode
      7. 10.4.7 Driver and Receiver Function Tables
  11. 11Application and Implementation
    1. 11.1 Application Information
      1. 11.1.1 Bus Loading, Length and Number of Nodes
    2. 11.2 Typical Application
      1. 11.2.1 Design Requirements
        1. 11.2.1.1 CAN Termination
      2. 11.2.2 Detailed Design Procedure
      3. 11.2.3 Application Curves
    3. 11.3 System Examples
      1. 11.3.1 ISO11898 Compliance of TCAN33x Family of 3.3-V CAN Transceivers Introduction
      2. 11.3.2 Differential Signal
      3. 11.3.3 Common-Mode Signal and EMC Performance
  12. 12Power Supply Recommendations
  13. 13Layout
    1. 13.1 Layout Guidelines
    2. 13.2 Layout Example
  14. 14Device and Documentation Support
    1. 14.1 Related Links
    2. 14.2 Support Resources
    3. 14.3 Trademarks
    4. 14.4 Electrostatic Discharge Caution
    5. 14.5 Glossary
  15. 15Mechanical, Packaging, and Orderable Information

Bus Wake via RXD Request (BWRR) in Standby Mode

The TCAN334 with low power standby mode, offers a wake up from the CAN bus mechanism called bus wake via RXD Request (BWRR) to indicate to a host microprocessor that the bus is active and it should wake up and return to normal CAN communication.

This device uses the multiple filtered dominant wake-up pattern (WUP) from ISO11898-5 to qualify bus traffic into a request to wake the host microprocessor. The bus wake request is signaled to the microprocessor by a falling edge and low corresponding to a “filtered” bus dominant on the RXD terminal (BWRR).

The wake up pattern (WUP) consists of a filtered dominant bus, then a filtered recessive bus time followed by a second filtered bus time. Once the WUP is detected the device will start issuing wake up requests (BWRR) on the RXD terminal every time a filtered dominant time is received from the bus. The first filtered dominant initiates the WUP and the bus monitor waits on a filtered recessive; other bus traffic does not reset the bus monitor. Once a filtered recessive is received, the bus monitor waits on a filtered dominant and again; other bus traffic does not reset the bus monitor. Immediately upon receiving of the second filtered dominant, the bus monitor recognizes the WUP and transitions to BWRR mode. In this mode, RXD is driven low for all dominant bits lasting for longer than tWK_FILTER. The RXD output during BWRR matches the classical 8-pin CAN devices, such as the TCANA1040A-Q1 device, that used the single filtered dominant on the bus as the wake up request mechanism from ISO11898-5.

For a dominant or recessive to be considered filtered, the bus must be in that state for more than tWK_FILTER time. Due to variability in the tWK_FILTER the following scenarios are applicable. Bus state times less than tWK_FILTER(MIN) are never detected as part of a WUP and thus no BWRR is generated. Bus state times between tWK_FILTER(MIN) and tWK_FILTER(MAX) may be detected as part of a WUP and a BWRR may be generated. Bus state times more than tWK_FILTER(MAX) are always detected as part of a WUP and thus a BWRR is always generated.

See Figure 33 for the timing diagram of the WUP. The pattern, tWK_FILTER time used for the WUP and BWRR prevent noise and bus stuck dominant faults from causing false wake requests. If the device is switched to normal mode, or an under voltage event occurs on VCC the BWRR will be lost.

TCAN330 TCAN332 TCAN334 TCAN337 TCAN330G TCAN332G TCAN334G TCAN337G WUP_sllseq7.gifFigure 33. Wake Up Pattern (WUP) and Bus Wake via RXD Request (BWRR)