V41 Quest/Villager

[mikeluscher159]

Hello, I'm trying to use NDSII on my '01 Nissan Quest/Mercury Villager
It's a Nissan ECU, Nissan Protocol's, And the FSM Dictates using a Consult 2
It "ONLY" has a 16 pin OBD2 Port, as it's a USDM vehicle.

I currently have a ELM327 v1.5 Bluetooth adapter, And a STN1170 Bluetooth adapter on the way

With the ELM, when I use the "Find ECU's" Button in the setting's, After setting the correct port, It find's 30 or so ECU's
But when I try to connect, It says "Invalid Comm" or It will just refuse to connect.

Does my adapter lack the correct protocol? What protocol does this Software Require?
I attached a picture of what my FSM has to say regarding GST/Consult 2 standard's
Any help would be greatly appreciated, And if i'm in the wrong sub-forum, Please Move me

happy holidays to all of you down under

[Tom]

The NDSII software will not work with ELM adaptors. Don't even bother trying.

What engine is in your car? Is it the VG33E?
Does your OBDII connector have any wires on pins 12 and 13?

[mikeluscher159]

This being a picture of my OBD2 port, I'm gonna say yes.

What adapter's are eligible?
And what is the protocol I'm looking for?
I assume STN1110/STN1170's are out?

And yes, It's the VG33E

[Tom]

Your car is one of the odd ones that have an OBDII socket but still use the old Consult I protocol for ECM diagnostics.
You need to use NDSI software and Consult I adaptor with an OBDII plug. I'm aware of only one website selling such adaptors but fell free to look around http://www.ecutalk.com/interface.aspx

[mikeluscher159]

I see.

Does NDS do thing's differently then the Factory Scan Tool

Because all over the FSM, It references using a "Consult II", It even uses a picture of a II.

I just want to be 100% sure before I drop $150+ on something that may not work.

[mikeluscher159]

Also, I read on the homepage that a 409/409.1 VAG COM 16 pin cable would work? Would this work in my instance?
I would be able to bear the cost of a $10 adapter over a $100 quite a lot easier.

[Tom]

The factory Consult II tool is backwards compatible with Consult I protocol. Your engine ECU is in fact using Consult I protocol over the OBDII plug.
The VAG COM adaptor will fit but not work. For $10 you can try it if you want.

[mikeluscher159]

I see.

Well are there any alternatives to that $100 cable?
Any STN adapters? What protocols does it need?

On the supported adapters page it says that several VAGCOM cables have been tested and work.

[Tom]

You need to look for Consult I adaptor that has an OBDII plug. You will find a lot of Consult I adaptors but they all have the 14-pin Consult I plug.
The VAG COM cables listed have been tested with the NDSII software. You need to use the NDSI software.

[mikeluscher159]

So, unless my some magic of untested software, this adapter works with Consult I, don't I just love being a guinea pig , I'm screwed into a $100 cable?