device and allows any J compliant PassThru device to connect to any vehicle network. PassThru Device Physical and Data Link Layer Protocol Support . J Recommended Practice for Pass-Thru Vehicle Programming Last Protocols Supported by a fully compliant SAE J Device. PassThru+ XS 2G is the only device fully compliant to J & J Recommended and tested by major OEM’s, the PassThru+ XS 2G device is a VCI .

Author: Tygokus Tojalkis
Country: Poland
Language: English (Spanish)
Genre: Life
Published (Last): 12 September 2007
Pages: 11
PDF File Size: 8.57 Mb
ePub File Size: 1.94 Mb
ISBN: 378-2-56722-568-7
Downloads: 56863
Price: Free* [*Free Regsitration Required]
Uploader: Mitaxe

Newer vehicles with CAN prktocol may be as fast as 2 minutes, while vehicles with CAN that have a lot of data to download will take well over an hour. To do that, you have to get the software application from the car manufacturer.

The programming time varies among vehicles based on communication speed of the protocol used, calibration file size, total number of calibration files, the number of ECUs to reprogram, and Internet connection latter is dependent on OEM. The actual number of messages returned is in NumMsgs. In addition, portocol following specifications clarify and, if in conflict with ISOoverride any related specifications in Protoocl This is dependent upon the make and model of vehicle.

Through close and intensive cooperation with our customersas well as a strategy that is based on quality and innovation, the company has become the market leader in its core business.

It is rooted in the group’s international dimension, which provides each and every one of our customers with local support that’s synonymous with proximity, fast response and flexibility.

Periodic messages will not be suspended during transmission or reception of a multi-frame segmented message. Prrotocol so called PASS THRU norm defines technically the protocols of communication which have to be supported pritocol a standard vehicle communication interface in order to enable the flashing of the ECU’s relevant for pollution emission.

J2534 FAQs

When does the legislation take effect? The protockl is not required to support baud rate detection based on the synchronization byte. What is J and J? Matching echoed bytes will not be placed in the receive message queue. No multi-frame messages can be transmitted without matching a flow control filter.


The following additional features of SAE J must be supported by the pass-thru device: I always recommended BlueHost Reviews for my clients. The total message size in bytes is the DataSize, and includes header bytes, ID bytes, and data bytes. A device alone is not enough to reprogram the ECU’s. This interface also includes some capabilities that may not be required for reprogramming, but allows the interface to be used for other purposes without placing a significant burden on the interface manufacturers.

This protocol can be used to handle any custom CAN messaging protocol, including custom flow control mechanisms.

Powertrain, Engine, Transmission, Throttle Controller and is mandatory on all vehicles from model year and forward. Where do I get the ECU reprogramming calibrations from?

Each protocol has different voltage and timing requirements, so this is no trivial task. If the application does not use the ISO transport layer flow control functionality, the CAN protocol will allow for any custom transport layer. The following features of ISO must be supported by the pass-thru device: Note that a fee set by the OEM may apply.

The EPA is forcing car manufacturers to release software that updates the firmware on their cars. It allows the interface J to be used for other purposes and includes features that are above and beyond emission related reprogramming needs. How is this possible? The application is required to handle any special timing requirements based on receipt of this response code, including stopping any periodic messages. Always one start bit and one stop bit.

Return to normal speed after a break indication 6. A consumer had to rely on the car manufacturers dealership. J25344 following pages explain DrewTech’s implementation, and should be useful to end-users who want to program with our DLL:. Even though each printer has different hardware, all printer drivers ‘look the same’ to Windows applications.

PassThru+ XS 2G & SAE J2534 protocol

The inventor of electronic diagnostics and a pioneer in the field of vehicle architecture, particularly multiplexed architecture, ACTIA innovates across its skills spectrum to stand out from the crowd, remain independent and maintain its leading position in the field. The default bus idle period before the interface shall transmit an address, shall be ms. Message Structure The following message structure will be used for all messages Transmit, Receive, Filters, and Periodics and indications.


The baud rate shall be set by the application, not determined by the SAE J interface. Some car manufacturers decided to check their application with PASS THRU hardware devices in order to assure the function of a device together with the software.

SAE J Pass-Thru API – EverythingHere – 博客园

If an OEM cannot comply with J by model yearthey may request one year additional extension to become J compliant. More than a requirement, quality is one of the ACTIA group’s true values, and is shared by all its employees in a certified environment.

A J compliant device for ECU reprogramming is considered a vehicle interface. PassThru device is unable to read specified number of messages from the vehicle network.

If the ISO checksum is verified by the interface, and the checksum is incorrect, the message will be discarded.

Passthru+ XS 2G & J protocol

Support for timer values that are less than or greater than those specified in ISO see Figure 30 in Section 7. The application needs to handle tester present messages when required. In a similar vein, the J API makes all “car communications” hardware look the same.

Support odd and even parity in addition to the default of no parity, with seven or eight data bits. Allow raw CAN messages. Consult OEM website guidance for minimum Internet connection specification requirements. Since the driver invisibly handles communication to the device, application software writers don’t have to worry about the connection details or low-level car protocols. Fortunately, each device comes with a software driver that implements the J API. A device requires a Windows-based PC on which the reprogramming application software operateswith a USB or Ethernet port, and an internet connection for Internet access to obtain reprogramming application software and calibration files.