Support of VCI hardware and D-PDU API (ISO 22900-2, J2534, RP1210)

[etas-lorenz]

There are at least three similar or extending standards defining a standardized D-PDU API to access Vehicle Communication Interfaces (VCI):

• [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=41276](ISO 22900-2): Modular vehicle communication interface (MVCI) -- Part 2: Diagnostic protocol data unit application programming interface (D-PDU API)
• SAE J2534/1: Recommended Practice for Pass-Thru Vehicle Programming
• TMC RP1210. TMC is the Technology & Maintenance Council of the ATA (American Trucking Associations).

There are already multiple products out there in the market including some products from ETAS. We should support this.

[Samispence]

So I have been reading about rp1210's and I agree that we should support it. But can we expect the definition to change in the next couple of years with the development of new technology?

[etas-lorenz]

Standards always evolve. RP1210 is already available in versions A and B. I've already seen proposals for version C. To my understanding this is upward compatible.

The same is true for J2534-1 and J2534-2.

So we are not braking anything if we now implement the current standards rather than waiting for updates.

[ZeroAviation]

Did this actually get implemented? Meaning, can I use a off the shelf J2534 interface with this application? J2534 is pretty generic between hardware, should be somewhat straight forward. Cheers

[yegorich]

Any update on this issue?

Thanks.

[electronslayer]

I would like to attempt to implement the RP1210B but need some preliminary guidance.

[Fang717]

I think its a good idea to support RP1210 device