Gen2 OBD2 app review

It is not just possible, it’s also highly relevant I would say. This applies to all software. Updated apps are cared for by devs and improved.

Many apps mentioned previously here are now abandonware, but still charge IAP. That’s not good for anyone.

I also very much like that Carscanner has model profiles that anyone can update and contribute to. So if you know the adress of a sensor that’s lacking, it’s easily programmable to fetch that data. Highly recommended.

 

(The CarScanner profile for Prius gen2 is actually very impressive, much more information than any other app I have evaluated. Some people (including reviewer?) does not select the correct profile and then end up with just basic OBD data…)

 

@mr_guy_mann, still have Car Scanner, able to comment?

The review post from 3 years ago seemed to indicate not just a matter of individual sensor PIDs missing, so much as entire ECUs.

 

Interested for the reply. And with the latest version and the correct profile…

 

My opinion is that this is the best for gen2 on iOS after testing many, many apps.

What app do you recommend, ChapmanF..?

 

I haven't tested enough alternatives on gen 2 to be anyone you'd ask for a recommendation. mr_guy_mann has.

The laptop I had Techstream on has let out the magic smoke, so lately I've been using the Autel AP200 based on the recommendation here, and I can confirm on my gen 3 it sees all ~ two dozen gen 3 ECUs and their data PIDs, and is able to do the most important things I used to do with Techstream.

 

Ok. A lot of opinions about apps are confirmation bias and subjective. My focus has been to not lock up your app towards any special hw supplier or IAP with apps that then are left abandoned.

(Clone the old ssd and apply image to a vm is my suggestion for your issue).

I also have techstream on an old MacBook Air (intel..) and it works great.

However, apart from programming smart keys, I would say with knowledge you can get any PID displayed in carscanner app if you know how-to.

All other apps are locking these features behind pay walls. That is why I love and chimed in for Carscanner and recommend it to anyone with gen2 and a dongle (I use vlink) with iOS BT support.

 

That's my suggestion too. It's the shortage of round tuits that gets in the way.

It is good to have an app with that flexibility—though with a dozen or two dozen ECUs in the car and each one having tens (some many tens) of PIDs, it can be an awful lot of work to configure such an app to be comparable to one that has them all out of the box.

How practical that is kind of depends on what you want to use it for. If you want, for example, to display some preferred gauges while driving, it's not very hard to program in a dozen PIDs you want to see. That's what I've done with my ScanGauge II.

If your car is malfunctioning right now and you want to start doing diagnosis right now, and you're not sure which PIDs are going to help before you see which ones are showing weird values, it never really feels like the time to be searching up programming details for a hundred PIDs.

And even that assumes that the app will be able to establish comms with the specific ECUs in the car that have the PIDs you want to see. In gen 2 especially, where only some of the ECUs are on the CAN bus and others are on the BEAN or AVC-LAN and only can be reached by asking some other ECU with more than one network interface to relay messages back and forth, or by voltage-level signaling on Tc or Ts, that's where a lot of the apps fall short.

It's easy to supply an app with a general way of entering PID info by ECU address, PID address, bit field, and arithmetic conversion, when all the ECUs are on a nice addressable bus where that works. Where that isn't the case, it's a lot harder to supply a general way to enter essentially new programming logic for whatever comm gyrations are needed to exchange messages with the harder-to-reach ECUs.