Comment by ibejoeb
15 hours ago
Does it have any make-specific features? For instance, I've used vcds for VW/Audi since it has better reporting than generic odb2 code readers.
15 hours ago
Does it have any make-specific features? For instance, I've used vcds for VW/Audi since it has better reporting than generic odb2 code readers.
At the wire level, no: it speaks generic OBD2 (ELM327), so it sees powertrain codes and standard PIDs. It won't talk to every module on a VAG car the way VCDS does — no ABS/airbag/body modules, no adaptations or coding. If you need that, VCDS stays on your bench.
Where it is make-specific is the interpretation layer. The code database includes manufacturer-specific DTCs for the 10 major makes, and there's per-model data down to the generation level — known failure patterns, which codes are common on which engines. So a P0171 on an E46 gets read in the context of "this generation eats intake boots and DISA valves," not a generic lean-code writeup. The AI report is conditioned on the exact year/make/model/engine, which is where most of the diagnostic depth comes from.
That being said, I'm continually expanding support, it really just depends on what sort of barriers I run into with these bluetooth scanners. For certain types of diagnostics (large truck / Buses etc) I'll likely need to make a separate desktop app that connects directly wired.
Would love to see more Subaru support