Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Automatic Baud Rate Detection on CAN Classic: A Deep Dive into SAE J1939-16
The SAE J1939-16 standard defines a process for automatically detecting the baud rate of CAN Classic networks, enabling devices to join without disrupting existing communication. This guide breaks down the key concepts, including ECU classifications, discovery modes, and implementation tips to help engineers design robust systems.
Understanding ECU Classifications in SAE J1939-16
The standard distinguishes between two types of electronic control units (ECUs) based on their role and installation:
- Permanently Installed ECU (PI-ECU): Required for normal system operation (e.g., engine control module, transmission control module). May use a predetermined baud rate or a detection procedure.
- Temporarily Installed ECU (TI-ECU): Not required for normal operation (e.g., service tools, datalink adapters). Must discover baud rate without prior network knowledge.
The classification directly affects the detection procedure: PI-ECUs have more flexibility (they may start with silent or active mode), while TI-ECUs must begin with silent baud discovery to avoid disrupting the network.
| Feature | PI-ECU | TI-ECU |
|---|---|---|
| Role | Required for normal system operation | Not required; typically a service tool |
| Baud rate knowledge | May have predetermined baud rate or use detection | Assumes unknown; must discover |
| Detection procedure | Can use silent or active mode as appropriate | Must initially use Silent Baud Discovery Mode; active mode only after confirmation |
| Network impact tolerance | Must minimize disruption; detection may occur only during initialization | Must avoid all disruption; silent mode ensures no ACK errors |
| CAN port variation | Detection capability can vary per port | Detection capability can vary per port |
Silent vs. Active Baud Discovery Modes
Baud rate detection relies on two modes defined by the CAN interface behavior:
Silent Baud Discovery Mode: The CAN interface listens only, does not transmit or assert the ACK bit. This prevents ACK errors and avoids disrupting ongoing communication. Bit-time measurement is performed by capturing error-free frames (where the ACK bit is set by other nodes) and measuring bit cell durations. The standard requires TI-ECUs to use this mode first.
Active Baud Discovery Mode: The interface participates normally – it transmits and asserts the ACK bit. This mode can be used to send specific 11-bit standard identifier frames to request responses and confirm baud rate, but only after a baud rate hypothesis is established via silent mode or for test/diagnostic purposes. Active mode carries a risk of ACK errors if the baud rate assumption is wrong, so it must be used cautiously.
The standard explicitly identifies the ACK bit as critical for silent measurement, and it warns that some hardware may not support a true silent mode (e.g., “listen only” mode that still participates in error signaling). Engineers must verify hardware behavior.
Implementation Considerations and Best Practices
Following the SAE J1939-16 process requires attention to several practical aspects.
🛠️ Engineering Design Insight
Always begin baud rate detection in silent mode to minimize network disruption. Ensure your CAN hardware supports a true silent mode (no ACK, no error frames). Validate bit-time measurements from multiple error-free frames to increase confidence before switching to active mode. Remember that baud rate detection capability can vary per CAN port and over the ECU lifecycle (e.g., bootloader vs. normal operation).
⚠️ Common Pitfalls
Do not skip silent mode and attempt active baud discovery on an unknown network. This can cause ACK errors and disrupt existing communication. Also, the standard explicitly excludes CAN FD baud rate detection – current J1939 CAN FD (J1939-17) uses a fixed 500/2000 kbit/s combination. Do not assume that all CAN ports on an ECU share the same detection capability.
Frequently Asked Questions
1. What is the difference between PI-ECU and TI-ECU baud detection procedures?
PI-ECUs can rely on a predetermined baud rate or use detection with either silent or active mode. TI-ECUs must always use the detection process starting with silent mode; active mode is only allowed after the baud rate is reasonably confirmed.
2. Why does the standard exclude CAN FD baud rate detection?
Currently, SAE J1939-17 specifies a single fixed baud rate combination (500 kbit/s data phase / 2000 kbit/s data phase), making automatic detection unnecessary for CAN FD networks.
3. What is the role of the ACK bit in baud rate detection?
The ACK bit confirms that a frame has been correctly received. In silent mode, the detecting ECU does not assert ACK, but it uses the ACK bit from other nodes as a timing reference for bit-time measurement. This is key to accurate baud rate determination without interfering.
4. What common mistakes should be avoided during implementation?
Avoid using active discovery without prior silent mode, assuming consistent detection capability across all CAN ports, and attempting detection on non-CAN Classic networks. Also, ensure the measurement method accounts for bit-time variations and uses error-free frames only.
