pcmhacking.net

hi i was wondering if anyone needing help with there development atm im thinking of creating a tool to be able to use obdx pro vt with tech2win

Good luck.

You need to make a j2534 dll to communicate with tech2win,and than translate the output of dll to obdxpro. The J protocol is also non standard used by tech2win.

The protocol is standard, just not the most common J2534. Its ISO 22900-2 D-PDU. https://www.iso.org/standard/41276.html (first 10 pages preview) https://www.sis.se/api/document/preview/69232/

yer i have to pay for that was hoping someone would share also the first link isnt in english

Tech2Win uses the ISO 22900-2 Diagnostic-Protocol Data Unit (D-PDU) API and RP1210 API.

Tazzi is still (?) working on the J2534 support.

MudDuck514 wrote:Tech2Win uses the ISO 22900-2 Diagnostic-Protocol Data Unit (D-PDU) API and RP1210 API.

Tazzi is still (?) working on the J2534 support.

The J2534 side I am, I have been bogged down with OBDX development along with helping implementation of future support for E38 and newer ecus into lsdroid

I have the J2534 dll 99% completed. It does recognise with J2534 application including pcmhammer, GM ACDELCO, GDS2 ect. I still have a few commands that the dealer software are calling to which I have not added yet, but appears to be at least doing all the 'major' commands.

The D-PDU is similar to that of J2534 where there is a standardized command set. Difference being there is different commands and requirements for returned data.

Ok so no point working on will you be releasing this any time soon or do you need help with it

modzer321 wrote:Ok so no point working on will you be releasing this any time soon or do you need help with it

I am not working on the D-PDU api.
Only the J2534, but this is closed source so its coding is not available to the public.

are you going to release what you made or no

modzer321 wrote:are you going to release what you made or no

Oh course, otherwise there would be no point making it