Skip to content

ECU diagnostic tools — Diagon/Launch vs OBD

Tags: #diagnostics · #obd · #scanner · #ecu · #elm327

Prices and suppliers on this page are Russian-market (RUB, at the dates shown). Verify locally before relying on them in Syria.

Some advice here concerns sub-zero winters and is less relevant in a hot climate.

Budget option: ELM327. A dual-board ELM327 (v1.5) OBD2 adapter, paired with a compatible OBD app on phone/laptop, can read and clear FAW X80 error codes and check engine temperature at the owner level, before a mechanic visit — but a single-board ELM327 clone reportedly does not work reliably, so buy the dual-board version 123 456. Confirmed capabilities are limited to reading/clearing DTCs and engine temperature; don't expect extended functionality (live data, module-specific diagnostics) beyond that from a plain ELM327 — for that, see the Diagon/Launch/MUCAR BT200 options below.

FAW X80 ECU diagnostics need specialized scanner software. Diagon or Launch scanners loaded with FAW firmware files ("fawcar") can read the full set of error codes 78. Standard OBD-II protocol readers (e.g. ELMscan, Torque) cannot access X80-specific fault codes 78 — using the correct tool is essential for finding the real root cause behind a warning light, not just a generic OBD code.

A MUCAR BT200 scanner paired with Diagzone PRO software was confirmed to work on the X80 for: reading ABS sensor faults/codes; reading TPMS (tire pressure sensor) data; electronically adjusting brake-shoe wear margins; and reprogramming/resetting the handbrake friction-collar spacing 910111213. Limitation: it cannot bind/ reprogram new TPMS sensors to the vehicle — that needs a dedicated TPMS programming tool, and it cannot record or reprogram pressure-sensor IDs 141516.

Naming quirk: scanners show "Besturn" instead of "FAW X80." Some OBD2 diagnostic tools identify the vehicle as "Besturn" or "Bestune" rather than "FAW X80" in their software — this is just a naming/branding variation in the tool's vehicle database (FAW's domestic brand name for this model line), not a sign of the wrong vehicle profile or a different underlying car. Reasoning given in the thread: the diagnostic software is somewhat rough around the edges and the vendor didn't bother adding the correct "R" or otherwise distinguishing the export badge — they lumped the whole FAW model lineup under "Bestune" to save the trouble 17181920. Expect to see "Besturn"/"Bestune" in fault-code readouts and treat it as equivalent to X80.

ECU physical location. The ECU is located under the dashboard, behind the instrument cluster panel/shroud, and is reachable from below the steering wheel after removing the panel — visible looking upward from the driver's footwell 2122. A second, independent thread confirms the same general area — "under the steering column, slightly to the right" — describing it as an easy reach 2324. On how much disassembly is required to get there: one owner reported not removing any lower/undershield components at all, only the hose/tubing routing in the way 25 — consistent with the "easy reach" framing above, though the amount of disassembly needed may vary by what other work is being done in that area at the same time.

