To Find an Event Near you,
enter your zip code

Control Module Programming Overview

Course format: Virtual instruction with posttest
I-CAR Credit Hours: 1 hour
Estimated Duration: 1 hour
Gold Class: $75.00
Platinum: $75.00
Standard: $90.00


  • Initialization and Calibration of Electronic Systems (MK190V01)

This course is an Annual Training option for the following roles:
Production Management
Steel Structural Technician
Aluminum Structural Technician
Non-Structural Technician
Electrical/Mechanical Technicians
Refinish Technician
Auto Physical Damage Appraiser

Control Programming Overview is a 1 hour course that examines module programming. The course continues to introduce the society of automotive engineers (SAE) J2534-1 and J2534-2 communication. The student examines the difference between programming and coding. Finally, the course provides tips for successful programming.

Course Content
Module 1 – Understanding Module Programming
Module one will provide information to help identify when control modules need to be replaced and the tools and software needed. The course will define what the terms "flash programming" and "burning the program" mean. Finally, the organization, National Automotive Service Task Force (NASTF), that helps facilitate the availability of service information will be discussed.

Module 2 – J2534-1 vs. J2534-2
The purpose and description of the two types of SAE J2534 communication programming will be included in module two.

Module 3 – Coding, Programming, and Security
In module three, the difference between programming and coding will be established. Systems that may be secured will be discussed. Finally, this module will discuss when a Locksmith Identification (LSID) is needed.


After completing this course, you will be able to:

  • Identify when control modules need to be replaced
  • Recall what the terms “flash programming” and “burning the program” mean
  • Identify what SAE J2534 is
  • Recall what J2534-1 applies to
  • Recall what J2534-2 applies to
  • Identify the difference between programming and coding
  • Identify when systems may be secured
  • Determine when an LSID is needed