>>772907Fine, but what's gonna happen now is i'm going to get suckered into shitposting in some thread and forget to turn it off... then i'm going to be "that asshole"...
>>772911>code readerI should also add... Get one that supports all the vehicle flavors.
Some of the cheap ($20-ish) ones only support one or two vehicle protocols, they're usually marketed brand-/year-specific.
My neighbors/coworkers all know i'm a motorhead; for every code I've pulled on my own vehicles I've pulled one or two for someone else. Having a reader that not only speaks Dodge, but also Ford, GM, Pontiac, Honda, Kia, etc has been pretty handy.
>SAE J1850 PWM>SAE J1850 VPW>ISO9141-2>ISO14230-4 (KWP2000)>ISO 15765-4/SAE J2480 (CANBus, which all vehicles newer than 2008 sold in the US use)are the 5 standards, having a reader that speaks all of those is worth the additional cost of the reader.
Shortly after I bought my '12 snowmobile, I went through the wiring diagrams and noticed they had switched to CANBus for the vehicle interface, from their old-style proprietary system. Bought a connector to mate up with the diagnostic port on my sled, and wired those pins to the appropriate terminals on my adapter.
Torque couldn't figure out what it was connected to, but when I paired the snowmobile to my computer I was definitely getting data back... it was just a matter of figuring out how to parse it into something useable.
Started poking around, made a few threads on sled and technical forums looking for information on how to "hack" the ECU...
...a few weeks later I got a cease-and-desist from Poo's legal team... kind of brought that project to a halt.
I'd love to have an off-the-shelf adapter that can pair to a phone, then use an app on there to display and log engine parameters (Coolant temp, RPM, injector duty cycle, timing advance, etc) along with sensors on the phone (GPS, elevation, acceleremoters).
For tuning, that'd be a real beneficial tool to have.
