Review on 📱 Wireless Data Module: AutoMeter 6035 OBD-II with Bluetooth for Apple iOS Devices - Dashlink by Adam Quintana

Love the concept, hate the execution. The hardware is fine, but it took a few times to get a stable connection and it takes a long time to identify the PID. Bluetooth doesn't automatically reconnect if I leave it in the car and sometimes it won't connect at all. The software is really poorly made. I suspect it was written in another tool, then ported and run in a container on an iPhone/iPad (Pega? Powerapps?). There's a "Remember my choice" checkbox on startup, but it doesn't work, and if you touch it, a gray box appears elsewhere on the screen, requiring you to acknowledge the warning every time you launch it. All graphics are distorted, they don't follow UI guidelines very well, works in landscape mode, pitch/roll etc. is wrong even when landscape mode is selected, limited ability to adjust gauges, can't mix gauges and dashboard content e.g g -place circle on sensor page, editing sensor position is clunky, not gridded, editing a sensor resets its type so you have to do everything from scratch, you can't put graphical borders on a sensor - like a red zone on dials at a specific temperature or pressure. The last sensor touched moves forward graphically, so if there is an overlap, you need to make some adjustments. It doesn't recognize my cars - none of them (99-2015 Lexus and Audis), so even though it says autofill the VIN it didn't find anything. There may be a limitation on the machine, but it's odd that I don't see any oil pressure or temp. etc. etc. The refresh rate is slow, but not sure if it's machine or implementation. They should hire me to fix this mess lol; It's definitely not up to professional software standards for a long time, but if they get decent programmers for it, it might be ok. It kind of fits my current needs, but it's probably best to wait a year or two while they either fix the software or someone else releases something better written. I don't know how hard it would be to read the bluetooth connection, but if it's not too hard or I can find information on how to read the odb port, I'll just write an interface that works with your hardware for my needs. (Used in racing cars). How about an open source connection? Money definitely in the sale of equipment. I don't even care about revs and speed as it has a rev limiter and speed doesn't matter in a race car so there's enough room on the iPad screen for what I want. In my ideal I would like per water temp, oil temp, oil pressure, voltage, fuel level, time since engine started, fuel mileage since engine started and G-Lap with maximums stored until you delete it all in one screen.