we don't have the mx though and i can't afford the ones we have at work. nearly whatever i want, program modules if i wanted if it wasn't blocked in the tablet's software, or if i need to do some google investigation on an issue and i want to read live data while i sit nicely inside. 30 devices at any given time could be used and not have interference issues and had quite a bit of range provided the wifi server was working correctly that day.Īlso, i use both bluetooth and wireless devices at work, and i can sit in the office 60 feet away with the wifi and read a vehicle outside if i want to, run evap tests, etc. there were also admin devices that could perform various things straight through the dealer connect ipads the regular ones could not access. i've had access to a chinese clone ids for a day but i couldn't find any configurable options though i think it was just unfamiliarity with the software in hindsight.Īlso, when i pushed service work through a franchise chrysler dealer nearly all the obd2 readers were wifi and were what both techs and service advisors used. Yeah kind of sorry i asked at this point because i don't need all the preaching and whatnot as i've been around the block a few times in this regard using both an 1.0 original elm and a newer revision, as well as a bluetooth elm, all unmodified with success. I wouldn't take that chance.īut, if there's equal chance to screw up the car over Bluetooth as there is wifi, then it's a case of pick your poison. Personally, if everyone is telling you to shy away from the WiFi version and even one report of issues using the WiFi version is good enough for me to go with the Bluetooth version. The difference is the phone is a lot less expensive. If speed between obd and device does have a bearing on obd-to-module write speed, then faster may not be better, as there may be less time for redundancy (if Focccus or the OBD is programmed to do that) and a higher chance that you pretty much brick your car like a failed rooted Android phone. In that case, if the write-to-module speed is slower than Bluetooth, then using a faster-than-Bluetooth connection isn't going to help you much. Hopefully, the speed benefits is only between the ODB-II and the device with the Focccus program, and the OBD itself governs the write speed to the module. That being said, sometimes the fastest speed isn't the best method. Click to expand."Work like it's supposed to"? Or work like you want it? Because if it isn't programmed to work with WiFi, and it doesn't work with WiFi, then it truly is working the way it's supposed to (or programmed to).
0 kommentar(er)
