If your recommending cheapest possible interface, as I said, don't expect quality reliability or even sane behavior. In my experience - and as far as technology goes it's considerable - this is by far and away the most likely cause of your "freaked out" ecu.
IOS apps are clumsy, slow, and buggy, in my experience too, as a generalization. REV, from what I have read of it, is definately a tier or two down from dashcommand. As I mentioned - reduce the load will reduce the likelyhood of encountering a problem.
The question is which interface is best. I can assure you with no reservations whatsoever that "the cheapest" is the worst possible advice you can give someone to that question. That's the advise you gave and it demonstrates a poor understanding of how to approach technology solutions.
The recommendation of a cheap $12 interface demonstrates the ignorance I am alluding to. I don't really care if your offended. I'm sorry but it's bad advice from someone who has clearly had significant troubles making things work the way you expect it to!
---------- Post added at 12:27 PM ---------- Previous post was at 12:25 PM ----------
I'm not saying that there are no IOS version bugs in dahscommand. I am saying that dashcommand in my experience is an excellent solution and I'm also saying that ignorance of quality and performance considerations, such as recommending a $12 interface will ensure that you have the maximum number of problems you could encounter.
---------- Post added at 12:36 PM ---------- Previous post was at 12:27 PM ----------
I used dashcommand branded USB/Bluetooth combo interface. USB works far better than bluetooth. Bluetooth worked well but had high latencies once you are logging a screenful of interesting data - and a screenful in dashcommand is a LOT more than REV and many other minimalist OBD solutions.
I have hardware disabled the bluetooth interface on mine recently because it had developed reliability issues. (physically removed the bluetooth daughterboard)
I would suggest that once you have chosen an application - dashcommand, REV, whatever - by research, then choose the interface that the vendor documents as having good compatibility. Go with the simplest solution that meets your need. Don't go professional 802.11 interfaces first go as others here have and then experienced trouble making it work. Especially not with IOS. You want a balance between performance, quality and cost. If you go lowest cost, you can be DAMN SURE that you are also working with the lowest performance and quality equipment, and are almost guaranteed to encounter significant issues.
Have a PC on hand to test the interface with if you are working with an iPad.
---------- Post added at 12:54 PM ---------- Previous post was at 12:36 PM ----------
Actually, on that note I would recommend AGAINST a combo interface. For the dashcommand bluetooth daughterboard on mine it was prone to vibration induced connection problems. It is not soldered to the board, it is a tension based retension mechanism. VIBRATION works it loose. It took 18months for mine to work loose, but work loose it did, and I presume that something shorted when it finally let go, because the bluetooth simply doesn't work properly anymore. It broadcasts and detects but frequently fails connectivity. It did not do this new, I am certain it's a result of bad connections due to vibration.
I would suggest - if you want to try both - separate dedicated USB and bluetooth options. If you re going a combo, you want to ensure that the hardware is a one-piece board. You might not be able to do that without cracking one open, so it's a question then for the vendor. Refer them to this exmple : Bluetooth daughterboards work loose due to vibration. Everything needs to be directly soldered to the circuit.
I can't refer you to hardware interfaces that I know for a fact have no design issues of any kind, but I can help you find and choose something that will work reliably.
"Blue Meanie" 2007 Aurora Blue MPS 3 - 18x8.5+44 SSR GTX01 - 235/40R18 Michelin PS5 - 3.5" ETS TMIC - CPE stg 2 mount - HKS/CPE BPV - 2XS inlet - 2XS short shift - Corksport turbo manifold - HT 98 octane tune - Leather/Aluminium handbrake - Momo shifty knob - 7" touchscreen - JDM Mazda Retractable dashtop screen assembly - Bespoke Raspberry Pi Android based GPS/Carplay and instrumentation - 36AH reserve battery and C-TEK isolator - TEIN Street Advanced coilovers 1" drop - Superpro bushings - 220Kw/410Nm.
"Lipstick" 2013 Velocity Red MPS 3 - 18x7.5+48 Enkei RPF1 -225/40R18 Federal RS-RR - CPE TMIC - COBB inlet - CPE stg 2 mount - COBB Stage 1 98 octane tune - COBB shifty knob - 2XS short shift - 2XS turbo manifold.