Possible new OBD2 interface

[NSFW]

https://www.crowdsupply.com/meatpi-elec ... /wican-pro
https://github.com/meatpiHQ/wican-fw

You can't buy one yet, but the last update was 3 months ago and they were just about to start production, so maybe it'll be ready soon?

It supports every automotive protocol that I've ever heard of, it's open source, and it's $90 US.

The big question in my mind is whether or not it supports VPW at 4x speed. It looks like the low-level protocol stuff is all done on a dedicated chip, so despite the firmware being open source it might not be possible to add 4x support if it's not already there.

[ironduke]

Looks interesting, quickly scanned but I don't see anything about J2534 standard?

[NSFW]

It uses a serial connection, similar to ELM devices. As far as I know, J2534 is strictly a Windows thing, but serial works with pretty much every operating system.

[Charlescrown]

I don't think J2534 has anything to do with windows. It's a standard set by the SAE for communicatios protocol to reprogram ECU's.

[antus]

J2534 doesn't say it has to be windows but then they define the software interface as a windows DLL interface, which then means it has to be windows. It would seem this tool doesn't support J2534, thus cant be used with most OEM tools that use that standard, or aftermarket / hobbyist tools that are written for J2534 and we also dont know if they intend to support large packets so we don't know if it'll work with pcmhammer yet (using the STN command set that it advertises). But, using STN it would have no 4x support as its not in the protocol and so would be a slow interface. At this stage I think the obdxpro interfaces are a better option for the sort of stuff we talk about here as they have an open protocol, do work with pcmhammer and do have J2534, as well as they're developed by those friendly to our community and who support the tools well. This meat pi is probably fine for people logging only or working with can and with no interest in J2534.

I had a bit of a look around the github source, it looks like only the can protocol is there, the rest is either private or not written yet. I also dont see all the PC protocols they advertise, and non-can protocols are not listed in the device pinouts in the readme.