

Drew Technologies has been involved in the development, testing, validation, deployment, and support of several global OEM factory diagnostics programs using J2534. Many automakers are developing their next generation diagnostics system to use J2534. Many OEMs adopted this standard because it offered them several advantages over proprietary systems using a published standard lowered development cost, the OEM could easily switch suppliers, and competition from vendors offered a wide portfolio of tools and competitive prices There are many tangible and intangible reasons why using automotive standards makes sense.

OEMs are using the SAE J2534 standard for their engineering calibration tools, module reprogramming, and global dealership diagnostics tools. The J2534 standard formalized a PC-to-vehicle API that would allow the same application to work with different hardware from different vendors. The intent of this was to require all OEMs to offer module reprogramming to repair shops in the aftermarket. In 2002, SAE Published the first J2534 document. SAE J2534 - The Vehicle Communications Standard All of Drew Technologies' products are based on standards.

It's not a new idea, but changes in automotive technology and maturing standards have finally allowed this idea to become a reality.
