12 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHWireless Wifi OBD2 Reader 2015
Reported or suspected cause
sometimes you have
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that report identifying a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Reported cause
The only minor issue is sometimes you have to try and connect twice.
Leading evidence: 'sometimes you have' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'sometimes you have' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Use "torque pro' app' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
If you use Android, you can use eithet wifi or bluetooth but the latter is a lot cheaper.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
If you use Android, you can use eithet wifi or bluetooth but the latter is a lot cheaper.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
12 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T060112Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Ive searched but the threads are old and figured that the tech has to be better now.
What OBD2 wireless readers are people using with their iPhones, and what apps are you using them with?
I may pull the trigger on this reader:
RioRand RD6 Wireless WIFI OBD 2 Car Diagnostic Reader Scanner for Iphone(RD6): Amazon.ca: Automotive
RioRand RD6 Wireless WIFI OBD 2 Car Diagnostic Reader Scanner for Iphone(RD6): Amazon.ca: Automotive
and Ive read that the DashBoard app is one of the better apps.
Today at work a colleague showed me his wireless garmin reader that connects via wifi to his gps or his phone (android). the stuff he could pull up was awesome. that reader is $100. the one above is only $20.
This is the reader I'm using
http://www.amazon.ca/Wireless-Diagnostic-Scanner-Adapter-iPhone4S/dp/B00DYOVXZ0/ref=sr_1_1?s=automotive&ie=UTF8&qid=1426350327&sr=1-1&keywords=elm327+wifi
http://www.amazon.ca/Wireless-Diagnostic-Scanner-Adapter-iPhone4S/dp/B00DYOVXZ0/ref=sr_1_1?s=automotive&ie=UTF8&qid=1426350327&sr=1-1&keywords=elm327+wifi
along with the Dash Command app. I connect my iPad mini via wifi and I'm good to go. Apparently IOS won't connect via Blutooth.
I use the one you are about to buy with dash command. The only minor issue is sometimes you have to try and connect twice. Other than that, cheap and works great.
finaly used this as i threw a code.
super easy to set up and intiate. super easy to navigate. showed the codes and an explanation of the code. lots of different screens to monitor items such as performance tuning.
overall well worth the $$ paid and id do it again (especially since i got dinged $35 to read codes my last visit for some work)
I've had a BT OBD reader for years, I love it. I use the "torque pro' app on my android phone. It reads/resets codes and displays a bunch of info too. I keep one in the garage and one in the car.
Basically any 'elm 327' compliant reader will do. I have bought a few over the years from either ebay or dx.com .
Got the bluetotth ODBii reader and downlaoded torque. I can finally get some more info from my car now...
why does this work but not my durametric??? argh
I bought a cheap Bluetooth one ($5 shipped on ebay), but it is incompatible with my iPhone. I have to use it with my Nexus tablet. So, that's something to watch out for if you go with a Bluetooth model.
Other than iPhone compatibility it works great.
For diagnostic purposes, the Android Torque pro wins hands down. For iOS, the OBD fusion app is good but still far from the Torque pro in terms of the GUI.
If you use iOS, you're stuck with wifi. If you use Android, you can use eithet wifi or bluetooth but the latter is a lot cheaper.
