EDUCATION BUILD // NOT SAFETY-CERTIFIED // SYNTHETIC DEMO DATAEmbedded32 is for learning and prototyping - not automotive-certified, safety-certified, or a complete SAE J1939 stack.
Embedded32
Menu

Learning outcomes

After completing the Embedded32 two-week module, students should be able to:

CAN and framing

  1. Explain the difference between standard (11-bit) and extended (29-bit) CAN identifiers.
  2. Send and receive classic CAN frames using @embedded32/can mock drivers.
  3. Implement a simple acceptance filter by CAN ID.

J1939

  1. Parse a 29-bit J1939 identifier into priority, PGN, and source address.
  2. Decode catalog PGNs to human-readable names using @embedded32/j1939.
  3. Build a J1939 CAN ID from logical fields.
  4. Describe PDU1 vs PDU2 at a conceptual level.

Simulation

  1. Wire multiple ECU simulators to a shared virtual CAN bus.
  2. Identify which source address originated a given PGN.
  3. Relate simulation output to a simplified vehicle profile (basic-truck).

Diagnostics

  1. Explain the purpose of DM1 active fault broadcasts.
  2. Extract MIL status and SPN/FMI from a synthetic DM1 payload.
  3. Write a short diagnostic summary identifying the affected ECU.

Professional practice

  1. Run repository verification commands (npm run build, npm run test:labs).
  2. State the limitations of an educational J1939 subset versus production tooling.

Not claimed as outcomes

Students are not expected to:

  • Certify compliance with SAE J1939 conformance tests
  • Operate production HIL or safety-critical systems
  • Use Embedded32 as a replacement for professional CAN analyzer hardware