The only J2534 device I own is a Tactrix OpenPort 2.0, which doesn't support VPW. I just added the J2534 classes in hopes that something would come along eventually... and look what happened! What's your account name on GitHub? I'll add you to the project. Antus and I have been PMing back and forth ...

Thanks for all of the info, I just ordered a couple. I'll stick with the stock firmware long enough to get some basic communication working, and then see about improving it. I'll read up on the AVT protocol in the meantime.

Use an allpro adapter from obddiag.net. I can get it doing 180 byte packets and 4x now with firmware mods. You need ttl serial in to it to reflash it. Will work with you on this project. I have working write on the avt now but im not happy with the code and am time poor. This packet size is a bit s...

Great thread guys. I agree the elm isn't ideal for a lot of this type of thing. I used so a bit then gave up on it a few years back when I needed a VPW transceiver. Ended up making our own (my son and I) out of a arduino mini. Similar to the designs shown earlier in this thread. I think it could do...

I have some experience with J2534 so I'm not too worried about that. What worries me more is devices that support the J2534 API (on the application-software side) but that don't actually support J1850 VPW (on the vehicle side). For example I talked with Tactrix about VPW support and they don't have ...

Also, does anyone know whether these devices can support VPW without the overhead of ELM's devices?

https://smile.amazon.com/dp/B074365Q6H/

I've been working on some utilities to help with reverse engineering: https://github.com/LegacyNsfw/PcmHacks My hope is to extract GM's reflashing kernel from a recorded session, open it up in IDA, figure out how it works, write a new one in C, as post that on Github as well. If anyone has anything ...

I realize this is quite an old post, but would you be willing to share the source code for the checksum plugin?

Thanks!