Archives

Finally took the plunge and ordered a Scangauge from Amazon. Got it a couple of days ago and plugged it into my HR15DE CVT Versa/Tiida/Latio hatchback. And waited, and waited, and waited... and it went to sleep. Sigh. Looks like the local version of the car is not OBD-II compatible... Does anyone know the protocol employed the US Versa? Maybe if I tried forcing the right one, it might work.

Just to be sure it wasn't a defective unit, I plugged the Scangauge into a colleagues Jazz/Fit L13 (1.3L iDSI) and it worked!

I'll have to search for another solution then. Meanwhile, the Scangauge may need to go on the local eBay... unless someone can suggest a hack that will make it work?

Gandalf, did you try it with the key in the on position? How about with the engine actually on? I used mine on an older Explorer that wouldn't connect unless the engine was actually on. It was strange, but that's the way it worked.

Finally took the plunge and ordered a Scangauge from Amazon. Got it a couple of days ago and plugged it into my HR15DE CVT Versa/Tiida/Latio hatchback. And waited, and waited, and waited... and it went to sleep. Sigh. Looks like the local version of the car is not OBD-II compatible... Does anyone know the protocol employed the US Versa? Maybe if I tried forcing the right one, it might work.

Just to be sure it wasn't a defective unit, I plugged the Scangauge into a colleagues Jazz/Fit L13 (1.3L iDSI) and it worked!

I'll have to search for another solution then. Meanwhile, the Scangauge may need to go on the local eBay... unless someone can suggest a hack that will make it work?

Did you try setting PIDs to SUPPORTED? What pins are populated on your car's connector? This should tell you what protocol is being used, then you could try forcing that protocol.

Thanks for the inputs. I'll try them after work today and let you guys know how it turns out.

i hv the exact same problem in my tiida purchased in dubai uae. even pid in supported doesnt seem to help. is there any other way to reconfigure this?