Site Loader

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: Kazirr Madal
Country: Jamaica
Language: English (Spanish)
Genre: Literature
Published (Last): 12 January 2007
Pages: 318
PDF File Size: 4.18 Mb
ePub File Size: 9.97 Mb
ISBN: 549-8-64795-831-8
Downloads: 57092
Price: Free* [*Free Regsitration Required]
Uploader: Kigazragore

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. It allows the interface J to be used for other purposes and includes features that are above and beyond emission related reprogramming needs. Those instructions were added into It also expands the scope of what a J device can do.

No work has been initiated for the J conformance test cases. There is no published standard yet.

Softing Automotive – PassThru (SAE J)

The following specifications clarify and, if in conflict with ISOoverride any related specifications in ISO The maximum sink current to be supported by the interface is mA. The range for all tests performed relative to ISO is —1. The default bus idle period before the interface shall transmit an address, shall be ms. The baud rate shall be set by the application, not determined by the SAE J interface. The interface is not required to support baud rate detection based on the synchronization byte.

Support odd and even parity in addition to the default of no parity, with seven or eight data bits. Always one start bit and one stop bit. Support for timer values that are less than or greater than those specified in ISO see Figure 30 in Section 7. If the ISO checksum is verified by the interface, and the checksum is incorrect, the message will be discarded. Interface shall not adjust timer parameters based on keyword values.


In addition, the following specifications clarify and, if in conflict with ISOoverride any related specifications in ISO The pass-thru interface will not automatically handle tester present messages. The application needs to handle tester present messages when required.

The application is required to handle any special timing requirements based on receipt of this response code, including stopping any periodic messages. The following additional features of SAE J must be supported by the pass-thru device: Return to normal speed after a break indication. Allow raw CAN messages. This protocol can be used to handle any custom CAN messaging protocol, including custom flow control mechanisms.

The following features of ISO must be supported by the pass-thru device: To maintain acceptable programming times, the transport layer flow control function, as defined in ISOprotocpl be incorporated in the pass-thru device see Appendix A.

If the application does not use the ISO transport layer flow control functionality, the CAN protocol will allow for any custom transport layer.

No single frame or multi-frame messages can be received without matching portocol flow control filter. No multi-frame messages can be transmitted without matching a flow control filter.

Periodic messages will not be suspended during transmission or reception of a multi-frame segmented message.

The next data byte shall not be sent until u2534 echo byte has been received and verified. If the echoed byte received doesn’t match the transmitted byte, or if after a period of T1 no response was received, the transmission will be terminated. Matching echoed bytes will not be placed in the receive message queue. How is this possible?

PassThru+ XS 2G & SAE J2534 protocol

The application and the printer driver communicate via an API. Pdotocol though each printer has different hardware. You are free pick any printer based on your preferences color, size, durability, cost, speed without worrying about software incompatibilities. The EPA is forcing car manufacturers to release software that updates the firmware on their cars.


J FAQs | Bosch Diagnostics

The software must be sold ‘for a reasonable price’, which will probably be a few hundred dollars. Each protocol has different voltage and timing requirements. Fortunately, each device m2534 with a software driver that implements the J API. The following pages explain DrewTech’s implementation, and should be useful to end-users who want to program with our DLL:. Message Structure The following message structure will be used for all messages Transmit, Receive, Filters, and Periodics and indications.

The total message size in bytes is the DataSize, and includes header bytes, ID bytes, and data bytes. Only the optional features will be described by this document.

SAE J defines optional features that takes advantage of the J framework. J framework potocol application interfaces for the following functionality: Return to normal speed after a break indication 6. What is an API? Even though each printer has different hardware, all printer drivers ‘look the same’ to Windows applications.

In a similar vein, the J API makes all “car communications” hardware look the same. The Software The EPA is forcing car manufacturers to release software that updates the firmware on their cars. Anyone can buy this software, even individual car enthusiasts.

These devices are not made by car manufacturers, but by any company that sees an opportunity. Each protocol has different voltage and timing requirements, so this is no trivial task. Since orotocol driver invisibly handles communication to the device, application software writers don’t have to worry about the connection details or low-level car protocols. PassThru device is unable to read specified number of messages from the vehicle network. The actual number of messages returned is in NumMsgs.

The specified protocol type within the message structure is different from the protocol associated with the communications channel when it was opened.