General check-engine-light procedure. When the check-engine light appears with no other clue: (1) first disconnect the negative battery clamp for several minutes and see if the light clears on reconnection — a low-cost first step, though not a reliable fix on its own (compare the winter-autostart card, which found battery disconnect doesn't clear vehicle-specific DTCs the way an actual scan/clear does); (2) if the light persists, connect an OBD reader (an ELM327-type adapter with an app such as CarScanner) to read the actual error code; (3) if it still recurs after that, visit a service center for professional diagnosis and code-clearing — a check-engine light left un-diagnosed by guesswork can change how the car drives and increase fuel consumption 262728.

Fuel-quality as a check-engine trigger. One documented case traced the check-engine light to poor-quality fuel from a substandard filling station rather than any component fault. Fix: partially drain the tank and refill with better-quality fuel (95+ octane), or switch filling stations; the error typically needs roughly 20–50km of driving on clean fuel to clear on its own, and may re-trigger once and then clear for good after a further top-up of good fuel 29.

OBD adapter scope: engine-only visibility. ELM327-type OBD adapters (Bluetooth or USB) reliably read only the engine/ECU's own fault codes. Other control modules — transmission, ABS, body electronics/BCM — are not visible through the standard OBD-II port with these adapters; for those, professional/module-specific diagnostic equipment (see the Diagon/Launch/MUCAR BT200 options above) is needed 303132.

Diagzone Pro — confirmed to recognize the vehicle. Diagzone Pro diagnostic software/scanner reliably recognizes and supports the FAW Besturn X80, reading vehicle parameters and diagnostic codes — useful context given some dealerships report the X80 missing from their service databases entirely; a shop lacking a scanner with X80 in its database simply won't be able to diagnose the car at all 3334.

Budget option: ELM327 Bluetooth v1.5. An ELM327 v1.5 Bluetooth scanner with a dual-PCB design and a PIC18F25K80 chip supports basic FAW X80 diagnostics. Available on Ozon.ru for roughly 800 RUB as of April 2026. Reads and clears error codes via a companion smartphone app. Not a substitute for a professional scanner (e.g. for TPMS programming — see that card), but sufficient for basic home troubleshooting 35 3637.

X-DIAG PRO-3 reads hidden fault codes other scanners miss. Standard OBD scanners — including basic Foxwell units and generic OBD2 tools — cannot read all of the X80's fault codes. The X-DIAG PRO-3 scanner can retrieve hidden/manufacturer-specific codes invisible to those other tools, for example climate-sensor faults B150112, B150297, and B150C12, and parking-brake errors that appear after brake-pad service. Recommended specifically for chasing persistent electrical gremlins after water damage, where a generic scanner comes back clean but the symptom persists 3839.

Media

OBD scan tool screen showing the vehicle identified as "Besturn"/"Bestune" rather than "FAW X80"

OBD scan tool screen showing the vehicle identified as "Besturn"/"Bestune" rather than "FAW X80"

Sources

This page is compiled from 39 community messages. Every fact carries a numbered reference to its original author and message.

Last updated: 2026-07-24


  1. Сергей Сергей (5040352039) · FAW X80 🚘🛠🛞 · 2025-06-12 · original message · ru ↩

  2. Денис З (1802459040) · FAW X80 🚘🛠🛞 · 2025-06-12 · original message · ru ↩

  3. Игорь Кияшевский (5998696629) · FAW X80 🚘🛠🛞 · 2025-06-19 · original message · ru ↩

  4. Игорь Кияшевский (5998696629) · FAW X80 🚘🛠🛞 · 2025-06-19 · original message · ru ↩

  5. Денис З (1802459040) · FAW X80 🚘🛠🛞 · 2025-06-19 · original message · ru ↩

  6. Игорь Кияшевский (5998696629) · FAW X80 🚘🛠🛞 · 2025-06-19 · original message · ru ↩

  7. palsanych1 (838938595) · FAW X80 🚘🛠🛞 · 2024-09-12 · original message · ru ↩↩

  8. Эдуард Янонис (1292719479) · FAW X80 🚘🛠🛞 · 2024-09-12 · original message · ru ↩↩

  9. Волосатая Фольга (1380548962) · FAW X80 🚘🛠🛞 · 2024-12-26 · original message · ru ↩

  10. Волосатая Фольга (1380548962) · FAW X80 🚘🛠🛞 · 2024-12-26 · original message · ru ↩

  11. HS Development (204359692) · FAW X80 🚘🛠🛞 · 2024-12-27 · original message · ru ↩

  12. Волосатая Фольга (1380548962) · FAW X80 🚘🛠🛞 · 2024-12-27 · original message · ru ↩

  13. Волосатая Фольга (1380548962) · FAW X80 🚘🛠🛞 · 2024-12-27 · original message · ru ↩

  14. HS Development (204359692) · FAW X80 🚘🛠🛞 · 2024-12-27 · original message · ru ↩

  15. HS Development (204359692) · FAW X80 🚘🛠🛞 · 2024-12-27 · original message · ru ↩

  16. Волосатая Фольга (1380548962) · FAW X80 🚘🛠🛞 · 2024-12-27 · original message · ru ↩

  17. Unknown · FAW X80 🚘🛠🛞 · 2025-03-28 · original message · ru ↩

  18. Valera P (557722718) · FAW X80 🚘🛠🛞 · 2025-03-28 · original message · ru ↩

  19. Unknown · FAW X80 🚘🛠🛞 · 2025-03-28 · original message · ru ↩

  20. Valera P (557722718) · FAW X80 🚘🛠🛞 · 2025-03-28 · original message · ru ↩

  21. Сергей Сергей (5040352039) · FAW X80 🚘🛠🛞 · 2025-06-13 · original message · ru ↩

  22. 1706 (6158563221) · FAW X80 🚘🛠🛞 · 2025-06-13 · original message · ru ↩

  23. Печной Двор (5216836218) · FAW X80 🚘🛠🛞 · 2025-10-17 · original message · ru ↩

  24. 🇯‌🇺‌🇱‌🇮‌🇦‌ (1707891432) · FAW X80 🚘🛠🛞 · 2025-10-17 · original message · ru ↩

  25. Валерий (7161884851) · FAW X80 🚘🛠🛞 · 2025-10-17 · original message · ru ↩

  26. Андрей Б. (1275682418) · FAW X80 🚘🛠🛞 · 2025-10-17 · original message · ru ↩

  27. Владимир Русанов (646975200) · FAW X80 🚘🛠🛞 · 2025-10-18 · original message · ru ↩

  28. No Comments.☝🏻 (695084771) · FAW X80 🚘🛠🛞 · 2025-10-18 · original message · ru ↩

  29. Владимир Русанов (646975200) · FAW X80 🚘🛠🛞 · 2025-10-18 · original message · ru ↩

  30. Владимир Русанов (646975200) · FAW X80 🚘🛠🛞 · 2025-10-18 · original message · ru ↩

  31. HS Development (204359692) · FAW X80 🚘🛠🛞 · 2025-10-18 · original message · ru ↩

  32. HS Development (204359692) · FAW X80 🚘🛠🛞 · 2025-10-18 · original message · ru ↩

  33. Сергей Куликов (5154529344) · FAW X80 🚘🛠🛞 · 2025-12-04 · original message · ru ↩

  34. Unknown (uid 7996652575) (7996652575) · FAW X80 🚘🛠🛞 · 2025-12-04 · original message · ru ↩

  35. Фаб (769398910) · FAW X80 🚘🛠🛞 · 2026-04-23 · original message · ru ↩

  36. Фаб (769398910) · FAW X80 🚘🛠🛞 · 2026-04-23 · original message · ru ↩

  37. Фаб (769398910) · FAW X80 🚘🛠🛞 · 2026-04-23 · original message · ru ↩

  38. Эдуард Янонис (1292719479) · FAW X80 🚘🛠🛞 · 2024-03-29 · original message · ru ↩

  39. Unknown · FAW X80 🚘🛠🛞 · 2024-03-29 · original message · ru ↩