Running like a PIG

Nissan 4x4 Owners Club Forum

Help Support Nissan 4x4 Owners Club Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
As an eBay Associate we earn from qualifying purchases.
Fez_uk said:
Yes but if he has no serial (rs232) connector on his laptop he will have to use a converter. Which he says he is.
Click to expand...
As long as the USB/serial i/f works as nature intended should be fine, however it may be necessary to set the baud rate etc. prior to running the s/w. 9600/8/1.
 
will these work on imports ie mine lol been running at limp home mode for about year been to nissan (about as much use as swift kick in rollocks) and two other snap on scanners found codes that dont exhist in there armoury or came up with pump timing battery off to reset turns it back into hooligun for 5 mins then flat out at 60 very anoying when used to be tonne up monster
 
jace said:
will these work on imports ie mine lol been running at limp home mode for about year been to nissan (about as much use as swift kick in rollocks) and two other snap on scanners found codes that dont exhist in there armoury or came up with pump timing battery off to reset turns it back into hooligun for 5 mins then flat out at 60 very anoying when used to be tonne up monster
Click to expand...

Sorry mate I have no idea, it's not my field:augie
I was given the link myself and went for it:D
Ask Timbo or rayf3262 for advice on this :thumbs
 
[FONT=Calibri, Verdana, Helvetica, Arial]Here’s a canned explanation of the Nissan Consult interface, apologies if it gets a bit to technical but here goes......

The Nissan consult interface is bespoke to Nissan has been fitted to many of their vehicles. It first appeared on the 14 pin connector then latterly on the 16 pin connector often confused with being an OBD connector.
It is NOT an OBD connector, is is simply a J1692 connector (2 rows of 8 pins) which indeed was/is part of the OBD compliance requirements.

The consult interface connections (pins 12 & 13) utilised on this connector are OEM specific, and can be used by ANY manufacturer for ANY purpose. Nissan chose to implement the consult interface on these connections, this was done on most vehicles fitted with an ECM/ECU.

It is unlikely that any DIESEL Terrano/Patrol or derivative produced prior to 2004 will be OBD compatible. (Just short of Terrano end of life! coincidence..)

So that leaves us with Nissan Consult. This is a very useful diagnostic interface that allows a lot of information to be amassed.
It is a simple 9600 Baud serial interface that uses a bespoke protocol, hence the need to use software that is able to communicate with it.
Many of the software “packages” were designed for the petrol heads and will not work well with the diesel ECU’s.
On initialisation the software is required to poll the ECU and determine which data fields (live sensors etc.) are valid for that ECU and then subsequently request the user selected info from the required data fields to show live sensor data.... If the software is diesel un-aware you are likely to get mislabeled or misleading information.

ECUtalk is diesel friendly.

The hardware required to achieve this is not magic, it is simply a level translation, the serial data from the ECU is 0V to +12V the interface only converts this to –12V to +12V, or thereabouts. Plus in the case of the 14 pin interface provide a serial clock at 16X9600 (153.600 Hz)
The interfaces sold on Ebay often originate from China, no problem they are the masters of copy and the circuitry is well documented and they should work ok.

I hope this helps a bit, any questions feel free to ask.
Cheers

[/FONT]
 
Just been out to try again with the ecutalk program:rolleyes:
Still nothing, not a sausage, dim byd :eek:
Could it be the consult plugin thingy I got is duff?
Can I test it?
Any ideas from the real world much appriciated:D
 
makeitfit said:
Just been out to try again with the ecutalk program:rolleyes:
Still nothing, not a sausage, dim byd :eek:
Could it be the consult plugin thingy I got is duff?
Can I test it?
Any ideas from the real world much appriciated:D
Click to expand...

OK.. first thing, I understand you are using a USB/Serial converter, should not be a problem but we need to figure out if this is working as it should.

So, ignoring the Consult interface pull the 9 pin connector from this and link pins 2 & 3. (paper clip might do)

Next fire up hyperterm (the Windows serial comms prog) and establish a connection at 9600 baud to comN where N is the comm port associated with your serial interface.

Anything you then type in the terminal window should appear on the screen, if it does not then there is a fundamental issue with your serial adapter and we need to work on fixing that first.

If it does work then there may be a problem with your interface... let me know..
 
Ok I've got the pins sussed:thumbs
BUT where do I find this "hyperterm" thing?:nenau
This could be a long night :lol
 
makeitfit said:
Ok I've got the pins sussed:thumbs
BUT where do I find this "hyperterm" thing?:nenau
This could be a long night :lol
Click to expand...
I am no Windows expert (there will be others... Clive?) but from memory on Win XP its in:
Programs:
Accessories:
Communications:
HyperTerminal

My memory of this stuff is sketchy, so beyond that you will have to wait until I get home on Wednesday when I am in front of a windows machine or I am sure someone else will chime in...

I am pretty sure that the issue is with the USB/serial adapter though...
did you install the drivers for this adapter prior to plugging it into the USB port?

If not you will need to remove the adapter, the in Windows device manager remove the "device" then install the drivers and re-connect the USB/serial adapter.

Sorry if this all sounds long winded but that the way it is!
 
Ok I've now found the hper space terminal but cant engage warp drive:doh
Just googlin' dilithium crystals in this time zone:rolleyes:
er Nope, but I have sent a droid to get some. Should be back online in a few parsecs:confused:
Space time continueum permitting................................
 
TARDIS error 00051
I've just checked in the device manager thing. It says my usb-serial port is running properly. It's on comm2 at the mo :rolleyes:
 
makeitfit said:
TARDIS error 00051
I've just checked in the device manager thing. It says my usb-serial port is running properly. It's on comm2 at the mo :rolleyes:
Click to expand...
so......... in Hyper(stupid name)Terminal can you connect to comm2 at 9600 baud? then with pins 2 & 3 connected together can you see anything you type echoed back to the terminal window?
If not... that's what needs to be fixed first...
Some of these USB/Serial adapters are a f~~~in pain....
 
rayf3262 said:
so......... in Hyper(stupid name)Terminal can you connect to comm2 at 9600 baud? then with pins 2 & 3 connected together can you see anything you type echoed back to the terminal window?
If not... that's what needs to be fixed first...
Some of these USB/Serial adapters are a f~~~in pain....
Click to expand...
When I opened hyper terminal it seems to be some sort of dialer uperer. I dont know how to make it do 9600 bauds and then speak to comm2. It asked me for my dialing code though:lol
 
You must log in or register to reply here.

Similar threads

M
Any assistance appreciated
2
Replies
32
Views
529
mruss5891
M
Lazy-Ferret
Wet boot carpet, leaking rear door seal.
Replies
15
Views
322
Thomas-the-Terrano2
Thomas-the-Terrano2
R
White smoke, lumpy running, no power
2
Replies
22
Views
476
Terranical
Terranical

Latest posts

Back
Top