Can not connect with nissan march k12 2003 mode. Because protocol issue. Any suggestion for that
Can not connect with nissan march k12 2003 mode. Because protocol issue l
- 967 Views
- Last Post 01 December 2021
The most common "protocol related" issues are:
- no power on ECU: engine does not started AND/OR key not at ON (II) position
- brake or bad contact of a signal wire in the diagnostic socket
- hanged adapter: need to be reset (unplug/plug back to the diagnostic socket)
- (partially) malfunction adapter ( https://incardoc.com/en-us/thread/Attention-Bad-Bluetooth-adapters-#post252 )
- your car have no or limited OBD-II support ( https://incardoc.com/en-us/article/what-cars-are-supported/ )
For the Nissan models without OBD-II support you might try conection via inner Nissan protocol Consult:
Settings-Protocol-Type of protocol-Nissan QG18DD (EN)
With issues or questions please use IN-APP option Menu-Info-Contact us, so we have a chance to review settings and car responces.
Thanks!
Ive had the same problem with my Nissan xterra 1st error was protocal now ut says that basically wasdesigned for an older phobe n newphone doesnot support old software
Ive had the same problem with my Nissan xterra 1st error was protocal now ut says that basically wasdesigned for an older phobe n newphone doesnot support old software
Upper unswer says nothing about the PHONE age or OS versions at all. Please just read and check upper suggestions.
If you have any issues or questions please use in-app option Menu-Info-Contact us and descripe the case as well as car model/year.
Thanks!
Categories
This Weeks High Earners
Hot Topics
- 1 Top 8 Most Comfortable Cars for a Smooth and Relaxing Drive
- 2 El Mercado de Vehículos Eléctricos Híbridos en España: Perspectivas de Crecimiento 2024-2032
- 3 Could InCarDoc reads Seatbelt state ?
- 4 Attention! "Bad" Bluetooth & WiFi adapters with low quality clones of ELM327.
- 5 App is not any longer available