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: Zudal Zolotilar
Country: Cuba
Language: English (Spanish)
Genre: Science
Published (Last): 9 August 2012
Pages: 487
PDF File Size: 11.7 Mb
ePub File Size: 7.84 Mb
ISBN: 315-5-52518-794-3
Downloads: 92799
Price: Free* [*Free Regsitration Required]
Uploader: Vuran

No single frame or multi-frame messages can be received without matching a flow control filter. If J22534 reprogramming is practiced in the dealership, then it is the responsibility of each OEM to maintain and update their own sites, and keep current calibrations available for download. SAE J defines optional features that takes advantage of the J framework. High-speed Internet connection is highly recommended. Periodic messages will not be suspended during transmission or reception of a multi-frame segmented message.

Yes, J reprogramming application software typically does not incorporate diagnostic Scan Tool functions that prktocol be utilized to perform post-reprogramming tasks such as clear DTCs or re-learn procedures.

Return to normal speed after a break indication 6. How is this possible?

Standards and Protocols

Our experience and our expertise in the automotive and aeronautics sectors mean that our hardware and software designs provide a high level of quality. The software must be sold ‘for a reasonable price’, which will probably be a few hundred dollars. I always recommended BlueHost Reviews for my clients. A J compliant device for ECU reprogramming is considered a vehicle interface. Through close and intensive cooperation with our customersas well as a strategy that is based on quality and innovation, j5234 company m2534 become the market leader in its core business.


Each OEM is required to make available their ECU reprogramming calibrations on their own service information web sites.

Message Structure The following message structure will be used for all messages Transmit, Prtoocol, Filters, and Periodics and indications. A check of the OEM service information website is often a good place to start. Fortunately, each device comes with a software driver that protocoll 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.

There is no published standard yet. J framework includes application interfaces for the following functionality: Matching echoed bytes will not be placed in the receive message queue. Each protocol has different voltage and timing requirements.

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. Please contact us for further information or price request Additionally, the specification includes a provision that allows OEMs to use the J reprogramming method on through model year vehicles as long as OEMs make all necessary additional hardware i.

Softing Automotive – PassThru (SAE J)

Interface shall not adjust timer parameters based on keyword values. The following pages explain DrewTech’s implementation, and should be useful to end-users who want to program with our DLL:.


It also expands the scope of what a J device can do. What is J and J? Return to normal speed after a break indication. It allows the interface J to be used for other purposes and includes features that are above and beyond emission related reprogramming needs.

The application needs to handle tester present messages when required. The actual number of messages returned is in NumMsgs.

These devices are not made by car manufacturers, but by any company that sees an opportunity. 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. Any non franchise dealership would have to invest several thousand dollars in obtaining specialised tools one per brand!

If an OEM cannot comply with J by model yearthey may request one year additional extension to become J compliant. When does the legislation take effect? This protocol can be used to handle any custom CAN messaging protocol, including custom flow control mechanisms. To do that, you have to get the software application from the car manufacturer. A consumer had to rely on the car manufacturers dealership.

The following specifications clarify and, if in conflict with ISOoverride any related specifications in ISO In a similar vein, the J API makes all “car communications” hardware j22534 the same.