X-Trail 2.2 YD ETi 2003 T30 - Can I get more than just ECMD

[TheBoss]

Well having discovered that DataScan II can read Consult II I bought one, I have now hit a problem, I can only connect to the ECMD, no connection available other wise to : ECM, BCM, TCM, ABS, SRS, OBDII, WBO2. So does this mean that these are not readable, can you confirm this ? If this is not the case how do I set the ini, etc ?

Vehicle X-Trail 2.2 YD ETI 2003 T30 - Denso ECU Consult II protocol using a KKL VAG COM 409.1 OBD to USB connector. I run Car Gauge Pro on my Android and it gets all the data from the ELM327 connected to the white OBD connector, see attached .pdf.

Thanks

[TheBoss]

I have a picture of the OBD connector so you can see the pinouts, I believe the connections are as follows, number 1 being top left :

1 - CHCK . 4 - CHASSIS . 5 - SIGNAL . 7 - K LINE . 8 - INGN
9 - ABS . 12 - SCI TX . 13 - SCI RX . 16 - 12V

[Tom]

A lot of cars from those years still use Consult I for diagnostics of the other ECUs. This is the case with your car. Pins 12 and 13 are used for the Consult I protocol.
ECM - is the petrol engine ECU - doesn't apply to you
OBDII - is the engine ECU using ISO 9141-2 protocol - doesn't apply to you
WBO2 - is for the wideband oxygen sensor controller - doesn't apply to you

Can you try the "Find ECU" function under settings->communication and see what active ECU Ids you get?

[TheBoss]

Thanks Tom - Will give it ago tommos and let you know. I will create a log and post for you.

The ETi preceded the T30 DCi engine and was built between Jan 2003 and September 2003. Prior to that the 2.2 YD DDTi engine was used from 2001. Aus did not get any of these as far as I know, but Jalal at the Aus Forum can confirm that.

This post on the forum may interest you http://baustralianxtrail.runboard.com/t124626,offset=0 Once I have a good set of results I will post on the UK forums.

[TheBoss]

Test using the "Find ECU" function gave these :

ECU Id 12
ECU Id 33

No idea what that translates into though, one of these must be the ECMD, I would suggest the Id 12 as CGP identifies this as ECU 12 and appears to read from that ? So what is Id 33 ? Created log files from connection to the ECMD, no other connection available ? Please see attached. Warm engine, ignition on only, second file engine running at idle with engine warming.

I notice you say that the Xy is Consult I, this is not what Nissan says ? CGP reads that the input is ISO 14230-4 KWP FAST from what I know. Although CI was used up to 2000, they used CII on the T30 Xy even though it was not OBDII compliant on the diesel till 2004, of course they, Nissan, maybe refering to OBDII compliant vehicles ? In which case I take it it to be Consult II you are saying there should be a K line reading too ? Thanks

[Tom]

You are correct; ECU Id 12 is the diesel engine ECU (ECMD).
I'm not sure what Id 33 is at this stage but I'll try to find out.

Your car uses pin 7 (k-line) to connect to the engine ECU. You can use the Consult II protocol or the OBDII protocol (ISO 14230-4) on this pin. There is also another ECU (Id 33) responding on this pin.
The OBDII connector also has pins 12 and 13 that are used for Consult I protocol. Those pins are probably used to connect to the rest of the ECUs on your car (ie. ABS, BCM, TCM ...).

The factory Nissan tool called Consult II is backwards compatible. It can use Consult II protocol (pin7) for diagnostics of your engine ECU and Consult I protocol (pins 12 and 13) for the rest. This way the car is OBDII compliant for the engine ECU but the rest has to be diagnosed using their proprietary tool.

All ELM327 and Vag Com adaptors can only use the k-line (pin7) for diagnostics. That's way you can not connect to any other ECUs. Except for ECU Id 33 which we are not really sure what it is at this stage.

[TheBoss]

So if I understand correctly NDSII should in theory be able to read ABS, TCM, etc as it is CII or would I need to use NDSI, as Nissan have made it a difficult as possible, to connect (12 & 13) for ABS, TCM, etc ?

Thanks for your prompt feed back Tom. It has been very usefull to have a Laptop based tool that can read CII on the T30 even though it at this stage is limited to the ECMD. It would be great if you get any further with Id 33, if there is a diagnostic mode I can send you a log file from let me know if it help with the development

As a point of interest, you can add this Nissan X-Trail 2003 YD2.2ETI engine to your list of supported vehciles, I will let you know if I get to test NDSII on the DDTi 2001-2003 or DCi engines

[TheBoss]

Hi Tom going to post couple more files for your use. First is ignition on engine not running, then second from start up for idle. Parameter Settings as download, will tweak when I get time.

Just to confirm the status of the engine at 145000 miles still going strong. Diesel EGR not blocked off, no engine mods apart from K&N panel filter and TOYO exhaust. If you want an ESM to compare data this may help - http://www.nissanforums.com/x-trail/962 ... anual.html

[xtsteve]

Hi Boss / Tom.
Was there any final out come to this discussion, as I'm in the same situation...
I want some sort of tool that will enable me to sort my old xtrail, Based in the UK,,
Xtrail, 2003 2.2 di, with what looks like an OBD2 plug same as Boss's

Cheers

Steve

[Jotuka1]

Hello Tom,

Thanks for adding me to the forum. I really appreciate it.

I have a Nissan Xtrail 2006 dCi YD22DTT, it's currently having issues with P2002 send the vehicle into Limp mode.
Apparently the code has become a hard code as I have tried clearing it but it won't go away. I cleaned the DPF
manually removing the blockage of Carbon and Ash in it. NDSII has been able to connect to the ECMD using the
VAG KKL 409.1 Cable. I have some log files for you to see what is happening in the Engine. Currently, the Vehicle
has 211100Miles. Please I need help on how to reset the DPF warning Light and Clear the Hard code P2002 from ECMD.
[attachment=2]20206171910.log[/attachment][attachment=1]20206171858.log[/attachment][attachment=0]20206171854.log[/attachment]